Misplaced Pages

User talk:Beeblebrox: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 07:16, 27 November 2024 editJclemens (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers45,490 edits Misplaced Pages:Articles for deletion/Ponytail canasta: r← Previous edit Latest revision as of 03:55, 14 January 2025 edit undoSdrqaz (talk | contribs)Checkusers, Oversighters, Administrators26,806 edits Granting extended-confirmed early: I don't follow 
(210 intermediate revisions by 49 users not shown)
Line 1: Line 1:

{{imbox|text=<big><big>'''I used to be called Beeblebrox. I'm fine with it if anyone still calls me that, or Beebs, or whatever. '''</big></big> }}
{{Archive basics {{Archive basics
|archive = User talk:Just Step Sideways/Archive %(counter)d |archive = User talk:Beeblebrox/Archive %(counter)d
|counter = 51 |counter = 52
|headerlevel = 2 |headerlevel = 2
|maxarchivesize = 120K |maxarchivesize = 120K
Line 29: Line 29:
{{skip to top and bottom}} {{skip to top and bottom}}


== Why did you redirect Mary-Catherine Deibel? ==
== Heads up: your unblock of GageCSayre ==


I don’t understand why you redirected ]. Those who proposed this gave no reasons and no editor responded to my analysis and additions to the article. Why not relist or declare no consensus? ] (]) 01:35, 1 January 2025 (UTC)
*]
*]
*]


:It was already relisted once specifically to allow for such a response, and none was forthcoming. It can therefore be assumed that your point was not found persuasive, the only comment coming after being in favor of merging or redirecting, and the only other "keep" comment was self-identified as weak. All other comments indicated opposition to a stand-alone article. I don't think another relist was likely to change that. ] ] 02:03, 1 January 2025 (UTC)
I was pleasantly surprised to see you slash through red tape and that ancient block, which was a refreshing change of pace after your stonewalling of ; HOWEVER, I believe in doing so you might've overlooked a relevant bit of information.
::It's my understanding that in AfD discussions, the outcome is not from a majority vote but rather from the content of the discussion. There was zero justification by any of the editors voting to delete or redirect. The nominator wrote This was not true in my estimation. I took my time to carefully evaluate the sources and add to the article. I noted that from my reading all the sources except the interview and one other met ] in ]. No one responded to that. After the first relisting, only one editor responded and did not give any justification for their vote. If others could explain why these sources shouldn't count towards notability that would be one thing, but they didn't. Ideally you would open this back up and ask for a direct evaluation of the references. If no one responds directly to the references, to me this is a "no consensus" decision. Note I'd never heard of this person before the AfD so my concern here is process. ] (]) 16:14, 1 January 2025 (UTC)
:::I believe I reasonably interpreted the consensus of the discussion. I will note that the lone "speedy delete" comment was ''not'' considered as there was no explanation whatsoever of what ] would apply. Any content that may be worth keeping can be pulled from the page history and merged at the redirect target. ] ] 21:23, 1 January 2025 (UTC)
::::I'm disappointed that you didn't address my ] concern as I'm not sure how you could interpret consensus without knowing why each editor voted the way they did.... I didn't realize the history with the page markup was available from the "Articles for deletion" subject page so thank you for noting that. ] (]) 23:30, 1 January 2025 (UTC)


== Username query ==
In , the user claims to be ], who is tagged as a sock of ], who in turn is tagged as a '''banned '''.


Hi Beeblebrox. I'm asking you about this because you're the most recent admin (at least at the time of this post) to have been active at ]. Do you think there's a ] or ] problem with respect to {{no ping|Socceroos TV}}? I just want a second opinion before adding {{tlx|uw-username}} template to their user talk page. -- ] (]) 08:45, 2 January 2025 (UTC)
It is, of course, entirely possible that the connection was made in error (] doesn't even mention "RoyalRumble24" as far as I can tell), but I think we can both agree that this isn't something to just ignore. If you disagree, please make a statement to that effect for the record.


:Unless there is an actual organization by that name, it probably isn't an issue. ] ] 18:53, 2 January 2025 (UTC)
Thank you. ] (]) 07:46, 26 October 2024 (UTC)
::Thanks for taking a look. I did some Googling and didn't come up with anything; so, I'll just AGF here and pursue things no further. -- ] (]) 22:07, 2 January 2025 (UTC)


== Request ==
:This is what I get for trying to AGF and look for a simple solution. I think I'm still inclined to just wait and see given the amount of time involved. The unblock doesn't really change anything as they apparently can't access that account, so if they don't immediately go back to creating hoaxes there's no issue, and if they do... banhammer. ] ] 17:28, 26 October 2024 (UTC)
::As the instigator of that thread I kind of feel the same way. +1 for them trying to be transparent though, when they could have just not mentioned all the extra socks.<span id="ClaudineChionh:1729984713167:User_talkFTTCLNJust_Step_Sideways" class="FTTCmt"> —&nbsp;''']''' <small>(''she/her'' · ] · ] · ])</small> 23:18, 26 October 2024 (UTC)</span>
::The problem is that effectively allowing a banned LTA back on the site isn't a call that a single admin can make. By simply unblocking, we're setting the editor up for failure.


Hello, is there any way I can gain access to the history of the deleted ] article? ] (]) 11:09, 2 January 2025 (UTC)
::Think about it: the ''best'' case scenario is that the user becomes a productive contributor, at some point gets into a dispute with someone over something (which is quite literally unavoidable), that someone decides to use the fact that the user is still technically banned to get the upper hand, and all hell breaks loose (with you at the center of it probably).


:{{done}} It is at ]. I feel I would be remiss if I didn't mention that several participants at the AFD found serious issues with the way this was sourced and that the content did not reflect an accurate reading of the sources. ] ] 19:00, 2 January 2025 (UTC)
::Instead of leaving the siteban situation effectively unresolved, we should follow the normal procedure: start with a CU check on TheAmazingCoffeeMan (I'm sure {{ping|NinjaRobotPirate}} wouldn't mind lending a hand) to make sure the banned LTA doesn't have twenty other accounts operating already (AGF but verify), ask them about ] they didn't mention, and then have a proper AN discussion.
::Thanks, and don't worry, this is the reason why I requested the version, for further examination of these issues, namely sockpuppetry, not to restore the content. ] (]) 19:42, 2 January 2025 (UTC)
:::Ah, gotcha. ] ] 19:45, 2 January 2025 (UTC)
::::So a user has moved the article to the mainspace. Can this please be reverted and locked until the evidence at the SPI is evaluated? ] (]) 14:15, 5 January 2025 (UTC)
:::::Looks like it was already moved back, I will go ahead and move-protect it. ] ] 08:35, 6 January 2025 (UTC)
::::::Thanks! ] (]) 10:56, 6 January 2025 (UTC)


== Administrators' newsletter – January 2025 ==
::Personally, I too would support letting them return based on the length of time that has passed since their vandalizing rampage alone, but it's in everyone's best interest to do it the proper way. ] (]) 02:10, 27 October 2024 (UTC)
:::I've raised the issue on their talk page. ] ] 18:38, 27 October 2024 (UTC)


] from the past month (December 2024).
==Dummy==
Good little user! Stay! ] ] ] 09:10, 26 October 2024 (UTC).
:I don't often find myself agreeing with colossal prehistoric reptilian / dinosaurian monsters, but to say that the thoughs expressed in ] are well articulated and as a long-term (c. 2005) WR/WPO lurker, align with my own. ] (]) 22:26, 26 October 2024 (UTC)


