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
    HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Friday, 16-Feb-2024 05:09:14 JST HistoPol (#HP) 🏴 🇺🇸  🏴 HistoPol (#HP) 🏴 🇺🇸 🏴
    • Scott M. Stolz

    @scott

    Thanks a lot, Scott.

    I am aware of several of these things. A friend of mine, https://stefanbohacek.online/@stefan, created https://jointhefediverse.net to remedy this lack of undesirable for newbies and no-nerds.

    I know what #whitelisting is general, but how would I go about this on #Mastodon?

    The whitelist, if I don't want to do everything manually (no-go,) would need to be "intelligent" and able to discern the platform s.o. is using for his handle...

    I can live with the screenshot issue.

    In conversation about a year ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: stefanbohacek.online
      Stefan Bohacek (@stefan@stefanbohacek.online)
      1.44K Posts, 296 Following, 1.01K Followers · Husband, father, creator of: 👋 https://jointhefediverse.net 🗺️ https://fediverse-explorer.stefanbohacek.dev 🐘 https://mastodon-tools.stefanbohacek.dev 🎨 https://generative-placeholders.glitch.me 🤖 https://botwiki.org 🤖 https://stefans-creative-bots.glitch.me 🏴 https://fightfascism.glitch.me And more: https://stefanbohacek.com/projects I also volunteer with https://techforcampaigns.org and https://tech.dsausa.org. He/him. 🗺️ Brooklyn, NY; prev. Bratislava
    2. No result found on File_thumbnail lookup.
      Join the fediverse!
      Learn about the fediverse and find your community.
    • AP-AT-Bridge Group repeated this.
    • Embed this notice
      HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Friday, 16-Feb-2024 05:48:20 JST HistoPol (#HP) 🏴 🇺🇸  🏴 HistoPol (#HP) 🏴 🇺🇸 🏴
      in reply to
      • Scott M. Stolz

      @scott
      Thanks.
      I can answer this one, as someone put quite a bit of work into this, here's how to #MassBlock :

      https://mastodon.social/@HistoPol/110661216855577004

      The list, however, contains only #Meta sites, and would not include the "....would be more concerned about..." issue.

      In conversation about a year ago permalink
    • Embed this notice
      Scott M. Stolz (scott@authorship.studio)'s status on Friday, 16-Feb-2024 05:48:23 JST Scott M. Stolz Scott M. Stolz
      in reply to
      @HistoPol
      I know what #whitelisting is general, but how would I go about this on #Mastodon?

      The whitelist, if I don't want to do everything manually (no-go,) would need to be "intelligent" and able to discern the platform s.o. is using for his handle...
      I don't use Mastodon, so I don't know for sure. Some people have mentioned that there is a whitelist mode that is called "limited federation mode" or something like that. The admin would have to turn that on since it is for the whole instance.

      If you don't want to use whitelist mode, people have been talking about blocklists that can be imported into Mastodon. I am not familiar with how they work. Maybe someone who uses Mastodon could answer this one?
      In conversation about a year ago permalink
      AP-AT-Bridge Group repeated this.
    • Embed this notice
      Qazm (qazm@tiggi.es)'s status on Friday, 16-Feb-2024 08:41:46 JST Qazm Qazm
      in reply to
      • Scott M. Stolz

      @scott In short, it's just like blocking one-by-one but as batch-action. Admins can also block domains using wildcards, I think.

      However, either would not work to block specific software. You would indeed have to use an instance in limited federation mode, where each connection is checked one-by-one, to avoid federating with Friendica and Hubzilla instances that could copy your posts over to other protocols.

      In conversation about a year ago permalink
      AP-AT-Bridge Group repeated this.
    • Embed this notice
      Scott M. Stolz (scott@authorship.studio)'s status on Friday, 16-Feb-2024 08:41:49 JST Scott M. Stolz Scott M. Stolz
      in reply to
      • Qazm
      @Qazm There are other options, like using a platform that has privacy, access lists, permissions, and better moderation tools. Mastodon only has block lists, which limits user's control over their own posts.

      For example, on Mastodon you can block someone so you can't see their posts, but you can't stop them from replying to posts they have already seen. On Hubzilla, you can actually turn off commenting on your posts so no one can reply or so that specific people can't reply, and can even delete other people's replies to your thread. You control the conversation in your thread. You can't do that on platforms like Mastodon.

      Also, on Hubzilla, it is all about user choice. So if Hubzilla implements the Bluesky protocol, both the admin AND the user would have to opt-in. Users would have to actively turn on the Bluesky addon to federate with Bluesky. Otherwise none of their posts will ever be sent to Bluesky. I am pretty sure Friendica will work the same way.

      So Hubzilla and Friendica would actually do a better job at blocking Bluesky than the bridge does. And the bridge actually has a lot of options for blocking Bluesky.

      So instead of blocking Hubzilla and Friendica, you probably want to start using it instead, since it gives you better protection against Threads and Bluesky than Mastodon does.
      In conversation about a year ago permalink
      AP-AT-Bridge Group repeated this.
    • Embed this notice
      Qazm (qazm@tiggi.es)'s status on Friday, 16-Feb-2024 19:02:17 JST Qazm Qazm
      in reply to

      @scott I don't think so. Other Hubzilla or Friendica instances that receive a Hubzilla post over AP can still boost it over there, right?

      The reply control from your instance won't stop Mastodon users from replying either (though it will stop you seeing those replies, and to some extent will reduce the visibility of replies).

      I think it all comes down to what's outlined in https://foggyminds.com/display/c6ef095f-1165-ce77-d6de-73f618365846 (saw that post a little after my reply above) and open federated social media in general being built around own-access-choices rather than data control, outside of posting modes with very limited reach which *should* be implemented with more privacy than they are.

      In conversation about a year ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: snarfed.org
        snarfed.org
        from Ryan Barrett
        Fediverse! I’ve been building a bridge to Bluesky, and they’re turning on federation soon, which means my bridge will be available soon too. You’ll be able to follow people on Blu…
      AP-AT-Bridge Group repeated this.
    • Embed this notice
      Scott M. Stolz (scott@authorship.studio)'s status on Friday, 16-Feb-2024 19:02:33 JST Scott M. Stolz Scott M. Stolz
      in reply to
      • Qazm
      @Qazm That was sort of my point. If you want to have more control over who can see and respond to your posts, you probably should stop using Mastodon and switch to a platform that supports privacy, access control, permissions, and moderation.
      In conversation about a year ago permalink

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.