I’m looking into Takahe and it seems that it’s getting very close to solve this. With takahe, you can use the same instance to serve multiple domains. So you could signup to a Takahe instance and bring your own identity. If you are not happy with the server, you just move to a different service and get your domain to point to the new server.
Hmmm. Interesting. Not sure I follow how serving multiple domains gets you a mobile/nomadic identity?
Are you saying that multiple single-user instances can be run out of a single takahe server?
Are you saying that multiple single-user instances can be run out of a single takahe server?
Yeah, but they don’t even have to be “single-user”. You can set up a domain with multiple identities.
If you are not happy with the server, you just move to a different service and get your domain to point to the new server.
I’m just learning about takahe now, but it very much looks like domains are the remit of server admins, not users. Setting up a domain appears to require admin-privileges on the computer running takahe, not something that an individual user or non-admin group of users can do. So it seems to me that takahe doesn’t facilitate users controlling domains and improving mobility of domains between different servers controlled by different admins, but rather appears to be a tool for a given admin-team to segment their users and move them around among the group of servers they control.
I could very much be missing something here, this doesn’t seem to be a scalable approach to server mobility or a way to extricate yourself from an admin team you’re in conflict with.
Setting up a domain appears to require admin-privileges on the computer running takahe
A takahe admin can not take the identity hostage. An admin can add any domain, but if that domain does not respond to the webfinger query pointing to the actual underlying domain, it will never matter. So at the end of the day what matter is how that domain responds to a webfinger query.
Fair enough. The level of close coordination required between takahe server admins and domain owners seems to make domain migration at-scale somewhere between very expensive and simply prohibitive relative to self-service account sign up though. And I’m not sure I see a clear path to resolving that issue, though it’s certainly an interesting project even if it can’t deliver domain mobility at scale.
