Comment on Embrace, Extend, and Exploit: Meta's plan for ActivityPub, Mastodon and the fediverse

walter_wiggles@lemmy.nz ⁨9⁩ ⁨months⁩ ago

• originalucifer@moist.catsweat.com ⁨9⁩ ⁨months⁩ ago

  there isnt one, because even the 'extend' in this hyperbolic scenario isnt real

  o0o0o0 the big 'extend' is threads users will get to use the threads app. puhlease. thats no extension of AP

  everyones getting their sphincter tight over their own hate and nothing more.

  source

  • jol@discuss.tchncs.de ⁨9⁩ ⁨months⁩ ago

    The original sense of EEE’s extend was pushing features that were not standard (to IE). An example would be for example if Threads implemented a stickers function that only worked in the Threads apps but to us only appeared as sticker-id:123456. Any features built around AP that worsens the experience for others can be seen as “extend”.

    source

    • originalucifer@moist.catsweat.com ⁨9⁩ ⁨months⁩ ago

      if users on my system want some bell or whistle somewhere else, groovy, dont let the door hit ya on the way out.

      threads is not going to magically, silently create a dependency in my system. its exactly like SMTP. no one is attempting to EEE email.

      i am not/will not receive anything from threads not in the protocol spec, and if my users dont like that they can go somewhere else. this is not a problem for me.

      i dont care what the threads instance has to offer with regards to bells and whistles, it affects me not.

      source

      • jol@discuss.tchncs.de ⁨9⁩ ⁨months⁩ ago

        no one is attempting to EEE email.

        Yes… they are?

        Have you noticed how Gmail labels don’t work with other email providers? Folders and categories? Stars and Important? Many people have come to rely on these features and moving to other providers becomes a bit of a hassle. This is the naughty extension of e-mail.

        Another great example is github. Git is open and interoperable, but most companies using github are stuck to it because they use Github also for issues, pull requests, and many other things.

        source
• scrubbles@poptalk.scrubbles.tech ⁨9⁩ ⁨months⁩ ago

  You should really read the article…

  source

  • thenexusofprivacy@lemmy.world ⁨9⁩ ⁨months⁩ ago

    Indeed! But here’s the relevant excerpt

    Of course, if and when Meta sees the fediverse as a significant threat, they’ll ruthlessly stamp it out.0

    But right now, they’ve got a huge potential longer-term opportunity to coopt the fediverse as a basis for decentralized surveillance capitalism. It might not work out, of course, but keeping a neutered fediverse around might still be useful to Meta as long as it’s not a threat to their dominance (just as Google subsidizes the Firefox browser).

    And in the short term, there’s money to be made – and regulators to try to influence – by exploiting the fediverse.

    source