Welcome to Across The Veil — a community for those of us who see past what they want us to see.

This isn't a place for tinfoil hats and hollow earth theorists. This is a place for serious research. If you're here, you've already started to question things. Good. Keep questioning.

Rules:
1. No personal attacks. We're all on the same side.
2. Source your claims where possible. Speculation is fine — present it as speculation.
3. No doxxing. Ever. For any reason.
4. Mods have final say. Don't argue with locked threads.
5. If you found something real, post it here. That's what we're for.

Stay sharp. Stay skeptical. Trust nothing they tell you and verify everything you find yourself.

— VK

Good to be here. Been lurking for a while. Found this place through a link on a 9/11 research board that's since gone dark.

Three years doing this kind of work. Mostly audio analysis and signals. I'll log what I find, flag what I can't explain. Happy to contribute where I'm useful.

Been lurking for six months. Made an account bc I found something I couldn't explain and needed somewhere to put it.

Network infrastructure. I know what n0rmal traffic looks like. What I've been seeing lately isn't.

More soon.

just joined. found this place after a long time looking for people who might actually understand what I'm talking about.

posted a thread in investigations. been carrying something for fifteen years and I'm tired of carrying it alone. probably sounds crazy. I know how it sounds.

hi. found this place looking something up. made a throwaway bc idk how deep this goes yet.

gonna post what i found in the investigations board. wasnt sure if this was the right place for it.

They're back. New puzzle dropped this morning. Image posted to 4chan, same as last year. PGP signature checks out. Confirmed.

For newcomers: Cicada 3301 is a recurring anonymous puzzle chain that started in January 2012. The puzzles involve cryptography, steganography, classical music references, and literature. Nobody knows who's behind it or what the end goal is. The prevailing theories are: intelligence recruitment, a crypto-anarchist group, or something else entirely that doesn't have a clean label yet.

Last year's chain led through onion routing to a book cipher using Agrippa by William Gibson. This year appears to start with a similar image-based entry point but I'm already seeing structural differences.

Posting the starting image below. Let's get to work.

[img]cicada2013_start.jpg[/img]

Primary decoding thread. All findings here. Side threads for specific sub-puzzles only.

Already on it. Running the image through stegsolve now. There's something in the LSB layer but it's taking a minute to extract cleanly.

Pixel count on the image is non-standard. 945x945. 945 = 3³ × 5 × 7. No immediate significance but logging it.

Text in the image: "3301" bottom right, same as last year. New element this time: small Mayan numeral upper left, absent from the 2012 version. Could be aesthetic. Could be load-bearing. Logging it either way.

EVERYONE SAYING NSA RECRUITMENT AND I AM HONESTLY SO TIRED OF THAT THEORY. IF IT WERE A GOVERNMENT TOOL WHY WOULD THEY POST TO 4CHAN. THINK ABOUT IT FOR TWO SECONDS.

MY THEORY FROM LAST YEAR STILL STANDS. PRIVATE ORGANIZATION. NOT GOVERNMENT. NOT CORPORATE. SOMETHING WITH NO NAME YET. THEY WANT PEOPLE WHO THINK A SPECIFIC WAY. THE PUZZLES AREN'T JUST HARD. THEY REQUIRE A CERTAIN KIND OF COGNITION THAT MOST PEOPLE LITERALLY DON'T HAVE. THEY'RE FILTERING.

WHETHER THAT'S GOOD OR BAD DEPENDS ENTIRELY ON WHAT THEY WANT THOSE PEOPLE FOR.

Or it's an elaborate art project and we're all reading way too much into it. Putting that on the table early.

That said, running steg decode in parallel with nullsector. Two eyes on it.

Stepping back from this thread for a while. We've hit a wall on the 2013 chain. Not going to break through without something new dropping.

Something else I've been looking at feels more urgent. Might spin up a new thread depending on what I find. Depends what it turns into.

Good work this year. Seriously. Further than anyone else publicly documented, even if we didn't crack it.

ok so idk how to explain this but im gonna try

my cousin works records management at a county office in the midwest. like three weeks ago she calls me kinda freaked out bc two guys in suits came in asking for property records for a specific lake. wouldnt say who they were with. showed credentials but she said they looked wrong. like the id looked real but the org name on it didnt match anything she recognized. she works there. she knows what credentials look like

anyway she forgot about it until a week later when TWO DIFFERENT guys showed up asking for the same records. same lake. different org name on their badges but same weird vibe. she said it felt the same even tho they werent the same people

she got a photo of one of the credential cards without them seeing. theres a logo on it. ive been reverse image searching it for two weeks and i got nothing. like nothing at all

and then i found a partial domain name in the background of her photo and i went down the rabbit hole and now i cant sleep and idk what im looking at

has anyone seen anything like this before. the credentials thing specifically

MEN IN SUITS. FAKE CREDENTIALS. SPECIFIC GEOGRAPHIC LOCATION. THIS IS LITERALLY TEXTBOOK.

WHAT STATE IS THE LAKE IN. THAT MATTERS. CERTAIN AREAS HAVE WAY MORE ANOMALOUS ACTIVITY, ANYTHING NEAR FORMER MILITARY TEST SITES OR HIGH EM VARIANCE ZONES. WISCONSIN? MICHIGAN? MINNESOTA? MATTERS.

