Open status my take on the open twitter movement
Here are my thoughts on how to make a twitter like system that won’t break all the time.
My idea is to take the XML-RPC ping service that blogs use and convert it into a one that can deal with statuses.
On top of this you layer what I am calling a status service server, these would be much like ping aggregation services like technorati but with logic for dealing with follows, @aims etc
Lastly on top of this would go the twitter client which would directly work with the status service.
Now this could break in much the same way as twitter could because if the status service goes down then you are back to square one. However I have a fix for this. The user can take their data (followers etc) to any service they like and as its all running on the same protocols they will get the same information from each.
This could lead to smart clients that could detect if status service A is down and if so switch to service B.
follow me on twitter if you wish to discuss this with me or contact me @ here