poster precheck
Show the likely repeats before the user hits submit. The point is not to police intent. The point is to surface the closest threads early enough to save mod time.
dupe-detector.
A Reddit-native duplicate-review tool with a simple promise: show repeat posts before they become moderator cleanup. This page turns the existing app listing, Devpost submission, demo video, and feedback threads into one shareable proof surface.
public project
Devpost live
walkthrough
43.88 sec
proof set
4 screenshots
community pulse
2 live threads
walkthrough
The demo moves through the two real surfaces that matter: a poster-side precheck that catches likely repeats before submission, and a moderator queue that keeps duplicate cleanup fast and explainable.
the two workflows, shown cleanly.
This is the shareable artifact missing from the main Reddit hub: a judge-safe and mod-safe place that shows exactly what the tool does without forcing someone to dig through a raw asset directory.
moderator queue
Keep the cleanup lane boring: see the strongest suspects, compare them fast, then lock, remove, or leave without queue archaeology.
clean state
The tool should also know when to get out of the way. A clean board matters as much as a flashy catch if the app is going to earn moderator trust.
live-data proof
The support set includes a live public-data render, not just mocked states. That matters for Devpost judges and for any mod deciding whether the app feels real.
Recent public feedback threads, not reposted spam.
We already used the dev subreddit for small feedback asks. The next move is not another duplicate post in the same community. It is sharing this cleaner proof surface in mod-tool contexts where rules allow and the problem is already visible.
the false positive museum is open
This is the current live thread asking for ugly near-duplicates and edge cases. It follows the Reddit rule set: ask for examples, not installs; tune around moderator pain, not contest bragging.
small duplicate-hunting check-in
The earlier check-in stays relevant as a baseline reference: where did the tool feel useful, and where did it feel annoying? Keeping both threads public helps future outreach stay specific instead of repetitive.