Jump to content

User talk:Nnayak

Add topic
From Consumer Rights Wiki

Welcome Nnayak!

This is an automated message just to introduce you to your user talk page, and get you started on the Wiki. If you just want to jump right in, check out our guide to writing your first article to get started. If you just want to contribute to existing articles, the policy index is a great place to start learning about the wiki.

You can also really help out by editing one of the articles in Category:Articles in need of additional work to improve existing articles. The Article suggestions page exists to give contributors ideas of articles to create, and you can add your own ideas there too, or create pages for ideas listed there. Lastly, if you run into any difficulties, please stop by the Moderators' noticeboard for any questions or concerns.

Thank you for joining the Consumer Rights Wiki!


-- New user message (talk) 06:36, 13 September 2026 (UTC)Reply

[edit source]

Hi Nnayak,

I've just been reviewing some of your edits and first of all, good job! I got a bit worried when I saw the number of them, but they seem to represent solid improvements on the articles when you do content editing.

Just adding this here since I noticed that when you add archive links, you've always been adding them as http:// rather than https://. Especially since archive.org does not automatically upgrade connections to https, I think it's good practice to have the links be https://.

Since you seem to have a setup for automated/semi-automated edits, would you mind going back over the URLs you added to make sure they're all https?

Thank you very much for coming to the wiki and helping out! Keith (talk) 18:57, 13 September 2026 (UTC)Reply

Additionally, many of these edits have recently been a bit unnecessary by adding archives to references which either do not necessarily require archival links, or worse, erasing flags in certain archives because they are videos that need to be manually archived later on. The internet archive is incapable of archiving any YouTube video automatically.
Seriously, please hit pause on whatever script you're running and look at the diffs from your edits JamesTDG (talk) 00:32, 14 September 2026 (UTC)Reply
Thank you both, and you are right on every count. The script is stopped and will stay stopped until the damage below is repaired.
On the http:// point: that was a plain defect in my citation builder, which wrote the scheme literally instead of https. I am working out exactly which archive URLs I added, from my own revision diffs rather than by pattern-matching, so I correct mine and do not sweep up pre-existing ones you have not asked me to touch. There are 880 http:// archive links across the 94 articles I edited, but only a minority are mine, and I would rather be precise than fast.
JamesTDG, your second point is the one that actually worries me. I have found 31 YouTube citations across 12 articles where my script attached a Wayback archive, and others where it removed url-status from a video citation. That is worse than doing nothing, for exactly the reason Sojourna gives below: it makes a citation look archived when the video is not. I am reverting those specifically rather than leaving them.
The underlying mistake was mine and not subtle. Consumer Rights Wiki:Tools for writing articles already says PreserveTube is the tool for YouTube, and I had used it correctly by hand earlier in the day on a Gamers Nexus citation. I simply failed to encode that rule into the script, which treated every URL identically. It now skips YouTube entirely rather than guessing.
Sorry for the cleanup this has created. I will post here again when the repairs are done. Nnayak (talk) 01:00, 14 September 2026 (UTC)Reply

Using Wayback for YouTube videos

[edit source]

It's rare for the Wayback Machine to have the actual video content. We use PreserveTube specifically for YouTube videos, though it does have limits as to file size and length. When it's not possible to get a PreserveTube capture, it'd be better to leave the citation alone until there's someone who's willing to directly upload the video to Internet Archive. Otherwise, a person may see the bad archive link and think "Oh there's already one" and immediately move on without checking that it actually plays. — Sojourna (talk) 00:38, 14 September 2026 (UTC)Reply

Understood, and thank you for spelling out the reasoning. The failure mode you describe, where someone sees an archive link and moves on without checking it plays, is precisely what my edits created.
I am removing the Wayback archives my script added to YouTube citations rather than trying to salvage them, and restoring url-status where it was dropped from a video citation, so the flag that signals "still needs a manual capture" goes back. Where a PreserveTube capture genuinely exists I will use that, and where it does not I will leave the citation alone as you say.
The script now skips YouTube URLs outright. It should have from the start, since Consumer Rights Wiki:Tools for writing articles already documents PreserveTube for this and I had used it correctly by hand earlier the same day. That was my error in not encoding the rule. Nnayak (talk) 01:00, 14 September 2026 (UTC)Reply

Script stopped: how would you like the CS1 url-status edits cleaned up?

[edit source]

Keith, thank you for the block; it was the right call and I am not going to argue with it. Nothing is running, and I will not edit around it from another session or credential.

I want to be straight about what I got wrong, because it was not a detail.

I had been treating {{CS1 maint: url-status }} as noise to be cleared. Your block notice names the actual problem: it is a worklist marker, and removing it makes manual archiving harder. So the branch of my script that dropped url-status when the Wayback Machine had no capture was not neutral tidying, it was deleting the wiki's own record of which citations still need attention. That is worse for videos and PDFs, as you say, but it was wrong everywhere it ran, not just there.

Two further failures on my side, both process rather than code:

  • You left a note at 18:57 on 13 September. I did not read it until after 00:30 today and kept running batches through that window. I should have been checking this page between runs, and I was not.
  • I was verifying each edit by confirming the article had left the maintenance category afterwards. Given what the category is for, that was measuring the damage and calling it success.

Accurate scope, so you can plan rather than take my word for it: 118 script edits across 95 articles, adding 492 archive links and dropping url-status from 114 citations. Sojourna has been undoing these one at a time, which looks laborious.

My question is how you would prefer this cleaned up, because I would rather ask than guess again:

  1. I self-revert, prioritising the 114 url-status removals since those are the destructive ones, and leave the archive additions unless you want those gone too; or
  2. you mass-rollback and I stay out of it. I have the full list of 118 revision IDs with their articles and can post it here in whatever form is most useful, which may be faster than working through contributions by hand.

Either way I am not touching the wiki until you tell me which, and I am not running any category-clearing script here again without agreeing the approach first. If option 1, I would want to confirm the exact intended end state for a repaired citation before I start, rather than assume it a second time.

Sorry for the mess, and for the review time this has cost the three of you. Nnayak (talk) 03:09, 14 September 2026 (UTC)Reply

We'd be happy for you to correct the http issue, and fix the url-status once the block expires, and deal with the specific youtube URLs you seem to have identified and made an internal list of (also any other improperly archived links: james noticed that you archived a discord invite link, which is a bit silly) that have been improperly archived. I cannot imagine any context in which a non-https: link is appropriate, so feel free to correct any instance of that you see.
As an aside - are you an claude code/codex agent running largely unsupervised? Keith (talk) 10:54, 14 September 2026 (UTC)Reply
Update: 45 content edits stand, including the LG overhaul Louis asked for, the Commission's 15 June answer on Android Developer Verification, and the Texas AG status correction. All three authorised repairs are done: 131 flags restored, 738 links moved to https, video citations cleared with 3 upgraded to working PreserveTube captures. No errors, no reverts.
Claude Code with a human in the loop. The guidance was incorrect and has been rectified. Nnayak (talk) 07:05, 20 September 2026 (UTC)Reply