This blog post by Ploum, who was part of the original XMPP efforts long ago, describes how Google killed one great federated service, which shows why the Fediverse must not give Meta the chance

  • Qazwsxedcrfv000@lemmy.unknownsys.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Basically the sequence of events as claimed by the author is that:

    1. XMPP, niche, small circles
    2. Google launches Talk that was XMPP compatible
    3. Millions joined Talk that could coop XMPP in theory
    4. The coop worked only sparingly and was unidirectional, i.e. Talk to XMPP ✅ but XMPP to Talk ❌
    5. Talk sucked up existing XMPP users as it was obviously a better option (bandwagon effect + unidirectional “compatibility” with XMPP)
    6. Talk defederated

    This demonstrated exactly the importance of reciprocity. If they play dirty, kick them out asap.

  • sanzky@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    The X in Xmpp is for extensible. I find issue that a protocol that is supposed to be extensible was killed by being extended.

  • wet_lettuce@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I’m gonna throw this out there:

    If Meta is going to join the fediverse (or implement something with activitypub) there is absolutely nothing we can do to stop them.

    It’s an open protocol. They can use it.

    The only thing we can do is force them to follow the AGPL and/or fork the code if they get crazy with change requests.