this post was submitted on 06 Jul 2023
337 points (97.2% liked)

Lemmy.ca's Main Community

2826 readers
1 users here now

Welcome to lemmy.ca's c/main!

Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.

Announcements can be found at https://lemmy.ca/c/meta

For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support

founded 4 years ago
MODERATORS
 

I've seen that some instances have already done it preemptively.

you are viewing a single comment's thread
view the rest of the comments
[–] jerkface@lemmy.ca 1 points 1 year ago (1 children)

In 2013, Google realised that most XMPP interactions were between Google Talk users anyway.

Isn't this what actually killed XMPP? XMPP still works, is still viable. But everyone stopped using it. That's got more to do with Facebook than Google, imho.

[–] leecalvin@lemmy.ca 3 points 1 year ago (1 children)

Yes. What they specifically did though was extend the protocol so that anyone who wasn't using their version of XMPP via Google Talk would be incompatible or seem "broken" when it really wasn't. It's just that they were using non-standard features, both incentivizing people to just switch to Google Talk and for development on the core protocol to slow down.

I bet money Threads is going to do the same thing. They'll introduce Threads only features that don't work with all the standard Activitypub implementations, causing frustration with Thread users and putting pressure on people to just jump ship to Threads from standard Activitypub implementations.

[–] jerkface@lemmy.ca 0 points 1 year ago

Okay, but again... so? That's just defederation. If that's the worst they can do to us.... So? That's also your proposed solution, so what!