You have been blocked indefinitely for repeated personal attacks and formaking only a poor non-apology apology at ANI. As perFirefangledfeathers's commenthere, the indefinite block is not intended to be infinite, but any future unretirement/unblock request needs to be accompanied by a constructive plan for future disputes. (Not necessarily by an apology, as forced apologies are worse than useless.) You can request unblock from an uninvolved administrator by placing {{unblock|your reason here}} on this page. Please don't edit while intoxicated.Bishonen |tålk13:30, 30 May 2025 (UTC).[reply]
@Zenomonoz: - my bad, man. I apologize for being such a douche that day. I was intoxicated and I can be an angry drunk. I had a drinking problem a few months ago and I’ve since recovered from it, but that doesn’t absolve me of responsibility for my actions while under the influence. In any event, you didn’t deserve that. I hope you can forgive my behavior that day.
@Firefangledfeathers: - To my knowledge, I have never retired before now. If you can substantiate otherwise, I’d like to know, because I can’t remember and you used that as a justification in your statement.
@Bishonen: - that seems perfectly reasonable to me.
I’ve had ample time to reflect on this. I believe simply abstaining from alcohol would solve the problem by itself; however, going forward I will make a concerted effort to maintain civility when engaging other users on talk pages and escalate to projects/ANI for feedback from third-party users when necessary instead of vent my anger on Wikipedia toward the counterparty.
If something more concrete and step-by-step is desired, here's a plan I find acceptable.
lengthy content
1.No editing under the influence. If I drink, I will not edit Wikipedia for at least 24 hours afterward.
2.Cooling-off rule. Before posting to noticeboards or heated talk threads, I will draft in my sandbox, wait 2 hours, re-read for tone, and remove any personal language.
3. Civility first. I will adhere toWP:CIVIL andWP:NPA. If I feel frustrated, I will stop and come back later or ask an uninvolved editor for a reality check.
4. Dispute-resolution path. Content disputes: BRD → talk page →WP:3O/WikiProject talk →WP:DRN. I will avoid jumping toWP:ANI except for clear conduct issues.
5. Voluntary restrictions (90 days).
No initiating or participating in ANI/AN threads unless I’m the subject or there’s an immediate policy-level concern.
1RR on pages where I’m involved in dispute; escalate to talk rather than revert.
6. Third-party feedback. For contentious posts, I will seek input at a relevant WikiProject or from an uninvolved editor before hitting “publish.”
7. Focus on constructive work. I’ll concentrate on article improvement, sourcing, and maintenance (particularly in pharmacology/biomed) and keep talk-page posts purpose-focused.
8. If I slip. If I breach civility again, I accept that a re-block (or formal editing restrictions) may be imposed without further warning.
Most range blocks, especially on schools, allow accounts to operate. You'll need to tell your IP so we can look into this(you may make a private unblock request viaWP:UTRS if you don't want to post your IP publicly).331dot (talk)08:08, 27 October 2025 (UTC)[reply]
Seppi, I just found out about this, and I'm wondering what happened. Mostly from a long time ago, I remember us editing pharmacology stuff quite productively, but the recent stuff just doesn't match with the editor I worked with in the past. I did see that you made some edits while intoxicated. If, after taking some time to get a hold of things, you decide to come back and make things right, I hope you can get back to the productive content work of the past. --Tryptofish (talk)20:16, 31 May 2025 (UTC)[reply]
Amphetamine is very impressive and helpful! Thank you a bunch for your dedication to it!
You said,Bet no one even cares what they just lost. athere. I care! And I believe a lot of Wikipedians care, too! Wishing you all the best in your future endeavours!!Genetic endowment (talk)06:57, 20 July 2025 (UTC)[reply]
It is not appropriate for ombox to be used in mainspace. Please correct your not-template template such that it emits content appropriately for mainspace. Perhaps no box would be most reasonable.Izno (talk)16:26, 25 October 2025 (UTC)[reply]
To be honest, it serves the same purpose as an infobox and a navigation template. If you want me to manually convery the HTML/CSS/template elements to mirror an infobox with page navigation, i’m happy to do that.
Also, fwiw, plenty of articles have navigation box templates that serve various purposes. Articles in a topical series, articles within a place/date range, etc.. This is just a sequenced list, and i’m going to have to break it into 9 sequenced list pages to reduce the load time from 3 minutes for each list to something not so stupid; it’s due to how browsers attempt to render and repeatedly recalculate the css elements as they receive more and more but not all of the table data.
I would in fact not preferIf you want me to manually convery the HTML/CSS/template elements to mirror an infobox with page navigation, i’m happy to do that. - emitting HTML directly is a pain for me for other reasons and is not guaranteed to be forward compatible. Using a{{sidebar}} as in my version would be fairly reasonable (I might generally prefer{{navbox}} these days). My current and only priority objection is to use of{{ombox}}.
I'd also appreciate if you moved this 'template' into actual template space if it is going to be used in mainspace content.Izno (talk)23:06, 26 October 2025 (UTC)[reply]
Eh, main reason it transcludes from there is that all the talk pages redirect to its talk page.
I realize it’s not common, but there’s plenty of instances where non-template pages transclude to the mainspace. I would also object if it werent for the fact that its use is clearly limited to the protein-coding gene lists page scope. IE, there’s no possibility that it’d be used elsewhere.
I’ll consider alternatives to ombox that get the job done. What specifically is your concern other than what the intended usage of that template is? Knowing that would help me identify a better solution.Seppi333 (Insert 2¢)01:00, 27 October 2025 (UTC)[reply]
Eh, main reason it transcludes from there is that all the talk pages redirect to its talk page. This is not a persuasive reason to keep the template in Wikipedia namespace.
plenty of instances where non-template pages transclude to the mainspace Those cause pain for users doing basic quality control who assume main space content lives in one of main, template, or module namespaces.
Intended use of the template is the primary issue. I think stylistically it's also quite wrong for where the content is being placed in the pages of interest, which is why I originally suggested above ditching the boxes entirely (though I'm not entirely certain ditching the box really goes with any page besides the primary list "disamib" page unless the content gets moved to a see also section). I'd be happy to compare features of another proposal besides the three I've suggested (no box, sidebar, navbox).Izno (talk)05:32, 27 October 2025 (UTC)[reply]
I wasn't actually trying to persuade you based on that use. I simply did it that way at the time for my own convenience, and for the fact that it simplifies project/navbox/talk navigation for others. I'm not actually aware of any policy or guideline requiring that transclusions into the mainspace come exclusively from the template space. So, in light of that, the strict partitioning you're describing as an ideal doesn't sound very persuasive to me when it creates more work for me and complexity for others over a simple solution like this. Moreover, despite ample objections – spanning a variety of issues – that I've received about these lists over the last 5+ years, you're the only person who has taken issue with the list navbox and its transclusion.
Sure, I could create an entirely separate page and create template documentation and a template talk page for a navbox that would need to refer back to the now more convoluted set of mainspace-project space-project talk space-template space pages.
Seems like a lot of unnecessary work that would require me to create a new page on Wikipedia and update the target in my python file in order to do exactly the same thing in Python (i.e., update the navbox at the new location) and on Wikipedia (transclude the same navbox from an entirely different pagename) as before.
The only things you've implied are issues specifically for you are that a project space -> mainspace transclusion isn't acceptable to you despite the atypical non-template-related purpose the project-space page serves in relation to a bot script literally deleting all other WP editors' incremental edits and completely rewriting each list page whenever an update runs. You've also pointed out you don't like the use of an ombox meta-template despite the fact that the intended ones for 99.9999% of article space use cases (ambox, tmbox, imbox, cmbox) don't even remotely come close to addressing this one (i.e., how many articles on WP are written exclusively by a bot?). If you can tell me what parameters and inputs to use in any of those message templates to generate what I wrote in the ombox, I will swap them immediately.Seppi333 (Insert 2¢)09:12, 27 October 2025 (UTC)[reply]
Hello! Voting in the2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. Alleligible users are allowed to vote. Users with alternate accounts may only vote once.
TheArbitration Committee is the panel of editors responsible for conducting theWikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to imposesite bans,topic bans, editing restrictions, and other measures needed to maintain our editing environment. Thearbitration policy describes the Committee's roles and responsibilities in greater detail.