<div style="display: flex; flex-wrap: wrap">
== A barnstar for you! ==
<div style="flex: 1 0 20em">

{| style="background-color: #fdffe7; border: 1px solid #fceb92;"
|rowspan="2" style="vertical-align: middle; padding: 5px;" | ]
|style="font-size: x-large; padding: 3px 3px 0 3px; height: 1.5em;" | '''The Admin's Barnstar'''
|-
|style="vertical-align: middle; padding: 3px;" | Your close at ] was exactly was what I thought of saying to asilvering, but chose not to for lack of desire to "argue with the refs" as it were. Thanks! ] 04:01, 28 October 2024 (UTC)
|}

:Thanks! ] ] 17:25, 28 October 2024 (UTC)

== Names ==

I'll stick with Beebs...it's used affectionately. ] ] ] 19:27, 31 October 2024 (UTC)

:I sometimes think I should've gone with that, as it refers specifically to me, but I wanted to make some sort of shout out to ] so here we are. ] ] 20:00, 31 October 2024 (UTC)

== Re: I guess we're not quite done here yet. ==

{{Talkback|TheAmazingCoffeeMan|I guess we're not quite done here yet.|ts = 20:21, 31 October 2024 (UTC)}} ] (]) 20:21, 31 October 2024 (UTC)

== Revision deletion for BLP violations ==

Hello, could you revdel some BLP violating content on this article: I removed it with my most recent edit. ] (]) 03:33, 1 November 2024 (UTC)

== An Update ==
Hi, {{u|Just Step Sideways}}. I am thrilled to share that I successfully completed my ] yesterday, guided by {{u|DreamRimmer}}’s mentorship. I wanted to share this update with you specifically, as it was your encouragement back in June 2024, when you ] and suggested I pursue NPP, that led me to consider taking this step. I hope to see you around, and please don’t hesitate to reach out if you feel I am deviating from Misplaced Pages's editing guidelines or committing any sort of mistakes. ] (]) 06:49, 1 November 2024 (UTC)

== Administrators' newsletter – November 2024 ==

] from the past month (October 2024).

]


] '''Administrator changes''' ] '''Administrator changes'''
:] ]
:] {{hlist|class=inline :] {{hlist|class=inline
|] |]
|]
}} }}
:] {{hlist|class=inline :] {{hlist|class=inline
|] |]
|] |]
|] |]
|] |]
|] |]
|] |]
|]
}} }}


] '''CheckUser changes''' ] '''CheckUser changes'''
:] ] :] {{hlist|class=inline
|]
|]
|]
|]
|]
}}
:] ]
:] ]


</div>
] '''Oversighter changes'''
<div style="flex: 1 0 20em">
:] ]
]

] '''Oversight changes'''
:] {{hlist|class=inline
|]
|]
|]
|]
|]
}}
:] ]


</div>
] '''Guideline and policy news'''
</div>
* Following a ], the ] proposal that went for a trial to refine the ] (RfA) process has been discontinued.
* Following a ], ] is adopted as a policy.


] '''Guideline and policy news'''
* Following ], ] was adopted as a ].
* A ] is open to discuss whether admins should be advised to warn users rather than issue no-warning blocks to those who have posted promotional content outside of article space.
] '''Technical news''' ] '''Technical news'''
* The Nuke feature also now ] to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.
* Mass deletions done with the ] tool now have the 'Nuke' tag. This change will make reviewing and analyzing deletions performed with the tool easier. {{phab|T366068}}


] '''Arbitration''' ] '''Arbitration'''
* {{noping|RoySmith}}, {{noping|Barkeep49}} and {{noping|Cyberpower678}} have been appointed to the ] for the ]. {{noping|ThadeusOfNazereth}} and {{noping|Dr vulpes}} are reserve commissioners. * Following the ], the following editors have been elected to the Arbitration Committee: {{noping|CaptainEek}}, {{noping|Daniel}}, {{noping|Elli}}, {{noping|KrakatoaKatie}}, {{noping|Liz}}, {{noping|Primefac}}, {{noping|ScottishFinnishRadish}}, {{noping|Theleekycauldron}}, {{noping|Worm That Turned}}.

* Eligible editors are invited to self-nominate from 3 November 2024 until 12 November 2024 to stand in the ].
* The Arbitration Committee is ] for roles such as clerks, access to the COI queue, checkuser, and oversight.
] '''Miscellaneous''' ] '''Miscellaneous'''
* An ] is happening in November 2024 to reduce the backlog of articles tagged with {{tl|Unreferenced}}. You can help reduce the backlog by adding citations to these articles. ] * A ] is happening in January 2025 to reduce the number of unreviewed articles and redirects in the ]. ]


---- ----
Line 132: Line 126:
}}}} }}}}
<!-- <!--
-->{{center|1=<small>Sent by ] (]) 10:21, 3 November 2024 (UTC)</small>}} -->{{center|1=<small>Sent by ] (]) 15:46, 5 January 2025 (UTC)</small>}}
<!-- Message sent by User:DreamRimmer@enwiki using the list at https://en.wikipedia.org/search/?title=Misplaced Pages:Administrators%27_newsletter/Subscribe&oldid=1254686817 --> <!-- Message sent by User:DreamRimmer@enwiki using the list at https://en.wikipedia.org/search/?title=Misplaced Pages:Administrators%27_newsletter/Subscribe&oldid=1266956718 -->

== Arbitration case request declined ==

Hi Just Step Sideways. The '']'' case request has been declined. While the arbitrators were closely divided, there was not an absolute majority to accept the case. For the Arbitration Committee, ]&nbsp;] 06:39, 7 November 2024 (UTC)

:I wonder if seventeen days is aome kind of record for a case request... ] ] 22:24, 7 November 2024 (UTC)

== Cleanup request ==

Hi! Hope things are well with you. Given can you fix the page ] in whatever fashion is recommended? ] (]) 12:36, 7 November 2024 (UTC)

:I did mean to do just that, must've got disctracted... Looks like HouseBlaster already got to it. ] ] 20:33, 7 November 2024 (UTC)

== I blame myself ==

for ]. I'd seen questionable blocks at UTRS and not said anything. Too unwilling to question a colleague. SMDH. ] (]) 12:47, 7 November 2024 (UTC)

:It's not an easy thing, holding colleagues to account, but he was called out on it repeatedly before this. It's not on you. ] ] 20:34, 7 November 2024 (UTC)
:If you ever see any of my actions you find questionable don't hesitate to point them out. Civil queries about admin actions between admins should be completely normal. ] (]) 23:11, 8 November 2024 (UTC)
:I'll take a portion of that {{u|Deepfriedokra|DFO}}. I've seen some questionable blocks but not so questionable or so often that I felt a need to stick my nose in. A more open culture among admins, challenging the decisions without challenging the admins, would go a long way to fending off any unnecessary escalation. To those who have felt able to tactfully step in to situations such as this before they have blown up, more power to you. ] (]) 12:31, 10 November 2024 (UTC)

== ==

... you're an Indian news company. ] (]) 22:37, 8 November 2024 (UTC)

:Yeah, for that you have to actually file a lawsuit and wait a couple months. And while I can't claim to know how these things are done on the subcontinent, in the US it isn't libel unless you can prove it is not true. ] ] 22:42, 8 November 2024 (UTC)

== November 2024 ==

Hi, do you think the following account might be a Flyer22 sock? ] (]) 08:14, 9 November 2024 (UTC)