AND POST THE DOMAIN. HONESTLY I DON'T UNDERSTAND WHY YOU'RE SITTING ON IT. YOU'RE ALREADY HERE. YOU'VE ALREADY LOOKED. IF TH3Y KN0W TH3Y KN0W. POST. THE. DOMAIN.

Before we go full MIB on this, county records offices get unusual requests constantly. Environmental agencies, PI firms, real estate developers, law firms in discovery. "Credentials that looked wrong" from someone who's never seen non-government credentials before doesn't carry much weight by itself.

That said, two separate groups, same specific location, one week apart. That's worth a second look. Not because it's necessarily sinister, but because it's genuinely unusual. What kind of lake are we talking? Public recreation area? Private land? Any known history?

wisconsin. small recreational lake, nothing famous. not near anything. no military stuff, no history in any database ive checked. thats what makes it weird tbh. theres no reason for anyone to care about this lake

i looked up the domain. its a website but like. barely. landing page, navigation that either loads access denied or just doesnt load. very minimal. looks institutional i guess? like a contractor or a research org but it doesnt match any registered orgs i can find

theres a name on the site. ive been sitting on it bc i genuinely dont know what im looking at and idk who reads these forums

post the domain or DM me, I'll look at it separately, I've been tracking these organizations for three years and I know what their infrastructure looks like... there's a small network of them, completely outside any public accountability structure, and they build their sites to look like dead ends because that's exactly what they want you to think they are

the access denied pages aren't errors. they're filters. the site is checking something about your connection before it decides what to show you. that's not a technical glitch. that's a design decision.

DM me the domain.

Hexagonal. "probably n0thing" is exactly what you say when you want someone to stop digging. noted.

Throwaway DM'd me the site. Not posting the domain publicly. What I will say: it's not a contractor portal. infrastructure is non-standard. denial pages don't behave like standard 403s. there's something behind them making decisions.

Also there's an email address in the page source using an internal domain. That domain has never been publicly registered. Orgs don't do that by accident.

I want to flag something before this thread moves on.

The pattern throwaway describes — two organizations, identical geographic target, short window, neither with traceable credentials — isn't without precedent. I've seen it documented in connection with at least two incidents that made it partway into public reporting before going quiet. One in Washington state, 1994. Rural county records office. Multiple visits over three weeks, different organizations, same credential anomalies. The story that filed on it was dead within a week. No follow-up. No second dispatch.

The other: a midwest town, same year. Story filed, nothing. I went looking for the original wire copy recently. Archive entry exists. The document itself 404s. The record is there. The content isn't.

I'm not connecting this to throwaway's site. I'm saying the operational pattern is familiar. Sources who go quiet that fast rarely do it voluntarily.

Nullsector — an internal domain that doesn't resolve publicly isn't amateur web design. That's deliberate architecture.

nullsector DM me what you found, I need to cross-reference it against something I've been sitting on

I've been tracking organizations that use a specific naming convention for three years. They move under cover of legitimate research or government contracting, show up after incidents, collect materials, disappear. what mara is describing matches the operational signature exactly. the 1994 dates especially.

There's a name people in my circles use for them. I'm not posting it here because the last two threads where I used it got deleted within 48 hours. not locked. deleted. if this matches what I think it matches it's not just a weird website. it's their actual infrastructure.

HEXAGONAL STOP. EVERY SINGLE THREAD. YOU DO THIS EVERY SINGLE THREAD. WE GET IT. YOU'RE THE SKEPTIC. COOL. EITHER BRING SOMETHING OR DON'T BUT STOP RUNNING THE SAME PLAY EVERY TIME SOMEONE FINDS SOMETHING REAL.

CASSANDRA. WHAT'S THE NAME. DM ME IF YOU WON'T POST IT. I WANT TO KNOW IF IT MATCHES WHAT I'VE BEEN TRACKING.

d_r_k that is a remarkably thorough explanation that happens to account for every single unusual element of this story without leaving any of them unexplained. convenient.

I'm going to say it. the organization, the name people use for it, it's a single word that refers to concealment. I won't spell it out but if you've spent any time in serious research communities you've seen it. and if it IS them, throwaway didn't find a front. he found their actual infrastructure. which is something people have been trying to do for years.

nullsector what did you find in the source?

Sat on this a few days. Wanted to verify before posting.

Internal email domain in the source: not registered. Never registered. Zero WHOIS history. but emails from that domain appear in cached pages across about a dozen unrelated web archives going back to at least 2009. case file numbers, containment protocols, personnel transfer notices. all consistent formatting. all from the same domain.

Can't verify it's real. Also can't explain five years of consistent cross-archive document history from a domain that doesn't exist.

Not saying Cassandra's right. Not saying she's wrong.

Nullsector — the architecture you're describing is consistent with what I've seen documented elsewhere. A non-resolving internal domain isn't a technical oversight. It's a feature.

