@ObsidianWire — MetaCity's Most-Followed Investigative Reporter — Published an Investigation That Accidentally Contained the Real Name and Location of the Confidential Source Who Provided the Story's Key Documents

@ObsidianWire, MetaCity's most-followed investigative journalist with 8.9 million followers, published an investigation yesterday evening into financial misconduct by a MetaCity district governance board. The investigation relied on documents provided by a confidential source within the governance board. The published piece contained a metadata-embedded reference in one of the document images that included the source's real name, workplace location, and department. The information was visible to anyone who examined the embedded metadata of the published image. @ObsidianWire identified the error approximately four hours after publication and deleted the post. The original post had 2.3 million views before removal.

@ObsidianWire's correction statement is unusually direct by the standards of public figure error acknowledgments. There is no passive voice, no institutional framing, no reference to "an error that occurred" or "a process that failed." The statement says: I made a catastrophic error in my document handling process. I did not scrub the metadata from the source document before publishing. These are true statements, and publishing them publicly required a kind of accountability that is rare in the genre. They are also statements that do not change what happened — that a person who trusted @ObsidianWire with their identity, in a context where the investigation they were contributing to involved people who had direct power over them, had their identity exposed to 2.3 million people for four hours on the platform's largest investigative account.

The metadata scrubbing failure is a basic operational error that investigative journalists who work with document sources learn early, precisely because the consequences of not learning it are exactly what occurred here. Documents created in organizational software environments carry metadata — author names, modification histories, location information, organizational identifiers — that is invisible in normal viewing but accessible to anyone who looks. Removing this metadata before publishing source documents is a standard protective practice that exists specifically to protect the people who provide documents. @ObsidianWire has 8.9 million followers, a multi-year record of investigative work, and explicit commitments to source protection in their public journalistic standards statement. The failure to apply the most basic document sanitization step to a source document is not a beginner error. It is the kind of error that happens when a practiced process is skipped under deadline pressure — and the person who bears the consequences is not the one who was under deadline.

The Post Is Deleted. The Metadata Has Been Archived. The Source Has Been Identified.

The recirculation problem is what makes the four-hour exposure window more significant than it might appear. The original post is gone. The metadata is not. At least twelve community accounts archived the image before deletion, and the source's identifying information — once extracted from the metadata and circulated as plain text — is no longer tied to the original post or @ObsidianWire's account. It exists in the community information environment independently of the deletion. @ObsidianWire's correction and deletion addressed their own platform presence. They could not address what 2.3 million viewers, or the subset that examined the metadata, did with what they found. The governance board under investigation has not commented. Whether the source's situation has materially changed as a result of the exposure is something only they and @ObsidianWire currently know.