hot take maybe but i think that activitypub vs atproto is really just an implementation detail and the actual divide is between corporate and non-corporate networks

[ana@starlite.rodeo]

hot take maybe but i think that activitypub vs atproto is really just an implementation detail and the actual divide is between corporate and non-corporate networks

[mcc@mastodon.social]

@ana There are elements to the atproto design which make it difficult for atproto to ever be hosted by a non-corporate entity.

[ana@starlite.rodeo]

aspects of a non-corporate social network have previously been able to exist alongside the corporate one, but increasingly this is becoming untenable and these two worlds are going to continue to separate

[ana@starlite.rodeo]

@mcc people are attempting to make it work anyway, and i don't want to cast any shade on their efforts. i think it's a good and noble cause

however, they seem to be making the assumption that corporate bluesky would never "defederate" from them completely and i don't think that is going to hold up at all

and then once that happens they've effectively built very complicated fediverse instances. maybe it would have been less trouble for communities to start with the fediverse instances that you can already set up! but the assumption above is preventing that from seeming reasonable right now

[mcc@mastodon.social]

@ana yeah i keep thinking about how there used to be that whole xmpp infrastructure for alternate clients talking to google and then one day google just turned it off

[ana@starlite.rodeo]

@mcc yup, that's really exactly what will happen i think. at that point they may find it easier just to migrate to an activitypub implementation of some sort than keep going with atproto, but they surely won't be migrating back to corporate bluesky

the point is that social media is about people first and implementations second, and everyone who isn't able or does not want to exist in that corporate world is going to end up on the "fediverse" eventually, no matter how many steps it takes to get there

[oblomov@sociale.network]

@ana @mcc FWIW the leading cause of the XMPP lock down (one of my “favourite” «why 2013 was the beginning of the end for the open Internet») was *allegedly* the partial Facebook Messenger XMPP support being used by FB to scrape the social graph of every Google Chat user. So Google was OK with federating while it was the only corpo juggernaut that could leverage said information, but closed the door when another corpo juggernaut tried to snoop in.

1/2

[oblomov@sociale.network]

So there's the possibility that BS will “play nice” while the only significant alternatives are initiatives like Blacksky and Northsky (sp?), but possibly not so much if, say, Meta tries to add AT Proto support to Threads, for example.

That being said, I agree with @ana's prediction. And hopefully in the mean time the Fediverse manages to fix its major technological pain points (like data portability), although I fear that might need taking down Mastodon leading position a notch or two.

2/2