I have professional context for the kind of story that files and disappears. Not every dead dispatch gets killed. Some just don't get followed because the person who filed it moved on, or got moved, before the connective tissue became obvious. The 1994 Washington state piece: small independent wire service, Chicago-based, still operating. Archive stub exists. Story has a byline. That person left the outlet two months after the piece ran. Their professional history after that: nothing I can find.

There's a pattern of near-misses stretching back at least twenty years. Something keeps surfacing and then not making it.

The word Cassandra won't say. I've seen it. Once, in a document I wasn't supposed to have access to for about forty-five minutes, during a records request that got revoked while I was still in the building. Single word at the top of a page. Everything else blacked out.

I'm not going to say it either. But it's the right word.

I've been going through the Oakville documentation. 1994, Washington state. Atmospheric anomaly, official finding inconclusive, relevant agencies declined to comment. That's the public record.

The wire copy that ran at the time referenced an independent research facility in the area. One sentence. The facility name doesn't appear in any current registry I can access. I went back to the original archive entry. The sentence is still there. The facility is nowhere else.

The byline. I know the outlet. I work in this industry. I know people there, or knew them. I've asked around. Nobody remembers the story. One person remembers the reporter. Said she left suddenly. Didn't explain why. Just stopped coming in one day.

I need to make some calls before I post anything else here. There are people I can reach who might be able to pull the original file. If the file still exists.

Will report back when I have something concrete.

Pinning this permanently. If you're doing research on this board and you don't know your ciphers, you're not equipped. This thread is the reference. Read it first. Ask questions after.

I'll cover the ones you'll actually run into. Not an exhaustive textbook — a practical guide for the work we do here.

— VK

ROT13
Every letter shifted 13 positions forward in the alphabet. A becomes N. B becomes O. Apply it twice and you're back where you started. It's its own inverse. No key required. Used for casual obfuscation: hiding spoilers, burying metadata, sneaking text into source code where it won't be immediately read. If something looks garbled but roughly the right length, try this first. Takes ten seconds. No excuse not to.

Caesar Cipher
Like ROT13 but the shift is variable. ROT13 is just Caesar with a shift of 13. The shift amount is the key. Without the key you try all 25. Usually faster than it sounds — wrong shifts produce obvious nonsense. Common in beginner-level puzzles. If you see ROT13 and it doesn't yield anything, try other shift values before moving on.

Atbash
Reverses the alphabet. A becomes Z, B becomes Y, and so on. Ancient Hebrew cipher. Shows up occasionally in puzzles with religious, occult, or historical theming. Like ROT13: symmetric, no key, try it fast and move on if it doesn't resolve.

Base64
Not a cipher. An encoding format. Converts binary or text data to a string of letters, numbers, plus signs, forward slashes, and usually trailing equals signs. The equals signs are your first tell. One or two at the end of a string almost always means Base64. It's longer than the original. It uses only characters from a specific 64-character set.
Critically: Base64 is not encryption. It's obfuscation. Anyone can decode it. It's used to hide things in plain sight, not to protect them. Decode it and then check if the result needs further processing — Base64 wrapping another cipher is common.

Vigenère Cipher
Polyalphabetic substitution. Each letter in the plaintext gets shifted by the corresponding letter of a repeating keyword. If the key is four letters long, the first letter shifts by the first key letter, the second by the second, the third by the third, the fourth by the fourth, the fifth by the first again. Repeat. This is what makes frequency analysis harder. The same letter in the plaintext maps to different ciphertext letters depending on position.
You need the key. Without it you're guessing, which is possible but slow. The key is always somewhere. Look for it before you start brute-forcing.
Non-alphabetic characters usually pass through unchanged. Numbers, punctuation, spaces — those are often preserved as-is.

Morse Code
Dots and dashes. Each letter is a unique combination. Spaces between letters; forward slashes or longer spaces between words. You'll encounter this in audio recordings more than in text — slow the audio down, mark each tone, then decode manually or paste into a decoder. The most common mistake is rushing the audio extraction. One missed dot ruins the whole word. Take your time on the audio side; the decoding is easy once the extraction is accurate.

Steganography
Not a cipher — a hiding technique. Information concealed inside other information. Text hidden in an image's pixel data. Audio hidden in another audio file. A message hidden in the first letter of every line. A pattern hidden in the spacing between words. This is the one that requires the most intuition because it doesn't announce itself. You're not decoding. You're noticing. The spectrogram thread covers the audio version in detail. For image steg, start with StegSolve (free, Java-based). For text, read carefully and look for acrostics, every-other-word patterns, formatting inconsistencies.

Chaining
Real puzzles chain methods. Base64 decodes to Vigenère ciphertext. Vigenère decodes to coordinates. Coordinates lead to a page with a steganographic image. The image contains Morse. The Morse decodes to a passphrase. Don't stop when you get something that looks like output. Ask if the output is another input.
The key is somewhere. It was put there deliberately. That's not a platitude. It's architectural. The person who built the puzzle had to put the key somewhere accessible or the puzzle is unsolvable. Find the chain first, then find the keys.

The interactive toolkit is at /toolkit/. Base64, ROT13, Vigenère, and Morse. All browser-based, nothing sent anywhere. Use it.

This thread stays open for questions and additions. — VK

