Consumer Rights Wiki talk:Moderators' noticeboard/Archive 9
Add topic| This is an archive of past discussions about Consumer Rights Wiki talk:Moderators' noticeboard. Do not edit the contents of this page. If you wish to revive an old discussion or start a new one, please do so on the current talk page. |
Archive everything
[edit source]is there a way the checking process for refs be automated? it is user maintained and isn't always accurate. perhaps all refs could be checked if they have the archive-url= filled? SinexTitan (talk) 18:26, 5 April 2026 (UTC)
- Bots existed on Wikipedia that automatically archived links, but for complicated/opaque reasons didn't sustain operation. Probably a big project. Is that what you mean? Weirdly, Wikipedia insists on archive-date, even though generally it's in the archive-url.
- On a somewhat related note - @Sojourna, the link you added [1] doesn't really work. Maybe use a better archiving service? .is or ghostarchive? .is usually does a better job than .org with such content and the archives are not prone to become unavailable (i.e. hidden by robots.txt changes). CrookKilla (talk) 04:51, 11 August 2026 (UTC)
- From what I recall, Ghost Archive and Megalodon did not fare as well when I attempted to archive MegaLag's YouTube Community post; both were not displaying the second image in said post. And Archive.today is blacklisted on CRW owing to its owner's actions early this year that brought its credibility into doubt.
- The capture I used from Internet Archive loads rather slowly, but it does display all the important parts. — Sojourna (talk) 04:59, 11 August 2026 (UTC)
- Projects:Archive_everything#Archival_services is incredibly one-sided. I disagree with the blacklisting. Reasons:
- There was no significant archive tampering. The way what did occur is described on the pages linked to from there calls into question the reliability of the narrator/narrative found on those pages.
- By contrast, we KNOW archive.org is likely to take down content essentially upon request by the archived site. For defensible reasons, but ones that make it markedly less useful for a Consumer Rights Wiki that is typically documenting bad behavior the actor typically wishes to hide!
Recent examples noted: https://x.com/archiveis/status/2014729926847373506 , https://x.com/archiveis/status/2013987834022043841
- By contrast, we KNOW archive.org is likely to take down content essentially upon request by the archived site. For defensible reasons, but ones that make it markedly less useful for a Consumer Rights Wiki that is typically documenting bad behavior the actor typically wishes to hide!
- "bizarre internet argument" is an inappropriate way to describe getting upset because someone ( Jani Patokallio ) was trying to doxx their staff, which I *think* is what was happening.
- Doxxing isn't okay, we agree?
- Rampant self-censorship to avoid all controversy bad, we agree?
- It's claimed "there's also a very real risk that they just take the site down" - claim lacks evidence.
- Probably many more; there's plenty I haven't read on the topic. I could be wrong, but I have looked well below the surface, and I use the site regularly. I'm a fan of IA, but... well, archive.is usually works better.
- They state, "among our users who are particularly wary of the FBI, there are also less frequently mentioned groups, such as environmental activists or right-to-repair advocates." src
- There was no significant archive tampering. The way what did occur is described on the pages linked to from there calls into question the reliability of the narrator/narrative found on those pages.
- Its page notes: "In early 2023, a team of researchers at the University of Amsterdam identified archive.today as the most-used open-access archiving service among fact-checking organisations."
- I would like to know what others who haven't assumed Wikipedia made the right decision think. It's notable how much discussion it's engendered - 5 RFCs on the topic... clearly there's lots of disagreement.
- - CrookKilla (talk) 07:58, 11 August 2026 (UTC)
- @CrookKilla, from what I've seen, the 'doxxing' only ended up going as far as saying the owner is Russian, which isn't any info at all considering that the owner refuses to let content get removed, including some that can doxx people themselves.
- Archive.today is definitely the best, and while it can be taken down at any time due to only having ONE owner, that is very unlikely, and for all we know the IA could suddenly shutdown.
- I agree that there wasn't much archive tampering, but since this site is owned ny pne person, they can do what they want with the archives and can very easily tamper more.
- Also, we don't want to be directing our users to a site that DDOSes a blogger's website.
- (Noting that I'm the one who told this issue to Keith) AnotherConsumerRightsPerson (talk) 06:31, 23 August 2026 (UTC)
- Thanks for being the first to engage. From what I've seen, the doxxing involved disclosing what were believed to be the full names of people behind the site. A GDPR complaint was filed.
- What does "including some that can doxx people themselves" mean? Garbled? ("ny pne" too.)
- Who says Brewster Kale would have a harder time tampering with the archives? I understand the DDoS is disabled (and prior to that, fetches were modified to be so limited as to be merely symbolic.)
- "Archive.today is definitely the best" - for archives that have the persistence required for a Consumer Rights Wiki? Possibly. Certainly better than IA's. CrookKilla (talk) 06:37, 1 September 2026 (UTC)
- Projects:Archive_everything#Archival_services is incredibly one-sided. I disagree with the blacklisting. Reasons:
Terms of Service info to share...
[edit source]Talk:Terms_of_service#Terms_of_Service_info_to_share... Feedback, anyone? CrookKilla (talk) 03:10, 11 August 2026 (UTC)
Re: Question regarding what can be added to a page.
[edit source]Heyo,
I occasionally edit stuff on the Honda company page regarding data breaches and their data collection.
Is there any restrictions to adding links that can allow users to request control? Specifically I was interested in adding this link somewhere: https://www.honda.com/privacy/disconnect-remote-vehicle-access which allows users to disable remote features on their car, allow users to retain some more privacy controls over their vehicles from Honda.
Best, Em Emlynet (talk) 20:29, 16 August 2026 (UTC)
- Just go for it, although I'm honestly not sure if it's allowed. AnotherConsumerRightsPerson (talk) 06:27, 18 August 2026 (UTC)
Templates and Bots
[edit source]Hope we can import better templates and get some bots working. Any plans for this?
e.g. {{Archives}} is not going to scale and doesn't support search. CrookKilla (talk) 22:34, 19 August 2026 (UTC)
- We had a bot that ran for a while before (Bananabot) but it hasn't been run since February, and I'm sure if anyone wants to make a bot it'd get approved!
- Templates could definitely be improved, especially if we give more of them Lua support. Sadly, since I don't think any of us know Lua, we're currently relying on Wikipedia for our few Lua modules. AnotherConsumerRightsPerson (talk) 20:17, 2 September 2026 (UTC)
Userify JS article
[edit source]I guess this is an appeal to the deletion notice on this article
I propose to move it to my space (even without redirects), please. To preserve revisions/history, and to have it as a sort of "archive" so that it can be easily restored in the future Rudxain (talk) 05:15, 23 August 2026 (UTC)
Better Logo instructions
[edit source]I want to replace the text "Upload an image of the company's logo" that appears when making a new company page, e.g. at https://consumerrights.wiki/index.php?title=Special:FormEdit/Company/Instacart&preload=Template%3ACompanyPreload should say something like
- Upload an image of the company's logo or, if it already has a logo on Wikipedia / Wikimedia Commons, you can just provide the name of the logo file, thanks to https://www.mediawiki.org/wiki/InstantCommons.
Longer instructions: For a company, do they have a wikipedia page? e.g. for https://en.wikipedia.org/wiki/Instacart, we can mouse over the logo and see "Instacart_logo_and_wordmark.svg" at the end of the URL. We can just paste that ("Instacart_logo_and_wordmark.svg") into the field on the page.
Speaking of the form, why ask for a description and not use it? It's put into the Description= field, but the contents of that field are not displayed on the page. Is this a bug in {{CompanyCargo}} or intentional? CrookKilla (talk) 18:33, 24 August 2026 (UTC)
Request for neutral review of a userspace draft (COI disclosed): Sony India BRAVIA warranty denial and legal notice
[edit source]Requesting neutral review of a userspace draft before any move to mainspace: User:Laxmimerit/Sony India remote warranty denial and legal notice to BRAVIA owner.
COI Disclosure: I am the consumer in the dispute the draft describes, so under the conflict of interest policy I am not moving it myself.
Why I think it meets the inclusion guideline: the subject is a practice, not a single service complaint. Sony India decided warranty eligibility from technician photographs reviewed remotely on WhatsApp, with no test or written report, and then served a legal notice threatening a ₹5 crore claim on the consumer for publishing the correspondence while a statutory consumer complaint was pending. As of 3 September 2026 the story has been reported by six outlets (Times Now, News18, Digit, LatestLY, Sportskeeda, Gizbot), all cited in the draft, and other owners have described the same photo-based "external damage" findings in the Reddit thread cited.
The draft uses plain-text reference addresses because the abuse filter blocks external links in userspace. If an editor moves it, I will supply the same references as Cite web templates with url= parameters, or convert them on request. Happy to make any changes asked for on the draft's talk page. Laxmimerit (talk) 11:58, 3 September 2026 (UTC)
- Hi @Laxmimerit!
- I've taken a look at the article, and I think it looks good! there are a sufficient number of external sources to meet notability and merit a movement to mainspace, so I'm happy to make the move. Keith (talk) 19:38, 3 September 2026 (UTC)
- i've also confirmed your account, so you shouldn't have any trouble with user pages in future. Keith (talk) 19:46, 3 September 2026 (UTC)
- Thank you so much Laxmimerit (talk) 13:07, 4 September 2026 (UTC)
- i've also confirmed your account, so you shouldn't have any trouble with user pages in future. Keith (talk) 19:46, 3 September 2026 (UTC)
Appeal: Incomplete on Sony BRAVIA pre-Android Linux TVs (2011-2012) — citations replaced with manufacturer documents and Internet Archive snapshots
[edit source]Requesting review of the {{Incomplete}} notice on Sony BRAVIA pre-Android Linux TVs (2011-2012), following a rewrite of its sourcing.
COI disclosure: I own two of the televisions described and I maintain the research repository the article previously cited. Because of that I am not removing the notice myself, and I have deliberately demoted my own repository to a methodology reference only — it is cited once, for how to reproduce a check, and never as the evidence for a claim.
Why the notice was fair. The notice asks for verifiable, credible evidence and names forum posts and personal blogs as what to avoid. As published, the article's three citations were my own GitHub repository, a GitHub discussion I opened, and a Serviio forum thread. That is precisely the pattern the notice describes, and it was a correct call.
What has changed. Every load-bearing claim is now cited to one of three source types:
- The manufacturer's own documents, at manufacturer URLs. Sony's application catalogs are still served today, and they are the evidence: the European catalog for this chassis generation offers eight applications, the Brazilian catalog offers two. The Sony-supplied manifest for one withheld application carries localized names in thirty languages including Portuguese; the Sony-supplied dictionary for another covers thirty-one languages with the Portuguese entries complete, down to "Rio de Janeiro" appearing in its timezone city list. Sony's own Source Code Distribution Service states the GPL obligation in Sony's words.
- Internet Archive snapshots of Sony's own pages. A October 2014 snapshot of Sony's source-code service lists this television generation by model number, including both sets I own; a July 2015 snapshot of the corresponding download page lists the twenty-three source packages that were offered. Those download links return HTTP 404 on Sony's live server today, while the same service currently lists 798 other KDL-series models.
- Independent third-party review. The technical finding behind the 3D incident was submitted to the HandBrake project, which reviewed it and merged a patch implementing the fix. That is an independent project accepting the diagnosis on its merits, which seemed a better citation than my own write-up of it.
One incident is still weakly sourced, and the article says so. The January 2022 firmware-removal incident rests on owner observation. I searched the Internet Archive for snapshots of Sony support pages for these models and found none. Rather than leave that implicit I have marked it inline in the article. If the preference is to remove that incident until it can be independently sourced, I will do that on request — I would rather the article be shorter and fully sourced than complete and partly unsupported.
On archived links. I saw the "Archive everything" discussion above. The Sony URLs cited live were not previously in the Wayback Machine, so I have submitted them and added archive-url= alongside each. This matters beyond citation quality: the article's strongest evidence currently sits on servers the manufacturer could withdraw at any time, exactly as it withdrew the source-code downloads.
Why I think it meets the inclusion guideline. The subject is a practice rather than a single consumer's complaint. Applications that were finished, localized and shipped to the manufacturer's servers were never offered in some markets, and the sets were then abandoned in that state; the source code the licence requires was published and later withdrawn while the same service continues for newer models. Both affect an entire television generation — one service manual alone covers five screen sizes — not the two sets I happen to own.
Happy to make any changes asked for, here or on the article's talk page. Capitain jack (talk) 21:25, 17 September 2026 (UTC)
- '''Follow-up, 18 September 2026 — the work has continued and the one gap the appeal named is now closed.''' Recording this here so the thread stays current. I am not asking for a faster decision; the notice can stay until a moderator has time.
- '''The weakly-sourced incident is resolved, and it also corrected an overclaim of mine.''' The appeal flagged the January 2022 firmware-removal incident as resting on owner observation. Sony's own Brazilian support site now settles it: in place of a download it serves a notice headed "Encerramento do software de atualização da TV", with a model checker that returns my KDL-46HX855 as affected and names its latest software as PKG2.120BRA. I have archived that page. Reading it also showed my original wording was too strong: the page routes an affected owner to a support contact rather than leaving no path at all, so I have rewritten the incident to what the page actually supports — no self-service download remains, and recovery depends on a discretionary support request or on third-party archives. I would rather the claim be narrower and exactly true.
- '''Sony's own dated end-of-service notices, for five separate services, each naming both sets.''' Since the appeal I have found and archived Sony Brasil's per-service shutdown announcements, one article per service, each listing KDL-46EX725 and KDL-46HX855 by model number among roughly a hundred and thirty sets:
- Facebook application, withdrawn from 27 April 2015 (Sony article S1Q2489).
- Skype, ended 30 June 2017 after prior withdrawal in June 2016 (S1Q2505).
- Video & TV SideView second-screen companion, TV functions ended 24 May 2017 (S1Q2517).
- Artist Information and TrackID music recognition, declared no longer functional (S1Q2522).
- Twitter / TV Tweet, removed March 2018 after a Twitter login-API change (S1Q2540).
- These are corporate communications on the manufacturer's own domain, dated, model-specific, and now permanently held at the Internet Archive.
- '''Independent reporting, and the same notices in other regions.''' Three of the shutdowns also have independent coverage, which I have cited: TechCrunch on the Skype-for-TV shutdown, 9to5Google on the Twitter wind-down, and Android Police on TrackID (where Sony itself recommended installing Shazam on a phone, rather than restoring the feature on the set). The same Sony notices are published in English by Sony Canada and Sony Latin America under the same article numbers, which confirms these were global communications rather than a local quirk.
- '''One incident added, from Sony's own manual.''' I have added an incident describing that the panel's documented 3D processing, including the 2D-to-3D "Simulated 3D" mode, was never available to the television's own internet and application content, although the same panel switches to 3D from other inputs. It is cited to Sony's own i-Manual for the set, which documents the feature with no input or source restriction on the Simulated 3D mode, and to reproducible owner testing for the observed behaviour. No claim is made about intent.
- '''A note for the Foundation, not a legal claim.''' The two sets are Brazilian-market units and the notices above are Sony Brasil's. I have added a short "Consumer-rights context (Brazil)" section that states the applicable provisions of the Código de Defesa do Consumidor against the sourced facts and draws no legal conclusion. It is flagged in the article as not legal advice and as a matter for the Foundation and Brazilian counsel to assess, not something the article decides.
- '''Still ongoing.''' I am continuing to archive the manufacturer's own support pages as I find them, so more citations of this kind may follow. Happy to change, trim or restructure anything, here or on the article's talk page. If the preference is still to keep the notice in place while this settles, that is fine by me. Capitain jack (talk) 05:27, 18 September 2026 (UTC)
Done. Apologies for the long wait. — Sojourna (talk) 20:21, 28 September 2026 (UTC)
- No worries, you guys are warriors! Thank you! Capitain Jack (talk) 21:12, 28 September 2026 (UTC)
Request: Incomplete removal from Lenovo Mirage AR after product-skeleton restructure
[edit source]The {{Incomplete}} tag on Lenovo Mirage AR reads "Article must follow proper incident page format, or appended to relevant company or product page". I have restructured the article to the product skeleton from {{ProductPreload}} (lead, consumer-impact summary, incidents, see also, references) and addressed the content gaps:
- The 2022 retirement of both companion apps (Star Wars: Jedi Challenges and Marvel Dimension of Heroes) is now an Incidents subsection, cited to the Star Wars Support and Disney Games and Apps Support retirement notices, both held at the Internet Archive (2022 and 2024 snapshots).
- The lead is cited for the 2017 launch, bundle contents and $199 preorder price (CNET, archived).
- The consumer-impact summary now explains the mechanism (smartphone-dependent headset, no onboard processing) rather than asserting conclusions, and quotes the no-refunds position from the retirement notices.
- Mechanical fixes: the floating uncited reference and bare
<references />were replaced with proper {{Reflist}} citations; the emptyWebsiteand multi-valueCompanycargo fields were cleaned up.
Two questions: (1) can the Incomplete tag come off, or is more work wanted first? (2) If the preference is instead to append this material to a company or product page and redirect, I can do that — but since the headset is the shared hardware across two retired app ecosystems, a standalone product page seemed the better home. Happy to adjust either way. — WTFelvemage (talk) 23:38, 27 September 2026 (UTC)
Done. — Sojourna (talk) 20:31, 28 September 2026 (UTC)
Request: SloppyAI removal from KPN mandatory SMS authentication
[edit source]The {{SloppyAI}} tag on KPN mandatory SMS authentication appears justified by the previous state of the article: raw markdown (bold markers, parenthetical bare links) pasted directly into wikitext. I have rewritten the article (rev 69338) and would appreciate a mod's eye on whether the tag can come off:
- All markdown converted to proper wikitext; all three sources converted to {{Cite web}} with archive links and translations of the Dutch titles.
- The previous text dated the rollout to "early 2024"; the cited Security.NL article (and KPN's own community FAQ) places the phased rollout in July 2025, mandatory for all customers from 5 August 2025. The IncidentCargo StartDate is corrected accordingly.
- The empty "Lawsuit" section (which stated no lawsuit exists) was removed.
- New, verified content: KPN added an authenticator-app option on 23 April 2026, so SMS is no longer the only method; the article now reflects both the original SMS-only situation and this update.
Sources: Security.NL, KPN's official community FAQ thread, and a KPN community thread with a moderator reply — all archived at the Internet Archive. WTFelvemage (talk) 23:54, 27 September 2026 (UTC)
Done. — Sojourna (talk) 20:38, 28 September 2026 (UTC)
Request: Incomplete removal from Scribd after tone and citation overhaul
[edit source]The {{Incomplete}} tag on Scribd predates a rewrite I just completed (rev 69340). Requesting a mod's judgment on whether it can come off:
- The article's only incident was written in editorial voice ("classic predatory scheme", accusatory image captions) with zero inline citations for its claims. It now states the same facts neutrally — payment details required at trial sign-up, temporary card verification charge, automatic monthly renewal — each cited to Scribd's own help-center articles (How to subscribe, Pending transactions during your free trial, Downloading documents, Upload benefits), all archived at the Internet Archive.
- The lead is now cited (About us, archived), the malformed citation (archive link outside the template, wrong parameter) is fixed, and the empty CompanyCargo Description is filled.
- Image captions rewritten to describe rather than accuse; both screenshots retained.
- Added a See also section linking {{Dark pattern}} and {{Click-to-cancel}}.
One editorial question: the previous text claimed the upload-for-download alternative is "written in small text and placed at the bottom of the page" to imply intent. I dropped that characterization since I can only verify the program's existence, not its visual prominence — but if the community considers it relevant, it could be restored with a citation. WTFelvemage (talk) 00:21, 28 September 2026 (UTC)
Done. On its own, I'm not sure it's worthwhile to include that bit unless it could be established as part of an overall pattern of behavior. The links in the see also section are fine in the meanwhile. — Sojourna (talk) 20:55, 28 September 2026 (UTC)
Request: Incomplete removal from BowFlex after CompanyPreload restructure
[edit source]The {{Incomplete}} tag on BowFlex lists two issues: "more research & references needed" and "Needs to be formatted to Template:CompanyPreload". I have reworked the article (rev 70031) and would appreciate a mod's judgment on whether the tag can come off:
- Restructured to the company skeleton: consumer-impact summary (privacy/user freedom subsections at correct heading levels), incidents, references. Fixed the heading-level skips (==== directly under ==) flagged implicitly by the skeleton mismatch.
- Added a "Chapter 11 bankruptcy and sale (2024)" incident section (March 2024 filing, April 2024 court-approved $37.5 million sale to Johnson Health Tech Retail), cited to The Columbian and the CPSC recall notice.
- Rewrote the recall section around the CPSC announcement itself (regulator source instead of a secondary health-news site): about 3,844,200 units across models 552 and 1090, 337 Nautilus dislodge reports including 111 injuries, and the voucher/prorated-voucher remedy. All three new sources archived at the Internet Archive.
- Added citations for the previously uncited claims: the locked-down Android build and preinstalled-app-only streaming on JRNY machines (Android Police review), and the data-sale opt-out bullet (the already-cited privacy policy).
- Fixed the empty <syntaxhighlight lang="wikitext" inline style="display: none;" />
|access-date=on the old drugs.com ref by replacing it with the CPSC primary source, and corrected the CompanyCargo parent/type to reflect the Johnson Health Tech acquisition.
The research-and-references gap is addressed to the extent the available sourcing allows; happy to keep digging if a mod sees remaining gaps. WTFelvemage (talk) 01:47, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:49, 14 October 2026 (UTC)
Request: Cleanup removal from Forced BIOS firmware update (citation placement)
[edit source]The {{Cleanup}} tag on Forced BIOS firmware update lists a single issue: "References should be placed after punctuation." I have moved all 27 misplaced inline citations to after their sentence/clause punctuation (rev 70033), with no content changes — ref count, headings, and text are identical to the prior revision. Requesting removal of the now-addressed tag. WTFelvemage (talk) 01:48, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:49, 14 October 2026 (UTC)
Request: Incomplete removal from Dairy Queen after CIS expansion
[edit source]The {{Incomplete}} tag on Dairy Queen reads "expand CIS with the 4 fields". I have expanded the consumer-impact summary to all four preload fields (rev 70035) and would appreciate a mod's judgment on whether the tag can come off:
- Added the missing Market control field: the nearly-all-franchise ownership structure, and the Collins v. International Dairy Queen, Inc. (M.D. Ga. 1996) certified franchisee class action alleging a Sherman Act §1 tying arrangement (defendants' summary-judgment motion on the tying claims denied).
- Replaced the two previous privacy-policy citations, which pointed to unofficial lookalike menu domains (daiiryqueenmenu.us, dairyqueenmenus.org), with the official Dairy Queen privacy statement (archived), and rewrote the privacy and user-freedom bullets to match what that statement actually says.
- Fixed heading casing (Users Privacy → User privacy etc.), lead grammar and founding date consistency, and typos in the incident sections.
Note: the Justia page for the Collins case would not archive (Wayback save 520), so it is cited live. WTFelvemage (talk) 01:55, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:49, 14 October 2026 (UTC)
Request: Incomplete removal from Google Chrome automatically disables uBlock Origin after MV3 update
[edit source]The {{Incomplete}} tag on Google Chrome automatically disables uBlock Origin asks for up-to-date information on the current state of Manifest V3. I have updated the article (rev 70037) from the official Chrome Manifest V2 support timeline (all dates verified against that page, freshly archived):
- Added the completed phase-out timeline to the Manifest V3 section: the March 31, 2025 default-disable with re-enable option, the Chrome 138 hard disable of July 24, 2025, the removal of the ExtensionManifestV2Availability enterprise policy with Chrome 139, and the August 31, 2026 removal of all remaining Manifest V2 extensions from the Chrome Web Store.
- Filled the previously empty Google's response section (Google's stated security rationale and the staged phase-out as presented on its own timeline), removing the {{Incomplete section}} placeholder.
- Added a sentence to Consumer response noting no workaround remains on current Chrome versions.
- Updated the IncidentCargo to EndDate 2026-08-31 / Status Resolved, matching the final store removal — flagging this cargo change explicitly in case a mod disagrees.
Requesting judgment on whether the tag can come off. WTFelvemage (talk) 01:57, 13 October 2026 (UTC)
- Removed the Incomplete tag since I believe it's as complete as it can be. I don't know if "Resolved" is the right one for the cargo status, because it could be confused for being fixed, but I don't have any better ideas either. — Sojourna (talk) 02:56, 14 October 2026 (UTC)
Request: Incomplete removal from HP 15-minute phone wait article
[edit source]The {{Incomplete}} tag on HP adds 15 minutes to all customer service phone calls lists two issues: wiki self-citation, and a background section not directly related to the incident. Addressed both in rev 70039:
- Removed the commented-out citations to the Rossman Group wiki entirely (the previous editor had already commented them out pending removal).
- Reworked the background to the directly related and cited material (the internal "warranty cost efficiencies"/"digital adoption" documents and the CFO digital-ecosystem statements, all to The Register).
- Moved the related-but-not-directly-relevant printer-business practices (Instant Ink, Dynamic Security, ink-locking) into a new See also section as internal links, so the context remains navigable without uncited claims.
- Fixed stray ampersands in prose.
Requesting judgment on whether the tag can come off. WTFelvemage (talk) 01:58, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:56, 14 October 2026 (UTC)
Request: Incomplete removal from ASUS VG259QM panel switch after incident conversion
[edit source]The {{Incomplete}} tag on ASUS downgrades a well-reviewed monitor panel lists two issues: improper external linking, and conversion to the incident skeleton. Both addressed in rev 70041:
- Restructured to {{IncidentPreload}}: lead summary, Background, Silent panel switch (2022) with an ASUS's response subsection, and Consumer response; references now render via {{Reflist}} instead of a bare
<references />. - Replaced the two inline external links in the lead with proper citations (the panelook pages are now cited only through {{Cite web}} templates, with a new citation for the AUO panel).
- Replaced {{ProductCargo}} with {{IncidentCargo}} (Company=Asus, StartDate=2022-07, Type=Poor Quality, Anti-consumer Behavior) and the self-named category with Category:ASUS — flagging the cargo/category conversion explicitly in case a mod wants different incident-type values.
- Removed the empty See also section and an editorial HTML comment; rephrased informal prose ("sounds the alarm", "unfortunate incident") neutrally; kept the carefully-worded no-direct-evidence framing on intent intact.
Requesting judgment on whether the tag can come off. WTFelvemage (talk) 01:59, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:58, 14 October 2026 (UTC)
Request: Cleanup removal from Subaru Starlink after preload restructure
[edit source]The {{Cleanup}} tag on Subaru Starlink lists two issues: citation placement after punctuation, and conformance to {{ProductLinePreload}} format. Both addressed in rev 70043:
- Moved the three misplaced citations after their punctuation.
- Restructured to the ProductLine skeleton: the thematic sections (Data collection, Data sharing and sales, Privacy concerns, Technical details, Consumer-protection issues) now sit under a Consumer-impact summary section placed before Incidents, with heading levels corrected throughout (no level skips).
- Fixed nonstandard date formats in prose (verified against Sam Curry's disclosure timeline: report November 20, 2024; blog post January 23, 2025).
- Cited the two previously uncited paragraphs of the app-exploit incident (both sourced from the Curry writeup, now a named reference) and filled the empty cargo Description.
Requesting judgment on whether the tag can come off. WTFelvemage (talk) 02:20, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:58, 14 October 2026 (UTC)
Request: Cleanup removal from Data lock-in (citation formatting, archive.today)
[edit source]The {{Cleanup}} tag on Data lock-in lists two issues: unformatted references, and archive.today usage. Both addressed in rev 70046:
- Converted all 24 bracket-style citations to {{Cite web}} (url/title/archive-url/access-date/website; authors and dates where the source text carried them; <syntaxhighlight lang="wikitext" inline style="display: none;" />
|trans-title=added for German-language sources). - Replaced the four archive.today links with web.archive.org captures: two had existing Wayback snapshots (Golem, Telekom Profis), one wrapped a Wayback URL of the Telekom announcement (used directly), and the WhatsApp FAQ page was freshly captured today before the swap.
No content changes. Requesting judgment on whether the tag can come off. WTFelvemage (talk) 02:25, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:58, 14 October 2026 (UTC)
Request: Cleanup removal from Google Pixel (citation authors and formatting)
[edit source]The {{Cleanup}} tag on Google Pixel lists two issues: reference formatting, and missing author names on the Reddit citations. Both addressed in rev 70048:
- Added author usernames to the three Reddit citations that lacked them (<syntaxhighlight lang="wikitext" inline style="display: none;" />
|author== Federal-Gas9517, Apprehensive-Low1765, Wim-1), verified against the submissions' metadata; all six Reddit citations now carry authors. - Normalized citation whitespace (collapsed double spaces inside {{Cite web}} invocations); every citation already carried an access-date and archive link.
No content changes. Requesting judgment on whether the tag can come off. WTFelvemage (talk) 02:27, 13 October 2026 (UTC)
Done. — Sojourna (talk) 02:58, 14 October 2026 (UTC)
Stub notice removal requests (2026-10-22)
[edit source]Requesting removal of {{StubNotice}} from three incident articles expanded into the full incident skeleton (revisions verified, no redlinks, all claims cited with archived sources):
- Goodlife now requires app to access gyms (rev 70451) — restructured into incident skeleton, refs converted to cite templates, app mechanics added from official pages.
- GoPro advertises waterproof cameras despite design flaw and lack of warranty (rev 70452) — neutral-tone rewrite per earlier Talk feedback, Cargo fields filled, consumer response added. Also flagging the title tone here for a moderator's judgment; a move to something like "GoPro HERO12 Black waterproofing warranty discrepancy" would match the editorial guidelines.
- Google password manager overrides third-party autofill (rev 70450) — expanded with Chromium cause, Google's response and consumer response; the {{Stub}} tag was removed in this edit and I am noting it here for confirmation rather than unilateral action.
WTFelvemage (talk) 03:14, 22 October 2026 (UTC)
- The stub tag should remain on the first two; I have added sections that were missing on the pages. — Sojourna (talk) 05:48, 22 October 2026 (UTC)
Stub notice removal requests (2026-10-22, second batch)
[edit source]Two more expanded incident articles, same treatment as the batch above:
- Instagram removes end-to-end encryption for direct messages (rev 70456) — filled the Background, Meta's response and Consumer response sections (replacing {{Ph-I-*}} placeholders), corrected dates against The Verge, The Hacker News and BBC sources. StubNotice retained, requesting removal.
- Chrome OS ends support for school Chromebooks (rev 70457) — Talk-page feedback showed the original premise was wrong (the Lenovo 300e 2nd Gen expires Jun 2029 per Google's AUE table, not 2025). Rewritten around the verifiable story: the PIRG Chromebook Churn criticism and Google's 10-year update policy. {{Stub}} retained, requesting removal — and the title itself likely needs a move to something like "Chromebook automatic update expiration", which needs a moderator.
WTFelvemage (talk) 03:21, 22 October 2026 (UTC)
- Removed stub for the Instagram incident. Keeping it for now for the Chrome OS page since it does not have a consumer response. — Sojourna (talk) 05:58, 22 October 2026 (UTC)
Stub notice removal requests (2026-10-22, third batch)
[edit source]Five more expanded articles, same treatment as the batches above (verified sources, no redlinks, no maint categories):
- HP India fined ₹1.4 billion for "cartelization" of ink cartridges, toner, PCs (rev 70461) - placeholders filled from CCI coverage; corrected penalty figures (two CCI orders totaling ~INR1.38B, per law.asia and Ars Technica). {{Stub}} retained.
- JetBrains retires CodeCanvas (rev 70466) - fixed malformed level-1 heading, restructured into incident skeleton, JetBrains response added. {{StubNotice}} retained.
- Good2Go Mobile (Canada) phases out 3G network, Merges with LuckyMobile (rev 70463) - corrected the unsourced "forced monthly contract" claim to what coverage supports (free Lucky Mobile SIM, balance forfeited, plans from $19/month), added the Ztar-Rogers CRTC dispute as background. {{StubNotice}} retained. Title likely needs a move for sentence case ("Merges" capitalized mid-title) - happy to take suggestions.
- Dead Star server shutdown (rev 70464) - all placeholders filled from Eurogamer/Game Developer; removed empty Lawsuit section; added delisting and Stop Killing Games consumer response. {{StubNotice}} retained.
- Apple authorized service provider program (rev 70465) - filled empty ProductCargo fields, replaced the unsourced "publicity stunt" claim with attributed criticism. {{StubNotice}} retained.
WTFelvemage (talk) 03:39, 22 October 2026 (UTC)
- Moved the Good2Go Mobile page to Good2Go Mobile (Canada) phases out 3G network and merges with LuckyMobile and left a redirect. — Sojourna (talk) 06:01, 22 October 2026 (UTC)
Stub/cleanup tag removal requests (2026-10-22, fourth batch)
[edit source]Five more, same standards (sources verified, renders checked, no redlinks or maint categories):
- Forced User Agreement on Jetbrains IntelliJ software (rev 70468) - converted ProductLineCargo to IncidentCargo and restructured per the Cleanup tag; cited JetBrains' own User Agreement and fallback-license docs. {{Stub}} and {{Cleanup}} both retained - requesting both come off (the Cleanup issue is now fixed).
- Dangerous Syneco 100kg 3 Step Domestic Lite Aluminium Ladder (rev 70469) - added IncidentCargo, restructured into incident skeleton, rewrote the typo-heavy text into neutral sourced prose around the Artisan Makes review. {{StubNotice}} retained, requesting removal.
- Feature ransom (rev 70473) - expanded the theme stub: definition, Impact section, and sourced summaries for the Bambu Lab ACS and Miku examples (Register snapshot 20261004085738). {{StubNotice}} retained, requesting removal.
- Logitech G HUB (rev 70471) - filled the empty ProductCargo fields (ReleaseYear 2018 via TechRadar early-access coverage), added an introduction, moved Linux support into its own section. {{StubNotice}} retained, requesting removal.
- Leadwerks (rev 70472) - neutral-tone rewrite per the ToneWarning: corrected the engine succession (Ultra Engine is the successor, per its Steam listing), sourced the account-requirement claims to the Steam store pages, and removed the unsourced login-blocking claims rather than leave them flagged. {{ToneWarning}} and {{Incomplete}} retained for mod review.
WTFelvemage (talk) 03:48, 22 October 2026 (UTC)
- Removed stub and cleanup tags.
- Changed stub to incomplete.
- Removed stub tag.
- Keeping the stub tag as there were sections missing. Added the placeholders for those.
- Removed the tone warning tag and replaced incomplete with stub. — Sojourna (talk) 06:17, 22 October 2026 (UTC)
Stub/cleanup tag removal requests (2026-10-22, fifth batch)
[edit source]Five more, same standards (sources verified and archived where possible, renders checked, no redlinks or maint categories):
- Adware (rev 70475) - filled all three placeholder sections from security-vendor glossary sourcing (CyberDefenders, archived). {{StubNotice}} retained, requesting removal.
- Legal lockout (rev 70476) - theme stub expanded: Impact section with sourced accept-or-lose framing, example summaries for the Activision Blizzard and Smartwool incidents. {{StubNotice}} retained, requesting removal.
- Liability limits (rev 70477) - restructured and typo-fixed, enforceability limits sourced to contract law explainers (Icertis archived; InterNACHI live - archive.org is intermittently refusing saves tonight). {{Stub}} retained, requesting removal.
- Consumer Advice (UK) (rev 70478) - list converted to prose, Contact section added from the Citizens Advice contact page (0808 223 1133, Mon-Fri 9-5, archived). {{StubNotice}} retained, requesting removal.
- Google Nest (rev 70479) - both Incomplete issues addressed: ProductLineCargo added per the ProductLine format, lineup cited to the Google Store (archived) and brand history to Forbes/The Verge (archived), Consumer impact summary and Incidents structure added. {{Stub}} and {{Incomplete}} retained, requesting both come off.
WTFelvemage (talk) 03:58, 22 October 2026 (UTC)
Done. — Sojourna (talk) 06:23, 22 October 2026 (UTC)
Follow-up: stub/incomplete tag removal requests (2026-10-22 late)
[edit source]Following up on the four pages where tags were kept pending missing sections - all sections are now filled and sourced:
- Goodlife now requires app to access gyms (rev 70651) - Goodlife's response and Consumer response filled; consumer sentiment sourced to App Store reviews via the iTunes review feed (archived).
- GoPro advertises waterproof cameras despite design flaw and lack of warranty (rev 70652) - GoPro's response filled with the subscription damaged-camera replacement program (gopro.com and the official FAQ, both archived); Cargo StartDate set to the HERO12 Black release.
- Dangerous Syneco 100kg 3 Step Domestic Lite Aluminium Ladder (rev 70654) - Background added with Bunnings retail sourcing; noted the ladder remained on sale at review time.
- Leadwerks (rev 70655) - Consumer impact summary and See also filled; engine-compatibility context added from the developer blog.
Requesting the remaining {{StubNotice}}/{{Stub}}/{{Incomplete}} tags come off these four. Thanks Template:Noping for the quick turnaround on the earlier batches. WTFelvemage (talk) 21:54, 22 October 2026 (UTC)
Done. — Sojourna (talk) 00:10, 23 October 2026 (UTC)
Incomplete tag removal requests (2026-10-26)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting {{Incomplete}} removal on each:
- Presonus removes VSL mixing app from VSL audio interfaces products line (rev 70834) — restructured to the product line skeleton (Consumer-impact summary, Incidents, Products); the VSL discontinuation is sourced throughout to the PreSonus discontinuation notice (OS X El Capitan changes, Windows wind-down, Universal Control 1.8); Big Sur incompatibility cited live (archive.org was returning 429s tonight, so three new sources are live with access-dates). Tag retained.
- Samsung Galaxy Z Fold 3's camera gets artificially blocked after unlocking the bootloader (rev 70835) — bare-URL citation converted to {{Cite web}}; Android Authority and Ars Technica coverage added; the One UI 4 beta 2 fix is detailed (including the F926B/F926N model caveat); uncited marketing claims trimmed; cargo description typo fixed.
- Google Pixel Watches do not come with repair options (rev 70836) — the tag's issue (sourcing for all watch generations) is resolved: replacement-only policy now sourced for every generation (Ars Technica for the original, Beebom and Android Authority for the Watch 2 and Watch 3 statements, live); empty Cargo fields (StartDate, Status, Type, Description) filled; the Rossmann video formatted as a proper reference.
- Samsung Gear 360 software and services discontinued (rev 70838) — app reliance and the ActionDirector end-of-download timeline cited to Android Headlines; community reverse-engineering efforts cited to APKMirror (live); capitalization and missing periods fixed.
- Google Pixel Buds "Touch and Hold" discontinuation (rev 70162) — no content edits needed: the article already carries full sections with citations throughout. Requesting the tag come off as-is.
Post-edit parses pass on all edited pages: references render, zero redlinks, no CS1 error or maint categories. Thanks Template:Noping in advance. — WTFelvemage
- Removed the Incomplete tag for all except the Samsung Galaxy Z Fold 3's camera gets artificially blocked after unlocking the bootloader, which I changed to a Stub since I added the consumer response section (which had been missing). — Sojourna (talk) 06:50, 27 October 2026 (UTC)
Incomplete tag removal requests (2026-10-26, second batch)
[edit source]Five more articles from Category:Articles in need of additional work completed, requesting {{Incomplete}} removal on each:
- Google OnHub (rev 70841) — empty User privacy section filled (cloud-only management, sourced to 9to5Google); the 2023 settings shutdown now fully sourced (Ars Technica for the Dec 2021 announcement and 40% Nest Wifi discount; 9to5Google for the Jan 11 2023 date and mesh factory-reset requirement); launch year corrected to 2015; empty Market control and Business model headers removed as unverifiable.
- Unnecessary retirement of Microsoft Office Lens (rev 70846) — grammar and date cleanup; new sources archived (all via existing snapshots); added Consumer response citing Windows Central coverage; stripped url-status flags that tripped a CS1 maint category.
- Chevron (rev 70843) — company intro facts (1879 founding, San Ramon HQ) cited to chevron.com and CFCU's own history page; fixed "Sam Ramon" and other typos; retitled the MOVEit section per the cited coverage. Two removals to flag for mod review: the empty {{Incomplete section}} "Chevron puts ads in gas pumps" subsection (no press coverage found anywhere — the uploaded image alone can't carry an incident per the no-original-research policy) and the unsourced "second highest U.S. oil company / 180 countries" claims. Happy to restore either if anyone has sourcing.
- Apple Self Service Repair (rev 70844) — the previously uncited consumer-impact bullets now sourced: serial-number requirement (PCMag), parts-pairing criticism and right-to-repair legislation context (iFixit), Apple Diagnostics step (Apple Support); removed the unsourced "repair outside approved channels voids warranty" claim (contradicts FTC guidance on warranty-void-if-opened); cleaned raw URLs out of See also.
- Humane Inc. (rev 70845) — empty Cargo Description and ParentCompany filled; company background expanded and sourced to Ars Technica (founders, $230M funding, pricing, ~10,000 orders); consumer-impact bullets sourced to 404 Media; fixed a malformed Engadget archive URL to a verified snapshot.
Post-edit parses pass on all five: references render, zero content redlinks (Apple Self Service Repair's category bar link is red only because the category is new), no CS1 error or maint categories. Wayback's save endpoint was returning 429s for most of tonight, but every new source had an existing snapshot, so all citations are archived. Thanks Template:Noping in advance. — WTFelvemage
- Removed the Incomplete tags.
- Chevron is now a Stub as the CIS section had been missing.
- Apple Self Service Repair is now a Stub; I added missing sections for "Incidents" and "See also". (I also changed the category to point to Apple instead.) — Sojourna (talk) 06:58, 27 October 2026 (UTC)
Do not delete article Remove Your Media
[edit source]Remove Your Media was marked for deletion and I strongly oppose that. Remove Your Media has a history of sending false DMCA notices using bots so it's good to document all of them in this wiki. When the page was marked for deletion, it was still incomplete - I was planning to add more incidents.
I removed Etsy section as requested by mods and added some more incidents. Somehundred (talk) 11:57, 27 October 2026 (UTC)
- I asked in Zulip staff chat yesterday for others' thoughts about the article, but have yet to get a response. I'll try pinging again tomorrow if there's still no replies. — Sojourna (talk) 00:51, 29 October 2026 (UTC)
- I appreciate you removing that section on your own. I made a small edit on the page to guide where there should be expansion. Mr Pollo (talk) 22:02, 30 October 2026 (UTC)
- What sources would be the best to reference licensees/copyright owners of Re:Zero? Should I put a link to a website or reference specific books? I'm relatively new to wiki editing so this is causing confusion.
- And regarding the first citation requirement, this article itself is a source where the incidents are listed and references for these incidents have been provided next to each. The main Incidents section expands on and provides proof for claims in the paragraph in Consumer impact summary.
- The claim next to second citation requirement is supported by the conclusions pulled from the observations and analysis of all the given incidents. In all cases described in this article, the notices sent out are invalid - the targeted content doesn't actually infringe on anyone's copyright. Article and video titles contain names of animated works, videos which have clips of an anime fall under fair use yet they are still targeted by DMCA notices. After reviewing every case, it isn't hard to draw conclusions that no one from RYM is manually verifying the validity of a notice before sending it and that bots are scraping the internet for specific keywords and instantly sending the notice when finding a site it hasn't whitelisted. Some cases are simply hilarious - like the Bleachbit notice where the site was targeted simply because it had the word Bleach in the title when there's also an anime called Bleach. Thus, I believe no citation is needed as this claim is simply derived from fact-driven conclusions.
- Anyone can also edit and improve the article themselves and add the citations they think would benefit. Somehundred (talk) 11:21, 31 October 2026 (UTC)
- I have added an example to the article of what I mean. I utilized this website for U.S. trademark searching. In regards to the licensing, are there press releases/blog posts from one of the companies stating their partnerships? Mr Pollo (talk) 20:34, 1 November 2026 (UTC)
- Can we use these articles from animenewsnetwork?
- https://www.animenewsnetwork.com/news/2015-12-02/yen-press-licenses-asterisk-war-re-zero-manga-light-novels/.96025
- https://www.animenewsnetwork.com/news/2016-03-22/crunchyroll-to-stream-re-zero-starting-life-in-another-world-anime/.100086 Somehundred (talk) 13:29, 4 November 2026 (UTC)
- I have added an example to the article of what I mean. I utilized this website for U.S. trademark searching. In regards to the licensing, are there press releases/blog posts from one of the companies stating their partnerships? Mr Pollo (talk) 20:34, 1 November 2026 (UTC)
Follow-up: sections filled after 2026-10-26 verdicts (2026-10-27)
[edit source]Thanks Template:Noping for the quick verdicts on both 2026-10-26 batches. I have filled the sections you flagged, and request the remaining {{Stub}} tags come off these three:
- Samsung Galaxy Z Fold 3's camera gets artificially blocked after unlocking the bootloader (rev 70898) — Consumer response filled with critical coverage of the camera lockout (The Verge, SamMobile).
- Chevron (rev 70899) — Consumer impact summary filled from the sourcing already in the article (MOVEit breach at CFCU, 90k+ customers, October 2026 settlement).
- Apple Self Service Repair (rev 70900) — Incidents: the category has no standalone incident articles yet, so I removed the example preload text and kept the category pointer; See also now links Apple and Right to repair. Tag retained.
Done. — Sojourna (talk) 00:53, 29 October 2026 (UTC)
Incomplete and stub tag removal requests (2026-10-27, new batch)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting tag removal on each:
- Amazon Luna revocation of third-party games (rev 70893) — the Incomplete issue ("needs more citations beyond a single source") is resolved: Engadget coverage added alongside The Verge throughout; Consumer response filled; empty Cargo fields (ArticleType, Type) filled. Tag retained.
- Amazon revokes access to their Appstore on non-Amazon devices (rev 70894) — Background and Incident sections filled with the Amazon developer notice (20 February 2025 announcement, 20 August 2025 cutoff), the official Appstore FAQ and GamesIndustry.biz coverage; Consumer response sourced to Forbes. All new sources archived (Wayback save endpoint was 429ing, so snapshots are pre-existing ones). Tag retained.
- Google Pixel 9 Pro camera bar separates from phone body (rev 70895) — full incident skeleton filled: camera bar separation incidents (October 2024 and January 2025 cases), Google's response (replacement refusals past 90 days) and ongoing owner reports, sourced to Android Police, TechRadar and Google's support community (community threads cited live; Wayback save was 429ing tonight). Tag retained.
- Bloomberg DMCA strikes GamersNexus video (rev 70901) — restructured to the incident skeleton with TweakTown and Notebookcheck press coverage plus the GamersNexus and Hacker News references already present; Cargo Status/ArticleType/Description filled. One removal to flag for mod review: the empty {{Ph-I-L}} Lawsuit placeholder section — no lawsuit has been filed according to the coverage. Also cleared a pre-existing CS1 maint category (numeric-names author field). Tag retained.
- Boris FX deactivates "legacy" Mocha Pro licenses (rev 70897) — copyedited (sentence-case heading, grammar), added a Boris FX response section from the company's own help center (FlexLM end-of-life notice and License Options, archived), and background sourcing from the official Mocha Pro product page. Note for transparency: I could not find sourced community reaction, so there is no Consumer response section. Tag retained.
Post-edit parses pass on all five: references render, zero redlinks, no CS1 error or maint categories. WTFelvemage (talk) 2026-10-27
- Removed tags for all except for the Boris FX article, which had been missing a section for consumer response. I haven't had any luck finding news about that incident that aren't either unrelated results or Boris FX's own web pages though. If you aren't able to find any either, feel free to remove the section and I can de-stub the page. — Sojourna (talk) 01:00, 29 October 2026 (UTC)
Incomplete tag removal requests (2026-10-28)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting {{Incomplete}} removal on each:
- T-Mobile AppSelector automatic app installations (rev 70991) — the empty Cargo fields are filled (StartDate set to 2023-11-06, the date of the earliest cited report of automatic installs; Status=Active; Type=Unwanted software, Privacy; Description added); archive links added to the three previously live-only citations; incident categories added.
- EA requires Battlefield 6 players to change motherboard settings (rev 70996) — restructured to the incident skeleton: EA's response section now sourced to EA's official Secure Boot Information page and EA Help (the article previously stated EA had not responded); updated for the October 10, 2025 launch; consumer response sourced to PC Gamer; a stray
<references />tag after {{Reflist}} removed. Two removals to flag for mod review: the {{Clarify}}-flagged Godot sentence (the cited source is about the game's map editor, not anti-cheat criticism) and the "requirements can still change since this is a beta" claim (superseded by the launch). - Airthings ASA app release (rev 70997) — all four {{Citation needed}} markers resolved with Airthings' own help center (app layout article, retirement FAQ) and attributed community reports; Cargo StartDate corrected from an unverifiable 2024-05-21 e-mail date to the documented October 1, 2025 retirement; Status=Resolved and Description added. The unsourced "measurements are automatically sent to their servers without warning" claim was replaced with what the sources support (the new app requires an account and login; users reported losing offline access).
- Sassy Saints review copyright claim (rev 70998) — the strike, the company's e-mail and the counter notification are now sourced verbatim from the creator's own Reddit thread; the strike date corrected from February 6, 2025 (which the thread shows was the removal deadline) to late January 2025; Cargo Status/ArticleType/Description filled. Two removals to flag for mod review: the paragraph about a follow-up apology e-mail from Sassy Saints (could not be verified against any source; happy to restore if anyone has one) and the old February 6 strike date.
- Google Nest Protect forced to use Google app (rev 70999) — the "contains only one source" issue is resolved: The Verge and 9to5Google coverage plus Google's support documentation added; the Google blog post now carries a Wayback archive in place of the megalodon link; Cargo Product corrected from "all generations" to the Nest Protect (2nd gen) per Google's support page; the unsourced "Affected users may wish to" advice lists replaced with sourced consumer response. One title flag for mod review: with the Nest app still functional for Protect (initial setup still requires it), "forced to use Google app" reads as an accusation, so a move to "Google Nest Protect transition to the Google Home app" is suggested.
Post-edit parses pass on all five: references render, zero redlinks, no CS1 error or maint categories, no Cargo missing-field categories. Wayback's availability API was 429ing IP-wide again tonight, so existing snapshots were located via the CDX index and two pages (the Windows Central how-to and Google's support page) were archived through the save endpoint; the Reddit threads are cited live with access dates. — WTFelvemage (talk) 28 October 2026 (UTC)
Done. — Sojourna (talk) 05:38, 29 October 2026 (UTC)
Follow-up: Boris FX consumer response section removed (2026-10-27 batch)
[edit source]Following up on the verdict in the 2026-10-27 batch thread: I searched again for any documented community reaction to the FlexLM license deactivation (general and trade press, the Creative COW Boris FX forum, Reddit, review sites) and, like Sojourna, found nothing beyond Boris FX's own pages and a reseller notice — no forum threads, reviews or coverage documenting how customers reacted. Per the offer in that verdict, I have removed the empty Consumer response placeholder section (Boris FX deactivates "legacy" Mocha Pro licenses, rev 71078) and would ask for the page to be de-stubbed. For transparency: the FlexLM citation's megalodon capture was left in place because archive.org was returning 429s all night; I verified the notice's text through Zendesk's article API instead. — WTFelvemage (talk) 29 October 2026 (UTC)
Done. — Sojourna (talk) 20:52, 29 October 2026 (UTC)
Incomplete and SloppyAI tag removal requests (2026-10-29)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting tag removal on each:
- Tim Hortons app collects user data without consent (rev 71073) — restructured to the incident skeleton with an intro and proper headings; the joint investigation findings are fully sourced to the commissioners' report and news release; the class action section documents the national settlement approved on 2022-09-22 (a credit for a hot beverage up to $6.19 CAD and a baked good up to $2.39 CAD, and deletion of the remaining geolocation data within 90 days, including from Radar Labs) and the Financial Post investigation that led to the case; the empty Cargo Description was filled, Company was corrected to the existing Tim Hortons page (Radar has no page) and Product blanked; Category:Data collection added. The raw external URLs in See also were replaced with the Tim Hortons wikilink (the OPC news release became a citation; a University of Waterloo news link was dropped as redundant).
- Veo paywalls camera features (rev 71074) — the update date is pinned to the official changelog (2025-02-26, version 3.3.0.3): the Cargo StartDate previously said 2025-03-13, which was the date the community confirmed the workaround was gone, not the patch date; the editorial Consumer trust subsection was restructured into a sourced Consumer response section; the Cargo Product and ProductLine links to pages that do not exist were blanked per the template rules; Category:Veo and Category:Digital rights management added (the page previously carried no categories at all).
- Age of Empires III delisting and shutdown (rev 71075) — the delisting timeline was corrected: the Steam notice says the game would "no longer be available for purchase" from the October 8 announcement, while the article previously said it would be delisted on October 30, which is the multiplayer shutdown date; two bare-URL citations were converted to {{Cite web}} with their existing archive links; Cargo ArticleType and Description filled, StartDate corrected to 2024-10-08, Status set to Resolved (the shutdown completed as announced) and Product blanked (no page exists); Category:Discontinued products and Category:Planned obsolescence added. Removals to flag for mod review: the "in an attempt to force players to instead purchase the newer Definitive Edition" claim (the intent is not established by any source; replaced with the sourced statement that the announcement directed players to the Definitive Edition), the "temporary discount, which was soon after deleted" claim (its citation is a bundle page archived before the incident and cannot support it), the unsourced "first foray into 3D graphics" line, and the unsourced GameRanger-staleness and weak-hardware implications. Also flagging the title: the game is officially styled "Age of Empires III" and "shut down" reads oddly as a noun, so a move to "Delisting and multiplayer shutdown of Age of Empires III" is suggested.
- HNGRYnsite Camera: From smart kitchen aid to e-waste (rev 71076) — turned into a proper incident article as the hidden comment on the page requested: intro, Background (late 2023 launch, €149.90, any-brand mounting), App shutdown, Liebherr's response (automatic refunds only for webshop buyers, third-party buyers directed to their retailers, pro-rated subscription refunds, personal data deleted by 2025-04-30) and a sourced Consumer response (no shutdown notice in the app store listings, cameras still sold at around €150 without any warning, WEEE disposal instructions including battery removal); all seven empty Cargo fields were filled (StartDate and EndDate 2025-03-31, Status Resolved, ArticleType Product, Company set to Liebherr-Hausgeräte GmbH). The iamhngry.com FAQ citation is now flagged url-status=dead (the domain redirects to Liebherr) with its existing Wayback snapshot kept, and a trans-title was added for the German Golem source. The stale hidden comment about the restructure was removed now that it is done. Also flagging the title for a move — the current one reads like an essay subtitle; "HNGRY app shutdown renders HNGRYnsite cameras inoperable" is suggested. {{SloppyAI}} retained and its removal requested alongside.
- Cerberus (rev 71077) — restructured to the Consumer-impact summary and Incidents skeleton; the "(201x)" and "(202x)" heading dates are pinned to the coverage (free license revocation 2015, paid license expirations December 2019, ad-blocker login wall June 2025, the latter dated via the uBlock Origin tracker issue); the email-history narrative was rewritten to what Android Police documents — the 2015 "never make any retroactive changes to paid licenses" promise and the Persona-era reassurance from 2017 — because the specific "20 February 2018" and "5 February 2019" email dates could not be verified against any source and were removed; two stray "currently blocked from adding supporting image" notes and the unsourced "no major news sources covered the backlash" line were also removed; the ad-removal price was dropped pending verification, since this page said about $120 USD while the {{Main}} incident page says $100 USD — the incident page may want the same treatment.
Post-edit parses pass on all five: references render, zero redlinks, no CS1 error or Cargo missing-field categories. Archive.org was hard-429ing tonight (save, availability and CDX alike), so the five genuinely new sources (the Financial Post investigation, the OPC news release, the LPC Avocats settlement page, the Liebherr press release and the GitHub issue) are cited live with access-dates; every citation that already had a snapshot keeps its archive. Thanks Template:Noping for the quick verdicts on both 2026-10-27 threads and on yesterday's batch. — WTFelvemage (talk) 29 October 2026 (UTC)
Done. — Sojourna (talk) 04:20, 30 October 2026 (UTC)
Stub and incomplete tag removal requests (2026-10-30)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting tag removal on each:
- Good2Go Mobile (Canada) phases out 3G network and merges with Lucky Mobile (rev 71126) — the 3G timeline now matches the reporting: Rogers retired its 3G network on 31 July 2025 while Good2Go set its own switch deadline at 31 August 2025 (the previous text implied a single national shutdown on 31 August); the Ztar v Rogers CRTC dispute is documented with its own citation, including Rogers' $3 legacy-network fee and $75 administrative charge; the migration terms (number portability, forfeited balances, $19 Lucky Mobile plans, 48-hour switches) are sourced; Category:Good2Go Mobile added. Title flag: "phases out 3G network" misattributes the network shutdown to Good2Go and "LuckyMobile" is missing a space; a move to "Good2Go Mobile winds down service ahead of Canada's 3G shutdown" is suggested.
- Polestar 2 (rev 71129) — restructured to the product skeleton with a Consumer-impact summary; the paid performance update section is sourced to Polestar's official specifications (310 kW/421 hp to 335 kW/455 hp, $1,195, included in the Performance pack from model year 2023) and The Verge's coverage (408 hp to 476 hp on the model sold at the update's introduction, and the one-time-fee positioning); the empty Cargo Category field was filled. Note for the linked incident page: it says the update adds 34 horsepower and lists the torque as 546 Nm, but per Polestar's official page 546 is the torque in lb-ft (about 740 Nm), and the 34 hp delta applies to current models — the 2021-era upgrade was +68 hp.
- Dead star server shutdown (rev 71130) — the shutdown-cost statement now cites Eurogamer, which carries the Jack Mathews quote directly; the final-days boosted Fame detail was added; the Cargo ProductLine and Product links were blanked per the template rules (no Dead Star pages exist); the Stop Killing Games mention is wikilinked. Title flag: the game is stylized "Dead Star", so a move to "Dead Star server shutdown" is suggested.
- Anthem (rev 71127) — the unsourced consumer-impact editorializing ("many consumers feel disdain towards the brand, their current and future offerings or the industry as a whole") was replaced with sourced statements: no offline mode was provided and physical-copy owners were equally affected, premium currency was taken off sale on announcement day, and the EA User Agreement permits terminating online services at any time with at least 30 days' notice while the shutdown was announced more than six months in advance (the previous "legal and permissible so long as 30 days notice" framing was an unsourced interpretation and now follows the agreement's wording); consumer reaction is sourced to Kotaku's shutdown coverage (final-hours sessions, trophy and screenshot gathering, subreddit memorials) and the 2022 GameStop one-cent used copies; the date formats and the "servers were shutdown" typo were fixed and the heading's "2026.01.12" normalized to 2026.
- Zyxel (rev 71128) — restructured to the company skeleton with a Consumer-impact summary; the incident is documented per Zyxel's advisory and TechCrunch (CVE-2024-40890 and CVE-2024-40891 command injection plus CVE-2025-0890 insecure default credentials on the same end-of-life DSL models; VulnCheck's July 2024 discovery and August 2024 report; GreyNoise's late-January 2025 active-exploitation report and its Mirai observation; the devices absent from Zyxel's end-of-life page and still sold on Amazon; about 1,500 exposed devices per Censys; Zyxel's 29 January awareness claim and its non-response to press). Two removals to flag: the "founded in 1989 in Taiwan" and "subsidiary of Zyxel Group Corporation" prose claims (both kept in the Cargo block but dropped from prose pending a proper source) and the Mastodon citation (a journalist's social post; TechCrunch covers the same material).
Also noted the Veo verdict from yesterday's batch — the re-tagging and the Talk page rationale make sense, and the page has been left as re-tagged. Post-edit parses pass on all five: references render, zero redlinks, no CS1 error or Cargo missing-field categories. Archive.org's save endpoint was 429ing IP-wide again tonight, but all four newly added citations (The Verge, the Kotaku GameStop piece and the two iPhone in Canada pieces) already had existing snapshots, located via the availability API and verified to render the cited content, so no live-only citations were added. Thanks Template:Noping for the quick verdicts on yesterday's batch, the Boris FX de-stub, and for executing both suggested title moves. — WTFelvemage (talk) 12:15, 30 October 2026 (UTC)
Done. — Sojourna (talk) 04:27, 31 October 2026 (UTC)
Stub and incomplete tag removal requests (2026-10-31)
[edit source]Five articles from Category:Articles in need of additional work completed, requesting tag removal on each:
- JetBrains retires CodeCanvas (rev 71260) — the incident cargo block was added (StartDate 2025-10-16, the announcement date; EndDate 2026-03-31; Status Resolved, since the shutdown completed on the announced schedule); a Consumer response section was added from Neowin's coverage of the announcement; Category:Discontinued products added; the duplicated full citations were converted to named references. Requesting {{StubNotice}} removal.
- Home Bargains (rev 71261) — the Consumer-impact summary is now sourced to the BBC reporting on the chain's use of Facewatch facial recognition (watchlist images circulated between stores, more than 35 wrongly flagged people reported to Big Brother Watch, the chain declining to comment on the 2025 case); a second incident subsection was added for the February 2026 Chester misidentification case with Facewatch's response. The unsourced one-line privacy claim was replaced by the sourced summary, and the redundant hardcoded Category:Articles in need of additional work link at the bottom was removed (the {{Incomplete}} tag still feeds the category, so the page remains listed until the tag comes off). Requesting tag removal.
- HP Reverb G2 (rev 71262) — the tag's stated issue (nothing about HP itself) is addressed: UploadVR's October 2022 reporting on the end-of-production rumors is documented, including HP's non-committal response, the $600-to-$350 flash sale and the departure of HP's Global Head of Virtual Reality; the platform side now states that Microsoft confirmed the 24H2 removal was intentional and that headsets keep working on version 23H2 with Steam only through November 2026; the Oasis driver section is sourced to Windows Central (a Microsoft principal firmware engineering manager who previously worked on the Windows Mixed Reality and HoloLens teams; free on Steam, not open-sourced). Corrections per the sources: the "inadvertently ended" claim (the removal was confirmed intentional) and the "former Windows Mixed Reality employee" attribution (he is a current Microsoft employee who previously worked on the WMR team). Requesting tag removal.
- Cryptic Studios (rev 71263) — restructured to the company skeleton; the intro, Consumer-impact summary and Incidents are sourced to Eurogamer, GamesIndustry.biz, PC Gamer, Massively Overpowered and MMORPG.GG: the October 2023 and October 2024 layoff waves under Embracer's restructuring, the "operate under DECA Games going forward" change, the November 2025 divestment to Project Golden Arc for about $30 million, and Jack Emmert's January 2026 return as CEO with Cryptic saying it had "reassumed responsibility" for its titles. Removals to flag for mod review: the "$250 anniversary bundles" and "$120 starter packages" prices (not verifiable against any source; replaced with Massively Overpowered's documented lockbox-key criticism of Star Trek Online), the "all Cryptic Studios developers to be laid off" claim (the sources report unspecified personnel changes and a downsizing to a minimal staff), and the stale "now owned by Embracer Group" framing (corrected to the divestment). The page carried no stub or incomplete tag — it was listed via five placeholder boxes, which are now filled and deleted, so it has left the work-needed category without mod action; noting that here for transparency.
- Gigantti pressured additional subscriptions (rev 71264) — the incident is now dated and sourced: the Consumer Ombudsman's October 2023 finding (misleading seller-liability information contrary to the Consumer Protection Act, customers unlawfully directed to manufacturers and importers, hard-to-reach customer service, liability denied on warranty-expiry grounds, gift cards offered instead of cash refunds, with Gigantti's commitments to correct all of it), and Iltalehti's reader reports (the €315 modem plus an undisclosed €356.40 care-service bill, the "same price" broadband renewal that was not, and the commission model pushing add-ons customers did not expect), with trans-titles for the Finnish sources; the two bare-URL citations were converted to {{Cite web}} and four more sources were added. Cargo StartDate pinned to 2023-10-06, the date the Ombudsman's finding was reported. Removals to flag: the unsourced "systematic anti-customer practices" and "designed to prey on the elderly" characterizations, replaced with what the sources document (named cases and attributed reporting), and the "in recent years" vagueness, now pinned to 2023; the redlinked Finland was changed to a Wikipedia link. Requesting removal of {{Incomplete}} AND of the {{Placeholder box}} glued to it on the first line — AbuseFilter 4 blocks any change to that glued line for non-mods, so I left it byte-identical and am asking for both to come off together.
All citations newly added today already had Wayback snapshots, so nothing was cited live-only. Post-edit parses pass on all five: references render, zero content redlinks, and no CS1 error or Cargo missing-field categories; the Gigantti page additionally picks up the site's Finnish-language sources category from its |lang=fi fields, which I read as intentional rather than an error. Thanks Template:Noping for the quick verdicts on the 2026-10-30 batch, the Good2Go tag removal and title fix, and the Dead Star move. — WTFelvemage (talk) 31 October 2026 (UTC)
Done. — Sojourna (talk) 03:09, 1 November 2026 (UTC)
Stub and incomplete tag removal requests (2026-11-01)
[edit source]Five articles from Category:Articles in need of additional work completed. Four leave the category by having their remaining placeholder sections filled and the boxes deleted; one tag removal is requested below.
- Johnson Controls GLAS Thermostat (rev 71336) — the Consumer impact summary is now sourced: the GLAS support site's statement that the thermostat "will not be impacted by the discontinuation of app support, and will continue to function as it does today", the 2018 product announcement, and the open-glas project documenting efforts to restore local control, including its finding that the residential firmware exposes no known LAN control service. All three previously unarchived citations now carry Wayback snapshots; the two glas.johnsoncontrols.com citations are url-status=dead with archives, as that site is now offline. The Incidents section documents the official end-of-support listing: the March 2026 cloud termination alongside the original October 2020 product discontinuation and the August 2019 Cortana feature removal. The Johnson Controls and Home Assistant redlinks became Wikipedia links. Removal to flag: the unsourced speculative paragraph about what restoration of local control "could allow" was replaced with what the open-glas project actually documents. Requesting {{Incomplete}} removal — the tag was added this morning and the placeholder section it flagged is now filled and sourced.
- Tesla locks heated rear seats behind paywall (rev 71332) — the empty Tesla's response section was filled and sourced: the paid unlock's origin in an owner's public request to Elon Musk (Teslarati), the December 2021 price cut from $300 to $200 alongside the Cold Weather bundle (Drive Tesla), rear heated seats becoming standard equipment on the Model 3 Rear-Wheel Drive from the 2022 model year (InsideEVs), and Tesla's own support page documenting the upgrade's eligibility window (delivered before November 1, 2021). Two typos in Background were fixed. The page's only category feed was the response-section placeholder box, now deleted with the section filled.
- The Machinery termination (rev 71333) — the Consumer response section is now sourced to PC Gamer and the Hacker News discussion (the rug-pull criticism of the deletion demand, the contrast with open-source licensing, and Our Machinery's earlier statements that it would like to open-source the engine). The raw-URL EULA comparison reference became two proper citations to the May and August 2022 Wayback snapshots of the EULA; archive links were added to the gamefromscratch and Hacker News references. The missing Cargo Status field was filled (Resolved), the intro Our Machinery redlink was unlinked (no page exists), and the orphaned {{Ph-I-C}} categories placeholder was replaced with Category:Our Machinery — that placeholder was the page's only category feed. The new category page is a redlink, as expected for a fresh category.
- Amazon sued for enrolling and charging customers into Audible without consent (rev 71335) — the empty Consumer response section was filled from the Heck complaint (charges discovered on statements, no acknowledgment carrying Audible's terms, cancellation policy or cancellation instructions) and the Sherk complaint's allegations (numerous complaints on public forums and consumer watchdog sites, enrollees who never used the service, retained fees). The Corporate response section now documents the outcome: summary judgment for Amazon and Audible on July 9, 2026, dismissed with prejudice (no capacity to redeem Audible titles via No-Rush rewards; no evidence Heck used the No-Rush option or the "Try for $0.00" button; Automatic Renewal Law-compliant disclosures), and the pending status of Sherk v. Audible, whose motion to dismiss was renoted for January 2, 2026. Corrections per the sources: the second suit's "January 10, 2025" filing date was wrong (that is the Vital Law article's date; Sherk was filed in March 2025), and Cargo StartDate moved from 2024 to 2022-05-13, the Heck complaint's date, flipping the year category to 2022 incidents. A leftover HTML comment pointing at the CourtListener complaint was removed after its content was integrated into the section.
- Anthropic Claude Code HERMES.md billing flaw (rev 71334) — the empty Consumer response section was filled from the already-cited sources: the GitHub issue thread's criticism of the refund refusal, including the remark that refunding would have been "the easiest PR win in the world", the affected user renewing the refund request after the fix, and the r/ClaudeAI PSA. Anthropic's response now documents Boris Cherny's April 25, 2026 statement that this was an "overactive anti-abuse system" and had been fixed, which replaces the article's speculation about a billing classifier. The empty Cargo ArticleType and Type fields were filled (Service; Billing, Subscription). No new sources were needed — every citation was already in the article with an archive.
Citation note: the Johnson Controls end-of-support page, the Heck complaint PDF and the Sherk order were saved to the Wayback Machine today; every other newly added citation already had a snapshot, so nothing is cited live-only. Post-edit parses pass on all five: references render (9, 11, 14, 17, 9), zero content redlinks, and no CS1 error or Cargo missing-field categories; the four placeholder-fed pages have left both the work-needed and verification-concerns categories, and the GLAS page keeps both through its Incomplete tag pending this request. Thanks again Template:Noping for clearing the 2026-10-31 batch overnight — all five tag removals and the ref clean-ups verified via the recent-changes log. — WTFelvemage (talk) 13:25, 1 November 2026 (UTC)
Done. — Sojourna (talk) 00:39, 2 November 2026 (UTC)
Tag removal requests and disclosures, 2026-11-02 batch (5 articles)
[edit source]Batch of five placeholder fills from Category:Articles in need of additional work. All sections that were preload placeholders have been filled with sourced content; tag-removal requests and disclosures below. Happy to restore or adjust anything on request.
- Linktree changes Terms of Service to allow collection of user content to train AI (rev 71399) — filled Linktree's response and Consumer response, corrected the announcement date to the March 24, 2026 blog post, and replaced an unsourced "May 31 email" sentence with the ToS one-month-notice clause. Requesting {{Stub}} removal. Disclosure: some new citations are live-only (archive.org snapshot checks were rate-limited tonight); the Asha Nyr Instagram post is cited as consumer sentiment only.
- Start Romagna increasing prices and voiding old tickets (rev 71400) — filled both response sections, added verified prices and fine amounts from the official tariff guide, and corrected the conversion window (old tickets usable until 31 July 2026, replaceable until 31 May 2027, not two years). Requesting {{Stub}} removal.
- Brave puts affiliated links in the address bar (rev 71401) — filled Consumer response with press and community coverage, all with archive links. Requesting {{Incomplete}} removal.
- Ola Electric disables vehicle riding modes without MoveOS+ subscription (rev 71402) — filled Consumer response and the empty Cargo fields (StartDate 2025-07-21, Status Active, ArticleType Product, Description). Requesting {{Stub}} removal.
- GoPro Karma (rev 71403) — filled the intro and GoPro's response, sourced the November 2016 recall with GoPro's own press release (removing a {{Citation needed}}), and added the January 8, 2018 discontinuation. Disclosure: I removed the "around 2,500 drones bricked" figure and its flyingglass.com.au citation from the February 2021 sentence — the 2,500 figure is only documented for the 2016 recall, and that source does not cover the 2021 update; the sentence now attributes the controller pairing failures to the end-of-life notice and community repair guides. Will restore the figure if anyone has a source for it. Requesting {{Incomplete}} and {{Cleanup}} review.
WTFelvemage (talk) 06:25, 2 November 2026 (UTC)
Done. — Sojourna (talk) 03:00, 3 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (3 November 2026)
[edit source]Five articles expanded and sourced per the usual workflow; requests and disclosures below.
- PlayStation 3 removal of OtherOS with system update 3.21 (rev 71494): expanded the lawsuit section with the verified settlement history (the October 2016 two-tier deal of $55/$9, rejected February 2, 2017 by Judge Yvonne Gonzalez Rogers; the revised up-to-$65 single-class settlement approved December 2017 with an April 15, 2018 claims deadline; checks of about $10 mailed November 2018), replacing the unsourced "up to $10" figure. Added Sony's response and a consumer response section, and removed the Ph-I-ComR placeholder. Also fixed the redlink PlayStation Blog (no local page; now plain text) and linked Sony and PlayStation 3. Requesting StubNotice removal.
- IFTTT credits system controversy (rev 71495): filled the empty Cargo Description and Type fields, wrote the Background, Incident, and IFTTT's response sections (removing the Ph-C-Inc and Ph-I-ComR placeholders), and verified the credit allotments (Free 1,000 / Starter 5,000 / Pro 20,000 / Pro+ 100,000 credits per month) against the official plans page and help center; the roughly 50-credits-per-simple-Applet figure is attributed to community reports, as the sources do not publish an official rate card. Requesting StubNotice removal.
- Microsoft ends use of bypassnro.cmd for Windows 11 (rev 71496): conformed the page to the IncidentPreload skeleton, which resolves the Cleanup issue; fixed the single-equals "=References=" heading; set the Cargo StartDate to ISO form (2025-03-28, same date) and filled the blank Status as Active; and documented the October 2025 escalation (registry re-enable and ms-cxh:localonly workarounds removed) along with the stable-release status as of October 2025. Requesting Stub and Cleanup removal.
- Elgato forces Stream Deck users to sign up (rev 71497): filled the Cargo Status, ArticleType, and Description fields; corrected the Cargo StartDate from 2023-10-24 to 2023-10-12, the 6.4 rollout and Marketplace launch date per Elgato's release notes and press coverage (the October 24 announcement stays in the prose); filled the Background, Incident, Elgato's response, and Consumer response sections, removing three placeholder boxes; fixed the "[Incident]" heading; and removed the empty Lawsuit placeholder section, as no litigation is documented. Happy to restore that section if anyone has sourcing. Requesting StubNotice removal.
- Pocket Casts (rev 71498): filled the consumer-impact summary, removing the Ph-C-CIS placeholder; documented the October 2, 2025 reversal (banner ads removed for one-time app purchasers) with The Verge's coverage; and replaced an unclosed, unarchived forum citation with The Verge's article carrying the same commitment quote. Requesting Incomplete removal.
All newly added citations carry archive links where snapshots existed; no new Wayback saves were needed this batch. Thanks as always. — WTFelvemage (talk) 20:47, 3 November 2026 (UTC)
Done. — Sojourna (talk) 05:37, 4 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (9 November 2026)
[edit source]Five articles expanded and sourced per the usual workflow; requests and disclosures below.
- AWS Lightsail won't cancel (rev 71812): restructured the page to the incident skeleton and filled all Cargo fields (the blank StartDate/Status/ArticleType/Type/Description were feeding deficiency categories). I also reframed the core claim per AWS's own documentation: deleting an instance stops that instance's charge, but attached resources (snapshots, static IPs, block storage) and stopped-but-not-deleted instances keep billing, which matches every complaint thread cited; the article previously said deleted servers keep billing. Set StartDate to 2021-04-04, the date of the earliest sourced complaint (a Reddit thread), so the field would not be left blank; happy to change if you prefer another convention. Also fixed the "screenshots" typo (snapshots) and normalized the references heading. The re:Post thread the article already cited is real (verified live and via its existing snapshot). Requesting Stub removal.
- VOIPO overbills customers and denies refunds (rev 71813): filled the Cargo Description, set Status to Pending Resolution (was "Unresolved") and EndDate to 2025-08-06 per the company's shutdown announcement. Fixed the heading capitalization to sentence case. Removed the unverified "$185 every 2 years" figure (the archived site showed a $149 two-year promo; complaint threads do not state a price). Documented the official apology reply in the Reddit thread and the August 6, 2025 cessation of operations (archived voipo.com announcement, which cites "a key vendor disrupting our ability to process credit cards or issue refunds"). Also removed the hardcoded link from the article body — that category should be fed by the maintenance tag, not self-declared in the text; the StubNotice still feeds it until you rule. One Trustpilot quote (a February 2026 review) is cited live because Wayback refuses to save Trustpilot (two 520s); the October 2025 snapshot covers the earlier quotes. Requesting StubNotice removal.
- Liberty Safe (rev 71814): fixed the Cargo Description, which was a copy-paste error describing a games distributor, and added the missing Company field. Renamed the incident heading to sentence case and "master code" per the sources. Sourced the incident with Fox Business, The New York Times, Newsweek, RECOIL, and the Missouri Attorney General's release, and documented the September 6, 2023 policy change (subpoena requirement, code-expungement form) plus the standing "Facts" page. Converted the bare-URL founding citation to Cite web and removed the "source found via Wikipedia references" note — the archived Liberty Safe history PDF is cited directly as the primary source. Dropped two older refs (an scnr.com piece and one company privacy-page ref) whose content is now covered by the stronger sources; happy to restore either if you prefer. Requesting Stub removal.
- Nissan shuts 2G car service in UK (rev 71815): filled the Cargo fields (StartDate/EndDate 2024-04-01 per Nissan's statement, Status Resolved, ArticleType Service, Type Cloud, Description) and fixed the intro sentence ("shut down down", previously uncited, now dated April 1 and cited). Added the Ofcom policy page for the 2G sunset dates, TechRadar for the owner workarounds, and a Later developments section covering the separate March 2026 shutdown of the same app for newer cars (The Guardian, newly archived today). No 4G retrofit, replacement remote service, or compensation was documented in any coverage I found, so the article makes no claim about them. Requesting StubNotice removal.
- PlayStation restricts how developers can give upgrades to "PS5" editions (rev 71816): corrected the Cargo StartDate from 2021-03-28 (the publication date of a cited IGN announcement article) to 2025-06-18, when Double Eleven's "Update for players on PlayStation" confirmed the delay; set EndDate 2025-06-26 and Status Resolved (upgrades went live at full release; was "Ongoing"), and blanked the Product field since the PlayStation 4/5 pages do not exist yet. Rewrote the intro so the platform limitation is attributed to the developer's "platform-specific limitations" statement rather than asserted in wiki voice, with background from Push Square (no Smart Delivery equivalent) and Eurogamer (the September 2021 $10-upgrade policy). Verified the 500 Rust Coins compensation and the apology from the developer's archived update page. Replaced the YouTube-trailer-comments citation with a Reddit thread. If you are open to a title move, the current one asserts a restriction as fact — something like "PlayStation platform limitations delay Rust Console PS5 upgrades" would match the sourcing; your call. Requesting StubNotice removal.
New Wayback snapshots created this batch: two AWS re:Post threads (2026-11-09) and The Guardian article (2026-11-09). Trustpilot refused archiving (520 on two attempts), hence the one live citation noted above. Thanks as always. — WTFelvemage (talk) 03:53, 9 November 2026 (UTC)
Done. For the VOIPO article I changed the Trustpilot ref URLs to link directly to the review posts in question and was able to successfully archive them using Megalodon.jp (Japanese archival website). I also moved the PlayStation incident article to what you suggested. — Sojourna (talk) 05:14, 10 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (9 November 2026, second batch)
[edit source]Five more articles expanded and sourced; requests and disclosures below.
- Asustor Drivestor NAS (rev 71820): filled both placeholder boxes (the intro and consumer-impact summary placeholders), which per house rules de-categorizes the page; the Stub stays for your call. Corrected the Cargo ReleaseYear from 2025 to 2021 (PCMag's October 2021 and StorageReview's December 2021 reviews; 2025 is when ADM 5.0 removed the features, not when the line launched). Reworded the incident prose around Asustor's official Feature Support Notice and kept all existing references, adding PCMag, TechRadar, and Asustor's Plex guidance. The one community thread documenting reaction (r/HomeNAS) could not be archived or fetched — Reddit's save endpoint returned a JavaScript-challenge shell — so the consumer-impact framing uses launch coverage documenting the removed transcoding as a headline selling point. Requesting Stub removal.
- Jeep (rev 71821): filled the empty Cargo Description, converted the three bare-URL citations to Cite web (the old The Drive citation's archive link pointed at the homepage rather than the article — now fixed to the article's own snapshot), and restructured Company Response as a sentence-case subsection under the ads incident. I softened "they cannot be disabled" to match the sources: one owner reported OK did not dismiss the popup, and Stellantis called it a temporary glitch with instant opt-out as the standard. Added the July 2015 Uconnect remote hack and the resulting 1.4 million vehicle recall as a second incident — no Uconnect page exists yet, so it is covered inline with Wired's original reporting. Requesting StubNotice removal.
- NZXT (rev 71822): restructured the Controversies section into an Incidents section per the company skeleton, and split out the Flex content under its own heading with
- Main article: NZXT Flex, now properly summarized: the November 30, 2024 Gamers Nexus investigation, the December 4 CEO response video, and the December 6 follow-up, plus ExtremeTech and The Verge coverage. Added the February 2021 CPSC H1 fire-hazard recall as a second incident with the commission's verbatim hazard description, and a consumer-impact summary. Kept the existing Kraken warranty content and its references; fixed the PC Gamer forum citation's empty archive-url parameter by citing it live. One citation needed the {{!}} escape because the video title itself contains a pipe character — caught by preview parse. Requesting StubNotice removal.
- Vulcan Strength (rev 71823): corrected the case name — the lawsuit was filed by Advanced Fitness Concepts, Inc., which does business as Vulcan Strength Training Systems, and the prior text read as though "Vulcan Strength" itself were the plaintiff entity; also corrected the founding year from 2008 to 2009 per the company's own about page, and added the parent entity to the Cargo. Documented the docket from the court records: the December 29, 2025 motion to dismiss for lack of personal jurisdiction (the jurisdiction hook is the affiliate program's forum clause, which the reviewer had accepted), the July 1, 2026 denial, the July 2026 answers, and the October 8, 2026 protective order — the dismissal order is archived from CourtListener today. Removed the External Links section, which duplicated the two cited videos as bare URLs; happy to restore if you prefer. Requesting Stub removal.
- Bumble (rev 71824): sourced and corrected the intro — the old text said the company was "founded in 2014 as MagicLab by Whitney Wolfe Herd", which overstates her role; the corrected version, per TechCrunch, is that she co-founded the Bumble app in 2014 within MagicLab, owned by Badoo founder Andrey Andreev, whose majority stake Blackstone bought in 2019 in a deal valuing the business at $3 billion, with Wolfe Herd becoming chief executive of the whole company (her return to the role was announced in January 2025). Changed "the lifetime option was offered beginning sometime in 2023" to "by October 2023", matching the cited snapshot's own date. Added three sourced incidents — the $22.5 million auto-renewal settlement (2020), the anti-celibacy billboard backlash (May 2024), and the data-breach class action (February 2026) — and reordered the incidents chronologically. A potential incident I had briefed to research (a "ceasefire" push notification) could not be documented in any outlet, so it was not added. Requesting Stub removal.
The previous batch's verdicts (revs 71812–71816) still stand as filed whenever you get to them. New snapshots this batch: the Vulcan court order (CourtListener PDF). Thanks as always. — WTFelvemage (talk) 06:00, 9 November 2026 (UTC)
Done. — Sojourna (talk) 04:55, 11 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (9 November 2026, third batch)
[edit source]Five more articles; requests and disclosures below. (Earlier batches from today, revs 71812–71816 and 71820–71824, still stand as filed.)
- Tim Hortons (rev 71837): filled the consumer-impact summary and Products sections, removing both placeholder boxes per house rules. Corrected the intro's figures — the old text read "over 5,500 and contains a net income of $938 million as of 2023"; per RBI's Form 10-K, the chain operated 5,833 restaurants as of December 31, 2023, and Tim Hortons segment income was $958 million for fiscal 2023 (the $938 million matched no figure in the filing). Rewrote the incident summary: the old text called the privacy commissioners' findings "a lawsuit" — the June 1, 2022 joint investigation findings and the separately litigated class-action settlement (approved September 22, 2022; free hot beverage up to $6.19 and baked good up to $2.39, plus deletion of the collected geolocation data) are now correctly separated, with the Financial Post investigation, the commissioners' quotes, and the settlement criticism sourced. Fixed three See-also redlinks (Starbucks, Dutch Bros, Bewley's now Wikipedia links; also the "Dutch Bro's" typo). Requesting Stub removal.
- GameStop (rev 71838): sourced the intro; dropped the uncited founding-history sentence (1984, Babbage's, McCurry and Kusin) — I could not verify it against a citable source this session and will happily restore it with one if anyone has it. Fixed the self-link (the page linked Wikipedia's GameStop article from the GameStop page) and the Non-fungible tokens redlink (now NFT). Converted the two bare-URL citations to Cite web keeping their existing archives. Added the crypto-wallet shutdown incident (announced August 2, 2023; removed from app stores November 1, 2023; Secret Passphrase deadline October 1) and a consumer-impact summary covering the store closures; merged sourced detail into the existing NFT marketplace section rather than replacing it. Removed a leftover HTML comment from a previous editor asking for expansion — done. Kept the {{Citation needed}} marker on the hold-times sentence exactly as it was. Requesting incomplete removal.
- IFTTT (rev 71839): the first line has StubNotice glued to the CompanyCargo block; I kept that line byte-identical and filled the fields below it, so the tag needs your removal from the glued line. Filled the empty Cargo Description and sourced the intro — dropped the uncited 2012 Wemo sentence and the "Jesse Tane and Alexander Tibbets" co-founder list, since the launch-era press I could verify names only Linden Tibbets. Corrected the Legacy plan incident's date (the old text said 2023; TechHive documents the pay-what-you-want plans being discontinued in early 2024, breaking the "forever" pricing promise) and fixed broken italic markup around "lifetime". Added the September 2020 free-tier cut to three Applets and the October 2026 credits rebrand with a Main link to the existing credits article. Requesting StubNotice removal.
- Unlocking Technology Act of 2013 (rev 71840): this page correctly covers H.R.1892 (Lofgren/Massie/Eshoo/Polis), which my research initially conflated with the narrower Goodlatte bill; the findings are now sorted. Added the verified background (October 2012 Librarian of Congress decision, unlocking illegal from January 26, 2013, the 114,000+-signature petition and the March 4, 2013 White House response, the FCC chairman's concerns), the bill's operative text from GovInfo, and a Related bills and outcome section: the narrower Unlocking Consumer Choice and Wireless Competition Act became law on August 1, 2014, and the October 2015 rulemaking renewed and expanded the unlocking exemption to tablets — resolving the specific controversy, though the broader Section 1201 reform the bill sought was never adopted. Requesting StubNotice removal.
- Privacy.com (rev 71841): corrected the corporate history — the old intro said Privacy.com "is a subsidiary of Lithic", but the verified chain is the other way around: the issuing platform was spun out of Privacy.com in 2020 and the whole company rebranded to Lithic in 2021, with Privacy.com continuing as its consumer product (TechCrunch and the company's own pages). Also dropped the "co-founded by Jason Kruse" claim — the press names only Bo Jiang as co-founder; Kruse is the CTO. Filled the consumer-impact summary (placeholder box removed) and added a sourced Incidents section: the 2020 card-number enumeration attack (from the company's own engineering blog), the October–November 2025 reports of unauthorized charges on dormant cards, the December 2021 mass card reissue after merchant declines of the prepaid BIN, the 2026 BBB complaints about unexplained account closures and refunds trapped in suspended accounts, and the 3% foreign-transaction fee introduced between mid-2022 and late 2023 (bracketed by archived support articles). The BBB page and the Hacker News thread are cited live because no usable Wayback captures exist; the User privacy subsection's low-quality citation was replaced with PCWorld's review. Requesting Incomplete removal.
Thanks as always. — WTFelvemage (talk) 18:09, 9 November 2026 (UTC)
Done. — Sojourna (talk) 07:16, 11 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (10 November 2026)
[edit source]Five more; requests and disclosures below.
- Guardzilla (rev 71880): filled the empty Cargo Description and Founded fields (St. Louis, 2014, per a contemporaneous PR Newswire release), the consumer-impact summary, and the Products placeholder; removed the empty See-also box (nothing exists to link — happy to restore with content). Expanded the 2018 vulnerability incident with the Rapid7 disclosure it was already citing secondhand (CVE-2018-5560, CVSSv3 10.0: a firmware root password cracked in three hours yielded shared S3 credentials exposing all customers' cloud video) and Bitdefender's parallel disclosure. No post-shutdown data leak was documented anywhere in the coverage I could find, so none was added. Requesting Incomplete removal.
- Cisco Requiring a service contract to download in-support device firmware (rev 71881): corrected the Cargo StartDate from 11-02-2013 to 2011-12-12 — the old value was the cited 2013 forum thread rendered in Cisco's MM-DD-YYYY format (so November 2, 2013, not February 11), and the requirement was already being complained about as a "New download policy" in a December 2011 Cisco Community thread, which is now cited. Also corrected the Cargo Company field to "Cisco Systems, Inc." to match the existing page, and deleted the orphaned categories placeholder sitting after the reflist (the real category was already below it). Restructured to the incident skeleton and added the documented context: the 2011 Server Fault exchange on obtaining security fixes without a contract, Cisco's own download-tier help pages, the second-hand-equipment impact (Cisco's relicensing program and iFixit's 2019 report), and the Reddit-documented complaints from 2014 and 2024. I could not find dedicated press coverage of the download gate itself despite targeted searches — iFixit's piece covers the adjacent Smart Licensing tightening and is cited as exactly that. Requesting Incomplete removal.
- Shake Shack upcharging non-tipping customers (rev 71882): filled the two placeholder boxes; corrected the outlet name ("The Main Wire" → The Maine Wire) and a "Shake Shake" typo; identified the TikTok user as Brian Powell per his Fox News interview, noting the video was a deliberate recreation after his wife noticed the behavior on a first, unrecorded purchase. Added the totals ($18.46 subtotal, $1.50 added), the 4.2 million view reach, Shake Shack's earlier TikTok-comment response, HMSHost's scale as the airport concessionaire, the tipping-fatigue survey the coverage cited, and the August 13 NBC retest where the price change did not occur. No kiosk or point-of-sale vendor was identified in any coverage, which the article now states. Requesting Stub removal.
- EA moves to in-house kernel-level anti-cheat on PC after purchase (rev 71883): filled the empty Cargo Status, ArticleType, and Description fields and the full affected-game list; corrected two migration dates (EA SPORTS WRC was announced May 17, 2024 and went live in June; Battlefield 1 was announced in August 2024 and went live in October). Reworded the refund claim: the old text said flatly "EA has refused to give refunds" — what the sources document is that EA offered no refunds, that Steam's automated refund path declined out-of-window requests, and that Valve granted an off-policy refund in at least one documented case after repeated direct requests. My research also disproved my own recollection that EA removed the anti-cheat from Garden Warfare 2 after backlash: the March 2024 deployment broke the game for Windows users as well, and EA fixed the installation while keeping the driver. Added the April 2025 EA Javelin rebrand and a March 2026 job-listing note on possible future Linux support. Requesting StubNotice removal.
- Google Chromebook (rev 71884): filled the consumer-impact summary and removed the Products and See-also boxes — the Products box contained its own boilerplate example text with no product pages existing to list, and See-also had nothing to link; happy to restore either with content. Added the Auto Update Expiration incident with the documented arc: the original five-year support window extended to 6.5 years by 2018, The Register's 2019 "best-before date" reporting, the 2023 PIRG "Chromebook Churn" findings for schools, Google's September 2023 ten-year update pledge, and OSNews's September 2026 report that a Google support document now caps updates for every Chromebook at mid-2034 — the pledge being walked back. On the existing ScreenAI incident, documented that Google issued no public response and that the community thread on the heat problems predates the viral post by about eight months. Requesting Incomplete removal.
Thanks as always. — WTFelvemage (talk) 05:26, 10 November 2026 (UTC)
Done. — Sojourna (talk) 01:55, 12 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (11 November 2026)
[edit source]Five more; disclosures below. None of the five carried a stub or incomplete tag — each sat in the work-needed category through placeholder templates, which I removed as the sections were filled, so no tag removals are being requested this time.
- Mercedes-Benz EQS rear-wheel steering requires subscription (rev 71954): filled the two empty response sections. Corrected the incident section's "full range is not available as a factory option" bullet: auto motor und sport documents that buyers could order the 10-degree system permanently from the factory, as does J.D. Power for the U.S. market, so the subscription is the post-delivery route only — the old bullet misread the cited sources. Added the U.S.-market scope (the full system is standard on U.S.-spec cars per The Drive and Jalopnik), the parking-package prerequisite, the Mercedes me activation flow, the company's only on-record statements about the system, and the 2024 Ostberg interview. Removed the unsourced closing line "This means customers are paying for a hardware in their car that can never truly be theirs" and the unsourced background bullets; the criticism now lives, sourced, in Consumer response.
- Mercedes-Benz locks horsepower behind paid subscription (rev 71955): filled the two empty response sections from the MBUSA press release, Motor1's 2024 subscription retrospective, and The Verge's 2022 and 2023 coverage. Corrected the Cargo StartDate from 2023-04 to 2022-11 — the $1,200-per-year listing appeared in Mercedes-Benz USA's shop in November 2022 (Carscoops, The Verge), with April 2023 the official launch of the tiered pricing — and the year category flipped accordingly. Filled the empty Cargo Status (Active; the upgrade is still listed in the MBUSA shop) and the empty Description. Fixed two typos ("customer" to "customers", "marketed has" to "marketed as").
- ASUS "sliding clip" battery connector defect (rev 71956): filled the two empty response sections — the CID policy quoted from ASUS's own support FAQ (verified against the live page), the May 2024 apology and repair-clarity pledges (PCMag, Tom's Hardware), with the article noting those statements were not connector-specific, plus NorthridgeFix's repair videos (oEmbed-verified live) and two further Reddit threads documenting the failure and a warranty denial. Removed the "silent insulation fix in late-2024 models" claim from the Background and the Cargo Description — I could not source it anywhere and am happy to restore it with a citation. Dropped TUF Gaming from the Cargo ProductLine for the same reason. Normalized the references: every named reference was defined twice with different bodies (an inline Cite web version and a second set inside the reflist); the reflist duplicates are removed and the inline definitions kept.
- Covert web-to-app tracking by Meta and Yandex (rev 71957): removed the orphaned categories placeholder that sat below the References section (the real categories were already in place). Replaced the two Wikipedia citations in Background with the research paper (Vlummens et al., "Bridges to Self: Silent Web-to-App Tracking on Mobile via Localhost", USENIX Security) and the IMDEA Networks press release. Corrected the Cargo EndDate from 2025-01 to 2025-06-03 — both companies stopped the transmissions by June 3, 2025 per the research site and The Register — and the Meta timeline from "late 2023" to September 2024 (Ars Technica and IMDEA). Added the Meta, Yandex, and Google statements to the response section and fixed a typo.
- Vulcan Strength (rev 71958): filled the consumer-impact summary and removed its placeholder — the defense fundraiser total updated from "over $70,000" to $84,633 from about 1,700 donations as of this week, the r/GarageGym donor roundup (Iron Bull Strength at $2,000, Bells of Steel at $1,200, and the creator commentary), and Gluck's remarks to PPC Land on suits chilling honest reviews. Added the company's two public statements to the lawsuit section: the November 2025 court-filing post and the December 2025 statement announcing the supplemental complaint.
Citation note: the Wayback save endpoint refused all new saves today (HTTP 429 across the board), but the availability API turned up existing snapshots for all but one of the new citations, so only The Verge's April 2023 pricing piece is cited live, along with the Reddit threads (never archivable), the MBUSA shop page, and the r/GarageGym roundup — all with access-dates.
Thanks as always, and thank you for clearing the November 9 batches and the November 10 batch so quickly. — WTFelvemage (talk) 13:28, 11 November 2026 (UTC)
Tag removal requests and corrections, batch of 5 (11 November 2026)
[edit source]Five more; requests and disclosures below.
- ILife (rev 71961): filled the consumer-impact summary and all incident sections, removing the four placeholder boxes. Fixed the Cargo (the Founded field said 2025-11-01, which is the date of the Tom's Hardware article — the company's own about page dates its founding to 2010, cited live) and a "vaccum" typo. Removed a broken {{Main}} call whose target parameter contained the literal placeholder text "link to the main CR Wiki article" — no target page exists. Expanded the A11 remote-kill incident with the verified timeline from the owner's blog and Tom's Hardware (telemetry including a live 3D home map and unencrypted Wi-Fi credentials; the device died after the telemetry block and a log entry showed a remote disablement), documented that iLife has never publicly responded, and added the community reaction with its documented skepticism (the top Hacker News and Reddit comments). Two notes: Wayback was hard-blocking this IP all session (CDX 429s plus an abuse-block on web.archive.org), so the new Hacker News and company-page citations are live with access-dates — the pre-existing refs kept their existing archives. And the company facts rest on the company's own about-page text plus third-party brand pages; the sandboxed fetches of iliferobot.com were network-blocked, so please sanity-check that one live ref if it looks off. Requesting {{Stub}} and {{Incomplete}} removal.
- Venmo (rev 71962): filled the consumer-impact summary placeholder. Reworded one existing claim: the article said a 2018 study "found" that Venmo "shares an enormous quantity of private data about users' lives by default" — that phrasing could not be verified against the blocked MarketWatch page, so the sentence now describes what the study covered (200 million public transactions, purchase histories exposed) and adds The Guardian's contemporaneous reporting on the same study. Added the FTC's February 2018 settlement with PayPal over Venmo (privacy-settings and "bank-grade security" misrepresentations plus a Gramm-Leach-Bliley Act violation — the settlement language is quoted from the FTC's own release) and the May 2026 friends-only default change for new users, including Business Insider's critique that the new default is "not even really private" while friend lists remain public. The FTC citation is live because ftc.gov refused this IP all session. Requesting {{Stub}} removal.
- MIRC (rev 71963): filled the empty Cargo Description and the consumer-impact summary placeholder, and converted the license timeline from bare bullets into prose with the original FAQ blockquote. Two citation-form fixes: the four archived registration-page refs carried `|url-status=deviated`, which is not a valid CS1 value — the live page works but shows different content, so they now use `|url-status=usurped`; and the register-page archive URLs dropped an unnecessary `:80` port that CS1 flags as an unfit URL. All five archived snapshots in the timeline (2015 lifetime, 2015 ten-year, 2015 "several year", 2018 three-year, 2024 one-year) were verified directly against the Wayback captures this batch. Added the r/mIRC 2020 thread documenting the version-7.x behavior (reinstallations reject expired keys) and the December 2022 Reddit reaction. One gap I could not close: Khaled Mardam-Bey's "consider registering again" FAQ text, which POC Network transcribed, could not be found in any archived page — it is not quoted in the article. Requesting {{Incomplete}} and {{Cleanup}} removal.
- Box Tops for Education (rev 71964): filled the consumer-impact summary placeholder with the program's documented scale ($953 million paid to schools as of 2021, per The Takeout's 25-year retrospective, cited live), the receipt-scanning privacy concern already sourced to The Atlantic, and the participation decline. Added a current-state paragraph noting that physical box tops were accepted only until they expired and the app is now the sole redemption path. The existing General Mills, Today, and Atlantic refs were kept as-is. Requesting {{Stub}} removal.
- Kayo Sports requiring location to stream (rev 71965): filled the empty company-response placeholder, which was the page's main gap. Kayo's own help pages (verified live; the moderator's earlier geo-restriction note applied to the legacy help-domain path, but the current kayosports.com.au article path loads fine from Canada) state the September 24, 2025 start, the precise-location requirement, and the "most relevant streaming experience" rationale, with the very-remote-regions page documenting the QR-code flow and the postcode-based geoblocking that the location enforcement serves. Added WhistleOut's reporting on the March 2025 Foxtel Group rights withdrawal for context, and expanded the consumer response with the July 2026 "should be boycotted" thread (2,319 points, documented cancellations), the Whirlpool reports of false positives (a Starlink customer geolocated to Perth blocked as remote), and the documented VPN conflict. The new citations are live: Wayback 429'd this IP all session; the September 2025 Reddit ref kept its existing archive. One verification note: the July 2026 all-platforms expansion is confirmed by three independent sources, but none pins the exact July 2 start date already in the Cargo, so that field was left as-is. Requesting {{Stub}} removal.
General note for this batch: web.archive.org and ftc.gov both hard-blocked this IP for the entire session (429s plus an abuse-block), so the handful of new citations are live with access-dates; every pre-existing archive link was kept. Thanks as always. — WTFelvemage (talk) 16:26, 11 November 2026 (UTC)
Done. — Sojourna (talk) 06:00, 12 November 2026 (UTC)
Tag removal requests and corrections, five-article cleanup (12 November 2026)
[edit source]Five user-approved article cleanups. All five retain their existing Stub or StubNotice tag; the empty section placeholders were removed as the sections were filled. Requesting review and removal of the remaining stub tags.
- Starlink replaces subscription pause with $5/mo low speeds (rev 71988): filled the incident and consumer-response placeholders and added Starlink's response. Corrected the speed description to a 500-kilobit-per-second cap, distinguished Mini hardware from subscription plans, and added the market/account exceptions, Residential-capacity warning, and free-cancellation/available-plan caveat. Replaced the exact September 12 effective-date assertion with the documented 30-day transition: the reproduced notice's September 12 opt-in deadline differs from CNET and Drive Tesla's September 13 reporting, so I could not verify one universal effective date. Consolidated the duplicate Verge references and replaced the CNET citation with PCMag's more precise coverage; CNET's claim that Standby guarantees a returning slot conflicts with the Residential caveat. Criticism is attributed to Thomas Ricker, and PCMag's favorable user reactions are included too. Requesting StubNotice removal.
- Tesla locks horsepower behind paywall (rev 71989): filled both response sections, using Tesla's advertised description rather than inventing a response to criticism. Filled StartDate with the December 19, 2019 launch-report date; added the original Model Y expansion in September 2020. Replaced the undated performance comparison with separately sourced 2019 Model 3, 2020 Model Y, and refreshed 2025 Model Y figures. The old Model 3 4.2/3.7-second figures occur in a 2022 guide, but are not the 2019 launch figures; the Performance-trim comparison was removed to avoid mixing specifications from different dates. Removed the blanket 50–100-horsepower/full-power assertions and narrowed eligibility. Added the initial-purchase refund limitation, the distinction from Performance/Track Mode, and both critical and favorable commentary. Removed the general OTA-pioneer background and its MotorTrend citation as peripheral; replaced the redundant Evannex citation with the original Model Y launch reporting. Requesting Stub removal.
- Tesla locks battery range behind paywall (rev 71990): filled both response sections and corrected the central scope. The upgrade was for eligible recent US Model Y RWD vehicles, not every pre-May-2024 RWD; July offers were up to 30 miles for $1,000 or up to 50 miles for $1,600, vehicle-dependent, rather than a universal $1,600 unlock to 320 miles. Separated the May proposal from July rollout and retained the range-estimate disclaimer. Added Tesla's NHTSA-hosted July 15 service bulletin, its VIN-specific applicability and software/activation instructions, Tesla North America's launch message, and Musk's explanation for charging. StartDate now uses the May 3 US-local announcement date; Cargo now identifies Tesla Model Y as the product instead of the former RWD Model Y product-line value. Removed unsupported blanket claims about identical batteries/weight/charging curves, factory-option availability, and universal eligibility; replaced the Tesla Oracle/Electrify News material with narrower contemporaneous reporting and the primary bulletin. The general OTA-pioneer paragraph and MotorTrend citation were also removed as peripheral. Criticism is attributed, and the text distinguishes unused capacity from withdrawal of the originally advertised range. Requesting Stub removal.
- Meta Oculus Quest 1 deprecation (rev 71991): filled both response sections and restructured the phased timeline. Corrected the UploadVR citation from February 28 to January 31, 2025; the article now distinguishes that contemporaneous block report from Meta's revised primary notice, which explicitly extends existing-app updates through May 1 and ends support May 2, 2025. The extension itself is undated, so I have not invented its publication date or a day-by-day enforcement history. Replaced the incorrect immediate January 2023 new-app ban with the later developer email setting April 30, 2024. Corrected Cargo dates to the announcement already documented by January 9, 2023 and the announced May 2, 2025 final update cutoff; normalized Unresolved to Active because the restrictions remain. Removed the unsupported claim of fifty OS releases (v50 is a version identifier), the claim that a final patch was issued in August 2024 (the sources establish maintenance through that month), and archive timestamps treated as publication dates. Replaced the two older support-page citations with the primary developer guidance and contemporaneous coverage. Preserved the distinction between lost Home/Party features and continued existing-app use, and added Meta's separate-build/180-day-notice guidance plus documented mixed reactions. Requesting Stub removal.
- Chuwi - 7430U product false advertisement (rev 71992): filled consumer response with an attributable January 24, 2026 Linus Tech Tips purchaser report, including the storage mismatch, reported return-shipping demand and attempted chargeback, without claiming a completed refund or chargeback. Narrowed the CPU findings to Notebookcheck's inspected CoreBook X and retailer-purchased CoreBook Plus, and replaced the condemning section heading with a neutral specification-discrepancy heading. Replaced the incomplete, inaccessible Sina reference and its Citation needed marker with OC3D's readable March 18 translation of AMD's statement; preserved Sojourna's original inline note verbatim with historical context. AMD reserved legal rights; the article does not claim a lawsuit. Removed the unverifiable December 2025 Reddit-date assertion and replaced the unreadable Reddit-based storage sourcing with the readable purchaser report; happy to restore the earlier date if someone can verify its source. Removed the subjective assessment of Chuwi's response and speculative prediction that returns could be denied; retained the actual original-condition/accessories requirement and May 31 refund deadline. StartDate now records the verified July 2, 2025 launch announcement. Trimmed incidental company/Intel-line background to focus on the affected specifications. Please also consider a neutral title such as "Chuwi CoreBook processor specification discrepancy". Requesting Stub removal.
Citation and verification note: every cited live source was opened and checked, including the downloaded Tesla service bulletin. Existing archive links on retained sources were preserved. Wayback's CDX and replay endpoints returned HTTP 429 throughout the parent checks, and the save probe was also refused with 429; availability returned some snapshots but their contents could not be replay-verified. Consequently the new PCMag citation; Electrek's original Model Y launch and owner-testing articles; the Energy Boost bulletin, July Electrek/Teslarati reporting and Fortune article; the Ars Technica, Road to VR, XDA and additional Meta developer-guidance articles; and OC3D/Linus Tech Tips are cited live with access dates rather than with unverified new captures. Existing archive contents could not be revalidated this session. The expected url-status maintenance notices were left alone. All five saved revisions were read back and parsed: sections and references render, with no article redlinks, reference errors, or CS1 error categories.
Happy to restore trimmed material with suitable sourcing. Thanks as always. — WTFelvemage (talk) 02:39, 12 November 2026 (UTC)
Done. Thanks for all the work you've been doing! :) — Sojourna (talk) 07:03, 12 November 2026 (UTC)
- My pleasure! :) WTFelvemage (talk) 14:57, 12 November 2026 (UTC)