:] would be the place to discuss that. ] ] 20:10, 9 November 2024 (UTC)

== No answer ==

]

Hello, I have not received any response for 11 days on this page. Is this normal? How can this be explained, and what should I do? Kind regards ] (]) 00:29, 11 November 2024 (UTC)

:Not at all sure why you decided to ask me in particular as I don't edit in that subject area, but I have responded there. ] ] 00:59, 11 November 2024 (UTC)

== November music ==
{{User QAIbox
| image = Apple tree in field, detail, Ehrenbach.jpg
| image_upright = 0.8
| bold = ] · ] · ]
}}
I uploaded more pics (see places), on a mountain in the sun above the fog. - ] - ]. -- ] (]) 23:53, 11 November 2024 (UTC)

:]I'm kinda bummed that I didn't make it back this year to the lake in the picture at the right. Last time we were there we took our ] out and managed to spot a bear with two cubs foraging on the mountainside. ] ] 00:12, 12 November 2024 (UTC)

==Notice of noticeboard discussion==
] There is currently a discussion at ] regarding an issue with which you may have been involved.&nbsp;The thread is ]. Thank you.<!--Template:Discussion notice--><!--Template:AN-notice--> <span class="nowrap">] (]) <small>(please ] me on reply)</small></span> 19:06, 12 November 2024 (UTC)

== Reminder to participate in Misplaced Pages research ==

Hello,

I recently invited you to take a survey about administration on Misplaced Pages. If you haven’t yet had a chance, there is still time to participate– we’d truly appreciate your feedback. The survey is anonymous and should take about 10-15 minutes to complete. You may read more about the study on its ] and view its ].

Take the survey ''''''.

Kind Regards,

]

<bdi lang="en" dir="ltr">] (]) 00:18, 13 November 2024 (UTC) </bdi>
<!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/search/?title=UOzurumba_(WMF)/sandbox_Research_announcement_list_for_enwiki_Current_Admins_(reminders)&oldid=27744339 -->

==Mail call==
{{ygm}} ] &#124; ] 11:04, 13 November 2024 (UTC).

And YGM from me. ] (]) 16:28, 14 November 2024 (UTC)

Forget it. The issue has resolved itself. Probably a cache error. ] (]) 16:37, 14 November 2024 (UTC)

:Weird. Before just now my last edit was about fourteen hours ago. Good to see you though. ] ] 18:33, 14 November 2024 (UTC)
I have also sent mail ] ] 07:58, 18 November 2024 (UTC)
* <small>I have also sent mail. It was to my insurance company...but...I just wanted to feel like part of the group. ]] 23:51, 18 November 2024 (UTC)</small>

== I don't understand the need to twist the knife ==

Just leave the guy alone. Jesus. ] (]) 23:36, 18 November 2024 (UTC)

:I just think it would be better for everyone if this just ended now instead of going on for a full week. It's probably in his own best interest to pull the plug now. ] ] 23:39, 18 November 2024 (UTC)
::And you think he's not able to see what's going on and decide for himself, and needs you to give advice (masquerading as a question), because ...? ] (]) 23:48, 18 November 2024 (UTC)
:::Nevermind. I'm just disappointed in almost everyone around here these days; I'm not sure why I thought that wouldn't be true of you too. Consider it a rhetorical question. ] (]) 23:50, 18 November 2024 (UTC)
::::I'll cop to it being a suggestion inside of a question. I'm not sure Graham has been honest with himself, based on comments I have seen him making, and this was an attempt to nudge him in that direction, not to kick him when he's down, but I can see how it could come off that way. ] ] 00:00, 19 November 2024 (UTC)
:I agree, that was an utterly pointless and mean "question". If you want to say he should withdraw, just tell him he should elsewhere in the discussion or on his Talk—you're not earnestly asking if he's considered it. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 02:57, 19 November 2024 (UTC)

== ArbCom 2024 Elections voter message ==

<div class="ivmbox " style="margin-bottom: 1em; border: 1px solid #a2a9b1; background-color: #fdf2d5; padding: 0.5em; display: flex; align-items: center; ">
<div class="ivmbox-image noresize" style="padding-left:1px; padding-right:0.5em;">]</div>
<div class="ivmbox-text">
Hello! Voting in the ''']''' is now open until 23:59 (UTC) on {{#time:l, j F Y|{{Arbitration Committee candidate/data|2024|end}}-1 day}}. All ''']''' are allowed to vote. Users with alternate accounts may only vote once.

The ] is the panel of editors responsible for conducting the ]. 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 ], ], editing restrictions, and other measures needed to maintain our editing environment. The ] describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2024 election, please review ] and submit your choices on the ''']'''. If you no longer wish to receive these messages, you may add {{tlx|NoACEMM}} to your user talk page. <small>] (]) 00:15, 19 November 2024 (UTC)</small>

</div>
</div>
<!-- Message sent by User:Cyberpower678@enwiki using the list at https://en.wikipedia.org/search/?title=Misplaced Pages:Arbitration_Committee_Elections_December_2024/Coordination/MM/02&oldid=1258243447 -->

== ] ==

Hello, Just Step Sideways, and hello@] (who had kindly relisted the page)

