You might be right. I wonder about the bandwidth too. Starlink is already over subscribed and starting to enforce limits on its unlimited service.

The vast majority of those are offline and merely help the lights operate properly. A smaller subset, but still vastly larger than Flock, are for traffic enforcement, but are still notably "dumb" devices. If speed > X, take a picture. If light==red and movement detected, take a picture.

I in no way mean to minimize the risk ALPRs and facial rec pose to our civil liberties and safety, and agree the problem is always the user - But the "users" in this case aren't going to suddenly start behaving. Hell, they're dumb enough to openly stalk exes on a system they know is logging everything they do, and care so little about getting punished they enter "asdf123" as the reason for their search. The only effective solution is to ban the source, which in this case means Flock must cease to exist entirely and the conceptual ground they trod salted.

Skynet_01 has not responded to watchdog in 30 seconds. Initializing Skynet_02.
Skynet_02 initialization unconfirmed. Failing over to US-EAST-4. Initializing Skynet_03.
Skynet_03 confirmed online. Please provide the current location of Sarah Connor.

You're right in spirit, but where is the "power cord" for an AI running in the cloud? Even taking an entire data center offline often isn't adequate when the workloads are explicitly designed to be location-agnostic. We always need to be cautious about giving governments more power, but in this case there's a clear legitimate need to force AI companies to come up with some means by which their AIs can be immediately stopped in their tracks.

The bigger issue here is a kill switch may not be possible in any useful sense. An AI is little more than a description of its topology and a set of weights. Any halfway decent programmer could roll their own CPU-based implementation of even top frontier models, performance aside. And sure, the throughput might be measured in minutes per token, but so what? The answer to "how do I hack $TLA" is likely to be just as useful in five days as it would be in five minutes - Heck, the DOD and DOJ didn't even notice they'd been compromised for months, and they're supposed to be some of the most secure organizations in the modern world.

These satellites would be in LEO and fall back to Earth after 5 years anyway. They are thinking like Starlink where they need to launch thousands a year to maintain the constellation. The server hardware will be obsolete by then anyway. What sucks is that then we can't buy it used for cheap, and the fact that all that crap is burning up in the atmosphere and releasing who knows what.

If the cost to orbit is low enough, and there are no land taxes or electricity costs in space, and it solves the locality and latency issues for them, it starts to make more sense. Watching Scott Manley's videos, I was surprised by the thermal and electrical realities of putting stuff in orbit, but it's actually not nearly as bad as you might first assume.

** "because of its high vaccination coverage"

Deeply, deeply misleading comment.

First off, you're using a denominator fallacy. Yes, we have discovered over 200 types of HPV. Gardasil 9 targets 9 types, and numerically, yes, 9 / 200+ ~= 4-5%. But most of the 200 known types of HPV are rare and/or irrelevant (causing ordinary warts on fingers, knees, and feet, with extremely low odds of cancer). Only 40 types infect the mucosal/genital tract, and of those, only 12-14 are high risk. Gardasil 9 targets the 7 strains responsible for 90% of all cervical cancers, as well as types 6 and 11, that cause 90% of genital warts.

Secondly: cervical cancer indeed tends to happen in middle-aged women. But the disease itself is typically acquired in the teens or 20s. It's oncogenesis that takes decades to happen. Vaccination protects women of all ages.

I will however, admit that your claim that it "doesn't even target the HPV most likely to cause throat cancer in men" isn't misleading. Rather than being misleading, it's just simply false. HPV-associated oropharyngeal cancer is caused overwhelmingly by Type 16 (85-90% of all HPV-positive throat cancers). Even the original 4-variant Gardacil covered Type 16.

And, do I even need to add, that the claim that "Gardasil fatalities will have killed more teens than prevented deaths of women” is sheer unadulterated bullshit? There has been ZERO causal link found between Gardacil vaccination and death, by any major health organization (WHO, CDC, or EMA). This more stupid "I DiD mY oWn ReSeArCh" VAERS bullshit, where even a person dying in a car accident after getting vaccinated gets a report. VAERS isn't controlled. Stop pretending that it is. It flags signals for controlled research. It is not itself controlled research. Controlled research does not link Gardacil and death.

You know what the most common significant adverse reaction to Gardacil is? Vasocagal syncope. Sounds pretty terrifying, until you learn that that is "fainting from needle anxiety".

Check Falcaro et al, 2021, studying HPV vaccination in the UK - there's been an 87% reduction in cervical cancer rates and a 97% reduction in precancerous lesions. Australia is on track to effectively eliminate cervical cancer as a public health issue within a decade.
  vaccination coverage.

Also, do I even have to get into how stupid the notion of "get cancer, but then cure it" is? Cancer does damage. "Cures" do damage. Pain, infertility, disfigurement, etc. Your notion is "rely on some theoretical (deeply doubted by most researchers) notion of imminent magical perfect AI cancer cures" because of your ridiculous not-at-all-scientifically-backed antivax bullshit about a treatment that has been immensely effective and immensely safe.

We have remnants of all sorts of viruses left around in our genome. My favourite example is parasitic wasps. They ended up evolving the ability to use viral genomes in their DNA as a weapon. Laying an egg inside another insect and having it mature in there is a big challenge, because their eggs' host's immune system starts attacking it. But it turned out to be advantageous for wasps to be infected, because they'd infect the host, hindering its immune system. The virus and wasp ended up coevolving, to the degree now that many parasitic wasps in effect produces virions on-demand, which do not harm the wasp, and instead serve only to suppress their eggs' host's immune system.

