🇮🇷 Iran Proxy | https://www.wikipedia.org/wiki/User_talk:Zinnober9
Jump to content

User talk:Zinnober9

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive
Archives

Archive 1 (2017 – 2023)
Archive 2 (2024 – 2024)
Archive 3 (2025 – )

A kitten for you!

[edit]

Thanks for the assist on my User Page!

 𝕆𝕜𝕚𝕖𝕓𝕝𝕠𝕜𝕖𝕨𝕚𝕝𝕝 ➢✧ 13:27, 28 October 2025 (UTC)[reply]

You are welcome, cheers. Zinnober9 (talk) 14:47, 28 October 2025 (UTC)[reply]


Guide to temporary accounts

[edit]

Hello, Zinnober9. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.

Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.

How do temporary accounts work?

Editing from a temporary account
  • When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern: ~2025-12345-67 (a tilde, year of creation, a number split into units of 5).
  • All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
  • A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
  • As a measure against vandalism, there are two limitations on the creation of temporary accounts:
    • There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
    • There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.

Temporary account IP viewer user right

How to enable IP Reveal

Impact for administrators

  • It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
  • It will still be possible to block an IP address or IP range.
  • Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).

Rules about IP information disclosure

  • Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
  • Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g. ~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67)
  • See Wikipedia:Temporary account IP viewer § What can and can't be said for more detailed guidelines.

Useful tools for patrollers

  • It is possible to view if a user has opted-in to view temporary account IPs via the User Info card, available in Preferences → Appearance → Advanced options → Tick Enable the user info card
    • This feature also makes it possible for anyone to see the approximate count of temporary accounts active on the same IP address range.
  • Special:IPContributions allows viewing all edits and temporary accounts connected to a specific IP address or IP range.
  • Similarly, Special:GlobalContributions supports global search for a given temporary account's activity.
  • The auto-reveal feature (see video below) allows users with the right permissions to automatically reveal all IP addresses for a limited time window.

Videos

  • How to use Special:IPContributions
  • How automatic IP reveal works
  • How to use IP Info
  • How to use User Info

Further information and discussion


Late thanks!

[edit]

I know I'm a bit late (~7 months), but I still did want to thank you for fixing my userpage! dot.py 08:51, 1 November 2025 (UTC)[reply]

No problem, cheers. Zinnober9 (talk) 21:25, 1 November 2025 (UTC)[reply]

Kozograd castle

[edit]

Thanks for catching my error on Kozograd castle. Sometimes I click through my edits too quick ignoring my own advice. Appreciate you catching it! Zackmann (Talk to me/What I been doing) 06:27, 8 November 2025 (UTC)[reply]

No problem, glad you knew what was needed. Hope you have a great weekend. Zinnober9 (talk) 06:39, 8 November 2025 (UTC)[reply]

Delinitng..

[edit]

Care to take a second look over some of my efforts? ShakespeareFan00 (talk) 22:50, 11 November 2025 (UTC)[reply]

