Wikipedia:Administrators' noticeboard

I made an appeal last week. I didn't expect the discussion to go beyond the topic and it eventually was closed a couple of days later. I'll try again and answer the allegations on my previous appeal.

I already removed this reminder a couple of years ago after I was told that it and I realized I was too harsh with that. I have moved on from that long time ago. When some editors convinced me to participate in the ANI, it took me some time to think of what to say there. Unfortunately, I wasn't able to do so by the time a consensus was made.

I really have moved on from my past troubles and learned from them. Believe me or not, I'm very honest with what I said, especially in my previous appeal.

I'm appealing (again) for my topic ban from closing AfDs to be lifted. From hereon, I'll be careful in closing deletion discussions. Whenever anyone challenges any of my closures, I'll revert it immediately and leave it for other editors to relist or close it. I really promise to be careful in closing them. That way, I won't get myself into trouble like before.

Proposal: Lifting Superastig's topic-ban from closing AfDs

ASTIG😎🙃 14:30, 13 July 2023 (UTC)[reply]

Proposal: User:Superastig topic banned from appealing their topic ban on closing AFDs for six months

• Due to the cluelessness shown above, support as proposer. Boing! said Zebedee (talk) 14:48, 13 July 2023 (UTC)[reply]
• Support. As I said above, this is getting close to
  WP:IDHT. To be blunt, find other areas to work on Wikipedia for now. Come back next year to see if the community would be more open. RickinBaltimore (talk) 14:53, 13 July 2023 (UTC)[reply
  ]
• Support 6 months may be too short a wait given the substantial conduct and communication issues but better than nothing. Abecedare (talk) 16:59, 13 July 2023 (UTC)[reply]
• Now, here's an interesting thing. As I read our rules and the precedents behind them, I don't think there's anything to stop Superastig from appealing this ban on appealing the first ban. We could get very deep in a recursive loop of banning appealing the previous ban banning appealing the ban before that. Nevertheless, I support this appealing ban. — Trey Maturin™ 18:03, 13 July 2023 (UTC)[reply]

  At that point, we would be far into

  WP:IDHT territory. ~UN6892 ^t_c 18:28, 13 July 2023 (UTC)[reply

  ]

  Don't give 'em

  ideas, Trey! :) Abecedare (talk) 18:33, 13 July 2023 (UTC)[reply

  ]

  Hmm, yes, I missed off "recursively construed" ;-) Boing! said Zebedee (talk) 19:17, 13 July 2023 (UTC)[reply]

  If he appeals the appeal ban then I for one will certainly be re-cursing. Many of you are familiar with my special talents along those lines. EEng 00:40, 14 July 2023 (UTC)[reply]

• Support, with enforcement mechanism. Appealing a second time within a week is disruptive, but Trey Maturin has a point that these restrictions have in recent times become meaningless. As such, I support with the addition of an enforcement mechanism: Should Superastig appeal early then said appeal is to be immediately closed and Superastig blocked for at least one week, with the block length to escalate should additional early appeals be made. BilledMammal (talk) 03:52, 14 July 2023 (UTC)[reply]
• Support - this should be self-evident even without a formal ban. Any discussion result should never be appealed in a shorter amount of time unless it can be shown either that the discussion was extremely unfair or closed improperly; or that some new fact, which either occured or was discovered after the discussion was essentially over, is provably relevant to the point that several users likely would have voted differently as a result. Animal lover |666| 08:54, 14 July 2023 (UTC)[reply]
• Support and lets make it a year. The users comments above dont appear to have any of the required maturity to seek a removal of the ban, but doing it anyhow. Jtbobwaysf (talk) 10:36, 14 July 2023 (UTC)[reply]
• Support while I still think further sanctions are needed, commenting here to endorse some action. This user is more interested in wasting our time then changing their behavior. Since it appears a broader AfD ban won't pass, this will give the user sufficient time to show productive editing that could merit lifting of ban. Star Mississippi 13:52, 14 July 2023 (UTC)[reply]
• Support Girth Summit told Astig in their talk page that "The restriction is indefinite, but may be appealed at AN no sooner than six months from today." I guess Astig was given the time frame of six months from the day they were Tbanned. Since their deadline is sometime within this month, I don't think they will be able to appeal anymore (not even after another six months) after this one. Correct me if I'm wrong. SBKSPP (talk) 01:51, 15 July 2023 (UTC)[reply]

  @SBKSPP: I think you're misreading "no sooner" as "no later". -- Tamzin^{[cetacean needed]} (she|they|xe) 03:36, 15 July 2023 (UTC)[reply]

  Oh shoot. I thought they're the same. Meaning "at least six months"? Then that means Astig is wrong here since they appealed sometime after five months. Changing my vote. SBKSPP (talk) 03:06, 18 July 2023 (UTC)[reply]

