sacnoradhq

There's a lack of nosological classification of meaningful sub-types of depression and their specific dysfunctions. It's currently scatter-gun, medieval treatments without bothering to measure or understand the systems affected.

From the comments as of writing, few read between the lines of this sloppy reporting: it's to standardize cloud-desktop apps for Amazon's internal use.

Meta, for example, consolidated to Workplace + Google, away from Dropbox, Microsoft, Apple, and others. They use AWS and Azure for some 50k desktops on demand and a few servers, but it mostly deploys to its own metal because it's way, way cheaper than AWS in most use-cases.

The city of Austin is floating legislation to allow up to 3 housing units per property including campers, RVs, and tiny homes.

Find me one contemporary example (ANSI C) with a disassembled screenshot.

This is writing sizeof(char) (== 1 almost everywhere) zero to address zero. It is not using a NULL macro or other predefined symbol.

In the real world, this would generally write a byte to address 0000:0000, leading to UB because it would fuck up the divide-by-zero IV.

PS: I used Borland C++ 3.1, Microsoft C++ 3.x and 4.5x, Watcom, and early GNU.

This statement would be technically legal on its own in x86 real mode if the compiler didn't do null pointer checks. However it would set the divide-by-zero IRQ handler to itself 0000:0000, and when the next division by zero happened, the machine run into UB (likely a reset or halt) because it would jump there, do 4x ADD byte ptr [BX + SI], AL (or ADD byte ptr [EAX], AL) followed by running the remaining interrupt vectors as instructions.

Post-ACID for stateful services -> DHC: Durability*, hygiene**, and confidentiality***.

* Superset of bare metal recovery readiness, proven backups, monitoring, availability, and warm storage integrity.

** Superset of consistency, isolation, referential integrity, and data hygiene.

*** Superset of authenticated, G4+ FHE, and/or zero-knowledge encryption at rest and in-flight, elimination of side-channels, least privilege access control of metadata and data, removing plaintext paths, reducing privacy-liability metadata, and eliminating bleed-through of internal metadata externally.

If you're not building a PaaS while running stuff, you should either rent or build a platform because having a reusable platform enables scalability and manageability.

And if you have 750+ employees, you better have an (endpoint) client platform too to minify development, non-development, and support variables.

The Target here in ATX next to downtown hired 2 ex-PMC's in full plate carriers. (APD's call backlog for nonviolent reports runs 36- to 48-hours, so it might as well be never. A private person must then either be equipped to defend themselves, cease venturing in public, or move because the police may be too busy or too unconcerned elsewhere.)

In this time period, there are many people who are eager to cause mass suffering, murder, sabotage, and dissolution of civilization. With advances in technological organization, there is an increasing potential for coordinated autonomous attacks against infrastructure, essential services, groups, and individual persons in multiple theaters concurrently.

It would be neigh impossible to defend against 100k flying drones wielding cow-knockers programmed to swarm, loiter, break windows, and kill humans. Such could be dispensed by purpose-built intermodal containers, moved by ordinary freight logistics to attack multiple population centers in a simultaneous attack.

Code and binaries are shipped to 10's of millions of servers by internal configuration management tools. Take Meta, Google, or Microsoft and turn them into AI exploit and worm fabrication at scale. While it may happen for only an hour or 2, there's quite a bit that could happen and the possibility of advanced persistent threats is real.

Target a demographic to alter their filter bubble to persuade them to engage in mass-casualty terrorism.

Hate group applies AI to create a designer virus lethal to particular a demographic.

Subtly disable water treatment facilities with an autonomous, stuxnet-like attack.

The median population center of America is around Indiana, so the average delivery charge will be ~3k. The total delivered cost with tax will be about 30k.

Also, there is a threat of municipalities, including states, suing the manufacturer for selling manufactured homes that aren't up to code. While the cases may lack standing or merit, they have lawyers who can make it very expensive to stay in business regardless.

My '85 VW Westfalia poptop camper is still cheaper than that by acquisition price.

(Not so cheap after solar, remodeling, restoration, and engine swap.)

That's immediately what I thought. Plus, there is no absolutely no way this will withstand a 70 mph windstorm while you can fold a travel trailer down in a reasonable amount of time. It's not a secure, real, permanent shelter that conforms to building codes: it's an illusionary shortcut.

Compost toilets are the easy part.