Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×
User Journal

Journal Journal: What Open Source Developers Can Learn From SCO 1

No less than once a week I hear about random corporation violating the license on some piece of open source software. The Free Software Foundation says that this happens all the time, but once the infringers are informed about their violation they typically correct the problem very quickly. Such failures typically include: not including a copy of the GPL or whatever license the software has been released under; not providing source code or an offer to supply source code; blatantly using GPL code and then licensing the complete work under a restrictive license.

Instead of notifying these companies and asking them kindly to comply, and then letting them off scot free, why don't the developers freakin' sue already? Sure, it costs money, but the great thing about lawyers is that they tend to overlook your lack of funds if they can see dollar signs on the horizon. They do it for insurance, liability and accident claims, I'm sure there's some ambulance chasers looking to make big bucks in copyright law too. The whole "sue for revenue" model isn't likely to go away. Large companies are just too pitiful at due diligence to actually follow a license as complicated as the GPL.

So what do you need to pull off this get-rich-quick-scheme? Well, number one is you need some copyrights. Thankfully, that's really easy to get, just hire some student programmers to work on open source and put your company name on the contribution. Once you've got a stake, no matter how small, it's my understanding that you can sue any infringers just as well as the major contributors. Of course, this tendancy by open source projects that are run by corporations to get copyright assignment on all contributions will trip you up.. guess you'll have to avoid those projects. Next, you'll need lawyers. Scum sucking, bottom feeding ones. You'll need them to review violations that you pay people to find in some "work from home" scheme. You'll also need them to send nasty letters and pull dirty tricks so the company can't weasle out of paying by complying with the license after the fact.

Speaking of paying, how much can you expect to get out of these fat corporate giants? Well, if you were to go to court you could expect to get at least "statutory damages" which is a minimum of $200/copy. But that's chump change. Typically any profits the company made that can be attributed to the violation will be awarded to the copyright holder, and that almost always exceeds the statutory damages by an order of magnitude. Then there's the punitive damages, which apparently don't exist in copyright law but always seem to be claimed, which tend to be around $70,000/copy.

So really, suing people who didn't bother to read the license on your open source software and have made a mint by unlawfully distributing your code is so easy even the most Lionel Hutz of lawyers should be able to get you a big fat payout. Then you can hire more developers, more people to look for copyright violations, and more lawyers in an endless regression.

The Almighty Buck

Journal Journal: A Foray Into Shareware 2

My friend Steve Dekorte suggested that I have a go at the old shareware game. He makes a comfortable living off a collection of Mac mini-apps that, he tells me, pull in about the same per year as he got working at a dot com. When I worked at dot coms I got paid above average so it sounds like a pumb to me.

Apparently Windows shareware developers make a lot more than Mac shareware developers, so I've cranked out a (hopefully) useful app called TcpSafe on Windows. It allows you to monitor where your computer is connecting and who is trying to connect to your computer. Good for catching spyware and trojans that "phone home" in the act, debuging sockets applications, troubleshooting network problems, monitoring the network for worms and hackers, etc.

I'm using Paypal for a payment system and I've integrated it into both my web site and the application. The licensing system is per machine. So if you want to use the registered version on multiple machines you've got to pay multiple times. As such, I've set the price really low ($9.99) and hopefully we'll make up for it with volume.

Steve had this great "I've Paid!" button idea which I've duplicated. So if you need to reinstall the software for some reason and it comes up in evaluation mode you can just hit the button and it downloads your license key automagically. Support costs are apparently the killer in shareware, so here's hoping everything runs smoothly!


Slashdot Top Deals

Pound for pound, the amoeba is the most vicious animal on earth.