Live data from Hacker News

Cartoon Network channel errors (1995 – 2025)

cnas.fandom.com

31–35 of 35 posts

Re: Cartoon Network channel errors (1995 – 2025)

#31

I worked for 10 years in broadcast, as a director, IT support, and an Engineer. I love picking errors out of any broadcast, especially with what I know now. Seeing things like this and other documented cases of broadcast errors always make me happy because I know how hard it is sometimes to be in that line of work and how easy it is to just make little blips here and there. Making errors is how I learned to never get…

Broadcast errors are not only interesting to watch, they also made TV feel human and alive. Nowadays, watching most cable channels feels like staring at the output of a VLC playlist with ten movies on loop.

Re: Cartoon Network channel errors (1995 – 2025)

#32
post #15

Earlier quoted context omitted.

As a kid i remember being fascinated by technical difficulties screens, EAS tests, etc. Generally anything that unwittingly revealed the technical aspects of running a broadcast station. This was before we really knew how to use the internet even, so for many years, I'd wonder what a screen saying "No Access Card" or "Coriogen Eclipse" meant. When we learned about Google, it was suddenly a very educational experience…

On Toronto's public transportation, TTC, occasionally the upcoming bus stop ticker would flash diagnostic information(?) and "64K RAM" instead of the upcoming stop name. Doesn't seem like there's a wiki page about these faults yet.

Actually, the Canadian government suppresses it because they just really don’t want anyone to know how to get to 64K RAM, ON.

Re: Cartoon Network channel errors (1995 – 2025)

#33

I completely understand the kind of mind that would catalog such a thing. This wouldn't be my thing to catalog, but I'm glad somebody did it.

My favorite niche catalog is this list of chairs of star trek: https://www.ex-astris-scientia.org/database/chairs-trek.htm

Re: Cartoon Network channel errors (1995 – 2025)

#34
post #15

Earlier quoted context omitted.

As a kid i remember being fascinated by technical difficulties screens, EAS tests, etc. Generally anything that unwittingly revealed the technical aspects of running a broadcast station. This was before we really knew how to use the internet even, so for many years, I'd wonder what a screen saying "No Access Card" or "Coriogen Eclipse" meant. When we learned about Google, it was suddenly a very educational experience…

On Toronto's public transportation, TTC, occasionally the upcoming bus stop ticker would flash diagnostic information(?) and "64K RAM" instead of the upcoming stop name. Doesn't seem like there's a wiki page about these faults yet.

What would they be running them on that has so little memory these days? Esp32?
Post reply on HN