If you want to think about a *really* hard fediverse problem that would have a *really* big payoff: don't worry so much about users moving domain-to-domain.
-
If you want to think about a *really* hard fediverse problem that would have a *really* big payoff: don't worry so much about users moving domain-to-domain. Figure out domains moving backend-to-backend.
-
puppygirlhornypost2@transfem.socialreplied to jenniferplusplus@hachyderm.io last edited by
@jenniferplusplus@hachyderm.io I'd love to be able to move instances from the root domain to a subdomain... even that is a challenge
-
jenniferplusplus@hachyderm.ioreplied to puppygirlhornypost2@transfem.social last edited by
@puppygirlhornypost2 that seems a lot more manageable, actually. Still not simple, of course. I think the bulk of it would be just a redirect proxy, which isn't particularly hard. But then that proxy would also likely need to trigger update and move activities to be sent to the client's inbox after responding with the redirect, since we probably can't assume that peers will update their cache otherwise. That part is more complicated. And both need to stay in place approximately forever.
-
jenniferplusplus@hachyderm.ioreplied to jenniferplusplus@hachyderm.io last edited by
@puppygirlhornypost2 and then you have to figure out how to make it legible to mastodon, since they decided webfinger is actually the unique identifier for no reason.
-
trwnh@mastodon.socialreplied to jenniferplusplus@hachyderm.io last edited by
@jenniferplusplus @puppygirlhornypost2 actual reason: mastodon predates activitypub by ~2 years, and ostatus-era user identifiers were not required to be (or even particularly recommended to be) https: uris. acct: uris were all over the place, and for mastodon it made sense to use those for "mentions".
then ap came along and strongly recommended https identifiers. a lot of "follow your nose" people in the socialWG, i've read. at the time, webfinger was even more complicated; you needed LRDD too