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 »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

60%
+1 −0
Q&A Submit same flag multiple times

When you submit a flag we don't refresh the page, and so when you flag again the flag modal doesn't "know" about your previous flag yet. After a refresh, you'll get the "you've previously flagged ...

posted 10mo ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2024-03-10T18:50:35Z (10 months ago)
When you submit a flag we don't refresh the page, and so when you flag again the flag modal doesn't "know" about your previous flag yet.  After a refresh, you'll get the "you've previously flagged this as..." notice.

While duplicate flags are a little noisy, this can only happen if you flag twice before reloading the page, so it's pretty rare.  I don't think we want to force a refresh after flagging, and it _can_ be legitimate to flag the same thing twice (for example to also flag something about the user), so I'm inclined to leave this as-is unless it becomes a problem.  Yes there's an abuse vector, but for that case, rate-limiting might be a better solution.