Timeline for Stop killing suggested edits in the name of "conflicted with a subsequent edit"
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 31, 2019 at 4:56 | comment | added | user243267 | @Chris and knzhou, I didn't know that. If already a system like that is in place, then I am happy!! My edit conflict is just a rare case. But if in other cases there is such a system in place, then there is no need for any other mechanism. Thanks for informing me about this :) | |
| Dec 31, 2019 at 2:36 | comment | added | David Z Mod | @Chris Last I heard, the SE team monitors both per-site metas as well as the mother meta site for feature requests... or at least they try, although the volume is probably too high for them to keep up with in general. | |
| Dec 31, 2019 at 0:27 | comment | added | Chris Mod | @FakeMod That already happens in most cases, though. It's only when both the high- and low- rep users are editing at about the same time this can happen. And regardless, any request for a new mechanism should go on the mother meta if you actually want any developers to see it. | |
| Dec 31, 2019 at 0:26 | comment | added | Chris Mod | @knzhou That's not true. Ben submitted their edit 6 seconds after FakeMod submitted theirs. (The timestamps are 2019-12-29 18:42:27Z and 2019-12-29 18:42:33Z) | |
| Dec 30, 2019 at 22:35 | comment | added | knzhou | Since we haven’t invented time travel, there’s no reasonable way to stop a high rep user from editing on the grounds that a low rep user might submit a conflicting edit later. If you really applied that role consistently, no edits would ever happen. | |
| Dec 30, 2019 at 22:34 | comment | added | knzhou | @FakeMod That already happens. The problem here is that Ben finished his edit before you even submitted yours. | |
| Dec 30, 2019 at 12:30 | comment | added | user243267 | Also, can we put some kind of mechanism such that a high rep user who wants to edit a question will have to first review the pending suggested edit of that question. He can then either accept, reject or edit the suggested edit. This way he will able to get his edit done and the suggester will also get his edit reviewed. But yeah there might be cases where a suggested edit wouldn't have been reviewed even once. In those cases, this system would only work if the approval of a single person would allow the suggested edit to be done. | |
| Dec 30, 2019 at 6:16 | comment | added | Chris Mod | @FakeMod Most of the time, that will leave it just looking like you are reverting a bunch of good edits and making some other ones, and would rightly be rejected. In any case, that doesn't preserve both edits- you still end up picking one and discarding the other. | |
| Dec 30, 2019 at 4:58 | comment | added | user243267 | Well I don't think combining edits will work. Rather I think that when you review the edit, the system should show you the latest/present form of the question instead of the original unedited one. This way, both the edits can be safely preserved. Is this kind of thing possible? | |
| Dec 30, 2019 at 4:55 | vote | accept | CommunityBot | ||
| Dec 29, 2019 at 22:57 | history | answered | ChrisMod | CC BY-SA 4.0 |