[mRg]The ‘not being able to migrate identity’ thing on Mastodon is a big negative. I love the decentralised instance thing but if i want to start my own single-user instance with a nice domain or change to another server I have to effectively start again or tell all my followers about my move.
How it stands currently is that, even though its a decentralised design, it encourages people to cluster on one or two servers (like mastodon.social) which, for me, negates the freedom of it.
There are two factors: 1) being able to ‘redirect’ people to your new address ie 301 I’m over on another instance now - all messages get pushed/re-addressed to the new one
2) migrating all your toots / faves etc to the new instance
2) migrating all your toots / faves etc to the new instance
I think 1) is way more important than 2 and should be seen as 2 different streams of work. From what i can tell everyone is trying to solve this whole thing all in one go.
AOL Keyword: phone weasel🌹@emargee yeah i'm not a dev on the project but it seems like it'd be cool if on both instances, you could input on each one that you're forwarding from here to there, and each person's instance should update their follow info when this information is either looked up or included in the toot stream somehow. there's got to be a slick way to do it
@dimspark yup, i think the fear would be that the overhead of a ‘toot’ would increase with the lookup each time but there must be a nice way to do it
@emargee yeah, i don't fully understand the architecture but there seem to be push and pull queues, i don't see why there couldn't be a push out to other instances containing a forward message and the instance just drops a notif on everyone following that person to ask if they want to update their entry