Not That Kind of ‘Open’

Link to: https://fedipact.online/

Daring Fireball

@daringfireball Openness isn’t merely a protocol thing. It’s a delicate power balance.

When an entity larger than all other combined joins, it may become "too big to fail" and start dictating terms.

Gmail unilaterally dictates who can use SMTP. GitHub became the center of decentralised git. Systems tend to centralise.

@kornel @daringfireball Yes, and the way to fight with GMail isn’t to “block” gmail from other email services. That hurts the other email services, not Gmail.

Meta’s threads doesn’t *need* ActivityPub. It has Instagram’s far larger network. Blocking them from your mastodon instance only hurts you, not them. It resigns Mastodon to forever being that weird niche rather than part of the mainstream.

Integrate and use it to make yourself mainstream!

@nmn @kornel @daringfireball Meta needs AP because the whole point of it is busting the protocol after taking on Twitter and BlueSky.

@oblomov @kornel @daringfireball Let’s say that’s true. It’s plausible that Meta wants to do the whole “embrace, extend, extinguish” thing.

Defederating them early won’t fix anything. Meta has a huge user base. Threads doesn’t need AP to “bootstrap” content.

It will either steal users from Mastodon, or it won’t. De-federating will incentive more users to switch away from Mastodon. Integrating will let them stay because of the integration.

@oblomov @kornel @daringfireball On the other hand. Meta could bring a HUGE amount of awareness about AP and Mastodon and it could lead to a large number of people joining, if only to check things out.

Some users might even like the experience on Mastodon better. Ivory, Mona, Ice Cubes, Elk are all great apps which are likely much nicer to use than whatever Threads will be.

Integration will mean they’ll still be able to connect with their friends

@nmn @kornel @daringfireball that's the same rhetoric that was used to welcome Facebook and Google federating their instant messaging platforms with XMPP. And we know how that ended. Are you looking for the same thing happening to ActivityPub?

@oblomov @kornel @daringfireball Mobile killed xmpp not Google or Facebook.

If anything Gmail and Facebook kelp Xmpp alive a few extra years.

@nmn @oblomov @kornel @daringfireball I use xmpp on daily bases for chat and video calls. No issues on mobile. Google and Facebook defederating after stilling most of users is what pushed xmpp to back. Later even the rest of protocols that could be used with xmpp thru bridges. Both companies used xmpp and openness to bootstrap their user base.
@potato_lisper @oblomov @kornel @daringfireball My point was not about the technical feasibility of XMPP on mobile. My point was that the new set of mobile chat apps like WhatsApp and iMessage are what killed XMPP, not Gmail and Facebook. They were late to the mobile messaging party.

@nmn @potato_lisper @kornel @daringfireball

Is this some kind of joke? Google and Facebook (the company, aka Meta now) killed XMPP by refusing to adopt the extensions that would have allowed its usage on mobile while keeping the federation, and you think *that* didn't kill the protocol?

@nmn @potato_lisper @kornel @daringfireball

I mean, you literally just said «they didn't kill the protocol, they killed the protocol».