The security boundary on the OS is the user of the process. If you run the malware under the same user as the key, than yes of course it has access. But in production you don't run software under the same user, and on the developer machine you wouldn't put the production key in the user keychain.
Who signs an "app" when I download it from Homebrew?
If all Homebrew "apps" are the same key then accepting a keyring notification on one app is a lost cause at it would allows things vulnerable to RCE to read/write everything?
I think you're assuming an ideal world where there's no information asymmetry, all the market participants receive and understand all the information and the risks, and clients could realistically move to an alternative platform that provably handles things better.
There's no custom of tipping that much at any of these places, but I feel cheap just clicking the lowest (no tip) of 4 options. Maybe all the time I've lived in the US plays a role here but it seems like it might just be the decoy effect [1] applied to tipping. It will be interesting to see if consumers see this as a dark pattern and push back.
In a security sensitive context, a parser should return an error on a duplicate key regardless what common parsers do and what the RFC fails to specify.
Implicitly, that means no security software dealing with json should be written in Go, Javascript, ruby, python, etc (where practically everyone uses json parsers that silently ignore duplicate keys)
Plenty of languages do have common json libraries w/ duplicate key errors, like haskell (aeson), rust (serde_json), java (gson, org.json, probably others), so there's plenty of good choices.
So yeah, correct parse result is '400 bad request'
And binary protocols, with index based implicit keys are and byte length prepended to variable length fields. Those are the gold standard (see ip and tcp headers.)
They also have 2% ev marketshare in China, because its still an expensive and complex feature that has downsides that the previous comment mentioned. Like these high energy batteries are dangerous as the can burn quite spectacularly, so I personally would not want to take and remove one from my car every charge hen I can wait a few minutes at a regular charging station that is much more common than a replacing station.
I think swappable batteries may be a more practical solution for heavy trucks rather than cars. They have the advantage that they are already built to carry heavy things loaded by forklift, unlike cars.
I agree, but there are aggressive subsidies around electric vehicles and general graft. Similar things happen in most countries but in dictatorships things can go to absurd levels when it aligns with the current policy.
This does mean entering your keyring password a lot.
https://en.wikipedia.org/wiki/GNOME_Keyring