Their math seems off. I really don't see how you get to 97% renewable when the state was burning natural gas to generate 2.8 GW of non-renewable power and had about 1.1 GW of nuclear at the time. There might be some funny math here where they assign all of the "dirty" power generated in the state to exports and can claim that that California is running on renewable power.
If this is a reward or payment for services, it is taxed as regular income, not as an investment. The FICA tax (SS/Medicare) will either be payed by the payer (shown on W-2) or the payee as self-employment tax when filing a Schedule C.
How do you handle backup and restore on a system like this? If the snapshots are at the OS level, and there is cross-app commingling of data objects, how can you restore the state of a particular application or object (formerly "file") without breaking everything? How do I restore a single document or a single contact in my address book?
Zero Trust is such a terrible name. What they really mean is less trust in network location, static firewalls, and site-to-site VPNs, and much more trust in the cryptography behind TLS, identity systems, and how they interact with applications.
I found the Radicale documentation [1] sufficient for setup, and it really hasn't needed much in the way of maintenance. I also enabled the awesome Git integration so that every client-side contact/vCard change becomes a server-side git commit to my contacts repo. Now my birthday greeting script can just "git pull" to get the latest contact data.
"In addition, the Android smartphone operating system (from version 4.0 onwards and possibly earlier; we don't know for sure when the change happened) uses GPSD to monitor the phone's on-board GPS, so every location-aware Android app is indirectly a GPSD client."
I noticed that my LeoNTP [1] GPS time server is counting down to the non-existent leap second near the end of November. I hope that it doesn't advertise this as an upcoming leap second to downstream NTP clients just before the event.
Using crudely produced industrial oxygen for medical purposes (human breathing) is dangerous. Even with the warnings included above, people will not fully understand the risks and consequences of using a DIY oxygen generator, including long-term lung damage.
Yes, I was offered a manual export of my domain list. By "dodged", I mean that the request for an export feature in the same ticket was ignored, sort of a passive-aggressive "wontfix". I would have just scraped the HTML table, but at the time it just didn't work in Firefox/Chrome, and there was a weird interaction between filtering and showing more than 25 domains on a page. This might be fixed now, but was very frustrating at the time. I felt like support ignored all of that and just offered a manual export, without understanding how much more time it takes for me to write up a ticket (and wait for response) vs implementing a proper export feature.
Export a zone file? Namecheap can't even export a text or CSV file of all of my domains and their expiration dates. This is a long-standing open issue that Namecheap support has dodged several times with us. I'm still a customer right now, but I'm looking for another registrar.
California declared a Stage 2 Emergency at 15:30 PDT today which begins curtailment of interruptible loads, a less drastic form of load shedding. A Stage 3 Emergency begins to affect firm load using rotating outages.
Windows 10 is constantly writing to the user profile directory, including the registry hives, temp/cache folders, and telemetry. Syncing the entire user profile directory turns into an never-ending battle of excludes for files, some of which exist only for seconds. Instead, only include the folders (Documents, Music, etc.) that you need to sync, and you will be much happier.
Maybe, but most ISPs are lazy/cheap and can't do a full-take packet capture of all customers data at the same time. The ones that I have seen usually have a custom or logging DNS server that associates each domain request with a customer account. So yes, in many cases, changing your DNS server is enough to avoid the larger DNS sniffing operations. You should also use an IP check query to make sure that you are really using the DNS server you think, and that you're not being DNATed back to your ISP's DNS server.
I gave NixOS a try recently, and generally liked it. I could get over the arcane packaging language and hit-or-miss documentation. The red flag for me was the inattention to software freedom. Most other distros like Debian or Fedora have source packages or SRPMs that include everything needed to rebuild a package from scratch. Nix pushes binary packages, and even stores them in S3, but with no matching source packages that I could find. They tout reproducible builds, but really haven't considered to how to deal with the "disapearing sources" problem, including vanishing git repositories. I grabbed some URLs that pointed to sources in the old Nix Tarball Cache and they all returned 404. Nix has no longer term plan to preserve package sources.
To me, it seems odd that government would have a monopoly on anything in health care. Non-profits can play a very valuable role in exposing inefficiencies in large bureaucracies.