Can I ask you to kindly undo your close of that AfD about film, please? There's not even '''one''' Delete !vote on that page.....and the nominator has asked for sources... that were provided (at AfD and on the page; it was vastly improved....(by me, fwiw)). Nor the nominator nor @], who had !voted Redirect (which had been the outcome of a first close, see ] where I asked Star Mississippi to relist it), have responded to new sources (added twice), true but that should not be considered a reason for deletion. At the very very least please consider a relist. Whatever your reading of the page is, it is absolutely impossible to consider there is a consensus to delete at all. Your closing statement does not indicate any reason for your decision, so I am assuming it is a mistake. Thank you in advance. -]. 00:40, 19 November 2024 (UTC)

:You are correct, I didn't mean to close that AFD at all. I was very confused for a minute there because an AFD I thought I had closed was still open and I couldn't figure out why. I clicked on the wrong one, I guess from scrolling too fast. I'll fix it now. ] ] 00:56, 19 November 2024 (UTC)
::Thank you very much! -]. 00:59, 19 November 2024 (UTC)
:::{{done}}. ] ] 01:00, 19 November 2024 (UTC)
::so you... stepped sideways to the wrong AfD? :)
::Thanks @] for the ping. Glad it was resolved in the interim while I was offline.I didn't watch the AfD after the relist so please do ping me if needed. ] ] 01:26, 19 November 2024 (UTC)
:::I read that in Mark E. Smith's voice.
:::When I'm closing AFDs I have the log for the whole day open, with only still-open discussions displayed, and there were two similarly long ones back-to-back. Not that it is anything but my fault but I assume that's how it happened. ] ] 01:55, 19 November 2024 (UTC)


== Why the name change? == == Unblock of ] ==


Since you recently unblocked that user with conditions following ], I am politely asking if you would be interested in my new user script, ], which allows you to temporary highlight those users in order to keep track of them! I am thinking that this situation could be a good use case for it. ] (] · ]) 18:18, 5 January 2025 (UTC)
Beeblebrox is a name I vaguely recall, and respect, though I don't think our areas of WP interest overlap much. Why have you changed it? ] (]) 09:46, 19 November 2024 (UTC)


:Interesting. So it would highlight edits to their user and talk pages? ] ] 20:21, 5 January 2025 (UTC)
:I had been contemplating it for some time. When I first registered this account, people, including myself, were generally unaware of best practices for online security. So we did things like name our account after one pet and use the other one's name as the password. Sadly, my cat Zaphod Beeblebrox passsed on some time ago. And I've been a longtime fan, due to my wife, of ] and since the death of ] I'de been contemplating a new username based on a fall song, so I went twith one of my favorites. ] ] 01:09, 20 November 2024 (UTC)
::It would highlight their username (like other user highlighter scripts), so you can spot them in, say, your watchlist/recent changes/discussions/etc. I'm thinking of maybe expanding the scope of the script so it can also mark users in the editing restriction log in the same way. ] (] · ]) 20:38, 5 January 2025 (UTC)
::Thank you for your explanation! I once observed an editor who changed his username as part of the process of standing for some official WP role. I'm reassured to know that you're not up to any such thing. ] (]) 11:21, 24 November 2024 (UTC)
:::At the time I changed it I did not anticipate ever running for ArbCom again, but after watching the committee struggle this past year I decided I'd run again. ] ] 20:08, 24 November 2024 (UTC) :::I'll give it a shot I suppose. ] ] 20:46, 5 January 2025 (UTC)
::::I installed it and bypassed my cache, but I'm not seeing anything. ] ] 20:53, 5 January 2025 (UTC)
:::::I'm now seeing it on other users' pages, but not the IP. Does it may be only work with accounts? ] ] 21:15, 5 January 2025 (UTC)
::::::Oh, that might be because it doesn't work on contribution links (which replace the user pages for IPs in some places), I'm going to fix that! Thanks! ] (] · ]) 22:05, 5 January 2025 (UTC)
:::::::It's actually looking to me like the user has to maybe be ''currently'' blocked? ] ] 22:07, 5 January 2025 (UTC)
::::::::Good catch, there was a <code><nowiki>!= "unblocked"</nowiki></code> instead of <code><nowiki>== "unblocked"</nowiki></code> somewhere in the code, I've fixed it! Does it work at ] now? ] (] · ]) 22:12, 5 January 2025 (UTC)
:::::::::That was it, working now. ] ] 22:23, 5 January 2025 (UTC)


== Now you see me, now you don't. ==
== cand q ==


I can't find any reporting on it, but over the last two days large parts of Alaska have apparently been subject to ] attacks. My entire ISP has gone offline at least four times in the last twenty-four hours. So, I may be right in the middle of something when I suddenly go offline, and I may or may not feel like resorting to using my mobile hotspot to get back online. ] ] 21:47, 5 January 2025 (UTC)
Thank you for standing for arbitrator. I am far away from it all (travel, mourning), not in the mood, so just an informal question you can answer or ignore:
* ''']''' chose ]er by five composers whose music was banned by the Nazis—], ], ], ] and ]—for a recital at the ].


What does this 2024 DYK tell you about infoboxes for classical composers in 2024? --] (]) 16:10, 19 November 2024 (UTC) :Thanks for letting the community know about your situation. Stay safe, Beebs. ] (]) 22:17, 5 January 2025 (UTC)
::I don't think my ISP is even the real target. They are a regional provider that mostly operates wireless-only residential connections. Their major infrastructure is piggybacked onto that of larger players', who I assume are the real targets. It's annoying, but if it's not Russia softening us up for an invasion that's probably all that will come of it, but I admit I do keep thinking of ]. ] ] 22:30, 5 January 2025 (UTC)


== Potential topic ban violation ==
== Explicit–Liz ==


Apologies in advance if this isn't the right place for this.
I don't think that thread is ready for closure. Maybe the immediate issue has been dealt with, but (per ]) it's a sign of a broader problem that really needs to be dealt with—the conflict's been dragging on for years, and if it isn't addressed, someday it's going to result in a block or desysop, which is the worst possible outcome for everyone. ] (]) 22:03, 21 November 2024 (UTC)


I was reading some military history articles and found my way to ] and saw that there was a ] for the user ] adding "decisive" to the result section of the infobox going against ].<br>
:I guess I think, given the various mitigating factors, that nothing concrete was going to come of this. The egregious personal attack and the confusion/lack of information regarding the supressed content make it extremely unlikely. Technically, no discussion should be had, ever, on-wiki regarding supressed content. ] ] 22:15, 21 November 2024 (UTC)
I was going to leave a link to the relevant MOS section on their talk page since the revert didn't give an explanation and I saw a large unblock discussion resulting in a topic ban on Azerbaijan and other related topics. Since the edit would seem to go against a restriction that you imposed, I felt like I should let you know. I suppose it could be considered a minor breach, but I figured I should perhaps inform someone lest it get out of hand.
::Perhaps that's true for the wheel-warring/suppression, but the point I was trying to make in my comment was that the problem goes well beyond the most recent incident—and I think that point deserves engagement rather than a closure 20 minutes later. ] (]) 22:25, 21 November 2024 (UTC)
:::I see the diffs you posted, but even without them, it is obvious to anyone who just read that single thread that these two don't get along and have not for some time. Absent any sort of explicit proposal I'm afraid I really don't see the point. ] ] 22:51, 21 November 2024 (UTC)
::::I suggest waiting to see if the issue continues before anyone makes an explicit proposal, or even an Explicit proposal. ] (]) 22:56, 21 November 2024 (UTC)
:::::I really enjoy how much likelier you are to comment on a subject if you can sneak in a cheap pun.
:::::And I agree, I think this thread was a shot across the bow to both of them to cut this out. Let's see if they abide by that. ] ] 23:01, 21 November 2024 (UTC)


Sorry if I'm overstepping my bounds! (I mainly just revert vandalism and don't report users too often.) ] (]) 08:17, 6 January 2025 (UTC)<br>
== Question re that ANI discussion just now ==


:And as I'm scrolling back up your page, I see you already had a related discussion about this user and keeping track of their edits. My apologies if I took up your time on something you were already aware of... ] (]) 08:22, 6 January 2025 (UTC)
I thought about leaving Tercer a first-and-only NPA warning for ] although if I were an admin, it would have been enough for me to block them. You're obviously right that a discussion needs to happen but I can't imagine it going anywhere as long one editor feels comfortable telling another "''you don't know anything''" and whatever else. Thoughts? <b style="font-family: Segoe Script;">'']]]''</b> 21:04, 23 November 2024 (UTC)
::Not at all, I was not aware of this and your alerting me to it is appreciated. I'm writing something up on their talk pages right now. Thank you. ] ] 08:25, 6 January 2025 (UTC)
:::Glad to be of help! I read through that whole discussion and it felt like it'd be a waste to throw away all that work you folks did by letting things potentially go too far. ] (]) 08:53, 6 January 2025 (UTC)


== Deletion review for ] ==
:That's a fair point, I've added a bit on that specifically to the closing message. ] ] 21:13, 23 November 2024 (UTC)
An editor has asked for ] of ]. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review.<!-- Template:DRV notice --> –] (]]) 04:39, 7 January 2025 (UTC)


==You've got mail!== == RfC notice ==
{{You've got mail}} <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 00:03, 24 November 2024 (UTC)


Hello, this notice is for everyone who took part in the ]. I have started a new RfC on the subject. If you would like to participate please follow this link: {{slink|Misplaced Pages talk:What Misplaced Pages is not|RfC on WP:NOT and British Airways destinations}}. ] (]) 00:37, 8 January 2025 (UTC)
== Another article for deletion ==


== Please undo ==
Regarding the deletion of ], shortly after the AfD was initiated it was moved from ] (see ). The latter article has not been deleted, and even retains the original AfD notice. Probably a 'feature' of the Misplaced Pages deletion software, but it and its Talk page also need to be deleted. Thanks. ] (]) 02:05, 24 November 2024 (UTC)


Hi, Zaphod, how are you! Sorry, but I believe ] to have been a mistake and would be grateful if you'd consider undoing it. I'm still trying to establish (in dilatory mode) whether a CCI is going to be necessary for this user, who has clocked up a good number of violations of our copyright policy. a further example, will blank and list in a moment.
:Huh, I thought the XFD closer would handle that but I guess not. I'll zap it now. ] ] 02:13, 24 November 2024 (UTC)


Not sure why you thought I might not wish to be consulted about the unblock in the normal way. Had you done so, I'd have said there's no possible benefit in unblocking a user with an imperfect grasp of copyright policy, and considerable scope for harm to the project – the CCI backlog counter hasn't been updated for a while, but last time I looked was at about 78000 pages. There's just a tiny handful of people working on that. ] (]) 22:54, 11 January 2025 (UTC)
== "I don't think I've ever actually seen that before." ==
About . There was also a few weeks ago for interest. It seems it happens, but I don't know how often. ] (]) 06:08, 24 November 2024 (UTC)


:I generally do not agree with or adhere to the idea that asking the blocking admin should be a ''de facto'' part of reviewing unblock requests. (in fact, unrelated to this specific situation, I was pondering a draft of a policy change to remove or alter language to that effect in the blocking policy at the exact moment you posted your concerns here) , I'll do it when something is unclear to me, I don't feel I'm seeing the context, etc, but this was a fairly straightforward COPYVIO block. I don't mean to imply in any way that it was wrong or unjustified, it looks like a good block to me.
:I'm fairly sure those are both the same person, fwiw. – ] 06:39, 24 November 2024 (UTC)
:However, it appears to me that the user simply did not understand exactly how copyright works, and how seriously it is taken on Misplaced Pages. This is one of several areas where Misplaced Pages's rules and expectations are ''considerably'' stricter than most of the rest of the modern internet, so I believe if a relatively new user makes a reasonable claim that they now understand the situation, a second chance is warranted, even if they have made rather egregious errors in the past.
::Prety weak to not realize that's never going to work, but I've given up being sursrised at such things, ] ] 08:18, 24 November 2024 (UTC)
:I think we've become a bit too unwilling to just give second chances when a user, as this one did, apologizes and commits not to repeat the behaviors that led to the block, and explains clearly how they intend to do that.
::I hope you are right. Apart from being quite funny, it means Misplaced Pages gets a free RFP testing service and everyone gets to watch if they can figure out how to find a method that works. ] (]) 09:42, 24 November 2024 (UTC)
:While I can understand your reservations about it, {{tq|imperfect grasp of copyright policy}} probably applies to a great many users. Some aspects of how copyright works are very straightforward, others have substantial grey area. I certainly can't claim to have a perfect understanding of it. I think that, realistically, the bar is somewhere around "a grasp of the general idea that you can't just copy someone else's work and repost it like it was your own work" and this user is indicating they now have at least that level of understanding. ] ] 23:24, 11 January 2025 (UTC)
::Hi both, I've referred this to ANI at ]. -- ] (]) 07:04, 12 January 2025 (UTC)
:::Hmmm, disappointing... Our ] is crystal-clear: "{{teal|Except in cases of unambiguous error or significant change in circumstances dealing with the reason for blocking, administrators should avoid unblocking users without first attempting to contact the blocking administrator to discuss the matter}}". You're welcome to disagree with that of course, and welcome to try to change it if you wish, but for as long as you're an administrator you're expected to adhere to it. And if you don't like the policy, do it because it's just ordinary good manners.
:::I have some limited sympathy for your second-chance crusade; as you surely know, we have a useful ] for just that purpose.
:::Anyway, thanks for drawing my attention back to that user, now CU-blocked for further socking. Regards, ] (]) 12:32, 12 January 2025 (UTC)
::::{{ping|Justlettersandnumbers}} How is it '''not''' a "]" when a user blocked for caused by their ignorance of familiarizes themselves with , apologizes for and promises to stop ? I'm very confused. ] (]) 16:14, 12 January 2025 (UTC)
::{{tps}} Unrelated to the Aguahrz case: Beeblebrox, you said {{xt|I was pondering a draft of a policy change to remove or alter language to that effect in the blocking policy at the exact moment you posted your concerns here}}. That would be a welcome improvement. A significant amount of admins consider unblocks to be, to some extent, a reversal of the original admin's block. In my view, any legitimate unblock request will come with new information or developments, even just the passage of time and an undertaking not to repeat the conduct. It follows that considering the request is looking at a fresh situation with new considerations, not the same situation the admin before was looking at. Policy should make clear that admins don't own the unrelated situation just because the same user is involved. Clearly the question is one of degree, and unblocking just because the original block was bad is another case and likely an admin action reversal. ] 11:10, 13 January 2025 (UTC)


== RE: Deletion decision of Wednesday 13 ==
== ] processing ==


I would like to challenge the ]. The participation was minimal, and there was no real reasoning as to why an article subject supported by at least four reliable sources, possibly five, isn't notable. The two other participants said they didn't think that was enough, but considering that multiple independent sources discuss the album, I don't see how that's convincing.--] (] &#124; ]) 23:17, 12 January 2025 (UTC)
There are a few talkpage archives still lingering. ] (]) 00:30, 25 November 2024 (UTC)


:The closers job is to do their best to read a consensus. Participation was minimal, no argument there, which unfortunately often makes consensus less clear.
:Good catch, zapped them all. Darn nonstandard talk page numbering. ] ] 01:03, 25 November 2024 (UTC)
:This was been open for three weeks, which is generally considered the maximum amount of relisting unless there are exceptional circumstances. The nominator and the one other participant besides yourself agreed on redirecting. In the five days the AFD remained open after that, neither you nor anyone else voiced any sort of objection to the idea. Redirecting in cases of marginal notability is generally considered a good alternative to deletion as it allows the subject to still be covered ''somewhere'', just without a stand-alone article. Any content worth merging can still be pulled out of the page history.
::Thanks for the quick fix! ] (]) 01:08, 25 November 2024 (UTC)
:So, I think my close was reasonable and within the bounds of admin discretion. ] ] 00:12, 13 January 2025 (UTC)
::I thought my keep vote was sufficient, I wasn't aware that I would then have to specifically voice objections to each contrary argument. I've been trying to avoid getting argumentative as I've of late been prone to getting into protracted, repetitive arguments. I definitely do appreciate the redirect rather than a hard delete. I just fail to see what justified it in light of the article meeting GNG standards.--] (] &#124; ]) 12:32, 13 January 2025 (UTC)


== hello ==
== ] ==


{{You've got mail}}
Why delete? There's a clear consensus that it exists, just not that it's notable. That's the perfect sort of situation for a redirect or merge. The only argument against a redirect or merge--it's not mentioned at the target--is a very surmountable problem. ATDs, by policy, should be prioritized over deletion, even when there's a strong consensus against retaining an article in its current form. ] (]) 02:49, 26 November 2024 (UTC)
Thank you so much for your time! Have a great week! ] (]) 15:21, 13 January 2025 (UTC)


== Granting extended-confirmed early ==
:@] {{tpw}} To be honest, I'm wondering why it was closed after there were two !votes that technically disagreed with each other instead of relisted. ] ] ] 04:40, 26 November 2024 (UTC)
::I feel like I tried to explain this when making the close. Despite the differing perspectives on what it meant, I did see a consensus that it was not notable and there were no sources. I do not believe that ] mandates that we ''must'' do a redirect in such circumstances. There's not really anything we can say without a single reliable source. The lack of reliable sourcing strongly suggests this is ], or at best almost totally unknown even to players otherwise familiar with canasta. ] ] 18:14, 26 November 2024 (UTC)
:::If you want to infer that it's made up, then I recommend you do your own BEFORE-like search before making such a supposition the basis for any action. There used to be a strain of thought that would excoriate closers for doing this, but I strongly encourage it: I believe it's the best way to see for yourself whether the !votes are reasonable. As I noted in the AfD, I saw stuff with the "ponytal canasta" name in it all over the Internet: {{tq|A quick survey of google, gnews, and gbooks shows there are plenty of references to this to verify it exists, even though I see nothing to suggest it is notable.}} For example, shows that there are out-of-print scoresheets for this variant that were sold by and reviewed on Amazon as late as mid-2022. Definitely doesn't contribute to notability, but just as definitely shows--especially with all the other NN ghits--that this isn't MADEUP, even if I can't support any argument of notability. ] (]) 07:15, 27 November 2024 (UTC)
:::Oh, and one thing: an entry in an already notable article doesn't need an RS suitable for notability, just one able to satisfy V, which non-controversial SPS'es can do just fine. ] (]) 07:16, 27 November 2024 (UTC)


Hello. Regarding ], my understanding based on ] is that administrators are free to grant {{code|extendedconfirmed}} as they see fit (see ] too). If you're nervous about them editing the relevant topic areas, you could grant it on the condition of staying away, I guess.
== UAA ==


This isn't specifically about that request, which didn't have much chance of success, but just a general point because I know that you deal with a lot of requests on that page. Thanks, ] (]) 02:10, 14 January 2025 (UTC)
Hey since you are around, can you check if the edits this was trying to make at UAA was a valid report? An user warned them on their talk page, but, like me, the user cannot actually see what the edits were and I have tried reporting some accounts before and being disallowed by a filter because the username was bad.<br>
This is also the IP that made the extensive (unsigned) report that you just removed (so it's probably related to that...). &ndash; ] (]) (]) 19:00, 26 November 2024 (UTC)


:I... don't think ARCA is relevant anymore. As is seemingly being established by the committee right now ], the committee is no longer in control in any way of this user right.
:Looks like they were trying to comment on that report and kept tripping multiple edit filters designed to stop LTAs. ] ] 19:37, 26 November 2024 (UTC)
:That being said, I admit I'm not entirely clear what the deal is with the translation tool, but I assume the community is deliberately restricting it to those that have met the minimum requirements. ] ] 02:34, 14 January 2025 (UTC)
::I don't follow, sorry. Nothing's been established at ''Palestine–Israel articles 5'' yet because as of writing this, an outright majority has rejected those changes. As the PD talk page makes clear, the Committee never had control over the user group: it created the 500/30 restriction, the Community created the user group, then the Committee modified the restriction to match the user group because based on a literal interpretation of it, accounts without 500/30 couldn't edit in restricted areas. At ''Palestine–Israel'', we could change the restriction to only allowing page movers to edit in it or whatever, but that wouldn't give us retroactive control over the user group.{{pb}}I had assumed that your reluctance to grant extended-confirmed early was over the ECR. Maybe I was wrong? For what it's worth, I think that ] was a decent example of granting extended-confirmed early: trusted on other projects and not likely to cause trouble over here. I think that the Community would be happy with a globally experienced user with fluent English being allowed access to the translation tool{{snd}}they can already translate with it to draft/userspace without extended-confirmed, so it's not like extended-confirmed makes a big difference there (see ], which I just created using my alternative account and can easily move into mainspace). ] (]) 03:55, 14 January 2025 (UTC)

Latest revision as of 03:55, 14 January 2025



tracks of previous discussions
Archive 1Archive 2Archive 3
Archive 4Archive 5Archive 6
Archive 7Archive 8Archive 9
Archive 10Archive 11Archive 12
Archive 13Archive 14Archive 15
Archive 16Archive 17Archive 18
Archive 19Archive 20Archive 21
Archive 22Archive 23Archive 24
Archive 25Archive 26Archive 27
Archive 28Archive 29Archive 30
Archive 31Archive 32Archive 33
Archive 34Archive 35Archive 36
Archive 37Archive 38Archive 39
Archive 40Archive 41Archive 42
Archive 43Archive 44Archive 45
Archive 46Archive 47Archive 48
Archive 49Archive 50Archive 51
Archive 52

RfA candidate S O N S% Ending (UTC) Time left Dups? Report
RfB candidate S O N S% Ending (UTC) Time left Dups? Report

No RfXs since 17:37, 25 December 2024 (UTC).—Talk to my owner:Online


please stay in the top three tiers

XFD backlog
V Oct Nov Dec Jan Total
CfD 0 0 3 27 30
TfD 0 0 0 15 15
MfD 0 0 0 1 1
FfD 0 0 5 9 14
RfD 0 0 27 34 61
AfD 0 0 0 0 0


Arbitration Committee proceedings Case requests

Currently, there are no requests for arbitration.

Open cases
Case name Links Evidence due Prop. Dec. due
Palestine-Israel articles 5 (t) (ev / t) (ws / t) (pd / t) 21 Dec 2024 11 Jan 2025
Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Clarification and Amendment requests

Currently, no requests for clarification or amendment are open.

Arbitrator motions
Motion name Date posted
Arbitrator workflow motions 10 January 2025

Skip to top Skip to bottom

Why did you redirect Mary-Catherine Deibel?

I don’t understand why you redirected Mary-Catherine Deibel. Those who proposed this gave no reasons and no editor responded to my analysis and additions to the article. Why not relist or declare no consensus? Nnev66 (talk) 01:35, 1 January 2025 (UTC)

It was already relisted once specifically to allow for such a response, and none was forthcoming. It can therefore be assumed that your point was not found persuasive, the only comment coming after being in favor of merging or redirecting, and the only other "keep" comment was self-identified as weak. All other comments indicated opposition to a stand-alone article. I don't think another relist was likely to change that. Beeblebrox 02:03, 1 January 2025 (UTC)
It's my understanding that in AfD discussions, the outcome is not from a majority vote but rather from the content of the discussion. There was zero justification by any of the editors voting to delete or redirect. The nominator wrote "A local celebrity only, with an interview and an obituary in The Boston Globe." This was not true in my estimation. I took my time to carefully evaluate the sources and add to the article. I noted that from my reading all the sources except the interview and one other met WP:SIGCOV in WP:RS. No one responded to that. After the first relisting, only one editor responded and did not give any justification for their vote. If others could explain why these sources shouldn't count towards notability that would be one thing, but they didn't. Ideally you would open this back up and ask for a direct evaluation of the references. If no one responds directly to the references, to me this is a "no consensus" decision. Note I'd never heard of this person before the AfD so my concern here is process. Nnev66 (talk) 16:14, 1 January 2025 (UTC)
I believe I reasonably interpreted the consensus of the discussion. I will note that the lone "speedy delete" comment was not considered as there was no explanation whatsoever of what CSD would apply. Any content that may be worth keeping can be pulled from the page history and merged at the redirect target. Beeblebrox 21:23, 1 January 2025 (UTC)
I'm disappointed that you didn't address my WP:NOTARG concern as I'm not sure how you could interpret consensus without knowing why each editor voted the way they did.... I didn't realize the history with the page markup was available from the "Articles for deletion" subject page so thank you for noting that. Nnev66 (talk) 23:30, 1 January 2025 (UTC)

Username query

Hi Beeblebrox. I'm asking you about this because you're the most recent admin (at least at the time of this post) to have been active at WP:UAA. Do you think there's a WP:CORPNAME or WP:ISU problem with respect to Socceroos TV? I just want a second opinion before adding {{uw-username}} template to their user talk page. -- Marchjuly (talk) 08:45, 2 January 2025 (UTC)

Unless there is an actual organization by that name, it probably isn't an issue. Beeblebrox 18:53, 2 January 2025 (UTC)
Thanks for taking a look. I did some Googling and didn't come up with anything; so, I'll just AGF here and pursue things no further. -- Marchjuly (talk) 22:07, 2 January 2025 (UTC)

Request

Hello, is there any way I can gain access to the history of the deleted Muslim migrations to Ottoman Palestine article? Makeandtoss (talk) 11:09, 2 January 2025 (UTC)

 Done It is at User:Makeandtoss/Muslim migrations to Ottoman Palestine. I feel I would be remiss if I didn't mention that several participants at the AFD found serious issues with the way this was sourced and that the content did not reflect an accurate reading of the sources. Beeblebrox 19:00, 2 January 2025 (UTC)
Thanks, and don't worry, this is the reason why I requested the version, for further examination of these issues, namely sockpuppetry, not to restore the content. Makeandtoss (talk) 19:42, 2 January 2025 (UTC)
Ah, gotcha. Beeblebrox 19:45, 2 January 2025 (UTC)
So a user has moved the article to the mainspace. Can this please be reverted and locked until the evidence at the SPI is evaluated? Makeandtoss (talk) 14:15, 5 January 2025 (UTC)
Looks like it was already moved back, I will go ahead and move-protect it. Beeblebrox 08:35, 6 January 2025 (UTC)
Thanks! Makeandtoss (talk) 10:56, 6 January 2025 (UTC)

Administrators' newsletter – January 2025

News and updates for administrators from the past month (December 2024).

Administrator changes

added Sennecaster
readded
removed

CheckUser changes

added
readded Worm That Turned
removed Ferret

Oversight changes

added
readded Worm That Turned

Guideline and policy news

Technical news

  • The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.

Arbitration

Miscellaneous


Sent by MediaWiki message delivery (talk) 15:46, 5 January 2025 (UTC)

Unblock of User:82.44.247.44

Since you recently unblocked that user with conditions following the discussion in which we both took part, I am politely asking if you would be interested in my new user script, User:Chaotic Enby/RecentUnblockHighlighter.js, which allows you to temporary highlight those users in order to keep track of them! I am thinking that this situation could be a good use case for it. Chaotic Enby (talk · contribs) 18:18, 5 January 2025 (UTC)

Interesting. So it would highlight edits to their user and talk pages? Beeblebrox 20:21, 5 January 2025 (UTC)
It would highlight their username (like other user highlighter scripts), so you can spot them in, say, your watchlist/recent changes/discussions/etc. I'm thinking of maybe expanding the scope of the script so it can also mark users in the editing restriction log in the same way. Chaotic Enby (talk · contribs) 20:38, 5 January 2025 (UTC)
I'll give it a shot I suppose. Beeblebrox 20:46, 5 January 2025 (UTC)
I installed it and bypassed my cache, but I'm not seeing anything. Beeblebrox 20:53, 5 January 2025 (UTC)
I'm now seeing it on other users' pages, but not the IP. Does it may be only work with accounts? Beeblebrox 21:15, 5 January 2025 (UTC)
Oh, that might be because it doesn't work on contribution links (which replace the user pages for IPs in some places), I'm going to fix that! Thanks! Chaotic Enby (talk · contribs) 22:05, 5 January 2025 (UTC)
It's actually looking to me like the user has to maybe be currently blocked? Beeblebrox 22:07, 5 January 2025 (UTC)
Good catch, there was a != "unblocked" instead of == "unblocked" somewhere in the code, I've fixed it! Does it work at User talk:82.44.247.44 now? Chaotic Enby (talk · contribs) 22:12, 5 January 2025 (UTC)
That was it, working now. Beeblebrox 22:23, 5 January 2025 (UTC)

Now you see me, now you don't.

I can't find any reporting on it, but over the last two days large parts of Alaska have apparently been subject to DoS attacks. My entire ISP has gone offline at least four times in the last twenty-four hours. So, I may be right in the middle of something when I suddenly go offline, and I may or may not feel like resorting to using my mobile hotspot to get back online. Beeblebrox 21:47, 5 January 2025 (UTC)

Thanks for letting the community know about your situation. Stay safe, Beebs. BusterD (talk) 22:17, 5 January 2025 (UTC)
I don't think my ISP is even the real target. They are a regional provider that mostly operates wireless-only residential connections. Their major infrastructure is piggybacked onto that of larger players', who I assume are the real targets. It's annoying, but if it's not Russia softening us up for an invasion that's probably all that will come of it, but I admit I do keep thinking of Leave the World Behind. Beeblebrox 22:30, 5 January 2025 (UTC)

Potential topic ban violation

Apologies in advance if this isn't the right place for this.

I was reading some military history articles and found my way to Battle of Baku and saw that there was a revert for the user 82.44.247.44 adding "decisive" to the result section of the infobox going against MOS:DECISIVE.
I was going to leave a link to the relevant MOS section on their talk page since the revert didn't give an explanation and I saw a large unblock discussion resulting in a topic ban on Azerbaijan and other related topics. Since the edit would seem to go against a restriction that you imposed, I felt like I should let you know. I suppose it could be considered a minor breach, but I figured I should perhaps inform someone lest it get out of hand.

Sorry if I'm overstepping my bounds! (I mainly just revert vandalism and don't report users too often.) Sigma440 (talk) 08:17, 6 January 2025 (UTC)

And as I'm scrolling back up your page, I see you already had a related discussion about this user and keeping track of their edits. My apologies if I took up your time on something you were already aware of... Sigma440 (talk) 08:22, 6 January 2025 (UTC)
Not at all, I was not aware of this and your alerting me to it is appreciated. I'm writing something up on their talk pages right now. Thank you. Beeblebrox 08:25, 6 January 2025 (UTC)
Glad to be of help! I read through that whole discussion and it felt like it'd be a waste to throw away all that work you folks did by letting things potentially go too far. Sigma440 (talk) 08:53, 6 January 2025 (UTC)

Deletion review for Guite people

An editor has asked for a deletion review of Guite people. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. –LaundryPizza03 (d) 04:39, 7 January 2025 (UTC)

RfC notice

Hello, this notice is for everyone who took part in the 2018 RfC on lists of airline destinations. I have started a new RfC on the subject. If you would like to participate please follow this link: Misplaced Pages talk:What Misplaced Pages is not § RfC on WP:NOT and British Airways destinations. Sunnya343 (talk) 00:37, 8 January 2025 (UTC)

Please undo

Hi, Zaphod, how are you! Sorry, but I believe this to have been a mistake and would be grateful if you'd consider undoing it. I'm still trying to establish (in dilatory mode) whether a CCI is going to be necessary for this user, who has clocked up a good number of violations of our copyright policy. Here's a further example, will blank and list in a moment.

Not sure why you thought I might not wish to be consulted about the unblock in the normal way. Had you done so, I'd have said there's no possible benefit in unblocking a user with an imperfect grasp of copyright policy, and considerable scope for harm to the project – the CCI backlog counter hasn't been updated for a while, but last time I looked was at about 78000 pages. There's just a tiny handful of people working on that. Justlettersandnumbers (talk) 22:54, 11 January 2025 (UTC)

I generally do not agree with or adhere to the idea that asking the blocking admin should be a de facto part of reviewing unblock requests. (in fact, unrelated to this specific situation, I was pondering a draft of a policy change to remove or alter language to that effect in the blocking policy at the exact moment you posted your concerns here) , I'll do it when something is unclear to me, I don't feel I'm seeing the context, etc, but this was a fairly straightforward COPYVIO block. I don't mean to imply in any way that it was wrong or unjustified, it looks like a good block to me.
However, it appears to me that the user simply did not understand exactly how copyright works, and how seriously it is taken on Misplaced Pages. This is one of several areas where Misplaced Pages's rules and expectations are considerably stricter than most of the rest of the modern internet, so I believe if a relatively new user makes a reasonable claim that they now understand the situation, a second chance is warranted, even if they have made rather egregious errors in the past.
I think we've become a bit too unwilling to just give second chances when a user, as this one did, apologizes and commits not to repeat the behaviors that led to the block, and explains clearly how they intend to do that.
While I can understand your reservations about it, imperfect grasp of copyright policy probably applies to a great many users. Some aspects of how copyright works are very straightforward, others have substantial grey area. I certainly can't claim to have a perfect understanding of it. I think that, realistically, the bar is somewhere around "a grasp of the general idea that you can't just copy someone else's work and repost it like it was your own work" and this user is indicating they now have at least that level of understanding. Beeblebrox 23:24, 11 January 2025 (UTC)
Hi both, I've referred this to ANI at WP:ANI#Beeblebrox and copyright unblocks. -- asilvering (talk) 07:04, 12 January 2025 (UTC)
Hmmm, disappointing... Our policy is crystal-clear: "Except in cases of unambiguous error or significant change in circumstances dealing with the reason for blocking, administrators should avoid unblocking users without first attempting to contact the blocking administrator to discuss the matter". You're welcome to disagree with that of course, and welcome to try to change it if you wish, but for as long as you're an administrator you're expected to adhere to it. And if you don't like the policy, do it because it's just ordinary good manners.
I have some limited sympathy for your second-chance crusade; as you surely know, we have a useful template for just that purpose.
Anyway, thanks for drawing my attention back to that user, now CU-blocked for further socking. Regards, Justlettersandnumbers (talk) 12:32, 12 January 2025 (UTC)
@Justlettersandnumbers: How is it not a "significant change in circumstances dealing with the reason for blocking" when a user blocked for caused by their ignorance of familiarizes themselves with , apologizes for and promises to stop ? I'm very confused. 78.28.44.127 (talk) 16:14, 12 January 2025 (UTC)
(talk page stalker) Unrelated to the Aguahrz case: Beeblebrox, you said I was pondering a draft of a policy change to remove or alter language to that effect in the blocking policy at the exact moment you posted your concerns here. That would be a welcome improvement. A significant amount of admins consider unblocks to be, to some extent, a reversal of the original admin's block. In my view, any legitimate unblock request will come with new information or developments, even just the passage of time and an undertaking not to repeat the conduct. It follows that considering the request is looking at a fresh situation with new considerations, not the same situation the admin before was looking at. Policy should make clear that admins don't own the unrelated situation just because the same user is involved. Clearly the question is one of degree, and unblocking just because the original block was bad is another case and likely an admin action reversal. arcticocean ■ 11:10, 13 January 2025 (UTC)

RE: Deletion decision of Wednesday 13

I would like to challenge the decision to redirect Skeletons. The participation was minimal, and there was no real reasoning as to why an article subject supported by at least four reliable sources, possibly five, isn't notable. The two other participants said they didn't think that was enough, but considering that multiple independent sources discuss the album, I don't see how that's convincing.--3family6 (Talk to me | See what I have done) 23:17, 12 January 2025 (UTC)

The closers job is to do their best to read a consensus. Participation was minimal, no argument there, which unfortunately often makes consensus less clear.
This was been open for three weeks, which is generally considered the maximum amount of relisting unless there are exceptional circumstances. The nominator and the one other participant besides yourself agreed on redirecting. In the five days the AFD remained open after that, neither you nor anyone else voiced any sort of objection to the idea. Redirecting in cases of marginal notability is generally considered a good alternative to deletion as it allows the subject to still be covered somewhere, just without a stand-alone article. Any content worth merging can still be pulled out of the page history.
So, I think my close was reasonable and within the bounds of admin discretion. Beeblebrox 00:12, 13 January 2025 (UTC)
I thought my keep vote was sufficient, I wasn't aware that I would then have to specifically voice objections to each contrary argument. I've been trying to avoid getting argumentative as I've of late been prone to getting into protracted, repetitive arguments. I definitely do appreciate the redirect rather than a hard delete. I just fail to see what justified it in light of the article meeting GNG standards.--3family6 (Talk to me | See what I have done) 12:32, 13 January 2025 (UTC)

hello

Hello, Beeblebrox. Please check your email; 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 remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

Thank you so much for your time! Have a great week! Phoebezz22 (talk) 15:21, 13 January 2025 (UTC)

Granting extended-confirmed early

Hello. Regarding comments like this at PERM, my understanding based on this 2022 ARCA is that administrators are free to grant extendedconfirmed as they see fit (see discussion at PERM too). If you're nervous about them editing the relevant topic areas, you could grant it on the condition of staying away, I guess.

This isn't specifically about that request, which didn't have much chance of success, but just a general point because I know that you deal with a lot of requests on that page. Thanks, Sdrqaz (talk) 02:10, 14 January 2025 (UTC)

I... don't think ARCA is relevant anymore. As is seemingly being established by the committee right now here, the committee is no longer in control in any way of this user right.
That being said, I admit I'm not entirely clear what the deal is with the translation tool, but I assume the community is deliberately restricting it to those that have met the minimum requirements. Beeblebrox 02:34, 14 January 2025 (UTC)
I don't follow, sorry. Nothing's been established at Palestine–Israel articles 5 yet because as of writing this, an outright majority has rejected those changes. As the PD talk page makes clear, the Committee never had control over the user group: it created the 500/30 restriction, the Community created the user group, then the Committee modified the restriction to match the user group because based on a literal interpretation of it, accounts without 500/30 couldn't edit in restricted areas. At Palestine–Israel, we could change the restriction to only allowing page movers to edit in it or whatever, but that wouldn't give us retroactive control over the user group.I had assumed that your reluctance to grant extended-confirmed early was over the ECR. Maybe I was wrong? For what it's worth, I think that this was a decent example of granting extended-confirmed early: trusted on other projects and not likely to cause trouble over here. I think that the Community would be happy with a globally experienced user with fluent English being allowed access to the translation tool – they can already translate with it to draft/userspace without extended-confirmed, so it's not like extended-confirmed makes a big difference there (see this, which I just created using my alternative account and can easily move into mainspace). Sdrqaz (talk) 03:55, 14 January 2025 (UTC)