The Good Space
thegoodspace.neocities.org
    • cwagner@lemmy.cwagner.meEnglish
      81·
      10 months ago

      But from the FAQ and everything, it makes it seem like the ultimate goal is to have an automated whitelist. So I’d need to somehow get a big, or many small, instance to vouch for mine. Again, as far as I understand it.

      I only have 2 instances blocked (lemmygrad and hexbear) as I don’t have to worry about anyone subscribing to e.g. porn instances with questionable content as I’m the only user.

      • gabe [he/him]@literature.cafeEnglish
        3·
        10 months ago

        The goal isn’t to make things a fully automated whitelist, it’s more so a list of instances that cause issues or are suspected as spam that would be blocked. Even then, instances see the info and are given the opportunity to do what they want with the info as they see fit.

        It really takes a lot to get fediblocked as a small user instance.

        • cwagner@lemmy.cwagner.meEnglish
          4·
          10 months ago

          From the announcement

          My thoughts then was to find a way utilize the “whitelisting” capabilities of lemmy and the fediverse to ensure that only trusted instances are federated. But this has it’s own share of problems. Particularly, it’s also difficult to scale, and it easily excludes people running their own instances.

          However the main benefit of whitelists, is that one does not have to be constantly vigilant. A dedicated bot network can spawn thousands of new domains and sleeper accounts to flood the fediverse and de-federation lists would easily grow exponentially to try and fruitlessly fight against this. A whitelist should theoretically remain relatively short and there’s natively protects against domain flooding.

          So I wanted to come up with something that would both make it easy to compile and maintain whitelists, but also not lock out people from individual accounts.

          That’s talking about a whitelist, which was the part that initially confused (as I don’t see how the issues from the first paragraph are solved this way) and scared me.

          • Rikudou_Sage@lemmings.worldEnglish
            5·
            10 months ago

            Well, Fediseer certainly can do that. But how you use it is really up to you and I don’t know of anyone who uses it as a whitelist currently. I personally have it set up in a way where I have my own blocked instances and I subscribe to lemmy.world and lemmy.dbzer0.com for instances with loli and csam.

            • cwagner@lemmy.cwagner.meEnglish
              6·
              10 months ago

              Okay, so it’s more an idea and a possibility, but not something expected to happen? That’s good to hear, my anxiety mainly came from that post ;) Oh, and thanks for vouching for my instance <3

              • gabe [he/him]@literature.cafeEnglish
                2·
                10 months ago

                As I said above, it’s unlikely many instances will fully automate those who don’t use it out. I make sure people are mindful of the way tools affect smaller or single user instances as well when development occurs. The goal of the tool overall is to do something that isnt a whitelist so we don’t single out small instances but rather a crowdsourced tool providing info on stuff that we want.

          • gabe [he/him]@literature.cafeEnglish
            3·
            10 months ago

            I fully understand your anxiety on the matter, and this is a critique I have actually had directly with the software. I did get into it a bit with db0 (sorry man!) over it, and thankfully my critiques were listened to and the reasoning behind the software itselfs overall use was clarified.

            The goal isn’t a glorified whitelist, but rather a crowdsourced tool that people can use what they want with it. You can automate the blocks if you want, you can make it so that there’s warnings when blocks are made, you can impliment a whitelist if you want, it’s really on people who use it. The only somewhat automated aspect of it that’s by default is the identification of instances with spam like behavior, and there is steps to rectify that if they are identified as such so it’s not like a permanent mark of shame.

            I participate in these conversations of fediseers tooling and development with single user/small instances in mind, so know that as tools are being made I am making sure others are mindful of how it may affect small single user instances/new niche communities. I will continue entering those conversations with those communities in mind as well. I gotchu.