Re:Google's Requirement for Developers to Be Verified Threat...
by GeekyBear on Tuesday October 07, 2025 @07:54PM
(#45510427)
There is no reason to punish users outside the EU who still have the legal right to demand that Google keep its word.
Re:Google's Requirement for Developers to Be Verified Threat...
by hyghjiyhu on Wednesday October 08, 2025 @10:12AM
(#45516412)
Please explain to me what the relevant parts are. What are the requirement that forces verified developers?
Re:Google's Requirement for Developers to Be Verified Threat...
by stockresearcher on Wednesday October 08, 2025 @10:20AM
(#45516508)
Scheduled to be published in December.
Re:Google's Requirement for Developers to Be Verified Threat...
by NotPractical on Wednesday October 08, 2025 @10:30AM
(#45516601)
Even if the idea originally came from the EU, the fact that Google is rolling it out worldwide would seem to indicate that they already wanted to do this, no? And regardless of whether they wanted to or not (inside the EU), it does not invalidate criticism of the move from outside of the EU.
Re:Google's Requirement for Developers to Be Verified Threat...
by sam_lowry_ on Wednesday October 08, 2025 @11:29AM
(#45517268)
> True open source with no monetization
Even RMS needs money once in a while, short of eating bits of his own flesh.. oh wait!
Sorry man. The EU Cyber Resilience Act is forcing these changes. An operating system is a class 1 important product. A tamper-resistant microchip is a class 2 important product. A device with a secure element is a critical product. Your smartphone has all of these pieces. Manufactures must follow a list of best practices to enjoy a presumption of conformity. That list of best practices is being compiled and made ready for publication, with full effect in 2026/2027. Google knows what is coming. Everyone big knows what’s coming.
True open source with no monetization can get a pass. Everyone else has to do this.
https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L...