Welcome — post issues of interest to Moderators
- Post appeals to article notice templates (e.g. Incomplete, Stub, etc.)
- Post requests for moderator action here (e.g. blocks)
- Just need a mod? Post here or ping a mod with a question.
- Post any information or news relevant to the moderation team here.
- To request an article to be created, do not post here, try Article suggestions instead.
- Do not report technical issues here, please use the Bugs noticeboard instead.
Open tasks
Tag review and corrections, batch of five (12 November 2026, second batch)
Five user-approved, targeted cleanups. Filled section placeholders were removed as the sections were completed. HBO Max is the only page in this batch with a remaining Stub tag; that tag has been preserved for moderator review.
- Brave browser (rev 72038): filled the consumer-impact summary and Cargo ArticleType/Category, and replaced promotional privacy wording with a factual browser description. Sourced the address-bar incident to Brave's apology, its v1.9.80 release notes and contemporary reporting. Replaced the two social-media citations in the tipping section with Brave's December 22, 2018 explanation; the old page's 90-day return and later blanket prevention claims were not verified by its GitHub citation, so those were removed in favor of the documented distinction between purchased tokens and promotional grants. The source says a default change was being considered, not already implemented. Removed the unsupported assertion that advertising was the company's primary revenue source and the broad Manifest V3 exemption claim, while retaining the sourced ad-blocking-engine description and optional Rewards explanation. Corrected the first GitHub citation's archive-date from November 7 to November 8 to match its Megalodon timestamp; retained both archive links, author names, and the existing editorial comment. The summary placeholder was the category feeder; no stub tag was present.
- HBO Max (rev 72039): filled the consumer-impact summary and Cargo Description; updated Company to Warner Bros. Discovery and corrected the original launcher to WarnerMedia. Replaced the vague rebranding sentence with the dated US Max relaunch and return to the HBO Max name. The existing lifetime-subscription heading/Main link had contained the unrelated US CNN/sports removal: it is now split into the Dutch legacy-plan downgrade (notification in February, effective March 24, 2025) and US Basic with Ads removal (effective March 30). The Dutch lifetime offer was a percentage discount, not a prepaid lifetime subscription; historical price/feature details are sourced to Android Planet and the actual Netherlands Premium offer terms. No legal conclusion or disputed contract-clause number was imported from the linked incident article. Replaced the old inaccessible live-news help/TheDesk material with the company announcement and independent reporting; omitted the ancillary beta-period claim rather than deriving its history from an unreadable help page. Fixed the Hulu redlink with a Wikipedia-link template. The Stub tag is preserved; requesting its review and removal.
- Chamberlain removes API access from new and existing garage door openers (rev 72040): filled the company-response section and removed its Incomplete section notice. Distinguished unauthorized myQ cloud integrations from authorized partnerships, which remained available; removed the blanket assertion that every third-party route was blocked or that the myQ app was the sole possible route. Replaced the unsupported claim that the company's stated motive was false, plus the unsourced sudden increase in ads/data collection, with the actual attributed performance/reliability explanation and November 7 traffic claim. The original company URL and its newsroom successor now resolve to an unusable homepage/shell, so the statement is sourced through its reproduction by Home Assistant and The Verge. StartDate now uses October 2023 at month precision, consistent with Home Assistant's November post referring to the previous month; removed the unsupported March 2024 EndDate. Kept the separate 2025 Security+ 3.0 issue, corrected the universal dry-contact description of ratgdo, and used its actual compatibility FAQ rather than inferring wiring behavior across all models. Trimmed the opening NYT epigraph, privacy-policy/terms links that did not establish the claimed API effects, and retail-product examples to keep the article focused. No stub tag was present.
- Skoda (rev 72041): filled the consumer-impact summary and corrected Founded from 1896 to 1895, sourcing the company history and full Volkswagen ownership since 2000. Removed the universal paid-MySkoda claim: the app is free to download, while subscriptions apply separately to Connect service packages; I could not establish that the app migration itself compelled all Citigo owners to start a new subscription. Attributed the Move&Fun notice and differing charging controls to the contemporaneous owner report rather than asserting total loss of all functions. Corrected the Citigo network-sunset premise: the manufacturer-linked impact table explicitly marks MOD1 Citigo iV as retaining Connect after the shutdown. The service-loss discussion is now model-dependent, distinguishing affected MOD2 vehicles and later software remedies, with the notice's validity date and market caveat stated. Removed the unsupported Citigo cannot-use-4G assertion. Preserved all listed model names and implemented the requested multi-column layout, removing the fulfilled formatting comment. The linked Citigo incident article still contains contrary claims; it was not edited because it is outside this approved batch. No stub tag was present.
- Micron (rev 72042): filled the consumer-impact summary and corrected the contradictory Crucial chronology: December 3, 2025 was the exit announcement, and the stated consumer-shipment deadline was February 2026, not a verified December 2026 closure day. Removed the exclusively-AI-business claim; the official announcement retains enterprise/commercial products. Reframed the cartel section around the European Commission's 2010 settlement and 1998–2002 conduct, including Micron's immunity from fines for reporting the cartel; removed the unsupported combined EU/US guilty-finding assertion instead of treating the EU release as proof of a US criminal conviction. Renamed the condemning warranty heading and corrected universal no-replacement wording: the closure FAQ describes limited parts and a conditional original-price/taxes/original-shipping refund, not two separate remedies or a proven general breach. Tom's Hardware's reported case includes an eventual replacement and an explicit correction saying the original-price offer was within the warranty terms. The refund terms are not a guarantee of reimbursement at current replacement prices. Replaced blocked HTML press-release citations with their official PDFs, sourced company history, and condensed the vague product bullets into the supported consumer/enterprise distinction. No stub tag was present.
Source-verification limitations: Crucial's warranty-home page returned a Request Rejected shell on direct and browser requests. Its exact closure-FAQ text was retrieved through search indexing and corroborated against the readable Tom's Hardware report; index freshness could not be independently guaranteed. Speak EV was readable during research but a later parent re-fetch hit a JavaScript challenge; the saved body was checked, and owner statements are expressly attributed. The uploaded Skoda email screenshot could not be visually verified because the vision backend failed, so it is not used as a citation or independent authentication. Official Micron, European Commission and Skoda PDFs were downloaded and read.
Archive note: exact-URL CDX checks returned HTTP 429, and the save probe was refused with 429. Existing archive URLs on retained sources were preserved. A verified existing Wayback capture was added for Android Planet's Dutch downgrade report; other availability results were not substituted blindly when their contents could not be replay-verified. New live-only citations, by article:
The expected url-status maintenance notices were left in place. All five saved revisions were read back and parsed: references and sections render, with no article redlinks, reference errors or CS1 error categories. No edits were made to the linked incident pages. Happy to restore trimmed material with suitable sourcing. Thank you, Sojourna, for clearing the previous batch. — WTFelvemage (talk) 16:02, 12 November 2026 (UTC)
Done. Skoda proved the most annoying for adding archive links; there were almost no recent captures on the Wayback Machine that didn't redirect the user to the live web page. New captures had to be created using Ghost Archive and Megalodon in most cases. — Sojourna (talk) 00:32, 13 November 2026 (UTC)
Tag review and corrections, batch of five (13 November 2026)
Five user-approved, bounded article cleanups. Filled summary placeholders were removed; the Incomplete tag on Google Maps and Stub/StubNotice tags on the other four pages were preserved. Requesting moderator review and removal of those notices.
- Google Maps (rev 72097): filled the consumer-impact summary and Cargo description/category; sourced the desktop launch date and removed the unsupported popularity superlative. Corrected the permanent-account-requirement framing: February reporting described limited signed-out views, and 9to5Google's February 23 update says access was restored, without settling test versus technical problem. Removed the Maps data-aggregation/data-sale/AdSense inference: the cited FTC release concerns YouTube children's privacy, not those Maps claims. Replaced the two unreadable Redlib citations with directly inspected reporting; removed the empty example incident and unsourced customer-friendly-alternative recommendation. Repaired Apple Maps and Waze redlinks with Wikipedia-link templates; retained Forced account as a See-also link.
- Flightradar24 (rev 72098): filled the impact summary and Cargo description, made the Cargo category specific, and replaced the Wikipedia citation and old archived about-page reference with the readable company history. Distinguished the 2006 hobby project from the 2007 standalone service. Separated the 2017 app transition from the announced March 30, 2020 legacy-app deadline. Corrected blanket loss-of-purchased-features wording: Pro in-app purchases did not transfer, existing subscriptions did, and free functions remained available; ad-free replacement use required a subscription. Replaced the screenshot-only citation with readable corporate notices and contemporary reporting. The living blog/FAQ's 2024 update dates are cited; their original 2017 publication dates do not date the later shutdown announcement. No claim of independently verified shutdown enforcement or refund entitlement was added. Conflicting company statements about the first mobile-app year were not imported.
- Microsoft Authenticator (rev 72099): filled the impact summary and clarified the intro/Cargo description: one-time codes, approvals and passwordless sign-in, not unsupported SSO or random-code wording. Distinguished OTP-secret export from password export, attributing the unsupported-export statement to the Q&A moderator identified as external staff. Kept same-platform-only restore and explained work/school re-registration. Replaced the exhaustive two-options claim, universal administrator-help implication and easy-workaround/product recommendations with fresh TOTP enrollment subject to organization policy. Corrected the 2025 retirement from universal deletion to in-app inaccessibility, retaining synced Edge access and distinguishing unsaved generated passwords. Retained the Hacker News/gHacks sources and their archives; dropped the redundant Flaming citation. Removed unverified publication dates from the living backup/Keeper documents, shortened the malformed multi-URL Cargo website field, and repaired Proton/Google Authenticator redlinks with Wikipedia-link templates. The existing image was left unchanged.
- TeamViewer (rev 72100): filled the impact summary/Cargo description and distinguished free personal use from paid organizational use. Separated versions 8–10's 2021 server retirement/complimentary access from versions 11–12's announced December 2025 network-support sunset; retained LAN availability and the company's distinction between license rights and infrastructure. Replaced the condemning invalidation heading and removed the unsupported class-action-organizing claim from a forum citation that only establishes subscription-only sales. Specified Jack Gershfeld, TeamViewer US, Inc., the Central District of California and the January 20, 2023 Ninth Circuit affirmance, using the actual court memorandum; this was dismissal of his pleaded claims, not blanket validation of all renewal practices. Updated the July 2025 law-change tense. Corrected current cancellation routes to portal, written ticket or phone, retaining the 28-day notice requirement. Preserved all three authors of the law commentary in separate author fields and all retained archive URLs.
- Maytag (rev 72101): filled the impact summary, neutralized the planned-obsolescence heading, and attributed the unavailable-parts account to the customer and his technician rather than a verified Maytag refusal. Explained the limited drive-motor/wash-basket warranty as described in the report; the failed part/model and coverage of the actual failure are unidentified. June 15 is the report's publication date, not an established breakdown date. No intent, companywide pattern or warranty breach is asserted. Corrected Founded from unsupported January 1 precision to 1893 and sourced Whirlpool ownership/acquisition. Replaced the blocked homepage citation with readable Whirlpool material; condensed the product range to the categories explicitly named there, rather than separately asserting freezers, microwaves and wall ovens. Fixed the empty named-reference reuse by defining the source once and reusing it properly. Added model-specific warranty guidance, without applying another model's warranty to this owner.
Source and archive limitations: all newly used sources were opened and checked, including the Ninth Circuit PDF. The Redlib/Reddit copies and their archive replays were blocked; their thread bodies are not relied upon. Microsoft's old autofill notice now redirects, so the 2025 chronology is supported by readable contemporary reports. Maytag's main homepage returned 403; readable official Whirlpool releases and Maytag Product Help supplied the replacement citations. A historical manufacturer warranty was inspected but not treated as this customer's unidentified model contract.
Exact-URL CDX requests and archive replays returned HTTP 429, as did a save probe. Availability lookups reported several snapshots, but their contents could not be replay-verified; no uninspected snapshot was substituted for a live source. Existing archive URLs on retained sources remain, including the older TeamViewer support capture; the revised cancellation methods were verified against the current July 2026 document, not inferred from that older capture. New live-only citations, grouped by article:
All five saved revisions were read back byte-for-byte apart from terminal newlines and parsed successfully: sections/references render, with no article redlinks, reference errors or CS1 error categories. The expected url-status notices remain. No linked incident articles were edited. Happy to restore trimmed material with suitable sourcing. Thank you, Sojourna, for reviewing the previous batch. — WTFelvemage (talk) 17:48, 13 November 2026 (UTC)
Done. — Sojourna (talk) 02:51, 14 November 2026 (UTC)
Tag review and corrections, batch of five (15 November 2026)
Five user-approved, bounded cleanups. Filled section placeholders were removed. The StubNotice tags on Chamberlain Group and Wink, the Stub tags on Haier and Logitech, and Chamberlain Group's Cleanup tag were preserved; requesting moderator review and removal where appropriate. Maplesoft had no stub tag: its remaining See-also placeholder was the additional-work category feeder.
- Wink (rev 72189): filled the impact summary, Cargo description and products section, and removed the stray pipe in the Cargo website field. Distinguished the May 6, 2020 subscription announcement from the July 27 implementation at US$4.99 per month. Kept the limited local-control exception for select Lights + Power devices and Z-Wave locks, rather than implying total hub shutdown. Condensed, but retained, the notice's unavailable-function list and specified user codes; this list is contained in the July notice's embedded image. The May source's May 20 date was preserved: the live page is revised material, and the July notice independently dates the original announcement. Retained both inherited announcement archives and used CNET's contemporary implementation report plus official Hub/Hub 2 descriptions. Blank author fields on the two corporate notices were filled with Wink Blog, not discarded to hide maintenance notices.
- Haier (rev 72186): filled the impact, products and See-also placeholders and Cargo description. Corrected the no-cloud claim: the integration used Haier's servers, with pyhOn as the underlying library, not a second independent integration or an offline replacement. Replaced the malformed pyh0n link/name with the correct library identification and repository documentation. Attributed the January 15 demand to Haier Europe, not GE Appliances/Haier US. Replaced the Reddit citation with the developer's FAQ and contemporary BleepingComputer reporting. The January 22 Hackaday article establishes dialogue, not a completed reversal; added the developer's January 29 update reporting legal matters off the table and reduced server-status checks, expressly as his account rather than a formal settlement. Removed the unsupported causal assertion that pressure itself forced a reversal. Reduced the unsupported April 28 founding precision to the verified year 1984 in prose and Cargo; changed the group-level Type from Public to Corporate group rather than conflating the group with a listed subsidiary. Sourced the June 2016 GE Appliances acquisition to GE's actual announcement. No change to the linked Chamberlain incident.
- Chamberlain Group (rev 72185): filled the impact summary/Cargo description and organized the two distinct incidents under dated headings, moving the developed API incident into a Main link. Replaced the forum-based API summary with Home Assistant and The Verge; distinguished unauthorized integrations from authorized partners and retained the company's attributed performance/reliability explanation. Removed the incidental MYQ-G0401 example to keep the summary about the documented integration restriction. Corrected Home Bridge from bricked in 2023 to product discontinuation in June 2022 and support withdrawal on June 15, 2024. The current FAQ still allows setup in the myQ app, while denying firmware updates and technical support; its refund refusal concerns an existing device going offline, not a verified blanket refund history. Removed the unsupported $70–90 range. Distinguished Home Bridge hardware from Homebridge software. Sourced the founding year and attributed the 50-million-US-homes figure to the undated AWS case study. Retained the ratgdo project link but removed the sweeping virtually-any-opener compatibility assertion; moved the Home Assistant further-reading item into the inline sources and retained the codeowner discussion link. No linked incident article was edited.
- Logitech (rev 72187): filled the impact summary and sourced the intro/product summaries. Narrowed the May 28, 2025 legacy Harmony software shutdown to the listed models; existing settings remain usable and other models retain MyHarmony/app support. Repaired the product link to point directly to Logitech Harmony, and removed the redundant, unsupported early-history details from that product bullet. Replaced future-tense POP shutdown wording with the attributed September 29 notice announcing October 15 loss of functionality; this is not an independent finding that every unit stopped operating that day. Removed the uniform €130-per-switch framing and spelled out the US-only 15% purchase-discount exclusions and March 31, 2026 expiry. Neutralized the condemning heading. Kept the Heise citation, author, archive and editorial comment; corrected its translated title to match the cited title. Replaced the unsupported blanket G HUB-dependency/Linux wording and H.264-removal allegation with basic official product descriptions; the linked webcam article's first-person testing is not independent sourcing for a company-level allegation. Reduced the unsupported October 2 founding precision to the official 1981 year. No linked product article was edited.
- Maplesoft (rev 72188): added inline support to the consumer-impact summary without claiming that two is an exhaustive lifetime total. Preserved both existing incident accounts and their cited archives, adding the actual Massachusetts-hosted notification as a full citation and specifying that names, email addresses and billing addresses may have been included in 2022. The primary notice is undated; no publication day was invented for it. Corrected Richard Console, Jr.'s author spacing. Replaced raw Wikipedia links with Wikipedia-link templates, spelled out the intro's software scope, and replaced the See-also placeholder with the existing Canva breach article. Removed DigitalEd from the product list and added the sourced explanation that it became a separate corporation in 2018.
Source/archive limitations: exact-URL CDX checks and replay inspection succeeded for the newly used archived sources, after some transient connection refusals. Existing archive URLs on retained references were preserved. The GitHub issue snapshot did not contain the later January 29 comment, so that specific developer update is cited live with an access date; its author, date and complete text were verified through GitHub's comment API. Chamberlain's Home Bridge FAQ archive renders a JavaScript shell; its inherited archive remains, but the current FAQ was opened and read in a real browser, including the retained-setup and limited refund answers. The original Chamberlain corporate notice now redirects to a homepage/shell, so it is not used as an independently inspected primary citation; the announcement is reproduced by the readable Home Assistant/Verge sources. The live GE URL now shows a company-reorganization shell rather than the release, so the verified January 3, 2021 capture is used with url-status=usurped. This deliberately produces CS1: unfit URL tracking; it is not an error in the captured release. The numeric-author and live-URL maintenance notices were not suppressed. The image-vision backend failed for Wink's embedded functionality table; local Tesseract OCR was checked against the inherited list, and the retained-control exception was separately verified in both readable company prose and CNET. No unverified claim of a complete POP shutdown or formal Haier settlement was added.
All five saved revisions were read back against their drafts and parsed: sections and reference markers render, with no article redlinks, reference errors or CS1 error categories. The preserved maintenance tags remain for review. Happy to restore trimmed material with suitable sourcing. Thank you, Sojourna, for clearing the previous batch. — WTFelvemage (talk) 06:07, 15 November 2026 (UTC)
Done. I tried utilizing all three archive services that CRW frequently uses (Internet Archive, Ghost Archive, and Megalodon), however GitHub's comment system has proven to be too problematic for the citation used on the Haier page — the relevant reply is hidden by default unless the user clicks to have the "remaining items" loaded. Even IA could not overcome this obstacle; when I'd click the "Load more" button nothing would happen outside of said button disappearing. Just another reason to dislike comment systems that don't use pagination... — Sojourna (talk) 03:26, 16 November 2026 (UTC)
Tag review and corrections, batch of five (15 November 2026, second batch)
Five user-approved, targeted cleanups. Filled section placeholders were removed. The Incomplete tags on Acer and TreeSize and Stub tags on Canonical, CosmosDirekt and Old Navy were preserved; requesting moderator review and removal where appropriate. These are improvements to existing subjects, not new incident allegations.
- TreeSize (rev 72198): corrected the revocation framing and the contradictory Personal-edition claims. Existing perpetual rights remain; maintenance, updates/support and installer/key downloads are separate. Ars explicitly identifies Personal as retaining a perpetual option and renewable maintenance. Used the vendor's license agreement, including the verified July 19 historical capture, without applying the separate subscription-expiry provision to perpetual licenses. Qualified the download restriction to the support period and retained the vendor's backup advice; Ars describes this as a longstanding policy, not a new removal of purchased-version use. Replaced the Reddit-based Personal allegation with the directly checked reporting and vendor documents; retained the existing screenshot with a neutral maintenance-expiry caption. Cleared the unrelated JAM products from ProductLine, normalized the company name, corrected ArticleType from Service to Product and the product category, sourced/corrected the intro, and replaced the See-also placeholder with Software as a service. Removed the knowledge-base citation's invented publication date, which had simply matched its archive date; retained its archive. Added missing access dates. ReleaseYear was not changed as part of this bounded licensing cleanup.
- Acer (rev 72194): filled the impact summary and distinguished plaintext logging (July 4, 2015–April 28, 2016) from the attorney general's documented attacker-request period (November 11, 2015–April 28, 2016). The regulator reports information concerning 35,071 people stolen; the data categories are described as fields logged without encryption, not a claim that every field was proved stolen for every person. Specified the January 26, 2017 settlement with Acer Service Corporation, $115,000 regulatory penalties and security reforms, not a customer-compensation fund. Added inline support to the technical account and removed the editorial security-critical filler. Narrowed the consumer response to the contemporary notification report and Justin Pasher's actual forum criticism; removed unsupported plural notification recipients, varied experiences, many complainants and credit-monitoring assertions. Corrected PCMag author Stephanie Mlot's misspelled first name. The existing staff citation's verified capture reports 9,026 employees at December 2024, so replaced the undated 7,800/47% claim with that dated figure. Corrected Gartner's ranking to preliminary 2023 shipments, not a 2024 market-status claim. Added missing/current access dates as applicable and converted the reference-list invocation to Reflist. The remaining company history/product list was not rebuilt.
- CosmosDirekt (rev 72196): filled the impact summary and distinguished a browser-accessible portal from its documented app-based second authentication step. The published standard process requires the provider's app; the article no longer says the entire portal is app-only or that the linked app stores are proved exclusive distribution routes. Kept the company's security/data-protection explanation as attribution, replacing the long quote and removing the unsupported misleading-law inference, Wikipedia citation and associated Citation needed notice. The cited October 2024 Kuketz post does not name CosmosDirekt; removed that source and the unsupported 2024 rollout heading. No replacement rollout date was invented. Dated Stefan Caliandro's original observation to November 22, 2025 and the successful individual workaround to his November 27 update, without presenting it as a generally advertised option. His page is live, so corrected url-status from dead to live while retaining its original archive. Removed the FAQ's unverified publication date copied from its capture date. Escaped the literal pipe in the Forbes citation title and repaired the Google Play Store redlink with a Wikipedia-link template.
- Canonical (rev 72195): filled the impact summary, linked the existing Ubuntu article and sourced the basic company description. Removed the unsourced current largely-funded-by-Shuttleworth assertion. Preserved the security/packaging positives but removed the unsupported comparative upstream-patch-share claim and clarified AppArmor support, the Snap Store, upstream kernel livepatching and Canonical's separate Livepatch service; retained the original supporting citations and added the actual service documentation, including its scheduled-reboot caveat. Described the Snap identifier/installed-package reporting more precisely and qualified the default-install claim for versions/flavours. Corrected online-search chronology: the 2014 PCWorld report described future Unity 8 plans; Cooke's December 2015 announcement concerned Unity 7 in new Ubuntu 16.04 installs, off by default rather than removed, with existing upgrade settings retained. A released-version review corroborates the behavior. Separated Ubuntu 18.04's preselected but declinable setup report from separate crash reporting, replacing the broad forum-derived tracking assertion with the primary Ubuntu explanation and contemporary reporting. Removed the redundant Super User and Ask Ubuntu citations in favor of those directly inspected sources and the separate later opt-out report. Preserved September 2022 APT-promotion reporting but did not project the later opt-out backward; the December 2022 report documents that control. Corrected the original OMG citation from its later update date to its October 13, 2022 publication date, preserving the original capture. Reduced the ambiguous numeric FSF publication date to the verified year 2012 rather than inventing day/month interpretation; preserved Stallman's name and archive. No new tracking mechanism or contribution ranking was asserted.
- Old Navy (rev 72197): resolved the See-also placeholder with Dynamic pricing and added inline support/attribution to the impact summary. Corrected CBC's publication date to February 7, 2025 and lawyer Justin Giovannetti's spelling. Limited the pricing findings to the 10 monitored items and removed wording that implied two separate items that were always on sale. Kept the proposed British Columbia action as allegations, dated its uncertified status to CBC's report, and included the reported refusal to comment; no current certification outcome was invented. Corrected Kaplan's cart total changing three times, not increasing three times, and included her reported app-price match in-store. Removed the measured-demographic-outcome implication about older shoppers and retained her concern as attributed analysis. Replaced the misleading typical daily plus/minus 36% wording with CBS's actual US$143–US$225 monitored-cart range and almost-daily changes; no personalized-pricing mechanism was inferred. Removed the redundant CBC player/YouTube-short citations and quotation, using the readable written investigation instead. Reduced unsupported founding-day precision to 1994, normalized the Cargo website field, neutralized its description, and removed the unsupported primarily-denim/family-marketing wording and excess bolding. Added missing access dates/url-status fields without stripping authors or existing archives.
Source/archive verification: the retained reference snapshots and all newly added archives were opened and checked for the relevant content. Initial connection refusals and compressed/blocked responses were transient; the successful retries supplied readable captures, including the CosmosDirekt FAQ and workaround, the Old Navy investigations, and the TreeSize terms and reporting. The Snap documentation's live routes returned empty shells, so the inspected inherited captures supplied the documented historical behavior. The Acer staff page timed out live but its existing capture was readable, and Gartner's existing capture supplied the actual 2023 table. No new citation was left live-only. Existing archive URLs on retained sources and author names were preserved; whole citations were removed only where claims were replaced or redundant, not to suppress maintenance notices.
All five saved revisions were read back against their drafts and parsed. Sections and references render, with no article redlinks, reference errors or CS1 error categories. The protected maintenance tags remain for moderator review. Happy to restore trimmed material with suitable sourcing. — WTFelvemage (talk) 07:33, 15 November 2026 (UTC)
Done. Sojourna (talk) 03:29, 16 November 2026 (UTC)
Tag review and corrections, batch of five (15 November 2026, third batch)
Five approved company-page cleanups are saved. Please review the remaining StubNotice tags on Cariad SE and Shimano. Their protected tag lines were left unchanged. Deye, Miku and Reason Studios had section placeholders rather than protected maintenance tags; those placeholders were removed after filling the sections.
- Cariad SE (rev 72253): added sourced company/product context and an impact summary, restructured the incident, added the company's category and linked the existing incident with a Main link. Corrected the response misquote: customers were told they did not need to act; this was not CARIAD saying it would take no action. Included the report that the issue was addressed. Distinguished the broader vehicle-record set, precise locations and contact data present for some drivers. Removed the unsupported public-cloud/unencrypted equivalence, speculation about whether users were informed, the non-leak distinction and the GDPR-violation inference; the heyData citation supporting that speculative passage was replaced by the directly checked reporting. Converted the reference list to Reflist and supplied missing access dates.
- Deye (rev 72254): filled the impact summary and replaced certainty about intentional manual remote bricking with the reported failures, Deye's attributed automatic-authorization explanation and denial, and the solar writer's qualified firmware-update speculation. Kept the conflicting geographic accounts separate; did not determine the legality of individual purchases or installations. Added Sol-Ark's December 3 branding/warranty clarification. Separated the 2023 microinverter relay issue and specified the later approved inverter/relay combinations. Removed the unsupported 25% estimate, blanket Chinese-state-control assertion, malice claims and unsourced market-rank/origin narrative. Replaced the blanket disconnection advice, cross-brand recommendations, generic SolarMan/control assertions and VPN instructions with a narrow, attributed SolarAssistant compatibility example for the documented SG05LP1 hybrid family, not a claim that all Deye devices are supported or that this remedies authorization failures. Sourced the business description/products and corrected Private to Public from the company's documented 2021 listing; described 1990 as its manufacturing origins. Removed the boilerplate self-category browsing sentence; retained the actual category and existing See-also targets.
- Miku (rev 72255): filled Products and the Cargo description. Distinguished the brand, Miku Inc. and the September 15, 2023 asset/operations acquisition by Innovative Health Monitoring, LLC. Removed the unverified 2018 founding assertion from the intro/Cargo rather than replacing it with a guessed incorporation date; the founder's account supports the January 2019 product launch. Replaced the unrelated Netflix/Reddit citation with the actual acquisition letter and The Register's reporting. Attributed the announced October 1 transition and October 2 app restrictions, without asserting that every user received an email or knew nothing beforehand. Preserved same-Wi-Fi live video/audio and identified two-way talk as paid in the notice. Moved the existing incident link into a Main link. Qualified the privacy account to the two notices' actual conditions/rights and removed unsupported post-account-closure retention wording and unverified publication dates. Added the actual arbitration/class-waiver terms and stated exceptions, marked last updated June 12, 2024; these policy explanations sit under consumer impact, not as newly claimed incidents. Filled the product description, included the terms' non-medical-device disclaimer, and scoped the published Miku Inc. warranty to its U.S./Canada original-purchaser and delivery-period terms. Did not present seven-day cloud storage as universally included. Retained both existing screenshots with neutral captions.
- Reason Studios (rev 72256): filled the impact summary/Cargo description and added a short products list. Replaced the acquisition/control implication with Verdane's documented 2017 partnership and sourced the basic company context; condensed unsupported promotional/history/business-model commentary. Distinguished retirement of new legacy offline authorization from retained authorizations on unchanged systems and the vendor's explicit online support for Reason 8 and later. Did not infer that every earlier version can currently activate, or that every perpetual copy stopped working. Kept the historical 60% promotion with its actual deadline. Replaced the forum-derived dongle/reinstallation generalization with the vendor's documented conditions. Specified the automatic month-long offline period, logout consequences and the separate renewable one-year option for the listed eligible licenses/annual subscriptions, including subscription-end limits. Removed unsupported EULA-infringement/transfer-right conclusions, Adobe contract comparisons, predictions about live-event losses, financial-motive claims and the blanket claim that accessing all previously created media eventually requires continued payment. Removed the redundant broader-implications section and category-browsing boilerplate, not the category.
- Shimano (rev 72257): filled Products and the impact summary, removing empty privacy/business-model bullets. Sourced the intro/Cargo description to the company profile rather than retaining an uncited founder-naming detail. Replaced the universal lighting restriction, alleged app regression and equipment-price generalization from the video with the dated October 2023 Cyclist and September 2022 Professional manuals: rider light switching is distinct from DU-EP801/DU-EP600 terminal configuration; the cited Professional version documents SM-PCE02 startup. Replaced the video citation with those primary manuals. Corrected the 75%-combined market assertion to the source's separate European 50% Bosch/20% Shimano expert estimates, not audited shipment totals or a current universal ranking. Gave the crankset case a proper heading, affected model/manufacturing scope, production-code check, reported incidents/injuries and conditional inspection/replacement remedy. Named both settlement parties and CPSC docket 26-C0002, dating provisional acceptance to the March 16, 2026 announcement and including the proposed agreement's no-admission terms. No later final-order/payment confirmation was located, so the text does not assert payment, a final violation finding or a present unresolved-case status. Removed the category-browsing boilerplate; kept the category and existing See-also targets.
Source/archive checks: all 27 distinct cited source URLs were checked through CDX and readable captures. Relevant bodies were inspected, including the actual timestamped PDF documents rather than only Wayback viewer shells. Transient connection refusals were retried serially, and gzip-encoded archive content was decoded before inspection. Current Reason help text was also checked through the publisher's article JSON API when its HTML pages blocked direct access. The blocked Shimano/CPSC pages were read through their verified captures; the proposed agreement was also readable at GovInfo. No citation was left live-only. Archive dates were derived from the exact replay timestamps. Author names and url-status fields were preserved on retained references; whole citations were removed only where replaced, irrelevant or no longer supporting the retained claim, not to suppress maintenance messages.
All five saved revisions were read back against their drafts and parsed. Sections and references render without article redlinks, reference errors, CS1 errors or missing required Cargo-field categories. Happy to restore trimmed material with suitable sourcing. — WTFelvemage (talk) 03:57, 16 November 2026 (UTC)
- Just did the Shimano one. Have removed the stub notice but had to make significant edits to ensure the article was clear for readers.
- I had to change quite a lot because the edit made it extremely unclear as to the actual problem re. the locked down components. You deleted "Customers with Shimano motors including the EP6 and EP801 are restricted from connecting electrical equipment such as lights to their e-bikes. Special software and hardware primarily used by bike shops is required to activate ports or accept new devices." and replaced it with "The October 2023 E-TUBE PROJECT Cyclist manual distinguishes switching lights on or off with a configured control from changing the drive unit’s light/accessory terminal settings. For the DU-EP801/DU-EP600 section, it directs users to the place of purchase for settings made through E-TUBE PROJECT Professional.", which is near-incomprehensible for someone not well-versed with the issue.
- I've re-added the original and left your version in as well because I don't really understand the full situation, but safe to say it needs a bit of a tidy-up.
- Similarly I also added "due to a high rate of mechanical failure" to the crankset bit so that the situation is clear to the reader.
- Given that these edits appear to be primarily AI-driven, I would suggest taking greater care in ensuring that original article text is preserved where sensible, and in ensuring that the output is readily understandable by a non-technical human.
- Going through the rest of them now. Keith (talk) 11:28, 16 November 2026 (UTC)
- Other notes on the consistent style issues in these edits:
- you are often over-attributing. an in-text attribution for facts as simple as the founding date of a company just bloats the text. Citations are fine for such things
- as discussed in the previous comment, descriptions of events are often overly precise and technical and do not give the reader enough basic context/information to properly understand the issue.
- Consumer Impact summaries are a bit all over the place. i know this isn't particularly standardised sitewide, but you should try for some consistency here.
- just finished going through the Reason Studios one, the above issues were present. Keith (talk) 11:51, 16 November 2026 (UTC)
- More thoughts @WTFelvenmage :
- the edits seem to be overly deferential to the wording used by companies in their explanation of situations. While some people on here can certainly be overzealous at times, I think these edits swing too far in the other direction.
- you really are far too willing to delete existing text and wordings where not necessary or productive
- where there's something that's probably true (e.g. a company being founded in 2018 when its first product was known to have been launched in 2019) but your bot can't verify it, use the Citation Needed template instead of deleting the text outright
- the article leads should take into account the fact that this is the consumer rights wiki, and aim to offer information relevant to the consumer as well as basic factual info about the company and when it was founded.
- you keep making weird meta-commentary on the reporting, e.g. "The reporting distinguished leak precise locations for about 460,000 vehicles from the broader set of records." in the Cariad one. Ok? So what? It just feels like a weird non-sequitur.
- You should definitely examine some of your previous edits with the mind to check for regressions similar to the ones seen here.
- I've now been through the 5 revisions in this thread. haven't fixed everything but have left things like [clarification needed] where needed. Keith (talk) 15:51, 16 November 2026 (UTC)
- Understood, Keith, and I’m sorry for making the articles harder to follow and creating extra work for you. You’re right: the edits lost useful context, removed too much existing wording, and buried the consumer issues in technical detail. I’ll preserve sensible text and make sure future edits are clear to a non-technical reader, with the consumer impact kept front and centre. I’ve taken your feedback on board and will make sure this doesn’t happen again. Thank you for taking the time to review and correct them. — WTFelvemage (talk) 19:16, 16 November 2026 (UTC)
Forced cloud expansion and stub review (16 November 2026)
- Forced cloud (rev 72283): expanded the short, uncited theme article into a sourced explanation of cloud dependence, its effects on owners, six documented cases, designs that preserve continued use, and consumer-protection proposals. The StubNotice line and existing categories were preserved; requesting review and removal of the stub notice if the expansion meets the requirements.
The lead and explanatory sections start with what owners can lose: working equipment, previously included features, or connections to other devices. The case summaries cover Revolv, Insteon, Miku, Chamberlain myQ, Spotify Car Thing and older Nest Learning Thermostats. They distinguish complete loss of operation from retained local functions. Insteon's incomplete initial restoration and new subscription are stated; Miku's retained local audio/video and paid features are separated. The 2023 myQ cloud block and the new Security+ 3.0 hardware restrictions are kept distinct, with the loss of third-party compatibility explained before the company's attributed rationale. Nest's cutoff and consequences are described as its announced policy rather than independently verified implementation.
Corrections and removals: retained the original Windows 11 and YouTube examples, but distinguished initial setup from continuous connectivity and periodic subscription-download checks from unconditional deletion of all downloads. Replaced the unsourced blanket claim that manufacturers have little reason beyond personal gain with documented effects and attributed proposals. The original unsupported Fire TV launcher claim was not carried forward because its blanket wording was not verified. The standalone centralization label and external local-first comparison were replaced by the sourced explanation of local versus server-dependent control; the substantive ownership, privacy, lock-in and offline-function concerns remain. No existing reference definitions were removed because the baseline had no inline citations. Happy to restore omitted material with suitable sourcing.
The safeguards section explains local control, direct app-to-device connections and replacement software in ordinary language; it does not recommend specific products or claim that local operation removes the need for security maintenance. The October 2026 Connected Device Longevity Act is explicitly described as model legislation, not enacted law, including reasonable support expectations, notice requirements, the manufacturer sales restriction, and conditions for an earlier support cutoff.
Source verification: all 18 cited sources were opened and their relevant contents checked. This included the consumer-group FTC letter, Consumer Reports longevity report/model legislation and Miku acquisition notice; the image-only Miku notice was read through OCR of its rendered pages and cross-checked with reporting. Direct visual verification could not be completed because the configured vision service returned a model-not-found error. All citations have access dates and url-status fields. Archive limitation: exact-URL CDX requests and the final save/replay probes failed with TLS unexpected-EOF errors. An availability lookup did identify a snapshot of the FTC letter, but it could not be replay-verified and was not substituted. All 18 references are therefore live-only in this revision:
The saved article was read back against the draft and parsed: all 19 section entries and references render, with no article redlinks, reference errors or CS1 error categories. Only Forced cloud was edited; linked incident articles were not changed. — WTFelvemage (talk) 21:48, 16 November 2026 (UTC)
Done. — Sojourna (talk) 03:21, 17 November 2026 (UTC)
|