Step by step
- Treat your posting schedule as the monitoring schedule. A repost on kemono.su follows a new post on the source platform, not a random calendar. Checking in the days after you publish catches far more than a weekly sweep at a fixed time.
- Keep every URL you have filed on. Store each kemono.su URL with its notice date and outcome. A repost is only provable as a repeat when the earlier record exists, and the repeat is what gives the second notice its weight.
- Cite the earlier notice when you re-file. Reference the previous notice and its date in the new one. A documented pattern reads very differently at the network and provider rungs than a single URL complaint does.
- Add returning URLs to the delisting list. A rebuilt kemono.su page is a new URL and a new search result. The earlier delisting request does not extend to it, so it needs its own entry rather than an assumption.
- Match on the image when the text changes. Reposts often lose the creator name from titles and captions. Perceptual hashing of a reference image finds those, because the image survives the edit that the keyword does not.
What openDMCA can honestly claim about reuploads on kemono.su
openDMCA queries the aggregator sources directly rather than waiting for a search engine to index a new page, and records where each leak was first seen. A post found that way is found before it is searchable, which is a genuinely earlier catch and is recorded as such.
The limit stated plainly: nothing here prevents kemono.su scraping a platform you publish on. What changes is the delay between a repost appearing and a notice being sent, and how much of the checking you personally do.
A liveness sweep runs daily against URLs already marked removed and reopens any that came back, which is how a removal that lasted six days is distinguished from one that held.
openDMCA gives the first two hops away: you can open the reupload check and run it on a URL of your own, with no account and nothing uploaded.
One thing that catches people out on kemono.su
openDMCA's queue runs every thirty minutes, but escalation past the first notice is opt-in and defaults to off, and the maximum number of dispatch rounds defaults to three. On a re-scraping host like kemono.su that combination matters: with escalation left at its default, a returning post gets one notice per round and then goes to delisting, rather than cycling through email rounds nobody reads.