• Support a ban of no longer than six months with whatever enforcement tools are available. Superastig’s continued poor conduct shows no signs of changing so no point in continued appeals of his original ban at this time. Frank Anchor 17:54, 15 July 2023 (UTC)[reply]
• Support I don't see their behavior changing in any meaningful way, given their immediate leap to appealing again. I can't legitimately see anyone being too eager to accept an appeal for at least a few months, and certainly not before Superastig can demonstrate that they understand
  WP:NAC. EggRoll97 ^(talk) 05:25, 16 July 2023 (UTC)[reply
  ]
• Support After several
  WP:BADNAC. I don't have faith that he can do it properly. scope_creep^Talk 16:30, 19 July 2023 (UTC)[reply
  ]

Proposal: User:Superastig topic banned from AfD in general

• I brought this up at the previous failed appeal and it got some traction, but the thread was closed before I could make a formal proposal. Superastig's history with AfD convinces me that they are not a net positive in this area and should be fully topic banned from deletion discussions. I'll repost my comments from the previous thread:

Another discussion involving Superastig showed up on my watchlist a few weeks ago. In this conversation (which occurred after they had been topic banned from closing AfDs) another editor said to Superastig: There are a few stations and TV channels that are up for deletion here. [...] I hope you could spare some time to save any of them from deletion. Superastig proceeded to vote keep on several of these articles. After being informed that this was canvassing, Superastig replied as follows:

In other words, you're telling me that it's a mortal sin for me to participate in deletion discussions after getting pulled out from my "break". I've stayed away from deletion discussions for a few months and never cared about a single article listed for deletion until @SBKSPP pinged me. I only picked a handful that I believe are worth being kept. It shouldn't be a big deal at all. It is never a mortal sin to be concerned about the articles listed for deletion, for God's sake.

You can hate, whine, cry, complain, throw hissy fits, say this, say that. But, my votes in the recent deletion discussions have (will have and still have) merit no matter what.

This behaviour speaks for itself IMO. Later, Girth Summit explained to them at length that this is in fact canvassing, and they still refused to get the message, stating Therefore, I believe what they did is not canvassing. I'll still stand by my views no matter what. Between the canvassing issues, the PA mentioned above, their past conduct at AfD and this unconvincing request, I believe that this editor is unable or unwilling to conduct themselves appropriately in this area and should be topic banned from AfD as a whole.

• Making another unconvincing appeal just a week after their previous one was unanimously opposed is additional evidence that they lack the judgment necessary to participate in this area. Spicy (talk) 19:25, 13 July 2023 (UTC)[reply]
• Support exhausting time sink. Would even support broader sanctions after this incredibly tone deaf appeal. Star Mississippi 01:42, 14 July 2023 (UTC)[reply]
• Comment: This is honestly too much. Half a month has passed and yet, you seem to question my past actions instead of moving forward. I already admitted my mistakes. I have moved on from those. Sheesh. ASTIG😎🙃 01:47, 14 July 2023 (UTC)[reply]

  The thing is, if you'd actually moved on, you wouldn't have started the thread above, and we wouldn't be here. - jc37 02:13, 14 July 2023 (UTC)[reply]

  User:Superastig, can I make a suggestion? When your behaviour and your interaction with others is under scrutiny, I think you would be best to omit words like "Sheesh" and other similar exclamatory expressions from your vocabulary. How you handle critical feedback can be a key part of how any future appeals you make will be judged. Boing! said Zebedee (talk) 09:11, 14 July 2023 (UTC)[reply]

  Well then, I'll try my best to do so next time. ASTIG😎🙃 10:45, 14 July 2023 (UTC)[reply]

  To be fair, some of the attitude from members of the WP administrative community can be a little overbearing, and at times frustrating. GeneralHamster (talk) 09:19, 18 July 2023 (UTC)[reply]

  If you really have changed, then you should've waited at least six months or rather more. Your previous appeal seemed too soon IMV. SBKSPP (talk) 03:08, 18 July 2023 (UTC)[reply]

