Interesting; was thinking about this myself recently - currently based in WA - but if we opt to moving to a new country altogether I believe we would always be liable for US fed tax which makes it a little less appealing (assuming we'd end up then being 'dual-taxed').
I recently got going with ReadMe for a side project* for documenting my API and can attest that both Greg and Gabe have been extremely responsive at fielding my bugs and feature requests.
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.
Hey Andrzej, thanks for the feedback - sounds very logical. You're right - dropping it on GitHub will not make any $'s, but it might enable one or two other developers to get some value from it, and if I'm honest, that's ultimately what I want.
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 pepijndevos. twitblock is a good anti-spam tool for users, but it's not an API like TWASE, so 3rd parties cannot integrate as easily.
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).