I just posted about the new AtomPub code. There's still some work to do
with it.
Once that's done, I'll build the necessary code to push from one account
to another using the AtomPub API. My rough idea here is:
1. us...@example.com decides to move her account to
us...@example.net .
2. She goes to http://example.com/ , goes to her account settings,
says she wants to move her account, and gives her API
credentials for example.net.
3. example.com pushes activities (notices, follows, faves), in
chronological order, to example.net. (This would probably
happen in a queue handler.)
4. example.com fixes up local subscriptions to user1 to follow
us...@example.net instead.
5. example.com changes the URL (but not the URI!) of user1's
notices, so Web hits will now redirect to the page on
example.net.
6. example.com disables us...@example.com account; can't follow, be
followed, post notices, do faves -- pretty much "silenced".
7. example.com sets up a feed mirror of us...@example.net to
us...@example.com so remote subscribers to the old (.com)
account will receive notices from the new account.
It's not a perfect system, but it's better than nothing.
Also, as far as I know, it's never been done before. Jabber doesn't work
this way; email doesn't work this way.
One big problem is that pushing all that data is going to flood the new
account; this whole process might be kind of hard with a new account.
-Evan
--
Evan Prodromou, CEO, StatusNet Inc.
1124 rue Marie-Anne Est #32, Montreal, QC, Canada H2J 2B7
E: e...@status.net T: 438-380-4801 x101 W: http://evan.status.net/
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
