Article suggestions: Difference between revisions

Line 212:

|[[Google]]

|Google apparently plans to reduce the interval of publishing source code of security patches they consider non-critical. This is another blow to the custom ROM community.

Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with ~~Graphene OS~~, now delayed source code disclosure). What's worst, they always cite safety as a reason.

Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with [[GrapheneOS]], now delayed source code disclosure). What's worst, they always cite safety as a reason.

|<ref>{{Cite web |title=Exclusive: Google wants to make Android phones safer by switching to ‘risk-based’ security updates |url=https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-url=http://web.archive.org/web/20260107025310/https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-date=7 Jan 2026 |website=Android Authority}}</ref>

|-

@@ Line 212: / Line 212: @@
 |[[Google]]
 |Google apparently plans to reduce the interval of publishing source code of security patches they consider non-critical. This is another blow to the custom ROM community.
-Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with Graphene OS, now delayed source code disclosure). What's worst, they always cite safety as a reason.
+Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with [[GrapheneOS]], now delayed source code disclosure). What's worst, they always cite safety as a reason.
 |<ref>{{Cite web |title=Exclusive: Google wants to make Android phones safer by switching to ‘risk-based’ security updates |url=https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-url=http://web.archive.org/web/20260107025310/https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-date=7 Jan 2026 |website=Android Authority}}</ref>
 |-