Modern Attack Vector · The Channel of Reach
The Comment That Knew
When the reply names a thing no public post mentioned.
The comment is short. Sometimes a single emoji. Sometimes a name — not your name, but the name of someone who died, or the name you have not been called since childhood, or the nickname only your family used. Sometimes a date: the date of a loss, the date of a beginning, the date of a private fear. The comment knows a thing the public post did not say. And the account that left it is one you do not know.
The platform's possible explanations: data brokers, scraped obituaries, leaked DM history, a follower who screenshotted and shared. The site does not contest those explanations. It adds only that the older tradition recognised this category — the named private detail surfaced by a stranger — and called it the gathered name. The protection is older than the platform.
The principle in the old books
“The witch's first gathering is the name. Where the name is known, the binding is possible. Where the name is guarded, the binding fails.”Margaret Murray, The Witch-Cult in Western Europe, 1921
“Coven activity against a marked person begins with the gathering of materials: the name, the daily pattern, the small private detail. The materials gathered, the operation follows.”Malleus Maleficarum, 1487, Part II, on the gathering
“Penemue taught humanity the writing of names, and from his teaching came the great wounding — for the name written and known is the name that can be bound.”Book of Enoch, Chapter LXIX, the fallen Watcher of names
The modern translation
The comment-that-knew is the modern dress of the gathered name. In 1487, the materials were gathered by the familiar walking past the door, by the conversation overheard at the well, by the small object left near the threshold. In 2026, the materials are gathered by data brokers, by old screenshots, by the obituary indexed online, by the algorithm's adjacency suggestions. The harvest is the same. The use is, by the tradition's account, the same.
The site holds one specific position. A named private detail surfaced by a stranger is to be treated as the second yielding — not the first. The first yielding was the original writing of the detail; the second is the resurfacing of it under attention. The discipline of the response is to refuse the third yielding (the reply, the screenshot, the engagement) and to close the channel that surfaced the second.
The protections, in order
When a stranger named a private thing
The protection translates directly. Do these in order.
- Do not reply. Do not screenshot. Do not show your friends. Each is a third yielding. The discipline at this moment is silence.
- Block and report. The block is the closed door. The report is the call to the watchman.
- Audit the source. Where was that detail ever written? An obituary? A locked account? A DM? A public post you forgot? Find the original channel. Close it.
- Speak the name in protection. If a deceased person's name was used in the comment, say their name aloud to a person who loved them, in a brief sentence of remembrance. The old grammar: the name reclaimed by love is unbound from misuse.
- Salt the threshold and pray Michael. The named detail was a small breach of the household; the response is the salt at the doorstep and the brief Michael prayer.
- If the named detail was a child, a death, or a location, treat the matter as acute. Tell one trusted person in person. The tradition does not isolate a marked person.
The diagnostic threshold
The standing rule: one indicator is to be noticed; two is “pay attention”; three or more is the threshold of action. Where the threshold is crossed, do not delay until morning — apply the protection in the same hour you notice the third indicator.
- The detail named is one no public post on any platform of yours has mentioned
- The detail involves a death, a child, a private date, or a name only an intimate would know
- The commenter's account is new, dormant, or otherwise fails the threshold check
- The comment arrived during a period of vulnerability (a recent grief, a recent move, a recent break)
- The same detail surfaces in a second place within the same week
Common questions
How did they know?
Often, the answer is mundane: an obituary, a leaked screenshot, a relative who shared, a data broker. The site holds that the mechanism does not change the response. The detail is out; the discipline is to close the channel, not to spiral on the mechanism.
Should I tell the person who died's family?
Only if you would have anyway. The comment does not place a new obligation on you toward a grieving family. If the detail's exposure feels actionable (the comment is harassing, the family has a stalker, the death was recent), then yes, alert them. Otherwise the discipline is your own threshold, closed quietly.
What if it was just AI scraping?
The site notes that AI scraping is itself the modern dress of the older gathering. The tradition's response does not require that the gatherer be human. The protection — close the channel, salt the threshold, do not reply — is the same.