But when the user clicks the link the system has no idea of what page to show at all.
Thus it seems when items are marked as duplicates, the system
should ensure the old link still redirects somewhere appropriate, and
doesn’t become a 404, etc.
I am unsure where it would point to once the topic in question has been deleted? Would the 404 not indicate that the topic has indeed been deleted as a duplicate?
Could that be automatic, similar way it should (is it?) when merging or by choose by acting staff because by definition it is 404; that can and should be under debate.
I feel doing redirections too difficult on Discourse, but the issue is propably just me.
At WordPress I have several plugins that helps me with 404/410/301/302 question. But WordPress is a bit different world per design and amount of users, so maybe it is unfair to compare.
It doesn’t matter. It never matters and that’s why we are using 301 redirections. Will it break possibility to continue discussion on that topic that email is using? Propably, I don’t know — but clicking that link should be redirected on forum.
Are we talking about same thing? As I see it here is too different scenarios/happenings:
what happends when an user (or Dan in this example ) is using reply-button of email client
Github, Bugzilla, and other issue trackers — and Stack Exchange, for that matter — have the inherent ability to close an item as a duplicate. That is, there is a Duplicate state which is tracked.
Discourse lets moderators combine topics by moving posts, but to my knowledge there is no actual “close as duplicate” functionality that includes tracking that status. What you’re seeing is just someone saying “oh, this is a duplicate, so I’ll delete it”.
That’s not the system throwing information away. It’s the moderator or admin.
I can see a “real” duplicate feature being useful in many cases. But it raises a lot of design questions that would need to be figured out.
Short of that, it’s might be better for the moderator to:
Comment linking to the other topic.
Unlist the topic instead of deleting.
Maybe close it, or mark it to close in a week.
That way, there aren’t mystery 404 errors when following links.
Well perhaps there should be more handy buttons for (templates for) moderators to do the right thing, instead of doing it by hand and creating dead ends. (I don’t know. I’ve never been a moderator.)
(And if they attempt to do it by hand, a friendly warning should come up and say, “Here try this instead.”)
To be clear though, your topic summary really boils down to “Deleted topics go to an error page” - there isn’t a discourse issue. The tools to merge and redirect already exist, you just don’t agree with the way particular topics have been moderated.
Just to note, we use all of the available tools when organising our topics here on Meta, and try to be as sensitive as possible to both posters and readers when deciding which are appropriate to use in each case.
It is rare for a duplicate topic to be deleted rather than merged and is generally reserved for cross-posting. Even in such cases an explainer is given with a link to the other topic so as not to cause confusion.
I think this should provide enough context for why a decision has been made, as well as give directions to where a more appropriate place to continue the discussion can be found.