• Support. A topic ban appeal immediately after one was just declined shows a very concerning lack of
  The Night Watch (talk) 03:18, 14 July 2023 (UTC)[reply
  ]
• Support, per my support in the previous discussion. BilledMammal (talk) 03:53, 14 July 2023 (UTC)[reply]
• Support AfD TBAN broadly construed; Superastig's behavior regarding their AfD closure TBAN appeals shows a lack of
  talk • contributions} (she/her) 04:03, 14 July 2023 (UTC)[reply
  ]
• Oppose. Retaliatory proposal. This user should be free to speak his mind; it's only his actions that should be constrained.—S Marshall T/C 07:56, 14 July 2023 (UTC)[reply]
• Oppose. Unless it can be shown that his behavior in AFD is problematic (neither the OP nor any of the voters even attempt to do this), there is no justification for such a ban. Bans are not a punishment, they are to protect Wikipedia against misbehavior. Animal lover |666| 08:59, 14 July 2023 (UTC)[reply]
• I'm going to Oppose this one, as I've seen no evidence of any ongoing disruption at AfD in general that needs to be prevented. The problems were, as far as I can see, all centred on closing deletion discussions. Boing! said Zebedee (talk) 09:05, 14 July 2023 (UTC)[reply]
• Oppose - One of the reasons I opposed the initial proposal to lift the topic ban is that Superastig has only participated in four AfD discussions since February. This is also a reason to oppose a broader topic ban - there is no evidence that Superastig is causing any serious disruption at AfD. WJ94 (talk) 09:37, 14 July 2023 (UTC)[reply]
• What is the point of banning someone from an area they are not contributing too but if they return and are disruptive the tolerance level might well be different.
  Spartaz ^Humbug! 14:09, 14 July 2023 (UTC)[reply
  ]
• Oppose This proposal is totally BS, given that they barely participated in AfDs after they were Tbanned. If an article they created gets contested in AfD and they cannot defend it because of the full AfD ban, that will be unfair for them. SBKSPP (talk) 01:52, 15 July 2023 (UTC)[reply]
• Strong oppose these proposals are getting out of hand. There is zero evidence that Superastig has been disruptive at AFDs over the past six months. Frank Anchor 03:30, 15 July 2023 (UTC)[reply]
• Oppose I can't comprehend why one would propose that someone who has not participated in AFD much would be banned for it. Nfitz (talk) 06:43, 15 July 2023 (UTC)[reply]
• Oppose The problem at issue isn't one of AFD as a whole. It's specifically about the editor's closures. I echo multiple others in this thread in saying that this measure is unnecessary. EggRoll97 ^(talk) 05:27, 16 July 2023 (UTC)[reply]
• Oppose He has enough of the metal horsepower to make excellent contributions at Afd, if he wants to. I don't why he can't make a contribution. scope_creep^Talk 16:32, 19 July 2023 (UTC)[reply]
• Oppose reeks of retribution. Regards, --Goldsztajn (talk) 22:55, 22 July 2023 (UTC)[reply]

Just noting, my oppose redundant having now read the subsequent discussion below. Regards, --Goldsztajn (talk) 23:03, 22 July 2023 (UTC)[reply]

Further battleground problems

I just noticed something disturbing at User talk:Superastig#Edit warring on Ang Syota Kong Balikbayan. In response to a content-related disagreement (and I've no idea who's right over the content as I haven't looked), Superastig ended with "Even if we argue about this 'til the day we die, my edit in the article stands. So, it's either you leave my edits as is or this issue you started will get worse. The choice is yours." That's the exact same Don't you dare challenge me attitude that earned them the ban from closing AFDs. And it happened when their behaviour is under close scrutiny here at AN. Their user page says "I have really moved on from my past troubles and learned from them." That would not appear to be true. So, do we need some sort of final warning about dropping that aggressive and threatening attitude? It can't be allowed to go on. Boing! said Zebedee (talk) 06:35, 15 July 2023 (UTC)[reply]

I also read that as a threat. I'm seriously thinking a preventative

WP:BLOCK is likely in order here. I'm open to other interpretations though. - jc37 12:04, 15 July 2023 (UTC)[reply

]

