Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Bad spam filtering

Parent

Bad spam filtering

+5
−0

A spammer was able to post the very same spam 3 times within 15 minutes - all identical posts with exactly the same title and the same user. It seems very trivial to completely flood the site with trash this way.

This shouldn't be possible to do for any user, spammer or not. Why even allow duplicate titles on the site?

History

0 comment threads

Post
+3
−0

In addition to simple rate limits, what if we could require some form of vetting after a user's first post? For example, first posts from new users go into a queue, so curators and moderators have attention drawn to them. Then if the first interaction with the post from a curator or moderator is not to mark it as spam, the user then gets to continue posting (up to the usual rate limit).

History

2 comment threads

No queues please! (4 comments)
Maybe linked to flags? (3 comments)
Maybe linked to flags?
trichoplax‭ wrote about 1 month ago · edited about 1 month ago

I like the idea of a 1 post limit if the first post is spam, but a queue could force a useful new contributor to wait until a moderator or curator is next online. Also, a flood of new users would mean all of them are limited to 1 post until they reach the front of the queue.

What if we use all the users rather than just moderators and curators? Instead of a queue, just prevent a user from posting if they have an open spam flag. Possibly only counting flags from users who registered before the flagged user, to avoid spammers using this in reverse to block others from posting?

At a quiet time a spammer might still be able to post their daily limit in quick succession. I'm not sure how to avoid that without a queue. Maybe a compromise could be to limit to 1 post per hour for the first post?

Karl Knechtel‭ wrote about 1 month ago

The problem with "more aggressive limit only if the first post is spam" is that spammers are the ones most likely to try multiple posts in quick succession, before the first one can be flagged.

Michael‭ wrote about 1 month ago

While Karl is correct, I think Lundin must have gotten a flag in before the spammer finished their bombing run.

I like Trich's idea, but we should weigh the possibility of a malicious existing user DOSing someone else. Maybe our old friend Wilson Score is a part of this?