Article suggestions: Difference between revisions

Line 244:

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.

|<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/}}</ref>

|-

|Google, Mozilla, Apple, but largely Google-led

|Google Chrome, Mozilla Firefox, and Safari are removing XSLT 1.0 support, which could break critical parts of government's websites worldwide. There are valid security reasons for them to want to stop supporting this 1999-era standard, however they have had 26+ years to update to a newer standard (such as the 2017-era 3.1 standard, which is backwards compatible and would allow these sites to continue to work). The single unpaid developer maintaining these libraries has more or less retired after getting flooded with impossible to satisfy security requests from these companies. There is an existing project called XRUST to implement the 3.1 standard, which is 2/3rds of the way through supporting all the features of 1.0 - the XSLT part fully supports all the 1.0 features at this point. XSLT is part of the W3C Consortium's open web standards for formatting and presenting XML, and is also how RSS works, so RSS feeds would stop working as well.

|

|-

|McDonald's/Taylor

@@ Line 244: / Line 244: @@
 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.
 |<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/}}</ref>
+|-
+|Google, Mozilla, Apple, but largely Google-led
+|Google Chrome, Mozilla Firefox, and Safari are removing XSLT 1.0 support, which could break critical parts of government's websites worldwide. There are valid security reasons for them to want to stop supporting this 1999-era standard, however they have had 26+ years to update to a newer standard (such as the 2017-era 3.1 standard, which is backwards compatible and would allow these sites to continue to work). The single unpaid developer maintaining these libraries has more or less retired after getting flooded with impossible to satisfy security requests from these companies. There is an existing project called XRUST to implement the 3.1 standard, which is 2/3rds of the way through supporting all the features of 1.0 - the XSLT part fully supports all the 1.0 features at this point. XSLT is part of the W3C Consortium's open web standards for formatting and presenting XML, and is also how RSS works, so RSS feeds would stop working as well.
+|
 |-
 |McDonald's/Taylor