In light of Dave Winer’s recent post about Twitter since the announcement on TechCrunch that some new API features are on the way, I thought I’d point back to a couple of earlier posts I made about these very subjects. Ie: Using Twitter as a ‘service layer’ and Open Sourcing the Twitter server (without SMS) – that post also talks about the’@dictionary word‘ TwitterBot which I created after having the idea as a proof of concept.
The new Twitter stuff will enable developers to write ‘GroupWare’ too by delivering messages privately. I hope that Obvious add ‘groups’ soon though. Also the ability to distinguish/register an account as a ‘bot’ as opposed to a human.
BTW : Bots should not have ‘friends’ – only followers. That’s how a ‘client/user’ can register with the bot/service more easily. Simply add the user account.
I also use Twitter for server alerts too, letting me know when somthing has completed or gone wrong – this will help ‘privatize’ them without needing an ‘alt’ account.
I started out by asking my followers where I could find a decent search engine that can respond to a ‘human question’ – after not finding a good enough one with a decent API, I plumped for the Urban Dictionary, which can provide very amusing results
One of the unique things about Twitter is the difference in push/pull with info than we are used to. Usually we ‘push’ a post, then ‘pull’ the website or feeds. Here, we have also have Twitter not only ‘pushing’ email, but also SMS – for ‘free’.
That’s so incredibly useful. ESPECIALLY given all the places in the world where mobile phones work, but the internet does not. Third World etc. This should be exciting to people working in remote situations.
Open Sourcing the Twitter server without the SMS capabilities would make the central Twitter.com/Obvious server like the ‘Sun’ where all the other OS Twitter servers would connect like ‘Planets’ – Obvious could then handle and monetize all the SMS transactions (which the OS server might lack) by charging for this feature.
Tweet! Tweet! Kerrchingg!! :)
Oh and I’ve been building a new forum-like content/communications system with RSS and OPML at the heart of it. Imagine ‘structured Tweets’ – with the ability to also attach files – as a payload – can you imagine how easy it is to flow, connect and direct all these via RSS and OPML? Wow!