Ace: aceofspadeshq at gee mail.com
Buck: buck.throckmorton at protonmail.com
CBD: cbd at cutjibnewsletter.com
Doof: doof2112 at proton.me
joe mannix: mannix2024 at proton.me
MisHum: petmorons at gee mail.com
J.J. Sefton: sefton at cutjibnewsletter.com
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
First, a Windows bug introduced in July that causes lock contention and eventually causes the machine itself to freeze, that they didn't find sooner because nobody in their right mind uses Windows as a server.
Second, a routine failover from the secondary network gateway to the primary one.
Third, 14% of the gateway capacity was already down due to an unrelated mishap.
This is why the problem took so long to fix: The underlying bug had already been deployed four months ago and had been waiting for its moment ever since, so rolling back recent changes and rebooting left behind systems that promptly failed again.
Which is the same experience everyone has with Windows.