I'm Paul Bissex, and e-scribe.com is my consulting business. I build web applications using open source software, especially Django. In the '90s I did graphic design for newspapers and magazines. Then I wrote technology commentary and reviews for Wired, Salon.com, Chicago Tribune, and lots of little places you've never heard of. Feel free to email me.
I'm co-author of "Python Web Development with Django", an excellent guide to my favorite web framework. Published by Addison-Wesley, it is available from Amazon and your favorite technical bookstore as well.
Built using Django, served by Apache and mod_wsgi. The database is SQLite. The operating system is FreeBSD, on a VPS hosted at Johncompanies.com. Comment-spam protection by Akismet. Vintage topo imagery from the Maptech archive. The markup engine is Markdown.
Akismet, bitbucket, del.icio.us, Django, Emacs, FreeBSD, Git, jQuery, LaunchBar, Markdown, Mercurial, OS X, Postfix, Python, Review Board, S3, SQLite, TextMate, Ubuntu Linux
At least 96060 pieces of comment spam killed since January 2008, mostly via Akismet.
Over on the Technorati blog I see that there's a summit on web spam happening next week. That's good. Link farms and spam blogs have been driving me batty.
For combatting the phenomenon from inside tools like Technorati, IceRocket, Feedster, Google Blog Search, and so on, I think our best bet may be collaborative reporting similar to the Razor or Pyzor email-spam-reporting networks.
On the model of Craigslist, last month Blogger introduced a "Flag" button at the top of the screen of all Blogspot-hosted blogs, which is on the right track. But nobody except Google has access to that information. A shared reporting system would mean that before I added an alleged blog to my index, or aggregator service, or whatever, I could query that central database to see if that URL had already been flagged as spam by other users.
This tech is already well-proven with email spam. I run Pyzor on my mail server, and when messages come through to my spamtrap addresses, they get immediately reported so that other users can benefit from that information. Likewise I benefit from the reports made by other users.
Obviously the system would have to be protected against poisoning by vindictive spammers, who might be tempted to report, say, all the URLs in Technorati Top 100.
Lots of other people have written about this in the past few months: David Sifry of Technorati, for one. There's also the Fighting Splog blog, and services like Splogreporter.com that may eventually be used in the way I'm describing. When Google launched their new blog search tool, it was immediately criticized for being full of spam blogs. That's an astounding oversight on their part, but mostly it points up the fact that there's as of yet no standard for attacking this problem. Let's create one.
Thanks for reading! Please note: Your comment will not appear until approved, which may take a few hours or more. Spammers will be torpedoed.
Booktools
2 comments
A different kind of URL shortener
4 comments
The syncbox
2 comments
Branching and merging in real life
8 comments
Summer Spam
1 comment
malpaso
Understanding tuples vs. lists in Python
13 days ago
vj100
Understanding tuples vs. lists in Python
13 days ago
scott
Bicycle Repair Man bundle for TextMate
19 days ago
Jasmine
Trying to send eBay a message?
56 days ago
Smok Cigs
Let's play a game: BASIC vs. Ruby vs. Python vs. PHP
93 days ago
Copyright 2012
by Paul Bissex
and E-Scribe New Media