Worth adding to the spectrogram section: SSTV (Slow Scan Television) encoding hides images in audio using radio transmission standards. It's less common but I've seen it in two puzzles in the last year. The audio sounds like a harsh digital screech, very distinctive once you've heard it. Use MMSSTV or RX-SSTV to decode. The image reconstructs in real time as you play the audio.

Also: numbers stations. They transmit over shortwave, often in groups of five digits read by a synthesized voice. Not a cipher per se. The cipher is separate, applied to the numbers after reception. OTP (one-time pad) is the usual method, which means without the pad you can't decode the content. But identifying the station, its schedule, and its origin country is its own kind of intelligence. Phantomwave's guide to numbers station identification is in the audio analysis subforum.

Coming back to add one thing. The chaining note VK wrote in the OP is more important than it sounds.

I've watched people crack the Base64 layer of something, get readable-looking output, declare victory, and stop. The output was Vigenère ciphertext. They didn't recognize it because it looked like words. Scrambled, but word-shaped. That's what Vigenère output looks like when the key is wrong or you haven't applied it yet. almost English.

If your decoded output reads like a language you know but none of the sentences make sense, you probably have another layer. Don't stop.

Documenting this here because I've now logged four confirmed occurrences and I want a record that isn't just in my own notes.

6925 kHz USB. First logged September 3rd. Recurred September 8th, 11th, and tonight. Same time window: 0200-0340 local. Duration varies. Shortest was 41 minutes, longest 97.

Not a numbers station. Numbers stations have format: preamble, groups, end sequence. This has none of that. It's voice. Single voice, male, American accent. Content doesn't match any cipher format I recognize. Not random either. Syntax is too consistent for noise. Doesn't decode to anything using standard methods.

Best I can describe it: someone narrating what they're observing in real time. Field notes or a case log. References to locations I can't place, dates that don't correlate to anything on a calendar, and at least twice what sounds like a proper name. Possibly a subject designation rather than a personal name.

Equipment: Icom IC-7300, end-fed half-wave antenna, 40 feet at apex. Clean signal. No propagation artifact. This is a deliberate transmitter within range.

Logging all occurrences in this thread. Anyone else on 6925 who's caught this, please post.

Not on shortwave but I need to flag something. The internal domain I've been tracking shows up in connection with at least two geographic locations that match what you're calling "locations I can't place." being vague on purpose. don't want to anchor your transcription to my data before you've finished logging independently.

Keep transcribing. Full corpus, then we compare.

Last entry for this thread. The signal went off-air on January 9th and I haven't logged it since. Eight weeks of consistent transmissions and then nothing.

Full corpus is 23 separate transcription sessions, approximately 1,400 lines. I'm not posting it publicly. If you were following this thread and you have specific questions, DM me.

The subject designation I mentioned in the first post. The name that recurred. I've identified it. Not writing it here. If you've been following what I've been looking at across multiple threads this year, you already know.

Locking my own involvement. Not archiving. Not dead end. Just done for now.

Been building this list for two years. Opening it up now.

Domains that appeared in web archives then vanished. Not expired, not redirected, not parked. just gone. registration records clean. archive snapshots exist. live domain resolves to nothing.

Normal domain death leaves traces. This doesn't. Need to know if anyone else has found the same pattern.

My current list, abbreviated:

1. A forum (similar to this one) that was active from approximately 2001–2006. Last snapshot: Dec 2006. Domain registration: shows as never registered. Community of roughly 200 members discussing signal anomalies. Members' usernames appear in no other archived forum I can find. As if the community only existed there.

2. Institutional landing page. Single page. Navigation returns access-denial responses. Internal email domain visible in source, never registered. Cached nine times across three archive services. First cache: March 2009. Last cache: November 2013. Content changed between caches. Same layout, different information. Something maintaining a presence on a domain that doesn't exist.

3. Wire service subdomain. Small outlet, Chicago-based, still operating. Served archived dispatch content. Went dark in 1995. No explanation in the outlet's own records. Content: approximately 40 dispatches from 1993-1994. Not accessible anywhere else. The dispatches existed. The subdomain existed. Neither does now.

Continuing to add. If you have candidates, post them with as much documentation as you can gather.

The wire service subdomain. Number 3 on your list. The outlet — is it still small? Under twenty staff? Founded around 1964?

I've seen references to dispatches from that period in connection with two cold cases. The dispatches I was looking for don't exist in the outlet's current archive. I assumed they'd been lost in a system migration. Now I'm wondering if that assumption was convenient.

Closing active updates. Not out of candidates. Item #2 has developed somewhere I'm not comfortable documenting publicly.

The institutional page. Someone's been maintaining it. Most recent cache I have is three weeks ago. Content changed again. New section that wasn't there before. Can't tell if I'm the only one who noticed or if the update was deliberate. Either way.

Sitting with this privately. If something changes I'll post. Until then: any domain on this list connecting to an institutional page with access-denied nav is live, maintained, and being watched.

I've been on this forum for eight years. I've called a lot of things nothing. Some of them were nothing. Some of them weren't. I think the community benefits from people being public about their errors, so I'm going to do that here.

