360
submitted 2 months ago* (last edited 2 months ago) by FlyingSquid@lemmy.world to c/tenforward@lemmy.world

Memory Alpha's riot timeline:

Early in the morning of September 1st, a fight between a guard and a dim sparked a riot, wherein the ghosts led by B.C. attacked the Sanctuary guards and quickly captured the Sanctuary Processing Center as well as the rest of the district. Armed with the weapons of the overpowered guards, the ghosts took six center employees hostage, including Vin, Calvera, and Lee. They were joined by "Gabriel Bell" and Michael Webb, who acted as the voice and face of the riot while dealing with police negotiator Detective Preston.

Chris Brynner, who owned Brynner Information Systems (which operated Channel 90 on the net), was convinced by Dax to break the law and to reconnect the Processing Center after the police cut it off. Reconnected on September 2nd, many Sanctuary residents (such as Henry Garcia) were able to tell their stories of imprisonment to the outside world. As a result, the American public became aware of the great injustice that had been hidden from them and further riots broke out in Sanctuaries across the US.

Despite protests from Detective Preston, the governor of California ordered National Guardsmen to retake the Sanctuary by force on September 3rd at 0500 hours. In the melee, hundreds of Sanctuary residents were killed, including B.C. and Michael Webb. "Gabriel Bell" was shot, protecting Vin and the other hostages (all of whom remained unharmed).

https://memory-alpha.fandom.com/wiki/Bell_Riots

you are viewing a single comment's thread
view the rest of the comments
[-] mkwt@lemmy.world 19 points 2 months ago

Every computer on TOS fits into room sized cabinets and has rows of blinkenlights on the front panel. This is what computers looked like when the show aired.

The blinkenlights are there to report the contents of the registers in binary code. This helps a lot when you are debugging by single-stepping the entire computer one instruction at a time. Any programmer today would think this is incredibly quaint.

The show completely missed the microcomputer revolution that was brewing in the real space program at the same time they were on the air. There was a period where Apollo Guidance Computer was consuming nearly the entire national supply of integrated circuits.

[-] humorlessrepost@lemmy.world 13 points 2 months ago

The blinkenlights are there to report the contents of the registers in binary code. This helps a lot when you are debugging by single-stepping the entire computer one instruction at a time.

And now we have redstone torches for this.

[-] MajorHavoc@programming.dev 12 points 2 months ago* (last edited 2 months ago)

The blinkenlights are there to report the contents of the registers in binary code...Any programmer today would think this is incredibly quaint.

True!

...

I still want one, though. They just look so cool.

[-] marcos@lemmy.world 3 points 2 months ago

by the time DS9 was aired, there were very informative blinkenlights on modems, and the Be (or was it Bee?) had a set of averaged ones measuring things like CPU and memory utilization.

Up to this day computers still come with one for disk IO. And it's still useful.

[-] grillgamesh0028@lemmy.world 2 points 2 months ago

only if you have one disk... then the light stops being useful, because you don't know which disk is I/O'ing, and needed to debig further...

[-] echodot@feddit.uk 3 points 2 months ago

I suppose the modern equivalent would be looking at machine code with a hex editor.

[-] MajorHavoc@programming.dev 1 points 2 months ago

Ooh. That's an interesting thought!

Maybe with an external pixel display.

[-] Stampela@startrek.website 8 points 2 months ago

Any programmer today would think this is incredibly quaint.

Like using a keyboard :D

this post was submitted on 01 Sep 2024
360 points (99.2% liked)

TenForward: Where Every Vulcan Knows Your Name

3693 readers
687 users here now

/c/TenFoward: Your home-away-from-home for all things Star Trek!

Re-route power to the shields, emit a tachyon pulse through the deflector, and post all the nonsense you want. Within reason of course.

~ 1. No bigotry or fascism. This is a Star Trek community. Hating someone off of their race, culture, creed, sexuality, or identity is not remotely acceptable, neither is supporting people who actively want to kill those groups. Mistakes can happen but do your best to respect others.

~ 2. Keep it civil. Disagreements will happen both on lore and preferences. That's okay! Just don't let it make you forget that the person you are talking to is also a person.

~ 3. Use spoiler tags. This applies to any episodes that have dropped within 3 months prior of your posting. After that it's free game.

~ 4. Keep it Trek related. This one is kind of a gimme but keep as on topic as possible.

~ 5. Keep posts to a limit. We all love Star Trek stuff but 3-4 posts in an hour is plenty enough.

~ 6. Try to not repost. Mistakes happen, we get it! But try to not repost anything from within the past 1-2 months.

~ 7. No General AI Art. Posts of simple AI art do not 'inspire jamaharon' and fuck over our artist friends.

Fun will now commence.


Sister Communities:

!startrek@lemmy.world

!memes@lemmy.world

!tumblr@lemmy.world

!lemmyshitpost@lemmy.world

Want your community to be added to the sidebar? Just ask one of our mods!


Honorary Badbitch:

@jawa21@startrek.website for realizing that the line used to be "want to be added to the sidebar?" and capitalized on it. Congratulations and welcome to the sidebar. Stamets is both ashamed and proud.


Creator Resources:

Looking for a Star Trek screencap? (TrekCore)

Looking for the right Star Trek typeface/font for your meme? (Thank you @kellyaster for putting this together!)


founded 10 months ago
MODERATORS