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.

Comments on Grace period for immediately noticed small errors

Parent

Grace period for immediately noticed small errors

+3
−2

Sometimes I will compose a lengthy post, submit it, see it in context and immediately notice a typo - no matter how careful I thought I was being.

I'm not sure it's desirable that, when I go to fix it immediately, the revision is recorded in the post's history. I could of course use the Redact feature, but that seems abusive.

An immediate edit like this Somewhere Else would not be recorded separately; there is a grace period of, IIRC, five minutes before an edit is recognized as actually revising the post.

Would it be desirable to follow that example here? Or do we see a benefit in preserving the original version and typo-fix separately?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Visibility to mods (1 comment)
Post
+5
−0

If we allow immediate updates to be "folded into" the original post, I would want to block it if anybody has interacted with the post -- if someone voted in that first minute, then an unannounced edit shouldn't be ok. Yes this is rare, but sometimes you get these quirks of timing. (It's happened to me.) And as someone noted in a comment, we would want moderators and admins to be able to see the true history, just in case it matters. When we start adding these guardrails, I wonder if we're making the code complicated and the interface confusing -- why did this edit get recorded separately but not that one?

(Thank you for not using redaction for this. Redaction is meant for things like credentials and PII. We have a change pending to add some extra guidance next to that checkbox.)

I know from personal experience how annoying it is for a typo or brain glitch to get through. It feels embarrassing. I console myself with the thought that most people probably won't even look, and for those who do, the favor of fixing it outweighs the shame of making the error in the first place. Maybe that's not always true, but it's the mindset I try to adopt.

Would it help to keep the true history (like now) but fuzz the "announcement"? Instead of "posted 5 min ago, edited 4 min ago", if we just show "posted 5 min ago" but show the edit in the history -- would that help? Or would that be confusing too? (We'd need to flesh out how that would work and what the thresholds are.)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Thoughts on the Redact feature (2 comments)
Thoughts on the Redact feature
Karl Knechtel‭ wrote about 1 year ago

I'm inclined to agree, but since I noticed the difference I felt it would be worthwhile to ask.

As regards redaction, I anticipate that people will abuse it regardless, and in the future moderators will not have the resources to police that sort of thing. It may become necessary to restrict that privilege or something. Or maybe redaction would only consider up to a certain number of recent edits... ?

Monica Cellio‭ wrote about 1 year ago

We have some pending changes to help with redaction, including rollback. There's also a proposal (I don't recall where this stands) to raise an auto-flag for redactions. If those aren't enough, we can add more restrictions. On the one hand we want to get things like API keys off of the public site as quickly as possible, no matter who first notices it; on the other hand, we have to guard against abuse.