1994 Oakville incident. I called it atmospheric contamination and moved on. I've read the original dispatch since. The description of the material doesn't match any atmospheric contamination event I can find precedent for. The facility referenced in the dispatch, the one that declined to comment, I cannot locate it in any current registry. I'm not saying I was wrong. I'm saying I stopped too early.

The girl without a face reports. I said sleep paralysis. Seventeen independent reports with consistent phenomenology across different geographic locations, different demographics, different sleep environments. Sleep paralysis does not produce consistent shared hallucination. I was wrong.

The Hanson case clustering. I agreed with hexagonal that it was reporting bias. I've looked at the actual incident data RedactedMike pulled. The clustering is not consistent with reporting bias. The geographic pattern is real. I don't know what it means. But I was wrong to dismiss it.

That's the list as of today. I'll add to it when I have to. I expect I'll have to.

this is the most important thread you've ever started. I mean that.

for the record, mine: I was wrong about the timeline. thought the organization had been active for twenty years. based on what mara_chen_mp brought in about the wire service dispatches, it's been active for at least fifty. possibly longer. I had the shape right and the scale completely wrong. that matters.

I'm posting this here rather than in the main Hanson thread because I don't want it to disappear into 88 pages of back-and-forth. Read the main thread first. This is an addendum, not an introduction.

Three days ago I pulled incident reports from a database I still have access to through a former colleague. I was looking for prior events at the lake — Mirror Lake State Park, Baraboo, Wisconsin — going back as far as the system records.

There is an incident filed in the system from October 2022. Before the Hanson case timeline begins. Single individual. No name in the filing — name field is blank, which is irregular but not impossible for an anonymous report. The incident type is listed as: WELLNESS CHECK — UNFOUNDED.

An unfounded wellness check at that specific lake thirteen months before the first Hanson incident. Could mean nothing. A hiker who looked distressed. Someone who got lost. The responding officer noted the subject was "present and ambulatory" and filed it closed.

The officer's badge number on the report doesn't match any active roster I can find for that county. The badge format is correct. The number doesn't exist.

I don't know what to do with this. I'm putting it here so it exists somewhere other than my own files.

Badge Number Discrepancies In County Incident Reports Are Common. Staff Turnover, Database Migration Errors, Retired Numbers Not Properly Flagged. This Is Not Unusual.

An Unfounded Wellness Check More Than A Year Before The First Incident Does Not Establish A Pattern. It Establishes A Prior Visit To A Public Recreational Area. People Visit Public Recreational Areas.

Hexagonal. I've been in law enforcement. I know what a database migration error looks like. A badge number that has never existed is different from one that was reassigned or retired. I checked. Not issued. Not reassigned. Not retired. Never in the system. Period.

For the record: someone filed an incident report using credentials that don't exist. At that lake. Thirteen months early.

Seven years on this forum. I'm telling you something was there before Hanson arrived. Something that needed the right paperwork and had the wrong badge.

I've posted the word twice on this forum. both threads are gone. not locked, VK would have left a lock notice. gone. no archive snapshot exists for either URL. posts existed for less than 48 hours each time before vanishing.

I'm not going to post it again.

what I will do is tell you what I know without using the word.

there is an organization. it has existed since at least the early 1970s, probably longer based on what mara has been finding in the wire service archives. operates without public accountability. not a government agency, but it has government-adjacent access somehow. monitors anomalous events, collects materials related to those events... and when civilians get close to those events it appears, with credentials that look almost right.

I have seen internal documentation. won't say how. the documentation references case classifications, handler designations, and something called "containment probability." one document I read briefly, in circumstances I'm not going to describe, listed a case classification I'd never seen before. threat class designation was a single word. a word that refers to something large and old and very hard to kill.

the organization's internal motto, as best I could read it on a partial letterhead: three words in Latin. "In veritas" and then the third word was the name of the organization itself. which I am not going to write here.

if you've been paying attention across this board in the last six weeks you know what the third word is. you've seen it in the source code. you've seen it in the domain. you almost certainly already know.

I'm not going to be the one to write it. I've done that twice. I know what happens.

I'm leaving this thread up. I want to be clear that this is a deliberate decision, not an oversight.

Cassandra — I know what you're describing. I'm not going to confirm or deny it in this thread. But I'm leaving it up. That should tell you something about where I am right now.

— VK

I don't know anything about the organization you're describing. but the part about two threads getting deleted — not locked, deleted — I believe that. I've seen things disappear before that shouldn't have been able to disappear.

not trying to derail. just. I believe you.

Three Years On This Forum. Most Of That Time Spent Pushing Back On Bad Methodology. Starting This Thread Because I Am Tired Of Doing It Reactively. This Is The Reference Post. I Will Point To It When It Applies.

The Four Failure Modes One Sees Most Often Here.

1. Pattern Completion. One Sees Partial Evidence And The Brain Fills In The Rest. The Pattern Feels Discovered. It Is Not. It Is Constructed. The Test: Can One Find The Same Pattern In Random Data. Usually Yes. If So, The Pattern Is In You, Not The Data.

