BOUNTY THREAD - $$$ for code

[SeqTester]

I have a question, lets say you DO send him $50 after there is a fix. What happens if SOE patches the next day and it breaks?

I am sure there will be lots of "I paid you $50, refix it again!!!" posts. I am not saying YOU will, but I am sure there would be someone saying it.

my 2cp

[orenwolf]

That's quite possible. But at the same time I don't think a Dev would risk the ire of the community by saying "pay me $50 again or no fix". That goes against the spirit we've seen in the ShowEQ dev team thus far.

Remember, the payment is for motivation more than anything else. Once someone writes something, they tend to want to imporive it, and care about the code itself. I have faith that a dev would continue to make "reasonable" changes without becoming unmotivated, just like they always have.

Now, if SOE severely changed everything a day later, then yes, I could see said dev throwing up their arms and becoming unmotivated, just like you or I would if you built something and someone took away the foundation, but I think that's very unlikey, since it would likely generate the ire of the playerbase again, as the last major change did.

It's far more likely the subsequent fixes would be "incremental", and such fixes tend to come fairly quickly on their own. It's these "post-expansion" changes that are usually difficult.

[The Duck]

True developers will work regardless of whether or not there's a monetary incentive. At jobs I've done in the past regarding computer work, I could hardly understand why I was being paid. The work was fun.

That's fair, but it's also fair to say that developers occasionally need extra cash for one reason or another. I myself have been programming for the last 10 years, professionally for about 6 of that.

I frequently find myself taking small projects that I can do in a week or so in my spare time at $80 an hour to pound out some utility for someone or another in my off time. I don't *need* another job, I do it because I like doing it, get incentive to try out new technologies, and at the end of it all, I gave up playing EQ at night for about a grand. Which...I usually blow on some new game or piece of hardware.

I have done code for free, yes, but it's not often. I program stuff all the time that I'm just messing around with, but it rarely goes anywhere.

If I was comfortable with the Linux environment, I'd probablly be on the SEQ dev team, but I'm not. Perhaps I might if it stayed broke long enough to become more than a minor nuisaince, but I'm still not to that point.

If the SEQ project was in C++/ASM in a windows development environment, I'm sure I'd be working on it when it broke. As such, the thought of learning a new development environment (debugging in any compiler you haven't used for years just sucks, period) isn't something I'm willing to do at this time.

That being said, I think it's fair to say that providing the people who already have the environments set up incentive to fix the code even when it isn't one of their personal priorities is a good idea. At worst, it provides someone like me the opportunity to code in an environment I am already familiar with, and turn that money over to those working in one I am not. At best, people like me finally get off our lazy asses and learn Linux, which just hasn't been a big priority for me over the years. (Frankly, a piece of software no one is getting paid to fix being broke for a month just doesn't really concern me. Once we approach 3 months, then I'll start to be annoyed. )

*quack*

[devnul]

Has it occurred to anyone that the very best way to keep SEQ not working is to put a tweak to the network layer on test?

As long as SEQ is not fixed they may take a very long time to patch. In fact the NW code may never get moved UNLESS SEQ is working.

I think we may have trained them to use the best and probably ONLY successful strategy they can employ to keep SEQ from working. Attack us at our weak spot.. our laziness.

dn

[mvern]

If it was just a "tweak", it wouldnt be a big deal. I kinda doubt they'd maintain a seperate codebase just to be sneaky with the evil seq users.

[Lyroschen]

I don't think Sony is really all that stressed out about SEQ. It would be a silly waste of resources to try soooo hard to interfere with something that's not causing them harm, or costing them money. Cursory attention is enough for such programs. Folks stupid enough to discuss their use of the program in game, or running up to a hiding GM, and starting a conversation, etc. The real threats are things such as registering expansions for free, crashing servers, getting GM status abilities, and interfering with the game enjoyment of other players.

Gaining a few advantages in the game may be an annoyance, and if they can put an end to it with minimal effort then they surely will. But, it's not money-smart to expend exceptional amounts of resources on it. The added security seemed to correspond with the release of LoY, which happened to be their first fully-online expansion release, and may have been subject to hacks allowing folks to flag their accounts for free. Even if it wasn't that, specifically, that's the type of motivation that would cause SOE to throw out such a hastily and crappily organized struct change. I seriously doubt SEQ was a major concern. But, that's just my opinion.

From the sound of it, waiting for SOE to stabilize things a bit before going nuts on fixing SEQ is a good plan. It's easy to get burned out on something like this, and having to start over repeatedly would be too much.

I appreciate your response, Mvern. Having an idea of what to expect goes great lengths to curbing withdrawl anxiety. \\=^ ) I wish I could e-mail you a beer for all your efforts.

