In networking, there is a similar concept called "dyinggasp" in which a device will send a signal when power is lost. This can help the operator determine if a service is likely to be down due to a power failure or a signal interruption.
I have said time and time again, keep a copy of the QR code (or the text encoded within) before adding it to an authenticator app. You may find out too late that you cannot recover the keys. You can do this by simply taking a photo or screenshot of the QR code and storing it in a safe place.
Even better, avoid any MFA mechanism that relies on short codes with low entropy. Instead you could use U2F which uses a hardware token in which the key material is designed to be extremely difficult to extract, and requires physical access to the device to even attempt.
This is the nice thing about keeping it in Keepass XC. The seed is saved as an attribute in the database, you can easily add it to another app if needed.
I am glad I got to experience the internet before this. It seems sadly inevitable. What was once built by and for the people has been taken over by the interests of the rich and powerful.
In the UK one of the best ways to launder money is to open a barber shop. Most people pay cash and unless they are going to watch every shop to see how many customers go through there's simply no way to police it effectively. I have heard that the shop owner will get a commission on any laundered money.
Same in Chile. A while ago our version of FBI closed 12000 barber shops along the country under an investigation on money laundering. It's so obvious it's ridiculous. 20 barber shops in the same street (we don't have a barber district btw), many of them working 24/7.
The generators I worked with were just massive diesel engines the size of a tractor trailer each. This was pre-def, pre-cat requirements. When I would switch on multiple load banks at once I could get a small puff of soot as the engines revved up. Provided the load was not varying heavily they would at least run clean enough that one could not see or smell any exhaust. This was in the 2000 time frame. Mind you the load tests are not real-world realistic at all and this can be further mitigated using step-start programmable PDU's in the data-center. Companies that own data-centers usually have a lot of political pull with the cities due to all the assorted taxes they pay, direct and indirect revenue and employees they bring in.
Cat has since added options for hydrogen [1] but I have no idea how many people have bought them.
One of Traefik's shortcomings with ACME is that you can only use one api key per DNS provider. This is problematic if you want to restrict api keys to a domain, or use domains belonging to two different accounts. I hope Nginx will not have the same constraint.
How much of that would trickle down to the developers who worked on KHTML on which Chrome is based I wonder. They should feel pretty chuffed that their offspring has resulted in such a large valuation.
Yes you can still commit as a logical delineation of changes. And every commit is automatically a PR, folding multiple commits is possible but not the common workflow, they prefer just reviewing and approving each commit.
https://forgejo.org/