Yep, this was more or less my point in the roving disruption, although it was before this discussion. They are a problem, nut just a problem in AfDs. last time it was canvassing, now it's edit warring. I have no idea why they haven't been more broadly blocked in their career. Star Mississippi 12:34, 15 July 2023 (UTC)[reply]

Yeah, this is not great [1]. Whether or not the actress playing the girlfriend in a film called "My Girlfriend, The Returnee" can be named as being in "the title role" (who cares?), this bit of the edit war is over a completely unsourced cast list that Superastig insists is correct because it's in IMDB (whether it's "verified" is irrelevant - Wikipedia:Reliable_sources/Perennial_sources#IMDb). Black Kite (talk) 12:49, 15 July 2023 (UTC)[reply]

I am really surprised that their conduct hasn't received more scrutiny before since this is really obvious violation of both content and conduct policies. And their AFD stats show that Superastig !voted in 28 AFDs (with a result match stat of <75%) and apparently closed almost 1900 AFDs. With the poor understanding of wikipedia policies they have displayed here, I cringe to think of the potential damage. Abecedare (talk) 15:16, 15 July 2023 (UTC)[reply]

Now THATS a reason to ban them from closing! The 75% isn't that troubling in itself. But there's a clear lack of understanding here - and that's a huge number of closes. Nfitz (talk) 21:40, 15 July 2023 (UTC)[reply]

@Abecedare: - they voted in 28 AFDs out of the last 200 AFD pages they edited, not out of 1891. Simply explotating that figure would lead to an estimate of 265 total votes. Anyway, here is another link showing more votes from the older AFD pages they edited, showing 66 votes out of 200 AFDs. starship.paint (exalt) 14:21, 16 July 2023 (UTC)[reply]

@Starship.paint: Thank you for the correction in my methodology! Scrolling through all the pages of their AFD stats, I now see that they !voted in roughly 1350 AFDs (with a result match stat of about 88%) and so apparently closed about 550 AFDs. Nothing "wrong" with any of those stats per se and so that shouldn't IMO play a role in any further sanctions. Abecedare (talk) 14:47, 16 July 2023 (UTC)[reply]

No need to give them a final warning about that IMV. Their attitude varies, differ when it comes to participating in AfDs, closing them or contribution. It can be better discussed in a separate thread and not here.

Based on their contribution, they barely go berserk and the recent one is an instance. So, it's pointless to give them a final warning. SBKSPP (talk) 03:09, 18 July 2023 (UTC)[reply]

So, SBKSPP, do you think their comment that I showed above is in any way acceptable? Don't you think we need some assurance that they will change their aggressive attitude towards other editors? Boing! said Zebedee (talk) 05:14, 18 July 2023 (UTC)[reply]

@Boing! said Zebedee: TBH it's unacceptable. But it can be toned down and said in a more civil way.

Just warn and note them about WP:OWN and I'm sure they'll change. SBKSPP (talk) 07:11, 24 July 2023 (UTC)[reply]

Yes, I do hope they can change. But they haven't been taking the feedback they've had so far, and have just doubled down on the ownership - in this very discussion, below. Superastig does finally seem to be listening, but it took a block to do it, so let's hope for a good unblock request - I've left some advice. Boing! said Zebedee (talk) 07:20, 24 July 2023 (UTC)[reply]

PS: Nice bit of advice you left there yourself, SBKSPP - that should help. Boing! said Zebedee (talk) 08:51, 24 July 2023 (UTC)[reply]

• I'm disappointed that Superastig has not responded, either here or at their talk page where I told them their comment was unacceptable (and they have edited since). If we don't see some kind of acceptable response, showing understanding of how their aggressive ownership approach must stop, I would urge some admin action. Boing! said Zebedee (talk) 05:12, 18 July 2023 (UTC)[reply]

You seem to have misunderstood the phrase this issue you started will get worse. If that happens, then they persisted. It's out of my control. So, I don't see it as a threat. It's not like saying they're gonna get haunted, which is considered a threat. I can't haunt them 'cause I don't know where they live. This is why I'd rather stay away from anything that would cause me to

lose my cool. ASTIG😎🙃 10:06, 18 July 2023 (UTC)[reply

]

