128
Introducing The Lemmy Overseer
(overseer.dbzer0.com)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
Maybe I'm being stupid, but how does this service actually determine suspicious-ness of instances?
If I self-host an instance, what are my chances of getting listed on here and then unilaterally blocked simply because I have a low active user count or something?
It's based on dynamic count. For now it's a very simple how many users per post there are and each instance can set their own threshold for it.
It's not about few users, it's about a tons of users and no activity. If you have 5000 users and 3 posts, it's likely those are all spam accounts. This is what we're checking for right now.
This is not a manual process currently, but I'm planning to add the possibility to whitelist and blacklist instances manually in the future.
Isn't it trivial for bot farms to just spam posts on their home instance? And how does this handle cases where the number of posts is zero?
Ideally the list of behaviors which trigger suspicion would be expanded over time, yes? Low hanging for first, just because it's easy doesn't mean spammers will program around it unless we check for it.