I think either end is good. Web apps that I can use in my existing browser session are fine, and so are native apps. It's specifically the worst-of-both-worlds middle ground that is Electron that I want to see go away.
That would be a reasonable explanation if most of the campsites had people charging EVs at their max individual current, but it sounded like just one did.
The entire reason we have so many different types of receptacles is so to keep you from plugging in something that the circuit can't handle. They shouldn't be giving people 14-50's if they don't have 50A peak and 40A continuous available. (There is a code exception to only allow 40A peak/32A continuous to a 14-50, but that's all most portable EV chargers draw anyway, so I doubt it even met that. And TT-30 offers no such exception at all.)
If pulling 24 amps through a TT-30 or 40 amps through a 14-50 trips a breaker, then it's the host's fault for the campground having a shoddy electrical system, not the truck driver's fault.
You use your phone 99.9% of the time, and have a backup card the exact same form factor as a credit card, that you keep with your credit cards and driver's license, for the 0.1% of the time you can't use your phone.
And if you opt for the fob, then you don't need to carry a backup card at all, because even when its battery is dead, you can tap it against the reader just like you would with the card.
You're mixing up two different things. One is the Bluetooth key that needs your phone to be close to the car and doesn't go over the Internet. That's what's free forever. The part that goes over the Internet is free for the first 8 years and is then $100/yr thereafter. Also, why do you use the word "unrestricted"?
Tesla is all the way on the easy and cheap end of the scale. It's $40 for two new key cards or $175 for a new key fob, and as long as you don't lose all of your existing keys at once, you can program new ones and deactivate lost ones yourself in about a minute with no extra tools or software. And using their phone app as a Bluetooth key is free forever.
> A flat cert.pem file (or similar) can't say "distrust this intermediate".
Why does that matter in this case? Can't this be fully mitigated with next to no collateral damage just by removing the trusted roots that signed them?
The fact that GrapheneOS digitally signs their releases doesn't make them not open source. This is indeed a bad situation, but the badness is 100% the fault of Google for having a hardware attestation "feature".
There was nothing deceptive about my statement. Every car has an obvious front door release. There are no cars where the non-obvious back door release is the only way out without electricity.
Where is it required? If the answer is "nowhere before, but now that passkeys support it, places are starting to", then that's an argument that it's bad, not that it's good. And being able to "use the same passkey spec as everyone else without having to invent their own thing" is bad. I want them to all have to invent their own, so that most of them will make mistakes that let the attestation be bypassed and freedom be restored.
The part unique to passkeys is that the ability to disallow use is already sitting dormant everywhere and literally just needs websites to flip a switch. The other things you mentioned would all take effort for websites to set up.
Indeed, there's nothing wrong with, e.g., passkeys backed by KeePassXC. The problem is specifically that passkeys support attestation, so eventually no websites that you need to use will support passkeys from those pieces of software.
IMO, Chrome not having any equivalent to Firefox's network.IDN_show_punycode is a major security risk. There's no reason English speaking users should ever be exposed to this attack surface at all.
Why does the title of this submission say "Dual License"? The linked page doesn't use that term anywhere, and it's also not an accurate description of what this change is.
As long as they're not mandating backdoors or weaknesses in things, banning end-to-end encryption, or anything like that, to make wiretapping and surveillance easier, I think it's compatible.
I have no issue with the people behind projects speaking politically on whatever they want, if they do so with their own personal voice. My issue is specifically with them doing so with the voice of the project.
Projects should only be political in their own field. For example, the FSF should be political in copyright and patent matters, but not military or entitlement spending matters.
The peak throughput does result in an overall monthly limit though. For a house with a 200A main breaker, that effectively limits your electric bill to $7,000/month, which is very reasonable compared to the tens of thousands of dollars in a single day that a lot of cloud billing disasters end up costing.