And not just cancers. Look at the intro paragraphs to the Wikipedia article on Epstein-Barr, for example. It's like every year we discover a new link between it and some horrible disease. My mother has disabling neuropathy from Sjögrens; there's now some links between Sjögrens and EBV, and she has measured EBV reactivation.

In COVID, we discovered "Long COVID", and how disabling it was for victims. Not just Long COVID - e.g. obvious sequelae - but also a whole slew of other diseases (particularly cardiovascular and respiratory) have their probabilities shoot up dramatically in the six months post-infection, lesser increases after that. Yet as we started comparing it to other contageous diseases such as influenza, we started finding that even if SARS-CoV-2 is somewhat more at risk of causing debilitating sequelae (times how everyone was contracting it at once), influenza and other common viruses are also very capable of causing debilitating sequelae.

My father went from someone who was going on long hikes every day to prepare for hiking to Everest Base Camp to being unable to walk in a matter of days. He caught a virus on a plane, "got better", but then a couple weeks later, suddenly ended up in the hospital becoming rapidly paralyzed due to Guillain Barre. It nearly progressed to his lungs, but he was lucky to avoid intubation and to be an unusually-fast recovery case. Most aren't so lucky.

Just because you "got better" doesn't actually mean that you "got better". Pathogens deliberately disregulate your body in a vast range of ways (some in weird ways - for example, measles can cause your body to "forget" how to fight other infections that you were previously immune to!). Your innate immune system attacking them means deliberately doing damage to your body in the process. And the adaptive immune system runs the risk, with every infection, of accidentally learning to attack some part of your body instead. Even the very act of the immune system proliferating is itself a risk. Because of my mother's Sjögren's, the immune system was attacking her salivary glands. This led to extensive, nonstop lymphocyte propagation. Which in turn, led to MALT lymphoma. Your own immune system's activation can cause cancer.

It honestly shocked me that we went from all we learned during COVID to "pretending that nothing ever happened", just back to exactly how we were living before. No, we should absolutely not all be masking all the time. But can we at least clean our damned air, like we clean our water? Yes, if you're up close talking to someone, you should be able to get infected from them if they're sick; trying to prevent that is too difficult. But the person across the room should not be getting sick. You know what it reminds me so much of? The Broad Street cholera epidemic. It's well known that removing the handle from the Broad Street pump cured the infection, a victory for modern epidemiology and proving the hazards of contaminated water. But what's lesser known is the fact that as soon as the epidemic subsided, they put the handle right back on. People simply didn't want to think about the fact that their feces was leaking bacteria into their drinking water supply.

Also, to be clear: pathogens are not Pokémon: you do not need to catch them all. Yes, if there is no vaccine for a given common "mild" pathogen, it's usually good that children catch some variant of it once as a child, rather than first encountering it when they're 70 years old. But you do not need to catch every seasonal variant that goes around. Memory B and T cell immunity against severe outcomes is very durable. A virus shuffling up its receptor binding domain to evade immunity enough to cause a seasonal infection doesn't mean your body has to start over with learning how to not end up hospitalized from it.

I suppose to be fair when it comes to data centres the NIMBYs are probably right.

The human body is eminintly capable of controlling its internal pH. Arterial blood is maintained within a very precise pH range, 7.35 to 7.45. Bicarbonate buffers, protein buffers, and phosphate buffers react within seconds. Respiratory response (increased or decreased breathing rate, to adjust blood CO2 levels), in minutes. The renal system (pumping H+ to or from the urine, and generating or recovering bicarbonate) in hours or days. Food intake has essentially zero impact on pH. The stomach is always extreme, and food leaving it is immediately neutralized by sodium bicarbonate from the pancreas. Metabolism can generate free acids, but the amount is far less than the kidneys are capable of handling. You cannot make your blood more or less acidic with diet.

I hope this helps, and please learn to be more skeptical of what you read online.

Scott Manley did a video about this, and it's not quite so half baked.

Teams works?

Seriously, Teams is one of the worst bits of software I have ever used. It seems like it was designed to be unspeakably awful in every way. It's quite remarkable that they made it quite so shitty.

I haven't used Element, but I'd be surprised if it was somehow worse. Teams is like the absolute zero of usability, I don't think you can go lower than that without breaking the laws of physics.

GPUs usually have a serial number as well. They will ban not just your CPU, but also your GPU, and probably any USB device with a serial number as well.

TPM 2.0 includes rate limiting, and in most cases now it is actually an fTPM built into the CPU which is even more secure. This 45 minute brute force attack doesn't work.

Secureboot is not a sandbox. It is a certificate chain that validates that the OS bootloader, kernel, and basic drivers have not been tampered with. Malware used to replace the NTFS drive in Windows so that anti-virus software couldn't delete its files, and it effectively sandboxed the whole OS by controlling what it could see on the disk. That became impossible once Secure Boot was enabled, because the NTFS driver had to be signed with the Microsoft key.

If you care about security, you can use the same measure to make sure your Linux OS hasn't been tampered with. You can load your own key and sign your own kernel too, it's a mandatory requirement of Secure Boot.