Ace: aceofspadeshq at gee mail.com
Buck: buck.throckmorton at protonmail.com
CBD: cbd at cutjibnewsletter.com
joe mannix: mannix2024 at proton.me
MisHum: petmorons at gee mail.com
J.J. Sefton: sefton at cutjibnewsletter.com
Chavez the Hugo 2020
Ibguy 2020
Rickl 2019
Joffen 2014
AoSHQ Writers Group
A site for members of the Horde to post their stories seeking beta readers, editing help, brainstorming, and story ideas. Also to share links to potential publishing outlets, writing help sites, and videos posting tips to get published.
Contact OrangeEnt for info: maildrop62 at proton dot me
Also if you're trying to write code for industrial control systems.
But if you're a citizen of Taiwan or Tibet or a member of the Falun Gong, and you tell it you're writing a monitoring system for a nuclear reactor, it's going to have a field day.
(Go away, Bing. Yes, I did search for an non-paywalled version that WaPo article, but now just go away.)
Uh. I'm typing this on an Asus laptop less than four years old. Not sure if it's considered a gaming laptop as it has no dedicated GPU. The same bug does affect ROG, TUF, and Zephyrus models, and symptoms were reported starting in 2021.
Anyway, on a regular schedule, every 30, 45, or 60 seconds depending on model, an interrupt fires off a BIOS ACPI call that in turn includes a sleep() call, something that would get a programmer shot, hung, drawn, and quartered back in the day. That makes everything stall for 13 milliseconds or so - not a lot of time, but if you're gaming at 80fps that's one frame just gone.
Oh, and sometimes it makes the entire system blue screen.
At no point during testing did the monitor make the entire system blue screen. I like the warning that's it's not a super-wide gamut monitor, since it "only" covers 100% of DCI-P3.