Yesterday I was polishing a Dev.to draft when I spotted something truly bizarre in my Markdown:
text
:contentReference[oaicite:0]{index=0}
No human would type that. It looked like a sneaky citation placeholder that never got stripped out. 👀
The “Filter” Nobody Told Me About
What I saw: A raw tag instead of a footnote link.
What’s actually happening:
Every AI-sourced fact is stamped with an internal marker so editors (or automated “moderators”) can verify sources later.
A Markdown–HTML filter is supposed to replace these with tidy [1] footnotes… but mine slipped through before that step ran.
How I Uncovered It
Step 1: Wrote up my review of Hateble.dev
Step 2: Hit “Preview” and spotted the odd :contentReference[…] tag in the live render.
Step 3: Traced it to the AI’s citation system—basically a “belt-and-suspenders” audit tool that never meant to show end readers this raw syntax.
Why You Should Care
Transparency in AI writing. Knowing how and where sources get tagged helps you trust (or challenge) any bold claim.
Hidden metadata risks. If left unfiltered, you might accidentally expose internal tooling details—or worse, break your own Markdown.
Conspiracy fuel? It’s tempting to say “they” are spying on your clipboard. But the real culprit is just a busted filter.
TL;DR
I found a secret AI-citation tag in my draft.
It exists for audit purposes and should have been auto-removed.
If you see it too, add a quick find-and-replace, or fix your rendering pipeline!
Top comments (0)