Superastig, I don't see any way to misunderstand "Even if we argue about this 'til the day we die, my edit in the article stands. So, it's either you leave my edits as is...". It looks like blatant battleground ownership to me (and you had the nerve to accuse the other editor of ownership). *You* do not get to dictate that your edit stands, and it is absolutely unacceptable for you to try to control content that way. Do you really not understand that? Boing! said Zebedee (talk) 14:55, 18 July 2023 (UTC)[reply]

you had the nerve to accuse the other editor of ownership: It's based on the article's history, where that incident happened a few times before. I wouldn't have had accused them if it wasn't for them persisting. My edits in that certain article aren't disruptive at all since I leave a clear explanation in each of my edit. If they make some minor changes to my edits, then fine with me. It's no big deal. But if they completely revert my edits, then I don't think that's tolerable. ASTIG😎🙃 15:00, 21 July 2023 (UTC)[reply]

That's a dictionary definition of

WP:OWN and you're providing no evidence to indicate you shouldn't be blocked more broadly. Star Mississippi 15:47, 21 July 2023 (UTC)[reply

]

That's terrible.—Alalch E. 15:53, 21 July 2023 (UTC)[reply]

Well, that response leaves me kind of speechless... admins? Boing! said Zebedee (talk) 20:39, 21 July 2023 (UTC)[reply]

I'm likely too involved to act, but I'd wholly support a broader block Star Mississippi 20:44, 21 July 2023 (UTC)[reply]

Well, gotta say thanks for making this whole thing real easy to understand.. Lulfas (talk) 21:28, 21 July 2023 (UTC)[reply]

Blocked indefinitely. Obviously open to review and any admins feel free to change (including modifying to a pblock) if so desired. Thanks, Daniel (talk) 04:07, 22 July 2023 (UTC)[reply]

Thanks Daniel, it's unfortunate but I think it's necessary - at least until we get some proper understanding of why their approach to disagreement is so utterly wrong. And, I'm not an expert on them, but I can't see a pblock that would work. Boing! said Zebedee (talk) 06:47, 22 July 2023 (UTC)[reply]

That was my thoughts - I considered a pblock from article-space but ownership issues would probably migrate to other namespaces, so in terms of being prevenative, I went the full block. Daniel (talk) 06:57, 22 July 2023 (UTC)[reply]

An indefinite block is too much IMV. Blocking them for 2 days to a week would suffice. But Blocking them indefinitely is outright ridiculous. Judging from their contributions, they're not like that everyday. I can say less than sometimes, they go berserk. Warn and note them about WP:OWN, and put them under surveillance by stalking their contribution page time by time. That'd do the trick. SBKSPP (talk) 07:14, 24 July 2023 (UTC)[reply]

Unfortunately, in my long experience, short timed blocks rarely work with chronic poor behaviour (even, perhaps especially, if that behaviour is intermittent), and editors often just sit them out and then carry on as before. What I think we needed is "You can't edit until you can convince us that your behaviour will change". And that's all an indefinite block is - it can easily be for less than 2 days. (I often think "indefinite" is a bad name - it's more of an open-ended block, just needing a bit of discussion to resolve.) Boing! said Zebedee (talk) 07:24, 24 July 2023 (UTC)[reply]

Note: Follow-up discussion at: Wikipedia_talk:What_Wikipedia_is_not#Alteration_to_NOTDIRECTORY. - jc37 18:46, 21 July 2023 (UTC)[reply]

Article: Awan (tribe)

Problem: [10] and [11]

Comment: There is a constant POV pushing going on in this article, even though it is extended user protected, the info box contains wrong information (NOR) and recently unreliable sources are added in the article. These are very basic things which senior editors should take care. When I highlighted these issues, no one from senior editors who visit this article regularly replied to it. - Greentree0 (talk) 17:59, 20 July 2023 (UTC)[reply]

• This is a content related issue, so don't expect the admins to intervene. M.Bitton (talk) 18:09, 20 July 2023 (UTC)[reply]

  That being said, there are other noticeboards where you may be able to receive more assistance on this matter. From the sound of your initial comment, either the

  reliable sources noticeboard might be a useful place to post. (I recommend posting to just one or the other, as posting to both will lead to confusion and duplicated work.) ModernDayTrilobite (talk • contribs) 20:29, 20 July 2023 (UTC)[reply

  ]

• Looking at the history, I would say that the ECP protection has actually stopped the problems; however as said above you may wish to post at one of those two noticeboards if you believe there are issues with the actual content. Black Kite (talk) 12:38, 21 July 2023 (UTC)[reply]

