User talk:Ad Orientem/Archive 24
This is an archive of past discussions with User:Ad Orientem. 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. |
Archive 20 | ← | Archive 22 | Archive 23 | Archive 24 | Archive 25 | Archive 26 | → | Archive 29 |
Your user rights
Hi, Ad Orientem. You've recently added yourself to some new user groups (149639144, 149639158), but the rights that they afford should be included with your administrative abilities. Were you experiencing an issue with your mop access? Sdrqaz (talk) 05:25, 24 July 2023 (UTC)
- @Sdrqaz A family member is gravely ill and there is a possibility I may have to travel north for a period of time during which I would have limited access to the internet and might not be able to respond to admin related queries in a timely manner. In that event I likely would hand in the bit until I return. As of right now that trip is looking a bit less likely, but still possible. But if it does happen I may sporadically pop in and do some editing as circumstances permit. -Ad Orientem (talk) 14:02, 24 July 2023 (UTC)
- Goodness. I'm sorry to hear that, Ad Orientem. Take as much time out as you need. I think that as an administrator, I frequently feel that I have an obligation to stay active even when I shouldn't. Our personal life is what truly matters – I hope that you find some peace in this troubling time. Sdrqaz (talk) 07:07, 25 July 2023 (UTC)
Discussion moved
I recently pinged you at Wikipedia:Village pump (technical). The discussion has now been moved to Wikipedia:Administrators' noticeboard#Massive wide-ranging IP block on Airtel India users. JBW (talk) 17:26, 25 July 2023 (UTC)
- Thank you. Alas I have little to add to the points already made at the discussion. -Ad Orientem (talk) 01:10, 26 July 2023 (UTC)
ITN recognition for 2023 Israeli judicial reform protests
On 26 July 2023, In the news was updated with an item that involved the article 2023 Israeli judicial reform protests, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. – filelakeshoe (t / c) 🐱 09:00, 26 July 2023 (UTC)
IP editing
I think 12.190.236.70 (talk · contribs · WHOIS) is a sock of 24.208.226.69 (talk · contribs · WHOIS), based on behavioural evidence. I'd go to SPI, but that seems a dead end right now... Urbanoc (talk) 13:03, 26 July 2023 (UTC)
- @Urbanoc IP blocked and page protected x 1 month. -Ad Orientem (talk) 13:26, 26 July 2023 (UTC)
regarding user:Jetstreamer
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
This user has consistently removed the source I mentioned from aviation-related articles without once ever providing a valid reason for labeling it a bad source. This is a waste of my and other editor’s time, as we must spend our time restoring it as a source. Jetstreamer constantly links to a previous discussion that has no consensus on the matter. I’m not sure what it is in your power to do, but something would be helpful here. SurferSquall (talk) 06:27, 27 July 2023 (UTC)
- (talk page watcher) Planespotters.com is not a reliable source, as it uses user-submitted content, per WP:SPS. You need to stop edit warring about this issue. If you still believe it to be a reliable source, you can make your case at WP:RSN, and allow the community to review it and decide if it is reliable. BilCat (talk) 07:16, 27 July 2023 (UTC)
- The only user-submitted content on Planespotters is the photos, which have nothing to do with the information in question. SurferSquall (talk) 19:10, 27 July 2023 (UTC)
- @SurferSquall Please take this discussion to the appropriate talk page. Thank you. -Ad Orientem (talk) 19:16, 27 July 2023 (UTC)
- The only user-submitted content on Planespotters is the photos, which have nothing to do with the information in question. SurferSquall (talk) 19:10, 27 July 2023 (UTC)
- A discussion about this incident is current here. I'd suggest that any further comment be made there. — Cheers, Steelpillow (Talk) 08:41, 27 July 2023 (UTC)
- @BilCat @Steelpillow @SurferSquall @Jetstreamer This looks like a content dispute involving a question over sourcing. I see no need at present for any admin involvement beyond a general reminder to avoid edit warring. Discuss and seek consensus. See the linked discussion above. -Ad Orientem (talk) 18:54, 27 July 2023 (UTC)
2A01:B747:150:344:0:0:0:0/64
2A01:B747:150:344:0:0:0:0/64 (talk · contribs · WHOIS)
Could you look at this IP range's edits again and block if necessary? They continued to vandalize after your previous 3-month block expired not too long ago. Thank you. 2601:1C0:4401:F60:60E5:D67:4438:4F5E (talk) 18:35, 29 July 2023 (UTC)
- Blocked x 6 months. -Ad Orientem (talk) 21:16, 29 July 2023 (UTC)
Other British monarch requested move discussions currently taking place
Since you recently participated in the Charles III requested move discussion, I thought you might like to know that there are two other discussions currently going on about other British monarch article titles here and here. Cheers. Rreagan007 (talk) 22:25, 30 July 2023 (UTC)
New redirect
Hello, I am trying to make Draft:Boeing 747-400BDSF << this redirect but I can't, can you make it please? Thank you RedundancyAdvocate (talk) 18:37, 1 August 2023 (UTC)
- @RedundancyAdvocate I have modified the draft so it is now a redirect. If this is what you wanted, feel free to move it into the mainspace. -Ad Orientem (talk) 18:57, 1 August 2023 (UTC)
- @RedundancyAdvocate Actually I just realized that as a new user you may not be able to create new pages in the mainspace yet. I have taken the liberty of doing this for you. Your redirect can be found at Boeing 747-400BDSF. Welcome to Wikipedia and happy editing. -Ad Orientem (talk) 19:05, 1 August 2023 (UTC)
- Thank you, i couldn’t move it to a main article RedundancyAdvocate (talk) 20:07, 1 August 2023 (UTC)
- @RedundancyAdvocate Actually I just realized that as a new user you may not be able to create new pages in the mainspace yet. I have taken the liberty of doing this for you. Your redirect can be found at Boeing 747-400BDSF. Welcome to Wikipedia and happy editing. -Ad Orientem (talk) 19:05, 1 August 2023 (UTC)
GayAbuFath (talk · contribs)
Was this supposed to be an indefinite block? Looks like a throwaway vandalism-only account (you blocked for 1 month). 2601:1C0:4401:F60:98B0:35FC:6D58:1B65 (talk) 05:04, 5 August 2023 (UTC)
- Yes, it was. Thanks for the heads up. -Ad Orientem (talk) 05:09, 5 August 2023 (UTC)
Hi, I see that this user is blocked for a lot of Finnish articles. Could you please watchlist Raimo Olavi Toivonen? I suspect they are going to have to be blocked from this article too, though so far they have made only one edit. Skyerise (talk) 12:14, 6 August 2023 (UTC)
- @Skyerise I will try to check on it now and then. But I have more then 10,000 pages watchlisted so not sure how effective that will be. If you see any further disruption drop me a line. -Ad Orientem (talk) 13:02, 6 August 2023 (UTC)
- Understood. I try to keep mine at no more than 1,000. Skyerise (talk) 13:04, 6 August 2023 (UTC)
- Looks like he's going to be a problem. Has reverted twice more. Skyerise (talk) 17:50, 6 August 2023 (UTC)
- Also, may be connected to this puppetmaster. Skyerise (talk) 17:52, 6 August 2023 (UTC)
- @Skyerise I've added the page to the rangeblock. -Ad Orientem (talk) 19:26, 6 August 2023 (UTC)
- Thanks! Skyerise (talk) 19:27, 6 August 2023 (UTC)
- @Skyerise I've added the page to the rangeblock. -Ad Orientem (talk) 19:26, 6 August 2023 (UTC)
Administrators' newsletter – August 2023
News and updates for administrators from the past month (July 2023).
Interface administrator changes
- The tag filter on Special:NewPages and revision history pages can now be inverted. This allows hiding edits made by automated tools. (T334338)
- Special:BlockedExternalDomains is a new tool that allows easier blocking of plain domains (and their subdomains). This is more easily searchable and is faster for the software to use than the existing MediaWiki:Spam-blacklist. It does not support regex (for complex cases), URL path-matching, or the MediaWiki:Spam-whitelist. (T337431)
- The arbitration cases named Scottywong and AlisonW closed 10 July and 16 July respectively.
- The SmallCat dispute arbitration case is in the workshop phase.
182.4.64.0/18
Sorry, meant to report 182.4.96.0/19, not 182.4.64.0/18. The other half of that range seems unrelated (different geolocation even). Suffusion of Yellow (talk) 18:48, 8 August 2023 (UTC)
- @Suffusion of Yellow Thanks. I will narrow the range. -Ad Orientem (talk) 18:49, 8 August 2023 (UTC)
- Done. -Ad Orientem (talk) 18:51, 8 August 2023 (UTC)
That registered editor you just blocked...
You should have a look at 2024's response to being blocked. –Skywatcher68 (talk) 01:19, 22 August 2023 (UTC)
- @Skywatcher68 I have replied and revoked their TPA. If this continues I will protect the article. -Ad Orientem (talk) 01:59, 22 August 2023 (UTC)
Three user names will be blocked on History of vehicle registration plates of the Philippines article.
Following the review of article timeline edits of History of vehicle registration plates of the Philippines. Here's the following usernames that using Filipino language typos on English Wikipedia under "How do you improve the article?" section:
As pending on the timeline of History of vehicle registration plates of the Philippines article. Three users will be permanently blocked due to Filipino language typed in input on English Wikipedia article. Jon2guevarra (talk) 22:17, 22 August 2023 (UTC)
- @Jon2guevarra Not sure what the above post is. Is this an informational post, or are you asking for some specific admin action? I took a look at their respective contrib logs and have blocked Khyan_Jewel_Cacapit x 48 hrs for disruptive editing. The other two have not edited recently and so a block is not justified. I also note that User:Daniel Case has protected the page History of vehicle registration plates of the Philippines x 6 months, which is entirely justified given the long record of disruption. Hopefully this will put the brakes on (pun intended) the problematic editing there. -Ad Orientem (talk) 22:56, 22 August 2023 (UTC)
Missing protection template
The protection lock template is missing from 2023 Tver plane crash, please add it. Thank you SurferSquall (talk) 19:07, 23 August 2023 (UTC)
- Note that User:MusikBot II will automatically add the appropriate template if one isn't adding manually. -- Ponyobons mots 19:10, 23 August 2023 (UTC)
- I thought it important as it's got pretty high edit traffic right now SurferSquall (talk) 19:17, 23 August 2023 (UTC)
- Understood; I just mentioned it in case you thought it would be left without a template in perpetuity :) -- Ponyobons mots 19:21, 23 August 2023 (UTC)
- MusikBot is quite slow sometimes. SurferSquall (talk) 19:23, 23 August 2023 (UTC)
- Understood; I just mentioned it in case you thought it would be left without a template in perpetuity :) -- Ponyobons mots 19:21, 23 August 2023 (UTC)
- I thought it important as it's got pretty high edit traffic right now SurferSquall (talk) 19:17, 23 August 2023 (UTC)
- @SurferSquall Done -Ad Orientem (talk) 19:17, 23 August 2023 (UTC)
Vandalism Attack on 2023 in Philippine Television.
We have a suspected user who vandalized the 2023 in Philippine Television.
Here's the blocking of the username...
We have to banned the user against violating the community standards and guidelines on Wikipedia. Jon2guevarra (talk) 10:42, 24 August 2023 (UTC)
- Declined User has received no warnings and appears to be a new user. I am not satisfied that their behavior is intentionally malicious. @Jon2guevarra. -Ad Orientem (talk) 22:59, 24 August 2023 (UTC)
Block evasion by 112.209.96.25/112.206.240.0/20
The user, 112.209.86.25, just have a suspected block evasion as 122.2.102.51. It is also the same user named 112.206.240.0/20, the one who keeps on disrupting edits. Would you mind blocking the user? 107.185.128.255 (talk) 20:16, 24 August 2023 (UTC)
IP you blocked back to disruptive editing
Hello, two days ago you blocked User:116.73.151.114 for disruptive editing, including persistent addition of unsourced content. The IP's block recently expired, but they are back to adding the same kind of unsourced, disruptive edits that got them blocked at this page [1]. I am not here to adjudge whether or not this one edit is sufficient enough to warrant another block, I just wanted to bring this to your attention, since they are back to adding unsourced content immediately after a block for such behavior expired. JeffSpaceman (talk) 16:30, 25 August 2023 (UTC)
- @JeffSpaceman Not a fan of recidivists. Reblocked x 2 weeks. -Ad Orientem (talk) 17:01, 25 August 2023 (UTC)
You've got mail
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can {{You've got mail}} or {{ygm}} template. at any time by removing the Mvcg66b3r (talk) 03:20, 27 August 2023 (UTC)
Why so many?
Hi! I noticed four screenfuls of revision deletions on my watchlist. (I’m used to seeing one deletion at a time).
Mind explaining what was going on and especially why so many revisions needed to be deleted from a main article?
Thanks, RadioactiveBoulevardier (talk) 05:07, 28 August 2023 (UTC)
- @RadioactiveBoulevardier The edits were not revdeled, just the user's name. They were editing areas of the project that touch on the Russo-Ukranian War and there are concerns regarding the possibility that they could possibly be doxed. The user has since created a WP:SECURESOCK. However, and out of an abundance of caution, it was deemed prudent to remove their original account name from the edit logs of certain pages. I am not sure if this process is done but I am hoping we are getting close. -Ad Orientem (talk) 08:35, 28 August 2023 (UTC)
- Ah, got it. Thanks for the prompt response! RadioactiveBoulevardier (talk) 08:44, 28 August 2023 (UTC)
Administrators' newsletter – September 2023
News and updates for administrators from the past month (August 2023).
|
|
- 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
.
- Special:Contributions now shows the user's local edit count and the account's creation date. (T324166)
- 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 tonote when broader community discussion, or changes to policies and guidelines, would be helpful
.
- 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.
Blocking Daniel Dunga due to offensive language and Filipino language typos.
Following the review of article timeline edits and history revision of History of vehicle registration plates of the Philippines. Here's the username that using Filipino language typos that repeatedly again with expletive offensive language on English Wikipedia under "How do you improve the article?" section.
As pending on the timeline of History of vehicle registration plates of the Philippines article. The user will be permanently blocked due to Filipino language typed in input on English Wikipedia article.
Hoping you to investigate the issue. Jon2guevarra (talk) 20:33, 3 September 2023 (UTC)
- @Jon2guevarra I have left a warning on their talk page. -Ad Orientem (talk) 21:47, 3 September 2023 (UTC)
More racist troll IPs
178.120.50.134 (talk · contribs · WHOIS)
178.124.163.11 (talk · contribs · WHOIS)
223.204.251.175 (talk · contribs · WHOIS)
Could you rev-del these edits and block each of the IPs for 3 months? (similarly blocked as 171.100.145.170 and other IPs). Thanks. 2601:601:51C:6A8:E15D:3D87:821D:CE85 (talk) 05:12, 4 September 2023 (UTC)
- Done FYI in the future it's best to report blatant vandalism of this sort to WP:AIV. Thanks for the heads up. -Ad Orientem (talk) 13:00, 4 September 2023 (UTC)
You've got mail
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can {{You've got mail}} or {{ygm}} template. at any time by removing the Mvcg66b3r (talk) 18:34, 1 September 2023 (UTC)
- Handled -Ad Orientem (talk) 20:39, 1 September 2023 (UTC)
New page patrol October 2023 Backlog drive
New Page Patrol | October 2023 Backlog Drive | |
| |
You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. |
MediaWiki message delivery (talk) 09:13, 9 September 2023 (UTC)
Khyan Jewel Cacapit will be declared a suspected sockpocket on Filipino language typos.
As of today, we have the review of article timeline edits of History of vehicle registration plates of the Philippines. Here's the suspected username that using Filipino language typos on English Wikipedia under "How do you improve the article?" section:
As pending on the timeline of History of vehicle registration plates of the Philippines article. This user will be permanently blocked, banned and revoked their user account due to repetitive Filipino language typo input on English Wikipedia article.
Hopefully to resolve the issue. Jon2guevarra (talk) 12:45, 12 September 2023 (UTC)
- Blocked x 1 week. -Ad Orientem (talk) 14:56, 12 September 2023 (UTC)
Books & Bytes – Issue 58
The Wikipedia Library: Books & Bytes
Issue 58, July – August 2023
- New partners - De Standaard and Duncker & Humblot
- Tech tip: Filters
- Wikimania presentation
Sent by MediaWiki message delivery on behalf of The Wikipedia Library team --14:26, 12 September 2023 (UTC)
Time for more than a warning?
Almost a year ago, you made this warning. The editor is still making disruptive edits and racking up warnings at User talk:Sythans27. They have never used edit summaries as far as I can tell, which is the thing you specifically warned them about. Other disruptive editing includes restoring content that is not MOS compliant, after being warned. Perhaps they are mobile editor and don't see the warnings, they definitely aren't communicating and have never used a talkpage. ☆ Bri (talk) 15:03, 13 September 2023 (UTC)
- @Bri I don't think this is actionable. They haven't received any formal warnings since May, which would make their last warning stale. A quick look at their editing history doesn't show them doing this all the time and relatively few of their edits have been reverted as disruptive. I am less than happy at their failure to communicate or acknowledge the messages left on their talk page. But as of right now, I'm not seeing enough for a block. -Ad Orientem (talk) 15:26, 13 September 2023 (UTC)
- Could you please look at this edit and the edit summary in particular, and see if you think anything has changed? Is there grounds for NPA at least for
you are a pageant hater, Who impersonates a Wikipedia user hahahahahaa
? ☆ Bri (talk) 13:56, 14 September 2023 (UTC)- @Bri Yeah, that's not cool. I left a formal caution on their talk page. -Ad Orientem (talk) 14:31, 14 September 2023 (UTC)
- Could you please look at this edit and the edit summary in particular, and see if you think anything has changed? Is there grounds for NPA at least for
Daniel Dunga repeatedly the Filipino language again on English article
As of today, we have the review of article timeline edits of History of vehicle registration plates of the Philippines. Here's the suspected username that using Filipino language typos on English Wikipedia under "How do you improve the article?" section:
As pending on the timeline of History of vehicle registration plates of the Philippines article. This user will be permanently blocked, banned and revoked their user account due to repetitive Filipino language typo input on English Wikipedia article.
Hopefully to resolve the issue. Jon2guevarra (talk) 21:06, 14 September 2023 (UTC)
- @Jon2guevarra I've blocked them from editing History of vehicle registration plates of the Philippines x 1 month. They have received enough warnings. -Ad Orientem (talk) 21:15, 14 September 2023 (UTC)
A barnstar for you!
The Anti-Vandalism Barnstar | |
Thanks for all your AIV work and handling the ones I send over. Cheers! Seawolf35 (talk) 01:01, 16 September 2023 (UTC) |
- @Seawolf35 Thank you! -Ad Orientem (talk) 01:23, 16 September 2023 (UTC)
Thank you!!
Thank you for the Barnstar and for immediately leaping into action when I reporting the problem! Polyquest (talk) 01:28, 16 September 2023 (UTC)
- @Polyquest It seems to be a good night for barnstars. In this case, well earned. -Ad Orientem (talk) 01:43, 16 September 2023 (UTC)
Would you mind...
If you have a moment, could you have a look at this new editor? Most of their edits are copyedits, but nearly all of their improvements add something grammatically incorrect. I left a message on their talk page, but they didn't agree. Thanks! Magnolia677 (talk) 14:36, 17 September 2023 (UTC)
- @Magnolia677 I am mostly seeing solid copyediting. In a few instances, I think there may have been an error, but it doesn't look like anything that might reasonably raise questions of deliberate disruption or competency. You might be better off to raise your concerns with the people at Wikipedia:WikiProject Guild of Copy Editors. As of right now I'm not seeing anything that would justify admin intervention. That said I appreciate the heads up and your looking out for the project. -Ad Orientem (talk) 15:56, 17 September 2023 (UTC)
- Hey, thanks! Magnolia677 (talk) 17:12, 17 September 2023 (UTC)
Maybe the current block is too narrow
Perhaps a topic specific block for this IP range isn't sufficient [2]. I've just scrolled through a bit of the recent history, and the contributions are not very impressive. Cheers, 2601:19E:4180:6D50:65F5:930C:B0B2:CD63 (talk) 19:28, 19 September 2023 (UTC)
- The level of collateral damage for a general block on that range would be pretty extreme. It could only be justified by an enormous amount of disruption that could not be addressed on a smaller range or through page protection. -Ad Orientem (talk) 20:18, 19 September 2023 (UTC)
Possible sock puppet account
Hello, you recently blocked a user who goes by "Friendlyhelper9949" for disruptive editing. I think this user has created another account under "Sparkinthedark22". "Friendlyhelper9949" had a tendency to edit track listings and this new user "Sparkinthedark22" is going around editing track listings. OkIGetIt20 (talk) 11:04, 20 September 2023 (UTC)
- @OkIGetIt20 Yeah. This is a sock of EmeraldWicket9947. I've indeffed them and reverted all of their current edits. Thanks for the heads up. -Ad Orientem (talk) 14:10, 20 September 2023 (UTC)
- Hey, I just learned that, EmeraldWicket9947/Friendlyhelper9949 is now back under three new accounts. "BeDefining", "Walkesu" and "Setuis". In an response to another user on Christina Milian's So Amazin' article EmeraldWicket9947/Friendlyhelper9949 under the screen name "BeDefining" stated, "i’m never gonna stop coming back". OkIGetIt20 (talk) 22:26, 28 September 2023 (UTC)
- @Ad Orientem I looked at this in response to same message to Yamla, having looking at Friendlyhelper9949 a few weeks ago at Sergecross73's talk page. All of the new accounts OkIGetIt20 identified are confirmed, blocked and tagged now. There's a /40 range here that may need account creation pulled, but the block log suggests that may be an issue, so I leave it to someone else to consider. @Yamla: As info. -- ferret (talk) 22:48, 28 September 2023 (UTC)
- @Ad Orientem, Yamla, and OkIGetIt20: To round this out, Sparnkinthedark22 is now confirmed, if there was any doubt. Also add KeepUp4930 to the pile. -- ferret (talk) 23:18, 28 September 2023 (UTC)
- @OkIGetIt20 Thanks for the heads up! @Ferret Thanks for handling that. I don't have access to the magic 8 ball so your assistance here was invaluable. Courtesy ping @Yamla. Ad Orientem (talk) 23:24, 28 September 2023 (UTC)
- Courtesy FYI @Ss112 & Livelikemusic. See the above thread please as both of you have dealt with this pervasive sock in the past and know their editing habits. Unfortunately, I have no reason to believe they won't be back. -Ad Orientem (talk) 23:30, 28 September 2023 (UTC)
- Thank you Ad Orientem. I agree, the edits do appear as them and they will likely be back very soon. I have my eye on another account, as well. livelikemusic (TALK!) 00:46, 29 September 2023 (UTC)
- @Livelikemusic Could you link me? I'm a CU and can check it. -- ferret (talk) 01:46, 29 September 2023 (UTC)
- Hi Ferret, it looks like the other account(s) I questioned were taken care of already! Safe to say they'll continue to be found out! livelikemusic (TALK!) 13:41, 29 September 2023 (UTC)
- Oops, looks like StayUnGrumpy (talk · contribs · deleted contribs · logs · filter log · block user · block log) may be a soft one. livelikemusic (TALK!) 15:24, 29 September 2023 (UTC)
- @Livelikemusic Could you link me? I'm a CU and can check it. -- ferret (talk) 01:46, 29 September 2023 (UTC)
- Thank you Ad Orientem. I agree, the edits do appear as them and they will likely be back very soon. I have my eye on another account, as well. livelikemusic (TALK!) 00:46, 29 September 2023 (UTC)
- Courtesy FYI @Ss112 & Livelikemusic. See the above thread please as both of you have dealt with this pervasive sock in the past and know their editing habits. Unfortunately, I have no reason to believe they won't be back. -Ad Orientem (talk) 23:30, 28 September 2023 (UTC)
- @OkIGetIt20 Thanks for the heads up! @Ferret Thanks for handling that. I don't have access to the magic 8 ball so your assistance here was invaluable. Courtesy ping @Yamla. Ad Orientem (talk) 23:24, 28 September 2023 (UTC)
- @Ad Orientem, Yamla, and OkIGetIt20: To round this out, Sparnkinthedark22 is now confirmed, if there was any doubt. Also add KeepUp4930 to the pile. -- ferret (talk) 23:18, 28 September 2023 (UTC)
- @Ad Orientem I looked at this in response to same message to Yamla, having looking at Friendlyhelper9949 a few weeks ago at Sergecross73's talk page. All of the new accounts OkIGetIt20 identified are confirmed, blocked and tagged now. There's a /40 range here that may need account creation pulled, but the block log suggests that may be an issue, so I leave it to someone else to consider. @Yamla: As info. -- ferret (talk) 22:48, 28 September 2023 (UTC)
- Hey, I just learned that, EmeraldWicket9947/Friendlyhelper9949 is now back under three new accounts. "BeDefining", "Walkesu" and "Setuis". In an response to another user on Christina Milian's So Amazin' article EmeraldWicket9947/Friendlyhelper9949 under the screen name "BeDefining" stated, "i’m never gonna stop coming back". OkIGetIt20 (talk) 22:26, 28 September 2023 (UTC)
Vandalism
Hi! I see you blocked this IP for a week. Special:Contributions/208.98.222.9 I collected already the evidences with bold font, that IP is making a long term the same boring vandalism on many articles: (honestly I do not know why IP edits allowed in Wiki) Talk:Hungarian alphabet#Cyrillic alphabet vandalism OrionNimrod (talk) 08:25, 25 September 2023 (UTC)
- I have been somewhat ambivalent about anonymous editing for a long time. It certainly is the source of the vast majority of disruptive editing. However, there is no really broad support for requiring registration within the community at the present time. -Ad Orientem (talk) 19:00, 25 September 2023 (UTC)
Talk page edit history
Could you remove the public view of that disruptive IP's edits on my talk page from the edit history as you did for the two other editors? I don't want something like that to be seen. Perhaps the the rest of the edits and edit summaries should be removed from this IP. WikiCleanerMan (talk) 15:58, 2 October 2023 (UTC)
- @WikiCleanerMan Looks like RickinBaltimore already got them. -Ad Orientem (talk) 16:08, 2 October 2023 (UTC)
Administrators' newsletter – September 2023
News and updates for administrators from the past month (September 2023).
|
|
- 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.
- 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)
- The 2023 CheckUser and Oversight appointments process has concluded with the appointment of one new CheckUser.
- Self-nominations for the electoral commission for the 2023 Arbitration Committee elections opens on 2 October and closes on 8 October.
Another sock of Friendlyhelper9949
Although they haven't edited since September 25, Vakiis certainly is another sock of Friendlyhelper9949 / EmeraldWicket9947's. They restored the sock's edits on some of the same articles. The editor EverythingYouNeedBaby edited after Vakiis on one of those articles looks suspicious too, as does another user Livelikemusic reverted on one of the articles Friendlyhelper9949's sock last edited, StayUnGrumpy. Ss112 03:07, 7 October 2023 (UTC)
- Ping Ferret. This looks pretty likely to me. -Ad Orientem (talk) 03:12, 7 October 2023 (UTC)
- @Ad Orientem and Ss112: Those three confirmed, plus DarknessSpike who needs reverting still and was active today. The IP range in use here is already blocked, these were all created back on the 24th during the last spate. I've swept around those ranges again and DarknessSpike was the only new one not identified yet. -- ferret (talk) 13:00, 7 October 2023 (UTC)
- @Ferret Thanks! I've reverted all of the edits from DarknessSpike. -Ad Orientem (talk) 13:21, 7 October 2023 (UTC)
- @Ad Orientem and Ss112: Those three confirmed, plus DarknessSpike who needs reverting still and was active today. The IP range in use here is already blocked, these were all created back on the 24th during the last spate. I've swept around those ranges again and DarknessSpike was the only new one not identified yet. -- ferret (talk) 13:00, 7 October 2023 (UTC)
Please don't remove "Disputed" tag
There is still an ongoing discussion, so it's not yet appropriate to remove the Disputed tag. Thank you. Not logged in 2 (talk) 19:07, 8 October 2023 (UTC)
- @Not logged in 2 I have replied on the article talk page. -Ad Orientem (talk) 19:48, 8 October 2023 (UTC)
- Okay, thanks for your professionalism about that. I went ahead and removed the tag. Not logged in 2 (talk) 20:09, 8 October 2023 (UTC)
Steven.Valentine is still adding personal, unsourced info to articles
I don't think that Steven.Valentine understands what this project is about - he has resumed adding unsourced information about his own life and, presumably, people to whom he is related or connected. ElKevbo (talk) 03:30, 13 October 2023 (UTC)
- @ElKevbo I am giving them the benefit of the doubt on a few of those edits and have dropped a note (the latest) on their talk page while reverting a couple of them. I am loathe to block people unless their behavior is manifestly bad faith, or the level of disruption demands it. Also, this is a new user who I think is not consciously trying to be disruptive. -Ad Orientem (talk) 05:12, 13 October 2023 (UTC)
frank clark
Go to the Denver Broncos website and go to roster. Frank Clark is nowhere on their website 2600:6C56:54F0:92F0:B5A9:F11C:FDA8:B5EC (talk) 20:11, 15 October 2023 (UTC)
- I think you have me confused with somebody else. -Ad Orientem (talk) 23:59, 15 October 2023 (UTC)
RevDel
[3] Does the edit summary require revision deletion? NoNAja (talk) 16:50, 16 October 2023 (UTC)
- @NoNAja Unless I'm missing something, this looks like run of the mill vandalism. Nothing that meets the guidelines for a revdel. -Ad Orientem (talk) 17:17, 16 October 2023 (UTC)
- I was thinking about the email address in the edit summary. NoNAja (talk) 17:25, 16 October 2023 (UTC)
- @NoNAja Good catch. Yes, that needs to go. -Ad Orientem (talk) 17:27, 16 October 2023 (UTC)
- I was thinking about the email address in the edit summary. NoNAja (talk) 17:25, 16 October 2023 (UTC)
Warning on Daniel Dungca edits on LTO temporary license plates.
As of today, we have the review of article timeline edits of History of vehicle registration plates of the Philippines. Here's the suspected username that edited typos on English Wikipedia under "How do you improve the article?" section:
A reason about the temporary license plates series was already released this year will be CBI 1001 and CBS 1001 in Region III. However, Daniel removed it but I restored the same temporary registered plates that we mentioned on LTO. Please be warned for the suspected edits.
As pending on the timeline of History of vehicle registration plates of the Philippines article. This user will be permanently blocked and revoked their user account due to repetitive Filipino language typo input on English Wikipedia article.
Hopefully to resolve the issue. Jon2guevarra (talk) 00:36, 19 October 2023 (UTC)
- @Jon2guevarra I don't think this is vandalism. It seems more likely honest mistakes. Also there have been no warnings since he was partially blocked in September. I suggest discussing this with them to see what they are trying to do. -Ad Orientem (talk) 00:59, 19 October 2023 (UTC)
Move I/O (Peter Gabriel album) to I/O (album)
Hi AO. Would you be able to move I/O (Peter Gabriel album) to I/O (album)? I'm asking for an admin to do it as the destination has a page history because it was previously the location of the article when it was redirected last year before being properly announced, so the page locations need to be swapped around. I filed this at WP:RM/TR and a user commented saying they weren't objecting but are noting that there's a user on the talk page who thinks the article text should say the lower-case i/o per Peter Gabriel's rendering of the title. In fact, in that thread, two users (Quwoting2 and RoyLeban) have said they agree it should be at the simpler I/O (album), and as there are no objections, I'm not sure what the hold-up with moving the article is. Ss112 13:51, 19 October 2023 (UTC)
- @Ss112 Done -Ad Orientem (talk) 14:14, 19 October 2023 (UTC)
Khyan Jewel Cacapit repeatedly posted again in Filipino in timeline edits.
As of today, we have the review of article timeline edits of History of vehicle registration plates of the Philippines. Here's the suspected username that using Filipino language typos on English Wikipedia under "How do you improve the article?" section:
As pending on the timeline of History of vehicle registration plates of the Philippines article. This user will be permanently blocked and revoked their user account due to repetitive Filipino language typo input on English Wikipedia article.
Hopefully to resolve the issue. Jon2guevarra (talk) 02:10, 21 October 2023 (UTC)
- Page blocked x 3 months. -Ad Orientem (talk) 18:41, 21 October 2023 (UTC)
Iskandar323
Considering the changes I had to make to "Nakba denial" (with a couple intervening ones by Dimadick) I think this editor has a very serious problem. That they choose a time of international strife to do this is doubly concerning. I don't think this person should be making Wikipedia articles or editing Wikipedia if this is their idea of how to state facts in Wikivoice and use quotes (without attribution?). That's the worst most one-sided "article" I've ever seen. Oh not to forget this correction they made themself after I pointed it out on NPOV/N. I have never seen such flagrant abuse of Wikipedia for advocacy by an apparently established editor. —DIYeditor (talk) 12:10, 21 October 2023 (UTC)
- I agree it's definitely an NPOV fail but I'd try not to get too worked up. The ongoing horror movie that began on October 7th has got everybody worked up. I'm encouraged by the fairly level headed response of the community overall. -Ad Orientem (talk) 18:44, 21 October 2023 (UTC)
- Perhaps I overreacted, and equally well I may not know what is par for the course in this kind of article. To me NPOV fail is putting it quite mildly. I guess I don't understand how someone intelligent (Iskandar speaks/writes fairly well at least) could make an article in good faith about an obviously controversial topic without the least acknowledgement that there is another point of view. —DIYeditor (talk) 08:06, 22 October 2023 (UTC)
Nakba denial
At ANI you say that he Nakba denial page is recently recreated. Was there a previous deletion discussion or similar? It doesn't seem to be linked in the AfD. Thanks. Sirfurboy🏄 (talk) 17:10, 22 October 2023 (UTC)
- @Sirfurboy It has been deleted twice previously. Deletion log for Nakbal denial. -Ad Orientem (talk) 17:39, 22 October 2023 (UTC)
- Thanks. I should have thought to look there. Sirfurboy🏄 (talk) 18:15, 22 October 2023 (UTC)
- No worries. I didn't realize that this wasn't already linked in the AfD. -Ad Orientem (talk) 19:41, 22 October 2023 (UTC)
- Thanks. I should have thought to look there. Sirfurboy🏄 (talk) 18:15, 22 October 2023 (UTC)
In 2021, you properly blocked (for nearly 4 years!) a pro-Hamas vandal IP ([5]), a block that is still active, but, unfortunately, you didn't rollback or revert their pro-Hamas vandalism on the Muhammad Sawalha article, which has, in light of everything happening since 7 October, taken on particular importance. I would do so but I think you probably would it so more skillfully. Can you do so or should I? If you choose to do so, can you add that he is a British citizen ([6], [7]). Thanks. 65.88.88.43 (talk) 18:13, 23 October 2023 (UTC)
- That's a rangeblock of 82.132.192.0/18 that was put in place to deal with an LTA that has been causing a lot of disruption over the years. It wasn't a specific response to the obviously POV editing on that page, which I probably was not even aware of given that block was not put in place for almost a full year after the edits in question. That said, clearly there is some problematic material that was added. The article subject also clearly falls under the heading of contentious topics and should not be open for editing by unregistered users. I am going to protect the page. Unfortunately, that won't solve the problematic content. I can't edit the article myself as I will be protecting the page in my capacity as an admin. I will drop a note at WP:NPOVN to alert experienced editors of the problems. -Ad Orientem (talk) 19:05, 23 October 2023 (UTC)
RevDel at Tedros Adhanom Ghebreyesus
Bit old, but I found this bit of probable racist abuse at that article's talk; might warrant a revdel. AryKun (talk) 17:18, 30 October 2023 (UTC)
- @AryKun Agreed and done. If that edit wasn't stale I'd have issued a WP:ZT block. -Ad Orientem (talk) 18:21, 30 October 2023 (UTC)
Administrators' newsletter – November 2023
News and updates for administrators from the past month (October 2023).
Interface administrator changes
- The WMF is working on making it possible for administrators to edit MediaWiki configuration directly. This is similar to previous work on Special:EditGrowthConfig. A technical RfC is running until November 08, where you can provide feedback.
- There is a proposed plan for re-enabling the Graph Extension. Feedback on this proposal is requested.
- Eligible editors are invited to self-nominate themselves from 12 November 2023 until 21 November 2023 to stand in the 2023 Arbitration Committee elections.
- Xaosflux, RoySmith and Cyberpower678 have been appointed to the Electoral Commission for the 2023 Arbitration Committee Elections. BusterD is the reserve commissioner.
- 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.
- 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!
PeopleEater143 using an IP
Hi AO. You blocked PeopleEater143 in 2018 and have blocked multiple of their sockpuppets since. I'm no expert with ranges but they are absolutely using the range 2601:48:0:0:0:0:0:0/32. Same terrible attitude on pop music articles that keeps popping up again and again [8] [9]. Also, the smoking gun here is that a sockpuppet of PeopleEater143 was edit warring on Divide (Ed Sheeran album) when it was a recent release, saying that singles released on the same day "need" to be listed alphabetically. See the edits of the IP addresses listed at Wikipedia:Sockpuppet_investigations/PeopleEater143/Archive#16_January_2017: this one, for example and this. They made an edit using this "logic" and referencing that album on another album article last month [10]. 100% the same person. Ss112 12:19, 8 November 2023 (UTC)
- AO, this editor is already back on another IP and edit warring when they've been reverted. Ss112 13:58, 8 November 2023 (UTC)
- @Ss112 Blocked the /32 range x 1 month. -Ad Orientem (talk) 17:49, 8 November 2023 (UTC)
My woes regarding AIV
Not a big deal at all, but I was declining the AIV report on User: 82.14.11.224 when you blocked them. They made two quick back-to-back test-like edits, Wesoree simultaneously gave them a Level 1 warning pointing the IP the Sandbox and made the AIV report. 10+ minutes had passed with no further edits. Then your block. Honestly, I think I need to just stay away from AIV altogether, a large amount of the reports there don't meet any of the reporting requirements, and it's the same group of editors making the same reports repeatedly. I see HJ Mitchell declining some reports here and there, but otherwise I think patrollers will just always continue reporting becomes most of the time a block will be made. I think I'm just out of step with how that board is generally admined, or maybe we need to remove requirement 2 from the directions at the top of the page. That's my rant for the day, sorry it fell on you! -- Ponyobons mots 23:52, 9 November 2023 (UTC)
- @Ponyo I sympathize having to regularly decline reports myself. So, I took a second look at the two edits by 82.14.11.224 in case I was misreading what might have been ill advised edits by a newbie. And I have to say, those two look like vandalism to me. But if you think there is a reasonable chance that these were something less than that, feel free to unblock them with a more formal warning. My guess is that the warning was issued before they saw the 2nd edit. That said, I do agree that an argument could be made for dropping a stronger warning vice the Level I. AIV is often a gray area.-Ad Orientem (talk) 00:03, 10 November 2023 (UTC)
- Oh they were vandalism, or test edits, but one of the requirements for reporting and blocking (outside of egregious disruption/racist/hate speech etc.), is that the editor has to be warned and then actual continue disrupting after being warned. I don't think the IP should be unblocked, I'm just really disappointed by the large uptick in the use of anti-vandal scripts to place a level 1 warning and report at AIV at the same time. Or stacking warnings up to level 4 when have been no intermittent edits, then reporting. It seems like gaming. But again, this is just me, looking for an ear to bend. I think I'll just stick to the bot reports for a while. Let the rest of you have all the fun (ha!). Thanks for all that you do here.-- Ponyobons mots 00:13, 10 November 2023 (UTC)
- As another who blocks a lot at AIV, it's a difficult line to walk. The purpose of the block is to prevent disruption, and balancing warnings against editor time and the possibility of vandalism slipping through isn't a science. ScottishFinnishRadish (talk) 00:16, 10 November 2023 (UTC)
- @Ponyo @ScottishFinnishRadish Warnings are usually desirable. But in cases of obviously bad faith editing, no warning blocks are within admin discretion per WP:BEFOREBLOCK. It's possible that this might not really be the best example for that though. -Ad Orientem (talk) 00:22, 10 November 2023 (UTC)
- I'm not disagreeing with you. I've placed many blocks without the full slate of warnings, or any warnings at all. I was trying to express why, in my view, it is common at AIV not to require the progression of warnings even when the vandalism isn't particularly egregious. ScottishFinnishRadish (talk) 00:27, 10 November 2023 (UTC)
- I actually consider(ed) myself as somewhat heavy handed with blocking. I don't think four levels of warning are needed, or even desirable in many (most?) cases. But I find the reports for bog standard test/vandalism edits recently are being made too soon. No more posting here, I'm off to make dinner. Sorry for taking up so much space on your talk page Ad Orientem.-- Ponyobons mots 00:29, 10 November 2023 (UTC)
- @Ponyo No worries. It's (almost) always good to hear from and get feedback from colleagues. -Ad Orientem (talk) 00:35, 10 November 2023 (UTC)
- For what it's worth, I share many of Ponyo's concerns. There's a small group of editors who report even the most trivial vandalism to AIV. I actually threatened to pblock one from the board and spent some time explaining the guidelines and the edge cases and their reports have got a lot better since. It might be good to have a more general discussion at WT:AIV or similar as we're four of the most active admins there and I think we agree on more than we disagree. HJ Mitchell | Penny for your thoughts? 12:14, 10 November 2023 (UTC)
- @HJ Mitchell, @Ponyo, @ScottishFinnishRadish I gave some thought to this last night, and I have boldly added a sentence to the edit notice at AIV. Unfortunately, I am not sure how effective that will be as a lot of the regulars who make reports to AIV use things like Twinkle where the edit notice isn't going to be seen. -Ad Orientem (talk) 14:41, 10 November 2023 (UTC)
- I think if the four of us all enforce it and we all decline reports where there hasn't been vandalism *after* a warning (preferably a more "serious" one), the message might start to get through. HJ Mitchell | Penny for your thoughts? 15:39, 10 November 2023 (UTC)
- The added wording also dovetails with Point 2 of the instructions on the main AIV page itself ("Except for egregious cases, the user must have been given enough warning(s) to stop their disruptive behavior."), so I agree with the update.-- Ponyobons mots 16:34, 10 November 2023 (UTC)
- This was a really interesting discussion! I report immediately for abject WP:PROMO and anything involving race/sociologically-based epithets/threats. I use Twinkle for warning and reporting, but when there is an extenuating circumstance I try to specify that ("user is engaged in ongoing campaign of altering sports statistics") as a reason I might not have bureaucratically given escalating warnings. If it's just a one-off instance of a kid adding "is dreamy" after, e.g., Jasmine Cephas Jones' name, that's when I see no reason to go to ANI unless the situation becomes repetitive and intractable (or they leave me a talk page message calling me a bad name, in which, yes, I am going to report; THAT behavior is not okay). Thanks for all of your help over the years! - Julietdeltalima (talk) 17:17, 10 November 2023 (UTC)
- @Julietdeltalima: obvious spammers, including people who clearly only came here to promote their company etc on their user page, you can mist certainly report to AIV. I think we're talking about your usual childish vandalism here. People who have an agenda incompatible with our goals should be politely but firmly shown the door as soon as they come to notice. HJ Mitchell | Penny for your thoughts? 17:52, 10 November 2023 (UTC)
- This was a really interesting discussion! I report immediately for abject WP:PROMO and anything involving race/sociologically-based epithets/threats. I use Twinkle for warning and reporting, but when there is an extenuating circumstance I try to specify that ("user is engaged in ongoing campaign of altering sports statistics") as a reason I might not have bureaucratically given escalating warnings. If it's just a one-off instance of a kid adding "is dreamy" after, e.g., Jasmine Cephas Jones' name, that's when I see no reason to go to ANI unless the situation becomes repetitive and intractable (or they leave me a talk page message calling me a bad name, in which, yes, I am going to report; THAT behavior is not okay). Thanks for all of your help over the years! - Julietdeltalima (talk) 17:17, 10 November 2023 (UTC)
- The added wording also dovetails with Point 2 of the instructions on the main AIV page itself ("Except for egregious cases, the user must have been given enough warning(s) to stop their disruptive behavior."), so I agree with the update.-- Ponyobons mots 16:34, 10 November 2023 (UTC)
- I think if the four of us all enforce it and we all decline reports where there hasn't been vandalism *after* a warning (preferably a more "serious" one), the message might start to get through. HJ Mitchell | Penny for your thoughts? 15:39, 10 November 2023 (UTC)
- @HJ Mitchell, @Ponyo, @ScottishFinnishRadish I gave some thought to this last night, and I have boldly added a sentence to the edit notice at AIV. Unfortunately, I am not sure how effective that will be as a lot of the regulars who make reports to AIV use things like Twinkle where the edit notice isn't going to be seen. -Ad Orientem (talk) 14:41, 10 November 2023 (UTC)
- For what it's worth, I share many of Ponyo's concerns. There's a small group of editors who report even the most trivial vandalism to AIV. I actually threatened to pblock one from the board and spent some time explaining the guidelines and the edge cases and their reports have got a lot better since. It might be good to have a more general discussion at WT:AIV or similar as we're four of the most active admins there and I think we agree on more than we disagree. HJ Mitchell | Penny for your thoughts? 12:14, 10 November 2023 (UTC)
- @Ponyo No worries. It's (almost) always good to hear from and get feedback from colleagues. -Ad Orientem (talk) 00:35, 10 November 2023 (UTC)
- I actually consider(ed) myself as somewhat heavy handed with blocking. I don't think four levels of warning are needed, or even desirable in many (most?) cases. But I find the reports for bog standard test/vandalism edits recently are being made too soon. No more posting here, I'm off to make dinner. Sorry for taking up so much space on your talk page Ad Orientem.-- Ponyobons mots 00:29, 10 November 2023 (UTC)
- I'm not disagreeing with you. I've placed many blocks without the full slate of warnings, or any warnings at all. I was trying to express why, in my view, it is common at AIV not to require the progression of warnings even when the vandalism isn't particularly egregious. ScottishFinnishRadish (talk) 00:27, 10 November 2023 (UTC)
- @Ponyo @ScottishFinnishRadish Warnings are usually desirable. But in cases of obviously bad faith editing, no warning blocks are within admin discretion per WP:BEFOREBLOCK. It's possible that this might not really be the best example for that though. -Ad Orientem (talk) 00:22, 10 November 2023 (UTC)
- As another who blocks a lot at AIV, it's a difficult line to walk. The purpose of the block is to prevent disruption, and balancing warnings against editor time and the possibility of vandalism slipping through isn't a science. ScottishFinnishRadish (talk) 00:16, 10 November 2023 (UTC)
- Oh they were vandalism, or test edits, but one of the requirements for reporting and blocking (outside of egregious disruption/racist/hate speech etc.), is that the editor has to be warned and then actual continue disrupting after being warned. I don't think the IP should be unblocked, I'm just really disappointed by the large uptick in the use of anti-vandal scripts to place a level 1 warning and report at AIV at the same time. Or stacking warnings up to level 4 when have been no intermittent edits, then reporting. It seems like gaming. But again, this is just me, looking for an ear to bend. I think I'll just stick to the bot reports for a while. Let the rest of you have all the fun (ha!). Thanks for all that you do here.-- Ponyobons mots 00:13, 10 November 2023 (UTC)
Hi Ad Orientem. My name is Kevin Frakes and I am the owner of PalmStar Media. Someone initially tried to create a negative article about me at AfC, was rejected, then put their content on the page about my business instead. Most of the content problems were addressed after I posted at BLPN, but there is one issue remaining regarding a lawsuit that did not involve PalmStar Media and is cited to an article that does not mention PalmStar. I posted about it here and was hoping you might be willing to take a look. As I have a conflict of interests, I will not be editing the page. Ksf207 (talk) 19:07, 17 November 2023 (UTC)
- Hi Ksf207. I've removed the material in contention pending better sourcing and some clearer connection to your business. Best regards... -Ad Orientem (talk) 21:00, 17 November 2023 (UTC)
Books & Bytes – Issue 59
The Wikipedia Library: Books & Bytes
Issue 59, September – October 2023
- Spotlight: Introducing a repository of anti-disinformation projects
- Tech tip: Library access methods
Sent by MediaWiki message delivery on behalf of The Wikipedia Library team --16:15, 27 November 2023 (UTC)
ArbCom 2023 Elections voter message
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:39, 28 November 2023 (UTC)