[CybMax]

I am in on the idea..

Ratt: Make a collective box with who donated, how much is in the pot, and keep it updated.. 1st one to solve the problem gets all the cash..

If Ratt makes this "official" with updated status of how much is in the pot at all times, one of the devs might just think "hmm.. i got nuttin special to do this weekend.. and why not make some cash" or whatever..

Think it is worth a try.. at least should put an end to the "i fixed the god damned code last time, and got $0 for it"

[Jel321]

If you look at the front page for SEQ you will see:

Want to support ShowEQ and the EFF... and recieve a nifty icon and tag to show you contributed? Click here

I dont think Ratt would turn down free money but this is the method he has chosen.

Besides, look at the insane uproar on these boards when SEQ is down and people are paying nothing for it.

Can you imagine how disgusting it would be if someone sent Ratt (or any of the devs) 50 bucks and then SEQ was down like this? Scary.

[orenwolf]

Again, this isn't to pay for ShowEQ.

This is to pay for the time a Dev uses to fix it.

If it breaks subsequently, as I said, the devs have been quick to fix it - with the exception of breakage following an expansion, as we have here.

I for one wouldn't blame a dev at *all* if sony pulled a major code change on them - that's the risk I take - but, as I've said in earlier responses, it's far more likely they would only be minor changes - changes that the devs correct reasonably often.

My primary goal is to get us out of the "Ykesha Rut", which I believe requires a certain abount of mundane work to do.. after the major changes are in, minor changes, I'm sure, will appear as they always have - within hours or days of the patch.

[BlueAdept]

Originally posted by orenwolf
If it breaks subsequently, as I said, the devs have been quick to fix it - with the exception of breakage following an expansion, as we have here.

Actually there have been several periods where EQ hasnt worked for extended periods of time. I think the longest it was broken was when Kunark came out. The encryption was changed from 16bit to 32 bit. There were many people saying that it would never be cracked and that it was the end of SEQ....it wasnt.

I for one wouldn't blame a dev at *all* if sony pulled a major code change on them - that's the risk I take - but, as I've said in earlier responses, it's far more likely they would only be minor changes - changes that the devs correct reasonably often.

With the cart system in EQ now, SEQ isnt obsolete, but it may narrow the user base quite a bit. I still prefer to see the map on my other monitor, but I only use the decoder (when it was working) when there is something Im specifically looking for (like to see if an epic mob is up). It only took sony 3 1/2 years to realize that people really want a map to see where they are.

You must not have been using SEQ long enough to remember when they would do weekly and sometimes daily encryption changes just to break SEQ. I would put anything past Sony, but now with the cart system, I dont know how high a priority it will be.

My primary goal is to get us out of the "Ykesha Rut", which I believe requires a certain abount of mundane work to do.. after the major changes are in, minor changes, I'm sure, will appear as they always have - within hours or days of the patch.

Ratt has already provided a means to make a donation. The EFF is a good organization and one that needs to be supported.

Making a "pool" isnt a good idea because then it creates an aura of competitiveness where devs might not share code with each other because it might help another dev get further ahead of another.

It sounds like Mvern already has it working on test and is just waiting for it to go live. I dont have a problem with that. In fact I think it is great that a dev is using the test server so that in the future, SEQ will be ahead of the game.

After 4 years, I am really supprised that EQ (let along SEQ) is still alive and kicking. I am really happy that there are people who still care enough to keep SEQ alive. I still feel that Sony should be supporting this project because without it, I believe a lot of us would have quit EQ long ago.