Cross-posting my comments from Wikipedia:Administrators'_noticeboard/Edit_warring#User:Rodagonda_reported_by_User:BangJan1999_(Result:_Declined): please refer to that page for context and further diffs.

User:Rodagonda is an obvious sockpuppet of Pitarobertz. A few minutes after account creation, Rodagonda immediately started removing G4 speedy tags from Savitha Nambrath, as shown in those diffs above. And today, they're at it again: [12], [13], [14], minutes after Pitarobertz removed the salt template:[15]. No response yet at User talk:Pitarobertz to my warning about sockpuppetry. Anon editors can't create an SPI, we can only add new reports to them, otherwise I'd have started one myself. 2A00:23EE:19C8:BA81:48C:2DFF:FEC5:9914 (talk) 11:16, 21 July 2023 (UTC)[reply]

A new third account, User:Peacehridhaan, has now taken over removing the speedy templates, and again 2 minutes after account creation: [16], [17]. 2A00:23EE:19C8:BA81:48C:2DFF:FEC5:9914 (talk) 11:49, 21 July 2023 (UTC)[reply]

•  Done Article deleted, article salted, obvious socks blocked. Black Kite (talk) 12:34, 21 July 2023 (UTC)[reply]

@Black Kite: thanks, and what's to be done about the sockmaster Pitarobertz? 2A00:23EE:19C8:BA81:48C:2DFF:FEC5:9914 (talk) 12:47, 21 July 2023 (UTC)[reply]

Would need someone to start a

WP:SPI for that, even though it's obvious; it could be meatpuppetry. Black Kite (talk) 17:14, 21 July 2023 (UTC)[reply

]

SPI report created at Wikipedia:Sockpuppet investigations/Pitarobertz. — AP 499D25 (talk) 23:58, 21 July 2023 (UTC)[reply]

On 11 February 2023 I started the article

They^. I wasn't in a good mood, so I got out of hand. Ghost_Cacus (talk) 17:08, 22 July 2023 (UTC)[reply]

@Ghost Cacus: that's not a valid excuse, your behaviour is unacceptable. Est. 2021 (talk · contribs) 17:10, 22 July 2023 (UTC)[reply]

Give me one source that says it's Soranus, not Apollo. Ghost_Cacus (talk) 17:12, 22 July 2023 (UTC)[reply]

And that ip isn't me Ghost_Cacus (talk) 17:12, 22 July 2023 (UTC)[reply]

Even if that ip was me, I wouldn't even use it. Ghost_Cacus (talk) 17:15, 22 July 2023 (UTC)[reply]

@Ghost Cacus: As I already wrote you on the article talk page: Stop playing, I already gave you more than one. I added the sources to the page long time ago,^[1][2][3] way before your recent reverts. Instead of ignoring both the sources and this talk page, and writing vulgarities in the edit summary, learn how to behave. and Stop acting dumb. The sources have been on the main page for months, and you already tried to delete them several times. You came here writing vulgarities from your account. The fact you also used an anonymous IP (23.242.174.8) to circumvent this talk page and delete the sources is just a very serious addition, and the fact you're trying to deny it is even worse. I'm now officially requesting admins to check IP 23.242.174.8 since you use it to circumvent talk pages. Est. 2021 (talk · contribs) 17:32, 22 July 2023 (UTC)[reply]

I've commented on the content issue on the article talkpage (and left a pointer to that discussion at Wikipedia talk:WikiProject Classical Greece and Rome#Deity equivalents where there is recent discussion on the general principle) but on the behavioural point frankly neither of you have behaved ideally. Yes, an edit summary saying "will you fucking stop?" isn't super civil, but frankly neither is you saying "stop acting dumb", nor you accusing them of "ignoring ... this talk page" when they are actively discussing on the talk page! Caeciliusinhorto-public (talk) 11:01, 24 July 2023 (UTC)[reply]

