https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

Many of us do not trust Facebook and anything it is associated with or swallows up.

EDIT:

https://techcrunch.com/2023/07/05/adam-mosseri-says-metas-threads-app-wont-have-activitypub-support-at-launch/

"Instagram head Adam Mosseri said "

““Soon, you’ll be able to follow and interact with people on other fediverse platforms, such as Mastodon. They can also find people on Threads using full usernames, such as @mosseri@threads.net.””

“We’re committed to building support for ActivityPub, the protocol behind Mastodon, into this app. We weren’t able to finish it for launch given a number of complications that come along with a decentralized network, but it’s coming,” he said.

“If you’re wondering why this matters, here’s a reason: you may one day end up leaving Threads, or, hopefully not, end up de-platformed. If that ever happens, you should be able to take your audience with you to another server. Being open can enable that.”

  • pjhenry1216@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Yeah, you can filter your feed. No one is arguing that. But you can’t filter the feed to someone else. That’s not how it works. I also don’t understand why you have to keep throwing around your supposed credentials when you haven’t been able to understand a simple web api concept. If you want Threads not to see you, they need to defederate your server. You don’t honestly think this server is posting to information to every other server individually, do you? Those servers grab information and that information is the same for every server that grabs it. It does not publish individual feeds to individual servers. That’s ludicrous when you consider the minimum specs for a server.

    Your credentials don’t mean much when you can’t provide any hint of skill to make it mean much.

    • Arotrios@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Sigh. You people are fucking exhausting. #5 of saying “you can’t do that” and giving nothing more than “server can’t handle it” as a reason, which is why I stated my credentials, because I’m sick of people talking out of their asses.

      When the instance that wants to publish your work makes a call to the api, they have a domain referrer value. Being able to filter on that value is already in place through the process of defederation.

      Filtering the output on that domain referrer value is neither some complex process, nor will it increase server load as you’re reducing the amount of content the API is producing.

      How do you think IP filtering works? Every public facing web service does it. This is the exactly the same thing, except that rather than blocking the entire site, you’re blocking a small part of it. It’s even easier than blocking a specific page to an IP, because you only have to block a subset of data coming out of the feed on the api.

    • Arotrios@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      FFS. Filter by domain referrer when the call is made to the API from the instance that wants to publish your work. It’s not that fucking hard. How do you think IP filtering works?