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 closure-as-duplicate post notice is inaccurate

Maybe what we need here is some way to close a question as "superseded by" another question; not really a duplicate per se, but something that works similarly from a technical and user perspective,...

posted 4y ago by Canina‭  ·  edited 4y ago by msh210‭

Answer
#3: Post edited by user avatar msh210‭ · 2020-08-24T13:12:44Z (about 4 years ago)
  • Maybe what we need here is some way to close a question as "superceded by" another question; not really a *duplicate* per se, but something that works similarly from a technical and user perspective, with different display strings in the UI and a different implied direction of causality.
  • That would allow handling precisely this case, and quite frankly, in my opinion would come in *awfully handy* especially on Metas at times, when an issue gets revisited at a later date.
  • Maybe what we need here is some way to close a question as "superseded by" another question; not really a *duplicate* per se, but something that works similarly from a technical and user perspective, with different display strings in the UI and a different implied direction of causality.
  • That would allow handling precisely this case, and quite frankly, in my opinion would come in *awfully handy* especially on Metas at times, when an issue gets revisited at a later date.
#2: Post edited by user avatar Canina‭ · 2020-08-24T06:08:19Z (about 4 years ago)
  • Maybe what we need here is some way to close a question as "superceded by" another question; not really a *duplicate* per se, but something that works similarly from a technical and user perspective, with different display strings in the UI.
  • That would allow handling precisely this case, and quite frankly, in my opinion would come in *awfully handy* especially on Metas at times, when an issue gets revisited at a later date.
  • Maybe what we need here is some way to close a question as "superceded by" another question; not really a *duplicate* per se, but something that works similarly from a technical and user perspective, with different display strings in the UI and a different implied direction of causality.
  • That would allow handling precisely this case, and quite frankly, in my opinion would come in *awfully handy* especially on Metas at times, when an issue gets revisited at a later date.
#1: Initial revision by user avatar Canina‭ · 2020-08-24T06:07:31Z (about 4 years ago)
Maybe what we need here is some way to close a question as "superceded by" another question; not really a *duplicate* per se, but something that works similarly from a technical and user perspective, with different display strings in the UI.

That would allow handling precisely this case, and quite frankly, in my opinion would come in *awfully handy* especially on Metas at times, when an issue gets revisited at a later date.