We used deterministic game play to implement multiplayer on the GB Color port of Vigilante 8.
The GBC Link Cable would pass 1 byte in each direction at the same time. It's a pair of shift registers filling each other up across the cable.
The game was locked to the GBC's frame rate. There was a lot work to update the screen that had to happen in each (effectively) V-Blank and if it was missed the smooth scrolling stuttered.
At multiplayer startup we passed our seed. To run it looked like this:
On frame A it reads the controls, and packs them into a byte and puts that in the transfer buffer. The transfer occurs while it renders frame B. At the start of frame C it has the local controls encoded in the byte sent on frame A and it has the other side's controls in the byte received in frame B.
It applies the controls to the game state and renders frame C. Local and remote controls are applied with one frame delay.
There was no frame delay of the controls for local play so if you ever lost in multi-player feel free to blame lag and me specifically if you need to.
The Scotland link in the grandparent post is to a picture of 2 people, 1 white, 1 black. 1 is not large numbers.
Look, Gemini is clearly doing some weird stuff. But going all "look what crazy thing it did" for this specific image is bullshit. Maybe it's a misunderstanding of Scotland in specific and the prevalence of black people in history in general, in which case in needs to be gently corrected.
But also misinterpretations of what the history is. As I write this there's someone laughing at an image of black people in Scotland in the 1800s[1].
Sure, there's a discussion that can be had about a generic request generating an image of a black Nazi. The thing is, to me, complaining about a historically correct example is a good argument for why this kind of thing can be important.
"It’s often assumed that African people arrived in Scotland in the 18th century, or even later. But in fact Africans were resident in Scotland much earlier, and in the early 16th century they were high-status members of the royal retinue."
In response to top of thread, retinal detachment does usually start with new floaters.
My first floater came with an unusually timed cluster headache ( like a migraine but usually with predictable timing ) so I had accompanying visual auras. Because I didn’t recognize it as a cluster I described it to the on call eye doc as new floaters and sparkles. That got me an emergency trip to optical ER and a slightly disappointed surgeon.
I intentionally start searches on Bing and have it set as default. But half of the time that I type anything to it it's because the browser didn't autocomplete like I expected.
So when I do want to see goggles results for the same thing I type "google", and a lot of the time the browser doesn't autocomplete to google.com before I hit return. So whoops, I just searched for "google".
> So how can we handle this case safely? There are a few ways I can think of.
strdup:
> The strdup() function returns a pointer to a new string which is a duplicate of the string s. Memory for the new string is obtained with malloc(3), and can be freed with free(3).
Here's a fun example. ASL allows, maybe even requires, negation after the statement. An interpreter friend of mine was interpreting Wayne's World in a mixed crowd. The whole "<statement>... NOT!" joke gets laughs from the hearing audience and the Deaf audience doesn't understand why.