Misplaced Pages

Latest revision as of 06:41, 26 December 2024

Click here to add a new enforcement request
For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
See also: Logged AE sanctions

Important informationShortcuts WP:AE WP:ARE Please use this page only to: request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator, request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic, request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators. For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard. Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions. To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}. Appeals and administrator modifications of contentious topics restrictions The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following: All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction. The appeal process has three possible stages. An editor appealing a restriction may: ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email. Appeals submitted at AE or AN must be submitted using the applicable template. A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted. Changing or revoking a contentious topic restriction An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies: The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or The contentious topic restriction was imposed (or last renewed) more than a year ago and: the restriction was imposed by a single administrator, or the restriction was an indefinite block. A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction: a clear consensus of uninvolved administrators at AE, a clear consensus of uninvolved editors at AN, a majority of the Arbitration Committee, acting through a motion at ARCA. Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped. Standard of review On community review Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action was not reasonably necessary to prevent damage or disruption when first imposed, or the action is no longer reasonably necessary to prevent damage or disruption. On Arbitration Committee review Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action represents an unreasonable exercise of administrative enforcement discretion, or compelling circumstances warrant the full Committee's action. The administrator may indicate consent at any time before, during, or after imposition of the restriction. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator. Appeals and administrator modifications of non-contentious topics sanctions The Arbitration Committee procedures relating to modifications and appeals state: Appeals by sanctioned editors Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may: ask the enforcing administrator to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-enwikimedia.org). Modifications by administrators No administrator may modify or remove a sanction placed by another administrator without: the explicit prior affirmative consent of the enforcing administrator; or prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below). Administrators modifying sanctions out of process may at the discretion of the committee be desysopped. Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied. Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions. Important notes: For a request to succeed, either (i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or (ii) a passing motion of arbitrators at ARCA is required. If consensus at AE or AN is unclear, the status quo prevails. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue. Information for administrators processing requests Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give. A couple of reminders: Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request. When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X". Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it. More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated. Closing a thread: Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days. Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct. You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages. Please log sanctions in the Arbitration enforcement log. Thanks again for helping. If you have any questions, please post on the talk page.

Ethiopian Epic

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Ethiopian Epic

User who is submitting this request for enforcement

Tinynanorobots (talk · contribs · deleted contribs · logs · filter log · block user · block log) 11:23, 12 December 2024 (UTC)

User against whom enforcement is requested