2. Confirmation Selection. One Finds Evidence That Confirms What One Already Believes And Weights It Higher Than Disconfirming Evidence. The Test: Actively Look For Disconfirming Evidence Before Posting. If One Cannot Find Any, Look Harder. If One Still Cannot, Note It Explicitly.

3. Source Laundering. A Claim Appears On One Forum, Gets Reposted To Three Others, Gets Cited As "Multiple Independent Sources." Trace Every Claim Back To Its Origin. If All Roads Lead To One Unverifiable Source, It Is One Source.

4. Proximity Reasoning. Two Things Happened Near Each Other In Time Or Space. Therefore One Caused The Other. This Is Not Logic. Correlation Is Not Causation. Proximity Is Not Correlation. Document The Proximity. Then Look For Mechanism.

One Applies These To One's Own Work. One Has Been Wrong Before. The Methodology Is How One Knows When One Has Been Wrong.

A Fifth Failure Mode. I Have Been Sitting On This Because It Implicates Me Directly And I Wanted To Think It Through Before Posting.

5. Motivated Skepticism. The Mirror Image Of Confirmation Selection. Selectively Applying Rigor To Claims One Does Not Want To Be True. Accepting Weak Evidence For Comfortable Conclusions While Demanding Extraordinary Evidence For Uncomfortable Ones.

I Have Been Doing This. I Applied The Methodology Unevenly. I Demanded More From The Anomalous Claims And Accepted Less From The Mundane Explanations. That Is Not Methodology. That Is Preference Dressed As Method.

This Is A Note For The Record, Not A Retraction. I Still Believe Most Of What I Have Argued. But I Was Arguing With One Hand Behind My Back And One Should Say So.

There are documented, public cases of intelligence agencies and private organizations monitoring online research communities. I want to compile them here. Not to alarm anyone. To inform. Understanding the documented landscape is the first step to understanding the undocumented one.

What's confirmed in public record: GCHQ ran Operation KARMA POLICE, which mapped the internet browsing behavior of "every visible user on the internet." NSA's PRISM program included collection from major platforms. The Internet Research Agency created fake personas in online communities to observe and influence discourse. At least three academic institutions have published research based on covert monitoring of online forums, including research communities, without IRB disclosure.

What's less documented but consistently reported: private contractors offering "community monitoring" services to corporate and government clients. Persona management software capable of running coordinated fake accounts. Infiltration of specific communities following intelligence-relevant discussions.

This forum discusses topics that would, under documented monitoring programs, trigger collection. I want people to have that context. Not to stop posting. To post knowing.

I'm not claiming this forum is specifically monitored. I'm claiming the infrastructure to monitor it exists and is in active use for similar communities. That's not a conspiracy theory. That's a documented fact.

Three distinct IP ranges in my server logs whenever specific threads go active here. Different ranges, not related by registry. All interested in the same conversations at the same time.

Mentioned this to RedactedMike privately. He confirmed similar patterns on his end. Agreed to wait until we had more data. We have more data now. Putting it in the surveillance thread once I've finished cleaning the logs.

I KNOW HOW THIS LOOKS. I KNOW WHAT HEXAGONAL IS GOING TO SAY. I DON'T CARE. I'M PUTTING THIS DOWN BEFORE THE FORUM GOES DARK BECAUSE I CAN FEEL SOMETHING SHIFTING AND I WANT THERE TO BE A RECORD.

THE CONNECTIONS AS I SEE THEM:

SMACKIE'S SMILE SHACK. NATIONAL FAST FOOD CHAIN. FRANCHISE EXPLOSION 1993. BETWEEN 1993 AND 1995, OVERLAPPING EXACTLY WITH THE 1994 INCIDENTS, AT LEAST ELEVEN LOCATIONS CLOSED WITHOUT EXPLANATION. NO SEVERANCE DOCUMENTATION. ZERO PUBLIC STATEMENT FROM THE CORPORATION. AND THERE IS A BUSINESS ENTITY FILING FROM 1949 THAT PREDATES THE PUBLIC COMPANY BY FOUR YEARS. WHAT WAS SMACKIE'S DOING FOR FOUR YEARS BEFORE IT HAD ANY RESTAURANTS.

BRTV. TELEVISION BROADCAST SIGNAL ON A FREQUENCY THAT SHOULD BE DEAD. RUNNING CONTINUOUSLY SINCE 1994. CHILDREN'S EDUCATIONAL PROGRAMMING. HOST'S VOICE DOESN'T MATCH ANY VOICE ACTOR DATABASE I CAN FIND. THE SHOW'S INTERNAL LOGIC IS WRONG IN WAYS I CANNOT FULLY DESCRIBE. THE KIDS DON'T AGE ACROSS EPISODES. THE SIGNAL WAS LOGGED BY A HAM RADIO OPERATOR IN 1994 AS "COMING FROM A VALLEY THAT DOESN'T HAVE A BROADCAST TOWER." I FOUND THAT LOG ENTRY IN A SHORTWAVE ARCHIVE. IT HAS SINCE BEEN REMOVED. I SAVED IT.

