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)
No queues please!
Lundin‭ wrote about 1 month ago

Review queues have been nothing but one big fiasco at SO. They are very difficult to get right and SO was never close to getting them working as intended. Then they tried to fix queues by adding more queues...

Karl Knechtel‭ wrote about 1 month ago

I agree that queues have generally been problematic, but in order for a system like this to be effective it has to hold the user back until an action is taken (a whitelist rather than blacklist approach), which in turn suggests prioritizing the opportunity for that action to be taken.

There are probably tweaks that could be made to address that; this is just a first cut at the idea.

Lundin‭ wrote about 1 month ago · edited about 1 month ago

In the past it was suggested that newer users would get a maximum question posting frequency. Perhaps that's a better fix? That's when we had lots of problems with certain users posting a whole lot of legitimate but low-quality questions, so that the whole front page of some sites was filled with down-voted bad questions with no answers. And that scares away other new users.

Karl Knechtel‭ wrote about 1 month ago

Well, I would also say that it's better if improvable questions can be improved (and the OP petitioned for improvements, where applicable) before exposure to up/down votes, but.

In principle we already support the suggestion, to my understanding: there are separate "Participate" and "Participate Everywhere" levels, which could have separate rate limits.