Grace period for updating comments
I don't know about anyone else, but I'll post a comment, re-read it, post it and then realize what I'd missed. So within seconds of posting my comment I edit it to add or modify what I finally realized I wanted to say and it shows that the comment was updated. It's a minor quirk, but I'd like it to not show that the comment was modified for last-minute changes. Would it be acceptable to allow a short grace period before it starts tracking changes to comments?
8 years ago by spaceghoti
with
16 comments
Join the Discussion
This is something we have considered doing in the past but we left it as is due to an edit being an edit. However, I feel that if enough people agree with this change, we can make it happen.
I'll accept whatever consensus decides. It's a personal quirk, and not critical.
I must say, I quite like the idea, as long as the window is short (say 5 mins), and perhaps the grace period ends as soon as a response is posted (within the window period). So any comment younger than 5 mins, with no responses, is eligible.
Edit: maybe the grace period also ends as soon as there is an up/down vote.
I agree that an edit should be an edit. Even if it takes you 10 seconds to update, someone may have replied to you - their version of your comment doesn't refresh when you change it, unless you want to implement some crazy ajax shit (which would be amazing btw!). A lack of information pertaining to why there might be confusion in a replying commenter's response is worse than the status quo.
I'd be all for it. It's a feature that's on most old school message board software. There's typically an edit window of five minutes or so before that edit tag shows up.
Is it possible to have the grace period be "until someone responds"? Or perhaps the shorter of "until someone responds" or X time?
I'm all for this if you have the time! I frequently notice dumb typos and grammatical errors right after I post, and it's mildly annoying, damn it! ;)
I do the same thing, and yes it is. What's really embarrassing is to miss something and discover it the next day, or another reader notices it and lets me know. Lucky for me,the forums I'm on,the people know me and find my mistakes amusing.
Actually I find that the "preview" feature helps with this issue. I'm getting into the habit of previewing every comment before it's posted, it forces me to re-read it and see If I missed something.
Yeah, I preview as well. And still I find there's something I missed or it strikes me how to say something better right after I've said it. So I end up doing a quick edit to make that final correction that didn't occur to me just before I hit "post."
Maybe a forced preview with a forced 10 second cooldown before being able to confirm would be a good idea?
Im against. Its a good feature, but there are probably better ways to improve snapzu rigth now. ¿Where is the backlog so we can rank them by priority?
With a software project like this, I think it's important for all available bugs and change requests to be raised, no matter how small. Capturing as many as possible, even 'nice-to-haves', actually improves the prioritization process by giving a more realistic backlog. There will always be certain 'quick wins' that can be thrown in without detriment to larger changes and add real value to a given update. It might be a nice idea to have a 'virtual' backlog for user prioritization, to be used as a feedback tool but, relistically, there will be a number of determining factors that the user base just won't be privy to.
That said, I really don't intend to slam your comment, just thinking out loud. :)
Ninja edit: typo. Hope no one noticed! ;)
Well put.
I think we agree. Its a good feature, I just want to see how it stacks in a backlog.
Then let's agree to agree! ;)