This is nonsense, the vast majority of critical CVEs are trivial to fix once you spot them. It's very rare that you have something like spectre where the solution is non-obvious: most of them are shit like "delete a `free`" or "put the `goto fail` in braces".
But what's the alternative for the trademarks that are truly universally known? Does it serve the public for me to be able to sell unauthorized Coca-Cola brand products, or more likely, the trademark owner selling a token item in each category to maintain the right to prevent others from using it?
> Refunding is one possible remediation, see section 32 (cancellation) and section 26 (The consumer's rights in the event of defects). That option cancels the purchase contract, meaning you as the consumer give the item back, while the seller gives you the money you paid for the item.
Only if the manufacturer fails to fix it per section 31: "If the defect is not rectified and no redelivery takes place pursuant to sections 29 and 30"
I don't understand how this functions in practice: if business A sells a widget to reseller B who sells it to reseller C who sells it to the customer, there's multiple layers of markup. How can the original manufacturer be expected to refund the purchase price?
Reading the law, it does not say that the consumer is entitled to a refund.
Then why only have one human bookkeeper? Surely two would be better, since you can compare their results. But then, perhaps you should hire three, so you can figure out which one is right.
The board game has extensive rules on mech design, but for weapons, it's just wherever they'll fit. Some of the built-in hardware has fixed locations: cockpit, life support, sensors go in the head; engines go in the center torso (with light and xtralight fusion engines spilling out into the side torsos as well), arm and hand actuators go in the arms, and hip, leg, and foot actuators go in the legs. You can see this in the critical slot section in a record sheet: https://i.redd.it/jt3p2f1v14gf1.jpeg
This one definitely deviates from tabletop: pretty much everything except the smallest weapons have an integral tonnage, and the weapons themselves don't line up directly with their tabletop versions.
The newer games tend to be absolutely consistent with the mech design rules in terms of what weapons are available, and their weights and sizes, such that board game designs are legal in the game (and usually the state you get the mechs in before you customize them), and customized mechs are legal board game designs. They tend to limit the customization by doing things like having mechs have predefined hardpoints that limit what types/sizes of guns can go where, because otherwise you just end up with every mech being identical, with maximum armor and the rest of the tonnage being spent on whatever happens to be the most optimal weapon.
The fact that the password is "rzadmin" makes it a lot more likely that this is just run of the mill stupidity, and not something more nefarious: you'd want a backdoor that isn't blindingly obvious and usable by the CIA.
They passed a tax on basically just Amazon in 2018 and there were rumblings of Amazon leaving the city for Bellevue/Redmond. The city council repealed it within a month and things quieted down, but then COVID happened, they passed basically the same tax again, and this time it stuck. Since then, Amazon's been slowly leaving Seattle for the eastside by moving employees as their building leases expire: https://www.seattletimes.com/business/amazon/amazon-no-longe...
> AOSP made it increasingly difficult to contribute without being an Android partner and it's nearly impossible now.
Yes, by "upstream", I mean "upstream Android".
> Google didn't invent MTE or memory tagging.
Sure, they didn't invent memory tagging (SPARC ADI was an implementation from a decade ago, and I'd bet IBM had an implementation of something similar in like the 70s, judging by the rest of ISA innovations in the last decade), but they definitely invented the instantiation of it in ARM. Pretty much everything aside from instruction encoding for MTE was specified in a doc sent by Google to ARM in response to ARM telling Google something along the lines of "the entirety of our efforts in the security space are going to be spent on something that you're not going to see any benefit from within the next decade: CHERI aka Morello aka Arran".
> They are "permitted" to access to Google Play Services because their work hardening Android currently benefits Google.
Very little in GrapheneOS has gone back upstream post-Copperhead.
> Once Google feels like there is sufficient stability and compatibility with hardened memory allocator and tagged memory (and when they can get Qualcomm to support it across their range), they will make harder, until impossible, for Graphene.
What are you talking about? Google doesn't use hardened_malloc, and they literally invented MTE.
