On 7 Sep 2009, at 16:36, Chris Messina wrote:
I'm curious if you goal is to be able to publish/create content within both contexts or — to use the language of yore — if you'd rather setup up master/slave relationship?
The relationship would be one between peers or equal status. Of course, the person joining the accounts together might just want to post messages just to one and treat the other as a slave.
I don't use Twitter, but I think this is conceptually similar to the Twitter bridge, but between two StatusNet instances rather than Twitter and one StatusNet instance. As each side would be a StatusNet instance though, we should be able to offer tighter, better, more reliable integration.
Finally, is this a common problem or just something that you'd like to have? Where might this situation show up in the wild? And when it does, would people want to copy ALL their posts, or just some? (Which I think could be a more interesting use case...)
Other people can probably come up with other use cases. Moving accounts is just one of them.
Another reason would be network resilience - not relying on a single point of failure. If identi.ca goes down, I can keep posting to example.com and hopefully (not sure of the details of the OMB spec in this area), identi.ca would pick up my messages when it resurfaced.
Lastly, I think it would be nice for this to be possible just for architectural reasons: StatusNet is supposed to be about decentralising microblogging; accounts shouldn't be tied to a single server.
-- Toby A Inkster <mailto:[email protected]> <http://tobyinkster.co.uk> _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
