In the end, the best hope is that gains enough traction to be adopted by would-be Twitter competitors, thereby insuring that people do have some control over the network they create on the service, have access to the full archive of posts that they wrote, and can generally be insured that the investment they make in the service won’t be devalued over time through business decisions made by the service provider. An alternative outcome where people run their own servers in the same way that they run their own blog software seems less plausible to me.

Some good writing from Rafe on the Twitter/

I left a comment:

There is also the (now stale) Jaiku code base -

It has XMPP at its core, and at one time I had believed / hoped that Google was going to enable one-click federation through Google Apps for Domains.

I don’t think a MAJORITY would ever run their own Twitter/Tent/Jaiku/whatever servers. But, does it make sense to push for a set of systems that CAN be run that way?

And, in much the same way as I use my domain with a few link-rel’s to use MyOpenID to be able to have my own OpenID without actually having to run a server, that would end up being the same level of distributed namespace.

I’d love to see several strong micro-blogging services — some commercial, some open source, some running their own — all being able to interoperate, in much the same way as there are blogging services.