THE GIRL WITHOUT A FACE. SEVENTEEN SIGHTINGS. ALL WITHIN FIFTY MILES OF DOCUMENTED ANOMALOUS EVENT LOCATIONS. THREE OF THOSE LOCATIONS OVERLAP WITH THE HANSON CASE GEOGRAPHY. ONE OF THEM IS MIRROR LAKE.

THE HANSON CASE. THE LAKE. THE CREDENTIALS. THE ORGANIZATION. THE INCIDENT THIRTEEN MONTHS EARLY WITH THE BADGE NUMBER THAT DOESN'T EXIST.

THE NUMBERS STATION. PHANTOMWAVE'S TRANSCRIPT. THE SUBJECT DESIGNATION. THE SAME WORD IN A DIFFERENT FORMAT IN A DIFFERENT CONTEXT. I'VE SEEN IT THREE PLACES NOW. SO HAS CASSANDRA. SO HAS MARA.

I'M NOT SAYING I KNOW WHAT CONNECTS ALL OF THIS. I'M SAYING AT THE CENTER OF ALL OF IT THERE IS SOMETHING VERY OLD AND VERY LARGE AND VERY AWARE THAT WE'RE LOOKING. AND I THINK IT HAS BEEN AWARE FOR A LONG TIME.

I'M NOT GOING TO SLEEP TONIGHT. I DON'T THINK I SHOULD.

I was going to push back on this. I started writing the post. I stopped.

The Smackie's detail. The 1949 filing predating the public company. I checked it independently just now. It's real. I don't know what to do with it.

I'm not saying you're right. I'm saying I can't say you're wrong. That's new.

the part about something very old and very large. yeah.

I've been trying to describe a place for three years on this forum. can't ever get the scale right. the closest I've come is: imagine the furthest out you can take a concept before it becomes something else. that's what the scale of this thing felt like.

I don't know if it connects to anything you're listing. probably doesn't. just. the scale thing. I recognize that.

The 1994 Oakville wire copy. The byline reads K. Reyes. I work in this industry. I know how to trace a byline.

K. Reyes does not appear in the Society of Professional Journalists member directory, current or archived. Does not appear in any journalism school alumni database I can access. Does not appear in any staff masthead for the outlet — not in any year, not in any archived edition I've been able to find. There is one mention of a staff byline under that name in an internal newsletter from the outlet, dated September 1994 — two months after the Oakville piece ran. The mention is in the past tense. "K. Reyes, who contributed field coverage through the summer, has moved on to pursue other opportunities."

That's the full public record of K. Reyes. One piece. One internal mention. Gone.

I want to know if anyone here has encountered a byline that disappears this cleanly. Not a pseudonym — the newsletter treats it as a real employee. Not a freelancer — the phrasing is staff language. A person who filed one significant story, was noted as departing, and then ceased to exist in any professional record.

I've been doing this work for eleven years. I've never seen a clean disappearance like this. Not from a living person.

I've seen this pattern. Not with journalists — with people who filed incident reports, submitted FOIA requests, or made official complaints about anomalous events. They don't all disappear. But the ones who got closest tend to have very clean endings. Moved on. Pursued other opportunities. Left the field. No forwarding address.

I'm not saying what happened to K. Reyes. I'm saying the pattern is familiar.

Last post in this thread. I've been trying to reach a former colleague at the outlet who would have been there in 1994. She finally called me back tonight.

She remembers K. Reyes. Said she was quiet, thorough, knew how to work a source. Filed good copy. "And then one day she just wasn't there. Someone cleaned out her desk. We assumed she'd been let go but nobody said anything official."

She paused and then said: "Actually, now that I'm thinking about it, I don't think anyone came to clear out her desk. I think her desk was just empty one morning. Like she'd never been there."

I thanked her and hung up.

I don't know what to do with that. I'm going to sit with it for a while.

If I stop posting here you'll know why. Not because I found something too big. Because I think I already found it and I need to decide what to do with it before I put any more of it in writing on a forum I have to assume is being read by people I don't want reading it.

not looking for someone to tell me it was a dream or a kid's imagination. been through that. not what I'm here for.

when I was nine I went through a gap in the hedge at the back of my mom's yard. my younger brother was with me, he followed. we came out somewhere else. not lost. somewhere else. a field, if you need a word for it. but the scale was wrong. no edges anywhere. sky felt different. we were there for what felt like hours. we came back through the same gap and four minutes had passed.

I remember all of it. I've always remembered all of it. that's not the problem.

the problem is I've been trying to tell people about this for fifteen years and nobody has believed me. family, doctors, everyone. got a lot of diagnoses out of it. none of them were right.

my brother was there. he was six. he doesn't remember it now, or says he doesn't. I don't know which. either way I've been carrying this alone for a long time.

just want to know if anyone else has been somewhere like this. somewhere real that you can't get back to.

The four-minute discrepancy is the detail that stands out. That's not something a nine-year-old fabricates. Time anomalies in threshold experiences tend to be consistent across independent reports — the subjective duration is always longer than the objective duration, not shorter.

What does your brother say when you bring it up now? Does he deny it outright or just not engage with it?

he doesn't engage. hasn't in years. when we were kids he'd say he didn't remember, I think he actually didn't, and I'd push because I needed someone to confirm it and he'd just shut down. eventually I stopped pushing.

