Interop standards for this like Open19 are not widely deployed and without interoperability it’s a dead
end since you need the hosting provider to give you the drop to your rack or cage. Hyperscalers I don’t know, but I’d guess they don’t deploy rack density that calls for liquid cooling yet.
Phone numbers have become the unique identifier used to build profiles of people and the providers can still claim “security” when they change it to pursue that revenue stream.
which is why you went with Delta and not Nocturna I would think? Deltas are fine in an otherwise noisy environment but they’re misery in say a bedroom at night.
If you tap into the address bar, start typing your search, type enough for it to be specific enough that autosuggest crap
clears, and “On this page” appears. Wildly undiscoverable in practice.
In a similar vein, I remember encountering a site where the frontend enforced basic complexity requirements ala “use at least one number and one symbol” but the system would silently drop all non-alphanumerics when it saved (presumably in some kind of failed conversion on the way into the backend DB). So setting a password like “foo_bar4!” would become “foobar4” which was surprising. What blew my mind though was when I figured out the stripped password worked to log in, which was how I eventually figured out what was happening, escaped the reset flow, and generated a compliant password.
similar, user-hostile behaviors I have found include:
- wifi network passwords are persisted through a system wipe and reinstall in recovery mode
- a phone home is required by an activation step during installation
- bluetooth is always re-enabled after an upgrade
in high scale stateless app services this approach is typically used to lower tail latency. two identical service instances will be sent the same request and whichever one returns faster “wins” which protects you from a bad instance or even one which happens to be heavily loaded.
I wasn’t in C++ style land but my recollection is that distilled experience would be backed up by extensive mailing list discussions. in case of contention the discussion might extend into case studies or other quantitative techniques atop google3. It’s difficult for me personally to describe the impact (outsized)of a super-resourced monorepo for this kind of thing. also as gp mentioned, it was sometimes possible to automate changes to comply with updated guidelines.