jchivers
A Google Feed API Alternative
The ReadMe product is very well polished and the support of Markdown means writing documentation is easy without a complicated editor layer to learn. There's also a palette of pre-configured widgets that you can drop into your pages to handle embedding code, images, custom HTML/CSS, tables, etc. if you want to get fancy.
Nearly every time I log in there's a new feature, bug fix or enhancement - it's great to see the guys build such a useful tool so quickly but without impacting quality or uptime.
* ReadMe powers http://dev.avisohq.com (warning: work-in-progress)
ReadMe (YC W15) Creates Crisp Documentation for Developers Using Your APIs
Dave McClure: The Gospel of a Lean VC [Entire Talk]
I'm not worried about making money from it per se - but would be happy to keep it maintained, updated and bug fixed if I could derive some nominal fee from it (I guess licensing).
I designed it to be extremely modular, so developers could add new spam checks and tune it to their needs with a minimum of fuss - it just might take some time to get all the components installed + running (I could create an install script methinks).
Thanks again!
I agree though that basic anti-spam filtering that'll catch the majority of spammer accounts is fairly basic, but it's still something you'd have to maintain and keep up with (as it's a somewhat moving target).
Ask HN: TWASE - Open Source or something else?
Three years ago I built an anti-spam engine for Twitter - http://twase.comI've not spent much time maintaining it since, and I have around 3 active users today.My current plan is to take the source and db schema and dump it on GitHub, but to get it up + running on your own server(s) isn't easy as it's got quite a complex backend.However, spammers/bots are still rife on Twitter and I can't help...