399 karma · joined May 13, 2016
He's arguing that if he gets reelected then the investigation doesn't matter. The other parties are arguing it's a stunt, and so are fielding no candidates.
Binface's candidacy accurately represents the absurdity of the whole thing.
For trusted publishing, it's not a band-aid, it's a significant improvement that kills an entire class of CI takeover publish attacks. I'm sure attackers will find another way but it's a big gap this is closing up.
China has significantly lower co2 emitted per capita than the US already. Per kWh no, but that's a different thing. AFAICT China's renewable growth is now outpacing demand growth significantly though, so that per-capita gap will widen, and the per kWh is steadily improving as well, and faster than the US.
For some concrete numbers: China added 400GW of renewables in 2025 vs 78 GW of coal generation. Reduced CO2 intensity of power grid by 5% vs US 3% drop. In 2025 US total power emissions went up 5% (for many reasons, but arguably high gas prices and lots of data centres) while China total power emissions dropped 1.5%
All the details make China's path look much cleaner than the US's.
I agree the Rajoy government's handling of this was very problematic, but the rest of this isn't really accurate. And the morals of the economy argument is terrible - the rest of the country needs us, so we should cut them off? The same argument would apply for Barcelona cutting off the rest of Catalunya. It's not a good direction.
Resd the article - this isn't a proprietary secret API, it's the official intended interop API the EU now obliges them to provide. Not exactly 100% what you're asking for (I too would prefer common standards) but forcing interop access is a very good start.
You can also buy quite a few routers now that have it built in, so you literally just tick a checkbox, then scan a QR code/copy a file to each client device, done.
Subscriptions are incentives for companies to keep doing what you want, along with direct consequences (everybody will cancel) to penalise them for ignoring their core user base.
Don't let the awkwardness of the system (fully agree modern banking is shit at letting you manage recurring bills) distract from the underlying user-beneficial dynamics.
https://firstpagesage.com/reports/top-generative-ai-chatbots... suggests 0.6% of chat use cases, well below the other big names, and I suspect those stats for chat are higher than other scenarios like business usage. Given all that, I can see how Gemini might not be focused on competing with them.
In that world nobody should ever ever sell a lifetime license, it's a huge responsibility with strictly limited upside. Imo "Use the current-ish version forever" is the only reasonable expectation, and that's a fair trade.
It's expectations like this that drive subscription models. People do (quite reasonably) want ongoing support and updates, but that takes continual work, so the only way to make that possible is to somehow provide ongoing funding.
If you want to sponsor Waydroid to help make that happen, you can do so right now: https://opencollective.com/Waydroid (I'm not affiliated, just a fan, and it's the only realistic route to this I see).
There's other issues (UX, privacy to the 3rd parties) and further improvements here coming with better wallets (EU-wide) soon, but even today it's absolutely possible to have digital id that doesn't tell the government every time you use it.
If anything, there's really a big advantage to it for the banks - most locals already have banking, immigrants are the one market where you can get new customers without having to push them past the effort/laziness of switching from their existing setup.
There are patches out now, but only after Apple released the OS to the entire team world and people reported the issue to the Electron team.
Imo, Electron is sufficiently popular that somebody should test at least one Electron app on a major new OS version sometime before releasing it as done! Any app would've worked, and there's plenty of popular ones, as this post shows.
Play Integrity is focused on checking the OS is original and the runtime environment of the app (your banking app in this case) isn't being messed with. Installing other apps as a developer isn't related to that. If you're not flashing a custom OS or modifying your bank's APK you'll be fine.
(You _should_ be able to use custom OSs and Play Integrity is awful, to be clear - but not because of anything directly relate to normal app development & sideloading)
While it clearly isn't a hard guarantee, in practice it does seem to generally work as these have been known issues without apparent massive exploits for decades. That CORS restrictions block probing (no response provided) does help makes this all significantly more difficult.
The issue is that CORS gates access only on the consent of the target server. It must return headers that opt into receiving requests from the website.
This proposal aims to tighten that, so that even if the website and the network device both actively want to communicate, the user's permission is also explicitly requested. Historically we assumed server & website agreement was sufficient, but Facebook's recent tricks where websites secretly talked to apps on your phone have broken that assumption - websites might be in cahoots with local network servers to work against your interests.