The blabber.im #XMPP server shuts down tomorrow.
Although we're now in the final hours, I've been working all week towards something to help. I've put up an initial version of a web-based XMPP account migrator at https://migrate.modernxmpp.org/
It's rushed and still a bit rough round the edges right now, but I really hope it is useful to people who still have data and contacts to migrate before blabber.im goes offline.
If you use it, let me know how it goes! 🙂
Can one selfhost that tool / is the source code public? I'm sure many providers would be interested as soon as it is production ready
Yes, certainly! There is a link to the source in the "About" section of the page.
And yes, I will be encouraging people to host it once it's a little more polished. It intentionally has no server-side dependencies, it's just some static HTML and JS files. No data is sent to the host.
I also plan to integrate the functionality directly into Prosody and Snikket, which I'm really excited about 🙂
It would be good if we could work up a standard process for winding up hosted services, giving users some warning and a timeline for migrating to a new host (where technically possible). Or even a possibility for others in the community to take over admin and financial responsibility for the service.
Agreed. Such a code would ideally be committed to ahead of time, too (it could help inform users selecting a service). For example in this case there were multiple offers of help, including reputable admins of other public XMPP services willing to bring the service under their wing, but they were declined.
Hubzilla is fantastic in that respect. It would be great if @snikket_im could eventually support a similar system of cloning user accounts across multiple servers. But from what little I understand of XMPP that would require some radical changes to the protocol.
@strypey @mattj @snikket_im @wyatwerp Snikket’s way of profitting seems to be to give free server access for a couple months and letting the person who controls that instance send out many invites to use it. Then a few months later Snikket has the option of charging a fee (like ~$2/month). Seems reasonable, but if they were to make changing servers simple then they might be acting against their bottom line.
Account migration is being worked on as part of Snikket: https://snikket.org/blog/dapsi-fund-account-portability/
Our hope is that (eventually) just enough people would either donate or use our hosting service, and help fund the project development. As Snikket is a not-for-profit org, any extra proceeds would get reinvested into the project, upstream projects, and improving the general ecosystem.
How difficult would it be to implement something like the Zot protocol's Nomadic Identity in XMPP? So that if the server hosting my account goes down tomorrow, I can shift to a backup server with no loss of contacts, messages etc.
Could this be built on top of the @snikket_im account migration work you're currently doing?
Even being for-profit doesn't automatically rule out working for social benefit. Supporting server-to-server migration of user accounts is in the roadmap for Element too, despite the fact that their main revenue source is also a hosting service. GitLab is for-profit but everything in a GL instance is a Git repo (issues boards, wikis etc), making server migration as easy as a git pull and git push.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!