Following a dispute over content at Talk:Sound of Freedom (film), a new ussr - User:Saikyoryu began hounding me to other, completely unrelated pages , e.g within an hour of me first editing A Letter to Liberals, they were there to partially undo my edit (my first edit: 01:09, 19 July 2023 , their first: 02:19, 19 July 2023). They then had the gall to go to the talk page of another editor and complain that I was following them around, The other editor told them they were in the wrong, and advised them to leave me alone, and I also warned them about it ([18]) and today the were back at it, at and just now at [Wikipedia:Fringe theories/Noticeboard. When I warned them again on the talk page, their response was to come to my talk page and call me a "misogynistic racist".[19] The user's editing history suggests to me they are not really a new user (I can provide detailed evidence) but whether or not they are a genuinely new user- an administrator needs to put a stop to this hounding and personal attacks. Red Slapper (talk) 04:12, 23 July 2023 (UTC)[reply]

I see Saikyoryu accusing User:Isaidnoway of Sealioning multiple times at Talk:Sound of Freedom (film) (once saying "Holy fucking fuck I am AUTISTIC and even I'm not as fucking dense as you are pretending to be with your fucking sealioning." and of "falsehoods", accusing User:FMSky of the same thing once. Also at that page accusing you of dishonesty and "lying bullshit".

The editor asked for help at User talk:ToBeFree and when that didn't work replied "I tried that form and it failed and lost my typing twice. Thanks for being just and dishonest and giving me the same run around the "help" people did. BARF." To be fair to them I see that they later apologised.

But before the apology they posted at User talk:MJL#Talk:Sound of Freedom (film) "ToBeFree won't do a thing to help anyone. The page I was sent to at the Help Desk won't WORK to ask for an edit to the talk page. You look like you're a person who might actually give a damn". Red Slapper responded there and there was back and forth between the two. Too long to go into detail here, people can read the discussion.

I see further attacks on User:Wolfquack and User:Skarmory on their talk pages.

I do think Saikyoryu could be a constructive editor if they could avoid this type of behaviour but I am not at all convinced they can do that. I'd like to hear from the editors they have attacked. Doug Weller talk 07:42, 23 July 2023 (UTC)[reply]

I was never attacked; all the conflict on my talk page was between them and Wolfquack. Still, what I see here is someone who needs to calm down and remember this is a collaborative project. Hostility is unnecessary and disruptive. They're constructive in terms of the work they do, at least from what I've seen, but more collegiality is needed. Skarmory (talk • contribs) 08:10, 23 July 2023 (UTC)[reply]

@Skarmory Sorry, misread that. Doug Weller talk 10:53, 23 July 2023 (UTC)[reply]

Thanks for the summary. I'm now here from

interaction ban is the minimum that should result from this discussion here. Whether it needs to be one- or two-way, I don't know. ~ ToBeFree (talk) 10:46, 23 July 2023 (UTC)[reply

]

civil, shown here in this level 2 notice, and then in their revert of the notice, made an unfounded allegation about my motive for the notice here. Since the personal attack on me, I have disengaged with interacting with Saikyoryu. In relation to Red Slapper, this personal attack is way over the line and is worthy of a block. In my view, editors who make an attack like that should be shown the door.— Isaidnoway (talk) 08:36, 23 July 2023 (UTC)[reply

]

Okay, I now see this is more widespread and user-unspecific than I thought. I've just removed a few personal attacks from comments that have not been replied to yet ([20]). I'd be blocking if there hadn't been the unpleasant non-administrative interaction between them and myself before. ~ ToBeFree (talk) 10:54, 23 July 2023 (UTC)[reply]

That guy is a sock anyway. Their first couple of edits consisted of tagging pages for notability (1), lecturing IPs (2), adding "citation needed" tags (3), and explaining users the concept of

^Seconded. Those early edits to the help desk are a dead giveaway. SN54129 12:17, 23 July 2023 (UTC)[reply]

Indef blocked. @Red Slapper, sorry that it took this long. Sandstein 12:38, 23 July 2023 (UTC)[reply]

Thank you. Red Slapper (talk) 12:55, 23 July 2023 (UTC)[reply]

Red Slapper is also a sock of NoCal100, so this is probably two POV socks beefing with each other and wasting our time. Moneytrees🏝️(Talk) 22:11, 23 July 2023 (UTC)[reply]

The article, Grand Mufti of India, is under attack.

https://en.wikipedia.org/w/index.php?title=Grand_Mufti_of_India&diff=cur&oldid=1160360777 2409:40F3:1014:6FE7:8000:0:0:0 (talk) 04:44, 24 July 2023 (UTC)[reply]

I semi-protected the article for three days. The disruption is pretty minor at this stage. Johnuniq (talk) 04:51, 24 July 2023 (UTC)[reply]