4 ms·
Finally, a cogent explanation. Edit: But missing a key issue, perhaps. > Because Mastodon uses a collection of Instances, you’re not at the beck and call of o
by mirimir 8y ago
Finally, a cogent explanation.
Edit: But missing a key issue, perhaps.
> Because Mastodon uses a collection of Instances, you’re not at the beck and call of one site owner. If you don’t like the direction an Instance is taking, you can pack your virtual bags and go. Mastodon even has an import/export tool that allows you to migrate the people you follow from one account/instance to another.
That sounds great. But if you do "pack your virtual bags and go", is there any way to map foo@bar.net to foo@baz.net? In the email analogy, there's clearly not. You need to tell all correspondents.
- colanderman 8y agoWith e-mail there is a way to migrate without losing your identity, if you own your own domain, and point its MX records at your provider (who is a real e-mail provider and not a "free" walled garden like GMail or AOL). Unfortunately owning a domain is not as accessible for 95% of the population as it ought to be. This concept of digital identity mobility is important to ensure that one's digital life is not tied to a single service provider. XMPP provides this capability as well, through SRV records. Bizarrely, given its aim to free users from walled gardens, Mastodon does not support SRV records [1]. The developers give some excuses about the WebFinger protocol, which basically means that if I want to own my own Mastodon identity, I must run my own server (either Mastodon or a WebFinger redirect). Apparently Diaspora made the same shortsighted decision [2]. I'm surprised and saddened that the concept of identity mobility is seemingly not well understood by those developing decentralized social platforms. [1] https://github.com/tootsuite/mastodon/issues/1931 https://github.com/tootsuite/mastodon/issues/1931 [2] https://github.com/diaspora/diaspora/issues/1109 https://github.com/diaspora/diaspora/issues/1109
- mirimir 8y agoYes, I know that. But email was just the analogy ;) For Mastodon, that would be running your own instance, I guess.
- colanderman 8y agoWhich is unfortunate. I consider myself a highly skilled technical user, and the burden of running and maintaining my own Mastodon server, or even my own Nginx server to redirect WebFinger requests somewhere else, exceeds the free time I have to devote to the problem. (Keeping another VM alive, updated, and configured through the years costs mental energy, time, and money.) Whereas, adding an SRV record to my existing DNS server? That's trivial, comes at no marginal cost to me, and doesn't leave me with the constant mental burden of worrying whether my Mastodon or WebFinger server is available, secure, etc. Owning my own digital identity should be easy. Simplicity encourages adoption, and widespread self-ownership of one's digital identity is key to hindering the growth of walled gardens. Mastodon does not make ownership of one's digital identity simple.
- mirimir 8y agoI totally agree. And it seems like Mastodon devs are starting to take the issue seriously. So perhaps there's hope.
- ColinWright 8y agoTo the best of my knowledge they have always taken account migration seriously. But it's a hard problem, and there are many, many issues to be sorted. As a result it has been and is being discussed in detail in the background while other features have been implemented and rolled out. Some of those other issues were contentious exactly because there was insufficient prior discussion, so the question of account migration is taking its time. As I say, it's hard, so it won't be happening in the immediate future. But it is happening.
- mirimir 8y agoThanks, that's good to know. I interpreted some comments on that ticket as dismissing account migration as almost frivolous. But maybe that's because it's an old and difficult challenge, and I didn't have the context to understand the comments.
- confounded 8y agoSome interesting discussion here: https://github.com/tootsuite/mastodon/issues/177 https://github.com/tootsuite/mastodon/issues/177 It seems possible!
- mirimir 8y agoYes, it seems that every user already has a private|public key pair. It's just that instances are apparently storing users' private keys. And that, for what it's worth, seems like a horrible idea. But whatever, if users had control of their private keys, they could easily move. As long as routing depended on public key hash (as with Tor .onion sites) instead of user@instance. More of a web model, instead of an email model ;)
- colanderman 8y agoThat seems like an overly complex scheme to solve a problem that XMPP solved years ago with SRV records.
- username3 8y agoKeybase
- PKop 8y agoI think this is a good use case for keybase.io It aggregates known (proven) identities, allows all currently verified identities to prove ownership of your next new one.
- mirimir 8y agoI thought of that too. But just keybase.io wouldn't be acceptable, because it's centralized. However, I vaguely remember language about Keybase being a protocol, and not just a site. But I've never used anything but keybase.io and indeed haven't heard about federation. But then there's https://keybase.io/kbpgp/ https://keybase.io/kbpgp/ so ???
- WorldMaker 8y agoThe Keybase verifications (sigchain) are also encoded into the Bitcoin blockchain in addition to stored on their servers if you wanted a more distributed way to check them. https://keybase.io/docs/server_security/merkle_root_in_bitcoin_blockchain https://keybase.io/docs/server_security/merkle_root_in_bitco...