W
Active Editors
Back to Profile

User Talk: Zinnober9

Server-side rendered snapshot of this editor's Wikipedia talk page discussions.

{{NoACEMM}}
{| class="infobox" width="270px"
|-
!align="center"|Archive ↗<br>Archives ↗
----
Archive 1 (2017 – 2023)<br>
Archive 2 (2024 – 2024)<br>
Archive 3 (2025 – )<br>
|}<!--Template:Archivebox-->

A kitten for you!



left|150px ↗
Thanks for the assist on my User Page!

<span class="nowrap" style="border:solid 4q cyan;border-radius:9in;padding:1q-1q;box-shadow:0 0 9q white">&nbsp;<b style="font-family:Garamond">𝕆𝕜𝕚𝕖𝕓𝕝𝕠𝕜𝕖𝕨𝕚𝕝𝕝</b> <b style="color:white" >➢✧</b> </span> 13:27, 28 October 2025 (UTC)
<br style="clear: both;"/>

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


Guide to temporary accounts



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?'''

thumb|350px|Editing from a temporary account ↗

'''Temporary account IP viewer user right'''

thumb|350px|How to enable IP Reveal ↗

'''Impact for administrators'''


'''Rules about IP information disclosure'''


'''Useful tools for patrollers'''


'''Videos'''
<gallery>
Temporary Accounts demo - IP Contributions.webm|How to use Special:IPContributions
Temporary Accounts demo - IP Auto-reveal.webm|How automatic IP reveal works
Temporary Accounts demo - IP Information.webm|How to use IP Info
Temporary Accounts demo - User Info Card.webm|How to use User Info
</gallery>

'''Further information and discussion'''


<!--copied by Zinnober9 from another user's talk page, omitting signature/timestamp -->

Late thanks!



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

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

Kozograd castle



Thanks for catching my error on Kozograd castle ↗. Sometimes I click through my edits too quick ignoring my own advice. Appreciate you catching it! '''<span style="color:#00ced1">Zack</span><span style="color:#007F94">mann</span>''' (<sup>Talk to me ↗</sup>/<sub><span style="color:orange;">What I been doing</span> ↗</sub>) 06:27, 8 November 2025 (UTC)

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

Delinitng..



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

:Is there something particular you have in mind? Zinnober9 (talk) 23:28, 11 November 2025 (UTC)
:{{tps}} 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)
::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)
:::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:
:::*Talk:AD 1 ↗ (indented div based templates)
:::*Wikipedia:Australian Wikipedians' notice board/Archive 63 ↗ (indented div based templates)
:::*Wikipedia:Administrators' noticeboard/IncidentArchive1010 ↗ (indented div based template (trout))
:::*Wikipedia:Administrators' noticeboard/Incidents/Noleander ↗ (indented div based template (trout), stray archive top causing stripped div)
:::*Talk:Al-Ahbash/Archive 9 ↗ (indented divs)
:::*Talk:American Society of Composers, Authors and Publishers/Archive 1 ↗ (linefeed+indent broken cite, indented reflist-talk).
:::Bulleted issue:
:::*Wikipedia:Arbitration enforcement log/2009 ↗ (unbullettable div based template)
:::False div by others:
:::*Wikipedia:Arbitration Committee Elections December 2014/Candidates/Guerillero/Questions ↗ (unclosed p tags, no actual div error. Swapped p to {{tl|pb}} for simplicity)
:::*Wikipedia:Arbitration Committee Elections December 2013/Candidates/Roger Davies/Questions ↗ (some mess of unclosed/stripped ul / ol / li / p tags. While li tags don't require a close, I'm opposed to leaving them open, and it interferes with the properly closed ul/ol tags turning red with the syntax highlighter, so I close them when I see them.)
:::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)
:::: 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)
:::::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)
:::::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 <em>extreme care</em> 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)
:::Omitting userspace, <span class="plainlinks">these 55 divs are now down to 4 ↗</span>:
:::*Talk:2016 United States presidential election ↗ has {{tl|consensus}} trying to host a {{tl|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 {{para|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 {{para|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 {{tl|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 {{para|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 {{tl|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:
<pre>
{{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}}
</pre>
:::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)
::::All fixed. Nice work. – Jonesey95 (talk) 22:49, 18 November 2025 (UTC)
:::::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)
::::::{{tl|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)
{{Outdent}}
Jonesey95: If {{tl|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 {{tl|Collapsed infobox section begin}}...{{tl|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)
: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)
: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)

Misnested tags::



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)

: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)

Q tag misnesting cleared , apart from 2 !



Progress. :-

misnested q ↗

em tags might also had attemtped misnesting removal.
ShakespeareFan00 (talk) 17:46, 20 November 2025 (UTC)
: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)

Another thanks, for a similar yet different reason



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! <code>dot.py ↗</code> 03:35, 26 November 2025 (UTC)

: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:
:*fireflytools ↗ (for seeing the breakdown of what remains by namespace and error type. Is based from Special:LintErrors ↗.)
:*Special:BlankPage/lintHint ↗ (for scanning a copied section of a page for remaining errors).
:*MW:Help:Lint errors/obsolete-tag ↗ (helpful page for many X to Y suggestions on various Obsolete tags)
: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)

Care to do some tag matching at Wikisource?



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)

: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)

A barnstar for you!



{| style="border: 1px solid gray; background-color: #fdffe7;"
|rowspan="2" style="vertical-align:middle;" | 100px ↗
|rowspan="2" |
|style="font-size: x-large; padding: 0; vertical-align: middle; height: 1.1em;" | '''The Barnstar of Diligence'''
|-
|style="vertical-align: middle; border-top: 1px solid gray;" | Thank you for your edit ↗ to the Alessandro Faedo ↗ entry
|}<!--Template:The Barnstar of Diligence--> Daniele.tampieri (talk) 20:43, 10 December 2025 (UTC)

:Thank you! Happy upcoming holidays, Zinnober9 (talk) 21:04, 10 December 2025 (UTC)

The Game



your page made me lose, here’s to hopefully making you lose once more as payback (in all seriousness, thanks for clearing up that little error on my profile, hopefully with experience I can get a better handle of this wikipedia thing) Foxxeil (talk) 18:05, 14 December 2025 (UTC)

:You are welcome, cheers. Zinnober9 (talk) 18:16, 14 December 2025 (UTC)

A cup of coffee for you!



{| style="background-color: var(--background-color-success-subtle, #fdffe7); border: 1px solid var(--border-color-success, #fceb92); color: var(--color-base, #202122);"
|style="vertical-align: middle; padding: 5px;" | 120px ↗
|style="vertical-align: middle; padding: 3px;" | Thanks for fixing up my error in that gallery - went back to double check I didn't do that in another article. Haven't worked with them much before, so I really appreciate it! Happy holidays and enjoy the rest of your week. <small style="color:#0080FF;background:#EAEAFF;border:2px solid;border-radius:4px;padding:0 4px">jellyfish</small>&nbsp;&#9993; 22:22, 18 December 2025 (UTC)
|}

InternetArchiveBot and external links



I was going to make a post at the meta talk page about Special:Diff/1328723541 ↗ and saw that you had reported the issue already a week ago. Do you know how long it's been doing this?<span id="Tenshi_Hinanawi:1766327916823:User_talkFTTCLNZinnober9" class="FTTCmt"> —&nbsp;Tenshi! (Talk page) 14:38, 21 December 2025 (UTC)</span>

:{{tps}} @Tenshi Hinanawi: From at least 2023, and possibly earlier. Have a look at this thread ↗ on the meta talk page. —Bruce1ee<sup>''talk''</sup> 14:51, 21 December 2025 (UTC)
::Read, thanks. Tenshi! (Talk page) 15:41, 21 December 2025 (UTC)
:The bot issue goes back (as far as I'm aware) to Aug 2023 when Jonesey95 filed a phab ticket {{phab|T344219}}, so just prior to that I'd imagine. It's been more noticeable here on enwiki since we cleared out the link in link errors last year. I'd be a little less ticked off by it if the operator(s) would give a good reply/give an update, but near radio silence (on this and multiple other issues reported on IAB's meta talk page) is starting to look problematic.
:In my way of thinking, since the bot has the knowledge of needing to know where to put the new added archive link, it has a way of determining the add here point, and adding a "add after the existing link address, '''AND after the ]'''" doesn't seem that hard a change (granted I'm not a coder). I could understand if there's a concern about a wikilink with a double ]] appearing (shouldn't be any on enwiki since that would be a wikilink in external link error, but this error is still present on other projects), but that statement could be extended to be a '''"AND after the ] UNLESS ]] then keep searching for ]"''', surely? I truly don't know why this hasn't been fixed yet as this doesn't seem that complicated a change. Zinnober9 (talk) 15:20, 21 December 2025 (UTC)
::I can't say for sure since I have no clue how to write PHP (which IABot uses), but to me that sounds accomplishable with regex. Though the botop hasn't been that responsive on the issues with their other bot either, so I'm not optimistic it'll get resolved. Tenshi! (Talk page) 15:41, 21 December 2025 (UTC)

Season's Greetings



{| style="background-color: #fdffe7; border: 4px solid #FFD700;"
|rowspan="2" style="vertical-align: middle; padding: 2px;" | 211px ↗
|style="font-size: x-large; padding: 2px 2px 0 2px; height: 1.5em;" | '''Merry Christmas and a Prosperous 2026!'''
|-
|style="vertical-align: middle; padding: 3px;" |
----
'''Hello Zinnober9, may you be surrounded by peace, success and happiness on this seasonal occasion ↗. Spread the WikiLove ↗ by wishing another user a Merry Christmas ↗ and a Happy New Year ↗, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2026. <br />Happy editing,'''<br />
Abishe (talk) 03:28, 27 December 2025 (UTC)

''{{resize|96%|Spread the love by adding {{tls|Seasonal Greetings}} to other user talk pages.}}''
|} Abishe (talk) 03:28, 27 December 2025 (UTC)

Happy New Year, Zinnober9!


<div style="border: 3px solid #FFD700; background-color: #FFFAF0; padding:0.2em 0.4em; height:auto; min-height:173px; border-radius:1em; box-shadow:.1em .1em .5em rgba(0, 0, 0, 0.75); box-shadow:.1em .1em .5em light-dark(rgba(0, 0, 0, 0.75), rgba(255, 255, 255, 0.75));" class="plainlinks">
left|x173px ↗x173px|right ↗
{{Paragraph break}}
{{Center|{{resize|179%|'''''Happy New Year ↗!'''''}}}}
'''Zinnober9''',<br />Have a prosperous, productive and enjoyable New Year ↗, and thanks for your contributions to Wikipedia.
<br /><span style="color:orange">'''''Volten'''''</span><span style="color:lime ">'''001'''</span> <sup><b style="color:red">☎</b></sup> 05:18, 1 January 2026 (UTC)<br /><br />
</div>
&nbsp;&nbsp;&nbsp;''{{resize|88%|Send New Year cheer by adding {{tls|Happy New Year fireworks}} to user talk pages.}}''
{{clear}}<!-- From template:Happy New Year fireworks --> <span style="color:orange">'''''Volten'''''</span><span style="color:lime ">'''001'''</span> <sup><b style="color:red">☎</b></sup> 05:18, 1 January 2026 (UTC)

:Thank you and happy New Year! Zinnober9 (talk) 06:03, 1 January 2026 (UTC)

The RNZAC cease to exist as of the 5 Dec 2025



Hi Zinnoberg9,

The RNZAC cease to exist as of the 5 Dec 2025, the last unit QAMR was absorbed into the 1 Bn RNZIR as an Infantry company known as QAMR Coy 1 RNZIR,

all RNZAC personnel where transitioned over to the RNZIR and wear there insignias and cap badge.

The reserve unit the Waikato Mounted Rifles now come under the Administration of the Infantry corps,

The RNZAC does not exist, there is no Personnel , there is no Armoured Fighting Vehicles

The RNZAC is now a historical formation of the NZ Army

Kind Regards

exsap Exsap (talk) 09:33, 2 January 2026 (UTC)

:And are there Reliable Sources ↗ that can verify your claims on this? Unless reliable sources are presented, these claims may not be added to the article. WP:BURDEN ↗ is on you to reliably source any claims you add to an article. This is not negotiable. Best wishes. Zinnober9 (talk) 14:20, 2 January 2026 (UTC)
::I did a very quick check on the Gazette of New Zeland, for 2025, and haven't found an official notice as such yet. The Gazette would be a definitve source I think. ShakespeareFan00 (talk) 20:19, 2 January 2026 (UTC)

Hello.



Hi there, if you are going to edit my user page, Next time please let me know :). By the way, You did a good job on renewing my user page! Just ask to edit it next time on my talk page. Thanks! -WikiSebasTheDev *Professional Dummy :P* WikiSebasTheDev (talk). 12:47, 23 January 2026 (UTC)

:While I understand your feelings on this, when I've asked first I've received a high rate of no responses at all or "you want to do what? Why?" or "Do your thing and don't bother me" responses, so I've found it far less bother to everyone to just go ahead and make the edit so the other user can see the before and after and if they weren't pleased with the change, ask for forgiveness and figure out a solution that satisfies us both afterwards. Zinnober9 (talk) 15:42, 24 January 2026 (UTC)
::It’s alright, Just ask next time. I’m fine with your edits :) -WikiSebasTheDev *Professional Dummy :P* WikiSebasTheDev (talk). 16:28, 24 January 2026 (UTC)

Empty header



Sorry, but I have no idea how that happened. I'm getting a lot of problems today with my Talk page being "restored" and presumably other things as well. It took me four tries just to find the edit you were talking about. Deb (talk) 12:24, 4 February 2026 (UTC)

:Thanks for the reply. If you happen to find out more later on, feel free to let me know. Sorry you are having issues and hope your issues clear out for you soon. Zinnober9 (talk) 17:53, 4 February 2026 (UTC)

WP:EIS ↗ parameters Thumb and Frameless



I am confused by this edit summary ↗ in which you wrote that "''Frame(less) and thumb do opposing things''."<br>
WP:EIS ↗ says that they work together:
: <code>thumb</code> (or <code>thumbnail</code>; either can be followed by <code>=<var>'''filename ↗'''</var></code>), <code>frame</code> (or <code>framed</code>), or <code>frameless</code>. Displays the image with specific formatting (see below).
Off and running (talk) 20:23, 22 February 2026 (UTC)

:That's not quite right. WP:EIS isn't saying that they work together, WP:EIS is saying that Type can be thumb, OR frame, OR frameless. No combination. The first parenthetical is adding additional information to thumb that thumb (aka thumbnail) can be followed by =filename. End of thumb comment. OR Type can be frame (aka framed). End of frame comment. OR type can be frameless. No additional comment.
:Thumb, frame, and frameless, are three common, different, ways to display an image, and they do different display options. You had stated frameless and thumb together on each file. Here's a comparison:
{{collapse top|image display options}}
right|thumb|"thumb" display ↗
right|frame|"frame" display ↗
right|frameless|"frameless" display ↗
Frameless doesn't display a caption, thumb and frame do.
Frame doesn't accept display sizing, thumb and frameless do.
{{collapse bottom}}
:I'll agree, the Type description on the WP:EIS page is a tad complicated in phrasing, and could be smoother, but it is accurate.
:Zinnober9 (talk) 22:18, 22 February 2026 (UTC)
::Thanks. It was really confusing the way it was written at WP:EIS ↗. I therefore reworte it ↗ per your explaination. Off and running (talk) 22:41, 22 February 2026 (UTC)

My userpage



Hi. If you think something is not right on my userpage, please let me know on my talk page, and please do not modify my userpage without my direct consent. I can fix those things myself. -<span style="text-shadow:7px 5px 7px #409fff;">Mardus <small>/talk</small></span> 04:11, 8 March 2026 (UTC)

:Hello, thank you for the message. I regularly don't contact first due to the high rate of no replies I've received from people when I did contact first, or the frustration I've received from the confused and bothered users (of varying, but typically lower HTML knowledge levels) who either want to see what changes I was looking to make beforehand, or would have rathered I had just got on with it and not bothered them further. While I completely understand your feelings on this, it hasn't worked out for me in practice, so I've opted to providing clear change summaries and asking for forgiveness whenever there is an issue and offering to figuring out a solution that satisfies us both in those cases as it's been easier for both parties in most cases. I hope you are having a nice weekend, Zinnober9 (talk) 06:23, 8 March 2026 (UTC)

Thanks with a question



Hi! Thanks for fixing my user page. I have a question, though: how do you get your userboxes all fancy and tucked away like that? I primarily concentrate on correcting grammatical errors, as formatting is not my forte. I don't know why my userboxes are so spread out and weird looking. I appreciate any help. Thank you! Possiblegermany (talk) 02:08, 10 March 2026 (UTC)

:I used the {{tl|Userboxtop}} (and associated {{tl|Userboxbottom}}) templates to put it in a single column, and did the collapsible groups with wikitables. I could have used {{tl|Userboxgroup}} for that, but I just didn't for some reason. Anytime you see formatting that you like, feel free to click edit to view the source code to see how things were done. If you'd like help with this, I'm happy to help. Zinnober9 (talk) 02:40, 10 March 2026 (UTC)

Nothing



Dude, Do you really know that your edit on my draft literally wasted my 1 hour worth of hard-work. Please, next time, if you wanna edit. please wait till the draft is in its form of an article. TheGreatEditor024 (talk) 16:17, 31 March 2026 (UTC)

:Thankfully, I copy pasted it in Microsoft Word. So, I can retrieve what I lost. TheGreatEditor024 (talk) 16:19, 31 March 2026 (UTC)
::But i didn't copy paste references. so, I have read all of them again. Thank you so much. TheGreatEditor024 (talk) 16:20, 31 March 2026 (UTC)
:I don't see how I wasted your time. If there was an edit conflict, your changes were saved on the edit conflict page returned after submitting; your version at the bottom and current version at the top. You had every chance of keeping your changes and adding them to the current version when such occurs. Drafts are open to editing by anyone. Zinnober9 (talk) 16:25, 31 March 2026 (UTC)
::there was an edit conflict, So I tried what I normally do. But this time, It just showed the former page before the edit. TheGreatEditor024 (talk) 16:29, 31 March 2026 (UTC)

Fake Speedy Deletion Cause



Good Morning, Afternoon, Sunset, or Night for all the administrators, and moderators! I am the rightful owner, and my page was removed So, my page got taken down or "deleted" for some reason, even though it was just about a music artist's life. If you have the reason why it was taken down, please tell me. Thank you! &#126;2026-21418-24 ↗ (talk) 21:16, 7 April 2026 (UTC)

:I am not an admin or moderator, but I did nominate your second draft for deletion due to recreation for <u>valid</u> reasons, reasons stated and shared with you on your talk page. Your (first) draft is still present at Draft:Midzy ↗, the appropriate namespace for building an article.
:Shortly after the first draft was correctly moved (due to being in the wrong namespace), you promptly recreated the draft again in the wrong place. Since the first draft was still present in draft space and only one draft may be present, I marked the recreation for speedy deletion. I filed it as a WP:G6 ↗, noncontroversial housekeeping due to the misplaced recreation, and stated why I thought it was G6 through custom rational. Another editor swapped it to the simpler, but also valid reason, WP:G8 ↗ (Pages dependent on a non-existent or deleted page), with which it was deleted. No fake reasons were stated or used, and if admins don't agree with the stated custom rational, they reject the speedy (but may delete it for a more appropriate rational).
:Please create and edit drafts in draft space rather than creating things in the inappropriate article talk space. When the draft is ready for review and reliably sourced (see WP:RS ↗), add <code><nowiki>{{subst:submit}}</nowiki></code> to the top of the draft and a reviewer will look it over, give comments for anything you need to fix, and/or move it to article space as a new article if it passes creation criteria. WP:YFA ↗ and WP:REFBEGIN ↗ will help you greatly in the draft creation process. And you may ask any draft creation questions you may have at WP:TEAHOUSE ↗. Best wishes. Zinnober9 (talk) 22:13, 7 April 2026 (UTC)

Your report on the Admin noticeboard (Vandalism)



{{ping|Zinnober9}} You recently reported user '''Tidujui''' on the :Wikipedia:Administrator intervention against vandalism ↗. Thanks you for bringing the issue to admin attention. I've issued a temporary partial block for 1 week.

In the future, the type of editing issue you reported better falls under :WP:Edit warring ↗ and should be reported at :WP:ANEW ↗ (The Admin Noticeboard for 3RR and edit warring). Thanks. &mdash; ERcheck (talk) 20:01, 19 April 2026 (UTC)

Here is a flower!



left|140x140px ↗
<h2 style="font-size: 17px; font-weight: bold; font-family: 'Montserrat'; border-width: 3px; border-style: solid; border-color: #FFED29; background-color: #FF0000; padding: 5px; margin: 10px 0; color: white;">Thank you for fixing my User Page!</h2> Mcrst.sean (talk) 12:43, 23 April 2026 (UTC)

:And thank you for the kind note, best wishes. Zinnober9 (talk) 22:52, 27 April 2026 (UTC)

May 2026



25px|alt=Information icon ↗ Please do not delete or alter ↗ legitimate talk page comments from other editors, as you did at :User talk:Danners430 ↗. Such edits are disruptive and may appear to other editors to be vandalism ↗. If you would like to experiment, please use your sandbox. ''I understand making the edit once - however making it twice in a row, after you’ve already been reverted - stay off my talk page.''<!-- Template:uw-tpv2 --> <span class="nowrap"><span style="color: RebeccaPurple">Danners430</span> <sub>tweaks made ↗</sub></span> 16:48, 4 May 2026 (UTC)

:{{ping|Danners430}} No, my corrective edit was not refactoring, and the correction of known syntax errors is explicitly permitted by Wikipedia specifically per the very page you link, at the section: WP:TPFIXFORMAT ↗. And within that permission, WP:LINTER ↗ gives the clear boundaries for what can and cannot be fixed/changed. Correcting the faulty syntax of how something displays, such that it visiually appears identical, or with the same intent as the original author's is NOT refactoring. While yes, my change no longer displayed the navbox, your comment has the clear intention of a ''"sigh"'' (exhale), not of a navbox for a band's albums, so replacing the assumed erronious {{tl|sigh}} with the logical "Sigh." that I replaced it with is in keeping with the intent as was situationally read, and removes the error of indenting a divbased navbox producing the "Multiline HTML table in list" error and DOES NOT MEET the criteria of refactoring.
:The template {{tl|sigh}} creates a navbox for the albums for the Japanese experimental metal band Sigh (band) ↗ and has no clear connection to the discussion as I read. If you *are* intending the usage of the navbox however, that is fine, BUT IT MAY NOT be indented. HTML does not allow div objects to be indented, and this is a divbased navbox.
:If however the band's navbox is wrong and you wish to have a sigh like comment icon, the next nearest template to a sigh (exhale) I could offer you is possibly
:{{tl|facepalm}}: {{facepalm}},
:or <nowiki>{{facepalm|sigh}}</nowiki>: {{facepalm|Sigh}}
:but there is no (know to me) equivalent to a "sigh" talkpage comment template.
:Please WP:AGF ↗, I have no interest in bothering you or your userpage, just in the correction and prevention of known and tracked errors, and the indenting of navboxes is an known and tracked syntax error.
:I will respect your wish for me to not edit on your talk page further on this matter. But I hope that this explanation brings you light on this matter and that this error will be addressed.
:Best wishes,
:Zinnober9 (talk) 17:44, 4 May 2026 (UTC)
::I did assume good faith the first time you did it and simply reverted your change - but this is the second time you've done it, after it was clear that I didn't want it changed.
::Edit - just to clarify, I'm only writing this short reply because I'm about to hit the road and can't fully digest your full message. All I'm asking is you stop making the change to my talk page for now. <span class="nowrap"><span style="color: RebeccaPurple">Danners430</span> <sub>tweaks made ↗</sub></span> 18:26, 4 May 2026 (UTC)
:::Ok, now I’ve had time to sit down and process this…
:::On your AGF point firstly - I have no issue with AGF when an editor makes a syntax fix on my talk page once. However, when you got reverted, common sense would dictate that instead of you making the same edit again, perhaps you should leave a note or discuss first? Instead you made the same edit without any further explanation, despite it being pretty clear that I didn’t want the edit made (as I’d reverted it previously).
:::if the only issue here is the template being indented… then here’s a thought - remove the indentation! Unless I’m missing something, there is zero harm in editors using these templates humorously on their own user talk pages… so kindly leave them alone. <span class="nowrap"><span style="color: RebeccaPurple">Danners430</span> <sub>tweaks made ↗</sub></span> 07:07, 5 May 2026 (UTC)
::::If you want to keep the navbox, by all means. There was every indication from the limited context that you thought it was a commentary template like "{{tick}}" or "{{comment}}" since it was a reaction response to the OP's comment about watching a vandalized article. So you wanting the band's navbox is quite unexpected but perfectly fine. Indent removed, navbox kept. Have a nice weekend. Zinnober9 (talk) 13:08, 7 May 2026 (UTC)
:::::The OP and I are almost like a tag-team (although we make every effort not to be, since tag teaming isn't appropriate!) - we both work in the same areas and both fight the same sort of issues, so there's a constant back and forth between us regarding problem articles to keep an eye on <span class="nowrap"><span style="color: RebeccaPurple">Danners430</span> <sub>tweaks made ↗</sub></span> 13:44, 7 May 2026 (UTC)

Explanation regarding user page edits



Hi,

I saw that you edited my user page. (First note that while I appreciate efforts to make it better, courtesy would prescribe that you ask permission first. That said, I'm fine with advice on how to make my user page visually better.)
I am a bit confused as to what the edits are supposed to do and what they are fixing, could you explain that? Is it purely esthetic, to respect some formatting convention, or for some other reason?

Thanks, EULunarWork (talk) 14:34, 12 May 2026 (UTC)

:Wikipedia keeps track of various syntax errors that break display or functionality of things, and the empty header ↗ error affects the display and the functionality of table of contents (example on section #12 and #13 ↗ where 12 is empty in the TOC, and 13 just says Languages). As long as there's some plaintext to display in the header, there isn't a reported issue. And this error is reported regardless of if there is a TOC present on the page.
:While I understand your position of ask me first, when I've tried that approach, I'm often met with no response or when there is a response, skepticism of what I'm asking for and I'm asked to show a diff of the edit, so it's just been easier to do the edit first and ask for forgiveness after on the occasion someone isn't happy and work with them on finding a middle ground. And WP:OWN#User_pages ↗ gives editors a general permission to correct syntax issues on other's userspace without prior permission, and WP:Linter ↗ states the boundaries on what can and can't be changed in userspace. Zinnober9 (talk) 01:37, 14 May 2026 (UTC)

::You edited my user page yesterday, and I echo the comments of User EULunarWork. I don't see how removing a minor syntax error helped the encyclopedia. That edit seems merely fussy to me. Couldn't there be more constructive edits you could spend your time on? Please take note that not every user appreciates an edit to our user page without permission or, at least, comment. See WP:USERTALKSTOP ↗. YoPienso (talk) 10:24, 5 June 2026 (UTC)
:::When some syntax errors get compounded, pages have become illegible, unloadable, or just a downright mess. While most of the more problematic issues have been cleared from enwiki, some of the smaller errors still rear their heads with functionality or display. Your page didn't have many issues on it, but I was specifically going after missing/stripped sub tags this week and that caught my eye on your page, so I cleared all other issues in one go to bother you less.
:::I've found that people are fussier when I've asked beforehand for my corrective edits than when I've gone ahead and edited and they see their page looks the same. Less work for me, less bother to others. I'm not required to ask beforehand, but I am required to stop (on your page) when asked, as you have here. Sorry for any bother, I thought you had a nicer clearer page structure than some others I've seen and I appreciated that. I hope you have a nice weekend, Zinnober9 (talk) 22:41, 5 June 2026 (UTC)
::::Thank you for your very courteous reply.
::::I'm not a coder. How can adding and deleting characters not affect the display? (I.e., changing the characters doesn't change the page.) Was my page "illegible, unloadable, or just a downright mess" or verging on it?
::::I'm OK with you fixing syntax errors, I guess, on my page or wherever. Maybe you'd be willing to create a template to inform users that you've done some clean-up? I'm more used to seeing bots do that kind of work, and some of them leave messages. Can't remember if I've seen that on my user page or just in articles.
::::Best wishes, YoPienso (talk) 14:34, 6 June 2026 (UTC)

Thank you for fixing my userbox table



It's been eluding me how to fix it, so thank you! Fwltur Gwydr (talk) 16:00, 15 May 2026 (UTC)

:Sure, no problem! Zinnober9 (talk) 16:06, 15 May 2026 (UTC)

Thank you



It is very much a appreciated for you help on editing my user page. Thank you very much @Zinnober9

- Welches2012 (talk) 18:11, 16 May 2026 (UTC)

:No problem, glad to help! Zinnober9 (talk) 21:54, 16 May 2026 (UTC)

Unclear guidance for Template:Documentation ↗



Hi, Zinnober! Thank you for fixing {{tl|GEOnet name search}} and {{tl|GEOnet ufi search}}.

Your edit comment said that {{tl|Documentation}} "MUST" be on a new line, per Wikipedia:Template documentation#How to create a documentation subpage ↗. However, careful perusal of that section does not indicate that this MUST be true: it shows an example where it is true, but doesn't say it must happen or it will generate lint errors.

You may wish to get consensus to fix Wikipedia:Template documentation#How to create a documentation subpage ↗, perhaps refraining from saying "MUST" in your edit comments until the guidance reflects that. — hike395 (talk) 04:20, 31 May 2026 (UTC)

:"Must" is maybe a little strong, but each time I've seen it on the same line, it's reported this issue. There was a batch of them earlier this month where I had this (secondary) discussion ↗ where Jonesey95 solved them. {{ping|Jonesey95}} Do you know if it is possible for documentation of a template to be on the same line as a template and be clean, or will it be a error each time and the How-to needs a minor update to mention this scenario? Zinnober9 (talk) 14:29, 31 May 2026 (UTC)
::There are places where having the documentation start on the same line as the last bit of the template code does not cause any errors, but the standard construction used at Wikipedia:Template documentation ↗ always works, it is easy for human editors to parse, and I can't think of a reason for editors to object to it. Consistency with a reason behind it is almost always a good thing. – Jonesey95 (talk) 03:16, 1 June 2026 (UTC)
:::Thank you for confirming and for updating the documentation. Zinnober9 (talk) 16:24, 1 June 2026 (UTC)

A barnstar for you!



{| style="background-color: var(--background-color-success-subtle, #fdffe7); border: 1px solid var(--border-color-success, #fceb92); color: var(--color-base, #202122);"
|rowspan="2" style="vertical-align: middle; padding: 5px;" | 100px ↗
|style="font-size: x-large; padding: 3px 3px 0 3px; height: 1.5em;" | '''The Minor barnstar'''
|-
|style="vertical-align: middle; padding: 3px;" | Thanks for cleaning up after me on Template:Geography topics ↗. <span style="font-family:Blackadder ITC; color:DimGray">GeogSage</span> <sup> (<span style="font-family:Blackadder ITC; color:DimGray">⚔Chat?⚔</span>) </sup> 04:37, 2 June 2026 (UTC)
|}

Speedy deletion declined: :Draft:James ipad1 ↗


Hello Zinnober9. I am just letting you know that I declined the speedy deletion of :Draft:James ipad1 ↗, a page you tagged for speedy deletion, because of the following concern: not a test page; just a bad draft. Thank you. Whpq (talk) 03:53, 6 June 2026 (UTC)

:Thank you for the message, sent you an email. Zinnober9 (talk) 04:59, 6 June 2026 (UTC)
::It appears you do not have email enabled. I am unable to send you a response. -- Whpq (talk) 11:30, 6 June 2026 (UTC)
:::Ah, my error. Setting now on. Zinnober9 (talk) 12:39, 6 June 2026 (UTC)
:::Initial issue has been resolved per your suggestion, thank you for your response. Zinnober9 (talk) 14:56, 7 June 2026 (UTC)

Would appreciate more clarity on a user page edit



You edited ↗ my user page with a summary about fixing an error of some kind, and I'm sure there is a good reason as you seem to do a lot of clean-up of syntax errors and such things, and I'm assuming you were led to my user page because it had an error of the kind you were going around cleaning up (which is much appreciated, by the way).

The thing is I can't immediately see what the error actually was, and the template documentation isn't particularly useful. To me the page looked the way I wanted it to before and now looks like what I was trying to avoid (don't worry about that I will just figure out some manual solution not involving the template). So, I would like to ask how you found my user page and if you could point me in the direction of a page where I can learn more about the thing you fixed? Many thanks. ⹃<span style="color:#711">Maltazarian</span>&nbsp;<sup>ᚾ<span style="color:#006">parley</span><math>\lor</math><span style="color:#226">investigate</span> ↗ᛅ</sup> 13:07, 11 June 2026 (UTC)
:Div based templates generally can't be indented (or bulleted) as they either throw a stripped or a misnested div error (or in bulleting situations throw a Multiline HTML table in list error), and since a number of templates can do this, I can't really point to a specific page for you. It's mainly a "know it when you see it" situation, but boxes and column related templates are the fussy ones. I found your page from this table User:WOSlinker/Lint_errors_per_tag, a breakdown of Special:LintErrors ↗.
:Since you had used the Div col ↗ template, it had appeared you wanted the multiple columns, and most of the time when I encounter unindentable templates on talk pages, its by way of the reply feature indenting everything replied, so that's what I assumed had happened here.

:Since you just want the single column, probably the best way would be to just have the indents for each flag and no div templates like so:

::::#{{flagicon|Argentina}} Chaco side-necked turtle ↗
::::#{{flagicon|Argentina}} ''Leptodactylus laticeps ↗''
::::#{{flagicon|Belize}} ''Leptodactylus melanonotus ↗''
::::#{{flagicon|Bolivia}} ''Leptodactylus knudseni ↗''
:::::...

:Alternately, Template:Col-begin ↗ (with a single Template:Col-break and a Template:Col-end) could also work. While their usage generally implies a desire of multiple columns, I do see single column usage not infrequently. These col templates also can't be indented, but contents can be like so:

{{Col-begin}}
{{Col-break}}
::::#{{flagicon|Argentina}} Chaco side-necked turtle ↗
::::#{{flagicon|Argentina}} ''Leptodactylus laticeps ↗''
::::#{{flagicon|Belize}} ''Leptodactylus melanonotus ↗''
::::#{{flagicon|Bolivia}} ''Leptodactylus knudseni ↗''
:::::...
{{Col-end}}

:Thanks for the message, let me know if I can help further. Hope you have a nice weekend, Zinnober9 (talk) 15:42, 12 June 2026 (UTC)
::Thank you for the reply! That helps a lot; I figured out out a solution, so now the page looks like I want it too without causing an error, and I've learned something that is good to know. Keep up the good work. ⹃<span style="color:#711">Maltazarian</span>&nbsp;<sup>ᚾ<span style="color:#006">parley</span><math>\lor</math><span style="color:#226">investigate</span> ↗ᛅ</sup> 17:01, 12 June 2026 (UTC)

Talk-page formatting move



Greetings. I do not mind much changes of the sort you did ↗ but, since you have not been part of the discussion, it seems a bit much, especially for a talk page from an uninvolved party, so I reverted it. I'd appreciate it if, no matter what the intention ↗, that happens no more. Take care. -The Gnome (talk) 06:09, 26 June 2026 (UTC)
:I was addressing the last remaining stripped q tag errors yesterday, which were either from either actual q tags, or from Template:talk quote ↗ being used in a block setting and not inline. And while your page has a stripped <nowiki></q></nowiki>, I mistook the template:quote ↗ as an intended tq in context since I almost always see tq and not quote on talk pages. I overstepped on changing quote to tq, I'm sorry for that. But would you be agreeable for either the <nowiki></q></nowiki> tag be removed, or a <nowiki><q></nowiki> tag be added ahead of that (but still within the quote template, otherwise it will be misnested) to clear the tracked error? Thanks, and sorry for overstepping on swapping the templates. Zinnober9 (talk) 15:29, 26 June 2026 (UTC)

brownie :D



{| style="background-color: var(--background-color-success-subtle, #fdffe7); border: 1px solid var(--border-color-success, #fceb92); color: var(--color-base, #202122);"
|style="vertical-align: middle; padding: 5px;" | 120px ↗
|style="vertical-align: middle; padding: 3px;" | yum Riverskysun (talk) 06:11, 11 July 2026 (UTC)
|}