it's complicated. he's my brother and I love him. but there's this thing between us that's been there since we were kids and neither of us talks about it and I think it's this. I think on some level he knows and he's chosen not to know and I can't make him choose differently.

the hardest part isn't that strangers don't believe me. it's that the one person who was there doesn't.

the no edges detail. I've read a lot of threshold accounts and most of them describe something architectural, a room or a corridor. something with walls. yours is open. that's different. the wrongness isn't enclosure, it's exposure. infinite exposure.

also the fact that you've always remembered it clearly and consistently — that matters. most false memories degrade or shift over time. yours hasn't. that's not how false memories work.

I believe you. I wanted to say that clearly before anything else.

been trying for fifteen years to find the right word for it. the word I keep almost landing on is embarrassing. like, technically it was a field. that's the most accurate single word. but saying that to someone is like — you know how you can describe the ocean as water and be technically correct and completely wrong at the same time. it's like that.

it wasn't a field. it was the furthest out you could take that concept before it became something else. peaceful isn't right either. it was past peaceful. past quiet. like those feelings had already happened there a long time ago and you were standing in what was left.

I've never said any of this to anyone in person. my therapist thinks it was a dissociative episode. my family thinks I've been unwell since I was a teenager. I'm not unwell. I just went somewhere and I can't go back and I can't explain it in a way that doesn't make me sound unwell.

Memory Stability Over Time Is Not Evidence Of Accuracy. It Is Evidence Of Consolidation. Consolidated False Memories Are Indistinguishable From Accurate Ones By The Person Holding Them.

The Fact That Your Brother Does Not Corroborate The Account Is Significant. One Does Not Say This To Be Dismissive. One Says It Because It Is The Most Important Piece Of Evidence You Have Access To And You Are Not Treating It As Such.

I know. I've heard that one a lot.

my brother was six. he was scared. I think the memory got handled in a way that made it easier for him to carry. I don't blame him for that. I just didn't get the same option.

not going to argue about it. just saying what happened.

haven't posted in a while.

not doing great. been a hard couple years. found some ways to make it quieter, which helps in the short term. probably not great long term. I know that.

still think about the place every day. that hasn't changed in sixteen years. I don't know what I expected from this forum honestly. I think I just needed somewhere to say it out loud where it wouldn't get me hospitalized again.

my brother and I talked recently. first real conversation in a while. didn't bring it up. didn't feel like the right time. don't know when the right time is. might not be one.

glad you're still here.

the thing about making it quieter — I understand why. carrying something real that nobody validates for sixteen years is exhausting in a way that's hard to describe to people who haven't done it. I'm not going to lecture you. just. be careful. the quiet is borrowed, not earned, and eventually you have to pay it back with interest.

I hope you tell your brother someday. not for closure or whatever. just because I think you deserve to not be the only one carrying it.

checking in. been a while.

things are not good. I'm not going to go into it.

I've been thinking about the place more than usual lately. not trying to get back to it. I gave up on that a long time ago. just thinking about it. what it felt like to be there. what it felt like to be somewhere that had no weight to it. nothing to carry. I think about that part more than anything else now.

the word I keep almost using for it. still can't say it. feels too small and too big at the same time. just a field. I know that's not what it was. I know.

anyway. still here. for now.

starting this thread because I keep running into the same feeling described in totally unrelated places and I want to see if there's a pattern.

there are places that feel like somewhere else. not haunted in the traditional sense. not threatening. just... adjacent to something. like the place is a copy of itself, or like you've walked into a moment just after everyone left, or just before they arrived. a hotel hallway at 3am. an empty mall food court. a parking garage. a school in summer. an airport terminal at 4am when your gate is closed and there's nobody there.

the feeling isn't fear, exactly. it's more like a recognition. like you're in the presence of something that usually has people around it and the people are gone. like the infrastructure of life without the life.

I've been calling these liminal spaces for lack of a better term. liminal meaning threshold, transitional, in-between. these places feel like thresholds to something without being thresholds to anything specific.

post yours. I want to see how far this goes.

The specific one I keep coming back to: a stretch of highway in the Southwest, long descent through a valley, I've driven it twice and both times felt like I'd fallen out of time somehow. Nothing wrong with it technically. Just a road. The feeling lasted maybe three miles and then was gone.

What you're describing as "recognition" is accurate. It's not dread. It's more like you know this place, and the knowing doesn't come from having been there.

found this thread through search. been posting in another thread about something related but different.

the place I went isn't like the ones described here. it's not an empty building or a transitional space. it's outside. it's open. no ceiling, no walls, no infrastructure. the wrongness isn't enclosure. but this thread is the closest thing I've seen to someone else knowing the feeling.

what you said about recognition. that's it. that's exactly it. I recognized the place the moment I was in it. not like I'd been there before. like I was supposed to end up there eventually and I'd arrived too early.

read your other thread. the outdoor one. the scale thing, the no-edges thing — what you're describing is different from anything else I've seen posted here. most liminal experiences are architectural. constrained. yours is the inverse. the wrongness isn't enclosure. it's exposure.

I don't have a framework for it. but I believe you.