Hello, thank you for reverting my edit and bringing my attention to the already present thread on the articles talk page which i didn't see as well as citing
WP:RSPSOURCES.
I hope you understand that i was simply trying to remove any potential bias in the article since Al-Jazeera, considering it is a state-owned media outlet, may very well hold prejudice in this topic.
Hjemt (
talk) 10:45, 2 March 2024 (UTC)reply
@
Hjemt. Sure, no problem at all. Let's see where the talk page discussion goes. –
Novem Linguae (
talk) 10:49, 2 March 2024 (UTC)reply
the West Bank is 110% illegally occupied. It's not "biased" on the part of Al Jazeera (far more reputable than any Israeli state media outlet) to say as much. Just so you got the memo.
2607:FEA8:A4E5:6A00:5CD1:3272:4C4D:E327 (
talk) 07:34, 3 March 2024 (UTC)reply
I think using that terminology reveals bias (taking a clear side on that controversial issue). That's fine though. Sources don't have to be 100% unbiased to be reliable. The media bias fact chart, for example, has two axes: reliability and left right bias. –
Novem Linguae (
talk) 10:37, 3 March 2024 (UTC)reply
Hi Novem Linguae, I've just added a couple sites (both reliable and unreliable) to
User:Novem Linguae/Scripts/CiteHighlighter/AllSourcesExceptNPPSG, it would be great if you could review my additions and update your script! The script has been super helpful reviewing articles, and I'm sure tons of editors agree. Thanks, TLAtlak 05:57, 4 March 2024 (UTC)reply
Nested template bug. Feel free to ping me from a non user talk page so the ping stays in my pingbox to remind me to work on this. I'll probably be busy until april. And the proper fix for this is probably to rewrite the script to use the parsoid api. –
Novem Linguae (
talk) 15:54, 6 March 2024 (UTC)reply
I've pinged you from the script talk page. Sounds like it can wait; I haven't seen this before so it must be rare.
Mike Christie (
talk -
contribs -
library) 15:59, 6 March 2024 (UTC)reply
Notification of administrators without tools
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
Also, two requests for the NovemBot, granted that you deem them reasonable and have a moment:
Could the bot possibly add something like {{Fa top}} & {{Fa bottom}} to promoted nominations? Consistency with the FA bot would be ideal—and I think the visual element makes it clearer if a conversation has ended.
Could the bot also put {{FC pass talk message}} on nominator talk pages? Although there's no template for GTs in this regard at the moment.
Again, these are super low-priority, so please no rush! Thank you again for all that you do here. Aza24 (talk) 02:47, 14 March 2024 (UTC)reply
Hey buddy. Just acknowledging that I've seen this. Will circle back to it when I'm less busy with work stuff. –
Novem Linguae (
talk) 17:48, 20 March 2024 (UTC)reply
Sounds good, thank you for your invaluable efforts. And again, no rush at all. Aza24 (talk) 00:08, 23 March 2024 (UTC)reply
Easy, let's knock these out, need some action on your side though:
{{Fa top}} & {{Fa bottom}}: Can you show me a diff please? Unclear which page you want this on and where exactly the two would go.
{{FC pass talk message}}: I think you'd need to fork this into its own template and make a few modifications, or modify the existing template to handle a "topic" parameter. Once this is ready, let me know and we can add this to the FGTC promotion work instruction and to NovemBot.
For the FA top and bottom I'm thinking of what the FAC bot does (
[1])—so this would be after pages are promoted, on the discussion page. Just seems like an archiving standard we ought to include; I imagine we'd be fine having it place {{Archive top}} and {{Archive bottom}}?
I'm currently discussing this was Sdkb. I think a new template is probably the route; although the current supports featured topics, it doesn't for good topics, as you allude to. And using the single-star icon for featured topics is a bit strange anyways. Will report back once progress is made on this template.
@
Aza24. I added the {{Archive top}}/{{Archive bottom}} feature just now. Can you run the bot on ONE regular topic (not an addition) so I can confirm the change? –
Novem Linguae (
talk) 09:46, 5 April 2024 (UTC)reply
@
Aza24. Let me know when you finish forking {{FC pass talk message}}, and I can get that added to NovemBot. Also let me know the next time you need a former topic re-promoted. That will give me a nice push to work on that feature. –
Novem Linguae (
talk) 10:48, 30 April 2024 (UTC)reply
Sounds good, thank you! There may be a delay with forking the template, I'm rather busy this May, but hopefully I'll get around to it early this summer. Aza24 (talk) 06:46, 5 May 2024 (UTC)reply
RFA2024 update: no longer accepting new proposals in phase I
Hey there! This is to let you know that phase I of the
2024 requests for adminship (RfA) review is now no longer accepting new proposals. Lots of proposals remain open for discussion, and the current round of review looks to be on a good track towards making significant progress towards improving
RfA's structure and environment. I'd like to give my heartfelt thanks to everyone who has given us their idea for change to make RfA better, and the same to everyone who has given the necessary feedback to improve those ideas. The following proposals remain open for discussion:
Proposals 3 and 3b, initiated by Barkeep49 and Usedtobecool, respectively, provide for trials of discussion-only periods at RfA. The first would add three extra discussion-only days to the beginning, while the second would convert the first two days to discussion-only.
Proposal 5, initiated by SilkTork, provides for a trial of RfAs without threaded discussion in the voting sections.
Proposals 6c and 6d, initiated by BilledMammal, provide for allowing users to be selected as provisional admins for a limited time through various concrete selection criteria and smaller-scale vetting.
Proposal 7, initiated by Lee Vilenski, provides for the "General discussion" section being broken up with section headings.
Proposal 9b, initiated by Reaper Eternal, provides for the requirement that allegations of policy violation be substantiated with appropriate links to where the alleged misconduct occured.
Proposals 12c, 21, and 21b, initiated by City of Silver,
Ritchie333, and
HouseBlaster, respectively, provide for reducing the discretionary zone, which currently extends from 65% to 75%. The first would reduce it 65%–70%, the second would reduce it to 50%–66%, and the third would reduce it to 60%–70%.
Proposal 13, initiated by Novem Lingaue, provides for periodic, privately balloted admin elections.
Proposal 14, initiated by Kusma, provides for the creation of some minimum suffrage requirements to cast a vote.
Proposals 16 and 16c, initiated by Thebiguglyalien and Soni, respectively, provide for community-based admin desysop procedures. 16 would desysop where consensus is established in favor at the
administrators' noticeboard; 16c would allow a petition to force reconfirmation.
Proposal 16e, initiated by BilledMammal, would extend the recall procedures of 16 to bureaucrats.
Proposal 17, initiated by SchroCat, provides for "on-call" admins and 'crats to monitor RfAs for decorum.
Proposal 25, initiated by Femke, provides for the requirement that nominees be extended-confirmed in addition to their nominators.
Proposal 27, initiated by WereSpielChequers, provides for the creation of a training course for admin hopefuls, as well as periodic retraining to keep admins from drifting out of sync with community norms.
To read proposals that were closed as unsuccessful, please see
Wikipedia:Requests for adminship/2024 review/Phase I/Closed proposals. You are cordially invited once again to participate in the open discussions; when phase I ends, phase II will review the outcomes of trial proposals and refine the implementation details of other proposals. Another notification will be sent out when this phase begins, likely with the first successful close of a major proposal. Happy editing!
theleekycauldron (
talk • she/her), via:
@
Novem Linguae, we have a reviewing crisis at Autoreviewing permission page, as more than 10 request are pending. I informed it AN. The last admin intervener has recently cleared two request after I notified at AN. Still many are left. Can you please help in clearing the backlog? ☮️Counter-Strike:Mention 269🕉️(
🗨️ ●
✉️ ●
📔) 01:15, 17 March 2024 (UTC)reply
I'm pretty busy this weekend. Maybe in the future. –
Novem Linguae (
talk) 03:34, 17 March 2024 (UTC)reply
Got bored again and added the Africa, Nigeria, South Africa Wikiproject sources. I believe I filled it all out correctly, would be super helpful if you could update the script again! Thanks :) TLAtlak 06:07, 20 March 2024 (UTC)reply
@
I'm tla. Looks good to me. I deployed the changes just now. Thanks for your work on this. –
Novem Linguae (
talk) 06:49, 20 March 2024 (UTC)reply
Hi. I just wanted to know the reason why you restored the page all over again. After a discussion in
this talk page it would be better to blank off this page completely. Keeping the LTA page in my opinion wouldn’t even help with
WP:DENY, as I might be worried that the vandalism would continue constantly if this were to happen. But in your opinion would it be better to leave the page alone or blank it completely. For me though it’s still better not to have an LTA page for this user. As if we were to have an LTA page it would get worse. kleshkreikne.T 08:06, 20 March 2024 (UTC)reply
Hey there. We have those LTA pages for a reason. I imagine that reason is to educate experienced editors and vandal fighters about our regular LTAs. Not much education will be taking place if the page is blank. Are you sure it is a good idea to be messing with these pages? Do you have enough experience to be blanking these LTA pages without discussion on the talk page? A quick perusal of
WT:LTA shows that the practice of blanking LTA talk pages is controversial, for example, the second comment in the section
Wikipedia talk:Long-term abuse#Archives AWB run. –
Novem Linguae (
talk) 08:15, 20 March 2024 (UTC)reply
So one of my fellow editors who was the one who dealt with the MRY thing decided to blank the whole thing off because of
WP:DENY. You should take a look at
WP:LTA/MRY to see why he blanked it on purpose. For me though I think it might’ve been guaranteed, but it didn’t work. Every LTA is different. You should leave a message on the one who blanked the whole LTA page as to why it’s not worth it. I’m not trying to be mean to the vandal but I just wanted to prevent additional disruption from taking place, so I had to blank it. kleshkreikne.T 08:45, 20 March 2024 (UTC)reply
Hard to believe you've only been editing for three weeks. Most editors don't even know about LTA pages. LizRead!Talk! 20:15, 24 March 2024 (UTC)reply
Maybe they were inspired by
this video (overview of LTAs on WP) to join? Aza24 (talk) 02:54, 25 March 2024 (UTC)reply
Sure. Will take a look in the next two days hopefully. Sorry I'm not doing it quicker. Will likely take a lot of brainpower to make all these NovemBot changes. –
Novem Linguae (
talk) 20:22, 24 March 2024 (UTC)reply
Notification of administrators without tools
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
I actually would love to take
User:Celestina007/Mailinglist/WP NIGERIA (a list compiled by a very proficient user who later left), to this page I mentioned above, don't know if it makes sense to just move it there, or better, change the content model of this one to Mass message delivery list.
Vanderwaalforces (
talk) 00:28, 30 March 2024 (UTC)reply
Hey @
Vanderwaalforces. I don't think we should move it from out of someone's userspace without permission. I'll change the content model and copy paste the contents for you. That should do the trick I think :) –
Novem Linguae (
talk) 03:08, 30 March 2024 (UTC)reply
Great! I see you’ve done it. Thank you so much.
Vanderwaalforces (
talk) 06:01, 30 March 2024 (UTC)reply
NPP Newsletter
Hello Novem, I hope you are doing well. I'm sorry to bother you with this message, but I just wanted to ask if you had a chance to review the newsletter draft. If not, there's no rush; I simply wanted to send a gentle reminder. Feel free to ignore this message. –
DreamRimmer (talk) 16:33, 30 March 2024 (UTC)reply
Thanks. I made some edits just now. Can you check with me in a couple days for a final approval? That'll give time for another round of polishing. –
Novem Linguae (
talk) 17:04, 30 March 2024 (UTC)reply
Sure. It looks great after your edits. Thanks for polishing it up. –
DreamRimmer (talk) 17:09, 30 March 2024 (UTC)reply
The NPP newsletter has been sent successfully. Could you please merge this
draft's edit history into
Wikipedia:New pages patrol/Newsletter/Archive/34? I accidentally copy-pasted content into the archive without moving the draft. Thanks in advance! –
DreamRimmer (talk) 16:59, 2 April 2024 (UTC)reply
I G6'd the new archive 34 and moved the draft to 34, preserving the history. Should be all fixed. –
Novem Linguae (
talk) 20:28, 2 April 2024 (UTC)reply
Hey there, just fyi, it's now the third (similar) IP address making the same edits to the page on Ursula von der Leyen. Not that I think they are being malicious past being outraged and not fluent in the language, but I wanted to make sure you were aware. Similar edits, by similar IPs, have been rejected at the corresponding German page as well.
JackTheSecond (
talk) 10:02, 3 April 2024 (UTC)reply
Will keep this in mind. Thanks for the info. If they keep it up, may need a
WP:RFPP. –
Novem Linguae (
talk) 10:08, 3 April 2024 (UTC)reply
Notification of administrators without tools
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
I try to be polite. At least for now! :P –
Novem Linguae (
talk) 20:40, 8 April 2024 (UTC)reply
GoldenRing
Not sure how you define "last few years", but the
2017 GoldenRing RfA is imprinted into my memory. He had 2385 edits over 12 when he ran. It was an absolute stunner of a successful RfA. I'm posting here as I don't want to give TheTechie any wrong ideas. Schwede66 08:05, 11 April 2024 (UTC)reply
Good info, thank you. I think RFA culture has changed since 2017 though. No offense to GoldenRing, and I could be wrong, but I don't think he could pass in today's RFA culture. Also 88 opposes is brutal, so even if someone could pass with 2k edits, I'd still advise against them running so that they don't have a bad RFA experience. Hope that makes sense. –
Novem Linguae (
talk) 08:59, 11 April 2024 (UTC)reply
Topic Ban
Could you please elaborate on what evidence that was presented that could possibly justify the topic ban you have imposed. There was a loud chorus of a group of editors calling for a sanction, who repeatedly restored the topic after it was archived. They presented accusations but didn't present any evidence to support those allegations. All were the same editors in a content dispute on Tim Hunt.
[2] My contribution history on
Tim Hunt. 100% of it reverted. 0.7% of all contributions on the article.
Note: {{npov}} tag added 13 March 2024, single revert to restore. 25 March 2024 - one single edit adding context and information in
WP:RS per
WP:NPOV.
Note: 13 March 2024 - comment on NPOV tags, 17 March 2024 - Further comment, 25 March 2024 - Comment on revert of my contribution. I had not made any comment in talk since 12th February.
Since 12th February, I've made 3 comments in talk, 1 contribution to the article in total. This is hardly the actions of someone who can't drop the stick.
I was accused of forum shopping, I raised the issue once when {{npov}} tags were being removed by edit warring. Didn't reply for nearly a week, didn't rise to the bait of edit warring.
Only one editor made an accusation of not assuming good faith seemingly supported by a diff. That took a talk quote taken out of context, which was a response to
[4], where the editors responsible for the RFC indicate they do not feel the need to respond to the closer's comments. Reference to misogyny is not my comment but for example
[5]he's just another misogynist.
I don't accept that a topic ban was justified. No evidence was presented, mere accusations of involved editors are not sufficient to justify action; I presented clear evidence those accusations were unjustified. I have already given up editing the article because of the toxic nature of the discussion, have no intention of returning but an unjustified broadly construed topic ban would prevent me from writing in other areas. I am asking you to reconsider your decision, in the light of the lack of any evidence of misconduct. WCMemail 12:47, 11 April 2024 (UTC)reply
Hey there. Thank you for your message, and I again apologize that I was the bearer of bad news.
I believe the job of a discussion closer is to summarize the discussion (with some caveats, of course, such as discarding sockpuppet comments and comments that do not comply with policy, downweighting comments that are unconvincing or don't make sense, etc.), and I can see no other way to summarize that discussion than a consensus to topic ban. Anything else, in my opinion, would be supervoting. The consensus of the discussion was very clear.
I spent about an hour closing the discussion, and another hour preparing this reply, and I am confident from the reading I did during these two activities that your behavior in the topic area bothered your fellow editors, caused friction that affected the collegial atmosphere, and should be adjusted.
I believe it's OK to un-archive a section that needs closure. The community took the time to opine on the issue, and I believe they should be able to have a conclusion to that process.
If we define involved as "participated in the RFC", then the following 3 editors who commented at the ANI were uninvolved: Lavalizard101, Aquillion, and Star Mississipi. Looks like the ANI did receive some non-involved participation, which is great. It appears these three did not choose to oppose the topic ban.
I'm sorry I can't accept your response and have requested a review at
WP:AN. Expressing legitimate concerns ref a
WP:BLP as mildly as I did should not engender the hostile response from those editors that it did. The collegial atmosphere was not disturbed by what I said, I'd entered an already toxic atmosphere where editors had adopted fixed positions, which is why I chose to disengage. As another editor noted I believe there are legitimate BLP concerns as well about the Hunt article, but after seeing the way Thomas B has been treated in this whole shameful debacle, I'm afraid to say anything for fear of proposals like this being thrown my way. There was no real community input and if you can be topic banned for 4 edits, none of which violated any wiki norm you've created a chilling editing situation where mob rules apply. WCMemail 15:52, 11 April 2024 (UTC)reply
Please be careful of
WP:BOOMERANG. By posting at AN, you're probably engaging in the same behaviors that I talked about in the ANI close (WP:DROPTHESTICK, WP:FORUMSHOPPING, and consuming large amounts of editor time).
With that said, I don't mind my actions being reviewed and I do not take it personally. I respect your decision. Good luck. –
Novem Linguae (
talk) 15:58, 11 April 2024 (UTC)reply
Hi Novem Linguae, I feel I owe a bit of explanation here. I feel that the freedom to be able to discuss is of paramount importance in Wikipedia. Without it, we are nothing, no article can change. I agree with your evaluation of the consensus to sanction WCM. But lynch mobs also have a strong consensus to sanction their victims. What I saw in ANI, both against Thomas B at the outset, and then with WCM, was a gerrymandering, bullying mob out to suppress something they didn't want to hear. And that is both unkind and an offence to freedoms for which many have fought. It is not in keeping with the spirit of the Wikipedia I once knew, and wanted to be part of. And for that reason I have retired permanently.
92.31.246.75 (
talk) 17:51, 12 April 2024 (UTC) (formerly Elemimele; I no longer have the use of my account)reply
Hi Elemimele. So sorry to hear that you retired over this. This dispute primarily seems to be about 1) the # of paragraphs in an article, and 2) knowing when fellow editors have had enough and are getting really annoyed. In theory, simple things that are easily fixable. But I guess not so simple in this case, eh? Your "side" seems to feel very strongly about what is happening to Tim Hunt's reputation and mental health, and its intersection with BLP. And the other "side" feels strongly about Wikipedia's philosophy to report on matters in proportion to how much they are reported in reliable sources. It's a tricky situation. Not sure if my words here help, but you deserve a full reply, so this is my attempt at it. Thank you for visiting my talk page and for your contributions to Wikipedia. Be well. –
Novem Linguae (
talk) 20:15, 12 April 2024 (UTC)reply
I could I suppose take the time to explain how your comments were overly simplistic to the point of coming across as asinine, infantile and patronising. However, I sense that would be futile and instead I'll simply note that editors expressing concerns about the article were dismissed as misogynists circling the wagons to protect another misogynist and you've literally handed ownership of the article to them. It wasn't a tricky situation but its one that needed someone with the moral courage to do the right not the easy thing. Instead you sided with the gerrymandering, bullying mob and I sit here and realise with great regret that Wikipedia is no longer a project that I can support because it doesn't reflect the values it espouses. WCMemail 18:25, 13 April 2024 (UTC)reply
Hi, I haven't been monitoring this since I've retired. I just wanted to correct something: there was no "your side" about this; I wasn't on any particular side, and was quite prepared to give an opinion on the article and walk away. I left because bullying behaviour and harassment have no place in a collaborative project, or any decent society. I watched this sort of behaviour being condoned, and actively facilitated at ANI, and had to ask myself some harsh questions on whether it is ethically appropriate to belong to a group of people who accept it? The answer, after a painful weekend of careful thought, was resoundingly "No", so I left.
149.155.219.44 (
talk) 13:18, 1 May 2024 (UTC) (formerly Elemimele, but locked out of my previous account! Not socking, honest!)reply
Why ARBECR all my comments?
You recently closed all my discussions on a talk page (
Talk:2024_Israeli_bombing_of_the_Iranian_embassy_in_Damascus) for not being extended-confirmed. The
WP:ARBECR page pretty clearly says that non-ECP users should still be allowed to contribute to the talk page unless they're being disruptive, which I wasn't. What's the deal here?
Amyipdev (
talk) 01:03, 12 April 2024 (UTC)reply
Hey @
Amyipdev. Thanks for the message. If you read
WP:ARBECR carefully, it essentially says that you can only use talk pages to make edit requests. You'll notice I didn't close the section where you made your edit request, but I did close the parts where you were not making an edit request. I hope that makes sense. –
Novem Linguae (
talk) 02:01, 12 April 2024 (UTC)reply
Something I noticed regarding this is that the instructions on that talk page are different than the ones on
Talk:Flour massacre. The former uses {{Contentious topics/talk notice|a-i}} whereas the latter uses {{ArbCom Arab-Israeli enforcement}}, which is more expansive and includes the instructions for non-EC to only make edit requests --
Gimmethegepgun (
talk) 10:02, 15 April 2024 (UTC)reply
Past issues with the citation bot
Just wanted to inform you, no action is needed.
I refer to the discussion at link in which you and
User:Hey man im josh participated.
I had past issues with the citation bot that the version at
https://citations.toolforge.org/ had bugs so I did run the bot from my account and it caused pollution of watchlist, and I was blocked for 1 hours and then it was an ANI but since that I contributed on Github to resolve the issues I had (mostly timeouts due to bad DOIs), and the author of the bot
User:AManWithNoPlan was very responsive, and now I mostly run the bot from
https://citations.toolforge.org/ that is a bot account and it resolves all the issues that happened for me in the past. Using the bot from
https://citations.toolforge.org should prevent recurrence of the the past troubles I had. When an editor will not like a particular behaviour (such as replacing {{Cite}} to {{cite}}, this will be compensated by consensus achieved via a bot feature approval process (although it may be a bad example as I never asked for such replacement to be approved, and I don't do these replacement any longer)). So following the right process is almost always a recipe for success. I am sorry that I did not follow the correct process from the beginning.
Maxim Masiutin (
talk) 11:56, 21 April 2024 (UTC)reply
No problem. Sounds like it's all resolved now. Thank you for the message. –
Novem Linguae (
talk) 08:48, 22 April 2024 (UTC)reply
Notification of administrators without tools
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
Hey, Novem Linguae. I hope this message finds you well.
You may remember that some time ago, you helped me on
VPT about my
user script. My user script is intended to make the lives of Wikipedians easier. As such, I would like some recommendations for features to implement in my user script. You can see the current (two) features
here. Please leave any feature requests for features that would help Wikipedians
here. Thanks! thetechie@enwiki:
~/talk/$ 22:04, 25 April 2024 (UTC)reply
... but re:
this edit, I think those were meant to be replies. In my read, the first is a reply to a call for a reblock, and the second is an endorsement of the reblock. Best, — Usedtobecool☎️ 10:46, 28 April 2024 (UTC)reply
Sounds good. I self reverted. Thanks for being nice about it. –
Novem Linguae (
talk) 11:35, 28 April 2024 (UTC)reply
Hey, do you have any idea why the bot isn't promoting the
Avengers films GT? It was marked for promotion last night. Is it because I moved the page of the nomination early in the process to change the name? -- ZooBlazer 16:52, 29 April 2024 (UTC)reply
@
ZooBlazer. Fixed. Sorry for the trouble. It was a bug unrelated to anything on your side. It wouldn't be a bot if it didn't break all the time ;-) –
Novem Linguae (
talk) 08:52, 30 April 2024 (UTC)reply
Yapperbot, your bot essay, etc.
Thanks for
this edit on your essay. I'm going to start working on Yapperbot adoption related issues again--been distracted by other Wiki matters--and was just re-reading your essay. I'm a bit surprised my request stalled
here. Before I ramp up again, I welcome any new thoughts about moving forward, either here or in one of the other places we have talked... --
David Tornheim (
talk) 04:46, 30 April 2024 (UTC)reply
(Not Novem) @
David Tornheim AFAIK yapperbot's directory is readable (should be /data/project/yapperbot). BY the looks of it, the directory only contains executables and no actual code. It might be more reliable/easier to redeploy the code based on the github project you allude to in the task.
Sohom (
talk) 04:58, 30 April 2024 (UTC)reply
Actually looking at it further, for yapperbot, you need three repositories
yapperbot-frs for the feedback request service,
yapperbot-pruner for the pruner service and
yapperbot-scantag for the scantag service. If you compile these repositories and set these up on a test toolforge instance, they should theoretically (emphasis on theoretically) work.
Sohom (
talk) 05:21, 30 April 2024 (UTC)reply
Noting that you should point the bots to test.wikipedia.org and no en.wikipedia.org for obvious reasons :)
Sohom (
talk) 05:28, 30 April 2024 (UTC)reply
@
Sohom Datta: Thanks for the feedback. Yes, I'm aware of all that--especially all the github code which I have spent plenty of time studying. (Although I don't remember "scantag" service--I'll look at that.) I did set up a copy of the code already, but I would like data for the *actual* config files--not the ones on github. And they were protected the last time I checked. I could give you a list. Possibly someone unprotected them but didn't inform me. I will look at the directories again. --
David Tornheim (
talk) 07:49, 30 April 2024 (UTC)reply
@
David Tornheim They don't appear to viewable at this moment. I've asked on phab, but I wonder if it would be possible to reconstruct those config file based on the code you already have?
Sohom (
talk) 19:15, 30 April 2024 (UTC)reply
I think the SREs (taavi) is worried that those files might contain secrets like passwords that would allow you to access yapperbot's account.
Sohom (
talk) 19:16, 30 April 2024 (UTC)reply
@
Sohom Datta: It's a reasonable concern. I believe I can prove that is not the case, as the password file is easy to find in the code. I'm not looking at the code right now, but I can dig into it and explain. Thanks for friending me on Discord. Do you know Go? I might have more questions later. I believe I understand the gist of how the code works, but using bots, the API, Toolforge, etc. are new to me. I can point you to the discussion of where we talked about adoption on here so you know my programming background. It sounds like you have experience with bots.--
David Tornheim (
talk) 01:59, 1 May 2024 (UTC)reply
P.S. I see you are an intermediate Go programmer. Nice. One of the few! :) I could have used your advice earlier, when I had trouble with modules downloading correctly. I believe that problem is taken care of.--
David Tornheim (
talk) 13:00, 1 May 2024 (UTC)reply
@
David Tornheim I'm pretty familiar with the basics of golang, and I do work on bots (albiet I don't think I've seen a golang bot), toolforge and mediawiki in general, feel free to ping (on Discord or onwiki) if you need any help anytime :)
Sohom (
talk) 00:50, 2 May 2024 (UTC)reply
@
Sohom Datta: Thanks for your offer to help! And thanks for backing me up on that thread. I might dig into the code again tonight to show what parts open the config files vs. which code uses the password file.
One of the editors said I could redo the code in any language if I wanted, but I don't see any reason to do that--"if it ain't broke; don't fix it". However, I admit I thought it was strange that Naypta chose a language that probably few Wikipedians would know rather than languages like Php, Python, Perl, etc.--especially given that he wasn't going to stick around to maintain it.
So I am curious if you think Go adds anything meaningful in terms of ease of use or functionality to the ever-expanding list of programming languages. And over the long-term--for maintenance purposes--would it be better if the code is converted into a language more editors know? I do like Go's use of modules and the simplicity/elegance compared to the equivalent in C (and probably many other strongly typed languages), but other than that, I haven't seen anything else remarkable about it. I figured Naypta might have just learned it, thought it was novel, and wanted to try it out. Even though I spoke at length with him when he released Yapperbot, I was too busy with other question that I don't think I asked him. So I am curious why you became interested in the language. Maybe it is more popular than I think? I have looked at
Go FAQ: What is the purpose of this project?'. --
David Tornheim (
talk) 06:56, 2 May 2024 (UTC)reply
A barnstar for you!
The Technical Barnstar
For your work on the various tools recently - much appreciated :)
KylieTastic (
talk) 11:21, 30 April 2024 (UTC)reply
Thanks. It's been fun to explore and tune up this old tech. –
Novem Linguae (
talk) 11:37, 30 April 2024 (UTC)reply
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the
voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please
review the U4C Charter.
Please share this message with members of your community so they can participate as well.
RFA2024 update: phase I concluded, phase II begins
Hi there! Phase I of the
Wikipedia:Requests for adminship/2024 review has concluded, with several impactful changes gaining community consensus and proceeding to various stages of implementation. Some proposals will be implemented in full outright; others will be discussed at phase II before being implemented; and still others will proceed on a trial basis before being brought to phase II. The following proposals have gained consensus:
See the
project page for a full list of proposals and their outcomes. A huge thank-you to everyone who has participated so far :) looking forward to seeing lots of hard work become a reality in phase II.
theleekycauldron (
talk), via
MediaWiki message delivery (
talk) 08:09, 5 May 2024 (UTC)reply
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
Greetings, Novem Linguae. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
I see you're involved in maintaining Twinkle, so I'm hoping you will know the answer to this; do you know if there is a way using the API/morebits to move a page and delete the page currently at the target, aside from sending a separate request to delete the page?
My understanding is that it is not but I am hoping I am wrong, as I'm trying to fix a bug with the rmCloser script where it can't overwrite pages even when the user is a pagemover.
BilledMammal (
talk) 01:57, 17 May 2024 (UTC)reply
Strangely I am not very familiar with Morebits because I mostly do bug fixes and small patches so haven't had an occasion to explore it in depth yet. @
SD0001 could probably answer this question easily though. –
Novem Linguae (
talk) 02:06, 17 May 2024 (UTC)reply
I don't think that's possible to do in a single request using the API. That's something only the special page allows. –
SD0001 (
talk) 03:29, 17 May 2024 (UTC)reply
@
SD0001: I thought so, but I had hoped otherwise; thank you all the same.
Solving this for admins won't be an issue - it will just require an additional API call to delete the page before moving the article, but that won't work for pagemovers as they lack access to the delete API. Do you know if there is a way to delete redirects through the API without using delete? Again, my understanding is that there is not, but I'm hoping I'm wrong as alternative solutions will be messy.
BilledMammal (
talk) 03:56, 17 May 2024 (UTC)reply
I'm not concerned about the double API call; my issue is I don't think there is an API call for "delete-redirect".
BilledMammal (
talk) 04:46, 17 May 2024 (UTC)reply
Oh. I think that's built into the move API. I think the algorithm is that any editor can move a page over a redirect if 1) the redirect only has one revision and 2) it is pointing at the current title. And any editor with `delete-redirect` (page movers and sysops) can move a page over a redirect 1) if it only has one revision. The best way to find out is probably to test it. –
Novem Linguae (
talk) 04:54, 17 May 2024 (UTC)reply
Unfortunately, I've been testing it and I don't think that it is there, unless there is a configuration option not documented at the
API page.
BilledMammal (
talk) 05:01, 17 May 2024 (UTC)reply
Test results
Perm
Edited via
Action
Result
Admin
Website
Move over a one revision redirect pointing back to the original page
Y
Admin
Action API via Special:ApiSandbox
Move over a one revision redirect pointing back to the original page
Y
Logged in user
Website
Move over a one revision redirect pointing back to the original page
Y
Logged in user
Action API via Special:ApiSandbox
Move over a one revision redirect pointing back to the original page
Could you try moving over a one revision redirect pointing at a different page?
With that said, I've now developed a function that uses the method at
Special:MovePage to allow this - I would like to replace it with something cleaner, but it isn't an issue if it's not possible.
BilledMammal (
talk) 06:47, 17 May 2024 (UTC)reply
Can you open a phab ticket requesting the ability to do this through the API? Letting page movers overwrite redirects not pointing back to the current page is a relatively recent feature, so allowing it via the API was likely just overlooked rather than intentionally left out. –
SD0001 (
talk) 12:43, 17 May 2024 (UTC)reply
Move over a one revision redirect pointing to a different page
Y Asks you if you want to delete the page, then you have to tick the box "Yes, delete the page". This shows up both when it's a regular page and when it's a redirect. This shows up both for one revision pages and multiple revision pages.
Admin
Action API via Special:ApiSandbox
Move over a one revision redirect pointing to a different page
N tried it both with ignorewarnings=true and ignorewarnings=false
Page mover / delete-redirect
Website
Move over a one revision redirect pointing to a different page
Y Asks you if you want to delete the page, then you have to tick the box "Yes, delete the page". Only shows up for redirects. Only works for one revision redirects.
Page mover / delete-redirect
Action API via Special:ApiSandbox
Move over a one revision redirect pointing to a different page
N tried it both with ignorewarnings=true and ignorewarnings=false
Logged in user
Website
Move over a one revision redirect pointing to a different page
N
Logged in user
Action API via Special:ApiSandbox
Move over a one revision redirect pointing to a different page
N
I think I understand your question and your confusion now. The page move webpage lets admins always overwrite pages, and the page move webpage lets page movers overwrite pages under certain circumstances, whereas the move API never lets this happen unless the page is a one revision redirect pointing at the page attempting to be moved. See results above. I think you'll definitely need two API queries for all situations except the situation where there is a one revision redirect pointing at the page attempting to be moved. I hope you find these test results as interesting as I did :) –
Novem Linguae (
talk) 08:36, 17 May 2024 (UTC)reply
With the website, try moving a page to a title where the title has no article, but the talk page has a single-edit redirect to a page other than the talk page of the article you are moving. If I am correct, you will be able to overwrite the page as an admin, but you will not be able to do so as a page mover.
BilledMammal (
talk) 14:56, 19 May 2024 (UTC)reply
You are in absolutely no way obliged to take this on, but it seems in your realm of expertise and interest...
Would you be interested in adding inline tagging to semi-automated tools? Evidence suggests it could significantly increase new editor retention (especially if tags replace reverts). Enterprisey was interested in taking it up, in
a discussion a while back. There's a related Huggle ticket,
T209797 (currently also mentioned on
WP:MED).
Separately, thank you for all the infrastructure work you've done. I'm sure I won't use it all directly, but I'll benefit from it indirectly, all the same.
HLHJ (
talk) 04:09, 19 May 2024 (UTC)reply
Hey. Thanks for the message. Did you have specifics in mind? Which tool, what feature to add, etc? –
Novem Linguae (
talk) 05:09, 19 May 2024 (UTC)reply
Thanks for the query, and sorry I've been so slow to reply.
Honestly, I don't mind which tool. The phab ticket is for Huggle, but I think the functionality is more important than how it is implemented. I'm also quite sure you'd know better than I where it would be most useful, and easiest to implement.
The simplest feature would be: when patrolling edits, IF the edit being reviewed is the addition of a single block of text, THEN have a button which adds just the citation needed point tag (not span tag) to the end of edit.
The "Basic design ideas" section in the phab ticket has a longer list (~removing the qualifications in the last sentence). These would probably be rarer use cases, tho.
HLHJ (
talk) 00:20, 24 May 2024 (UTC)reply
You could ask for a user script that does this by posting at
WP:US/R. The user script could add an [add CN] link on the recent changes, watchlist, and/or diff screens when the diff meets the parameters you described. –
Novem Linguae (
talk) 01:44, 24 May 2024 (UTC)reply
Thanks, I'll look into this.
HLHJ (
talk) 15:00, 24 May 2024 (UTC)reply
Report spam links on enwiki
Hi Novem Linguae, long time no see. I would like to ask where I can report spam links on enwiki. I noticed a
subtle edit adding an advertisement link that went undetected for months (please see the last link in the edit). Thank you.
Plantaest (
talk) 19:14, 24 May 2024 (UTC)reply
Hi Novem - just wanted to say thanks for the kind statement on the arbitration request page earlier - I was getting a bit stressed and worried over the implications of some of the things being said there - especially on that page because I don't really understand what's happening but it all feels very important. Feels a bit like being summoned into an alien courtroom. It was all a bit daunting, and your message made me feel a bit better about the situation. Again, just wanted to say thanks
BugGhost🪲👻 18:08, 27 May 2024 (UTC)reply
You're welcome. Yeah, careful of participating in places like the administrators notice board and anything with the word arbitration in it. It is easy to unintentionally get in the middle of drama in those places. –
Novem Linguae (
talk) 21:27, 27 May 2024 (UTC)reply