cross-posted from: https://lemmy.world/post/5007912
Kbin.social and one lemmy instance with queer furries (yiffit.net) were mentioned in the article.
cross-posted from: https://lemmy.world/post/5007912
Kbin.social and one lemmy instance with queer furries (yiffit.net) were mentioned in the article.
deleted by creator
I think you just need to stay federated?
deleted by creator
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.
deleted by creator
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.
deleted by creator
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.
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.
No. It’s not an automated whitelist, it’s an automated blacklist (for some). If you want to avoid getting blocked, nothing has changed - don’t spam, don’t post illegal stuff. And if your instance starts spamming, be responsive in resolving the problem.
Fediseer doesn’t change any of that, it just provides an easy way to mark instances as not good.
You need to “beg” (which in reality is just “ask”) only if you want to become an active member of Fediseer.
deleted by creator
I already replied there, but here’s some more info: there are instances which have a whitelist-only approach, but those are only few. I think those could probably use Fediseer the way you’re describing. But most instances want to federate with as many instances as possible, so switching to whitelist-only doesn’t make sense for them.
Anyway, I’ve guaranteed for you on Fediseer if you want to participate.