This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the
current talk page.
Hi Bradv. ArbClerkBot doesn't seem to be up right now. Would it be possible to look into that? If you lack capacity to look into it, that's also totally understandable. It may also be helpful to add a technically-minded member of the clerk team to the maintainers of the bot.
We could also likely write a brief bash script to check the health of the task and if error shows, then kill it and let it restart. --
Amanda (she/her) 22:21, 1 August 2023 (UTC)
@
AmandaNP: hm, it doesn't seem to have worked with the most recent post either. Best, KevinL (aka
L235·t·c) 23:02, 2 August 2023 (UTC)
Hey Kevin, I'm currently on vacation but I'll look into this next week. –
bradv 17:22, 3 August 2023 (UTC)
Take your time — this is as non-urgent as it gets :) KevinL (aka
L235·t·c) 17:56, 3 August 2023 (UTC)
I just looked into it. Something seems to have pulled out the underlying library we are using out from underneath us :/ Going to read the documentation again to see how to readd this, though I swear we haven't touched this, so this was either a server lapse or something tool admins did purposefully. --
Amanda (she/her) 18:14, 6 August 2023 (UTC)
Technical reason: venvs/grid engine which we are using for this are extremely flakey on the bastion servers. I've been told that stability only exists in k8ns. So essentially we have to migrate to k8ns to prevent this from happening again, and I've never touched said software, and although
wikitech:Help:Toolforge/Jobs framework exists, i've been told it's an absolute pain in the ass to set up, but will be fine once you get it there. And DeltaQuadBot is now at risk over this same issue and explains why I've had similar issues in the past there too. So another boatload of manhours to figure this out that I'm not taking unplanned time out of my day to deal with it. I will consider it for next weekend.
Plain english reason: Bot does not have the proper food to run, bot will continue to fail until we change it's diet, and DeltaQuadBot is at risk for this also. --
Amanda (she/her) 21:12, 6 August 2023 (UTC)
@
AmandaNP, I'm not sure the version on toolforge ever worked properly. The bot was running on my own server until May 22, when it inadvertently got shut down. I've restarted the server and now it appears to be working again. I am interested in porting this though, so let's work on that together when we both have some free time. @
L235, it's running again. ;) –
bradv 13:01, 9 August 2023 (UTC)
That would explain why it looks like the errors started last year... That is reassuring. I'll reach out and offer some dates that would be best. --
Amanda (she/her) 13:03, 9 August 2023 (UTC)
Following
an RfC,
TFAs will be automatically semi-protected the day before it is on the main page and through the day after.
A discussion at
WP:VPP about revision deletion and oversight for
dead names found that [s]ysops can choose to use revdel if, in their view, it's the right tool for this situation, and they need not default to oversight. But oversight could well be right where there's a particularly high risk to the person. Use your judgment.
The SmallCat dispute case has closed. As part of the final decision, editors participating in
XfD have been reminded to be careful about forming local consensus which may or may not reflect the broader community consensus. Regular closers of
XfD forums were also encouraged to note when broader community discussion, or changes to policies and guidelines, would be helpful.
Miscellaneous
Tech tip: The "Browse history interactively" banner shown at the top of
Special:Diff can be used to easily look through a history, assemble composite diffs, or find out what archive something wound up in.
New Page Review article queue, March to September 2023
Backlog update:
At the time of this message, there are 11,300 articles and 15,600 redirects awaiting review. This is the highest backlog in a long time. Please help out by doing additional reviews!
October backlog elimination drive:
A one-month backlog drive for October will start in one week! Barnstars will be awarded based on the number of articles and redirects patrolled. Articles will earn 4x as many points compared to redirects. You can
sign up here.
PageTriage code upgrades:
Upgrades to the
PageTriage code, initiated by the
NPP open letter in 2022 and actioned by the
WMF Moderator Tools Team in 2023, are ongoing. More information can be found
here. As part of this work, the
Special:NewPagesFeed now has a new version in beta! The update leaves the NewPagesFeed appearance and function mostly identical to the old one, but updates the underlying code, making it easier to maintain and helping make sure the extension is not decommissioned due to maintenance issues in the future. You can try out the new Special:NewPagesFeed
here - it will replace the current version soon.
Notability tip:
Professors can meet
WP:PROF #1 by having their academic papers be widely cited by their peers. When reviewing professor articles, it is a good idea to find their
Google Scholar or
Scopus profile and take a look at their
h-index and number of citations. As a very rough rule of thumb, for most fields, articles on people with a h-index of
twenty or more, a first-authored paper with more than a thousand citations, or multiple papers each with more than a hundred citations are likely to be kept at AfD.
Reviewing tip:
If you would like like a second opinion on your reviews or simply want another new page reviewer by your side when patrolling, we recommend pair reviewing! This is where two reviewers use
Discord voice chat and screen sharing to communicate with each other while reviewing the same article simultaneously. This is a great way to learn and transfer knowledge.
Hi, @
Bradv: I was partially blocked for problematic COI editing and wanted to check with you first before asking to be unblocked. The reason I would like to be unblocked is so I can directly edit a project I am working on that involves the
California Historical Landmarks in Santa Clara County. There are many corrections that need to be made on this page as well as the landmark articles that, in several cases, do not point to the correct article and/or have no information about the landmark, e.g. the site of invention of the first commercially practicable integrated circuit. I admit that I did some problematic COI editing and I promise not to do it again. I enjoy doing the research and working on meaningful Wikipedia articles. Please let me know what you think?
Greg Henderson (
talk) 17:56, 27 September 2023 (UTC)
I'm not sure why you are asking me.
User talk:Drmies#I am partially blocked already exists, and if you can't accept that advice you can try post an {{
unblock}} request on your talk page or appeal to
WP:AN. I would suggest, however, that your best path to restoration is to be as forthcoming as possible about your previous COI editing, and to help others with the cleanup efforts. More apologies alone won't cut it – we need to see that you understand what it takes to write a
neutral encyclopedia. –
bradv 19:49, 30 September 2023 (UTC)
An RfC is open regarding amending the
paid-contribution disclosure policy to add the following text: Any administrator soliciting clients for paid Wikipedia-related consulting or advising services not covered by other paid-contribution rules must disclose all clients on their userpage.
Technical news
Administrators can now choose to add the user's user page to their watchlist when changing the usergroups for a user. This works both via
Special:UserRights and via the API. (
T272294)
WikiProject Articles for creation is holding a month long
Backlog Drive!
The goal of this drive is to reduce the backlog of unreviewed drafts to less than 2 months outstanding reviews from the current 4+ months. Bonus points will be given for reviewing drafts that have been waiting more than 30 days. The drive is running from 1 November 2023 through 30 November 2023.
Barnstars will be given out as awards at the end of the drive.
There is a backlog of over 2300 pages, so start reviewing drafts. We're looking forward to your help!
MediaWiki message delivery (
talk) 13:23, 31 October 2023 (UTC)
I see they are now edit warring the closure from different IP addresses. --
CNMall41 (
talk) 21:57, 5 November 2023 (UTC)
I see this has now been taken care of by another admin. I'm not sure which LTA this is, but if you see them pop up again I suggest reporting them to
AIV. –
bradv 18:29, 6 November 2023 (UTC)
Following
a motion, the contentious topic designation of Prem Rawat has been struck. Actions previously taken using this contentious topic designation are still in force.
Following
several motions, multiple topic areas are no longer designated as a contentious topic. These contentious topic designations were from the Editor conduct in e-cigs articles, Liancourt Rocks, Longevity, Medicine, September 11 conspiracy theories, and Shakespeare authorship question cases.
Following
a motion, remedies 3.1 (All related articles under 1RR whenever the dispute over naming is concerned), 6 (Stalemate resolution) and 30 (Administrative supervision) of the Macedonia 2 case have been rescinded.
Following
a motion, remedy 6 (One-revert rule) of the The Troubles case has been amended.
An arbitration case named Industrial agriculture has been opened. Evidence submissions in this case close 8 November.
Miscellaneous
The
Articles for Creation backlog drive is happening in November 2023, with 700+ drafts pending reviews for in the last 4 months or so. In addition to the AfC participants, all administrators and New Page Patrollers can conduct reviews using the helper script, Yet Another AFC Helper Script, which can be enabled in
the Gadgets settings.
Sign up here to participate!
Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The
Arbitration Committee is the panel of editors responsible for conducting the
Wikipedia 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 impose
site bans,
topic bans, editing restrictions, and other measures needed to maintain our editing environment. The
arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2023 election, please review
the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{
NoACEMM}} to your user talk page.
MediaWiki message delivery (
talk) 00:32, 28 November 2023 (UTC)
Public clarification
Yeah, so it turns out you weren't even in that bit of discussion, sorry again—I was actually replying to
User:SarekofVulcan, who mentioned NewYorkBrad in his comment, and of course I misread it as being yours. Slightly convoluted, but a fooolish mix up on my part.
——Serial 12:27, 28 November 2023 (UTC)
That makes more sense, but I think you're still missing a word. It doesn't really matter though – there are plenty of comments worth ignoring in that thread; no sense adding to the pile. –
bradv 15:24, 28 November 2023 (UTC)
Conflict with griefer Skitash on Tunisia related pages
Dear Wikipedia Administrators,
I hope this message finds you well. I am writing to appeal the block you placed on my Wikipedia account. I believe the block was issued due to my attempts to revert edits made by a user engaging in ethno-centric bias, specifically in relation to the representation of Tunisian ethnicity, language, and Berber ancestry.
I understand the importance of maintaining a neutral point of view on Wikipedia and strive to adhere to its policies. In this case, my intention was to ensure that the information presented accurately reflects the diversity of perspectives and historical facts regarding Tunisian heritage.
The user in question has been systematically removing sourced content that acknowledges the non-Arabic aspects of Tunisian ethnicity and language, as well as information about Berber ancestry or other non-arab ancestry or language elements. This raises concerns about the impartiality and accuracy of the content being presented on Wikipedia.
I believe my efforts to revert these edits were in line with Wikipedia's commitment to providing unbiased and verifiable information. My actions were not intended to disrupt the platform but rather to uphold the principles of neutrality and inclusivity that are essential to Wikipedia's credibility.
I kindly request a review of the block on my account, taking into consideration the context of the edits in question and my commitment to upholding Wikipedia's content policies. I am more than willing to engage in constructive discussions, provide additional sources, and work collaboratively to ensure the accuracy and neutrality of the content related to Tunisian ethnicity and language.
Thank you for your time and consideration. I look forward to a resolution that promotes the integrity and objectivity of Wikipedia.
Sincerely,
asmodim
Asmodim (
talk) 22:23, 30 November 2023 (UTC)
The block has already expired, so there's no point in appealing it. I'm glad to see you are discussing your disagreements now instead of edit warring – that's a considerable improvement. The next step would be to make a coherent argument on the talk page, supported by
reliable sources, on exactly what needs to be changed. Bonus points if you can do so while
commenting on content rather than on the contributor. –
bradv 01:58, 1 December 2023 (UTC)
Editor experience invitation
Hi Bradv :) I'm looking for people to interview
here. Feel free to pass if you're not interested.
Clovermoss🍀(talk) 02:18, 1 December 2023 (UTC)
@
Immanuelle, you know you can move these yourself now, right? We trust you. –
bradv 06:57, 2 December 2023 (UTC)
Nevermind, I see there's still a restriction in effect. I'll look these over in the next day or so. –
bradv 06:59, 2 December 2023 (UTC)
@
Immanuelle, I've accepted all of these. There is some concern that
Amazing Cultivation Simulator may not meet
WP:GNG, but that can be dealt with at
AFD. Likewise, there was some objection to
Makimuku Ishizuka Kofun being a stand-alone article rather than merged into
Makimuku ruins, but that can be dealt with in mainspace if there is consensus for merging. (I also note that your
restriction prohibits you from merging content from declined drafts, so arguably you couldn't even perform the merge as suggested by AfC reviewers anyway.) –
bradv 17:16, 2 December 2023 (UTC)
@
Bradv yeah currently all declined articles with suggested merges have been completed. I feel that restriction in particular is a rather unconstructive one that I plan on appealing soon.
I also want to attempt to prove I can do translations well by getting an exemption for
Draft:Horaisan Kofun so I can prove myself
I am a bit unsure what to do for this, and whether to wait longer. Do you have advice in this area?
Immanuelle ❤️💚💙
(talk to the cutest Wikipedian) 19:37, 2 December 2023 (UTC)
Congratulations!
Most Braddiest Brad
For being the most BarfVD ever.
GRINCHIDICAE🎄 20:26, 2 December 2023 (UTC)
You've outdone yourself. –
bradv 21:21, 2 December 2023 (UTC)
Just a thought
I just want to say that it is because of
admin power moves such as these, that people like me who have spent an entire DECADE working towards improving Wikipedia want to quit for good. You speak about "thousands of people [...] working tirelessly to help improve the encyclopedia and achieve its vision" in your user page. What has been the point of my working tirelessly for a decade to achieve this, so that I can be demeaned and blocked without consequence for reverting spam?
Krimuk2.0 (
talk) 06:38, 3 December 2023 (UTC)
What about your treatment of the other editors on
that page? I count at least 7 reverts from you on December 1, without even a single post on the talk page. This is textbook
edit warring, and as someone who's been around for over a decade, you should know better. –
bradv 15:23, 3 December 2023 (UTC)
You mean treatment of reverting spam & poorly sourced info from other editors, that was
reverted by someone else soon after?
Krimuk2.0 (
talk) 06:35, 4 December 2023 (UTC)
It doesn't matter whether you were correct or not, you were still edit warring. Regardless, the talk page of the article is still available to you if you wish to engage in some collaborative article building. –
bradv 14:50, 4 December 2023 (UTC)
thank you
Hi bradv, the ANI thread closed before I could respond to your final comment to me
[1], so I am following up here. Overall, I regret not being more proactive about seeking more editor participation with the content side of the dispute - I filed a request at RFPP and then a report at ANEW, but I could have also gone to BLPN and/or pursued other content-related dispute resolution options, and I could have used the
disputed inline template.
I appreciate your responses to my replies to your requests for an explanation at ANI about why I thought a BLP exemption applied, because this interaction emphasizes how controversial BLP exemptions for 3RR can be. One aspect of our interaction that I found particularly helpful is the clarification of how a credible claim of a BLP exemption may seem apparent, but if it requires an essay of explanation, then it can be considered 'controversial.'
And then I reviewed the July 2022 "
Making WP:3RRNO point 7 more specific" discussion in the WT:Edit warring Archive, and I think it not only reinforces all of this but also adds depth related to the implementation and purpose of the policy. So I hope this follow up helps provide some reassurance about my improved understanding of the 3RRBLP threshold. Thank you,
Beccaynr (
talk) 04:34, 4 December 2023 (UTC)
I appreciate your message, @
Beccaynr. I hope it didn't feel too much like I was interrogating you – I was really trying to understand your objections to the change. But yes, the
3RRBLP exemption is somewhat complicated, as it needs to strike a delicate balance between preventing disruptive editing while protecting the rights of the subjects of BLPs. I read that discussion you linked and I don't know where I stand: on the one hand adding a word like "obvious" or "uncontroversial" should make things more clear, but I question whether that would weaken our BLP protections. And if we make that change, what kind of other nefarious behaviour are we going to unlock? Perhaps another way of looking at this is that we don't even need that exemption – it's already covered by
WP:IAR. In other words, if you're going to break 3RR it should be obvious to any reasonable Wikipedian that it was the right thing to do, and that you're willing to risk consequences to protect the integrity of the encyclopedia. At any rate, I appreciate you patiently explaining the real-life context and implications of these edits. I don't know much about Indian politics or history, but I am trying to learn. Happy editing. –
bradv 15:13, 4 December 2023 (UTC)
Thank you, bradv, and your questions felt more like the
Socratic method to me, including because the interaction helped me better understand the meaning of 'controversial' in the 3RRBLP exemption. And while this is an imperfect analogy, I am familiar with the delicate balance of a lawyer's duties related to roles as an officer of the court and representative of a client, which in some ways reminds me of the delicate balance between protecting the encyclopedia from disruptive editing and protecting the rights of a BLP subject. I also feel as if I have some experience from work on contentious BLPs that made some concerns expressed in the WT:Edit warring archive discussion ring true about unintended consequences from policy language changes.At this point, I am tending to think of 3RRBLP somewhat like seeking ex parte relief - where other participants have no opportunity to be heard, and the best case is clearly obvious and urgent. I also found the WT:Edit warring archive discussion useful because admin perspective was offered; while it may be possible to find an admin who recognizes a BLP claim, "obvious to any reasonable Wikipedian that it was the right thing to do" seems to be a higher threshold, particularly for the broadest protection from being blocked. This has given me a lot to consider for how I personally wish to proceed, and I also appreciated the traffic ticket analogies in the archived discussion, because my personal preference is to slow down rather than try to talk my way out of tickets. Thanks again,
Beccaynr (
talk) 20:05, 4 December 2023 (UTC)
Beccaynr and Bradv I respond to the ping also here. But this conversation is correctly formed with the special nature of topic. This page Dwivedi is stressful to modify because the whole history of assembly has intimidate and ad hominem challenges. The criteria and standards of other philosophers articles are not appliqués to the page from this problem. During the survey, I found that certain other Indian académics pages have this problem. Wikipedia may please take into account this particular circumstance with Indian politic to keep this a decent page.
The NDTV interview has the context of the birthday of Gandhi as same as the co-authored Indian Express. Her stress on Gandhi in this clip of less than a minute is not significant. Her articles and co-author book dedicated to Gandhi to be a most complete and learned job. The Print website quotes many of her solo words. But research on social networks shows that the journalist interpreted her statements to reflect indignation of the far right in social media. Clear that it is biased to create sensationalism. Most other media reports of her recent statements are the same method derived.
If you utilise Google and make social networks research, its statements are almost always wrongly attributed. It is the basis of threats and harassment. But the other basis is something now apparent after seeing the recent publishing history of article page. People of the far right want to keep the bad sensational target on Hinduism, but her vast declarations, written alone and co-written, on discrimination and racism of caste in India are the real animosity's cause. In the article in Esprit on Hindou many many Indian politicians and academicians are named not just Gandhi. The solution may be to make a section on her work on the castes and to expand it. Your project of making article separate on “Hindou Hoax” is good also. The alarming question here is that it can find the threats to her on social networks undeleted. Serious problematic is you can find assassinations of many Indian philosophers intellectuels in news and wikipedia.
Guillaume R Legrand (
talk) 21:21, 4 December 2023 (UTC)
You have both given me a lot to read up on. Thank you. –
bradv 15:22, 5 December 2023 (UTC)
I'm giggling
If I'd known the sock would out themselves so publicly, I wouldn't have spent as much time on the SPI filing. Thanks for the good work b!
Firefangledfeathers (
talk /
contribs) 03:39, 6 December 2023 (UTC)
My pleasure. ;) –
bradv 03:43, 6 December 2023 (UTC)
Context for talk page stalkers
here. –
bradv 17:25, 6 December 2023 (UTC)
Following a
talk page discussion, the
Administrators' accountability policy has been updated to note that while it is considered best practice for administrators to have
notifications (pings) enabled, this is not mandatory. Administrators who do not use notifications are now strongly encouraged to indicate this on their user page.
Arbitration
Following
a motion, the
Extended Confirmed Restriction has been amended, removing the allowance for non-extended-confirmed editors to post constructive comments on the "Talk:" namespace. Now, non-extended-confirmed editors may use the "Talk:" namespace solely to make edit requests related to articles within the topic area, provided that their actions are not disruptive.
The Arbitration Committee has
announced a call for Checkusers and Oversighters, stating that it will currently be accepting applications for CheckUser and/or Oversight permissions at any point in the year.
Hi Brad! I'd like to wish you a splendid solstice season as we wrap up the year. Here is an artwork, made individually for you, to celebrate. (The trees happened to be especially tall in this one.) I always appreciate your insights and contributions. Take care, and thanks for all you do to make Wikipedia better!Cheers, {{u|Sdkb}}talk
We wish you a Merry Christmas, We wish you a Merry Christmas, We wish you a Merry Christmas, And a Happy New Year!
May your holidays be filled with peace and joy. Spread the
WikiLove by wishing another user a
Merry Christmas, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Happy New Year!
CAPTAIN RAJU(T) 22:34, 28 December 2023 (UTC) Adapted from {{
Xmas6}}. Spread the cheer by adding {{
subst:
User:Altamel/Christmas}} to their talk page.
@
CAPTAIN RAJU, did you mean to put this in this section? –
bradv 22:40, 28 December 2023 (UTC)
I did not want put this in this section.I already tag new section/subject.thanks.
CAPTAIN RAJU(T) 22:52, 28 December 2023 (UTC)
Okay, I'm going to suggest you go back and add section headings for all the messages you sent out today. With the way you did it the messages won't archive properly. –
bradv 23:02, 28 December 2023 (UTC)
Scripts++ Newsletter – Issue 23
New year, new scripts. Welcome to the 23rd issue of the Wikipedia
Scripts++ Newsletter, covering around 39% of our favorite new and updated user scripts since 24 December 2021. That’s right, we haven’t published in two years! Can you believe it? Did you miss us?
Got anything good? Tell us about your new, improved, old, or messed-up script
here!
User:Alexander Davronov/HistoryHelper has now become stable with some bugfixes and features such as automatically highlighting potentially uncivil edit summaries and automatically pinging all the users selected.
To a lesser extent, the same goes for
User:PrimeHunter/Search sort.js. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Aaron Liu:
Watchlyst Greybar Unsin is a rewrite of Ais's Watchlist Notifier with modern APIs and several new features such as not displaying watchlist items marked as seen (hence the name), not bolding diffs of unseen watchlist elements which doesn’t work properly anyways, displaying the rendered edit summary, proper display of log and creation actions and more links.
Alexis Jazz:
Factotum is a spiritual successor to reply-link with a host of extra features like section adding, link rewriting, regular expressions and more.
User:Aveaoz/AutoMobileRedirect: This script will automatically redirect MobileFrontend (en.m.wikipedia) to normal Wikipedia. Unlike existing scripts, this one will actually check if your browser is mobile or not through its secret agent string, so you can stay logged in on mobile! Hooray screen estate!
Deputy is a first-of-its-kind copyright cleanup toolkit. It overrides the interface for
Wikipedia:Contributor copyright investigations for easy case processing. It also includes the functionality of the following (also new) scripts:
User:Elominius/gadget/diff arrow keys allows navigation between diffs with the arrow keys. It also has a version that requires holding Ctrl with the arrow key.
Frequently link to Wikipedia on your websites yet find generating CC-BY credits to be such a hassle? Say no more!
User:Luke10.27/attribute will automatically do it for ya and copy the credit to yer clipboard.
User:MPGuy2824/MoveToDraft, a spiritual successor (i.e. fork) to
Evad37's script, with a few bugs solved, and a host of extra features like check-boxes for choosing draftification reasons, multi-contributor notification, and appropriate warnings based on last edit time.
/CopyCodeBlock: one of the most important operations for any scripter and script-user is to copy and paste. This script adds a copy button in the top right of every code block (not to be confused with <code>) that will, well, copy it to your clipboard!
m:User:NguoiDungKhongDinhDanh/AceForLuaDebugConsole.js adds the
Ace editor (a.k.a. the editor you see when editing JS, CSS and Lua on Wikimedia wikis) to the Lua debug console. "In my opinion, whoever designed it to be a plain <textarea> needs to seriously reconsider their decision."
GANReviewTool quickly and easily closes good article nominations.
ReviewStatus displays whether or not a mainspace page is marked as reviewed.
SpeciesHelper tries to add the correct speciesbox, category, taxonbar, and stub template to species articles.
User:Opencooper/svgReplace and
Tol's fork replaces all rasterized SVGs with their original SVG codes for your loading pleasures. Tell us which one is better!
ArticleInfo displays page information at the top of the page, directly below the title.
/HeaderIcons takes away the Vector 2022 user dropdown and replaces it with all of the icons within, top level, right next to the Watchlist. One less click away! There's also an
alternate version that uses text links instead of icons.
Following a
motion, the Arbitration Committee rescinded the restrictions on the page name move discussions for the two Ireland pages that were
enacted in June 2009.
I was just at the
User:Worm That Turned talk page and read your mention of the EotW/Eddie award and how it helped you stay on board. For you to mention it after all these years gives me great enjoyment and a sense of awareness that the award accomplishes what it was intended to do. It means so much for me to hear that... at a time when I am thinking of slowing down or handing it on to the next caretaker. Thanks for the boost of encouragement.
Buster Seven Talk (UTC) 06:07, 15 January 2024 (UTC)
Hi @
Buster7, I meant what I said to WTT – the EotW program is definitely a good thing, and I really hope it stays as active and effective as it has been. Thanks for running it all these years. Incidentally, Worm's response to me was to pay it forward, so if you're encouraged and remotivated by my message, I suppose I have. Cheers. –
bradv 01:52, 17 January 2024 (UTC)
An
RfC about increasing the inactivity requirement for Interface administrators is open for feedback.
Technical news
Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. (
T326065)
Arbitration
Following a
motion, the Arbitration Committee adopted a new enforcement restriction on January 4, 2024, wherein the Committee may apply the 'Reliable source consensus-required restriction' to specified topic areas.
Community feedback is
requested for a draft to replace the "Information for administrators processing requests" section at
WP:AE.
A vote to ratify the charter for the
Universal Code of Conduct Coordinating Committee (U4C) is open till 2 February 2024, 23:59:59 (UTC) via
Secure Poll. All eligible voters within the Wikimedia community have the opportunity to either support or oppose the adoption of the U4C Charter and share their reasons. The details of the voting process and voter eligibility can be found
here.
Community Tech has made some preliminary decisions about the future of the
Community Wishlist Survey. In summary, they aim to develop a new, continuous intake system for community technical requests that improves prioritization, resource allocation, and communication regarding wishes.
Read more
I saw that you closed the previous
previous SPI on this editor, after it had been pending for some time. I was wondering if you would be open to closing the
current one as well, as it has also been pending for a while after CU had commented.
33ABGirl (
talk) 09:19, 12 February 2024 (UTC)
Thank you for taking the measure to block the account.
33ABGirl (
talk) 02:29, 14 February 2024 (UTC)
I want to bring your attention to several IP's where the editing pattern is similar to the user account on the current event portal for a certain day. The IP's are 82.34.33.245, 185.177.200.54, and 2A00:23C4:B18A:2E01:96E6:F7FF:FE2B:63E4. These are the ones I found so far and have been recent since I opened that casepage. I wanted to bring this to your attention since you blocked and closed the page. I've been reverting the edits due to their suspicious similarities. --
WikiCleanerMan (
talk) 2:36, 19 February 2024 (UTC)
Another one is 76.146.66.26. --
WikiCleanerMan (
talk) 16:17, 19 February 2024 (UTC)
This
report may also be of relevance. I reported a similar IP to Courcelles (who did the CU on the SPI), who blocked the IP for a duration of one week.
33ABGirl (
talk) 01:37, 20 February 2024 (UTC)
Scripts++ Newsletter – Issue 24
Hello everyone, and welcome to the 24th issue of the Wikipedia
Scripts++ Newsletter, covering all our favorite new and updated user scripts since 24 December 2021. Uh-huh, we're finally covering the good ones among the rest! Aren't you excited? Remember to include a link in double brackets to the script's .js page when you install the script, so that we can see who uses the script in WhatLinksHere! The ScriptInstaller gadget automatically does this.
Aaron Liu (
talk) 01:00, 1 March 2024 (UTC)
Got anything good? Tell us about your new, improved, old, or messed-up script
here!
Featured script
Making user scripts load faster by SD0001 is this month's featured script, which caches userscripts every day to eliminate the overhead caused by force-downloading the newest version of scripts every time you open a Wikipedia page. Despite being released in April 2021, our best script scouters have failed to locate it due to its omission from
the US of L. For security reasons, the script only supports loading JavaScript pages.
Newly maintained scripts
After earthly attempts at improving the original have failed...
Ahecht has created
a fork of
SiBr4/TemplateSearch, which adds the "TP:" shortcut for "Template:" in the search box, and updated it to be compatible with Vector 2022.
AquilaFasciata/goToTopFast is a much faster fork of the classic goToTop script that also adds compatibility for Minerva and Vector 2022.
Without caching. Each script takes 400–500ms. A particularly large script takes 1.11 s! Internet download speed is 50 Mbps.With caching enabled. Each script takes just 1-2 ms to load.
Improve a script
Unfortunately, this section has remained nearly identical. Help us out here!
To a lesser extent, the same goes for
PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Dragoniez/SuppressEnterInForm stops you from accidentally submitting anything due to pressing enter while in the smaller box, and works on almost anything... except the InputBox element itself, used in subscription lists and
the Signpost Crossword! Oh, the humanity!
Doǵu/Adiutor(pictured) provides a nice, integrated interface to do some twinkley tasks such as copyvio detection, CSD tagging, and viewing the most recent diff.
Eejit43 has quite the aesthetically pleasing scripts, all made in
TypeScript.
/afcrc-helper is a replacement for the unmaintained
Enterprisey/AFCRHS and processes Redirects for Creation and Categories for Creation requests.
/ajax-undo stops the "undo" button from taking you to another page while providing a text box to provide a reason for the revert.
/redirect-helper(pictured) adds a much better interface for editing and redirects, including categorization, for which valid categories are dictated by
/redirect-helper.json.
/rmtr-helper helps process technical requested moves without being able to actually move them.
Guycn2/UserInfoPopup(pictured) adds a flyout after the watchlist star on userspace pages that displays the common information you might use about a user.
Jeeputer/editCounter, under userspace, adds a portlet link to count your edits by namespace, put them in a table, and put that table in a hardcoded subpage, all in the background.
Hilst/Scripts/sectionLinks converts all section links to use the § sign, which are known to be preferred over the ugly # by 99% of the devils I've met.
PrimeHunter/Category source.js adds portlet links to tell you where a category for an article comes from and supports those from template transclusions.
Sophivorus's
MiniEdit adds some nice, li'l buttons next to paragraphs to edit their wikitext with a minimal interface.
Edit-listings
Dragoniez/ToollinkTweaks adds more and customizable links next to users in page history, logs, watchlist, recent changes, etc.
Firefly/more-block-info optimizes the display of rangeblocks in contribution pages. Doesn't work outside the English locale of any wiki, unfortunately.
NguoiDungKhongDinhDanh/AjaxLoader makes paging links (e.g. older 50, 500, newest) load without refreshing and makes you realize how slow your internet actually is.
Appearance-ricing
Ahecht/RedirectID adds the redirect target to all redirects. For all the
WP:NAVPOPS haters. (Do these exist?)
Dragoniez/MarkBLockedGlobal: Remember the "strike blocked usernames" gadget? Now you can use a red, dotted line to highlight rangeblocks and global locks!
Jonesey/common(pictured) has some styles to overhaul your Vector 2022 experience. It reduces padding everywhere, and makes the top bar animation faster.
Aaron Liu/V22 is a fork that narrows the sidebars instead of upheaving them, reverts the January 2024 dropdown changes, and restores the old page-link color for links that don't go outside the current wiki.
Nardog: SmartDiff is a spiritual successor to
Enterprisey/fancy-diffs. It makes the page title part of links in diffs clickable, along with template and parser function calls. Unnamed parameters can be configured per template to also be linked. All links are styled based on the normal CSS classes of rendered links.
For the paranoid:
Rublov/anonymize replaces your username at the top of the screen with the generic "User page" text. Remember, it is your duty to persuade everyone that
editing is an honor.
/AjaxBlock provides a dialog box for easy input of reasons while blocking users.
/Selective Rollback(pictured) provides a dialog box to customize
rollback edit summaries and does them without reloading the page. Seriously, why doesn't MediaWiki already do this?
/flickrsearch adds a portlet link to search for uploadable flickr images about the subject.
/randomincategory adds a portlet link when on Category pages to go to a random page in the current category.
Vghfr/EasyTemplates adds a portlet link to automatically insert some of the most common inline {{
fix}} templates.
Yes, we're just doing 'em as we go now. Thanks for reading through this looong issue, if you did! I'm sure this'll send a record for the longest issue ev-ah. You may need to wait even longer for the last issue, as our reserve of old-y and goodie scripts have ran out... We encourage you to try and do some of the requests or improvement tasks. See you in Summer, hopefully!
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the
current talk page.
Hi Bradv. ArbClerkBot doesn't seem to be up right now. Would it be possible to look into that? If you lack capacity to look into it, that's also totally understandable. It may also be helpful to add a technically-minded member of the clerk team to the maintainers of the bot.
We could also likely write a brief bash script to check the health of the task and if error shows, then kill it and let it restart. --
Amanda (she/her) 22:21, 1 August 2023 (UTC)
@
AmandaNP: hm, it doesn't seem to have worked with the most recent post either. Best, KevinL (aka
L235·t·c) 23:02, 2 August 2023 (UTC)
Hey Kevin, I'm currently on vacation but I'll look into this next week. –
bradv 17:22, 3 August 2023 (UTC)
Take your time — this is as non-urgent as it gets :) KevinL (aka
L235·t·c) 17:56, 3 August 2023 (UTC)
I just looked into it. Something seems to have pulled out the underlying library we are using out from underneath us :/ Going to read the documentation again to see how to readd this, though I swear we haven't touched this, so this was either a server lapse or something tool admins did purposefully. --
Amanda (she/her) 18:14, 6 August 2023 (UTC)
Technical reason: venvs/grid engine which we are using for this are extremely flakey on the bastion servers. I've been told that stability only exists in k8ns. So essentially we have to migrate to k8ns to prevent this from happening again, and I've never touched said software, and although
wikitech:Help:Toolforge/Jobs framework exists, i've been told it's an absolute pain in the ass to set up, but will be fine once you get it there. And DeltaQuadBot is now at risk over this same issue and explains why I've had similar issues in the past there too. So another boatload of manhours to figure this out that I'm not taking unplanned time out of my day to deal with it. I will consider it for next weekend.
Plain english reason: Bot does not have the proper food to run, bot will continue to fail until we change it's diet, and DeltaQuadBot is at risk for this also. --
Amanda (she/her) 21:12, 6 August 2023 (UTC)
@
AmandaNP, I'm not sure the version on toolforge ever worked properly. The bot was running on my own server until May 22, when it inadvertently got shut down. I've restarted the server and now it appears to be working again. I am interested in porting this though, so let's work on that together when we both have some free time. @
L235, it's running again. ;) –
bradv 13:01, 9 August 2023 (UTC)
That would explain why it looks like the errors started last year... That is reassuring. I'll reach out and offer some dates that would be best. --
Amanda (she/her) 13:03, 9 August 2023 (UTC)
Following
an RfC,
TFAs will be automatically semi-protected the day before it is on the main page and through the day after.
A discussion at
WP:VPP about revision deletion and oversight for
dead names found that [s]ysops can choose to use revdel if, in their view, it's the right tool for this situation, and they need not default to oversight. But oversight could well be right where there's a particularly high risk to the person. Use your judgment.
The SmallCat dispute case has closed. As part of the final decision, editors participating in
XfD have been reminded to be careful about forming local consensus which may or may not reflect the broader community consensus. Regular closers of
XfD forums were also encouraged to note when broader community discussion, or changes to policies and guidelines, would be helpful.
Miscellaneous
Tech tip: The "Browse history interactively" banner shown at the top of
Special:Diff can be used to easily look through a history, assemble composite diffs, or find out what archive something wound up in.
New Page Review article queue, March to September 2023
Backlog update:
At the time of this message, there are 11,300 articles and 15,600 redirects awaiting review. This is the highest backlog in a long time. Please help out by doing additional reviews!
October backlog elimination drive:
A one-month backlog drive for October will start in one week! Barnstars will be awarded based on the number of articles and redirects patrolled. Articles will earn 4x as many points compared to redirects. You can
sign up here.
PageTriage code upgrades:
Upgrades to the
PageTriage code, initiated by the
NPP open letter in 2022 and actioned by the
WMF Moderator Tools Team in 2023, are ongoing. More information can be found
here. As part of this work, the
Special:NewPagesFeed now has a new version in beta! The update leaves the NewPagesFeed appearance and function mostly identical to the old one, but updates the underlying code, making it easier to maintain and helping make sure the extension is not decommissioned due to maintenance issues in the future. You can try out the new Special:NewPagesFeed
here - it will replace the current version soon.
Notability tip:
Professors can meet
WP:PROF #1 by having their academic papers be widely cited by their peers. When reviewing professor articles, it is a good idea to find their
Google Scholar or
Scopus profile and take a look at their
h-index and number of citations. As a very rough rule of thumb, for most fields, articles on people with a h-index of
twenty or more, a first-authored paper with more than a thousand citations, or multiple papers each with more than a hundred citations are likely to be kept at AfD.
Reviewing tip:
If you would like like a second opinion on your reviews or simply want another new page reviewer by your side when patrolling, we recommend pair reviewing! This is where two reviewers use
Discord voice chat and screen sharing to communicate with each other while reviewing the same article simultaneously. This is a great way to learn and transfer knowledge.
Hi, @
Bradv: I was partially blocked for problematic COI editing and wanted to check with you first before asking to be unblocked. The reason I would like to be unblocked is so I can directly edit a project I am working on that involves the
California Historical Landmarks in Santa Clara County. There are many corrections that need to be made on this page as well as the landmark articles that, in several cases, do not point to the correct article and/or have no information about the landmark, e.g. the site of invention of the first commercially practicable integrated circuit. I admit that I did some problematic COI editing and I promise not to do it again. I enjoy doing the research and working on meaningful Wikipedia articles. Please let me know what you think?
Greg Henderson (
talk) 17:56, 27 September 2023 (UTC)
I'm not sure why you are asking me.
User talk:Drmies#I am partially blocked already exists, and if you can't accept that advice you can try post an {{
unblock}} request on your talk page or appeal to
WP:AN. I would suggest, however, that your best path to restoration is to be as forthcoming as possible about your previous COI editing, and to help others with the cleanup efforts. More apologies alone won't cut it – we need to see that you understand what it takes to write a
neutral encyclopedia. –
bradv 19:49, 30 September 2023 (UTC)
An RfC is open regarding amending the
paid-contribution disclosure policy to add the following text: Any administrator soliciting clients for paid Wikipedia-related consulting or advising services not covered by other paid-contribution rules must disclose all clients on their userpage.
Technical news
Administrators can now choose to add the user's user page to their watchlist when changing the usergroups for a user. This works both via
Special:UserRights and via the API. (
T272294)
WikiProject Articles for creation is holding a month long
Backlog Drive!
The goal of this drive is to reduce the backlog of unreviewed drafts to less than 2 months outstanding reviews from the current 4+ months. Bonus points will be given for reviewing drafts that have been waiting more than 30 days. The drive is running from 1 November 2023 through 30 November 2023.
Barnstars will be given out as awards at the end of the drive.
There is a backlog of over 2300 pages, so start reviewing drafts. We're looking forward to your help!
MediaWiki message delivery (
talk) 13:23, 31 October 2023 (UTC)
I see they are now edit warring the closure from different IP addresses. --
CNMall41 (
talk) 21:57, 5 November 2023 (UTC)
I see this has now been taken care of by another admin. I'm not sure which LTA this is, but if you see them pop up again I suggest reporting them to
AIV. –
bradv 18:29, 6 November 2023 (UTC)
Following
a motion, the contentious topic designation of Prem Rawat has been struck. Actions previously taken using this contentious topic designation are still in force.
Following
several motions, multiple topic areas are no longer designated as a contentious topic. These contentious topic designations were from the Editor conduct in e-cigs articles, Liancourt Rocks, Longevity, Medicine, September 11 conspiracy theories, and Shakespeare authorship question cases.
Following
a motion, remedies 3.1 (All related articles under 1RR whenever the dispute over naming is concerned), 6 (Stalemate resolution) and 30 (Administrative supervision) of the Macedonia 2 case have been rescinded.
Following
a motion, remedy 6 (One-revert rule) of the The Troubles case has been amended.
An arbitration case named Industrial agriculture has been opened. Evidence submissions in this case close 8 November.
Miscellaneous
The
Articles for Creation backlog drive is happening in November 2023, with 700+ drafts pending reviews for in the last 4 months or so. In addition to the AfC participants, all administrators and New Page Patrollers can conduct reviews using the helper script, Yet Another AFC Helper Script, which can be enabled in
the Gadgets settings.
Sign up here to participate!
Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The
Arbitration Committee is the panel of editors responsible for conducting the
Wikipedia 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 impose
site bans,
topic bans, editing restrictions, and other measures needed to maintain our editing environment. The
arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2023 election, please review
the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{
NoACEMM}} to your user talk page.
MediaWiki message delivery (
talk) 00:32, 28 November 2023 (UTC)
Public clarification
Yeah, so it turns out you weren't even in that bit of discussion, sorry again—I was actually replying to
User:SarekofVulcan, who mentioned NewYorkBrad in his comment, and of course I misread it as being yours. Slightly convoluted, but a fooolish mix up on my part.
——Serial 12:27, 28 November 2023 (UTC)
That makes more sense, but I think you're still missing a word. It doesn't really matter though – there are plenty of comments worth ignoring in that thread; no sense adding to the pile. –
bradv 15:24, 28 November 2023 (UTC)
Conflict with griefer Skitash on Tunisia related pages
Dear Wikipedia Administrators,
I hope this message finds you well. I am writing to appeal the block you placed on my Wikipedia account. I believe the block was issued due to my attempts to revert edits made by a user engaging in ethno-centric bias, specifically in relation to the representation of Tunisian ethnicity, language, and Berber ancestry.
I understand the importance of maintaining a neutral point of view on Wikipedia and strive to adhere to its policies. In this case, my intention was to ensure that the information presented accurately reflects the diversity of perspectives and historical facts regarding Tunisian heritage.
The user in question has been systematically removing sourced content that acknowledges the non-Arabic aspects of Tunisian ethnicity and language, as well as information about Berber ancestry or other non-arab ancestry or language elements. This raises concerns about the impartiality and accuracy of the content being presented on Wikipedia.
I believe my efforts to revert these edits were in line with Wikipedia's commitment to providing unbiased and verifiable information. My actions were not intended to disrupt the platform but rather to uphold the principles of neutrality and inclusivity that are essential to Wikipedia's credibility.
I kindly request a review of the block on my account, taking into consideration the context of the edits in question and my commitment to upholding Wikipedia's content policies. I am more than willing to engage in constructive discussions, provide additional sources, and work collaboratively to ensure the accuracy and neutrality of the content related to Tunisian ethnicity and language.
Thank you for your time and consideration. I look forward to a resolution that promotes the integrity and objectivity of Wikipedia.
Sincerely,
asmodim
Asmodim (
talk) 22:23, 30 November 2023 (UTC)
The block has already expired, so there's no point in appealing it. I'm glad to see you are discussing your disagreements now instead of edit warring – that's a considerable improvement. The next step would be to make a coherent argument on the talk page, supported by
reliable sources, on exactly what needs to be changed. Bonus points if you can do so while
commenting on content rather than on the contributor. –
bradv 01:58, 1 December 2023 (UTC)
Editor experience invitation
Hi Bradv :) I'm looking for people to interview
here. Feel free to pass if you're not interested.
Clovermoss🍀(talk) 02:18, 1 December 2023 (UTC)
@
Immanuelle, you know you can move these yourself now, right? We trust you. –
bradv 06:57, 2 December 2023 (UTC)
Nevermind, I see there's still a restriction in effect. I'll look these over in the next day or so. –
bradv 06:59, 2 December 2023 (UTC)
@
Immanuelle, I've accepted all of these. There is some concern that
Amazing Cultivation Simulator may not meet
WP:GNG, but that can be dealt with at
AFD. Likewise, there was some objection to
Makimuku Ishizuka Kofun being a stand-alone article rather than merged into
Makimuku ruins, but that can be dealt with in mainspace if there is consensus for merging. (I also note that your
restriction prohibits you from merging content from declined drafts, so arguably you couldn't even perform the merge as suggested by AfC reviewers anyway.) –
bradv 17:16, 2 December 2023 (UTC)
@
Bradv yeah currently all declined articles with suggested merges have been completed. I feel that restriction in particular is a rather unconstructive one that I plan on appealing soon.
I also want to attempt to prove I can do translations well by getting an exemption for
Draft:Horaisan Kofun so I can prove myself
I am a bit unsure what to do for this, and whether to wait longer. Do you have advice in this area?
Immanuelle ❤️💚💙
(talk to the cutest Wikipedian) 19:37, 2 December 2023 (UTC)
Congratulations!
Most Braddiest Brad
For being the most BarfVD ever.
GRINCHIDICAE🎄 20:26, 2 December 2023 (UTC)
You've outdone yourself. –
bradv 21:21, 2 December 2023 (UTC)
Just a thought
I just want to say that it is because of
admin power moves such as these, that people like me who have spent an entire DECADE working towards improving Wikipedia want to quit for good. You speak about "thousands of people [...] working tirelessly to help improve the encyclopedia and achieve its vision" in your user page. What has been the point of my working tirelessly for a decade to achieve this, so that I can be demeaned and blocked without consequence for reverting spam?
Krimuk2.0 (
talk) 06:38, 3 December 2023 (UTC)
What about your treatment of the other editors on
that page? I count at least 7 reverts from you on December 1, without even a single post on the talk page. This is textbook
edit warring, and as someone who's been around for over a decade, you should know better. –
bradv 15:23, 3 December 2023 (UTC)
You mean treatment of reverting spam & poorly sourced info from other editors, that was
reverted by someone else soon after?
Krimuk2.0 (
talk) 06:35, 4 December 2023 (UTC)
It doesn't matter whether you were correct or not, you were still edit warring. Regardless, the talk page of the article is still available to you if you wish to engage in some collaborative article building. –
bradv 14:50, 4 December 2023 (UTC)
thank you
Hi bradv, the ANI thread closed before I could respond to your final comment to me
[1], so I am following up here. Overall, I regret not being more proactive about seeking more editor participation with the content side of the dispute - I filed a request at RFPP and then a report at ANEW, but I could have also gone to BLPN and/or pursued other content-related dispute resolution options, and I could have used the
disputed inline template.
I appreciate your responses to my replies to your requests for an explanation at ANI about why I thought a BLP exemption applied, because this interaction emphasizes how controversial BLP exemptions for 3RR can be. One aspect of our interaction that I found particularly helpful is the clarification of how a credible claim of a BLP exemption may seem apparent, but if it requires an essay of explanation, then it can be considered 'controversial.'
And then I reviewed the July 2022 "
Making WP:3RRNO point 7 more specific" discussion in the WT:Edit warring Archive, and I think it not only reinforces all of this but also adds depth related to the implementation and purpose of the policy. So I hope this follow up helps provide some reassurance about my improved understanding of the 3RRBLP threshold. Thank you,
Beccaynr (
talk) 04:34, 4 December 2023 (UTC)
I appreciate your message, @
Beccaynr. I hope it didn't feel too much like I was interrogating you – I was really trying to understand your objections to the change. But yes, the
3RRBLP exemption is somewhat complicated, as it needs to strike a delicate balance between preventing disruptive editing while protecting the rights of the subjects of BLPs. I read that discussion you linked and I don't know where I stand: on the one hand adding a word like "obvious" or "uncontroversial" should make things more clear, but I question whether that would weaken our BLP protections. And if we make that change, what kind of other nefarious behaviour are we going to unlock? Perhaps another way of looking at this is that we don't even need that exemption – it's already covered by
WP:IAR. In other words, if you're going to break 3RR it should be obvious to any reasonable Wikipedian that it was the right thing to do, and that you're willing to risk consequences to protect the integrity of the encyclopedia. At any rate, I appreciate you patiently explaining the real-life context and implications of these edits. I don't know much about Indian politics or history, but I am trying to learn. Happy editing. –
bradv 15:13, 4 December 2023 (UTC)
Thank you, bradv, and your questions felt more like the
Socratic method to me, including because the interaction helped me better understand the meaning of 'controversial' in the 3RRBLP exemption. And while this is an imperfect analogy, I am familiar with the delicate balance of a lawyer's duties related to roles as an officer of the court and representative of a client, which in some ways reminds me of the delicate balance between protecting the encyclopedia from disruptive editing and protecting the rights of a BLP subject. I also feel as if I have some experience from work on contentious BLPs that made some concerns expressed in the WT:Edit warring archive discussion ring true about unintended consequences from policy language changes.At this point, I am tending to think of 3RRBLP somewhat like seeking ex parte relief - where other participants have no opportunity to be heard, and the best case is clearly obvious and urgent. I also found the WT:Edit warring archive discussion useful because admin perspective was offered; while it may be possible to find an admin who recognizes a BLP claim, "obvious to any reasonable Wikipedian that it was the right thing to do" seems to be a higher threshold, particularly for the broadest protection from being blocked. This has given me a lot to consider for how I personally wish to proceed, and I also appreciated the traffic ticket analogies in the archived discussion, because my personal preference is to slow down rather than try to talk my way out of tickets. Thanks again,
Beccaynr (
talk) 20:05, 4 December 2023 (UTC)
Beccaynr and Bradv I respond to the ping also here. But this conversation is correctly formed with the special nature of topic. This page Dwivedi is stressful to modify because the whole history of assembly has intimidate and ad hominem challenges. The criteria and standards of other philosophers articles are not appliqués to the page from this problem. During the survey, I found that certain other Indian académics pages have this problem. Wikipedia may please take into account this particular circumstance with Indian politic to keep this a decent page.
The NDTV interview has the context of the birthday of Gandhi as same as the co-authored Indian Express. Her stress on Gandhi in this clip of less than a minute is not significant. Her articles and co-author book dedicated to Gandhi to be a most complete and learned job. The Print website quotes many of her solo words. But research on social networks shows that the journalist interpreted her statements to reflect indignation of the far right in social media. Clear that it is biased to create sensationalism. Most other media reports of her recent statements are the same method derived.
If you utilise Google and make social networks research, its statements are almost always wrongly attributed. It is the basis of threats and harassment. But the other basis is something now apparent after seeing the recent publishing history of article page. People of the far right want to keep the bad sensational target on Hinduism, but her vast declarations, written alone and co-written, on discrimination and racism of caste in India are the real animosity's cause. In the article in Esprit on Hindou many many Indian politicians and academicians are named not just Gandhi. The solution may be to make a section on her work on the castes and to expand it. Your project of making article separate on “Hindou Hoax” is good also. The alarming question here is that it can find the threats to her on social networks undeleted. Serious problematic is you can find assassinations of many Indian philosophers intellectuels in news and wikipedia.
Guillaume R Legrand (
talk) 21:21, 4 December 2023 (UTC)
You have both given me a lot to read up on. Thank you. –
bradv 15:22, 5 December 2023 (UTC)
I'm giggling
If I'd known the sock would out themselves so publicly, I wouldn't have spent as much time on the SPI filing. Thanks for the good work b!
Firefangledfeathers (
talk /
contribs) 03:39, 6 December 2023 (UTC)
My pleasure. ;) –
bradv 03:43, 6 December 2023 (UTC)
Context for talk page stalkers
here. –
bradv 17:25, 6 December 2023 (UTC)
Following a
talk page discussion, the
Administrators' accountability policy has been updated to note that while it is considered best practice for administrators to have
notifications (pings) enabled, this is not mandatory. Administrators who do not use notifications are now strongly encouraged to indicate this on their user page.
Arbitration
Following
a motion, the
Extended Confirmed Restriction has been amended, removing the allowance for non-extended-confirmed editors to post constructive comments on the "Talk:" namespace. Now, non-extended-confirmed editors may use the "Talk:" namespace solely to make edit requests related to articles within the topic area, provided that their actions are not disruptive.
The Arbitration Committee has
announced a call for Checkusers and Oversighters, stating that it will currently be accepting applications for CheckUser and/or Oversight permissions at any point in the year.
Hi Brad! I'd like to wish you a splendid solstice season as we wrap up the year. Here is an artwork, made individually for you, to celebrate. (The trees happened to be especially tall in this one.) I always appreciate your insights and contributions. Take care, and thanks for all you do to make Wikipedia better!Cheers, {{u|Sdkb}}talk
We wish you a Merry Christmas, We wish you a Merry Christmas, We wish you a Merry Christmas, And a Happy New Year!
May your holidays be filled with peace and joy. Spread the
WikiLove by wishing another user a
Merry Christmas, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Happy New Year!
CAPTAIN RAJU(T) 22:34, 28 December 2023 (UTC) Adapted from {{
Xmas6}}. Spread the cheer by adding {{
subst:
User:Altamel/Christmas}} to their talk page.
@
CAPTAIN RAJU, did you mean to put this in this section? –
bradv 22:40, 28 December 2023 (UTC)
I did not want put this in this section.I already tag new section/subject.thanks.
CAPTAIN RAJU(T) 22:52, 28 December 2023 (UTC)
Okay, I'm going to suggest you go back and add section headings for all the messages you sent out today. With the way you did it the messages won't archive properly. –
bradv 23:02, 28 December 2023 (UTC)
Scripts++ Newsletter – Issue 23
New year, new scripts. Welcome to the 23rd issue of the Wikipedia
Scripts++ Newsletter, covering around 39% of our favorite new and updated user scripts since 24 December 2021. That’s right, we haven’t published in two years! Can you believe it? Did you miss us?
Got anything good? Tell us about your new, improved, old, or messed-up script
here!
User:Alexander Davronov/HistoryHelper has now become stable with some bugfixes and features such as automatically highlighting potentially uncivil edit summaries and automatically pinging all the users selected.
To a lesser extent, the same goes for
User:PrimeHunter/Search sort.js. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Aaron Liu:
Watchlyst Greybar Unsin is a rewrite of Ais's Watchlist Notifier with modern APIs and several new features such as not displaying watchlist items marked as seen (hence the name), not bolding diffs of unseen watchlist elements which doesn’t work properly anyways, displaying the rendered edit summary, proper display of log and creation actions and more links.
Alexis Jazz:
Factotum is a spiritual successor to reply-link with a host of extra features like section adding, link rewriting, regular expressions and more.
User:Aveaoz/AutoMobileRedirect: This script will automatically redirect MobileFrontend (en.m.wikipedia) to normal Wikipedia. Unlike existing scripts, this one will actually check if your browser is mobile or not through its secret agent string, so you can stay logged in on mobile! Hooray screen estate!
Deputy is a first-of-its-kind copyright cleanup toolkit. It overrides the interface for
Wikipedia:Contributor copyright investigations for easy case processing. It also includes the functionality of the following (also new) scripts:
User:Elominius/gadget/diff arrow keys allows navigation between diffs with the arrow keys. It also has a version that requires holding Ctrl with the arrow key.
Frequently link to Wikipedia on your websites yet find generating CC-BY credits to be such a hassle? Say no more!
User:Luke10.27/attribute will automatically do it for ya and copy the credit to yer clipboard.
User:MPGuy2824/MoveToDraft, a spiritual successor (i.e. fork) to
Evad37's script, with a few bugs solved, and a host of extra features like check-boxes for choosing draftification reasons, multi-contributor notification, and appropriate warnings based on last edit time.
/CopyCodeBlock: one of the most important operations for any scripter and script-user is to copy and paste. This script adds a copy button in the top right of every code block (not to be confused with <code>) that will, well, copy it to your clipboard!
m:User:NguoiDungKhongDinhDanh/AceForLuaDebugConsole.js adds the
Ace editor (a.k.a. the editor you see when editing JS, CSS and Lua on Wikimedia wikis) to the Lua debug console. "In my opinion, whoever designed it to be a plain <textarea> needs to seriously reconsider their decision."
GANReviewTool quickly and easily closes good article nominations.
ReviewStatus displays whether or not a mainspace page is marked as reviewed.
SpeciesHelper tries to add the correct speciesbox, category, taxonbar, and stub template to species articles.
User:Opencooper/svgReplace and
Tol's fork replaces all rasterized SVGs with their original SVG codes for your loading pleasures. Tell us which one is better!
ArticleInfo displays page information at the top of the page, directly below the title.
/HeaderIcons takes away the Vector 2022 user dropdown and replaces it with all of the icons within, top level, right next to the Watchlist. One less click away! There's also an
alternate version that uses text links instead of icons.
Following a
motion, the Arbitration Committee rescinded the restrictions on the page name move discussions for the two Ireland pages that were
enacted in June 2009.
I was just at the
User:Worm That Turned talk page and read your mention of the EotW/Eddie award and how it helped you stay on board. For you to mention it after all these years gives me great enjoyment and a sense of awareness that the award accomplishes what it was intended to do. It means so much for me to hear that... at a time when I am thinking of slowing down or handing it on to the next caretaker. Thanks for the boost of encouragement.
Buster Seven Talk (UTC) 06:07, 15 January 2024 (UTC)
Hi @
Buster7, I meant what I said to WTT – the EotW program is definitely a good thing, and I really hope it stays as active and effective as it has been. Thanks for running it all these years. Incidentally, Worm's response to me was to pay it forward, so if you're encouraged and remotivated by my message, I suppose I have. Cheers. –
bradv 01:52, 17 January 2024 (UTC)
An
RfC about increasing the inactivity requirement for Interface administrators is open for feedback.
Technical news
Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. (
T326065)
Arbitration
Following a
motion, the Arbitration Committee adopted a new enforcement restriction on January 4, 2024, wherein the Committee may apply the 'Reliable source consensus-required restriction' to specified topic areas.
Community feedback is
requested for a draft to replace the "Information for administrators processing requests" section at
WP:AE.
A vote to ratify the charter for the
Universal Code of Conduct Coordinating Committee (U4C) is open till 2 February 2024, 23:59:59 (UTC) via
Secure Poll. All eligible voters within the Wikimedia community have the opportunity to either support or oppose the adoption of the U4C Charter and share their reasons. The details of the voting process and voter eligibility can be found
here.
Community Tech has made some preliminary decisions about the future of the
Community Wishlist Survey. In summary, they aim to develop a new, continuous intake system for community technical requests that improves prioritization, resource allocation, and communication regarding wishes.
Read more
I saw that you closed the previous
previous SPI on this editor, after it had been pending for some time. I was wondering if you would be open to closing the
current one as well, as it has also been pending for a while after CU had commented.
33ABGirl (
talk) 09:19, 12 February 2024 (UTC)
Thank you for taking the measure to block the account.
33ABGirl (
talk) 02:29, 14 February 2024 (UTC)
I want to bring your attention to several IP's where the editing pattern is similar to the user account on the current event portal for a certain day. The IP's are 82.34.33.245, 185.177.200.54, and 2A00:23C4:B18A:2E01:96E6:F7FF:FE2B:63E4. These are the ones I found so far and have been recent since I opened that casepage. I wanted to bring this to your attention since you blocked and closed the page. I've been reverting the edits due to their suspicious similarities. --
WikiCleanerMan (
talk) 2:36, 19 February 2024 (UTC)
Another one is 76.146.66.26. --
WikiCleanerMan (
talk) 16:17, 19 February 2024 (UTC)
This
report may also be of relevance. I reported a similar IP to Courcelles (who did the CU on the SPI), who blocked the IP for a duration of one week.
33ABGirl (
talk) 01:37, 20 February 2024 (UTC)
Scripts++ Newsletter – Issue 24
Hello everyone, and welcome to the 24th issue of the Wikipedia
Scripts++ Newsletter, covering all our favorite new and updated user scripts since 24 December 2021. Uh-huh, we're finally covering the good ones among the rest! Aren't you excited? Remember to include a link in double brackets to the script's .js page when you install the script, so that we can see who uses the script in WhatLinksHere! The ScriptInstaller gadget automatically does this.
Aaron Liu (
talk) 01:00, 1 March 2024 (UTC)
Got anything good? Tell us about your new, improved, old, or messed-up script
here!
Featured script
Making user scripts load faster by SD0001 is this month's featured script, which caches userscripts every day to eliminate the overhead caused by force-downloading the newest version of scripts every time you open a Wikipedia page. Despite being released in April 2021, our best script scouters have failed to locate it due to its omission from
the US of L. For security reasons, the script only supports loading JavaScript pages.
Newly maintained scripts
After earthly attempts at improving the original have failed...
Ahecht has created
a fork of
SiBr4/TemplateSearch, which adds the "TP:" shortcut for "Template:" in the search box, and updated it to be compatible with Vector 2022.
AquilaFasciata/goToTopFast is a much faster fork of the classic goToTop script that also adds compatibility for Minerva and Vector 2022.
Without caching. Each script takes 400–500ms. A particularly large script takes 1.11 s! Internet download speed is 50 Mbps.With caching enabled. Each script takes just 1-2 ms to load.
Improve a script
Unfortunately, this section has remained nearly identical. Help us out here!
To a lesser extent, the same goes for
PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Dragoniez/SuppressEnterInForm stops you from accidentally submitting anything due to pressing enter while in the smaller box, and works on almost anything... except the InputBox element itself, used in subscription lists and
the Signpost Crossword! Oh, the humanity!
Doǵu/Adiutor(pictured) provides a nice, integrated interface to do some twinkley tasks such as copyvio detection, CSD tagging, and viewing the most recent diff.
Eejit43 has quite the aesthetically pleasing scripts, all made in
TypeScript.
/afcrc-helper is a replacement for the unmaintained
Enterprisey/AFCRHS and processes Redirects for Creation and Categories for Creation requests.
/ajax-undo stops the "undo" button from taking you to another page while providing a text box to provide a reason for the revert.
/redirect-helper(pictured) adds a much better interface for editing and redirects, including categorization, for which valid categories are dictated by
/redirect-helper.json.
/rmtr-helper helps process technical requested moves without being able to actually move them.
Guycn2/UserInfoPopup(pictured) adds a flyout after the watchlist star on userspace pages that displays the common information you might use about a user.
Jeeputer/editCounter, under userspace, adds a portlet link to count your edits by namespace, put them in a table, and put that table in a hardcoded subpage, all in the background.
Hilst/Scripts/sectionLinks converts all section links to use the § sign, which are known to be preferred over the ugly # by 99% of the devils I've met.
PrimeHunter/Category source.js adds portlet links to tell you where a category for an article comes from and supports those from template transclusions.
Sophivorus's
MiniEdit adds some nice, li'l buttons next to paragraphs to edit their wikitext with a minimal interface.
Edit-listings
Dragoniez/ToollinkTweaks adds more and customizable links next to users in page history, logs, watchlist, recent changes, etc.
Firefly/more-block-info optimizes the display of rangeblocks in contribution pages. Doesn't work outside the English locale of any wiki, unfortunately.
NguoiDungKhongDinhDanh/AjaxLoader makes paging links (e.g. older 50, 500, newest) load without refreshing and makes you realize how slow your internet actually is.
Appearance-ricing
Ahecht/RedirectID adds the redirect target to all redirects. For all the
WP:NAVPOPS haters. (Do these exist?)
Dragoniez/MarkBLockedGlobal: Remember the "strike blocked usernames" gadget? Now you can use a red, dotted line to highlight rangeblocks and global locks!
Jonesey/common(pictured) has some styles to overhaul your Vector 2022 experience. It reduces padding everywhere, and makes the top bar animation faster.
Aaron Liu/V22 is a fork that narrows the sidebars instead of upheaving them, reverts the January 2024 dropdown changes, and restores the old page-link color for links that don't go outside the current wiki.
Nardog: SmartDiff is a spiritual successor to
Enterprisey/fancy-diffs. It makes the page title part of links in diffs clickable, along with template and parser function calls. Unnamed parameters can be configured per template to also be linked. All links are styled based on the normal CSS classes of rendered links.
For the paranoid:
Rublov/anonymize replaces your username at the top of the screen with the generic "User page" text. Remember, it is your duty to persuade everyone that
editing is an honor.
/AjaxBlock provides a dialog box for easy input of reasons while blocking users.
/Selective Rollback(pictured) provides a dialog box to customize
rollback edit summaries and does them without reloading the page. Seriously, why doesn't MediaWiki already do this?
/flickrsearch adds a portlet link to search for uploadable flickr images about the subject.
/randomincategory adds a portlet link when on Category pages to go to a random page in the current category.
Vghfr/EasyTemplates adds a portlet link to automatically insert some of the most common inline {{
fix}} templates.
Yes, we're just doing 'em as we go now. Thanks for reading through this looong issue, if you did! I'm sure this'll send a record for the longest issue ev-ah. You may need to wait even longer for the last issue, as our reserve of old-y and goodie scripts have ran out... We encourage you to try and do some of the requests or improvement tasks. See you in Summer, hopefully!
Administrator changes
Interface administrator changes
Technical news
Arbitration
Fixed It was a queue error, standard "
have you tried turning it off and back on again". --
Amanda (she/her) 21:52, 1 August 2023 (UTC)
Guideline and policy news
Miscellaneous
GRINCHIDICAE🎄 19:20, 1 December 2023 (UTC)
Got anything good? Tell us about your new, improved, old, or messed-up script
here!
Featured script
Updated scripts
Improve a script
Requested scripts
New scripts
CheckUser changes
Oversighter changes
Bureaucrat changes
Newly maintained scripts
.png)
.png)
Requested scripts
