3 ms·
I think one of the fundamental problems with even federated systems is that your identity is tied to your server. If I decide to leave mstdn.io in favor of some
by munificent 9y ago
I think one of the fundamental problems with even federated systems is that your identity is tied to your server. If I decide to leave mstdn.io in favor of some other Mastadon server, as far as I know, I lose all of my followers.
Even email has this problem. It's virtually impossible to change email providers unless you happen to own your own domain that you use for email instead of "@gmail.com" or "@yahoo.com" like most people do. Having your own domain works, but then you have the burden of dealing with the server that responds to that domain.
Strangely, one system has solved this, and they solved it decades after initial deployment: phones. Used to be, if you moved or switched phone provider, you had to get a new phone number. These days, you can "keep your phone number" when you switch providers.
The technology behind that is called Local Number Portability and is managed by the Number Portability Administration Center [1]. That's a private organization, but I think has some federabal obligations for fairness [2]. That sounds a little similar to how domain name registration and ISBN numbers are managed [3].
There's probably a lesson here. Maybe part of the solution for federation and privacy is a single authoritative registrar for root identifiers (i.e. the "@blah" part of your identity). And then all of the federated systems sit on top of that. The individual user owns that identifier instead of the server.
I think you need some kind of level of indirection like these, so that a user's identity isn't directly bound to the federated server they happen to be using today. Basically a mutable map that users control where they can map a logical identity to the current server they are using. So, if your, say, Mastodon ID was "munificent@muni_root", Mastodon would ask muni_root, "What's the current Mastodon server ID for user munificent". If I move from one Mastodon server to another, I just update that one record and everything keeps working.
We could, I suppose, use domain names for this. But in practice (1) that space is already getting used up and (2) the usability is low and the overhead and costs high because that's not what it was designed for.
[1]: https://www.npac.com/number-portability/how-lnp-works https://www.npac.com/number-portability/how-lnp-works
[2]: https://www.npac.com/the-npac/about/neutrality https://www.npac.com/the-npac/about/neutrality
[3]: https://en.wikipedia.org/wiki/International_Standard_Book_Number#How_ISBNs_are_issued https://en.wikipedia.org/wiki/International_Standard_Book_Nu...