Andrew V (talk | contribs)
Andrew V (talk | contribs)
List of incidents not yet covered: added links to companies
Line 42: Line 42:
|<ref>{{Cite web |title= |url=https://www.heise.de/en/news/Amazon-makes-Fire-TV-Blaster-unusable-11145570.html |url-status=live |archive-url=http://web.archive.org/web/20260120070820/https://www.heise.de/en/news/Amazon-makes-Fire-TV-Blaster-unusable-11145570.html |archive-date=20 Jan 2026}}</ref>
|<ref>{{Cite web |title= |url=https://www.heise.de/en/news/Amazon-makes-Fire-TV-Blaster-unusable-11145570.html |url-status=live |archive-url=http://web.archive.org/web/20260120070820/https://www.heise.de/en/news/Amazon-makes-Fire-TV-Blaster-unusable-11145570.html |archive-date=20 Jan 2026}}</ref>
|-
|-
|Anker
|[[Anker]]
|In Anker's Terms of Service for Solix solar generator product, under 19.3 Mandatory Updates:
|In Anker's Terms of Service for Solix solar generator product, under 19.3 Mandatory Updates:
In critical situations—such as addressing severe security vulnerabilities, complying with legal requirements, or ensuring compatibility with our service architecture—we reserve the right to issue mandatory Updates for both the firmware and the App. These essential updates may install automatically, or require immediate installation before further use, and you will not be permitted to opt out. If you fail to install such an update, certain device functionalities or access to the App may be limited or suspended to maintain the security and integrity of our service.
In critical situations—such as addressing severe security vulnerabilities, complying with legal requirements, or ensuring compatibility with our service architecture—we reserve the right to issue mandatory Updates for both the firmware and the App. These essential updates may install automatically, or require immediate installation before further use, and you will not be permitted to opt out. If you fail to install such an update, certain device functionalities or access to the App may be limited or suspended to maintain the security and integrity of our service.
Line 56: Line 56:
|<ref>{{Cite web |title=Apple will no longer fix the $17,000 gold Apple Watch |url=https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |url-status=live |archive-url=https://web.archive.org/web/20260222211749/https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |archive-date=22 Feb 2026|website=The Verge}}</ref>
|<ref>{{Cite web |title=Apple will no longer fix the $17,000 gold Apple Watch |url=https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |url-status=live |archive-url=https://web.archive.org/web/20260222211749/https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |archive-date=22 Feb 2026|website=The Verge}}</ref>
|-
|-
|Apple, Beats
|[[Apple]], [[Beats]]
|No support for Powerbeats (4th generation) despite the headphones being under 5 years from when Apple last distributed the product for sale. The product is not listed as discontinued or vintage, and by Apple's own guidelines, should be eligible for replacement parts and repair. OEM replacement eartips cannot be purchased for any Beats earphones.
|No support for Powerbeats (4th generation) despite the headphones being under 5 years from when Apple last distributed the product for sale. The product is not listed as discontinued or vintage, and by Apple's own guidelines, should be eligible for replacement parts and repair. OEM replacement eartips cannot be purchased for any Beats earphones.
|<ref>{{Cite web |title=Obtaining service for your Apple product after an expired warranty |url=https://support.apple.com/en-us/102772 |url-status=live |archive-url=http://web.archive.org/web/20260207094149/https://support.apple.com/en-us/102772 |archive-date=7 Feb 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Beats Repair and Service |url=https://support.apple.com/beats/repair |url-status=live |archive-url=http://web.archive.org/web/20260104000857/https://support.apple.com/beats/repair |archive-date=4 Jan 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Apple store search for eartips |url=https://www.apple.com/us/search/eartips?src=alp |url-status=live |archive-url=http://web.archive.org/web/20251028001314/https://www.apple.com/us/search/eartips?src=alp |archive-date=28 Oct 2025|access-date=2025-10-18}}</ref>
|<ref>{{Cite web |title=Obtaining service for your Apple product after an expired warranty |url=https://support.apple.com/en-us/102772 |url-status=live |archive-url=http://web.archive.org/web/20260207094149/https://support.apple.com/en-us/102772 |archive-date=7 Feb 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Beats Repair and Service |url=https://support.apple.com/beats/repair |url-status=live |archive-url=http://web.archive.org/web/20260104000857/https://support.apple.com/beats/repair |archive-date=4 Jan 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Apple store search for eartips |url=https://www.apple.com/us/search/eartips?src=alp |url-status=live |archive-url=http://web.archive.org/web/20251028001314/https://www.apple.com/us/search/eartips?src=alp |archive-date=28 Oct 2025|access-date=2025-10-18}}</ref>
Line 71: Line 71:
|<ref>{{Cite web |title= |url=https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |url-status=live |archive-url=http://web.archive.org/web/20260212060655/https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |archive-date=12 Feb 2026}}</ref><ref>{{Cite web |last=LMG Clips |title=Wikipedia Banned 690,000 Archive Links - LMG Clips |url=https://youtu.be/rrnFUvFGf5A?si=32JRogu2ID9xykHd |access-date=2026-03-03 |website=LMG Clips on YouTube - Wikipedia Banned 690,000 Archive Links}}</ref>
|<ref>{{Cite web |title= |url=https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |url-status=live |archive-url=http://web.archive.org/web/20260212060655/https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |archive-date=12 Feb 2026}}</ref><ref>{{Cite web |last=LMG Clips |title=Wikipedia Banned 690,000 Archive Links - LMG Clips |url=https://youtu.be/rrnFUvFGf5A?si=32JRogu2ID9xykHd |access-date=2026-03-03 |website=LMG Clips on YouTube - Wikipedia Banned 690,000 Archive Links}}</ref>
|-
|-
|'''Arduino''' (/ɑːrˈdwiːnoʊ/) is an Italian open-source hardware and software company owned by Qualcomm
|'''[[Arduino]]''' (/ɑːrˈdwiːnoʊ/) is an Italian open-source hardware and software company owned by Qualcomm
|Arduino’s new terms of service worries hobbyists ahead of Qualcomm acquisition.
|Arduino’s new terms of service worries hobbyists ahead of Qualcomm acquisition.
User shall not:
User shall not:
Line 91: Line 91:
|
|
|-
|-
|Best Buy
|[[Best Buy]]
|In late 2025, BestBuy added [https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. "Comparable Value"] as means of comparing values of products that is of equivalent value to other products sold by manufacturers, 1st party, or 3rd party vendors. Changes to their pricing model has made it to where it is more difficult to determine overall value of a product compared to MSRP.
|In late 2025, BestBuy added [https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. "Comparable Value"] as means of comparing values of products that is of equivalent value to other products sold by manufacturers, 1st party, or 3rd party vendors. Changes to their pricing model has made it to where it is more difficult to determine overall value of a product compared to MSRP.
|<ref>{{Cite web |last=Support |first=Best Buy |date=2025-01-24 |title=Pricing: Promotions |url=https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. |url-status=live |access-date=2026-02-24 |website=Best Buy}}</ref>
|<ref>{{Cite web |last=Support |first=Best Buy |date=2025-01-24 |title=Pricing: Promotions |url=https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. |url-status=live |access-date=2026-02-24 |website=Best Buy}}</ref>
Line 111: Line 111:
|<ref>{{Cite web |title=Webnovel ToS |url=https://www.webnovel.com/terms_of_service |url-status=live |archive-url=http://web.archive.org/web/20260101204816/https://www.webnovel.com/terms_of_service |archive-date=1 Jan 2026}}</ref>
|<ref>{{Cite web |title=Webnovel ToS |url=https://www.webnovel.com/terms_of_service |url-status=live |archive-url=http://web.archive.org/web/20260101204816/https://www.webnovel.com/terms_of_service |archive-date=1 Jan 2026}}</ref>
|-
|-
|Devolo
|[[Devolo]]
|Devolo switches off servers and removes their app from stores for their "Home Control" system, thus severely reducing the functionality of their devices (apparently Z-Wave-based).
|Devolo switches off servers and removes their app from stores for their "Home Control" system, thus severely reducing the functionality of their devices (apparently Z-Wave-based).
|<ref>{{Cite web |title=IT-News für Profis |url=https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |url-status=live |archive-url=http://web.archive.org/web/20251210052941/https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |archive-date=10 Dec 2025|website=Golem |language=de}}</ref>
|<ref>{{Cite web |title=IT-News für Profis |url=https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |url-status=live |archive-url=http://web.archive.org/web/20251210052941/https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |archive-date=10 Dec 2025|website=Golem |language=de}}</ref>
|-
|-
|Dell and HP
|[[Dell]] and [[HP]]
|HP and Dell have disabled HEVC (H.264/H.265) hardware encoding and decoding support built into their laptops’ CPUs using both Intel and AMD processors.
|HP and Dell have disabled HEVC (H.264/H.265) hardware encoding and decoding support built into their laptops’ CPUs using both Intel and AMD processors.
|<ref>{{Cite web |last=Harding |first=Scharon |date=2025-11-21 |title=HP and Dell disable HEVC support built into their laptops’ CPUs |url=https://arstechnica.com/gadgets/2025/11/hp-and-dell-disable-hevc-support-built-into-their-laptops-cpus/ |url-status=live |archive-url=https://web.archive.org/web/20251121083438/https://arstechnica.com/gadgets/2025/11/hp-and-dell-disable-hevc-support-built-into-their-laptops-cpus/ |archive-date=2025-11-21 |access-date=2025-11-21 |website=Ars Technica}}</ref>
|<ref>{{Cite web |last=Harding |first=Scharon |date=2025-11-21 |title=HP and Dell disable HEVC support built into their laptops’ CPUs |url=https://arstechnica.com/gadgets/2025/11/hp-and-dell-disable-hevc-support-built-into-their-laptops-cpus/ |url-status=live |archive-url=https://web.archive.org/web/20251121083438/https://arstechnica.com/gadgets/2025/11/hp-and-dell-disable-hevc-support-built-into-their-laptops-cpus/ |archive-date=2025-11-21 |access-date=2025-11-21 |website=Ars Technica}}</ref>
Line 123: Line 123:
|<ref>{{Cite web |date=2025-10-02 |title=E621 |url=https://e621.net/ |url-status=live |archive-url=http://web.archive.org/web/20260128164339/https://e621.net/ |archive-date=28 Jan 2026|website=E621}}</ref>
|<ref>{{Cite web |date=2025-10-02 |title=E621 |url=https://e621.net/ |url-status=live |archive-url=http://web.archive.org/web/20260128164339/https://e621.net/ |archive-date=28 Jan 2026|website=E621}}</ref>
|-
|-
|EcoVac
|[[EcoVac]]
|Vacuum cleaner robots produced by company 'EcoVac' were found vulnerable to hacking over bluetooth allowing for remote control and access to camera feed. Security researcher Dennis Giese notified the company in December of 2023. In August of 2024, the issue was described by the company as "extremely rare in typical user environments and require specialized hacking tools and physical access to the device."
|Vacuum cleaner robots produced by company 'EcoVac' were found vulnerable to hacking over bluetooth allowing for remote control and access to camera feed. Security researcher Dennis Giese notified the company in December of 2023. In August of 2024, the issue was described by the company as "extremely rare in typical user environments and require specialized hacking tools and physical access to the device."
|<ref>{{Cite web |last=Fell |first=Julian |date=2024-10-04 |title=We hacked a robot vacuum — and could watch live through its camera - ABC News |url=https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |url-status=live |archive-url=http://web.archive.org/web/20251128025250/https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |archive-date=28 Nov 2025|access-date=2025-09-10 |website=ABC News}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-09 |title=Ecovacs home robots can be hacked to spy on their owners, researchers say {{!}} TechCrunch |url=https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |url-status=live |archive-url=https://web.archive.org/web/20260222212044/https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |archive-date=10 Aug 2024}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-15 |title=Lorenzo Franceschi-Bicchierai on X: "Finally, Ecovacs responds to the researchers' findings, saying it won't fix the bugs. |url=https://x.com/lorenzofb/status/1823774980460388675 |url-status=live |archive-url=http://web.archive.org/web/20241108194816/https://x.com/lorenzofb/status/1823774980460388675 |archive-date=8 Nov 2024}}</ref>
|<ref>{{Cite web |last=Fell |first=Julian |date=2024-10-04 |title=We hacked a robot vacuum — and could watch live through its camera - ABC News |url=https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |url-status=live |archive-url=http://web.archive.org/web/20251128025250/https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |archive-date=28 Nov 2025|access-date=2025-09-10 |website=ABC News}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-09 |title=Ecovacs home robots can be hacked to spy on their owners, researchers say {{!}} TechCrunch |url=https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |url-status=live |archive-url=https://web.archive.org/web/20260222212044/https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |archive-date=10 Aug 2024}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-15 |title=Lorenzo Franceschi-Bicchierai on X: "Finally, Ecovacs responds to the researchers' findings, saying it won't fix the bugs. |url=https://x.com/lorenzofb/status/1823774980460388675 |url-status=live |archive-url=http://web.archive.org/web/20241108194816/https://x.com/lorenzofb/status/1823774980460388675 |archive-date=8 Nov 2024}}</ref>
Line 135: Line 135:
|
|
|-
|-
|Gaggia
|[[Gaggia]]
|Between 2015 to 2019, the redesigned Gaggia Classic removed the traditional three-way solenoid valve. The valve was restored in the 2019 Gaggia Classic Pro after criticism and backlash from the espresso enthusiast community.
|Between 2015 to 2019, the redesigned Gaggia Classic removed the traditional three-way solenoid valve. The valve was restored in the 2019 Gaggia Classic Pro after criticism and backlash from the espresso enthusiast community.
|<ref>{{Cite web |last=Waddell |first=Kelsey |date=2023-03-23 |title=Gaggia Classic vs Pro: A Closer Look at the Differences |url=https://www.roastycoffee.com/gaggia-classic-vs-pro/ |website=Roasty Coffee}}</ref>
|<ref>{{Cite web |last=Waddell |first=Kelsey |date=2023-03-23 |title=Gaggia Classic vs Pro: A Closer Look at the Differences |url=https://www.roastycoffee.com/gaggia-classic-vs-pro/ |website=Roasty Coffee}}</ref>
Line 147: Line 147:
|
|
|-
|-
|Google
|[[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.
|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 Graphene OS, now delayed source code disclosure). What's worst, they always cite safety as a reason.
Line 156: Line 156:
|<ref>{{Cite web |title= |url=https://www.reddit.com/r/GoogleMaps/comments/1r4iauf/google_maps_now_forces_you_to_signin/ |archive-url=https://web.archive.org/web/20260223032117/https://old.reddit.com/r/GoogleMaps/comments/1r4iauf/google_maps_now_forces_you_to_signin/ |archive-date=23 Feb 2026}}</ref><ref>{{Cite web |title= |url=https://www.reddit.com/r/GoogleMaps/comments/1r74v0f/cant_view_images_without_logging_in/ |archive-url=https://web.archive.org/web/20260223032213/https://old.reddit.com/r/GoogleMaps/comments/1r74v0f/cant_view_images_without_logging_in/ |archive-date=23 Feb 2026}}</ref>
|<ref>{{Cite web |title= |url=https://www.reddit.com/r/GoogleMaps/comments/1r4iauf/google_maps_now_forces_you_to_signin/ |archive-url=https://web.archive.org/web/20260223032117/https://old.reddit.com/r/GoogleMaps/comments/1r4iauf/google_maps_now_forces_you_to_signin/ |archive-date=23 Feb 2026}}</ref><ref>{{Cite web |title= |url=https://www.reddit.com/r/GoogleMaps/comments/1r74v0f/cant_view_images_without_logging_in/ |archive-url=https://web.archive.org/web/20260223032213/https://old.reddit.com/r/GoogleMaps/comments/1r74v0f/cant_view_images_without_logging_in/ |archive-date=23 Feb 2026}}</ref>
|-
|-
|Google, Mozilla, Apple, Microsoft, 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<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 |archive-url=http://web.archive.org/web/20260211221059/https://github.com/whatwg/html/issues/11582 |archive-date=11 Feb 2026|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 |archive-url=http://web.archive.org/web/20260116015839/https://www.w3.org/TR/xpath-31/ |archive-date=16 Jan 2026|website=W3C}}</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 |archive-url=http://web.archive.org/web/20260131231248/https://gitlab.gnome.org/GNOME/libxml2/-/issues/913 |archive-date=31 Jan 2026|access-date=2025-10-25 |website=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 |archive-url=http://web.archive.org/web/20260204085435/https://gitlab.gnome.org/World/Rust/markup-rs/xrust |archive-date=4 Feb 2026|access-date=2025-10-14 |website=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 |archive-url=https://web.archive.org/web/20260222212228/https://ppc.land/google-targets-rss-feeds-in-new-xslt-removal-proposal/ |archive-date=22 Feb 2026|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/ |url-status=live |archive-url=http://web.archive.org/web/20260131231310/https://thenewstack.io/xslt-debate-leads-to-bigger-questions-of-web-governance/ |archive-date=31 Jan 2026|access-date=2025-10-14 |website=The New Stack}}</ref>
|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 |archive-url=http://web.archive.org/web/20260211221059/https://github.com/whatwg/html/issues/11582 |archive-date=11 Feb 2026|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 |archive-url=http://web.archive.org/web/20260116015839/https://www.w3.org/TR/xpath-31/ |archive-date=16 Jan 2026|website=W3C}}</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 |archive-url=http://web.archive.org/web/20260131231248/https://gitlab.gnome.org/GNOME/libxml2/-/issues/913 |archive-date=31 Jan 2026|access-date=2025-10-25 |website=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 |archive-url=http://web.archive.org/web/20260204085435/https://gitlab.gnome.org/World/Rust/markup-rs/xrust |archive-date=4 Feb 2026|access-date=2025-10-14 |website=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 |archive-url=https://web.archive.org/web/20260222212228/https://ppc.land/google-targets-rss-feeds-in-new-xslt-removal-proposal/ |archive-date=22 Feb 2026|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/ |url-status=live |archive-url=http://web.archive.org/web/20260131231310/https://thenewstack.io/xslt-debate-leads-to-bigger-questions-of-web-governance/ |archive-date=31 Jan 2026|access-date=2025-10-14 |website=The New Stack}}</ref>
|
|
Line 193: Line 193:
|
|
|-
|-
|KOSA
|[[KOSA]]
|KOSA claims to make kids safer, but it’s really a dangerous censorship bill that would give the U.S. government unprecedented control over the internet. This would put youth in danger by preventing them from accessing potentially life-saving resources.
|KOSA claims to make kids safer, but it’s really a dangerous censorship bill that would give the U.S. government unprecedented control over the internet. This would put youth in danger by preventing them from accessing potentially life-saving resources.
|<ref>{{Cite web |last= |first=Fight for the Future |date=2026-01-24 |title=Reject online censorship. Tell lawmakers to oppose KOSA! |url=https://www.stopkosa.com/ |url-status=live |archive-url= |archive-date= |access-date=2026-01-24 |website=Stop KOSA}}</ref><ref>https://web.archive.org/web/20250228145348/https://www.houstonchronicle.com/news/houston-texas/education/article/Katy-ISD-blocks-LGBTQ-resources-suicide-16647274.php</ref>
|<ref>{{Cite web |last= |first=Fight for the Future |date=2026-01-24 |title=Reject online censorship. Tell lawmakers to oppose KOSA! |url=https://www.stopkosa.com/ |url-status=live |archive-url= |archive-date= |access-date=2026-01-24 |website=Stop KOSA}}</ref><ref>https://web.archive.org/web/20250228145348/https://www.houstonchronicle.com/news/houston-texas/education/article/Katy-ISD-blocks-LGBTQ-resources-suicide-16647274.php</ref>
|-
|-
|LBRY Foundation, Odysee
|[[LBRY]] Foundation, [[Odysee]]
|Community first decentralization & Odysee's plan to enable censorship by switching away from the opensource LBRY network.
|Community first decentralization & Odysee's plan to enable censorship by switching away from the opensource LBRY network.
|<ref>{{Cite web |title=The LBRY Foundation |url=https://lbry.org/ |url-status=live |archive-url=http://web.archive.org/web/20260211161516/https://lbry.org/ |archive-date=11 Feb 2026|access-date=2025-08-08 |quote=The LBRY community invites everyone to join us in building a more free and open way to share content and information online.}}</ref><ref name=":2">{{Cite news |last=Watson |first=RT |date=6 Jun 2024 |title=Decentralized YouTube alternative Odysee acquired by Forward Research despite content concerns |url=https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |url-status=live |archive-url=http://web.archive.org/web/20251127094918/https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |archive-date=27 Nov 2025|access-date=16 Aug 2025 |work=The Block}}</ref><ref>{{Cite journal |last=Li |first=Jun |last2=Grintsvayg |first2=Alex |last3=Kauffman |first3=Jeremy |last4=Fleming |first4=Charles |date=2020 |title=LBRY: A Blockchain-Based Decentralized Digital Content Marketplace |url=https://ieeexplore.ieee.org/document/9126007 |journal=2020 IEEE International Conference on Decentralized Applications and Infrastructures (DAPPS) |location=Oxford, UK |publisher=IEEE |doi=10.1109/DAPPS49028.2020.00005 |isbn=978-1-7281-6978-1 |via=IEEE Xplore |url-status=live |archive-url=http://web.archive.org/web/20250825221749/https://ieeexplore.ieee.org/document/9126007/ |archive-date=25 Aug 2025}}</ref>
|<ref>{{Cite web |title=The LBRY Foundation |url=https://lbry.org/ |url-status=live |archive-url=http://web.archive.org/web/20260211161516/https://lbry.org/ |archive-date=11 Feb 2026|access-date=2025-08-08 |quote=The LBRY community invites everyone to join us in building a more free and open way to share content and information online.}}</ref><ref name=":2">{{Cite news |last=Watson |first=RT |date=6 Jun 2024 |title=Decentralized YouTube alternative Odysee acquired by Forward Research despite content concerns |url=https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |url-status=live |archive-url=http://web.archive.org/web/20251127094918/https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |archive-date=27 Nov 2025|access-date=16 Aug 2025 |work=The Block}}</ref><ref>{{Cite journal |last=Li |first=Jun |last2=Grintsvayg |first2=Alex |last3=Kauffman |first3=Jeremy |last4=Fleming |first4=Charles |date=2020 |title=LBRY: A Blockchain-Based Decentralized Digital Content Marketplace |url=https://ieeexplore.ieee.org/document/9126007 |journal=2020 IEEE International Conference on Decentralized Applications and Infrastructures (DAPPS) |location=Oxford, UK |publisher=IEEE |doi=10.1109/DAPPS49028.2020.00005 |isbn=978-1-7281-6978-1 |via=IEEE Xplore |url-status=live |archive-url=http://web.archive.org/web/20250825221749/https://ieeexplore.ieee.org/document/9126007/ |archive-date=25 Aug 2025}}</ref>
|-
|-
|LG
|[[LG]]
|LG discontinued its LG Bluetooth Remote app (including plugins such as "btc4") making it non-public on the Play Store and making Bluetooth controllable devices (like for example the CM2630B) half as useful, without even publishing neither the protocol used to control such devices nor the source code of the app.
|LG discontinued its LG Bluetooth Remote app (including plugins such as "btc4") making it non-public on the Play Store and making Bluetooth controllable devices (like for example the CM2630B) half as useful, without even publishing neither the protocol used to control such devices nor the source code of the app.
|
|
Line 209: Line 209:
|<ref>{{Cite web |last=Koebler |first=Jason |date=6 Aug 2025 |title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops |url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |url-status=live |archive-url=http://web.archive.org/web/20260216173226/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |archive-date=16 Feb 2026|access-date=15 Sep 2025 |website=404 Media}}</ref><ref>{{Cite web |date=26 Aug 2025 |title=Lowe’s U.S. Privacy Statement |url=https://www.lowes.com/l/about/privacy-and-security-statement |url-status=live |archive-url=http://web.archive.org/web/20251228013530/https://www.lowes.com/l/about/privacy-and-security-statement |archive-date=28 Dec 2025|access-date=15 Sep 2025 |website=Lowe's}}</ref>
|<ref>{{Cite web |last=Koebler |first=Jason |date=6 Aug 2025 |title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops |url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |url-status=live |archive-url=http://web.archive.org/web/20260216173226/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |archive-date=16 Feb 2026|access-date=15 Sep 2025 |website=404 Media}}</ref><ref>{{Cite web |date=26 Aug 2025 |title=Lowe’s U.S. Privacy Statement |url=https://www.lowes.com/l/about/privacy-and-security-statement |url-status=live |archive-url=http://web.archive.org/web/20251228013530/https://www.lowes.com/l/about/privacy-and-security-statement |archive-date=28 Dec 2025|access-date=15 Sep 2025 |website=Lowe's}}</ref>
|-
|-
|McDonald's/Taylor
|[[McDonald's]]/Taylor
|McDonald's US mandates which ice cream machine has to be used by franchise licensees. The company that makes these machines uses deliberately obfuscated error codes to force restaurant owners to use their expensive tech service to fix them and reset the machines. The company makes more money from these "repairs" support than with actual sales. Not strictly end consumer, but the pattern warrants documenting imo.
|McDonald's US mandates which ice cream machine has to be used by franchise licensees. The company that makes these machines uses deliberately obfuscated error codes to force restaurant owners to use their expensive tech service to fix them and reset the machines. The company makes more money from these "repairs" support than with actual sales. Not strictly end consumer, but the pattern warrants documenting imo.
A similar problem exists with Doremi (Dolby) cinema projectors where their DRM leads to a ridiculous number of actions breaking the so-called "marriage" (projector-media block unity), requiring a costly technician to reset it. This one needs sources researched, though, as I don't have one on hand.
A similar problem exists with Doremi (Dolby) cinema projectors where their DRM leads to a ridiculous number of actions breaking the so-called "marriage" (projector-media block unity), requiring a costly technician to reset it. This one needs sources researched, though, as I don't have one on hand.
Line 227: Line 227:
|
|
|-
|-
|Navdy, Harman International
|[[Navdy]], [[Harman International]]
|Device discontinued and no updates, device can be used offline for 1 year until it stops working.  
|Device discontinued and no updates, device can be used offline for 1 year until it stops working.  
https://www.reddit.com/r/navdy/
https://www.reddit.com/r/navdy/
|
|
|-
|-
|Netgear (internet networking equipment)
|[[Netgear]] (internet networking equipment)
|Almost every Netgear internet router requires the creation of a new account to function as a router, where the TOS includes an agreement to binding arbitration. Most if not all devices are locked into proprietary firmware with no option to change. Some automatic updates have reportedly cause loss of performance with option to revert to a previous version, "bricking" the device in some cases.  
|Almost every Netgear internet router requires the creation of a new account to function as a router, where the TOS includes an agreement to binding arbitration. Most if not all devices are locked into proprietary firmware with no option to change. Some automatic updates have reportedly cause loss of performance with option to revert to a previous version, "bricking" the device in some cases.  
Engages in anti-consumer practices, requiring a subscription for basic WiFi-router features such as parental controls. According to a blogpost by a senior employee, grew from "45% in 2016 to over 60% in 2019" of the US consumer router market. In 2025, Netgear is "being sued by TP-Link for a 'Smear Campaign' to Advance US Router Ban [of it's competitor TP-Link].  
Engages in anti-consumer practices, requiring a subscription for basic WiFi-router features such as parental controls. According to a blogpost by a senior employee, grew from "45% in 2016 to over 60% in 2019" of the US consumer router market. In 2025, Netgear is "being sued by TP-Link for a 'Smear Campaign' to Advance US Router Ban [of it's competitor TP-Link].  
Line 240: Line 240:
[https://www.pcmag.com/news/tp-link-accuses-netgear-of-smear-campaign-to-advance-us-router-ban?test_uuid=04IpBmWGZleS0I0J3epvMrC&test_variant=B <nowiki>[65]</nowiki>]
[https://www.pcmag.com/news/tp-link-accuses-netgear-of-smear-campaign-to-advance-us-router-ban?test_uuid=04IpBmWGZleS0I0J3epvMrC&test_variant=B <nowiki>[65]</nowiki>]
|-
|-
|Nothing
|[[Nothing]]
|Nothing brings home-screen ads (can be disabled manually) and [[bloatware]] to its lower end models despite previously boasting about being bloatware free
|Nothing brings home-screen ads (can be disabled manually) and [[bloatware]] to its lower end models despite previously boasting about being bloatware free
|<ref>{{Cite web |last=Floemer |first=Andreas |date=2025-10-27 |title=Phone 3a: NothingOS 4.0 brings optional ads to the lock screen |url=https://www.heise.de/en/news/Phone-3a-NothingOS-4-0-brings-optional-ads-to-the-lock-screen-10904033.html |url-status=live |archive-url=https://web.archive.org/web/20260222212507/https://www.heise.de/en/news/Phone-3a-NothingOS-4-0-brings-optional-ads-to-the-lock-screen-10904033.html |archive-date=22 Feb 2026|access-date=2025-10-27 |website=Heise Online}}</ref>
|<ref>{{Cite web |last=Floemer |first=Andreas |date=2025-10-27 |title=Phone 3a: NothingOS 4.0 brings optional ads to the lock screen |url=https://www.heise.de/en/news/Phone-3a-NothingOS-4-0-brings-optional-ads-to-the-lock-screen-10904033.html |url-status=live |archive-url=https://web.archive.org/web/20260222212507/https://www.heise.de/en/news/Phone-3a-NothingOS-4-0-brings-optional-ads-to-the-lock-screen-10904033.html |archive-date=22 Feb 2026|access-date=2025-10-27 |website=Heise Online}}</ref>
|-
|-
|OICA (European automotive lobby organisation)
|[[OICA]] (European automotive lobby organisation)
|The OICA recently pushed for the right to emit sounds from quiet electric cars to make them as loud as conventional cars with combustion engine and against stricter noise regulation in cities. The fake engine noises in question are specifically not for safety purposes, but for emotional effect for the driver. However, instead of playing the noises only inside for just the driver to hear, the noise is to be played on speakers on the exterior, thus affecting the general public. Noise pollution has long been known to have adverse health effects. ''[NOTE: Similar to environmental aspects, greenwashing etc., we will have to find a good angle for how this fits the wiki. I would say it does match the general theme of manufacturers deliberately making their products worse for minor financial gain and lobbies pushing against things that are in public interest.]''
|The OICA recently pushed for the right to emit sounds from quiet electric cars to make them as loud as conventional cars with combustion engine and against stricter noise regulation in cities. The fake engine noises in question are specifically not for safety purposes, but for emotional effect for the driver. However, instead of playing the noises only inside for just the driver to hear, the noise is to be played on speakers on the exterior, thus affecting the general public. Noise pollution has long been known to have adverse health effects. ''[NOTE: Similar to environmental aspects, greenwashing etc., we will have to find a good angle for how this fits the wiki. I would say it does match the general theme of manufacturers deliberately making their products worse for minor financial gain and lobbies pushing against things that are in public interest.]''
|<ref>{{Cite web |last=Krempl |first=Stefan |date=2026-01-07 |title=Sound Dictatorship vs. Quiet: The Battle for E-Car Roar |url=https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |url-status=live |archive-url=http://web.archive.org/web/20260108165124/https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |archive-date=8 Jan 2026|access-date=2026-01-08 |website=Heise Online}}</ref>
|<ref>{{Cite web |last=Krempl |first=Stefan |date=2026-01-07 |title=Sound Dictatorship vs. Quiet: The Battle for E-Car Roar |url=https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |url-status=live |archive-url=http://web.archive.org/web/20260108165124/https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |archive-date=8 Jan 2026|access-date=2026-01-08 |website=Heise Online}}</ref>
|-
|-
|Persona (Age verification service)
|[[Persona]] (Age verification service)
|Used by Discord to do age verification using facial 3d scans, which are transmitted to Persona servers. It has been revealed that the company has ties to Palantir and Peter Thiel.
|Used by Discord to do age verification using facial 3d scans, which are transmitted to Persona servers. It has been revealed that the company has ties to Palantir and Peter Thiel.
|<ref>{{Cite web |title= |url=https://www.pcgamer.com/software/platforms/oh-good-discords-age-verification-rollout-has-ties-to-palantir-co-founder-and-panopticon-architect-peter-thiel/ |archive-url=http://web.archive.org/web/20260221224755/https://www.pcgamer.com/software/platforms/oh-good-discords-age-verification-rollout-has-ties-to-palantir-co-founder-and-panopticon-architect-peter-thiel/ |archive-date=21 Feb 2026}}</ref>
|<ref>{{Cite web |title= |url=https://www.pcgamer.com/software/platforms/oh-good-discords-age-verification-rollout-has-ties-to-palantir-co-founder-and-panopticon-architect-peter-thiel/ |archive-url=http://web.archive.org/web/20260221224755/https://www.pcgamer.com/software/platforms/oh-good-discords-age-verification-rollout-has-ties-to-palantir-co-founder-and-panopticon-architect-peter-thiel/ |archive-date=21 Feb 2026}}</ref>
Line 265: Line 265:
|<ref>{{Cite web |title=You'll Own Nothing and Be Happy |url=https://www.youtube.com/watch?v=5I5-rAyFQrk |website=YouTube |type=Video |url-status=live |archive-url=https://preservetube.com/watch?v=5I5-rAyFQrk |archive-date=16 Feb 2026}}</ref>
|<ref>{{Cite web |title=You'll Own Nothing and Be Happy |url=https://www.youtube.com/watch?v=5I5-rAyFQrk |website=YouTube |type=Video |url-status=live |archive-url=https://preservetube.com/watch?v=5I5-rAyFQrk |archive-date=16 Feb 2026}}</ref>
|-
|-
|Twitch
|[[Twitch]]
|Twitch has recently partnered with Persona to verify the ages of new affiliates before first payouts.
|Twitch has recently partnered with Persona to verify the ages of new affiliates before first payouts.
|
|
|-
|-
|UP3 By [[Jawbone]]
|[[UP3]] By [[Jawbone]]
|Approximately 2011, Pioneering startup company from San Francisco, had revolutionary fitness trackers.  In 2017 with no notice to customers they stole personal data and shut down app which in turn,  bricked devices. Highly likely went bankrupt and sold to sister company to manipulate customer services and rights. Now owned by Aliph brands.
|Approximately 2011, Pioneering startup company from San Francisco, had revolutionary fitness trackers.  In 2017 with no notice to customers they stole personal data and shut down app which in turn,  bricked devices. Highly likely went bankrupt and sold to sister company to manipulate customer services and rights. Now owned by Aliph brands.
|
|
|-
|-
|Vive
|[[Vive]]
|In 2022, Vive discontinued the original Vive Facial Tracker module a year after the original release, then released an updated model with proprietary firmware that blocked use on other 3rd party VR headset, while only allowing the new model to work with their new locked-down headset. The 2021 version of the face tracker's long term support was seemingly cut overnight without any software updates since 2021.
|In 2022, Vive discontinued the original Vive Facial Tracker module a year after the original release, then released an updated model with proprietary firmware that blocked use on other 3rd party VR headset, while only allowing the new model to work with their new locked-down headset. The 2021 version of the face tracker's long term support was seemingly cut overnight without any software updates since 2021.
|<ref>{{Cite web |last=Vive Team |date=2022-08-07 |title=VIVE Focus 3 gets Facial Tracker, and Eye Tracker |url=https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |url-status=live |archive-url=https://web.archive.org/web/20250619155201/https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |archive-date=2025-06-19 |access-date=2025-09-21 |website=Vive Blog}}</ref><ref>{{Cite web |last=StateKi |date=2023-10-10 |title=Post by StatekTi on X |url=https://x.com/StatekTi/status/1733954156379963393 |url-status=live |archive-url=https://archive.ph/DiYbF |archive-date=9 Jan 2026 |access-date=2025-11-21 |website=X (Formerly Twitter)}}</ref>
|<ref>{{Cite web |last=Vive Team |date=2022-08-07 |title=VIVE Focus 3 gets Facial Tracker, and Eye Tracker |url=https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |url-status=live |archive-url=https://web.archive.org/web/20250619155201/https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |archive-date=2025-06-19 |access-date=2025-09-21 |website=Vive Blog}}</ref><ref>{{Cite web |last=StateKi |date=2023-10-10 |title=Post by StatekTi on X |url=https://x.com/StatekTi/status/1733954156379963393 |url-status=live |archive-url=https://archive.ph/DiYbF |archive-date=9 Jan 2026 |access-date=2025-11-21 |website=X (Formerly Twitter)}}</ref>
Line 281: Line 281:
|
|
|-
|-
|WHMCS
|[[WHMCS]]
|Discontinuation of support and updates for WHMCS legacy “Owned” licenses, forcing users who want ongoing updates or technical support to switch to subscription licensing and pay recurring fees rather than continue with the original owned model. This change affects all holders of legacy owned licenses and alters the long-term terms under which those licenses were originally sold
|Discontinuation of support and updates for WHMCS legacy “Owned” licenses, forcing users who want ongoing updates or technical support to switch to subscription licensing and pay recurring fees rather than continue with the original owned model. This change affects all holders of legacy owned licenses and alters the long-term terms under which those licenses were originally sold
|<ref>{{Cite web |title=WHMCS Knowledgebase |url=https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |url-status=live |archive-url=http://web.archive.org/web/20251211021038/https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |archive-date=11 Dec 2025}}</ref><ref>{{Cite web |title=Important pricing changes to your WHMCS owned license Mailer |url=https://www.whmcs.com/members/mailings/?k=price21-emailo |url-status=live |archive-url=https://web.archive.org/web/20260215233549/https://www.whmcs.com/members/mailings/?k=price21-emailo |archive-date=15 Feb 2026}}</ref>
|<ref>{{Cite web |title=WHMCS Knowledgebase |url=https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |url-status=live |archive-url=http://web.archive.org/web/20251211021038/https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |archive-date=11 Dec 2025}}</ref><ref>{{Cite web |title=Important pricing changes to your WHMCS owned license Mailer |url=https://www.whmcs.com/members/mailings/?k=price21-emailo |url-status=live |archive-url=https://web.archive.org/web/20260215233549/https://www.whmcs.com/members/mailings/?k=price21-emailo |archive-date=15 Feb 2026}}</ref>
Line 304: Line 304:
|
|
|-
|-
|Xcode support dropped for older MacBooks
|[[Xcode]] support dropped for older MacBooks
|Apple has discontinued support for up to date versions of Xcode iOS development on older MacBook devices (discovered on my MacBook Pro 2017, but I’m sure it applies to other old devices as well), resulting in not being able to use a perfectly capable machine for iOS app development without having to go through countless loopholes. 1) you cannot commit new updates without utilizing a third-party medium, 2) the warning and error compiler is out of date due to not being able to update to the latest version, which of course supports the latest iOS release, so you have to figure it out on your own like it’s the 80’s 3) you must commit and release a new TestFlight build (through [1] loophole) to do any testing instead of being able to simulate on your Mac or even a connected device 4) this all really stems from the fact that the new Xcode updates require the new MacOS version which is also discontinued for older MacBooks. This means 8 year old device is basically just useless for such applications.
|Apple has discontinued support for up to date versions of Xcode iOS development on older MacBook devices (discovered on my MacBook Pro 2017, but I’m sure it applies to other old devices as well), resulting in not being able to use a perfectly capable machine for iOS app development without having to go through countless loopholes. 1) you cannot commit new updates without utilizing a third-party medium, 2) the warning and error compiler is out of date due to not being able to update to the latest version, which of course supports the latest iOS release, so you have to figure it out on your own like it’s the 80’s 3) you must commit and release a new TestFlight build (through [1] loophole) to do any testing instead of being able to simulate on your Mac or even a connected device 4) this all really stems from the fact that the new Xcode updates require the new MacOS version which is also discontinued for older MacBooks. This means 8 year old device is basically just useless for such applications.
|[[Category:Sources]]
|[[Category:Sources]]