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
    SolSoCoG (solsocog@ieji.de)'s status on Thursday, 27-Jul-2023 00:31:38 JST SolSoCoG SolSoCoG

    Don't trust big blocklists that uses a *council* that mostly consists of triggerhappy admins of small gated instances, some of which are plain lying and childish.

    #fediblock

    In conversation Thursday, 27-Jul-2023 00:31:38 JST from ieji.de permalink
    • Embed this notice
      SolSoCoG (solsocog@ieji.de)'s status on Thursday, 27-Jul-2023 15:19:02 JST SolSoCoG SolSoCoG
      in reply to
      • Hawkwinter

      @Hawkwinter that's a sensible thing to do! There's instances that start their journey by loading in the tier0 list, causing ieji.de to be limited for false reasons. Mastodon.art decided, for whatever deranged reason, to limit ieji with the reason transmisandry, this was actually just copied by other *council* members without validation, causing 2 instances in total of the blocklist limiting us, resulting in being part of the tier0 list. Can't take the #Oliphant #blocklist serious like that.

      In conversation Thursday, 27-Jul-2023 15:19:02 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: ieji.de
        ieji.de
        ieji.de is a generalistic mastodon instance, with the goal of being the fastest mastodon instance in Europe and with a focus on user privacy, like being usable via the tor network.
    • Embed this notice
      Hawkwinter (hawkwinter@mementomori.social)'s status on Thursday, 27-Jul-2023 15:19:04 JST Hawkwinter Hawkwinter
      in reply to

      @SolSoCoG
      I'm all for shared blocklists, but I do think they should be set up with transparency, and explanations for why each server should be blocked, with documentation.

      And when I checked the big shared list, I didn't see anything like that so I could be confident that each block was justified.

      Combing through #fediblock to see why I'm going to block each server I block and know the blocks are warranted - I'll at least know the blocks are warranted.

      In conversation Thursday, 27-Jul-2023 15:19:04 JST permalink
    • Embed this notice
      SolSoCoG (solsocog@ieji.de)'s status on Friday, 28-Jul-2023 01:05:04 JST SolSoCoG SolSoCoG
      in reply to
      • Hawkwinter

      @Hawkwinter yeah, the issue I see is that this instance has been blocked by the art admin for a fabricated claim, that's a big issue. Where one claim is fabricated, another one follows. The people at art sure are nice and they have quite a moderation team lineup. But what art people don't really notice is that they are cut off by, let's say 20% of the content they could see on a different instance. I mean sure, some of it can safely be cut off, but you get my point.

      In conversation Friday, 28-Jul-2023 01:05:04 JST permalink
    • Embed this notice
      Hawkwinter (hawkwinter@mementomori.social)'s status on Friday, 28-Jul-2023 01:05:05 JST Hawkwinter Hawkwinter
      in reply to

      @SolSoCoG

      As I mentioned though, I do think the idea of a shared blocklist is a good one. And I'm on .art and quite like the people there so far.

      But the implementation... I want to know I'm being reasonable, and that means I need to be able to skim through the entire block list and see the documentation for each block on that list.

      It's possible I would agree with every block on the list. But I would need to read the documentation to know.

      {I spent a good 40h researching instances and fedi-software before I made my first fediprofile. I'm just someone who wants to make sure I'm making the right decisions.}

      In conversation Friday, 28-Jul-2023 01:05:05 JST permalink

      Attachments


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.