this post was submitted on 16 Oct 2024
128 points (99.2% liked)
Fediverse
28396 readers
121 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It would be nice if there was a way to handle instance/user migrations. If an instance gets their domain name taken away, there's no way AFAIK for the admin to say "Here's our new location, with a verifiable signature". Likewise there's no way for a user AFAIK to move their account with a verifiable signature that the new one is still them. Ideally this could all happen automatically with signatures getting synced automatically and all that.
I'm sure it would be a lot of work and no idea if ActivityPub would get in the way, but it would give people a lot more assurance that they didn't pick a server that will screw them over by going down.
It totally would. In ActivityPub, all objects (like users and posts) have an identifier that includes the domain name. For instance, your ID is
https://midwest.social/u/m_f
. That's what identifies your user. There is no way to change an ID - the point of an ID is after all that it stays the same and still refers to the same entity. This is a pretty serious limitation of ActivityPub right now unfortunately.I wonder who was the idiot who made a persistent ID for identity reliant on a third party factor that can be trivially taken away.
Any plans for solving it that are known?
Not as far as I am aware - I don't think you can really fix it within the protocol, i.e. without a breaking change. Then you may as well make a new protocol.
I think there's a FEP that could (or fixes) this. To my understanding ID can be any URI, so there are better ways. I guess it's hard because it would brake a lot of stuff or how mastodon is build.
Any FEP trying to fix this will be incompatible with existing instances, so I don't really see how it's gonna work.
Yeah, it sucks. But I think that at a certain point it will need to happen if we want to make ActivityPub better with better portability.