Lessig Wagers His Job On Anti-Spam Theory 409
kien writes "Lawrence Lessig is betting his position at Stanford on his anti-spam legislative recommendations. From his blog:'First the analysis: Philip Jacob has a great piece about spam and RBLs. The essay not only identifies the many problems with RBLs, but it nicely maps a mix of strategies that could be considered in their place. But, alas, missing from the list is one I've pushed: A law requiring simple labeling, and a bounty for anyone who tracks down spammers violating the law. Here goes: So (a) if a law like the one I propose is passed on a national level, and (b) it does not substantially reduce the level of spam, then (c) I will resign my job. I get to decide whether (a) is true; Declan can decide whether (b) is true. If (a) and (b) are both true, then I'll do (c) at the end of the following academic year.' The Declan referred to in point (b) is Declan McCullagh." Update: 01/07 02:45 GMT by T : Speaking of whom, here is Declan's acceptance of Larry's bet.
something missed (Score:3, Informative)
Re:A is A (Score:2, Informative)
Re:A is A (Score:2, Informative)
Well, you're entitled to that opinion. But have you read Professor Lessig's book The Future of Ideas [amazon.com] where he academically supports his argument.
It's easy to have an opinion and forecast the future (as you have done). It's much more difficult to have an educated opinion and forecast the future with references (as Lessig has done).
Here's one slashdotter that smells a troll.
--K.
Re:NATIONAL law will stop third-world spammers? (Score:2, Informative)
That's a valid point. It leads to what I personally call a "slashdot paradox". I'm outraged that a Russian programmer (and then, the company that employed him) was prosecuted here in the US for software that is legal in Russia. Yet if Prof. Lessig's law is passed in the US...paradox. It could be argued that laws passed in the US have typically been adopted in one form or another around the world (which sucks...ref: DMCA) but that could be countered by the jurisdictional nightmare that the RIAA/MPAA have run into while trying to prosecute Kazaa.
The blessing and (for right now at least) the curse of the Internet is that it globalizes the public commons. We're only now beginning to confront all of the issues that are raised by this fact.
--K.
Re:Please resign now (Score:2, Informative)
Actually, after reading his book [amazon.com] I'm more inclined to think that he understands the issues at stake on a different level.
--K.
Re:First problem with this solution: (Score:3, Informative)
Crap, I've made quite a few posts with the double-S up to now... ugh! Gotta love Google Suggestions though
I'm not sure about this. The success of Bayesian filtering (rather, Classification) is that it learns what you, the end-user, considers SPAM. How does a SPAMmer learn what you, personally, don't consider to be SPAM?
Currently I get a TON of SPAM with "jm4n" in the subject (my most common email username), and often it sounds like a reply to a personal email ("thanks for your email! Look at my web site and see me naked!").
But the point is, since it learns, and it's completely based on individuals (rather than some generic description of what constitutes SPAM), it works rather well -- better than you might imagine. I suspect this will work in the future.
I also mentioned:
If some implementation were to add common word-groups instead of just word occurrances, it might even be more rock-solid
Currently Bayesian classification is extremely simplistic. It classifies word-counts, and figures if the word "Viagra" never appears in "real" mail, and often appears in "Junk" mail, then this is a key indicator that this is SPAM.
If this were extended to word groups (say, groups of words that appear together frequently, like "penis enlargement" or "work from home"), it could even be more effective. I'm tempted to work on some Perl scripts to implement this even further than what Mozilla does (and, being on the server-side, stop wasting bandwidth on my DSL; not to mention multiple-client compatibility)...
Re:First problem with this solution: (Score:5, Informative)
Re:Sting the bastards into oblivion (Score:3, Informative)
Of course, this highlights another point I think most people are not aware of. For network providers, spammers can be big business. Many of the bigger spammers purchase fatter pipes than many of the big technology-centric companies out there. As much as ISPs despise the headaches spammers bring them, spammers are also among their biggest clients. Spammers consume backbone bandwidth at rates that few other businesses do and this is translated into profits at a time when the ISP business is pretty rough. Since most ISPs require spammers to pay upfront for their bandwidth, this is a welcome addition to the bottom line. Obviously there are people sending spammers money or they wouldn't be able to afford these network pipes.
Re:First problem with this solution: (Score:4, Informative)
Apple has it set up in a very friendly way. It prompts you initially for mail it thinks is spam. At that point it has preliminary training from Apple plus whatever you give it. At a certain point it figures it is accurate enough and goes off on its own automatically.
As I mentioned, after a little training myself, it has yet to make a mistake. It is amazing what that does to your workflow!
Don't get me wrong. OSX Mail isn't a perfect mail client. It isn't aware of the blockquote HTML tag, for instance. And I hate how it uses a drawer that isn't resizable for its folders. Unlike the old Claris Mail it doesn't have scriptable triggers for certain mail events either. (Of course neither do most mail clients, especially on other platforms) But other than that it really is very, very impressive.
Re:Rubbish (Score:2, Informative)
The analogy you are trying to make doesn't work. Refusing to accept your electronic mail is not the same thing as killing you. Killing you is immoral and illegal. Configuring my mailer to refuse electronic mail from your ISP is neither.
I suppose the problem here is the use of the phrase "collateral damage". It is an unfortunate military metaphor which does tend to suggest the analogy you are trying to draw. But it won't work.