I don't live in Paris, so I don't know what is best. I'm sure that some people who live there would prefer a Costco. I'm not catholic (like many people in France) so while I appreciate the architecture I otherwise have no particular use for that building - I'm more likely to visit it as a foreigner (as part of some tour) than if I was a local (where I could anytime, but in practice would likely always find something else to do).
> But the attacker website can itself hook the XHR made from inside the no-fetch-if hook to extract the random extension UUID.
Oh great. I recently learned[0] that some Firefox extensions can be tricked into leaking their install-unique UUID, which can then be used as a tracking identifier. Today I learn that any site can get my unique uBO UUID by hooking fetch('/adsbygoogle.js').
Chromium used static IDs for web accessible resources until very recently, and even now it's only optional for extensions to use dynamic IDs. This page enumerates extensions with non-dynamic URLs in Chromium: https://browserleaks.com/chrome
Another important benefit is that transfers between cards flow across the switch and bypass the CPU, that ain't nothing. At least for the AMD cards. Nvidia firmware refuses nach
Nobody should have sex with people whose livelihoods they have control over, it's not that crazy and its not a "men aren't allowed to flirt anymore" thing.
Does this library model lose chromium's process sandbox features? A quick search tells me "Electron applications heavily benefit from Chromium’s sandboxing features, and they have become a foundational pillar of modern Electron security." It doesn't immediately sound like your approach maintains that security.
That's the brand confusion born of appropriating Google's Pixel mark and the reason why trademark protection exists.
If you make a hamburger seasoning blend that approximates the taste of McDonald's and call it "McDonald's burger flavor", you're going to have a bad time with the legal system. I don't expect this to fly either.
You said, "I first thought that it was a replacement OS for Google Pixel phone", which was my experience as well. I was arguing that confusion began with the branding. It could be said that better copy on the landing page could offset it, but it's still a reasonable interpretation of the name 'PixelOS'.
reply