[Fantastik]

Originally posted by The Duck


If the SEQ project was in C++/ASM in a windows development environment, I'm sure I'd be working on it when it broke. As such, the thought of learning a new development environment (debugging in any compiler you haven't used for years just sucks, period) isn't something I'm willing to do at this time.

*quack*

Heh, SEQ aside, as one of your "FUN" projects mess around with some code in linux. Actually, first checkout www.gentoo.org and get a development box up and running. Having a box litterally custom compiled by you to start with has a geek factor on its own.

I used to code heavily for MacOS and Irix (Back in the days when windows was a toy OS and if ya needed to do any real kind of graphics ya did it in Irix, or cheaper, on a mac). I was getting frustrated with MacOS for one reason or another and having time i started fooling around with linux when it was very infantile. It's come a long way.

The compilers are now increadably robust. Actually, they are better than anything found in the windows world for pure code crankage. CVS rocks too. Takes a while to find an editor you like, and the framework if you are used to using one, is lacking or not there at all.

Coding is done a little differently in linux/unix. The tools are robust, the pretty compiler graphics/debugging are not. However, if ya play wtih it a bit, and actually get a feel for it, its REAL nice. Coding with an editor is set up for text/keyboard use. Being able to hot key around large chunks of code, colapse and expand fuctions, jump to fuctions, ect all without having to take the time to use a mouse or some goofy interface is nice. Any serious coder will understand what I mean by this.

I'm not advocating you switch... your bread and butter seems to be on what ever platform you are coding for. But for simple enjoymnet of coding stuff for yourself, linux is really, really fun to screw around in. You ahve total control over everything, everything is well documentd on the net, and if ya cant find docs/info jsut look at the libs or source.. its all there for ya. Its a ton of fun.

Just my 2cps.

[devnul]

"If it was just a "tweak", it wouldnt be a big deal. I kinda doubt they'd maintain a seperate codebase just to be sneaky with the evil seq users." - Mvern

Well they ALREADY maintain a seperate codebase. That bit would be just never move to live. I mean it's not like they ever REALLY test the new code on Test anyway.

Sort of a chloroform deploying portable enticement snare for SEQ programmers.

Is it worth their trouble? Well they try a lot of other much harder technically things which all failed. Why not try psyops? A lot less work. And if they are it is succeeding better from a resources expended vs SEQ downtime perspective. Mainly because we are _not even aware we are under attack_.

I want to take this time to thank you for all your efforts btw Mvern. SEQ has continued to exist recently largely because of you. We owe you much.

dn

PS Bottom line. As long as they keep different netcode on test SEQ does not work on live. They have to have noticed this.

[orenwolf]

Originally posted by BlueAdept


Ratt has already provided a means to make a donation. The EFF is a good organization and one that needs to be supported.

I never suggested otherwise. Doesn't change the fact that a "tip jar" may provide motivation.

Making a "pool" isnt a good idea because then it creates an aura of competitiveness where devs might not share code with each other because it might help another dev get further ahead of another.

Well, that's rather unlikely, since the code would be released as OSS anyway. Moreover, as I've already said, if it turns out the multiple people contribute to the fix, it'll be split up as such. I seriously doubt the devs would choose to not collaborate for $50.

[Alfred]

You are obviously a "the glass is half full" kind of person.

[fryfrog]

what about all the people that worked to get showeq to THIS point, where a "fix" is possible? if you take away the work of EVERYONE that has contributed to SEQ thus far, a "fix" would be pretty useless.

i believe that all of the SEQ devs would release a fix when they had it working if they were paid or not, because you don't come 4 yours on an open source project for the money. sure, a "tip jar" would be nice... but it would be unfair to ONLY give it to the dev that solves the problem. i would be willing to bet that if all of you willing to "tip" a dev would use the money and go take a programming class or buy a programming book and help out, the devs would be much more thankful.

just my humble opinion. as a fair number of people have pointed out already, SEQ has been broken badly before. broken for a long time even. eventually, it gets fixed. sometimes its someone who no one has seen up until that point (kinda like mvern) or one of the old time devs. thats the beauty of open source. help them fix it.