Is there something particular you have in mind? Zinnober9 (talk) 23:28, 11 November 2025 (UTC)[reply]
(talk page stalker) Some feedback: this one should have at least removed the word "face" from the /font tag; in this one, you added two closing braces that should not have been added. In this edit, you left behind a stray bold tag; removing all except obsolete tags makes it more likely that bots will be able to tidy up the page after you leave. I then looked at about ten in a row that looked good, especially this tricky one. And one last thing: Always, always use an edit summary. Turn on the gadget that reminds you to leave an edit summary.
Some general recommendations: Use a more helpful edit summary with a link that explains what Linter errors are. My default is "Fix Linter errors." When I leave behind obsolete tags, I write "Fix Linter errors. More needed. Leaving obsolete tags for bots." When I edit in User space, where people tend to be more protective of their pages, I add: "I hope you don't mind this minor cleanup edit in your user space." Also, use the LintHint script, and keep fixing errors and clicking and unclicking the LintHint button until you have only obsolete tags remaining. That way, bots will have a good chance of fixing the rest of the page. – Jonesey95 (talk) 00:22, 12 November 2025 (UTC)[reply]
I had mind these:-
misnested div
Omitting User space for now. Any chance you could explain how to resolve misnested DIV?ShakespeareFan00 (talk) 08:50, 12 November 2025 (UTC)[reply]
Ah. I read your initial comment as Jonesey did with you asking for a review some of your recent edits, and didn't want to just dive in without some sort of focus. I agree with their comments however.
As for the misnested div issues, those typically boil down to one of two types of issues, a div based template that can't be bulleted or indented, or some unclosed (non-div) tags within a div based template triggering the extra reported errors. I ran into some variations of these when clearing the HTML5 misnests.
This is how I fixed each of those "A" pages (and their div error comment):
Indented issue:
Bulleted issue:
False div by others:
There was something rather odd on Wikipedia:Administrators' noticeboard/IncidentArchive1010 causing LintHint to breakdown entirely, so I had to remove the first eleven or so sections temporarily while editing to get LintHint to work on that page. The incredibly odd thing was that no particular section was at fault. I tried narrowing it down, and when I separated it at Ape Spam, both halves (of the eleven) were functioning with LintHint. Since it wasn't causing an actual lint error to be reported, and I wasn't seeing anything particularly wrong, I left that be.
Happy to help with others if stuck or interested, Zinnober9 (talk) 21:02, 12 November 2025 (UTC)[reply]
Feel free to continue with other letters, like you had been doing with closing italics. Here the issue is structural 'glitches'. I was working slowly through misnested spans. If you want to handle DIV's and Tables.:) ShakespeareFan00 (talk) 21:18, 12 November 2025 (UTC)[reply]
Sounds good. Looks like 55 non-userspace divs remaining, 620 userspace divs remaining. I don't see any misnested "table" issues though, but I see a few td/tr/th misnested cases. Should be all gone in a week or two. I'm getting excited on the quickly dwindling mainspace italics since this past week's efforts have been dropping the backlog quicker than the average 1k a week, so I think a few additional people are dipping into going after these now that we're getting closer. Zinnober9 (talk) 23:16, 12 November 2025 (UTC)[reply]
Administrators' noticeboard/IncidentArchive pages can be the most difficult pages to fix, because they are long and contain many sections wrapped in div-based templates, so the whole section is highlighted by LintHint instead of just one bit of code. My approach to them is typically twofold: 1. Turn on the syntax highlighter gadget (I always have it on), and start at the top of the page, scrolling down and fixing errors as I go so that the blocks of text are white, yellow, or pink and not gray or blue. 2. Then re-run LintHint, use it to target sections with errors, and copy-paste those errors to Special:ExpandTemplates, where you can use LintHint to find the actual line(s) of text with the error(s). Fix the errors, then copy the whole unexpanded wikitext back, replacing the section that you copied. This second step takes extreme care to ensure that you don't replace the wrong section or paste the text block into the wrong browser tab. Always click "Show changes" and check your diffs before saving any changes made in step 2. Those pages are a minefield; be careful out there. – Jonesey95 (talk) 02:04, 13 November 2025 (UTC)[reply]
Omitting userspace, these 55 divs are now down to 4:
  • Talk:2016 United States presidential election has {{consensus}} trying to host a {{plainlist}} template. I'm strongly suspecting consensus's text parameter is inline and not block, so unless I'm missing how to get consensus to behave as a block (adding |div=yes didn't work), changing the template to support block text is likely the change needed. I'm not immediately aware how to change that.
  • Talk:Joseph (opera) While adding |div=yes clears a missing stripped div pair, there remains two misnested and a stripped div for some reason I can't work out, and it isn't the content within the {{Collapsed infobox section begin}}, I tried a begin immediately followed by its end for same results.
  • Wikipedia:WikiProject COVID-19/Case Count Task Force. Same as Joseph. While this one also needs a |td=yes (to the first for the td error) and the Graph extension needs to be rewritten to Chart extension, there's still something afoot with two misnested and a stripped div per appearance of {{Collapsed infobox section begin}} that I haven't worked out.
  • Talk:Gender Trouble Not sure what's more important, how it displays or how it's written. Removing the indents does something crazy with the Zeman ref in displaying that centered, otherwise I'd do this:
{{sfn|Zeman|Kapur|Jones-Gotman|2012}}{{rp|71}}
:===Notes===
{{Reflist|colwidth=25em}}
:===References===
{{refbegin|2}}
:*{{cite book|last1=Zeman|first1=Adam|last2=Kapur|first2=Narinder|last3=Jones-Gotman|first3=Marilyn|title=Epilepsy and memory|year=2012|publisher=Oxford Univ. Press|location=Oxford|isbn=978-0199580286|edition=1. |url=https://books.google.com/books?id=cwJREAAAQBAJ&dq=Epilepsy+and+memory&pg=PP1}}
{{refend}}
While the ref templates do need to be unindented, something more is needed to not have Zeman in the middle and I'm not sure what that is. Zinnober9 (talk) 17:03, 16 November 2025 (UTC)[reply]
All fixed. Nice work. – Jonesey95 (talk) 22:49, 18 November 2025 (UTC)[reply]
I see they were easier than I was making them. I appreciate you taking care of these! Zinnober9 (talk) 00:11, 19 November 2025 (UTC)[reply]
{{Collapsed infobox section begin}} often creates a tag mess, and it goes against MOS:HIDE. I often just remove it. – Jonesey95 (talk) 03:01, 19 November 2025 (UTC)[reply]

Jonesey95: If {{Collapsed infobox section begin}} goes against MOS:HIDE, why does it exist at all? I have seen pages where it seems to be helpful. However, it's problematic on other grounds. Infoboxes are just templates. The parameters of a template can be listed in any order. The use of {{Collapsed infobox section begin}}...{{Collapsed infobox section end}} presupposes that the infobox parameters it surrounds are all within a single display section and no infobox parameters elsewhere in the infobox markup are displayed in this section. These assumptions might not be correct. And none of this is documented. —Anomalocaris (talk) 01:56, 21 November 2025 (UTC)[reply]

You are welcome to document this major problem with that template, and you are welcome to open a discussion on its talk page (or on the MOS talk page) about whether it should exist at all. I don't have a strong opinion about it, but when it causes problems, I have no qualms about using MOS to justify its removal. – Jonesey95 (talk) 02:21, 21 November 2025 (UTC)[reply]
Jonesey95: Heh. I did open a discussion on this at Template talk:Collapsed infobox section begin#LintHint errors on 3 October 2021. Nobody responded. —Anomalocaris (talk) 03:35, November 21, 2025
You could try again with a new section, or take it to a wider audience at templates for discussion. I don't like how blindly hit and miss it is with working cleanly, and the MOS issue is probably something that needs to be worked out. Zinnober9 (talk) 22:10, 21 November 2025 (UTC)[reply]

Misnested tags::

[edit]

Wow - misnested big

I thought I hadn't attempted as many as I thought. Want to clear out the last few, and then move onto others? ShakespeareFan00 (talk) 23:48, 19 November 2025 (UTC)[reply]

Done. Fairly straightforward. Some were transcribed or were a byproduct of unclosed p tags within something else. Still working on the divs in userspace from the previous conversation, and making really great headway on the unclosed tags in main, so I'm going to pass on the 7500 misnested bigs in userspace at this time. Hoping we all get those italics in Main cleared off before New Years; looking very likely with the current community rate of 3k a week based on last week and this week's progress. Zinnober9 (talk) 01:44, 20 November 2025 (UTC)[reply]

Q tag misnesting cleared , apart from 2 !

[edit]

Progress. :-

misnested q

em tags might also had attemtped misnesting removal. ShakespeareFan00 (talk) 17:46, 20 November 2025 (UTC)[reply]

Cleared the q tags (including the last few in userspace). Mainly misnested italics that got intertwined. Had no idea on one, but it was an old draft on a sockpuppet account (2015), so felt comfortable blanking outright. Zinnober9 (talk) 18:34, 20 November 2025 (UTC)[reply]

Another thanks, for a similar yet different reason

[edit]

Hello! I just wanted to let you know that your efforts on fixing WP:LINT errors has actually inspired me to start fixing lint errors, so I wanted to thank you for that! dot.py 03:35, 26 November 2025 (UTC)[reply]

Welcome, glad to have you! If you have any questions, feel free to ask, either at Wikipedia talk:Linter or here.
Some links I find incredibly useful that might help you:
I also highly recommend the LintHint tool for scanning a page for errors remaining while editing a page. User:PerfektesChaos/js/lintHint has info on how to add the tool to your common.js page.
I'll mention that we are skipping 'Duplicate ID' errors and 'Background color inline style...' errors; they are mostly tracking categories right now.
Cheers, Zinnober9 (talk) 03:02, 27 November 2025 (UTC)[reply]

Care to do some tag matching at Wikisource?

[edit]

https://en.wikisource.org/wiki/Special:LintErrors/stripped-tag

Mostly it's finding which DIV tags (and templates) haven't been matched up between different pages.

Thanks. ShakespeareFan00 (talk) 00:44, 29 November 2025 (UTC)[reply]

I haven't gotten the feel for the (sub)pages over there, so I'm going to pass. I did take a whack at some of the empty headers over there, will go back for some more tomorrow. Zinnober9 (talk) 04:30, 30 November 2025 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Zinnober9&oldid=1325213409"