Ethiopian Epic (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Misplaced Pages:Arbitration/Requests/Case/Yasuke

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. November 14th created during the Yasuke case and went active when it ended. First 11 edits were to Government of Japan. In one case three edits were used to write one sentence.
2. November 12 Manually reverted the lead back to how it was in September.
3. November 16 Falsely Claimed cited material was OR. (G
4. November 24 Falsely Claimed cited material was unsourced
5. November 24 It took an ANI report to get him to use the article talk page. His defense was accusations and denial.
6. November 23 He reverted to a version that went against consensus established on the talk page and contained a falsely sourced quote.
7. November 25 Engages in sealioning
8. November 29 Removes a well sourced line from Yasuke as well as reverted an edit that was the result of BRD. He has now started disputes with me on all three Yasuke related articles.
9. November 30 starts disputing a new section of
10. December 2 Brought again to ANI, he claims that I didn't get consensus for changes, even though I had discussed them on talk prior to making them.
11. December 4 He keeps mentioning ONUS, and asking me to discuss it, in response to me discussing.
12. December 9 Used a non-controversial revert to hide his edit warring.
13. December 11 did the same thing on List of foreign-born samurai in Japan.
14. December 11 He also repeatedly complains that he doesn't like the definition because it is vague and claims that his preferred version is "status quo"

Diffs of previous relevant sanctions, if any

1. Date Explanation
2. Date Explanation

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

[

• Alerted about discretionary sanctions or contentious topics in the area of conflict, on December 1 (see the system log linked to above).

Additional comments by editor filing complaint

I am not sure if this is actually a AE matter, but was told to go here by multiple admins. The biggest issue is the Editing against consensus on accompanied by bludgeoning. However, there are signs of bad faith editing on all three pages where I have interacted with EE. It could also be a CIR issue or it could be some sort of harassment. I don't know. I just know that EE first avoided providing clear reasons for reverting edits and has been trying to engage in Status Quo Stonewalling. He keeps citing Onus or Burden and asks me not to make a change until the discussion is over. Often, this doesn't make sense in context, because the change was in place. He has made false claims about sources and what they say. His editing on Yasuke is not so much a problem as the discussion which comes across as gaslighting.

@User:Red-tailed hawk, I am not an expert on proxies or socks. All the IPs have only posted on the one article and have advocated an odd definition for samurai, that doesn't apply to the article. All except the first one have just reverted. It is possible that this is just laziness, or lack of confidence in writing skills etc. After all, the false citation was added by another user and was just kept. I found the latest one the most suspect, in part because of it first reverting to the incorrect definition, before restoring most of the text and second because of falsely citing policy. I am not sure if they are proxies, but I hoped that someone here would have the expertise to know. I don't think the proxy evidence is the most important. EE is either acting in bad faith or has CIR problems. The later is possible, because he thanked City of Silver during ANI, although City of Silver has been the harshest critic of EE's behaviour towards me.

I think there should be some important context to the quote: "those who serve in close attendance to the nobility". The quote can be found in several books, on Samurai it is sourced to an article published in Black Belt Magazine in the 80s by William Scott Wilson, where he describes the origin of the word samurai. He is describing the early phases of its meaning in that quote, before it became to have martial connotations. It also refers to the time before 900. The earliest foreign samurai on the list was in the late 1500s. It also doesn't apply to most of the persons on the list. Finally, it is not mentioned in Vaporis's book, which EE keeps adding as the source. He hasn't even made the effort to copy the citation from Samurai.

@User:Eronymous

Not only did I have a dispute with Symphony Regalia about samurai being "retainers to lords", but also on Yasuke about "As a samurai" and on List of Foreign-born Samurai in Japan EE made the same reverts as SR. EE had with his first edit in all three articles continued a dispute that I had already had with SR.

@User:Ethiopian Epic I actually don't have a problem with you discussing things. Your talk page posts aren't really discussion though. Your main argument on all three pages has been a shifting of the burden of proof. You don't really discuss content and continually ask me not to make changes without discussing first, and then make changes yourself. I understand that your position is that your preferred version is the status quo. However, my edits regarding the definition on List of Foreign-born samurai in Japan , were discussed and consensus was clearly gotten. Similarly, my edits on Yasuke were discussed, and even though I didn't use the exact same version as Gitz said, Gitz had suggested using warrior instead of bushi, so I used samurai, because I thought it would be less controversial.

Notification of the user against whom enforcement is requested

Discussion concerning Ethiopian Epic

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Ethiopian Epic

This is clear retaliatory filing because I recently didn't agree with Tinynanorobot's edits against RFC consensus, and because I made talk page sections on some recent edits.

@Eronymous That's not true and you are a very obvious alt account with only 26 edits. No one gave you a notification of this discussion and it's not on the Yasuke talk page. This suggests you are the sock puppet of someone here. Your post is also misleading and incorrect it wasn't an insertion. The line you are talking about in Samurai has been there for over 10 years and is normal. I know because I've read it before. Here is a version from 2017 that still has it. I don't understand why you are misrepresenting edits and using an alt account.

@Red-tailed hawk I think he is just fishing. That's why he removed his IP claims. Even his other diffs are just mislabeled regular behavior. It's amusing because Eronymous is the likely alt of Tinynanorobots or someone posting here. I think the way Tinynanorobots edits against clear consensus, skips discussion, and then files frivolous ANI/AE reports with misleading narrative like above is disruptive. Discussion is an easy solution and benefits everyone. I hope he will respect RFC consensus.

Statement by Relm

I am largely unfamiliar with the account in question, but I do frequently check Yasuke. I believe that EthiopianEpic has displayed a clear slant and battleground mindset in their editing in regards to the topic of Yasuke, but that their conduct on the Yasuke page itself so far has generally been in the ballpark of good faith edits. The revert on December 9th was justified, and their topic on November 29th is well within bounds (though I acknowledge that the background of their prior disputes on other pages with Tinynanorobots shows it may be edit warring) given that the two things being reverted was a change that seemed to skirt the prior RFC with agreement being given in a very non-direct way, and the other portion being an addition which had not been discussed on the talk page prior to its implementation (though previous discussions ered on the side of not including it). I am not accusing Tinynanorobots of any misconduct in any part of that either.

What I will note is that in addition to the sockpuppet IP allegations made by Tinynanorobots, I wanted to lodge that the posting style of EthiopianEpic, as well as their knowledge of much of the previous discussions on the page deep in the archive, led me to suspect that they were an alt of User:Symphony_Regalia. I never found anything conclusive. Relm (talk) 14:48, 12 December 2024 (UTC)

Statement by Simonm223

These two editors have been tangling at WP:AN/I repeatedly. Last time they came there I said that this would likely continue until a third party intervened. And then the thread got archived with no action (see AN/I thread here) so I'm not surprised that the two of them are still tangling. There is evidence that both editors have engaged in a slow-motion edit war. Both have claimed the other is editing against consensus. Here I will say that it appears TinyNanoRobots is more correct than Ethiopian Epic. Furthermore, while neither editors' comportment has been stellar, as other editors have pointed out, it appears more that EE is following TNR about and giving them a hard time than the alternate. . In the linked AN/I case (above) you'll note EE attempted a boomerang on TNR and was not well-received for the effort.

Frankly my view is that both editors are not editing to the best standards of Misplaced Pages but there is definitely a more disruptive member of this duo and that is Ethiopian Epic. I think it would probably cut down on the noise considerably if they were encouraged to find somewhere to edit which was not a CTOP subject and if they were encouraged to leave TNR alone. Simonm223 (talk) 18:05, 12 December 2024 (UTC)

Statement by Eronymous

Similar to Relm I check on the Yasuke page every so often, and it seems very likely given the evidence that User:Ethiopian Epic is an alt of User:Symphony_Regalia created to evade his recent ArbCom sanctions, having started editing the day prior to the Yasuke case closure. Of note to this is the last edit of Symphony_Regalia on Samurai was him attempting to insert the line "who served as retainers to lords (including daimyo)" - curiously enough, Ethiopian Epic's first edit on Samurai (and first large edit, having just prior made 11 minor ones in a short timeframe to reach autoconfirmed status) is him attempting to insert the same controversial line that was reverted before.

Symphony_Regalia has a history of utilising socks to edit Yasuke/Samurai related topics and is indefinitely blocked from the .jp wiki for extensive sockpuppetry (plus multiple suspected IPs) for this.

Prior to being sanctioned Symphony Regalia frequently got into exactly the same arguments concerning wording/source material with User:Tinynanorobots that Ethiopian Epic is now. One could assume based on their relationship that he is aggrieved that Tinynanorobots was not sanctioned by ArbCom during the case and is now continuously feuding with him to change that through edit warring and multiple administrator incidents/arbitration requests in the past few weeks. Eronymous (talk) 22:31, 12 December 2024 (UTC)

Statement by Nil Einne

I was ?one of the editors who suggested Tinynanorobots consider ARE in the future. I did this mostly because after three threads on ANI with no result, I felt a change of venue might be more productive especially since the more structured nature of ARE, as well as a likely greater concern over low level of misconduct meant that some outcome was more likely. (For clarity, when I suggested this I did feel nothing would happen from the third ANI thread but in any case my advice being taken onboard would likely mean the third thread had no result.) I did try to make clear that I wasn't saying there was definitely a problem requiring sanction and also it was possible Tinynanorobots might themselves end up sanctioned. Since a topic ban on both is being considered, I might have been right in a way. If a topic ban results, I'd like to suggest admins considered some guidance beyond broadly constructed on how any topic ban would apply. While the entirety of the Yasuke article and the list of foreign born samurai stuff seem clear enough, one concern I've had at ANI is how to handle the editing at Samurai and its talk page. A lot of the recent stuff involving these editors seems to relate to the definition of samurai. AFAIK, this is generally been a big part of the dispute of Yasuke (he can/can't be a samurai because it means A which was/wasn't true about him). Nil Einne (talk) 12:42, 15 December 2024 (UTC)

Result concerning Ethiopian Epic

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• I've never been very impressed with retaliatory filings, and the one below is no exception. I will also note that I'm never too impressed with "must be a sock" type accusations—either file at SPI or don't. In this case, though, I think Yasuke would be better off if neither of these two were participating there. Seraphimblade 19:33, 12 December 2024 (UTC)

  Red-tailed hawk, what are your thoughts after the responses to you? Seraphimblade 16:18, 17 December 2024 (UTC)

  I think that it would be declined if it were an WP:SPI report and the editor should be mindful not to throw sock accusations around willy-nilly going forward. But I typically don't see any sort of sanction imposed when someone makes a bad SPI report, particularly if they're newer or aren't quite clueful yet. So I don't see much to do on that front other than tell them that we need more specific evidence of socking when reports are made than merely shared interest, particularly when the IPs are scattered across the world. — Red-tailed hawk _(nest) 02:24, 18 December 2024 (UTC)

  I'm still inclined to topic ban both these editors from Yasuke, but would be interested in hearing more thoughts on that if anyone has them. Seraphimblade 07:10, 23 December 2024 (UTC)

• I also generally don't like "might-be-a-sock"-style accusations; when we are accusing someone of sockpuppetry by logged out editing we typically need evidence to substantiate it rather than just floating the possibility in a flimsy way. Filer has provided several diffs above as possible socks, but each of those IPs geolocates to a different country (Germany, Norway, and Argentina respectively) and I don't see evidence that any of those IPs are proxies.@Tinynanorobots: Can you explain what led you to note the IP edits? Is it merely shared interest and viewpoint, or is there something more?— Red-tailed hawk _(nest) 02:01, 13 December 2024 (UTC)
• Looking at this .... mess... first, I'm not sure what actually was against the ArbCom decision - I don't see a 1RR violation being alleged, and the rest really appears to me to be "throw stuff at the wall and see if it sticks". But, like Seraphimblade, I'm not impressed with either of these editors actual conduct here or in general. I could be brought around to supporting a topic ban for both of these editors in the interests of clearing up the whole topic area. Ealdgyth (talk) 14:33, 13 December 2024 (UTC)
• @Tinynanorobots: you are well above the 500 word limit. Please request an extension before adding anything more. Barkeep49 (talk) 16:18, 17 December 2024 (UTC)

Tinynanorobots

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Tinynanorobots

User who is submitting this request for enforcement

EEpic (talk) 19:14, 12 December 2024 (UTC)

User against whom enforcement is requested

Tinynanorobots (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Misplaced Pages:Arbitration/Requests/Case/Yasuke

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. 09:21, 14 November 2024. Tinynanorobots removes As a samurai from the lead text and replaces it with signifying bushi status against RFC consensus (There exists a consensus to refer to Yasuke as a samurai without qualification).
2. 17:12, 15 November 2024. Tinynanorobots removes who served as a samurai from the lead text and adds who became a bushi or samurai against RFC consensus (There exists a consensus against presenting Yasuke's samurai status as the object of debate).
3. 12:43, 20 November 2024. On List of Foreign-born Samurai, Tinynanorobots removes the longstanding definition and adds This list includes persons who ... may not have been considered a samurai against RFC consensus (There exists a consensus against presenting Yasuke's samurai status as the object of debate).
4. 07:48, 23 November 2024. Tinynanorobots reverts to remove As a samurai in the Yasuke article after Gitz6666 opposes at , again ignoring WP:ONUS.
5. 03:13, 4 December 2024. I restore and start a talk page discussion so that consensus can be formed.
6. 14:10, 6 December 2024 . Tinynanorobots, when consensus fails to form for his position, becomes uncivil and engages in a sarcastic personal attack What you are saying doesn't make sense. Perhaps there is a language issue here. Maybe your native language handles the future differently than English?
7. 14:22, 11 December 2024. Tinynanorobots removes "As a samurai" again, ignoring WP:ONUS and BRD even though no consensus has formed for his position, and no consensus has formed to change existing consensus.
8. 08:37, 6 December 2024. Tinynanorobots explains their reasons, I don't know if samurai is the right term which is against consensus.
9. 07:27, 28 November 2024. POV-pushing - With no edit summary Tinynanorobots tag bombs by adding Slavery in Japan.

Diffs of previous relevant sanctions, if any

1. Date Explanation
2. Date Explanation

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

• Alerted about discretionary sanctions or contentious topics in the area of conflict, on 23:06, 13 November 2024.

Additional comments by editor filing complaint

Tinynanorobots frequently edits against consensus, restores his edits when others revert, doesn't wait for consensus, and engages in feuding behavior. He seems to think WP:BRD or WP:ONUS don't apply to him which is disruptive, and I don't know why.

Unaccounted removals of sources 23:44, 14 September 2024 - Warning from other editor about repeated removal of content when multiple users are objecting.

AGF 12:21, 15 September 2024 - Warning from yet another editor about not assuming good faith and making personal attacks

It seems to be chronic which suggests behavior problems. Tinynanorobots also frequently fails to assume good faith in others. I don't know why as I don't have any issues with him.

Their preferred edit for Yasuke against the RFC consensus is now still in the lead section.

@Relm Sorry for the confusion. I think we talking about different edits, so I'll adjust that part. I am referring to Tinynanorobot's repeated removal of As a samurai against RFC consensus, which states There exists a consensus to refer to Yasuke as a samurai without qualification.

Notification of the user against whom enforcement is requested

18:40, 12 December 2024

Discussion concerning Tinynanorobots

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Tinynanorobots

The accusations made by EE are so misleading as to be evidence against him. Most of what he is discussing is in reference to a successful BRD. I actually discussed the bold edit first on the talk, but didn't get much of a response. I decided a bold edit would get more feedback. The edits were reverted and then discussed. Gitz's main problem was OR, not a RfC violation. This was because he didn't read the cited source. Anyway, since Atkin says "signifying bushi status", I have no objection to restoring this text.

I never used any sarcasm, I know that some languages handle how they talk about time differently. It seems reasonable that a translation error could be the reason for EE asking me not to change the article, althoug my edit had already been restored by someone else and at the same time asking me to discuss that I had already discussed and was already discussing. I am disappointed that EE didn't point out that he felt attacked, so that I could apologize.

This was written in response to another user, and the whole thought is I don't know if samurai is the right term. It is the term a fair amount of sources use, and the one that the RfC says should be used. It is also consistent with common usage in reference to other historical figures. In fact earlier in that post I said this: I am not qualified to say whither or not Yasuke having a house meant that he was a samurai This is blatantly taking a quote out of context in order to prejudice the Admins against me.

@User:Ealdgyth I filed here, because the last time I filed at ANI it was suggested that I bring things here if things continue by an Admin. I try to follow advice, although I keep getting conflicting signals from Admins. I am most concerned that you find my work on Samurai and List of Foreign-born Samurai in Japan not adding anything helpful. My suggestion to rewrite the way samurai was defined on the List in order to reduce OR and bring it in line with WP:LSC was meant with unanimous approval by those who responded. Samurai is a high importance article that has tags on it from years back, is unorganized and contains outdated information. I am not the best writer, but I have gotten some books, and am pretty much the only one working on it.

I just thought that the Admins here should know about the ongoing SPI

Statement by Relm

I am the editor alluded to and quoted as 'protesting' Tinynanorobots edit. When I originally made that topic, I was fixing a different edit which left the first sentence as a grammatically incomplete sentence. When I looked at it in the editing view, one of the quotes in the citation beforehand was quoting Atkins Vera, and I mistook this for the opening quote having been changed. When I closed the editing menu I saw 'signifying samurai status' in the second paragraph and confused the two for each other as I had not noticed the addition of the latter phrase a little under a month ago. I realized my mistake almost immediately after I posted the new topic, and made this (1) edit to clarify my mistake while also attempting to instead direct the topic towards making sure that the edit recieved sufficient assent from Gitz (it did) and to talk about improvements that could be made to the opening sentence. I further clarified and made clear that I was not accusing Tinynanorobots of having done anything wrong in a later response (2).

Though many of their earlier edits on the page may show some issues, as they grew more familiar with the past discussions I believe that Tinynanorobots has made valuable contributions to the page in good faith. Relm (talk) 03:21, 13 December 2024 (UTC)

Statement by Barkeep49

• @Ealdgyth I think this misinterprets the ArbCom decision. So Yakuse is a contentious topic and it has a 1RR restriction, in the same way as say PIA. As in PIA administrators can sanction behavior that violates the contentious topics procedures besides 1RR. Beyond that, editing against the RFC is a finding of fact from the case. Barkeep49 (talk) 16:25, 17 December 2024 (UTC)

Statement by (username)

Result concerning Tinynanorobots

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• As above, I'm failing to see what exactly is against the ArbCom case rulings - I don't see a 1RR violation. But also as above, I'm coming to the view that neither of these editors are adding anything helpful to the topic area and am leaning towards a topic ban for both. Ealdgyth (talk) 14:35, 13 December 2024 (UTC)

Rasteem

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Rasteem

User who is submitting this request for enforcement

NXcrypto (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:06, 13 December 2024 (UTC)

User against whom enforcement is requested

Rasteem (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBIPA

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. 23:21 12 December 2024 - removed wikilink of an Indian railway station thus violating his topic ban from India and Pakistan.

This violation comes after he was already warned for his first violation of the topic ban.