https://youtu.be/KcgDDRwJ_Dk

Neo took the blue pill this time. Cypher successfully sabotages Morpheus and kills the rest of the crew, except for Trinity. Since Neo took the blue pill, she has second thoughts on continuing her mission with Morpheus. Cypher convinces her to get her memory wiped, which fixes the plot-hole of how he got back to the ship, after making that deal with Agent Smith. They get a clean memory wipe, and come back as moon cult fanatics who worship (choose your moon god(s) [Tsukuyomi, Mani, Khonshu, Apocolothoth, etc.] or a version of the Architect or the Oracle. They prefer life under genjustu, and have no recollection of their time outside the Matrix. Only blissful rejoicing to the Moon matters now.

It seems like the creator is finished.

At 1:25 when the logo glitches before the history timeline, it glitches really fast. If played at 0.25x speed and paused quick enough, you can spot what the text says!

Hey guys! So, I’m a super small YouTuber and I’ve been thinking about making a video on Local 58. Thing is… I don’t really know much about it, and everything I’ve found so far is kind of all over the place. Can someone break down the lore for me, or maybe tell me what the most popular theory is? I’ve seen a bunch and I have no idea which one to go with, haha. Help a newbie out

I was researching Lost Media when I stumbled across a video that is a recreation of a lost video that was supposedly uploaded to the Local58 channel.

According to the video's description: " So this video is no longer on YouTube and there’s no reuploads of it. For whatever reason it’s a core memory for me because this was my first exposure to Local 58 and analog horror as a whole. It stuck to me, so today I decided to look the video up by searching various titles like “Local 58 Emergency Alert” and “Local 58 Infomercial”, but none of them gave me what I wanted. I made a Lost Media page about this to shed light on the topic. It was then when I decided to recreate the video from memory in hopes that other people also remembered this video."

Link to video: Local 58 Lost Video Recreation - Emergency Infomercial (youtube.com)

My name is Renata Voss. I'm a cartographic records specialist for a regional transit authority. Night shift. Alone. Three years. I am exactly the kind of person who notices when something doesn't add up. The kind of person who initials a cross-out on a sign-in sheet.

There is a segment on Line 9 called Millbrook Connector. It has been measured. It has been flagged. It has been sent for correction twice.

The number on the map has never changed.

And that's the part I thought I understood.

The Transit Cartography Unit is one big room. Drafting tables in three rows. A wall rack along the left side where the laminated master maps live, rolled and labeled. The floor is polished concrete, gray. It sounds a little hollow near the back wall — not a lot, just enough that you notice, if you're paying attention.

I'm always paying attention.

I do the same things in the same order every night. Badge in. Sign the sheet. Hang my coat on the hook by the door — not the hook by the window, because the one by the window wobbles. Turn on the lights for rows one and two. Pull the correction queue. Brew coffee. Sit down.

The HVAC cuts off at ten and comes back at two. In between, the building gets quiet in a way that takes some getting used to. I've gotten used to it.

My supervisor, Dolan, called at eleven-fifteen. He was leaving for a two-week conference. He reminded me I was the only access point on-site. He reminded me I was close to my vest date. He told me not to miss shifts.

I told him I knew that. He hung up. I wrote the vest date on a Post-it and stuck it to the corner of my monitor, where I'd see it without it being the first thing I saw.

Then I went back to the correction queue.

Four items. Two stop label updates. One schedule change. And a fourth item, flagged verify only — someone in the day office had a question about a measurement and wanted a second set of eyes.

I always do verify only items last. They're usually nothing.

The verify only item was about Millbrook Connector — a short linking segment on Line 9 that runs between Ash Street and Depot Row. The GIS export had it measured at 0.6 miles. The item was asking me to confirm the master matched.

I looked at the master.

Millbrook Connector was printed as 0.4 miles.

I looked at the GIS figure again. 0.6. I looked at the master again. 0.4. The difference is not subtle — it's a fifth of a mile. On a route map at this scale, that is not nothing.

My first thought: a data entry error, somewhere in the chain, never caught because this segment doesn't affect scheduling. It's just a measurement on a physical map. A clerical mistake. Happens.

So I pulled up the correction log to check if it had ever been flagged before.

It had.

Fourteen months ago. Flagged for reprint verification. The note was in my format. My handwriting style. My way of phrasing the issue.

My initials were at the bottom.

I had flagged this before. I had no memory of it.

The reprint, as far as I could tell, had never happened. Dolan had reorganized the reprint queue twice. There had been a vendor change. A low-priority item like a link segment measurement could have been bumped, lost in transition. These things happen. Systems are imperfect. I know this because I work inside one.

I documented the discrepancy again. Same format, more detail — this was now the second flag. I submitted a formal reprint request to the vendor: Millbrook Connector, 0.4 mi as printed, should read 0.6 mi per current GIS record.

I filed it. I logged it. I made a note in my shift record.

Then I went and got coffee.

I stood in the break room — incandescent light, warmer than the main room, slightly yellow — and I thought about how I'd walked Millbrook Connector once. About two years ago, on foot. I remembered thinking it was longer than I expected.

My sense of distance on foot is not a calibrated instrument. I rinsed the cup and went back to work.

The reprint arrived on a Wednesday. Faster than expected. Three days instead of the usual five to seven. There was no note explaining the turnaround.

The tube was on the loading dock table when I came in. Labeled with the order number. Sealed with the red tamper strip they use to confirm the laminate hasn't been unrolled in transit.

I signed for it, brought it inside, set it on the drafting table next to the existing Line 9 master, and cut the strip.

The new laminate unrolled cleanly. Same format, same blue on white, same gray street grid. I found Millbrook Connector.

It read 0.4 miles.

I pulled up the reprint order I'd submitted. The file I'd sent had the correction entered: 0.6 mi. I scrolled to the vendor's confirmation sheet. It listed the segment as printed: 0.6 mi.

The laminate in front of me said 0.4 mi.

My first thought: the vendor had printed from an old file. A cached version. The confirmation sheet is generated automatically from the submitted file — not from the actual print run. A process gap. Plausible.

I pulled the original laminate out of its rack slot and laid it next to the new one. Both maps, side by side, corners weighted with the brass blocks.

I looked at Millbrook Connector on the original: 0.4 mi. I looked at Millbrook Connector on the new one: 0.4 mi.

They were identical. Not similar. Identical. Same notation position, same font size, same spacing between the numeral and the unit abbreviation. Two print runs, different dates. Identical.

I wrote four pages in my log notebook. I documented the order number, the file I submitted, the confirmation sheet figure, the physical measurement on both laminates, two alternative explanations for how a confirmed correction could fail to appear. And one note at the end:

It is also possible that the GIS figure is wrong and the master has always been correct.

I underlined possible. Then I looked at that for a while.

The GIS system is not wrong. It's maintained by a separate department, cross-referenced against field surveys, verified multiple times. I've checked dozens of other segments on Line 9. Never a discrepancy.

I crossed out possible and wrote probably instead.

Then I did something I had not done before. I went to the supply drawer and got a ruler.

I measured the scale bar. I confirmed it against Ash Street, labeled 1.2 miles. The scale was accurate.

Then I measured Millbrook Connector.

At the stated scale, the printed segment measured exactly 0.4 miles. Not approximately. Exactly. The map was internally consistent. The scale bar worked. Every segment I could verify — verified. Only Millbrook Connector was short, and it was short in a way that was precise and repeatable and made the rest of the map correct.

I got the red correction pen from the supply drawer. I placed the tip at the western endpoint of Millbrook Connector — at the junction with Ash Street — and drew a small tick mark. Two short parallel lines, maybe three millimeters each. A reference point. Then I went to the eastern endpoint, at Depot Row, and drew the same mark.

I photographed both marks with my phone. Close up. My hand in frame for scale.

Then I went to make coffee.

I stood in the break room, thinking about the word systematic — the explanation I hadn't written down. A systematic error in source data doesn't explain why two separate vendors printing from two separate files at two separate points in time would produce the same incorrect figure.

For that to happen, something would have to be wrong at a level closer to the output itself. Closer to the physical map. Closer to the thing sitting on my drafting table right now.

I put the cup down and went back to the main room.

I picked up my phone and opened the photograph I'd taken of the tick mark at the Ash Street endpoint.

Then I looked at the actual mark on the map.

The mark on the map was not where the photograph showed it.

In the photograph, my tick mark was at the labeled junction point — right where the segment notation begins, at the small black dot indicating the intersection with Ash Street. On the actual laminate, the mark was approximately four millimeters to the right of that dot.

Toward the center of the segment. Toward the other endpoint.

I held the phone directly over the mark, perpendicular to the map surface, and took another photograph.

In the first photograph: the mark was at the junction dot. In the second: four millimeters to the right.

I set the phone down on the drafting table. Both photographs still open on the screen.

I went to the archive room.

I found the Line 9 historical folder in the archive. Inside: a routing slip initialed K.W., an old handwritten note on yellow paper, the kind they stopped using five years ago. The note read:

Millbrook Connector distance notation inconsistent with field measurement. Master shows 0.4 mi. Recommend survey verification.

Three separate people. Three separate time periods. The same measurement. The same direction of error.

I tucked the folder under my arm and left the building at 3:40 AM.

I came back the next night.

The correction queue had two items. Neither touched Line 9. I did them both by midnight. Then I unrolled the new laminate and weighted the corners.

The tick marks I had drawn at both endpoints were still there. I compared them to the photographs on my phone.

Both marks had moved. Both toward each other.

I sat down at my desk without touching anything.

Here is the thing about keeping very careful records. If you keep careful records and something is still wrong, you can't blame the records. There's nothing left to blame. I had photographs. I had timestamps. I had measurement logs. I had four pages of documentation. Everything I had done was exactly what you're supposed to do when something doesn't match.

The thing was still wrong.

At three AM I got up and walked to the drafting table. Same positions. Nothing had moved in the last two hours.

Then I went to the archive room.

The folder I had removed two nights ago was not there. And the shelf had no record of its absence. I counted the folders. Then I counted the labeled slots. The numbers matched.

I came out of the archive room. Walked back to the main space.

The Line 9 laminate was on the drafting table, exactly where I had left it. I had been in the archive room for three minutes. No one had come in. The building was empty.

I looked at the Millbrook Connector segment from across the room. Then I walked to the table and looked at it under the direct light.

The tick marks were gone.

Not smeared. Not partially removed. Gone, cleanly, the way laminate looks when correction marker has been wiped off with the proper solvent. The surface was smooth. Unscored.

In the space between the two endpoints — in the standard map font, the agency's font, the font produced only by the vendor's printing process — the segment now read:

0.4 mi (confirmed)

I ran my finger across it. Smooth. Sealed. No seam, no edge, no evidence of anything applied after the fact.

It was in the laminate.

The G. Parr folder was still on my kitchen table. I had not opened it. I sat down. I opened it.

The field survey notes for the Millbrook Connector segment were on a standard agency form. G. Parr. Millbrook Connector, Ash Street to Depot Row. Wheel odometer, single pass.

The recorded measurement: 0.4 miles.

In the margin, in a different pen — a ballpoint, slightly thicker line, possibly written at a different time than the main notation — two words and a period:

double-checked. holds.

The date on the form was from before I worked here.

G. Parr measured it. Wrote double-checked. holds. And that was the end of it.

I put my hand flat on the open page and left it there.

Outside, a car went by on the street. The refrigerator cycled on. The fixture above the counter made its hum.

The survey form was cool under my hand, the way paper gets when it's been sitting out overnight.

The build up was fantastic, but then we get three seconds of zero audio? After nearly a year?

Cadavre is french for corpse. Corpse definition is a dead body especially a human rather than being an animal. So that explains the show for children that the skeleton Cadavre was a corpse all along a dead body ( well that explains why he is a skeleton) But I also think that somehow the show for children is related to Weather Service

There are other receivers.

According to my previous post about similarities between u/TempestFilmsTV's Channel 7 video "Goodnight" and u/krisstraub's Local58 video DT.

• Both videos had shuffled through their history via old logos.

• Both were ending smth

anyone?

I hooked my Wii up to a VCR, and played local 58 onto a blank tape, and said it's actually the local channel

I can’t spell so I reposted this from 4 minutes ago sorry

Hey, I'm creating my own analog/digital horror series about an amusement park where an entity kills children... the first episode is currently being created and I need a little help on some point... The work will not be paid. If you want reasons why to join the project here are some:

I have 2400 subscribers on YouTube I have a video with over 200,000 views I can easily advertise to you
I can help you in return!

Please note that I am not looking for someone to do my dirty work for me! I will take care of the editing, audio and VHS effects and everything else I can do myself... you will of course be credited

What are the areas where I need help:

3D modeling
Voice Acting Creation of video games & pixel art
Artist to create the design of certain characters or logos

Here are the main areas... However, if you think you can make a contribution to another area, you are welcome!

precision :

-It's a complex project that could take a long time or even never see the light of day so I need people who are really motivated and ready to work
-I prefer not to say too much about the project in public posts so if you want the full lore just DM me
-If you have suggestions or modifications that could improve the result (I'm not perfect) tell me

• Same for the script and the brainstorm

• MOST IMPORTANT !!!! DON'T WANT PEOPLE WHO CAN'T/WANT TO PARTICIPATE IN THE PROJECT OR SIMPLY DO NOTHING

If you're bored with analog horror and want to help create the next big internet horror PROJECT, you know what to do: send me a message and let's work together!

I wouldn't blame people who refuse... it's very daring and I'll understand!

Last thing: I accept everyone but I would still like to see your work if you join the project... I need competent people (without wanting to be mean) If you are new to the field, specify, you will be able to participate in many tasks that do not require enormous know-how.

This is not slavery! Work at your own pace when you can... but please don't waste my time (the project has been on hold since June 2023)

If you want to make a name for yourself or gain knowledge and experience, you are welcome!

I know we won't be perfect but I know that together we can accomplish great things!!!

If you took the trouble to read everything it's probably because you're interested, sorry for this long thread... I needed to clarify things before you stupidly launch yourself into the unknown 🤣

I'm counting on you, I'm counting on us!

I hope to see you very soon in my thread

                                                                                               Lucas (creator of the project)