Article suggestions: Difference between revisions

Yinglet (talk | contribs)
 
(One intermediate revision by one other user not shown)
Line 245: Line 245:
|<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>
|<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, Mozilla, Apple, Microsoft, 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.  
|Google Chrome, Mozilla Firefox, and Safari are removing XSLT 1.0 support, which could break critical parts of government's websites worldwide<ref>{{Cite web |last=Dimant |first=Dimitrii "Mamut" |date=2025-08-10 |title=XSLT removal will break multiple government and regulatory sites across the world #11582 |url=https://github.com/whatwg/html/issues/11582 |url-status=live |access-date=2025-10-25 |website=Github (specifically the Web Hypertext Application Technology Working Group's HTML standards repo, controlled by Mozilla, Google, Microsoft and Apple)}}</ref>. 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<ref>{{Cite web |date=2017-03-21 |title="XML Path Language (XPath) 3.1: W3C Recommendation 21 March 2017" |url=https://www.w3.org/TR/xpath-31/ |url-status=live |website=https://www.w3.org/}}</ref>). The single unpaid developer maintaining these libraries has more or less retired after getting flooded with impossible to satisfy security requests from these companies<ref>{{Cite web |last=Wellnhoffer |first=Nick |date=2025-05-08 |title=Triaging security issues reported by third parties |url=https://gitlab.gnome.org/GNOME/libxml2/-/issues/913 |url-status=live |access-date=2025-10-25 |website=https://gitlab.gnome.org}}</ref>. There is an existing project called XRUST to implement the 3.1 standard<ref>{{Cite web |date=2025-05-09 |title=XRust: XPath, XQuery, and XSLT for Rust |url=https://gitlab.gnome.org/World/Rust/markup-rs/xrust |url-status=live |access-date=2025-10-14 |website=https://gitlab.gnome.org}}</ref>, 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, disrupting the livelihoods of podcasters<ref>{{Cite web |last=Rijo |first=Luis |date=2025-08-20 |title=Google targets RSS feeds in new XSLT removal proposal |url=https://ppc.land/google-targets-rss-feeds-in-new-xslt-removal-proposal/ |url-status=live |access-date=2025-10-14 |website=PPC-Land}}</ref>. This has led to questions of who owns the web - the public (including the government) who paid for and laid down the highways / web infrastructure - or a handful of large corporations? <ref>{{Cite web |last=Branscombe |first=Mary |date=2025-09-01 |title=XSLT Debate Leads to Bigger Questions of Web Governance |url=https://thenewstack.io/xslt-debate-leads-to-bigger-questions-of-web-governance/ |access-date=2025-10-14 |website=The New Stack}}</ref>
|
|
|-
|-
Line 273: Line 273:
|The Japan Times uses DMCA to take down an open source study resource for Genki and Quartet workbooks.
|The Japan Times uses DMCA to take down an open source study resource for Genki and Quartet workbooks.
|<ref>{{Cite web |last=Clydesdale |first=Seth |date=2025-09-11 |title=Important Information Regarding Genki and Quartet Study Resources |url=https://ko-fi.com/post/Important-Information-Regarding-Genki-and-Quartet-D1D21L4B1S}}</ref><ref>{{Cite web |title=Update Regarding Genki and Quartet Study Resources DMCA Situation |url=https://ko-fi.com/post/Update-Regarding-Genki-and-Quartet-Study-Resources-Y8Y21M1F5E}}</ref><ref>{{Cite web |date=2025-10-03 |title=All Exercises for Genki/Quartet Study Resources Have Been Removed |url=https://ko-fi.com/post/All-Exercises-for-GenkiQuartet-Study-Resources-Wi-R6R81M8LLN}}</ref>
|<ref>{{Cite web |last=Clydesdale |first=Seth |date=2025-09-11 |title=Important Information Regarding Genki and Quartet Study Resources |url=https://ko-fi.com/post/Important-Information-Regarding-Genki-and-Quartet-D1D21L4B1S}}</ref><ref>{{Cite web |title=Update Regarding Genki and Quartet Study Resources DMCA Situation |url=https://ko-fi.com/post/Update-Regarding-Genki-and-Quartet-Study-Resources-Y8Y21M1F5E}}</ref><ref>{{Cite web |date=2025-10-03 |title=All Exercises for Genki/Quartet Study Resources Have Been Removed |url=https://ko-fi.com/post/All-Exercises-for-GenkiQuartet-Study-Resources-Wi-R6R81M8LLN}}</ref>
|-
|E621
|Terms of service that require agreement to forced arbitration to use the website.
|<ref>{{Cite web |date=2025-10-02 |title=E621 |url=https://e621.net/ |url-status=live |website=E621}}</ref>
|}<!-- List alphabetically!! -->
|}<!-- List alphabetically!! -->