Protect. Moderate. Purge. Your. Sever.

3 years ago by alert to c/lemmy

Please. Captcha by default. Email domain filters. Auto-block federation from servers that don't respect. By default. Urgent.

meme not so funny

And yes, to refute some comments, this publication is being upvoted by bots. A single computer was needed, not "thousands of dollars" spent.

load all comments

jollyroger 63 points 3 years ago

The admin https://lemmy.dbzer0.com/u/db0 from the lemmy.dbzer0.com instance possibly made a solution that uses a chain of trust system between instances to whitelist each other and build larger whitelists to contain the spam/bot problem. Instead of constantly blacklisting. For admins and mods maybe take a look at their blog post explaining it in more detail. https://dbzer0.com/...

save

path: 0 465184, hotness: undefined, score: 63, children: 23

mlaga97 15 points 3 years ago

Obviously biased, but I'm really concerned this will lead to it becoming infeasible to self-host with working federation and result in further centralization of the network.

Mastodon has a ton more users and I'm not aware of that having to resort to IRC-style federation whitelists.

I'm wondering if this is just another instance of kbin/lemmy moderation tools being insufficient for the task and if that needs to be fixed before considering breaking federation for small/individual instances.

save

path: 0 465184 474996, hotness: undefined, score: 15, children: 4

Raiden11X 6 points 3 years ago

He explained it already. It looks for a ratio of number of users to posts. If your "small" instance has 5000 users and 2 posts, it would probably assume a lot of those users would be spam bots. If your instance has 2 users and 3 posts, it would assume your users are real. There's a ratio, and the admin of each server that utilizes it can control the level at which it assumes a server is overrun by spam accounts.

save

path: 0 465184 474996 482931, hotness: undefined, score: 6, children: 3

Irisos 2 points 3 years ago

The issue is that it could still be abused against small instances.

For example, I had a bit less than 10 bots trying to signup to my instance today (I had registration with approval on) and those account are reported as instance users even though I refused their registration. Because of this my comment/post ratio per user got a big hit with me being unable to do anything (other than delete those accounts directly from the db).

So even if you don't allow spam accounts to get into your instance, you can easily get blacklisted from that list because creating a few dozen thousands account registration requests isn't that hard even against an instance protected by captcha.

save

path: 0 465184 474996 482931 484362, hotness: undefined, score: 2, children: 1

eekrano 2 points 3 years ago

Comment / post ratio is useless as well for this though.

Create a server
Create 10,000 bot accounts
Have 85% of bot accounts create a random post
Have 40% of post a comment on the main level posts

Looks like I pretty busy, totally real server by the aforementioned metric

save

path: 0 465184 474996 482931 484362 493883, hotness: undefined, score: 2, children: 0