GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    ophiocephalic 🐍 (ophiocephalic@kolektiva.social)'s status on Wednesday, 20-Dec-2023 01:11:40 JST ophiocephalic 🐍 ophiocephalic 🐍

    Did you know that, if you or your Mastodon instance is blocking Meta, your posts and account can still be data-mined by them? That is, unless your instance has Authorized Fetch activated. More info here: https://kolektiva.social/@ophiocephalic/111602259275182233

    #FediPact #DefederateMeta #Meta #Facebook #Threads #Instagram #AuthorizedFetch

    In conversation Wednesday, 20-Dec-2023 01:11:40 JST from kolektiva.social permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      ophiocephalic 🐍 (@ophiocephalic@kolektiva.social)
      from ophiocephalic 🐍
      With the Zuckerberg takeover impending, there's a lot of confusion circulating about the use of user-level and instance-level blocks, and how our online expressions can be secured against Meta. Everyone who objects to their accounts being mined by the Zuckerberg entity for data collection, AI ingestion, monetization, and possible ghost-profile building needs to understand this problem. Here's information to clarify. Neither a user-level block, or an instance-level block, will protect our posts from Meta data-mining by default on a Mastodon instance. Posts won't be delivered directly, but can be ingested by other means; if, for example, users on Meta-federated instances boost them. However, both user and instance blocks will totally prevent post delivery in all cases IF your host instance has enabled the functionality called Authorized Fetch. By default, Authorized Fetch is off on Mastodon instances and most haven't turned it on. If this concern is important to you, you might want to respectfully reach out to your admins and let them know. Remember that they are working hard to provide and sustain online community at no charge. It's likely they won't be very familiar with it and will need time to look into it. For more information on Authorized Fetch, check out this blog post by @brook@sunny.garden : https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/ Please untag Brook from replies unless you specifically intend to address him #FediPact #DefederateMeta #Meta #Facebook #Threads #Instagram #AuthorizedFetch
    • Tokyo Outsider (337ppm) repeated this.
    • Embed this notice
      ophiocephalic 🐍 (ophiocephalic@kolektiva.social)'s status on Wednesday, 20-Dec-2023 01:11:40 JST ophiocephalic 🐍 ophiocephalic 🐍
      in reply to
      • Tokyo Outsider (337ppm)
      • The Nexus of Privacy

      Authorized Fetch will help keep our accounts safe from Meta data-mining. Participate in polls on the Authorized Fetch issue here:

      by @tokyo_0: https://mas.to/@tokyo_0/111607524638174586

      by @thenexusofprivacy: https://infosec.exchange/@thenexusofprivacy/111602607824043839

      #FediPact #DefederateMeta #Meta #Facebook #Threads #Instagram #AuthorizedFetch

      In conversation Wednesday, 20-Dec-2023 01:11:40 JST permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Tokyo Outsider (337ppm) (@tokyo_0@mas.to)
        from Tokyo Outsider (337ppm)
        ❓ Did you know? Unless your instance has the "authorized_fetch" option turned on, blocking another instance as an individual user only mutes posts from that instance—and doesn't stop your publicly visible posts from being retrieved, cached and displayed on that instance. Authorized_fetch checks which instance wants to load your data before handing it over. Would you like your instance to enable #authorized_fetch? #ActivityPub #facebook #fedipact #mastoAdmin #mastodon #meta #threads #security [ ] yes, please turn on authorized_fetch [ ] no, my posts can appear on instances I blocked
      2. No result found on File_thumbnail lookup.
        The Nexus of Privacy (@thenexusofprivacy@infosec.exchange)
        from The Nexus of Privacy
        A poll: if you're planning on blocking Threads , do you want your posts to federate there so that hate groups can interact with them and Meta can track you? The way blocking works on Mastodon, if your instance hasn't enabled "authorized fetch", [blocking Threads won't actually prevent your posts from federating there](https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/) if somebody on another instance who hasn't blocked Threads boosts your post. This means that anybody on Threads can still potentially see your posts, including hate groups like Libs of TikTok and Gays Against Groomers. And Meta's privacy policy says they'll use the information to target advertising and improve their products by training AIs. And most large Mastodon instances today haven't turned on authorized fetch. If you're planning on -- or considering -- blocking Threads, do you still want your posts to federate there? #meta #threads #fedipact #fedimeta @fediverse@lemmy.world @fediversenews@venera.social [ ] No. Blocking means blocking [ ] Yes. That's how things should work! [ ] I don't care either way [ ] I'm not even considering blocking Threads, so it doesn't apply to me [ ] Not sure

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.