Article suggestions: Difference between revisions
WhaleShark (talk | contribs) removed "PEAK" as I've created a page for it |
fixed some cite errors |
||
| Line 64: | Line 64: | ||
|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= |url=https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |website=Golem | |<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 |website=Golem |language=German}}</ref> | ||
|- | |- | ||
|E621 | |E621 | ||
| Line 104: | Line 104: | ||
|- | |- | ||
|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 |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= | |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=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 |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 |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 |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 117: | Line 117: | ||
|Hewlett-Packard(HP) | |Hewlett-Packard(HP) | ||
|Hewlett-Packard(HP) is removing support pages for older products, making it more difficult to continue to use older products, generally making the support experience worse, and trying to coerce users to buy new products. | |Hewlett-Packard(HP) is removing support pages for older products, making it more difficult to continue to use older products, generally making the support experience worse, and trying to coerce users to buy new products. | ||
|<ref>{{Cite web |first=gremlin12345 |date=Oct | |<ref>{{Cite web |first=gremlin12345 |date=17 Oct 2025 |title=HP will remove perfectly good documentation for products they no longer support. This seems very anti-consumer. |url=https://www.reddit.com/r/LinusTechTips/comments/1o91l44/hp_will_remove_perfectly_good_documentation_for/ |url-status=live |archive-url=https://web.archive.org/web/20251021202329/https://www.reddit.com/r/LinusTechTips/comments/1o91l44/hp_will_remove_perfectly_good_documentation_for/ |archive-date=2025-10-21 |access-date=2025-10-21 |website=reddit}}</ref><ref>{{Cite news |date=Oct 21, 2025 |title=HP Keeps Getting Worse - LMG Clips |url=https://www.youtube.com/watch?v=VNM_xUcYpK0 |url-status=live |work=Linus Media Group}}</ref><ref>{{Cite web |title=HP support pae for the j4500-j4600 series |url=https://support.hp.com/in-en/drivers/selfservice/hp-officejet-j4500-j4600-all-in-one-printer-series/3645081 |url-status=live}}</ref> | ||
|- | |- | ||
|[[Hikvision]] | |[[Hikvision]] | ||
| Line 171: | Line 171: | ||
|[[Microsoft Windows 11]] | |[[Microsoft Windows 11]] | ||
|The Windows 11 Bing Wallpaper app, which offers regularly changing desktop wallpapers, opens bing.com at every single click onto the desktop and tries to make bing.com the default search engine during launch. This is the latest step in a series of invasive actions to get Windows users to use Bing and Edge. | |The Windows 11 Bing Wallpaper app, which offers regularly changing desktop wallpapers, opens bing.com at every single click onto the desktop and tries to make bing.com the default search engine during launch. This is the latest step in a series of invasive actions to get Windows users to use Bing and Edge. | ||
|<ref>{{Cite web |title= |url=https://www.windowslatest.com/2025/10/26/windows-11s-bing-wallpaper-app-opens-bing-com-if-you-click-anywhere-on-the-desktop/}}</ref> | |<ref>{{Cite web |date=26 Oct 2025 |title=Windows 11’s Bing Wallpaper app opens <nowiki>Bing.com</nowiki> if you click anywhere on the desktop |url=https://www.windowslatest.com/2025/10/26/windows-11s-bing-wallpaper-app-opens-bing-com-if-you-click-anywhere-on-the-desktop/ |website=Windows Latest}}</ref> | ||
|- | |- | ||
|[[Mitsubishi Motors]] | |[[Mitsubishi Motors]] | ||
| Line 196: | Line 196: | ||
|[[Sony]] | |[[Sony]] | ||
|The PSVita required a proprietary memory system and came with no usable memory natively; as a result, to effectively use the console, one had to purchase official, expensive memory cards from Sony. The PCH-1000 also had a proprietary charging port, making it nearly impossible to replace the cable should it break once Sony's support for the console dwindled. The charging port issue was later addressed via an updated console which changed the port to a microUSB connection. However, the expensive proprietary memory card issue remained and was exacerbated by Sony's blockage of using the PCH-2000's 1GB of storage while a memory card was inserted. Sony's continued efforts to block homebrew via firmware updates limited the owner's ability to continue using the device years after support was dropped for the console. | |The PSVita required a proprietary memory system and came with no usable memory natively; as a result, to effectively use the console, one had to purchase official, expensive memory cards from Sony. The PCH-1000 also had a proprietary charging port, making it nearly impossible to replace the cable should it break once Sony's support for the console dwindled. The charging port issue was later addressed via an updated console which changed the port to a microUSB connection. However, the expensive proprietary memory card issue remained and was exacerbated by Sony's blockage of using the PCH-2000's 1GB of storage while a memory card was inserted. Sony's continued efforts to block homebrew via firmware updates limited the owner's ability to continue using the device years after support was dropped for the console. | ||
|<ref>{{Cite web |title=PlayStation Vita Launches From 22 February 2012 |url=https://blog.playstation.com/archive/2011/10/19/playstation-vita-launches-from-22-february-2012/ |url-status=dead |archive-url=https://blog.playstation.com/archive/2011/10/19/playstation-vita-launches-from-22-february-2012/ |archive-date=2011-10-19 |access-date=2025-10-18 |website= | |<ref>{{Cite web |title=PlayStation Vita Launches From 22 February 2012 |url=https://blog.playstation.com/archive/2011/10/19/playstation-vita-launches-from-22-february-2012/ |url-status=dead |archive-url=https://blog.playstation.com/archive/2011/10/19/playstation-vita-launches-from-22-february-2012/ |archive-date=2011-10-19 |access-date=2025-10-18 |website=<nowiki>PlayStation.Blog</nowiki>}}</ref><ref>{{Cite web |title=PS Vita Slim internal storage not usable with a memory card |url=https://web.archive.org/web/20131013181238/http://www.justpushstart.com/2013/10/ps-vita-slim-internal-storage-usable-memory-card/ |url-status=dead |archive-url=https://web.archive.org/web/20131013181238/http://www.justpushstart.com/2013/10/ps-vita-slim-internal-storage-usable-memory-card/ |archive-date=2013-10-13 |website=Just Push Start}}</ref><ref>{{Cite web |title=Types of card media |url=https://manuals.playstation.net/document/gb/psvita/basic/media.html |url-status=dead |archive-url=https://manuals.playstation.net/document/gb/psvita/basic/media.html |archive-date=2012-08-29 |access-date=2025-10-18 |website=Playstation}}</ref><ref>{{Cite web |title=Meet the Hackers Breathing New Life Into Sony’s Abandoned PlayStation Vita |url=https://www.vice.com/en/article/meet-the-hackers-breathing-new-life-into-sonys-abandoned-playstation-vita/? |url-status=live |access-date=2025-10-18 |website=Vice}}</ref> | ||
|- | |- | ||
|[[Superbox]] | |[[Superbox]] | ||
|Android TV box manufacturer Superbox remotely locks consumers' devices if they were sold below the manufacturer's minimum specified prices and asks consumers to contact the retailer when they complain. | |Android TV box manufacturer Superbox remotely locks consumers' devices if they were sold below the manufacturer's minimum specified prices and asks consumers to contact the retailer when they complain. | ||
They are not the first to do something like this. [[Deye]] locked down inverters in the US that they suspected might be gray imports. | They are not the first to do something like this. [[Deye]] locked down inverters in the US that they suspected might be gray imports. | ||
|<ref>{{Cite web |title= |url=https://www.youtube.com/watch?v=5I5-rAyFQrk}}</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}}</ref> | ||
|- | |- | ||
|[[TikTok]] | |[[TikTok]] | ||
| Line 262: | Line 262: | ||
|Ulanzi | |Ulanzi | ||
|The company offers a tutorial on how users can mix their own fog juice to use with Ulanzi mini fog machines from readily available low-cost ingredients, whereas competitors sell proprietary fog juice at extortionate prices, refuse to release the formula and refuse to honour the warranty if users use anything but the OEM brand with their machines. | |The company offers a tutorial on how users can mix their own fog juice to use with Ulanzi mini fog machines from readily available low-cost ingredients, whereas competitors sell proprietary fog juice at extortionate prices, refuse to release the formula and refuse to honour the warranty if users use anything but the OEM brand with their machines. | ||
|<ref>{{Cite web |title= |url=https://www.youtube.com/watch?v=qiq1B6-dcEM}}</ref> | |<ref>{{Cite web |title=Tutorial {{!}} How to DIY Ulanzi FM01 Fog Machine Juice? |url=https://www.youtube.com/watch?v=qiq1B6-dcEM |type=Video}}</ref> | ||
|- | |- | ||
|APSystems | |APSystems | ||
|After requests from users, the company released a firmware update that adds a local API to their EZ-1M solar micro inverter, allowing it to remain fully usable if the company ends support for the device | |After requests from users, the company released a firmware update that adds a local API to their EZ-1M solar micro inverter, allowing it to remain fully usable if the company ends support for the device | ||
|<ref>{{Cite web |title= |url=https://global.apsystems.com/document/apsystems-ezhi-local-api-user-manual/}}</ref> | |<ref>{{Cite web |title=APsystems EZHI Local API User Manual |url=https://global.apsystems.com/document/apsystems-ezhi-local-api-user-manual/ |website=global.apsystems.com}}</ref> | ||
|} | |} | ||