@haubles @pluralistic @Mastodon
Cory is great on describing the power dynamic of "switching costs" and the Fediverse dramatically turning the tables on that, for the good of each user.
@tchambers @haubles @pluralistic @Mastodon
But Bluesky’s model is even better in that regard!
Currently, in the Fediverse you lose all your posts when you’re moving
With Bluesky, you don’t
https://mastodon.social/@o_simardcasanova/113422975574382875
@o_simardcasanova @tchambers @pluralistic @Mastodon did@you@read the article? It touches on more than either platform’s enablement of user migration
@o_simardcasanova @haubles @pluralistic @Mastodon
Well, to be fair, you CAN download and upload your posts here and not lose them on Mastodon, but point taken that the migration is still getting there, but #ActivityPub is working that out for future version.
I'm still confused how BlueSky migration of social graphs would work IF there were another non-BlueSky entirely other ATproto service overall - and how that would work in terms of interoperablity with those users on the BlueSKy service.
@tchambers @o_simardcasanova @haubles @pluralistic @Mastodon Is that a new Mastodon feature or supported by a third-party tool? I know I can export my posts, but I wasn’t aware of any ability to import those into another Mastodon instance (and it wouldn’t typically work for non-Mastodon instances because the URL path formats are not the same across implementations).
@steve @tchambers @o_simardcasanova @haubles How would the URL format matter? If the posts are being migrated to a new domain you gotta rewrite all IDs anyway (with all the issues re: federation that entails), so the URL structure would be the least of your worries. Otherwise the Sharkey post history import function couldn't work.
I remember reading of at least one weirdo who manually massaged their old posts into the new instance's postgres. We all know it's possible, just prohibitively hard.
@julian @tchambers @o_simardcasanova @haubles Yeah, sorry. I should have been more specific. I was referring to the issues even with a personal domain name (and migrating between implementations with that domain). With two different domains, I don’t know how transparent post migration would be possible with Mastodon.
@steve @tchambers @o_simardcasanova @haubles Yeah, to transparently swap server software (including Mastodon→Mastodon) you'd have to preserve post IDs and encryption keys at the minimum. No idea if anyone's ever accomplished that.
But I think migrating account histories between domains is the more commonly requested feature. Although unless Mastodon implements FEP-ef61 or something comparable, that'll only ever be a content import that loses past interactions by other accounts.
@tchambers @haubles @pluralistic @Mastodon On AT Proto, your social graph is hosted on your PDS
This is for instance why you cannot remove followers, as to do so you would have to write on your follower’s PDS
You don’t "migrate" on AT Proto, you can take your PDS and host it elsewhere, which isn’t the same thing
@tchambers @haubles @pluralistic @Mastodon The existence of other AT Proto services changes literally nothing
AT Proto services are indexers, other services make decisions on what they want to index
WhiteWind is a blogging platform and only indexes blog posts and replies (posted on Bluesky, so it indexes a small subsets of records of the type "Bluesky")
Smoke Signal is an event scheduling platform and only indexes events
And so on
@tchambers @haubles @pluralistic @Mastodon In other words, interoperability already exists