Slashdot Mirror

I'm sure the argument that you just happened to luck out is not a strong one.

All it takes is ONE hostile fork to TOTALLY ruin your day when the GPL is used. Just check this out:
http://www.xmule.ws/phpnuke/modules5125.html

As the saying goes, Let's eat drink and be merry, for tomorrow we die.

HopeSeekr of xMule

Glad to see that Newspeak is in such vogue with the proletariat of today! Heil Bush, mein Weltführer!

Poll: Should Bush resign?

I spent roughly 80 hours a week for 2 years of the prime of my life developing an application. I rewrote virtually 80% of the 150,000 line C++ codebase. In short, it was forked by very hostile and childish people who continually kry [sic] "Leave us alone" at my program's site, lol.

The hostile fork started when I was personally targeted by the MPAA for my development efforts on 23 August, 2003

The GPL provides *zero* possibilities for overcoming hostile forks. If they want to copy your CVS (and keep their's private) they can effectively publish your own code before you release your program...which technically makes it "their" code. You cannot obfuscate code in order to get an advantage because the GPL forbids this.

How they won the battle was a systemmatic assault of every website comment section (just search for "xmule and comment") on the internet, attacking both myself (Un-Thesis | HopeSeekr) and the program. When this fails my program's site (www.xmule.ws) is routinely DDoS'd, the worst occuring when our original domain (www.xmule.org) was DDoS'd for approximately THREE months and had its DNS hijacked because of it.

Use the OSSAL dual licensed with the Creative Commons License to defeat the GPL! CCL is JUST AS FREE as the GPL (including no commercialization of *straight copies*) yet doesn't have the viral clause. OSSAL License expressly prevents the use of OSSAL code in GPLd products.

For detailed description of the difference between xMule and its hostile fork, see The Coding Philosophies of aMule and xMule . For a summary of some of the most blatant attacks against xMule by this fork, see Part III: On Hostile Forks.

Sincerely,
Ted R. Smith | HopeSeekr

I spent roughly 80 hours a week for 2 years of the prime of my life developing an application. I rewrote virtually 80% of the 150,000 line C++ codebase. In short, it was forked by very hostile and childish people who continually kry [sic] "Leave us alone" at my program's site, lol.

The hostile fork started when I was personally targeted by the MPAA for my development efforts on 23 August, 2003

The GPL provides *zero* possibilities for overcoming hostile forks. If they want to copy your CVS (and keep their's private) they can effectively publish your own code before you release your program...which technically makes it "their" code. You cannot obfuscate code in order to get an advantage because the GPL forbids this.

How they won the battle was a systemmatic assault of every website comment section (just search for "xmule and comment") on the internet, attacking both myself (Un-Thesis | HopeSeekr) and the program. When this fails my program's site (www.xmule.ws) is routinely DDoS'd, the worst occuring when our original domain (www.xmule.org) was DDoS'd for approximately THREE months and had its DNS hijacked because of it.

Use the OSSAL dual licensed with the Creative Commons License to defeat the GPL! CCL is JUST AS FREE as the GPL (including no commercialization of *straight copies*) yet doesn't have the viral clause. OSSAL License expressly prevents the use of OSSAL code in GPLd products.

For detailed description of the difference between xMule and its hostile fork, see The Coding Philosophies of aMule and xMule . For a summary of some of the most blatant attacks against xMule by this fork, see Part III: On Hostile Forks.

Sincerely,
Ted R. Smith | HopeSeekr

I spent roughly 80 hours a week for 2 years of the prime of my life developing an application. I rewrote virtually 80% of the 150,000 line C++ codebase. In short, it was forked by very hostile and childish people who continually kry [sic] "Leave us alone" at my program's site, lol.

The hostile fork started when I was personally targeted by the MPAA for my development efforts on 23 August, 2003

The GPL provides *zero* possibilities for overcoming hostile forks. If they want to copy your CVS (and keep their's private) they can effectively publish your own code before you release your program...which technically makes it "their" code. You cannot obfuscate code in order to get an advantage because the GPL forbids this.

How they won the battle was a systemmatic assault of every website comment section (just search for "xmule and comment") on the internet, attacking both myself (Un-Thesis | HopeSeekr) and the program. When this fails my program's site (www.xmule.ws) is routinely DDoS'd, the worst occuring when our original domain (www.xmule.org) was DDoS'd for approximately THREE months and had its DNS hijacked because of it.

Use the OSSAL dual licensed with the Creative Commons License to defeat the GPL! CCL is JUST AS FREE as the GPL (including no commercialization of *straight copies*) yet doesn't have the viral clause. OSSAL License expressly prevents the use of OSSAL code in GPLd products.

For detailed description of the difference between xMule and its hostile fork, see The Coding Philosophies of aMule and xMule . For a summary of some of the most blatant attacks against xMule by this fork, see Part III: On Hostile Forks.

Sincerely,
Ted R. Smith | HopeSeekr