+
-
@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 @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 @haubles @pluralistic @Mastodon The existence of other AT Proto services literally change 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)
Smoke Signal is an event scheduling platform and only indexes events
@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
This is a bonfire demo instance for testing purposes
Automatic federation enabled