The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#61
|
|||
|
|||
Quote:
Quote:
By the way, I work ten hours a day programming (just not PHP), and I appreciate your dedication and generosity, but ten hours for a hack is really not that much. I understand the effort and investment it takes, people, but as Miratos said, some stuff being said here is worded pretty badly by hackers trying to make a point. |
#62
|
||||
|
||||
And do you get paid for those ten hours of programming?
|
#63
|
|||
|
|||
Quote:
As for programming what do you make $20 an hour? If so thats $200 that I've sacrificed in order to share my work. Not really that much? How about you donate that to the hackers that sacrifice their time. Quote:
Hostility and misunderstanding? You have your mind so locked on your own views that you're disregarded the opinions of those that do hack. So I should thank you on behalf of the hackers for your hospitality in making vb.org a greater place. You think you can understand this community by just walking in and telling those of us that have been here and spent endless hours at vb.org that our opinions and views are wrong? I think it is you that is mis-understanding, we create hacks for members to use, not tell them to make their own else why would we make any? or why would this community exist? This thread is clearly aimed at people using other hackers code and making it their own, they are the ones that I say write your own work. If you want to start a thread bashing hackers and their work because they don't do enough then you're at the wrong place, because it really seems as though you're trying to be hostile with those of us that do hack. So before you accuse me of telling everyone to write their own hacks, next time read the topic first. Regards, g-force2k2 |
#64
|
|||
|
|||
I'm going to sum up this thread plain and simple: not only is it a rule that has always been enforced at vB.org but just now stated, but IT IS ILLEGAL to do so in the first place.
Please, no more challenging of the rule or our authority to enforce it. I'm not above closing the thread. |
#65
|
|||
|
|||
Quote:
The point is though... yes, you're "not telling people to make their own hacks", but you're also "telling people not to modify existing hacks" (without the permission of the author). Look, I'm all for the regs here, it's illegal, and I wouldn't even think about it. But some of the "if you want them so bad, learn PHP" is way out of line, don't you see? |
#66
|
||||
|
||||
Quote:
Quote:
|
#67
|
||||
|
||||
Quote:
Quote:
Quote:
Quote:
|
#68
|
|||
|
|||
I just started to recently visit vb.org on a more frequent basis, and have not taken a close look at the VB2 hacks. What would happen if I write a hack that already exists for VB2 without knowing about a similar VB2 hack?
|
#69
|
||||
|
||||
There's nothing wrong wirh writing your own hack. The problem is taking someone else's code, porting it and then posting it as your own.
|
#70
|
|||
|
|||
I'm neither a hacker nor a programmer, just an average visitor to vB.org. I remain amazed by both the generosity and knowledge of the authors of the mods presented here and wish in no way for anyone to infringe upon their rights.
However, as an average "joe" visitor when I see a vB2 mod that I hope will be updated to work with vB3 I am left wondering if this will ever occur. Is the author working on it? Gone away, lost interest and could care less about updating their mod? Or are they feverishly working on an update? Might there be a pragmatic way for vB.org to inquire of the authors their intentions? Might they be asked if they are willing to allow others to carrying on with updating (with credit given) if they have no interest in doing so themselves? Might there be a way for vB.org to help streamline the process for everyone involved? I dunno...just asking. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|