999
Dear server admins, please defederate threads.net. Dear users, ask your server admin to defederate threads.net. (mstdn.social)
submitted 2 years ago by to c/fediverse@lemmy.world
827 comments fedilink hide all child comments
 

Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.

If you're a server admin, please defederate Meta's domain "threads.net"

If you don't run your own server, please ask your server admin to defederate "threads.net".

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 2 years ago (5 children)

I just don’t think it’s possible for something to kill the fediverse. And if it is possible, then it is a flaw in the design of the fediverse and needs to be fixed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 24 points 2 years ago (1 child)

    Are you planning to pay for the extra bandwith to deal with all the additional traffic?

    Meta will.

    And then when they own the servers amd all the traffic, lemmy will be quietly murdered.

    Quietly, because they'll control the traffic, and therefore the narrative

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 12 points 2 years ago* (last edited 2 years ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 2 years ago (1 child)

    Today no.

    Come make your instance on Meta(tm) it's free(tm)!! Its fast! It's yours!!

    Then later they'll wreck havoc on our small servers making them slow and unreliable, making their servers even more interesting for people. And so on.

    And that's just one way among lots of ways.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -13 points 2 years ago (1 child)

    I love that your fear is they will be successful and the lemmy devs and admins don't have their shit together or a plan to handle anything but a small niche headcount.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (2 children)

    All activity pub needed to do was create a user rights guidelines that prevents profiting off the data. Meta wouldn't have touched the Fediverse with the 10-foot pole, if that were the case.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    ActivityPub is a protocol, not a fucking organization. It literally has no agency.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    You can licence a protocol

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 2 years ago (1 child)

    ActivityPub can't license anything. When you identify actual human beings in this conversation, perhaps you might have a point. So far you don't.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (1 child)

    First off, calm the hell down. You're being needlessly antagonistic.

    Secondly, it seems like the W3C is the publisher of the activity pub standard seems like they ducats what is an isnt compliant.

    Seems like of was specifically authored by a team including Evan Prodromou according to the wiki.

    If they wanted too, but like literally and open source software, it could have been given licencing requirements

    Specifically, my research has turned up that implementations of these protocols can be licensed. Threads' version of ActivityPub likely has its own licence. I think it would be safe to say that the creators of Lemmy and Mastodon specifically could have privacy rights dictated within their license implementation. That would nullify threads legal capabilities.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago

    People have been writing about this ad nauseum. It's the embrace, extend, extinguish strategy. Join fediverse, extend the spec with so that not all clients are compatible with all features, repeat as necessary until everyone is using your client, finally drop compatibility with other clients.

  • permalink
  • fedilink
  • source
  • parent