When I click the “Publish” button at the top right of this page, this post won’t only appear at the Web address this blog has occupied since April of 2011. People who have chosen to follow this blog on Mastodon will get the full text on that network–and if they reply, their feedback there will show up as a comment here.
At least, that’s how I think things will work. I’ve only had a couple of days to grasp WordPress.com’s announcement Wednesday of its new integration of the ActivityPub open standard behind Mastodon and other federated-social-media platforms. Since I’ve already had nine other people take up my invitation to follow this blog on the “fediverse,” notwithstanding its ungainly “@[email protected]” handle–and since I wrote about this venture Thursday for PCMag–I hope I’ve got that right.
Seeing this sort of open-ended experimentation happen is a good thing about life in the fediverse. I like participating in a project that’s still in a creation stage.
But the last two weeks also reminded me of the potential costs of setting up shop on a social platform in flux: The Mastodon instance I’ve mostly-happily occupied since last November, journa.host, merged into another journalism-centric instance, newsie.social, with no advance notice visible from its admins. I learned about this from an easily-missed announcement in the Mastodon Web app, after which a post from the journa.host admin team pledged that “Journa.host will continue to operate as an independent server and there will be no changes for our current members.”
And then two apparently migration-induced server glitches left me unable to use my account for an hour or two, after which I had to resolve an images-not-loading issue in one browser.
None of those things amount to an instance-firing offense (for a contrary perspective, see this thread from freelance journalist Zecharias Zelalem), but the experience did lead me to think about what changing instances might be like if things came to that. And the answer would be: not great! Mastodon’s data-transfer support is closer to “settings portability” than “account portability.” To wit, while moving my account to a new instance would let me keep my follower and following lists, my handle would change and my older posts would not show up at my new fediverse abode.
The AT Protocol underneath Bluesky, the decentralized Twitter alternative at which I’ve been spending an increasing amount of time, does allow full account portability–although that support remains somewhat evanescent until a good set of competing “Personal Data Servers” come online. So my Twitter-bailout scenario remains unclear, even if I’m increasingly sure that the answer won’t be Meta’s Threads.
https://robpegoraro.com/2023/10/13/one-step-forward-one-step-sideways-in-the-fediverse/
#ActivityPub #ATProto #ATProtocol #Bluesky #journaHost #Mastodon #newsieSocial #postTwitter #Threads #TwitterExodus #wordpress