How should we handle duplicate content on dev.to?

Ben Sinclair - Jun 7 '18 - - Dev Community

As more posts appear here I'm noticing more duplicates. People don't always search to see if their ideas have already been covered before writing a new one or making a new spin on an existing post.

Stack Overflow handles this by shutting the new posts down. Yahoo! Answers handles it by not caring and generally being full of it. In every sense.

We're still early days with this site really, so what are other people's ideas about how to handle it?

We currently have "trending" and "classic posts" as asides to posts, but maybe we could have a "related" section based on keywords or something?

Duplicate isn't always duplicate either - an almost identically-named post could be about the news of a pending event or about how that event has changed the world a year on, for example.

Thoughts?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player