Article suggestions: Difference between revisions

|[[ABC Financial Services]]

|Manages memberships and recurring service subscriptions for other companies. Prevents customers from being able to cancel a service by locking them into a never-ending cycle of auto renewals, and not allowing the customer to opt out of auto renewal.

|-

|[[Acer]]

|Removed Predator/Nitro Sense Applications for laptops from their support sites somewhere in early March 2026 (Looking at wayback machine snapshots). The application is required by the laptops to be able to toggle "Turbo" mode, which applies overclocks and boosts cooling. Additionally, recent Windows update(s) (KB5083769/KB5082417) have broken the application, making users unable to use it even if you were able to install it.

|-

|Affinity / [[Canva]] page created needs editors to help

|[[ASUS]] (ROG)

|Releases bios updates via windows executable, meaning that you can't update your bios to the latest version to amend a security vulnerability or fix an issue unless you're running microsoft windows.  The windows executable simply extracts a binary file, that you can drop on a thumb drive.  This could be easily done via direct download to support other operating systems.

|

|-

|[[Carvana]]

|Saying cars that have been in accidents have not; Lies about inspection and does not replace brake pads even when worn down. Non-refundable $1,500 shipping fee. See [https://www.youtube.com/watch?v=r9yhOeTUEo4 Louis Rossmann's video]

|

|-

|FBI buys location data of US citizens

|<ref>{{Cite web |title=FBI is buying location data to track US citizens, director confirms |url=https://techcrunch.com/2026/03/18/fbi-is-buying-location-data-to-track-us-citizens-kash-patel-wyden/ |url-status=live |website=[[TechCrunch]]}}</ref>

|-

|[[Foxconn]]

|

|-

|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 [[GrapheneOS]], now delayed source code disclosure). What's worst, they always cite safety as a reason.

|Google restricts data visible in Google Maps for users who are not signed in with an account (see [[Forced account]]). Reviews and photos are no longer visible without login. This also forces users to agree to Google's TOS and logs them into all other Google services, such as YouTube or Google Search so that now all their data in those other services is associated with their accounts. This also raises concerns that other services such as YouTube might follow.

|<ref>{{Cite web |date=14 Feb 2026 |title=Google Maps now forces you to sign-in |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 |website=Reddit}}</ref><ref>{{Cite web |date=17 Feb 2026 |title=Can't view images without logging in? |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 |website=Reddit}}</ref>

|-

|[[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>

|

|-

|[[GoPro]] Hero 12

|GoPro Hero 12 requires the GoPro app to be installed before you can use the camera. Many currently used devices are not compatible with the app, therefore making use of the camera difficult to impossible for new owners or upon camera factory reset. There's also the question of what data the app collects and whether it requires login and or camera activation.

|

|-

|[[Hyundai]] (BlueLink)

|<ref>{{Cite web |last=Delaney |first=John |date=2021-11-09 |title=Kangaroo Indoor + Outdoor Cam Review |url=https://www.pcmag.com/reviews/kangaroo-indoor-plus-outdoor-cam |url-status=live |archive-date=2024-08-11 |access-date=2026-04-01 |website=PCMag}}</ref><ref>https://www.bestbuy.com/product/kangaroo-indoor-outdoor-wired-1080p-security-camera-white/J3QLYYW64G/sku/6506997/reviews?pageSize=20</ref>

|-

|-

|[[Kohls]]

|Pearl Abyss

|Crimson Desert engaged in hardware gatekeeping by purposely locking out support for Intel GPUs. Their response when people asked what was going on was, “Get a refund.” They failed to mention in their hardware requirements that Intel GPUs were not supported. Intel also reached out to Pearl Abyss over the course of Crimson Desert’s development to offer support but was ignored. Pearl Abyss has now backpedaled after public backlash and says they will offer Intel GPU support.

|-

|[[Persona]] (Age verification service)

|[[Content delivery network]] ([[CDN]])

|[[wikipedia:Content_delivery_network|WP]], see also [[Cloud (service)]]. While helpful, they can infer the browsing history of millions of users across sites. The bigger their monopoly, the more cross-site tracking power they have. Even GDPR has been against using CDNs in some situations. Examples of CDN: [[wikipedia:Amazon_CloudFront|CloudFront]] (see [[Amazon]] [[wikipedia:Amazon_Web_Services|AWS]]), [[Cloudflare]], [[Microsoft]] [[wikipedia:Microsoft_Azure|Azure]], [[wikipedia:Fastly|Fastly]], etc...

|

|}

|Reticulum is an open-source, decentralized networking stack designed to communicate between practically any wireless device, even without internet. Its purpose is to provide fully anonymous end-to-end encrypted communication by default, especially in the age of government surveillance. The Reticulum network, protocol, and hardware are not tied any company in particular but were initially created by Github user 'markqvist'. Honorable mention to NomadNet, which is a network of nodes that serve webpages, similar to the internet, that communicate via Reticulum.

|<ref>{{Cite web |last=markqvist |title=Reticulum Network |url=https://reticulum.network/ |access-date=2026-02-15 |website=Reticulum |archive-url=http://web.archive.org/web/20260222180553/https://reticulum.network/ |archive-date=22 Feb 2026}}</ref>

|-

|stevesgames.co.uk