Wikipedia:Administrators' noticeboard/IncidentArchive1027
From Wikipedia, the free encyclopedia
Kavin Mudaliar
Kavin Mudaliar is engaging in edit war, dispute and adding regional research, and already informed. Over to Admin. --AntanO 17:21, 2 January 2020 (UTC)
- AntanO, I think this report should be at WP:AN3 rather than here, but from a cursory inspection it does look like Kavin Mudaliar's approach to editing is concerning - they're getting reverted a lot, and there's not much in the way of talk page participation from them. GirthSummit (blether) 18:16, 2 January 2020 (UTC)
User:Mclarenfan17
- Mclarenfan17 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
The mentioned user keeps changing the outlook of 2020 World Rally Championship#Entries to his own liking. This is going on for atleast one month. We've had a system for every previous season article. Most of all, we had a discussion, where nobody supported him (all participants were against this new format), but Mclarenfan17 still editwars to keep his own preferred version. I'm making this report, because I can not see the good faith in these edits. Examples of the edits (just enough not to break 3RR): + 3 during the last 24h . So is a consensus something to respect or not? Pelmeen10 (talk) 23:17, 26 December 2019 (UTC)
- Comment: I don't deny that a consensus was formed. However, in the time since that consensus was formed, new details have come to light and the implementation of that consensus contradicts the sources in the article. I will try to keep this as simple as possible:
- At the time the consensus was formed, Hyundai and Toyota had announced their driver line-ups:
- Hyundai had two full-time entries (for Tanak/Jarveoja and Neuville/Gilsoul) and a third entry shared between two crews (Sordo/del Barrio and Loeb/Elena).
- Toyota had three full-time entries (for Ogier/Ingrassia, Evans/Martin and Rovanpera/Hulttunen).
- However, after that consensus was formed, Toyota went on to announce that they would enter two additional cars during the year, one for Jari-Matti Latvala and one for Takamoto Katsuta. This is supported in the article by this source (currently source #20 in the article). Crucially, the article makes it clear that Toyota have not decided how to structure their team:
If [Jari-Matti] Latvala secured a five-round deal it could reignite enthusiasm for Toyota to create a 'B team'. Latvala could potentially run alongside Toyota protege Takamoto Katsuta, who will start all eight European WRC rounds and Rally Japan. Sources in Toyota confirmed a second team was under consideration for 2020. The original idea was for [Kalle] Rovanpera and Katsuta to drive for the second team so the two youngsters could learn out of the spotlight. Registering and running a second, point-scoring manufacturer team could be beneficial for Toyota's ambitions of a second makes' title in three years. Latvala said he is ready to help [team principal Tommi] Makinen and Toyota.
"Like I said, I want to drive next year. Maybe it could make sense to join [Katsuta] in a second team and try to score some points," Latvala said.
- And this is where the issue stems from. The consensus in the article is to organise the entry table by grouping the entrants together, bringing it in line with the style of table used in previous years. This style uses two tables, one for entries that can score manufacturer points, and one for entries that cannot. By organising the 2020 entries so that they centred on the team, the article implies that the team structure has been set, which contradicts the sources. I have tried to point this out in edit summaries and on the article talk page, but the only response that I have gotten from Pelmeen10 has been the claim that I am deliberately going against the consensus because I don't like it. Furthermore, after I posted an explanation for why a different format was needed, this is what he responded with:
You comments are WP:IDONTLIKEIT. You don't have any kind of consensus here. The unannounced car numbers just can't be shown as the most important thing, which the sorting is based on. Like we discussed, there are no sources to back all these numbers. Loeb btw is now associated with number 9.
- I have tried to point out that the table format implies something that contradicts the sources and he instead talks about "unannounced car numbers", which leads me to believe that he has not read a) any of my comments or b) the sources in the article and has instead rushed to revert my changes to the article, assuming that I did it because of previous opposition to the table format.
- Pelmeen10 opened his post with a question: is a consensus something to respect or not? I would like to answer that: yes, a consensus is something to be respected—but at the same time, a consensus does not give editors a licence to ignore, dismiss or misrepresent a reliable and verifiable source. Mclarenfan17 (talk) 00:03, 27 December 2019 (UTC)
- EDIT: I have since realised that when Pelmeen10 mentions "unannounced car numbers", he is referreding a a discussion at WT:MOTOR in which he and another editor made a specific claim (that because the title of the regulations refers to "seasonal numbers", drivers must reapply for their numbers every year, and so all of the numbers in the 2020 article are unsourced), but refused to provide any sources to support this when asked for them. In the time since posting this ANI report, Pelmeen10 has repeated the claim (by referring me to that discussion) to justify enforcing the consensus. My response has been to provide multiple sources debunking his theory. If he is trying to claim that the consensus was based on that discussion at WT:MOTOR, then I would argue that there was never a consensus to begin with because it was based on original research (only the title refers to "seasonal numbers"; there is nothing in the actual regulations to support his claim) and because he refused to provide reliable and verifiable sources despite being asked multiple times, instead insisting that the burden rested with people who disagreed with him. Mclarenfan17 (talk) 01:54, 27 December 2019 (UTC)
- This noticeboard does not adjudicate content disputes; yet, so far, the discussion is about content details. Please focus future comments on "urgent incidents" or "chronic, intractable behavioral problems". Cullen328 Let's discuss it 04:28, 27 December 2019 (UTC)
- Comment @Cullen328: I am aware of what ANI is for and I am not trying to use it to resolve a content dispute. I simply feel that Pelmeen10 is misrepresenting things. He claims that I am wilfully ignoring a consensus because of personal preference, but I am not. I simply felt the need to provide some contextual detail because a) I cannot assume any admin reading this is familiar with the subject, b) the reasons for my decisiom to change the format back are not immediately obvious when reading the article, and c) I feel that Pelmeen10 has a habit of not reading articles, sources and policies thoroughly and I wanted to put something here to refer back during any discussion.
- What would you suggest I do otherwise? Say "yes, I ignored the consensus"? Because I did. Not out of personal preference as Pelmeen10 claims, but out of necessity. When I changed the format of the table back, I tried to keep a format that at least resembled the consensus, but was unable to do so. I posted this message to the article talk page (dated 29 November), addressed Pelmeen10 directly (and later edited that message) that same day when he reverted it. There was little activity on the talk page (and none directly related to the issue) until 26 December when I again explained to Pelmeen10 why I felt that I had to make the change. With no opposition to the change for a month (and the expectation that the original consensus would be applied once a more-comprehensive source becomes available), I felt that WP:EDITCONSENSUS applied as a temporary solution. Mclarenfan17 (talk) 05:36, 27 December 2019 (UTC)
- Mclarenfan17, you openly admit that you are ignoring consensus even though Wikipedia:Consensus is policy, and you are claiming that your own personal perception of "necessity" overrides policy. I am unpersuaded. Can you please explain yourself more clearly? Cullen328 Let's discuss it 05:45, 27 December 2019 (UTC)
- What would you suggest I do otherwise? Say "yes, I ignored the consensus"? Because I did. Not out of personal preference as Pelmeen10 claims, but out of necessity. When I changed the format of the table back, I tried to keep a format that at least resembled the consensus, but was unable to do so. I posted this message to the article talk page (dated 29 November), addressed Pelmeen10 directly (and later edited that message) that same day when he reverted it. There was little activity on the talk page (and none directly related to the issue) until 26 December when I again explained to Pelmeen10 why I felt that I had to make the change. With no opposition to the change for a month (and the expectation that the original consensus would be applied once a more-comprehensive source becomes available), I felt that WP:EDITCONSENSUS applied as a temporary solution. Mclarenfan17 (talk) 05:36, 27 December 2019 (UTC)
@Cullen328: in the time between the consensus being formed and this ANI being opened, more information about the 2020 World Championship has been made public. I felt that this source published on 29 November (and currently in the article as source #20) changed things and would have affected the consensus discussion had it been available at the time (for the record, the consensus was still being discussed as recently as 28 November).
The consensus at WP:WRC is that entry tables should be structured in such a way that all crews competing for one team should be grouped together (for example, in the 2019 article). This is common across all motorsport-related articles. However, that consensus was formed before 29 November. On 29 November, Toyota announced that they would enter two additional cars during the 2020 season. The content of that source made it clear that they had not yet decided on the structure of the team. Would it be one big team of five cars? Or two separate teams? And if so, how would the cars be split between them?
When I saw this, I realised that there would be a problem with the consensus. It meant that the entry table grouped all five Toyota entries together as if they were one team, which contradicted what the source said. This source—Autosport—is one of the most widely-used sources across motorsport articles because it is extremely reliable. Furthermore, Hyundai had already announced how their team would be structured, which meant I felt the article further contradicted the source because it implied Toyota had finalised their structure, which they had not.
When I made the changes to the table, I tried as best I could to respect the consensus while also reflecting the content of the 29 November source, but I simply could not make it work. I also knew that within six weeks an ironclad source—the entry list for the first round—would be published, resolving the issue altogether because it would make clear who was competing for which team. I felt that I had to choose between a consensus which inadvertently contradicted sources (which had not been available at the time) or overlooking the consensus in favour of a very reliable and verifiable source with the expectation that the consensus would be applied once a source would be published within six weeks. Everything that I did here was in good faith. It was not, as Pelmeen10 contends, because I didn't like the consensus, but because of information published after the consensus was formed. Had the information published on 29 November been available when the consensus was formed, it would have been factored into the consensus discussion in which case a) the consensus would not have been formed as it was, or b) editors would have agreed to wait until the structure of Toyota's team was announced before we applied the table format. Mclarenfan17 (talk) 06:20, 27 December 2019 (UTC)
- Mclarenfan17, you say the you understand that this noticeboard does not judge content disputes and yet you continue to to argue here at ANI in favor of your preferred content. Let me be clear: no uninvolved editor here at ANI cares about your content disputes. Go pursue Dispute resolution which might include a Request for comment. In brief, if the facts underlying a consensus have changed, then engage with other editors interested in the article to build a new consensus. Be persuasive. Forcefully claiming the right to impose your preferred changes is wrong, just plain wrong. Please do not go there. Cullen328 Let's discuss it 07:33, 27 December 2019 (UTC)
- @Cullen328: I'm not sure what you want me to say here. You asked me to explain my actions, and I have tried to do just that with a sufficient level of detail that you understand my thinking here, but you just reply "ANI isn't for content disputes". I'm not claiming that I have some right to ignore a consensus. I'm saying when I was put in a position where I had to choose between a consensus and a reliable source, I chose the reliable source when satisfying both the consensus and the source proved impossible. When I posted this to the article talk page, nobody came along and made an alternative suggestion that resolved the dilemma. I had every expectation and every intention that the agreed-upon format would eventually be applied and everything I did was done in good faith. This has nothing to do with a "preferred version" of the article.
- What would you do in my position? You can observe a consensus that is largely cosmetic, but contradicts reliable sources that you did not have access to when that consensus was made; or you can overlook the consensus for the time being to make sure the article accurately reflects its sources with a view to reintroducing the consensus as soon as it is possible to do so. You cannot satisfy both at once, and it seems that my biggest mistake was that I made the wrong choice. I made it because I cannot see anything in WP:CONSENSUS that says editor are allowed to form a consensus that ignores WP:RELIABLE. If I'm missing it, please point it out to me. Mclarenfan17 (talk) 08:13, 27 December 2019 (UTC)
- Mclarenfan17, the correct course of action here would have been to first boldly attempt to edit the article, then go to the talk page to hash it out. You should not attempt to reinstate your edits again until the discussion has been resolved. If you think that other editors on the article are ignoring your arguments, you can take it to WP:DRN or convene an WP:RFC. signed, Rosguill talk 08:54, 27 December 2019 (UTC)
- @Rosguill: I tried to do exactly that. This is the edit I made to the article on 29 November, and this is the explanation I posted to the talk page five minutes later. The only person who responded (and not on the talk page, my talk page or at any relevant WikiProject) was an editor with a habit of reverting things on sight and not reading articles and sources, including articles he is reverting. Case in point, this edit where he removed reliably-sourced content (Takamoto Katsuta's entry) because he didn't check. I've been bold, I've posted an explanation for why I felt the changes were necessary, shown a willingness to work with others on it and nothing has come of it until the past 24 hours (there were a few other edits in the past week, but largely unrelated to the issue and were adding unsourced content). Mclarenfan17 (talk) 09:10, 27 December 2019 (UTC)
- Mclarenfan17, taking it to the talk page in November was the correct decision. If other editors don't respond to you there, the next step is to convene an RfC or start a thread here, depending on the exact nature of the issue. signed, Rosguill talk 09:17, 27 December 2019 (UTC)
- Rosguill, other editors in rallying articles now mostly leave one or couple of comments (or are not even gonna comment anymore), because Mclarenfan17 can keep up the discussion endlessly (weeks, months) with the same arguements, which will never lead to anything. Pelmeen10 (talk) 18:08, 27 December 2019 (UTC)
- Mclarenfan17, taking it to the talk page in November was the correct decision. If other editors don't respond to you there, the next step is to convene an RfC or start a thread here, depending on the exact nature of the issue. signed, Rosguill talk 09:17, 27 December 2019 (UTC)
- @Rosguill: I tried to do exactly that. This is the edit I made to the article on 29 November, and this is the explanation I posted to the talk page five minutes later. The only person who responded (and not on the talk page, my talk page or at any relevant WikiProject) was an editor with a habit of reverting things on sight and not reading articles and sources, including articles he is reverting. Case in point, this edit where he removed reliably-sourced content (Takamoto Katsuta's entry) because he didn't check. I've been bold, I've posted an explanation for why I felt the changes were necessary, shown a willingness to work with others on it and nothing has come of it until the past 24 hours (there were a few other edits in the past week, but largely unrelated to the issue and were adding unsourced content). Mclarenfan17 (talk) 09:10, 27 December 2019 (UTC)
- Mclarenfan17, the correct course of action here would have been to first boldly attempt to edit the article, then go to the talk page to hash it out. You should not attempt to reinstate your edits again until the discussion has been resolved. If you think that other editors on the article are ignoring your arguments, you can take it to WP:DRN or convene an WP:RFC. signed, Rosguill talk 08:54, 27 December 2019 (UTC)
- What would you do in my position? You can observe a consensus that is largely cosmetic, but contradicts reliable sources that you did not have access to when that consensus was made; or you can overlook the consensus for the time being to make sure the article accurately reflects its sources with a view to reintroducing the consensus as soon as it is possible to do so. You cannot satisfy both at once, and it seems that my biggest mistake was that I made the wrong choice. I made it because I cannot see anything in WP:CONSENSUS that says editor are allowed to form a consensus that ignores WP:RELIABLE. If I'm missing it, please point it out to me. Mclarenfan17 (talk) 08:13, 27 December 2019 (UTC)
So can I revert to the wikitable format we have a consensus of? The one we've used for years. Because no Rfc or DRN has started (which I'm pretty sure is not necessary, because all active editors in this subject have already given their thoughts. Plus, Mclarenfan17 claims his version is just temporary. Is it now clear that Mclarenfan17 shouldn't revert me again? Though, I don't want to be part of an edit war. Pelmeen10 (talk) 17:29, 27 December 2019 (UTC)
- Comment: I have no objection to the consensus being applied, but would suggest that its implementation needs to accurately reflect the sources in the article. In other words, it cannot group the five Toyota entries together as though they are one team. Mclarenfan17 (talk) 18:52, 27 December 2019 (UTC)
Another violation: Mclarenfan17 did not even respect a consensus after the DRN/Rfc is finished: here is one where uninvolved editor summed up the discussion with "it appears that there is a small consensus favouring the removal of the third row" - but just 3 days later (24 Nov 2019) Mclarenfan17 reverts it claiming "The "consensus" was so small that no-one did anything with it for TEN WEEKS and it's undermined by one editor's agenda". So the behaviour is repeating over and over again... Pelmeen10 (talk) 18:03, 27 December 2019 (UTC)
- Comment: the "consensus" in question was formed by an editor who has engaged in a sustained campaign of harrassment (particularly wikihounding) against me. It was very weak to begin with me and clearly designed to frustrate my editing practice rather than benefit the article. Mclarenfan17 (talk) 18:52, 27 December 2019 (UTC)
- No, that user (Tvx1) has respect among other rallying editors (including me). But it looks to me that you try to undermine his comments by getting personal (attacking and insulting). You have also attacked other editors, both in comments and edit summaries. If needed, I can bring examples. Pelmeen10 (talk) 19:03, 27 December 2019 (UTC)
- That user's edit history shows that his only contributions to rallying articles are to join in discussions on the current season's talk page and oppose me in discussions. He has never actually contributed anything to a rallying article. It stands out because his edit history shows a handful of topics that he likes to edit articles about, and that he contributes to multiple articles and talk page discussions within those topics—but not rallying, where he only ever contributes to one talk page at a time. It's really none of your business and a matter for a separate ANI. Mclarenfan17 (talk) 19:44, 27 December 2019 (UTC)
- You are making some serious accusations of bad faith and generally seriously wrong editing by User:Tvx1 here even though you provided no diffs, and AFAIK there's no case where your claims were established. You've also failed to notify Tvx1 of this discussion despite your serious accusations. I'll do so for you but I suggest you either provide diffs and a brief summary to support your allegations or withdraw them lest you are blocked for personal attacks for making unsupported allegations of wrong doing. I recalled seeing your 2 names before and came across Wikipedia:Administrators' noticeboard/IncidentArchive1015#Harrassment by an editor, and your claims didn't seem to be accepted in part because your comment was way too long. Nevertheless, there was some frustration at your unwillingness to accept any wrong doing on your part. Nil Einne (talk) 04:55, 28 December 2019 (UTC)
- @Nil Einne: I did not want to turn this discussion into a discussion about wiki-hounding. I feel that a separate ANI would be more appropriate for that; however, I have not had any issues with the editor in question and last time I tried to raise subject of wiki-hounding, I felt the editor successfully misrepresented my ANI report as bring some petty revenge for "losing" a DRN discussion (which was not helped by a DRN volunteer refusing to read anything I posted, but seeing fit to pass judgement on it anyway). As you can perhaps appreciate, in light of this I have little appetite to start another ANI about wiki-hounding. Mclarenfan17 (talk) 07:40, 28 December 2019 (UTC)
- You are making some serious accusations of bad faith and generally seriously wrong editing by User:Tvx1 here even though you provided no diffs, and AFAIK there's no case where your claims were established. You've also failed to notify Tvx1 of this discussion despite your serious accusations. I'll do so for you but I suggest you either provide diffs and a brief summary to support your allegations or withdraw them lest you are blocked for personal attacks for making unsupported allegations of wrong doing. I recalled seeing your 2 names before and came across Wikipedia:Administrators' noticeboard/IncidentArchive1015#Harrassment by an editor, and your claims didn't seem to be accepted in part because your comment was way too long. Nevertheless, there was some frustration at your unwillingness to accept any wrong doing on your part. Nil Einne (talk) 04:55, 28 December 2019 (UTC)
- That user's edit history shows that his only contributions to rallying articles are to join in discussions on the current season's talk page and oppose me in discussions. He has never actually contributed anything to a rallying article. It stands out because his edit history shows a handful of topics that he likes to edit articles about, and that he contributes to multiple articles and talk page discussions within those topics—but not rallying, where he only ever contributes to one talk page at a time. It's really none of your business and a matter for a separate ANI. Mclarenfan17 (talk) 19:44, 27 December 2019 (UTC)
- If you believe there are procedural issues which means a closure was incorrect, you should discuss this with the closer and try to get the closing statement changed. Worst case, you could always bring it to WP:AN or similar and ask for a re-close. Likewise if you feel that consensus has changed because of new information, it may be okay to WP:BOLDly make a change in some cases. But once someone objects, you need to work on establishing that consensus has indeed changed. If someone has objected, and no one else is commenting, then you have no real evidence that consensus has changed, whatever your views of the other person's objections and so you have to return to the old consensus established via an RfC. You can try using WP:3O or some other method like posting a neutral message on a relevant wikiproject asking for more feedback. Ultimately, if you cannot get a consensus via those methods, then you need to start another WP:RfC to establish this alleged new consensus and overturn the old one. You cannot simply refuse to accept a consensus, even a narrow one because you don't like it. To be clear I'm including any sincere belief on your part that the consensus view is wrong, doesn't work, is based on OR, is invalid, etc as well as your personal opinions on the motivations of other editors. Especially not a consensus 3 days old. Nil Einne (talk) 05:11, 28 December 2019 (UTC)
- I feel I did exactly that. I made a BOLD edit based on new information. I posted an explanation on the talk page and I got no response. Pelmeen10 did revert it and I directly addressed him on the talk page, asking him to take care because his revert had deleted content from the article that had nothing to do with the consensus. He never responded. Nobody did, and things have been quiet until about 24 hours ago. Despite Pelmeen10's repeated claim that I ignored the consensus because I disliked it, everything I did was done in good faith. I felt I had to choose between a consensus and a source with information that could change the consensus. I only made the change after trying to re-format the table to be consistent with the consensus, but also accurately reflect the sources, but failed.
- No, that user (Tvx1) has respect among other rallying editors (including me). But it looks to me that you try to undermine his comments by getting personal (attacking and insulting). You have also attacked other editors, both in comments and edit summaries. If needed, I can bring examples. Pelmeen10 (talk) 19:03, 27 December 2019 (UTC)
- If Pelmeen10 wants to continue claiming I ignored the consensus because WP:IDONTLIKEIT, then I think he needs to provide some evidence to support the claim. Otherwise, he is ignoring WP:AGF.
- I have performed a few reverts in the section of the article in the past week, but this was because unsourced content was being added to the article and had nothing to do with the consensus. Mclarenfan17 (talk) 07:40, 28 December 2019 (UTC)
I said the above without looking at the article discussion. And frankly now that I have, I wouldn't want to talk to you on the talk page either. I see you proposed working together on wording an RfC which is excellent.
But then I see you said this "
Nothing Tvx1 has to say on this subject has any value.
" and "I sm not insulting people. It is a simple statement of fact: Tvx1's only interest in these discussions is hounding me.
" which is quite the opposite. If you want to minimise your involvement with Tvx1, that is fine. But as I said above, if you have evidence that Tvx1 is hounding you, you need to open an ANI case and convince the community of this. Until you do so, you need to stop making accusations especially not on article talk pages, and especially where it's of little relevance. (The editor tried 3 ping 3 others, so it's not like they were only asking for Tvx1's opinion.)As an uninvolved editor, seeing such random personal attacks makes me very reluctant to get involved in any discussion with you. Who knows if you're going to decide to attack me for no reason?
More generally, if I'm frank, this seems a very dumb issue to get so worked up about. The championship starts on the 23 January per the article. This means that by now, by the time any RfC closes, if it lasts the full 30 days, it will be moot point since the concerns will no longer hold. This doesn't mean it's okay to have inaccurate information, but can you all really not come to some sort of agreement to address all concerns? Have you consider keeping the table as is and using footnotes to clarify for example? Surely there's something you can do without needing an RfC. If you wanted an RfC to try and solve the issue for future years, that would be another thing, but it may be better to wait until this year's championship starts so people don't get too bogged down in the details specific to this year.
Nil Einne (talk) 09:50, 28 December 2019 (UTC)
- I've tried to implement a consensus version taking on board the concerns of both editors I can only hope it sticks of they take it from here since I don't think I can be bothered taking it further. Anyway I mainly came back to say if anyone does want an RfC, it is imperative that you agree on a wording beforehand and then focus on some brief explanation backed by our policy and guidelines for your preference. An RfC with extensive back and forths between existing participants like Wikipedia talk:WikiProject World Rally/Archive 3#Request for Comment on table format is likely doomed to failure. Nil Einne (talk) 11:22, 28 December 2019 (UTC)
- Thanks for the content-related help. But I started this topic because the behaviour of the mentioned user - ignoring consensus and editwarring into his own preferred version. I'm not convinced the user will stop this kind of behaviour. His previous user Prisonermonkeys was blocked several times for editwarring, I feel the only thing he is learned, is not to break 3RR (more than 3 reverts in 24h) and remove "undid revision..." from edit summaries. I mean, previous dispute was with not showing the possibility that the defending champion can choose number 1 for his car number (per the rules), I insisted TBA (no direct source for the numbers) & started a discussion here, later moved it here to get more feedback. These are the reverts Mclarenfan17 made: He reverted different users 21 times to a version with only #8 until left it alone. Pelmeen10 (talk) 18:22, 28 December 2019 (UTC)
- None of those edits provided a source to support the change of the number.
- Thanks for the content-related help. But I started this topic because the behaviour of the mentioned user - ignoring consensus and editwarring into his own preferred version. I'm not convinced the user will stop this kind of behaviour. His previous user Prisonermonkeys was blocked several times for editwarring, I feel the only thing he is learned, is not to break 3RR (more than 3 reverts in 24h) and remove "undid revision..." from edit summaries. I mean, previous dispute was with not showing the possibility that the defending champion can choose number 1 for his car number (per the rules), I insisted TBA (no direct source for the numbers) & started a discussion here, later moved it here to get more feedback. These are the reverts Mclarenfan17 made: He reverted different users 21 times to a version with only #8 until left it alone. Pelmeen10 (talk) 18:22, 28 December 2019 (UTC)
- I've tried to implement a consensus version taking on board the concerns of both editors I can only hope it sticks of they take it from here since I don't think I can be bothered taking it further. Anyway I mainly came back to say if anyone does want an RfC, it is imperative that you agree on a wording beforehand and then focus on some brief explanation backed by our policy and guidelines for your preference. An RfC with extensive back and forths between existing participants like Wikipedia talk:WikiProject World Rally/Archive 3#Request for Comment on table format is likely doomed to failure. Nil Einne (talk) 11:22, 28 December 2019 (UTC)
- I would also like to point out that Pelmeen10 made a specific claim in that WT:MOTOR discussion. I repeatedly asked him to provide sources to support that claim and he refused. He instead insisted that the burden lay with people who disagreed with him to prove him wrong. The issue came up on the 2020 article talk page where he claimed that the numbers "were not directly sourced or official". My response was to provide four reliable sources, all of which debunked his original claim. Pelmeen10 replied to this by saying the issue was not being discussed, even though he brought the subject up in the first place.
- It is obvious that Pelmeen10 wants to see some kind of admin action taken against me. However, the diffs he has provided show me reverting unsourced content and he himself has a bad habit of making unsourced claims and refusing to provide any sources in support of those claims when challenged. He has also taken to engaging in original research to reach the claims that he has made in the first place. Mclarenfan17 (talk) 23:07, 28 December 2019 (UTC)
- I don't really get the accusation you made. The content added to Wikipedia needs direct sources, not the other way around. The content shouldn't be wrong by adding more than sources actually write. I was challenging your added content, not you challenging me. While you're trying to boomerang this somehow, you are confusing something by providing 26 December talk, while the reverts I listed happened between 31 October and 21 November. So the issue did not come up just 2 days ago but was resolved on 21 November by you not reverting (examples ) the note that was suggested in the discussion. The note is now there from 21 November. The rule that defending champion can choose number one, is in the sporting regulations and you know it. I tryed adding the sporting regulations as a source on 3 November, which you reverted. "The issue" with other numbers was raised in 22 November here by two more users, Tvx1 and SSSB. I quote: Having taken another look at the sources in the article, as well as at the sporting regulations, I'm no longer convinced that these drivers/crews have chosen career numbers. Neither the sources, nor the regulations mention "career numbers". They all actually talk about season/seasonal numbers. It seems like they only reserve a number for the duration of a season. While it is likely that crews will pick the same numbers over multiple season, we can't really be certain of that. - In any of the sources you provided, it was never mentioned that they can keep the same number year on year, nor was explained what the "career number" means. In the rules, they are still "seasonal numbers". Sorry for discussing content here. Pelmeen10 (talk) 01:42, 29 December 2019 (UTC)
That is original research.
Having taken another look at the sources in the article, as well as at the sporting regulations, I'm no longer convinced that these drivers/crews have chosen career numbers. Neither the sources, nor the regulations mention "career numbers". They all actually talk about season/seasonal numbers. It seems like they only reserve a number for the duration of a season. While it is likely that crews will pick the same numbers over multiple season, we can't really be certain of that.
The only place that "seasonal numbers" is mentioned is in the title of Section 17 of those regulations. There is nothing in the text of Section 17 that "it seems like they only reserve a number for the duration of a season". I have repeatedly searched for sources to support this intepretation, and have found nothing. I have repeatedly asked you to provide sources to support this interpretation, and you have refused. And I have provided no less than four reliable and verifiable sources that specifically state that crews choose permanent numbers. You responded by changing the subject. It's quite obvious that you don't have the sources to support the claim, but nevertheless insist on it being true and refuse to address anyone or anything that points out that this is incorrect. Mclarenfan17 (talk) 05:27, 31 December 2019 (UTC)
- None of the sources you listed mention what does that "career number" mean! It fails to mention that the numbers will carry on to the next season (2020 in this case). That's what you can call WP:CRYSTAL or WP:OR. Removing the numbers for not having enough information is not OR, very funny you'd think that. It would be the correct thing not to list "expected numbers". Now you've even added the same numbers to 2021_World_Rally_Championship#Entries, crazy. Pelmeen10 (talk) 18:50, 2 January 2020 (UTC)
For What It's Worth
This is a dispute that is partly a content dispute and partly a conduct dispute, as are many disputes here. This is a conduct forum. However, most conduct disputes, in particular most difficult conduct disputes, begin as content disputes. A conduct dispute that does not have a content element is usually simply vandalism or trolling, and can usually be resolved by one administrator concluding, with no objection, that the offender is not here constructively and needs blocking. Unfortunately, what we have here is a dispute involving an editor who is involved in multiple content disputes about motorsports (and possibly other matters). An editor who is involved in frequent content disputes is either an editor who edits in a contentious area, or an editor who doesn't collaborate well. This editor, User:Mclarenfan17, appears to be an editor who gets into a lot of content disputes, many of which come to WP:DRN as content disputes, and some of which come here as conduct disputes. I have generally tried to be neutral in the content disputes, and have assisted in resolving them by RFC. However, if an editor gets into too many content disputes, maybe they are an editor who doesn't compromise enough. Robert McClenon (talk) 18:49, 30 December 2019 (UTC)
User:SinclairCEO
Maybe this should have gone to AIV, but it's a slightly complicated. I think Special:Contributions/SinclairCEO needs a block. While I have no idea if any of this is true , their first edit was this which I strongly suspect is not true. Someone has been trying to add such nonsense for a few months now . The last edit is particularly interesting since it comes from Special:Contributions/Marshall77, who managed to get themselves blocked after adding material to that article (Doug Chapman (American football)) that was rev-deleted. It also highlights another reason for a block, assuming SinclairCEO doesn't know what to do to edit the article, they may go inactive since the article has been semi-protected. But the history with Marshall77 suggests it will be re-activated once protection expires. BTW, while I assume looking at the rev-deleted material will probably be enough to prove whoever is behind this is up to no good, see if there are any doubts. Incidentally, I think we can be sure that the editor is trying to imply some connection with Sinclair Broadcast Group which doesn't exist so it's also a username violation. Yes, I'm sure they'll be back, but with more blocks, it will hopefully be easier to deal with e.g. simply reported to AIV. Nil Einne (talk) 06:24, 3 January 2020 (UTC)
Confirmed to at least one previous vandal and blocked. NinjaRobotPirate (talk) 06:38, 3 January 2020 (UTC)
Editor making legal threats
Toddstarnes3 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Editor has threatened to sue those editing the article about him previously, and again repeatedly today, see dif. Obviously he is frustrated and I have attempted to explain alternative options dif, but he has not responded to the WP:NLT warning made in November, nor previously responded to COI concerns, and other accounts User:Toddstarnes and User:TPDNYC were blocked by Donald Albury as socks. Melcous (talk) 10:16, 3 January 2020 (UTC)
- Do you think this really is Todd Starnes making the edits? Hard to prove I know. If true, then WP:AUTO would apply.--♦IanMacM♦ (talk to me) 10:35, 3 January 2020 (UTC)
- It doesn't really matter whether it is Starnes or not. Whoever it is the legal threats are grounds for a block unless and until they are withdrawn unequivocally. This doesn't mean that we should ignore them, but simply that anyone has to choose between being able to edit Wikipedia and making such threats. Phil Bridger (talk) 10:44, 3 January 2020 (UTC)
User:HunterTubeHD85960
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
@HunterTubeHD85960: has incessantly vandalized the article Rumble (2021 film). Adding unsourced and fabricated castings and reverts whenever anyone fixes it. User clearly doesn’t exist to be helpful. Rusted AutoParts 17:54, 3 January 2020 (UTC)
- @Trivialist: can attest to this. Rusted AutoParts 17:55, 3 January 2020 (UTC)
- @Rusted AutoParts: Can you describe the results of your prior discussions with HunterTubeHD regarding this issue? What did they say or do when you brought these issues up with them, expressed your concerns to them, or asked them to explain their editing? --Jayron32 18:07, 3 January 2020 (UTC)
- Dif's would be helpful.-- Deepfriedokra 19:00, 3 January 2020 (UTC)
- here’s the edit history of the article. I suspect the editor is also the IP making the same edits/reversions. This specific edit summary is where I ask Hunter/the ip to source these edits and neither have done so, just continuously reinserting without offering any source. Rusted AutoParts 19:36, 3 January 2020 (UTC)
- Dif's would be helpful.-- Deepfriedokra 19:00, 3 January 2020 (UTC)
- @Rusted AutoParts: Can you describe the results of your prior discussions with HunterTubeHD regarding this issue? What did they say or do when you brought these issues up with them, expressed your concerns to them, or asked them to explain their editing? --Jayron32 18:07, 3 January 2020 (UTC)
Another disruptive account, while AIV is locked
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The nonsense edit summaries alone are good for a block, per WP:NOTHERE. 2600:1702:4000:8110:2155:4AFF:F5F9:39E8 (talk · contribs). 2601:188:180:B8E0:C4B2:972D:AD9:DDC (talk) 04:05, 1 January 2020 (UTC)
- I blocked them for a short time, thanks. Johnuniq (talk) 04:14, 1 January 2020 (UTC)
- Thank you. Cheers, 2601:188:180:B8E0:C4B2:972D:AD9:DDC (talk) 04:20, 1 January 2020 (UTC)
@Johnuniq: I think 2600:1702:4000:8110::/64 (talk · contribs · deleted contribs · logs · filter log · block user · block log) is more likely to catch the next IP they use, based on the contribs of the previous two months. —[AlanM1(talk)]— 08:37, 2 January 2020 (UTC)
Proposal to block 2600:1702:4000:8110::/64
Any opinions on whether the /64 range should be blocked for a significant period (at least a month)? In that range, the following 12 IPs have edited, with the first being 10 November 2019:
I don't have time at the moment for a thorough check, but several that I looked at appeared to be the same user having fun. Some edits could be defended as good faith, but IMHO they look like trolling designed to make editors argue for an hour whether such good-faith edits should be rolled back. If none of the above IPs are constructive, a significant block would be warranted. @AlanM1: any thoughts? Johnuniq (talk) 09:14, 2 January 2020 (UTC)
Geoffemerick account
William Zabaleta is a talent manager, one of his former clients Geoff Emerick, a grammy winning recording engineer. An account User:Geoffemerick claimed to be emerick himself in 2017. The account was editing about his own articles. Unfortunately, Emerick died in 2018, but this account keeps on editing articles related to William Zabaleta, his agency and his clients. I suspect a case of shared accounts, UPE, and COI, and a general sense of disgust for the talent agency. Daiyusha (talk) 13:20, 2 January 2020 (UTC)
- The use of an account in the name of a person who died recently is also in extremely poor taste. Phil Bridger (talk) 16:56, 2 January 2020 (UTC)
Olympics ip editor
47.213.232.81 (talk · contribs · IP contribs · WHOIS) Keeps adding falsified data to tables, claiming that the 2024 Youth Winter Olympics have been awarded to Pyongchang, when they have not. (here and here). ip has an extensive history of being uncooperative and quickly blanking their talk page. Cards84664 (talk) 21:36, 1 January 2020 (UTC)
- I was only trying to help. I used a citation in the 2024 Winter Youth Olympics page and in the Youth Olympic Games page and according to the source I cited in both of these pages, Pyeongchang is the only confirmed candidate so far and the IOC is to award the host city in a week and none of the other cities in contention have expressed further interest. 47.213.232.81 (talk) 09:23, 2 January 2020 (UTC)
- That's not how Wikipedia works. See WP:NOTCRYSTALBALL. –MJL ‐Talk‐☖ 14:35, 3 January 2020 (UTC)
2A02:C7F:CAA9:1300:A0B6:32BB:47AF:92E7 reported by 107.77.227.107
2A02:C7F:CAA9:1300:A0B6:32BB:47AF:92E7 (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log) – This user has been making questionable unexplained changes to Abby Hatcher for months. Because the user's IP changes a lot, a range block may be needed. 107.77.227.107 (talk) 18:17, 3 January 2020 (UTC)
Edits are not vandalism. Please ensure recent edits constitute vandalism before re-reporting. I don't see where the edits in question are vandalism. It mostly looks like innocuous wording changes and a few minor additions. I don't see bad faith anywhere in the two edits made by that IP, or why they even needed to be reverted. Jayron32 18:22, 3 January 2020 (UTC)
- The user has repeatedly state that Sparkles is a Fuzzly, but Sparkles is never referred to as a Fuzzly in the show. The user also keeps describing Grumbles as "monster", but a monster does not have a definite appearance. I fear he/she will just keep adding these without explanation. In fact the user doesn't seem to explain his/her edits. 107.77.227.107 (talk) 18:54, 3 January 2020 (UTC)
- Yes, but this is not vandalism. Vandalism does NOT mean "Something I disagree with". This is a disagreement between you and them over a few wording changes and what those words mean. Have you tried starting a discussion on the article talk pages to explain why you disagree with their changes? What were your prior attempts to reach out to this person? --Jayron32 19:19, 3 January 2020 (UTC)
- The user has repeatedly state that Sparkles is a Fuzzly, but Sparkles is never referred to as a Fuzzly in the show. The user also keeps describing Grumbles as "monster", but a monster does not have a definite appearance. I fear he/she will just keep adding these without explanation. In fact the user doesn't seem to explain his/her edits. 107.77.227.107 (talk) 18:54, 3 January 2020 (UTC)
- Special:Contributions/2A02:C7F:CAA9:1300:A0B6:32BB:47AF:92E7/64 may be interesting. ~ ToBeFree (talk) 19:10, 3 January 2020 (UTC)
- I don't see any evidence of bad-faith editing there. A few minor tweaks here and there, the kind of stuff thousands of people do every day. Can you post some diffs of actual bad-faith editing in that /64 range? --Jayron32 19:20, 3 January 2020 (UTC)
- What this article could use is sources, rather than fights over a fictional race of animals on a kid's show that a five year-old and a 40 year-old parent will never care to learn the specifics about. I see plenty of sources literally nobody outside of the kidvid cruft community cares about regarding episode premiere ratings...I see nothing about the actual show's characters, but I see lots of long writing about each character that would make for a good lullaby (they all need severe editing). This has all the makings of a lame edit war. Nate • (chatter) 01:35, 4 January 2020 (UTC)
- I don't see any evidence of bad-faith editing there. A few minor tweaks here and there, the kind of stuff thousands of people do every day. Can you post some diffs of actual bad-faith editing in that /64 range? --Jayron32 19:20, 3 January 2020 (UTC)
Page blanking by User:Wisegrandaugher
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
A new user keeps blanking and renaming a page titled Finkenberg's Sons Furniture. As a different user, User:New York Historian 1870, had removed an AfD tag and blanked the page, I'm at two reversions and I don't want to edit war by hitting three reverts. Can somebody look into this situation to see what's going on? The user also moved the page to Administrator please delete this article. Hog Farm (talk) 02:45, 4 January 2020 (UTC)
- I don't really know what's going on either. But I speedy deleted the redirect as a test page, moved the article back, and move-protected it. I also left a note on Wisegrandaugher's talk page that I hope will resolve some of her concerns. NinjaRobotPirate (talk) 03:15, 4 January 2020 (UTC)
Austhistory99
The author user:Austhistory99 (self declared COI) of this hatchet job on author Bruce Pascoe has been contributing to both his bio article and the article for his book Dark Emu - considering the tone of his website Dark Emu Exposed, I believe this goes beyond a COI. Austhistory99 has now published a copy of Pascoe's book the articles talk page, the book is popular and contemporary, currently in publication and published under copyright - offering the text in full is a blatant copyright violation. Given the editors self admitted authorship of an attack page that describes the articles subject as "Chairman Pascoe" and "Emperor Pascoe" among other slurs and their recent copyright violation/disregard for the subjects intellectual property. I believe this editor has a demonstrable and serious issue with the articles subject and should be topic banned from all articles relating to Bruce Pascoe. Bacondrum (talk) 02:07, 4 January 2020 (UTC)
- Whatever else, I agree that linking to the full book is a violation of WP:COPYVIOEL. While WP:REX and other methods can be used to exchange resources to help editors, a general link to the full book in the talk page is way too far. The editor should be blocked if they do this again. Nil Einne (talk) 02:37, 4 January 2020 (UTC)
- Thanks for the feedback. I want to point out that the copyright that was violated regarding Dark Emu belongs to the BLP article's subject Bruce Pascoe making this a particularly troubling case of copyright violation. Considering the editor runs a page dedicated to defaming Pascoe and discrediting his book, it seems inconceivable that he did not know it was a copyright violation. Bacondrum (talk) 04:02, 4 January 2020 (UTC)
User:TM2042
Repeat vandalism by TM2042 on Blair Cottrell repeatedly adding unfounded/uncited claims including accusations of (Redacted). Blatant vandalism. Bacondrum (talk) 04:40, 4 January 2020 (UTC)
- Blocked. But please read the large banner that appears whenever you edit this page:
If the issue concerns a privacy-related matter, or potential libel/defamation, do not post it here.
NinjaRobotPirate (talk) 05:06, 4 January 2020 (UTC)- Noted, thanks. Bacondrum (talk) 05:13, 4 January 2020 (UTC)
User:Coloursred1 and edits in tennis
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Coloursred1 (talk · contribs · deleted contribs · page moves · block user · block log)
2020 Australian Open – Main Draw Wildcard Entries (edit | talk | history | protect | delete | links | watch | logs | views)Take at look at User:Coloursred1 and its vicious editing in Wikipedia that I have seen a rumor in the Australian Tennis Season swing that Maria Sharapova is about to appear in the upcoming Australian Open as the remainder of the Wildcards have not yet announced. Usually, this user continues editing without giving a reason on the subject rumor. ApprenticeFan work 13:44, 30 December 2019 (UTC)
- (Non-administrator comment) @ApprenticeFan: You did not notify Coloursred1 of this discussion per the instructions.But yes; that's one helluva unsourced-POV pushing single-handed WP:NOTLISTENING edit war from Coloursred1, with added BLP concerns. ——SN54129 14:18, 30 December 2019 (UTC)
- That's not counting the aggression . And combined with their refactoring , of both the OP's comment and my response to it—!!! NOTHERE, anyone...? ——SN54129 14:27, 30 December 2019 (UTC)
Administrator note I have boldly blocked 31 hours for disruption. Feel free to review and modify if needed.-- Deepfriedokra 14:31, 30 December 2019 (UTC)- Reply from Coulursred1
I had sources and references, Keroks had personal issues with Sharapova’s doping case and didn’t want her on the list. You should take up an issue with him and not me. Go check it all, it all has sources. Back off Coloursred1 (talk) 14:33, 30 December 2019 (UTC)
-- Deepfriedokra 14:43, 30 December 2019 (UTC)- I'm afraid Keroks side of the discussion wasn't that much better.-- Deepfriedokra 14:48, 30 December 2019 (UTC)
- @Deepfriedokra:Note that this user has now resorted to a new account with disruptive sockpuppet edits. Fyunck(click) (talk) 05:59, 31 December 2019 (UTC)
- I'm afraid Keroks side of the discussion wasn't that much better.-- Deepfriedokra 14:48, 30 December 2019 (UTC)
New user without an interest in providing sources
Appears to be a good faith editor, but has ignored templates and prefers to add content without sources; more specifically, their 'sources' are meaningless. I'd prefer not to edit war and go to a level four warning, so any assistance would be grand. 2601:188:180:B8E0:65F5:930C:B0B2:CD63 (talk) 17:42, 4 January 2020 (UTC)
- And an apparent minor copyright violation that may require rev/deletion . 2601:188:180:B8E0:65F5:930C:B0B2:CD63 (talk) 17:48, 4 January 2020 (UTC)
- I've done the revision deletion and another admin has issued a short block for disruptive editing. Thanks for reporting. — Diannaa 🍁 (talk) 19:02, 4 January 2020 (UTC)
- My thanks to you both. 2601:188:180:B8E0:65F5:930C:B0B2:CD63 (talk) 19:03, 4 January 2020 (UTC)
- I've done the revision deletion and another admin has issued a short block for disruptive editing. Thanks for reporting. — Diannaa 🍁 (talk) 19:02, 4 January 2020 (UTC)
User:Pmoore2222 COI
Despite repeated warnings in the past at User talk:Pmoore2222, this user is again editing in a way that raises serious COI concerns. Note that his entire list of User Contributions, dating back to 1 April 2009, consists solely of edits to what appears to be his own bio. NedFausa (talk) 21:33, 2 January 2020 (UTC)
- He apparently confirms he is Patrick Moore (consultant) with this edit summary and with this edit to his talk page asking to be unblocked back in 2011. Note that back in 2011 when he was unblocked, it was on condition of editing in userspace only. See User_talk:Pmoore2222#COI. He is now in violation of that agreement, albeit it was nearly 9 years ago. @Materialscientist: pinging Materialscientist to the conversation as he was the blocking/unblocking administrator at the time. --Hammersoft (talk) 22:49, 2 January 2020 (UTC)
- It's been a couple of days, and no further activity from him has happened. I've posted a long note to him regarding this issue, as it appears unlikely he will see this thread before it is archived. I've watchlisted the article, and watchlisted his talk page. Hopefully he can work with us, not against us. --Hammersoft (talk) 15:21, 4 January 2020 (UTC)
InedibleHulk's signature
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
InedibleHulk seems to be a competent editor and it feels like overkill to bring this here, but despite repeated pleas by several users to fix their signature, they have refused. Hulk's signature is in violation of WP:SIGAPP, specifically the bold first line which reads: Your signature must not blink, scroll, or otherwise cause inconvenience to or annoy other editors
(emphasis mine). Hulk's signature formats the timestamp in a manner that bots do not recognize, and therefore prevents or otherwise interferes with the activities of archive bots. It is also incompatible with user scripts like Unclutter. The weird part of this is that Hulk seems to understand and acknowledge that their signature is a violation of unambiguous policy, but does not seem to care.
I want to be clear that I am here as a last resort, and harbor no resentment toward Hulk. I'm honestly just baffled that this is the hill that they have decided to die on. WMSR (talk) 21:18, 3 January 2020 (UTC)
- @WMSR: Have you got any specific examples of how—for instance—their signature may prevent a bot from archiving a thread no matter how many times the bot passes by? ——SN54129 21:32, 3 January 2020 (UTC)
- Signature example:
- InedibleHulk (talk) 20:07, 3 January 2020 (UTC)
- — xaosflux Talk 21:39, 3 January 2020 (UTC)
- I don't take a lot of weight in the "bots don't like it" part - sure they don't but that's not really a big deal. Causing "what links here" linkbacks from articles on every single signing though is a bit much. — xaosflux Talk 21:42, 3 January 2020 (UTC)
- Indeed, perhaps. Bots and their lack of feelings are of no interest to anyone. But when humans—whether editor or reader are potentially inconvenienced, then yes, I think there's an issue. For example, as RedRose64 pointed out over six months ago, a thread was not archived for ten days because of the (lack of) timestamp. If accidental, it wouldn't be a problem; but since mens rea has been established, it certainly comes within the realm of WP:DE. More to the point, the length of time over which the issue has been raised multiplied by the number of times it has been (?) laughed off indicates that some—I don't attempt to understand what—kind of point is being made.In any case, the bottom line is that, after so many fruitless attempts at resolution met with (at best) levity, this complaint was unfortunately overdue here. ——SN54129 21:58, 3 January 2020 (UTC)
- (@Closing admin: This comment can be read as a Require standard date/time (aka prohibit) opinion per the discussion below. ——SN54129 14:19, 4 January 2020 (UTC))
- Enough people have complained about this to mean that this editor should either change the signature immediately to something that resolves the complaints or revert to the standard signature. This is an encyclopedia, not a social networking site where such personal preferences that get in the way of other people's work is indulged. Phil Bridger (talk) 21:52, 3 January 2020 (UTC)
- Let's put "enough people" to the test. How many editors are annoyed or inconvenienced by the signature? Petition subsections below. – Levivich 21:57, 3 January 2020 (UTC)
- No, let's not. This is a very simple matter of someone who has a signature that causes some people annoyance, and refuses to change it the light of that. Creating battelefield-style voting sections just makes this, well, a battlefield. Why on Earth do we allow silly childish custom signatures anyway? As I said, this is supposed to be an encyclopedia, not a social networking site. Phil Bridger (talk) 22:07, 3 January 2020 (UTC)
- Phil, I hate your signature. I hate everyone's signature that is not customized. Why? Because it's difficult to tell the difference (at least for me) between a "plain" signature and some other kind of wikilink. Signatures that are colorful and pop are better than plain signatures because they (1) allow you to quickly identify one comment from another, (2) allow you to quickly identify who is speaking, (3) don't get confused for a regular link, and (4) are pretty and interesting and sometimes funny. "Not a social networking site" has nothing to do with it. (And that tired, tired slogan needs to be retired permanently. We are, in fact, a social networking site, a collaborative encyclopedia project where socializing and networking are required and happen every day among thousands of people.) As with all things, opinions on signatures vary. Of course, that doesn't mean that you should have to change your signature just because I personally don't like it. To me, it really does matter whether it's 3 editors who are annoyed, or 30, or 300. Because you'll find 30 editors annoyed about anything. Hell, 300 are annoyed by me, and I'm still here! :-D PS: It's not a battlefield, it's a straw poll. Instead of arguing over whether "a lot" of editors are bothered, or just "a few" or "some", let's just have a show of hands and see how many think this is a problem that needs to be addressed. – Levivich 22:48, 3 January 2020 (UTC)
- Augh, I have to agree with Levivich here at some level (not re: Phil B.'s signature, because he has a reason that makes sense to him and that's a contraindication to "hate" in JDL-world). I had this argument with my business partner because even IRL I use green Century Schoolbook in my email and signature thereof, unlike anyone else in my small business. Why? Because that way I can spot my own content in a thread. Freaking SCOTUS uses Century Schoolbook and that's enough of a respectability endorsement for me. And my favorite color is green. I'm 48 and hate cyber-gewgaws as much as anybody but I convinced the highly non-convince-able Business Partner that I had a rationale and it improved my efficiency. I'm just sayin'. Julietdeltalima (talk) 00:05, 4 January 2020 (UTC)
- Phil, I hate your signature. I hate everyone's signature that is not customized. Why? Because it's difficult to tell the difference (at least for me) between a "plain" signature and some other kind of wikilink. Signatures that are colorful and pop are better than plain signatures because they (1) allow you to quickly identify one comment from another, (2) allow you to quickly identify who is speaking, (3) don't get confused for a regular link, and (4) are pretty and interesting and sometimes funny. "Not a social networking site" has nothing to do with it. (And that tired, tired slogan needs to be retired permanently. We are, in fact, a social networking site, a collaborative encyclopedia project where socializing and networking are required and happen every day among thousands of people.) As with all things, opinions on signatures vary. Of course, that doesn't mean that you should have to change your signature just because I personally don't like it. To me, it really does matter whether it's 3 editors who are annoyed, or 30, or 300. Because you'll find 30 editors annoyed about anything. Hell, 300 are annoyed by me, and I'm still here! :-D PS: It's not a battlefield, it's a straw poll. Instead of arguing over whether "a lot" of editors are bothered, or just "a few" or "some", let's just have a show of hands and see how many think this is a problem that needs to be addressed. – Levivich 22:48, 3 January 2020 (UTC)
- No, let's not. This is a very simple matter of someone who has a signature that causes some people annoyance, and refuses to change it the light of that. Creating battelefield-style voting sections just makes this, well, a battlefield. Why on Earth do we allow silly childish custom signatures anyway? As I said, this is supposed to be an encyclopedia, not a social networking site. Phil Bridger (talk) 22:07, 3 January 2020 (UTC)
- Let's put "enough people" to the test. How many editors are annoyed or inconvenienced by the signature? Petition subsections below. – Levivich 21:57, 3 January 2020 (UTC)
- I disagree about the backlinks being a problem, Xaos. There are already thousands upon thousands of backlinks to January 3 already, including thousands just in User: space alone (nevermind talk pages and mainspace). Same with January 2, and 2020, and 2019. How many pages does Hulk sign each day? A few... less than 10? Hulk is adding less than 0.1% to the backlinks. Even over the course of all of 2019, I bet it's less than 1%. The "backlink spam" is negligible. I wonder if there's a tool to verify this. – Levivich 21:57, 3 January 2020 (UTC)
- I don't understand the point in having a sig's day and year link to mainspace; if it is causing issues with useful bots, then I'd agree that it violates WP:SIGAPP and should be changed. OhNoitsJamie Talk 22:17, 3 January 2020 (UTC)
- If the worst it does is, as mentioned above, delay an archive bot from archiving for a few extra days, I don't think that's a problem. If there are other, more serious, problems caused, then it might be a problem. Just my two cents. – Levivich 22:48, 3 January 2020 (UTC)
- yes there are several problems. As someone who is from a different time zone, his signature makes it impossible to understand the chronology of the comments. I have had chance to work with him on discussions about a couple of controversial pages and following those ungodly timestamp in a threaded discussion on a talk page is an absolute nightmare. I had also asked him to change this but it seems he has become a pro in deflecting requests to change his sign. This ANI was destined to happen. --DBigXrayᗙ 00:24, 4 January 2020 (UTC)
- If the worst it does is, as mentioned above, delay an archive bot from archiving for a few extra days, I don't think that's a problem. If there are other, more serious, problems caused, then it might be a problem. Just my two cents. – Levivich 22:48, 3 January 2020 (UTC)
- I don't understand the point in having a sig's day and year link to mainspace; if it is causing issues with useful bots, then I'd agree that it violates WP:SIGAPP and should be changed. OhNoitsJamie Talk 22:17, 3 January 2020 (UTC)
- I disagree about the backlinks being a problem, Xaos. There are already thousands upon thousands of backlinks to January 3 already, including thousands just in User: space alone (nevermind talk pages and mainspace). Same with January 2, and 2020, and 2019. How many pages does Hulk sign each day? A few... less than 10? Hulk is adding less than 0.1% to the backlinks. Even over the course of all of 2019, I bet it's less than 1%. The "backlink spam" is negligible. I wonder if there's a tool to verify this. – Levivich 21:57, 3 January 2020 (UTC)
| Inedibility resounds around. "Chopped heart and lungs boiled in a wee sheep's stomach! Tastes as good as it sounds!" ——SN54129 22:08, 3 January 2020 (UTC) |
|---|
| The following discussion has been closed. Please do not modify it. |
|
- To be clear, I didn't decide to die on this hill. If it happens, it happens. But I've never once started these polite disagreements. InedibleHulk (talk) 22:44, 3 January 2020 (UTC)
- So which hill did you decide on, then? Victims' names? Retirement of the intercontinental belt? – Levivich 23:05, 3 January 2020 (UTC)
- You know that valley between those things? Bury me there. Next to the hamulet. InedibleHulk (talk) 23:25, 3 January 2020 (UTC)
- (Non-administrator comment) I use a script that translates the UTC timestamps to local time and formats it for display the way I want. It doesn't work on IH's sigs though. It seems anti-social and non-collegial of them to do this unless there's a really good reason. I could write a custom handler for IH's format, but what about the next one? Wouldn't it be easier for IH to use a custom script that converted everyone else's sig to their desired format instead? —[AlanM1(talk)]— 02:18, 4 January 2020 (UTC)
- I don't have Javascript enabled, so if that's part of the deal, it's easier for you to adjust things on your end. Don't worry about the next one, I've only seen one other guy do it Hulk-style here in seven years. I'm a dying breed. InedibleHulk (talk) 03:02, 4 January 2020 (UTC)
- It's not even just random editor's custom's scripts. The Wikipedia:Comments in Local Time gadget fails with it too. That said, while now that I'm paying attention, I do find this disruptive and not because of the effect on timestamp interpreting scripts, however I have to be honest I either never noticed this before or did but didn't think much of it despite regularly seeing InedibleHulk in places. Nil Einne (talk) 02:33, 4 January 2020 (UTC)
- (Non-administrator comment) I use a script that translates the UTC timestamps to local time and formats it for display the way I want. It doesn't work on IH's sigs though. It seems anti-social and non-collegial of them to do this unless there's a really good reason. I could write a custom handler for IH's format, but what about the next one? Wouldn't it be easier for IH to use a custom script that converted everyone else's sig to their desired format instead? —[AlanM1(talk)]— 02:18, 4 January 2020 (UTC)
- You know that valley between those things? Bury me there. Next to the hamulet. InedibleHulk (talk) 23:25, 3 January 2020 (UTC)
- You mean someone else changed your signature for you? I think we may need to block your account as compromised..... Nil Einne (talk) 04:03, 4 January 2020 (UTC)
- In case you're not kidding, I mean I've consistently decided to go on living with this annoying problem. It's the nice normal people who want to see me fry for this. Can't really fault them for it, though, I tricked a poor gadget. InedibleHulk (talk) 04:21, 4 January 2020 (UTC)
- Actually you don't have to go on living with this annoying problem. You can still change your signature back thereby resolving the problem you did not create because you evidently did not change your signature even though your account was never compromised. Nil Einne (talk) 11:57, 4 January 2020 (UTC)
- InedibleHulk, I doubt people here want to see you fry for this. People here just want to focus on discussions to improve the article on talk pages without getting annoyed by ungodly timestamps. It was brought here to be fixed, only because you could not be bothered to fix this annoying problem. Apparently you believe this is something worth dying for. --DBigXrayᗙ 12:35, 4 January 2020 (UTC)
- In case you're not kidding, I mean I've consistently decided to go on living with this annoying problem. It's the nice normal people who want to see me fry for this. Can't really fault them for it, though, I tricked a poor gadget. InedibleHulk (talk) 04:21, 4 January 2020 (UTC)
- So which hill did you decide on, then? Victims' names? Retirement of the intercontinental belt? – Levivich 23:05, 3 January 2020 (UTC)
- Prohibit "
otherwise cause inconvenience to or annoy other editors
". Altering the format of the timestamp inconveniences and annoys other users directly, and less directly by causing scripts and bots to malfunction. It does not usefully distinguish the user in the sense Levivich would like. I would go so far as to say that any user probably should not alter, format or cause any links in the timestamp portion of the sig but I would have to see more examples. Timestamps are part of the cooperative operation of the talk pages and I would say, like indenting/threads and not interleaving comments, they are just part of "how it works" and should not be optional. —DIYeditor (talk) 03:03, 4 January 2020 (UTC) - Prohibit if Levi really wants a straw poll, then I guess he shall have one. We certainly couldn't just fix an obvious problem and move on with minimum disruption. No sir, that wouldn't be the Wikipedia way. Inedible's signature is causing problems with archiving. They need to fix it. (And the extra back links are, at best, a potentially-disruptive nuisance). I don't buy Inedible's 'Golly gee, I'm not sure it's such a big deal' attitude. Stop stalling and fix your mess. And yes, you have chosen this hill to die on. Bully for you that you never started any of these
polite disagreements
(the same ones that keep arising because you can't be bothered to fix your signature). You want a cookie or something? Sheesh. Lepricavark (talk) 04:14, 4 January 2020 (UTC)
- Keep your cookie, but if you're feeling generous, just don't call me "they". It's annoying. You know I'm a guy by my name. InedibleHulk (talk) 04:25, 4 January 2020 (UTC)
- Trust me, I could think of quite a few other things to call you. Lepricavark (talk) 04:29, 4 January 2020 (UTC)
- From the way you wrote that, I get the feeling we've met. If it's any consolation, I'm probably sorry for how things went. Cheers to new beginnings? InedibleHulk (talk) 04:40, 4 January 2020 (UTC)
- You expressed annoyance at my adherence to increasingly-standard pronoun usage (no, your username does not make it 100% clear that you are male) in a thread that was caused by your refusal to change an annoying and decidedly non-standard signature. Hence my snarky reply. No, I'm not aware of any prior history nor do I bear you any personal ill will. I just think it's very silly of you to refuse to change your signature after the problems with it have been explained clearly and repeatedly. Lepricavark (talk) 04:47, 4 January 2020 (UTC)
- And I think it's silly of people to keep bothering me about changing it. That's the real time-killer. From day one, I was clearly not interested, and repeatedly suggested quickly looking elsewhere if they see something vaguely disturbing but harmless in the future. But yeah, personally, I don't dislike you. Good luck with forgetting about this, seriously! InedibleHulk (talk) 05:52, 4 January 2020 (UTC)
- It's not harmless. That's the whole point. But it sounds like you either can or won't understand that your signature is a problem. Or do you understand and just can't be bothered to fix it. But you can be bothered to try to spin this to make it seem like everyone else is the problem, not you. Lepricavark (talk) 17:57, 4 January 2020 (UTC)
- And I think it's silly of people to keep bothering me about changing it. That's the real time-killer. From day one, I was clearly not interested, and repeatedly suggested quickly looking elsewhere if they see something vaguely disturbing but harmless in the future. But yeah, personally, I don't dislike you. Good luck with forgetting about this, seriously! InedibleHulk (talk) 05:52, 4 January 2020 (UTC)
- You expressed annoyance at my adherence to increasingly-standard pronoun usage (no, your username does not make it 100% clear that you are male) in a thread that was caused by your refusal to change an annoying and decidedly non-standard signature. Hence my snarky reply. No, I'm not aware of any prior history nor do I bear you any personal ill will. I just think it's very silly of you to refuse to change your signature after the problems with it have been explained clearly and repeatedly. Lepricavark (talk) 04:47, 4 January 2020 (UTC)
- From the way you wrote that, I get the feeling we've met. If it's any consolation, I'm probably sorry for how things went. Cheers to new beginnings? InedibleHulk (talk) 04:40, 4 January 2020 (UTC)
- Strictly speaking your name could be seen as a reference to She-Hulk as well. --Aquillion (talk) 06:01, 4 January 2020 (UTC)
- FYI to anyone, if you have navigation popups gadget enabled, mousing over a sig will show the user's gender if they set one in their own preferences (there's a note in prefs telling you it will be public). It's very helpful. Someguy1221 (talk) 06:11, 4 January 2020 (UTC)
- @InedibleHulk: How about a compromise? You can accomplish the MDY re-formatting of everyone's timestamps (not just your own) without scripting at Special:Preferences#mw-prefsection-rendering. Do you really need the date linked? —[AlanM1(talk)]— 06:20, 4 January 2020 (UTC)
- If you mean I should check the appropriate box under Date Format, I tried. It's still checked, 77 months later. Does nothing. Is my gender flag working? Yes, I really need the date linked. InedibleHulk (talk) 06:30, 4 January 2020 (UTC)
- That setting changes the way dates are displayed in history pages, not in others' signatures. WMSR (talk) 06:36, 4 January 2020 (UTC)
- Works great, in that case. InedibleHulk (talk) 06:49, 4 January 2020 (UTC)
- Re: prefs, my mistake. I agree the amount of time spent on signature issues is unreasonable. The platform should handle this stuff in a user-proof way. Not that I agree with this user's disruption to make the point. Require standard timestamp. —[AlanM1(talk)]— 07:00, 4 January 2020 (UTC)
- The Wikipedia:Comments in Local Time gadget let's you set whatever date format you want. Of course it will also adjust the time to match your local time. And currently I don't think there is any way to stop this other than by changing your browser so it reports your timezone as UTC, but you could try asking the gadget designer on the talk page Wikipedia talk:Comments in Local Time. Turning off the local time thing goes against the purpose of the gadget, but there could be reason why an editor would want to manually set a time zone rather than follow their browser. It does some other things by default, like add the number of days and uses a non 24 hour clock, but these can be turned off. I've been using it for a very long time and it seems to nearly always work in default mode so I assume will also work for adjust the date format. Of course, it will fail with InedibleHulk's time stamp as I outlined above. Also it would require you to enable JavaScript Nil Einne (talk) 11:05, 4 January 2020 (UTC)
- Re: prefs, my mistake. I agree the amount of time spent on signature issues is unreasonable. The platform should handle this stuff in a user-proof way. Not that I agree with this user's disruption to make the point. Require standard timestamp. —[AlanM1(talk)]— 07:00, 4 January 2020 (UTC)
- Works great, in that case. InedibleHulk (talk) 06:49, 4 January 2020 (UTC)
- That setting changes the way dates are displayed in history pages, not in others' signatures. WMSR (talk) 06:36, 4 January 2020 (UTC)
- If you mean I should check the appropriate box under Date Format, I tried. It's still checked, 77 months later. Does nothing. Is my gender flag working? Yes, I really need the date linked. InedibleHulk (talk) 06:30, 4 January 2020 (UTC)
- @InedibleHulk: How about a compromise? You can accomplish the MDY re-formatting of everyone's timestamps (not just your own) without scripting at Special:Preferences#mw-prefsection-rendering. Do you really need the date linked? —[AlanM1(talk)]— 06:20, 4 January 2020 (UTC)
- FYI to anyone, if you have navigation popups gadget enabled, mousing over a sig will show the user's gender if they set one in their own preferences (there's a note in prefs telling you it will be public). It's very helpful. Someguy1221 (talk) 06:11, 4 January 2020 (UTC)
- Trust me, I could think of quite a few other things to call you. Lepricavark (talk) 04:29, 4 January 2020 (UTC)
- Keep your cookie, but if you're feeling generous, just don't call me "they". It's annoying. You know I'm a guy by my name. InedibleHulk (talk) 04:25, 4 January 2020 (UTC)
InedibleHulk has now updated his gender in Preferences, putting an end to this off-topic discussion |
|---|
|
- Require standard date/time (aka prohibit). I agree individuality is good. However, correctly formatted timestamps are currently the only way the end of a comment can be determined by a bot. One day bots will be smarter but meanwhile the archiving and reply-to issues mean a standard timestamp is highly desirable. Given that the only reason to not have a standard timestamp is to express displeasure against the mindless mob, the signature should be fixed. Johnuniq (talk) 06:36, 4 January 2020 (UTC)
- This is about writing my dates like a regular North American mob member, nice and forward-like. And subtly exposing the past, one day at a time. Mindless masses are cool, in my books. Remember Automatic for the People? Word is buddy's sixty today, pass it on. InedibleHulk (talk) 06:43, 4 January 2020 (UTC)
- I'm not sure all these people understand. It's not like years ago. – Levivich 07:52, 4 January 2020 (UTC)
- You seem to have got this rebellion thing topsy-turvy. Such a trivial matter as making your signature conform to expectations is simply stubbornness, not rebellion, and making quotes about some bore-rock band that filled stadiums and tens of millions of other people follow is about as far from rebellion as you can get. And oh to be sixty again. Phil Bridger (talk) 19:17, 4 January 2020 (UTC)
- @Phil Bridger: This is a thing of truth. They were completely tedious post 1987. Or possibly even '86, I can't remember now. ——SN54129 19:26, 4 January 2020 (UTC)
- Yes! Exactly. Not rebelling here. Simple personal stubbornness, per usual. The "important" thing was just telling you he's sixty now. Boring, predictable round number. Mediocre band, but people remember it. Nothing complicated. InedibleHulk (talk) 21:05, 4 January 2020 (UTC)
- @Phil Bridger: This is a thing of truth. They were completely tedious post 1987. Or possibly even '86, I can't remember now. ——SN54129 19:26, 4 January 2020 (UTC)
- This is about writing my dates like a regular North American mob member, nice and forward-like. And subtly exposing the past, one day at a time. Mindless masses are cool, in my books. Remember Automatic for the People? Word is buddy's sixty today, pass it on. InedibleHulk (talk) 06:43, 4 January 2020 (UTC)
- Require standard timestamp, as nominator. WMSR (talk) 07:48, 4 January 2020 (UTC)
- Require standard timestamp, (aka prohibit other type of timestamps). These standard timestamps are there for a very good reason and are there not just for bots. Timestamps help to understand the chronology in a threaded discussion. As I mentioned in my comment above his signature makes it harder for anyone, who is not in the same timezone as his, to decipher when he made that comment. This is a major inconvenience and an impediment to discussion on talk pages. His reasons for keeping it hardly holds weight. FWIW, Cookies for changing it have already been given. --DBigXrayᗙ 08:26, 4 January 2020 (UTC)
- Require standard timestamp. I'm not hugely fussed about the archive bots, but if the non-standard timestamp prevents proper reformatting for those users who want timestamps displayed in their local time rather than UTC, then that's a significant inconvenience. Fut.Perf. ☼ 08:29, 4 January 2020 (UTC)
- Require standard timestamp. The current timestamp adversely affects or completely defeats a number of widely-used tools, and the counter-argument is entirely uncompelling. I, Hulk, and others have previously commented at length at Hulk's UTP, if anyone is interested in reading further. ―Mandruss ☎ 08:55, 4 January 2020 (UTC)
- Require standard timestamp, regretfully. I wish there was a better way to do it, but there is too much value in having a standardized timestamp for all the reasons listed above, and too little reason why anyone would need to replace it. That said, rather than focusing on one editor, we might want to consider a larger RFC to update WP:SIGAPP and make it unambiguous that signatures must contain a standardized timestamp. The purpose of talk pages is communication, which is best-served by ensuring timestamps are easily accessible to tools, bots, and so on. There's plenty of other ways people can customize their signature without impairing that functionality. --Aquillion (talk) 09:55, 4 January 2020 (UTC)
- I would oppose an update to SIGAPP per WP:CREEP. We know of only one active user using a non-standard timestamp, and there is ample evidence that he would have dismissed any such requirement as "silly". For any other user, I believe that the arguments against, the ongoing parade of complaints, and the fact that they are alone in using a nonstandard timestamp will continue to be sufficient. Wait until there is a demonstrated need. ―Mandruss ☎ 10:19, 4 January 2020 (UTC)
- In my assessment, this is straightforward WP:POINT disruption. The actual issues are petty ones, sure. Relatively minor in the grand scheme of the universe, sure. But they are real. The simple situation of having minor issues and complaints repeatedly brought to your attention and refusing to resolve them, for no real reason whatsoever, is the equivalent of trolling. Per WP:CIR and WP:COMMUNICATE, responding amicably to simple and straightforward issues without causing drama is an utterly base expectation the community holds. Refusing to do so is disruptive editing. The fact that it’s ‘not a big deal’ is not a caveat to any of this. There are no vested contributors. Petty pot stirring and boundary pushing is not a big deal, but that doesn’t mean we should or will tolerate it. Per these community norms, and per the above, I intend to block the user if they continue to refuse to resolve this minor issue, until which point they resolve it. The fact that they essentially say “I’m not choosing to die on this hill but I will” indicates to me that they prioritize petty disruption over the smooth running of the project. ~Swarm~ {sting} 09:58, 4 January 2020 (UTC)
- Require standard timestamp - There should no real reason to ever wikilink timestamps, Also via Preferences all dates for me are set to DMY so currently IncredibleHulks talkpage is a mishmash of both which bugs the hell out of me. –Davey2010Talk 10:56, 4 January 2020 (UTC)
- Require standard timestamp let's just end this shit. This thread has seriously gone off the rails when editors are prevented from challenging others on their incredibly offensive suggestions. Nil Einne (talk) 11:15, 4 January 2020 (UTC)
- Collapsing off-topic discussion is not sending a thread off the rails, rather quite the opposite. This discussion is not about that, "incredibly offensive" or otherwise. But given Swarm's stated intent to block until the sig is changed to use the standard timestamp, this thread seems eminently closable to me, and that would "end this shit". ―Mandruss ☎ 11:21, 4 January 2020 (UTC)
- If the discussion was off-topic, then the whole fucking thing was off-topic. Not part of it. And so is this fucking aside. The fact remains, my comment was incredibly on-topic, to the claim made here, in this thread by another editor that I found unwarranted, or even offensive. It was largely apart from the main discussion, and before it was collapsed, there was zero reason why it would ever come into this discussion. If InedibleHulk wanted to challenge me, that is their right, and I see no harm in them doing so. I probably would not reply, since I generally do my best to say all I need to say and leave it be, hence the long comments. Sometimes unexpected things do come up, like happened here. In this case, that was because my right to reply to a comment I found unwarranted was challenged so I did reply further but this didn't come from InedibleHulk. But mostly I find it best to leave a lengthy reply and avoid getting draw into long back and forths. Suffice it to say, I remain unconvinced there was a reason to selective collapse my reply. Nil Einne (talk) 11:53, 4 January 2020 (UTC)
- Collapsing off-topic discussion is not sending a thread off the rails, rather quite the opposite. This discussion is not about that, "incredibly offensive" or otherwise. But given Swarm's stated intent to block until the sig is changed to use the standard timestamp, this thread seems eminently closable to me, and that would "end this shit". ―Mandruss ☎ 11:21, 4 January 2020 (UTC)
- Require standard timestamp ~ it's absolutely ridiculous that someone who wants to be part of the community (participating in this great project) is unwilling to abide by the simplest and most innocuous of the community's requests, but rather seems to go out of his way to purposely antagonise it. Not at all collegial. Happy days, LindsayHello 12:43, 4 January 2020 (UTC)
- Require standard timestamp – this is incredibly POINTy behaviour. InedibleHulk has been repeatedly told his signature is causing problems and has refused to change it, for no good reason. P-K3 (talk) 14:32, 4 January 2020 (UTC)
- Prohibit (require standard timestamp) and support for Swarm's proposal. Schazjmd (talk) 15:35, 4 January 2020 (UTC)
- Require standard timestamp per Swarm. The long-term refusal to follow requirements is disruptive and a time-sink for those who encounter it. Nick Moyes (talk) 15:42, 4 January 2020 (UTC)
- Require standard timestamp This is perhaps the most pointless WP:POINT disruption I've seen. It's a waste of everyone's time. Der Wohltemperierte Fuchs talk 16:58, 4 January 2020 (UTC)
- Require standard timestamp It breaks archiving. End of. Andy Dingley (talk) 17:35, 4 January 2020 (UTC)
- Let it be The main source of disruption is clearly the complaining, not the lack of stamp. InedibleHulk (talk) 18:42, 4 January 2020 (UTC)
- @InedibleHulk: Please review my above comments, it explains why your refusal to fix something you feel is a non-issue is in itself disruptive, lays out the underlying community rules and norms, and rationalizes a discretionary block purely based on that alone. Note also that we operate by consensus, and, while you have the right to your opinion and it has been noted for the record, there's a clear consensus that your signature is disruptive on its own merits and is to be changed. You can disagree all you want, but you cannot reject it. Refusal to accept a consensus is yet another layer of WP:POINT disruption. Additionally, we can and will issue blocks to enforce consensus when needed. No one wants to see you blocked, but truthfully you and only you are going to force our hand here. This is, again, a really bizarre thing to be forcing a block over this, but at this point, it is quite simply the next step. If not because you agree, if not for fear of a block, please at least respect the consensus here and fix your sig. Take all the time you need to mull it over, but continuing to post your unchanged sig, or continuing to edit without confirming that you have resolved the issue will be interpreted as a refusal. ~Swarm~ {sting} 19:12, 4 January 2020 (UTC)
- If you're going to block me for using the signature I've used since 2013, that would be the biggest disruption ever associated with it. I won't let you. I'll stop using it (after responding to questions at this needless clusterfuck, I mean). InedibleHulk (talk) 20:05, 4 January 2020 (UTC)
- Support indef block, per this suggestion, until they fix it. Andy Dingley (talk) 20:46, 4 January 2020 (UTC)
- What, block me for not using it? Then unblock me once it's fixed, but still unused? How would you even know I'd fixed it? InedibleHulk (talk) 20:58, 4 January 2020 (UTC)
- Support indef block, per this suggestion, until they fix it. Andy Dingley (talk) 20:46, 4 January 2020 (UTC)
- If you're going to block me for using the signature I've used since 2013, that would be the biggest disruption ever associated with it. I won't let you. I'll stop using it (after responding to questions at this needless clusterfuck, I mean). InedibleHulk (talk) 20:05, 4 January 2020 (UTC)
- @InedibleHulk: Please review my above comments, it explains why your refusal to fix something you feel is a non-issue is in itself disruptive, lays out the underlying community rules and norms, and rationalizes a discretionary block purely based on that alone. Note also that we operate by consensus, and, while you have the right to your opinion and it has been noted for the record, there's a clear consensus that your signature is disruptive on its own merits and is to be changed. You can disagree all you want, but you cannot reject it. Refusal to accept a consensus is yet another layer of WP:POINT disruption. Additionally, we can and will issue blocks to enforce consensus when needed. No one wants to see you blocked, but truthfully you and only you are going to force our hand here. This is, again, a really bizarre thing to be forcing a block over this, but at this point, it is quite simply the next step. If not because you agree, if not for fear of a block, please at least respect the consensus here and fix your sig. Take all the time you need to mull it over, but continuing to post your unchanged sig, or continuing to edit without confirming that you have resolved the issue will be interpreted as a refusal. ~Swarm~ {sting} 19:12, 4 January 2020 (UTC)
- Require standard timestamp to enforce a minimum requirement of accessibility. I'd just disable "fancy" signatures wiki-wide, but that probably goes too far for most users' liking. ~ ToBeFree (talk) 19:15, 4 January 2020 (UTC)
- Advise standard timestamp Consensus is rare - and we seem to have something close to a consensus. That should be an eye opener for the Hulk. I am generally a freedom junky, but I can sort of agree with Swarm in saying we have some minimum standards. I am just not sure we need to threaten the editor with draconian blocks over a signature. Perhaps an RfC? ANI is rarely the place for issues that are not straight up disruption to the encyclopedia. Wm335td (talk) 20:09, 4 January 2020 (UTC)
- Require standard timestamp - if it prevents archiving then there is no discussion to be had, surely? The fact this editor has refused to change it is very concerning, as is their general attitude in this discussion. GiantSnowman 20:57, 4 January 2020 (UTC)
General signature timestamp guideline change
The discussion above is currently trending towards a general discussion about signature timestamps - to not fork this discussion, perhaps we can continue below on a guideline change to Wikipedia:Signatures? It currently reads: All signature timestamps must end with the trailing "(UTC)". This is mandatory and required by archiving bots for them to function correctly. Signatures that interfere with the archiving bots are considered disruptive and editors may be blocked for it.
but perhaps should be strengthened to:
Signatures should not include customization to the format of timestamps. All timestamps should adhere to the normally system generated format, ending with the trailing "(UTC)". This is necessary for clear communications, and for archiving bots to function correctly. Signatures that interfere with the archiving bots may be considered disruptive and editors may be blocked for it.
- Thoughts? — xaosflux Talk 14:33, 4 January 2020 (UTC)
- Better to fix the bots to accommodate the humans than the other way around. I hope everyone realizes from a technical point of view how utterly ridiculous this is. Bots should recognize signatures by the use of some kind of signature flag that the four tildes should insert, rather than by looking for a particular string. Bots should be smart enough to read mdy or dmy with or without wikilinks. It’s embarrassing that something as simple as linking the time stamp should break a bunch of bots and scripts. Think about it folks: WMF brings in $100 million a year but our software breaks if someone wikilinks the time stamp. In the year 2020, we have cars that drive themselves and robots on Mars, but Wikipedia, 5th largest website, can’t handle this. – Levivich 15:19, 4 January 2020 (UTC)
- Accommodate which humans besides InedibleHulk? Who else is doing this? Who else knows how to do this? Of them, who wants to do this? To get the standard timestamp, one has to do nothing at all, and nothing at all is never an unreasonable burden. You might as well argue that users should be able to define the character to use in place of the tilde when they sign, so that the software accommodates the humans instead of the other way around. ―Mandruss ☎ 16:22, 4 January 2020 (UTC)
- Er, the WMF has nothing to do with self-driving cars and robots on Mars. Why would the technological capacities of other organizations be relevant to our own? Besides, those things have far more practical utility than these wikilinked timestamps. What's the point of investing resources to enable us to do something that doesn't need to be done? Lepricavark (talk) 17:52, 4 January 2020 (UTC)
- Lepricavark, hahaha investing resources to enable us to do something that doesn't need to be done is exactly what is happening here right now. With $100 million a year, you’d think we could get some normal software, but nooo lets tear each other apart instead. Good plan. – Levivich 20:05, 4 January 2020 (UTC)
- It was your idea to have a straw poll. Well, you got one. Lepricavark (talk) 20:10, 4 January 2020 (UTC)
- Better to fix the bots to accommodate the humans than the other way around. I hope everyone realizes from a technical point of view how utterly ridiculous this is. Bots should recognize signatures by the use of some kind of signature flag that the four tildes should insert, rather than by looking for a particular string. Bots should be smart enough to read mdy or dmy with or without wikilinks. It’s embarrassing that something as simple as linking the time stamp should break a bunch of bots and scripts. Think about it folks: WMF brings in $100 million a year but our software breaks if someone wikilinks the time stamp. In the year 2020, we have cars that drive themselves and robots on Mars, but Wikipedia, 5th largest website, can’t handle this. – Levivich 15:19, 4 January 2020 (UTC)
- Comment I have no objection to this, but it's likely neither necessary, as we aren't seeing multiple issues, nor productive, as it seems IH has dug in his heels on this for some reason. InedibleHulk, please just rise above whatever first made you think, "You can't make me" the first time someone brought this up and to dig those heels in deeper and deeper each time someone complained, until now this feels to you like an issue of principle in which you simply must triumph in the name of all independent thinkers everywhere. It's not an issue of principle. It's just plain not important. It's a small decision you made years ago that isn't in any way symbolic of your individual rights. You don't 'lose' if you decide to change. --valereee (talk) 15:25, 4 January 2020 (UTC)
- This has nothing to do with fighting for free speech, independent thinkers or liberal society. Not even a contest. I'm just calmly refusing to change what I like, like I have for years with very slight impact. It's those fighting for change since it became hot yesterday who believe in winning, I find. InedibleHulk (talk) 20:34, 4 January 2020 (UTC)
- Refusing to change something that no one has complained about is fine. Continuing to refuse to change it after someone has complained is assholery. --JBL (talk) 21:08, 4 January 2020 (UTC)
- Changing for the sake of a gadget, script or tool is pussification, if you want to see this shift in Team America: World Police terms. InedibleHulk (talk) 21:58, 4 January 2020 (UTC)
- Refusing to change something that no one has complained about is fine. Continuing to refuse to change it after someone has complained is assholery. --JBL (talk) 21:08, 4 January 2020 (UTC)
- This has nothing to do with fighting for free speech, independent thinkers or liberal society. Not even a contest. I'm just calmly refusing to change what I like, like I have for years with very slight impact. It's those fighting for change since it became hot yesterday who believe in winning, I find. InedibleHulk (talk) 20:34, 4 January 2020 (UTC)
- Support the proposed changes. Levivich, Please read my comments above, sometimes, as in this case, it is the human that needs "fixing". Nothing wrong with the bots or WMF software. User:Xaosflux is trying to make sure that in future, any more such issues can be swiftly dealt with, without wasting a lot of community time, as we are doing in this thread and IH's talk page for this issue. --DBigXrayᗙ 15:39, 4 January 2020 (UTC)
- Mild Support Any smart-arse who really wanted to get around that original wording could easily do so, and be totally smug about it, and waste lots of people's time trying to deal with the problem they'd caused. But would anyone really be so small-minded and POINTy to actually do that, or not change it when asked? It's a shame we think we might need to modify otherwise quite clear wording just because they might try! Nick Moyes (talk) 16:04, 4 January 2020 (UTC)
- Oppose per WP:CREEP. We know of only one active user using a non-standard timestamp, and there is ample evidence that he would have dismissed any such requirement as "silly". Wait until there is a demonstrated need. Anyway, it takes quite a bit of imagination and technical insight to even figure out how to change one's timestamp. As I understand it, you have to (1) code a nonstandard timestamp in your signature definition, using the appropriate "magic words", and (2) always sign with three tildes to prevent the system from adding the standard timestamp. ―Mandruss ☎ 16:11, 4 January 2020 (UTC)
- The code is printed out in plain gobbledygook in my archives, if anyone wants to dig it up and wield my power. Three tildes is so much easier, you'll love it. But don't make the same mistake I did (going first). InedibleHulk (talk) 22:13, 4 January 2020 (UTC)
- Weak oppose per Mandruss and valereee. We shouldn't change our policy because one person wants to disrupt Wikipedia to make a point. This whole thing is just absurd and the solution is to sign with 4 tildes if you're going to sign at all. — Wug·a·po·des 16:20, 4 January 2020 (UTC)
- Mandruss, Wugapodes, Thanks for the thoughts. What makes you feel so optimistic that we may not have more such folks in future. In fact this is a case that was brought to notice, there may be folks already tweaking their timestamps when they clearly shouldn't. Instead of repeating this entire time wasting process once again from the scratch, I would prefer, we put this clearly in black and white, so that folks planning to test the tolerance limits for the community can be discouraged. Finally WP:SIG is a "guideline". DBigXrayᗙ 16:33, 4 January 2020 (UTC)
- Again, wait until there is a demonstrated need. Act based on what we know, not on what might be. In any case, even the policy part of SIG, SIGAPP, has never been strictly enforced anyway (if it had been, the issue of Hulk's timestamp wouldn't have persisted for years). If you examine the arguments in this discussion that oppose Hulk's timestamp, they generally don't refer to the policy itself but rather to the breakage of tools and the ongoing editor complaints. So the policy itself is fairly beside the point. ―Mandruss ☎ 16:36, 4 January 2020 (UTC)
- Mandruss, Wugapodes, Thanks for the thoughts. What makes you feel so optimistic that we may not have more such folks in future. In fact this is a case that was brought to notice, there may be folks already tweaking their timestamps when they clearly shouldn't. Instead of repeating this entire time wasting process once again from the scratch, I would prefer, we put this clearly in black and white, so that folks planning to test the tolerance limits for the community can be discouraged. Finally WP:SIG is a "guideline". DBigXrayᗙ 16:33, 4 January 2020 (UTC)
What makes you feel so optimistic that we may not have more such folks in future
WP:AGF mostly. Between the existing guidance and WP:POINT, our guidance sufficiently describe how to not be disruptive with your signature. Even if someone doesn't understand and has a disruptive signature, if they really are editing in good faith and here to build an encyclopedia, when asked, they should stop. The only reason we are having this discussion is because asking the editor on their talk page didn't work. Changing ourpoliciesessays of various levels of consensus to address someone intentionally trying to game the system isn't going to help anything; people who want to test the tolerance limits of the community will do so no matter what, and honestly of all the ways someone can do that with their signature, modifying the timestamp is one of the harder ones. (edit conflict) Ŵ̴̬̆̌̕̚û̶̘͌̀͊g̴̡͚̦̒̋ͅà̵̤̰̂̚ͅp̷̳̺͓̻̀ò̸̧͉͋̓ͅd̶̬̥̥͑̄̉ͅȩ̷̲̺̰̓ś̷̥̋͝ 16:52, 4 January 2020 (UTC)
- Support The idea that the bots must conform to the user isn't an argument that holds much water when there's no practical reason for a user to change their date stamp at all. Ideally, that would be technically beyond their purview. But in the meantime, might as well spell it out. Der Wohltemperierte Fuchs talk 16:58, 4 January 2020 (UTC)
- The practical reason for linking the date is letting people click it and learn new things. Yours only sits there, backward. No offense, just does. InedibleHulk (talk) 22:27, 4 January 2020 (UTC)
- Support - there are reasons to do this well covered above, and I'm not seeing any downsides. Annoying signatures of active users are often very difficult/time-consuming to address if the user digs their heels in, as can be seen in this thread (and the related threads). If there's really no downside to this, it seems worth codifying. — Rhododendrites talk \\ 17:40, 4 January 2020 (UTC)
- Support it shouldn't be necessary to spell this out, but apparently it is. There's no compelling reason to be able to wikilink the timestamp and no need to change the bots. Lepricavark (talk) 17:52, 4 January 2020 (UTC)
- Weak Support provided InedibleHulk is grandfathered in Slywriter (talk) 19:01, 4 January 2020 (UTC)
- Support. There is clear support in the given case; this should be part of WP:SIG for the future. ~ ToBeFree (talk) 19:15, 4 January 2020 (UTC)
- Question, Comment, or Concern. I can think of at least two examples outside of this recent controversy where users used a custom timestamp. phab:T231993 filed by Leduyquang03 from a few months ago rings a lot of bells in my mind. The second example is Lourdes who I know does it from time-to-time (link). I'm pinging these users in case they want to weigh in here about this potential rule (which I do kinda support tbh). –MJL ‐Talk‐☖ 19:53, 4 January 2020 (UTC)
- Neutral, as such a requirement seems to already fall under the previously cited guideline. WMSR (talk) 20:21, 4 January 2020 (UTC)
- Oppose The existing guideline already covers the present situation; more elaborate tailoring to the present situation is not necessary to handle the present situation nor any other conceivable future scenario. The rewrite is unnecessarily complicated, and simultaneously strengthens and weakens phrasing for no good reason. --JBL (talk) 21:08, 4 January 2020 (UTC)
- Comment: There is actually another part of the guideline that discourages customised timestamps (under #Purpose of signatures):
... signatures also serve a technical purpose: various user scripts and talk-page archiving bots, including lowercase sigmabot III, rely on their time stamps to know when to archive old threads. It's because of this that it's also important to avoid overly customizing the date output of a signature, as doing so can lead to stale threads persisting long after they'd otherwise be archived.
- However, if a mention in the WP:SIGPROB section is still desired, I suggest a more concise rewrite:
Customizing a signature's timestamp is prohibited, as it will interfere with automated discussion archiving.
- This can be combined with the following line (about failure to sign) to read:
Other disruptive practices include customizing a signature's timestamp (as it will interfere with automated discussion archiving) and failing to sign after being reminded.
LTA
Anyone here experienced in LTA? I have a long-time refspammer I would like to list. Guy (help!) 23:32, 4 January 2020 (UTC)
- User:Bbb23 is the best. Lightburst (talk) 23:36, 4 January 2020 (UTC)
- Have you got a spraycan and a stencil for that? Narky Blert (talk) 01:16, 5 January 2020 (UTC)
- User:Bbb23 is the best. Lightburst (talk) 23:36, 4 January 2020 (UTC)
98.111.189.131
98.111.189.131 (talk · contribs) is making non-stop vandalism only edits, despite repeated (including level 4) warnings... - Adolphus79 (talk) 04:11, 5 January 2020 (UTC)
Apparent legal threat by IP
IP user 98.208.64.39 has posted what appears to be a legal threat at User talk:ToBeFree, threatening "I will be reporting you, should this happen again to both Wikipedia and the German relevant authorities in your nation", apparently in response to a block. PohranicniStraze (talk) 02:44, 5 January 2020 (UTC)
Legal threat after ANI-based block
See Special:Diff/934168029, which appears to be about Special:Redirect/logid/104638690. ~ ToBeFree (talk) 02:45, 5 January 2020 (UTC)
- Merging sections.
PohranicniStraze. ~ ToBeFree (talk) 02:46, 5 January 2020 (UTC) - Now blocked for a little bit longer. ToBeFree, I saw on Facebook that my lawyer lifted 275 pounds in a workout, and I'll put you in touch with him. Drmies (talk) 02:49, 5 January 2020 (UTC)
~ ToBeFree (talk) 03:38, 5 January 2020 (UTC)
Editor won't delete company page
Hi,
My name is Shira and i'm head of marketing for Comsec. I have followed the deletion request procedures twice, and the editor wrote: Please refrain from making unconstructive edits to Wikipedia, as you did at Comsec Consulting. Your edits appear to be disruptive and have been or will be reverted.
Our management team is not interested in having a Wiki page for Comsec, which is why i asked for it to be deleted. I have spent a few hours trying to see how i can communicate this request otherwise. As a private company, we have to have the option to do. Can i please ask for someones help on this?
Thank you very much. Best, Shira — Preceding unsigned comment added by 212.235.30.250 (talk) 12:58, 2 January 2020 (UTC)
- Unfortunately, this is not how deletion works at Wikipedia. In your previous two attempts to delete the article, you first blanked it (which is disruptive, and doesn't delete it anyway) and then used the PROD template, which is only for obviously non-notable articles. The valid reasons for deletion are at WP:DEL#REASON and do not include the subject's wish to do so. You could try WP:AFD, but I'd suggest, looking at the article, that it is probably notable per WP:CORP and would not therefore gain consensus for deletion. Black Kite (talk) 13:07, 2 January 2020 (UTC)
- (EC) I assume this is about Comsec Consulting. To be blunt, we don't really care what your management team is or is not interested in. As a private company, you do not get to dictate what others write about your company, with a few very limited exceptions relating to defamation and similar, but simply writing about the existence of your company clearly doesn't qualify as defamation. In other words, as a private website, we get to chose what we do and do not write about. Once a WP:PROD has been removed, you do not get to add it back. Your only option is to take it to WP:AFD. But if you take it to AFD with the reasoning that your management team doesn't want the article, it will fail. I'm not certain from the article whether or not your company meets our WP:GNG or Wikipedia:Notability (organisations and companies). Although the sourcing seems limited, I do see some info suggesting there may be enough reliable secondary source coverage. Regardless, this is best assessed by someone familiar with our sourcing requirements, not by you someone with a WP:COI who only wants to page gone because your management team doesn't like it. Nil Einne (talk) 13:12, 2 January 2020 (UTC)
- Nil Einne, this is biting the newbies and is far too aggressive. Please stop. DanBCDanBC (talk) 18:41, 7 January 2020 (UTC)
- I do not see that Nil's edit was biting or aggressive, but simply spelling out that encyclopedia articles are not part of anyone's marketing programme so are not under the control of their subjects. It's better to say this clearly rather than string people along with euphemisms only for them to eventually find this out. Phil Bridger (talk) 19:40, 7 January 2020 (UTC)
- Nil Einne, this is biting the newbies and is far too aggressive. Please stop. DanBCDanBC (talk) 18:41, 7 January 2020 (UTC)
- See Wikipedia:Articles for deletion/Comsec Consulting, courtesy of User:Michepman. ——SN54129 13:19, 2 January 2020 (UTC)
- A few years ago, an individual successfully had a bio article of himself deleted. The individual was a (by then) known critic of Wikipedia. PS - Can't remember the fellows name. GoodDay (talk) 13:21, 2 January 2020 (UTC)
- BLP applies to critics of Wikipedia too?! ;) ——SN54129 13:26, 2 January 2020 (UTC)
- GoodDay, Daniel Brandt. Guy (help!) 13:30, 2 January 2020 (UTC)
- Per WP:BLPREQUESTDELETE and WP:BIODELETE, biographies of living persons are basically the only area where the wishes of a subject comes into consideration when it comes to article deletion, in a very limited set of circumstances. Nil Einne (talk) 13:36, 2 January 2020 (UTC)
- BTW, I find it interesting that the page was originally created by User:Shar1R , an editor who's main other contributions seem to have been creating an article on another Israeli company GigaSpaces and one of their products Cloudify , and some Israeli band Nikmat HaTraktor . Suffice it to say, this wouldn't be the first time some company had once thought it a good idea to pay for an article to be written about them only to later come to regret it. Although if this was what happened here, I don't really see anything that bad about the article, regardless of whether the info in it is completely up to date with what the company does now. Nil Einne (talk) 13:36, 2 January 2020 (UTC)
- Comment These issues are solved so easily just by opening an articles for deletion discussion. Shira, we keep articles where notability can be demonstrated. If enough editors can reach a delete consensus, the article will be deleted. Eliteplus (talk) 17:03, 3 January 2020 (UTC)
- Well depends what you mean by solved I think. From the way the AFD is heading, I don't think the article is going to be deleted. And so given the OP's previous comments, I'm not sure if they would consider it an acceptable solution. Still let's hope they take our counsel onboard and accept that's how things work here even if they're not happy. Nil Einne (talk) 12:58, 4 January 2020 (UTC)
Persistent dispute at Croatian Air Force
After removing an AIV report that seems to have been an outing attempt, I've had a look at the underlying conflict. Diffs such as Special:Diff/934031454, Special:Diff/934032086 and Special:Diff/924187200 seem to indicate a long-term conflict between FOX 52 and at least one IP editor.
FOX 52, perhaps you could take a moment to explain the situation from your point of view here. The latest escalation at WP:AIV seems to indicate a need for such a discussion, possibly leading to a community ban or block against a user who appears to be attacking you repeatedly. WP:ASPERSIONS seems to be relevant, for example. ~ ToBeFree (talk) 15:55, 4 January 2020 (UTC)
- From my end, it's been constant battle with several IP's (which may be just one individual) - They're gripe seems to be with using outdated / non-English sources, vs. updated English sourcing. (per: WP:NONENG) - I'd suggest a long term semi-protection on the page- FOX 52 (talk) 04:34, 5 January 2020 (UTC)
Oversight at Talk:Timeline of Romanian history#Tomis
Please oversight Talk:Timeline of Romanian history#Tomis, there is no WP:OUTING so it can be rendered here. Tgeorgescu (talk) 00:12, 2 January 2020 (UTC)
- Nothing there rises to the level of requiring oversight. I've dropped a NPA warning on the IP's talk page though. Blackmane (talk) 00:29, 2 January 2020 (UTC)
- @Blackmane: Ok, good to know. On ro.wiki obscenities and personal attacks usually get hidden from public view. Tgeorgescu (talk) 00:40, 2 January 2020 (UTC)
- @Blackmane: Oh, yes, the culprit is 93.122.250.147 (talk · contribs · IP contribs · WHOIS). Tgeorgescu (talk) 00:43, 2 January 2020 (UTC)
- @Tgeorgescu: there are very specific requirements for Oversight on en.wp, please see WP:OVERSIGHT. Also, Oversight requests should be sent to the oversight request email and not on a very public page such as ANI. Blackmane (talk) 05:15, 2 January 2020 (UTC)
Such can be revdel'd.-- Deepfriedokra 05:37, 5 January 2020 (UTC)
- I HATted that. Looks like it would require a prohibitively large range block to stop it all. There's no clean version, so I did not revdel so as not to lose the thing, though I guess it should be archived. If 147 has been adequately warned, I could block.-- Deepfriedokra 05:45, 5 January 2020 (UTC)
- 147's last edit was January 1st, so I won't block now.-- Deepfriedokra 05:47, 5 January 2020 (UTC)
Undiscussed changes to ~1,500 pages using AWB
On 11 December 2019, Kwamikagami (talk · contribs) unilaterally changed ⟨²⟩ to ⟨ˇ⟩ on Help:IPA/Swedish and Help:IPA/Norwegian and made around 1,500 edits to pages that contained the symbol inside {{IPA-sv}} or {{IPA-no}} using AutoWikiBrowser, in spite of MOS:PRON#Other languages' recommendation to discuss changes to IPA keys in advance. Kwamikagami also unilaterally changed ⟨¹⟩ in Swedish transcriptions to ⟨ˈ⟩, although ⟨¹⟩ had been introduced after a discussion months earlier. When asked to point to the consensus for these changes, the user responded, "The consensus is that we use IPA for IPA", without providing any specific policy, guideline or discussion.
Although the introduction of ⟨²⟩ was not based on an explicit consensus either (but discussed and agreed on by two editors nonetheless), the fact it had been in use on so many pages for more than three years illustrates an implicit yet well-established consensus. I asked for comments on this matter at Help talk:IPA/Swedish, pinging ten users who had recently edited or discussed the Swedish guide, and no one has come out in favor of the new ⟨ˇ⟩, while three have explicitly spoken against it.
I would simply apply BRD if the changes were made only to the guides or to a handful of pages, but the sheer scale of them is making me reluctant to revert them and risk inciting a massive edit war. I want to ask whether Kwamikagami was allowed to make these changes without consulting others first and whether they should keep their privileges, particularly AWB. Nardog (talk) 06:39, 2 January 2020 (UTC)
- Basically, IPA templates should be in IPA, or they're misleading to our readers. You can always find editors who wish to substitute in-house conventions, but such walled-garden usage is detrimental to an encyclopedia with a world-wide scope. We've long had agreement that digits should not be used for tone in Asian, American or African languages. It's only in a few European languages that spurious IPA tone numbers continue to be used. In this case, several publications of the IPA itself explicitly recommend these characters for the two tones of Swedish and Norwegian. They're dated, but at least they're not actually wrong. I don't see why fixing the IPA to actually be IPA needs prior permission, any more than fixing any other error. — kwami (talk) 05:01, 3 January 2020 (UTC)
Off-topic forum |
|---|
|
- I'm not a fan of such large-scale changes when the talk page already made it clear that people would have disagreed. Then again, I hesitate to be too critical of Kwami's mass edit. If an editor is willing to discuss the matter, presumably they're also willing to fix their own large-scale changes if discussion steers towards a consensus they initially disagreed with. AGF prompts us to believe this about other editors without clear evidence to the contrary. I have seen a number of instances when Kwami implemented a consensus that they personally disagreed with.
- If other people are expecting to punish Kwami for an epic game of BRD or, even worse, to explicitly get them to say that they'll self-revert if consensus goes against their stated position, I would hope that we can at least acknowledge that this carries with it a pretty strong assumption of bad faith. — Ƶ§œš¹ [lɛts b̥iː pʰəˈlaɪˀt] 14:47, 3 January 2020 (UTC)
- @Kwamikagami: You've had your say at Help talk:IPA/Swedish, and it is clear you stand alone. Repeating it here, which is a place to discuss not content but conduct, is not going to move the needle in your favor. Can you make a promise not to edit war if I reverted your bold edits in honor of WP:BRD, or, better yet, revert them yourself as Aeusoes1 suggested? (Indiscriminate replacement in IPA-sv wouldn't do it as some instances are of Finland Swedish, which still must use ⟨ˈ⟩.) Nardog (talk) 10:19, 5 January 2020 (UTC)
Weeb Dingle pretending to be new with a different account
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Weeb Dingle (talk · contribs) is an editor whose editing I and others have had issues with; for example, see this and this ANI thread on him, and this post by me on his talk page. I noticed his Nkofa (talk · contribs) account at Talk:Polyamory. By looking at Nkofa's very early contributions, I knew that the editor wasn't new (for example, immediately creating a user page, which is a rare thing for newbies to do and is very characteristic of socks because they want to immediately blend in by having a blue user page). As seen here, I went to Nkofa's talk page and asked him about his previous account(s). He ignored my query and continued editing. I looked at his latest editing and recognized him as Weeb Dingle when I saw him at Talk:Guitar synthesizer. A topic like that is one of Weeb Dingle's interests. I felt that it was too much of a coincidence to see both accounts at Polyamory and interested in a topic like that. I then examined Nkofa's edit summaries -- such as "nonsequitur," "reduced superlatives; updated tenses" and "tone generally neutralised" -- and saw that they are edit summaries that Weeb Dingle uses. After seeing all of that, I had no doubt about Nkofa being Weeb Dingle. As also seen on Nkofa's talk page, I gave him a chance to come clean as Weeb Dingle. He did not. Berean Hunter, a CheckUser, later confirmed them as being the same person.
My issue (like I stated on the Nkofa talk page) with this is the following: Weeb Dingle presents himself as new on the Nkofa user page, stating, "I am not certain what I am doing yet so I hope that people can be patient with me. [...] This is my first day here and I have not yet found a one-click way to insert a date so let me just say it is 22 December 2019." Contrary to what WP:Clean start states, he continued editing in the same areas. It is deceptive because he is not new and others will believe that he is a new editor (as evidenced by the Welcome template on his talk page) editing these same areas when he is Weeb Dingle. Am I to just pretend that I don't know who he is? I didn't want to, especially given my issues with his editing. I think he changed to Nkofa to avoid scrutiny. And WP:SCRUTINY is clear. If an editor wants to change their name, they can change their name. But he pretended to be new. So what should be done in this case? Flyer22 Reborn (talk) 08:30, 4 January 2020 (UTC)
- The editor seemed to imply they were taking this to ANI , but then didn't. I've told them that at a minimum, they need to ensure the connection between the accounts is clearly declared. Nil Einne (talk) 15:20, 4 January 2020 (UTC)
- My apologies for procedural error. I did not see this before posting below. Nkofa (talk) 20:22, 4 January 2020 (UTC)
I have taken the liberty of reformatting the seperately created section below as a subsection of this section, as they concern the same issue. --JBL (talk) 21:02, 4 January 2020 (UTC)
User:Flyer22 Reborn
First, the confession. Until a couple of months ago, I was editing as Weeb Dingle. Sometime around Thanksgiving Day, my laptop crashed. I was able to recover almost everything and to reconnect with all of my online accounts — except for my W'pedia logon, where I'd been relying on the "stay logged in" cookie for months. And fool that I am, the password is one of those "oh this is so clever I'll never forget it" brainfarts. I was not able to find any official way to request assistance with this, I spent hours digging through endless Help pages, and concluded that in that respect I am hosed. Unless there is a way back known by others, or I trip over some handwritten note, the Weeb Dingle account is functionally dead, though I would happily take it up again given the opportunity. I took that as a maybe the Universe is telling you something event and chose to start anew as Nkofa, editing articles and staying out of trouble, in particular avoiding encounters with one particular user. My intent was/is not at all malign, in no way abusing the position of "running multiple accounts." When someone opts to file an official grievance about this, I will move forward gladly.
But I was tracked down by the sockhunter User:Flyer22 Reborn. That opens up a bunch of issues, which will take explanation. What follows relies almost entirely on my imperfect memory; I did not at any point keep a diary of my grievances.
Though I readily stand up for what I believe to be right, I have never in life been comfortable appealing to some authority for support, in large part because I find mobbing (bullying by a group) distasteful at best, even when I am entirely certain of my stance. (In like manner, I have shied away from bringing differences over the editing of articles before a group, as I likely ought have done.) Despite many months of probable cause, I disliked even posting here, but I am now comfortable with it.
Until a decade ago, I was a professional editor. Soon after signing up as a Wikipedia editor, I worked on some article (possibly Romance (love)) for a half-hour, an oddly awkward passage that also struck me as editor-imposed conjecture unsupported by any nearby citation. I fixed the language and marked it up with a couple of templates (which admittedly I was still learning to apply). It was my biggest WP accomplishment to that point, and I did feel a bit proud. Within hours, it was entirely reverted. Knowing that changes of any significance need (supposedly) to be discussed, I checked the Talk page, and found absolutely nothing. This bothered me, because any editor worth the label would (so I assumed) have fixed my missteps and left a helpfully instructive note there or on my own Talk page. There was, though, a comment in the revision history, which basically wagged a finger in my face for doing it wrong. That was how I first encountered User:Flyer22 Reborn.
My degree work was primarily in human relationships and sexuality; I am both published and well-versed in those topical areas, and this has informed my choices for Wikipedia articles needing oversight. As a result, there were repeated run-ins with User:Flyer22 Reborn, no more productive. I began using article Talk pages to explain my changes, and found myself going into ever-greater detail, soon regularly accompanied with quoted examples and bullet-point lists, sometimes using hundreds of words to explain why ten weren't correct. I got much more terse than normal, and have said unkind things about the poor quality of more than a few articles. Soon enough, I was being regularly threatened with various charges and potential sanctions, some tiffs becoming quite ludicrous, as when User:Flyer22 Reborn used a Talk page to harangue me for "abusing" Talk pages.
Yes, I met snarkiness with snarkiness, and I am chagrined to have found myself in such miserable company. That's part of the reason I shifted to Nkofa without pursuing Weeb Dingle more vigorously.
As explained in User:Flyer22 Reborn's "My views on disruptive editors, including WP:Socks, and disgruntled editors," I defer to the standard thus set:
- Regardless of an editor's intention when following another, WP:HOUND, states, "Many users track other users' edits, although usually for collegial or administrative purposes. This should always be done carefully, and with good cause, to avoid raising the suspicion that an editor's contributions are being followed to cause them distress, or out of revenge for a perceived slight. [...] The important component of hounding is disruption to another user's own enjoyment of editing, or disruption to the project generally, for no constructive reason." Notice the "disruption to another user's own enjoyment of editing" part? It matters not what your intention is if "disruption to another user's own enjoyment of editing" is the result of your tabs on that editor/following that editor.
I certainly don't now care about the intentions of User:Flyer22 Reborn, I was highly suspicious that I was being followed spitefully, I am definitely tired of being hounded, and my enjoyment of editing Wikipedia is a fraction of the first months — therefore, the criteria are met.
I seek not anyone's punishment, just some separation: All I want is to be left alone to edit. Issue a restraining order or equivalent. If I make some change in error, then I am glad to learn the basis of the mistake, and not be harangued for crass ineptitude. Though repeat encounters with User:Flyer22 Reborn have eroded my civility, I strive to be more open and interactive with editors, even when I feel them to be entirely wrong-headed. However, I do not view Wikipedia as my social network or online community — nothing wrong with anyone else doing so — rather a place to perform tasks necessary to help point users to credible, timely, reliable information.
I am known as a strong-willed person (IRL, at least); if I am feeling this beaten-down, then there are certainly a dozen who, for the sin of mere self-confidence, have been cowed to silence by User:Flyer22 Reborn, and as many who have given up entirely on Wikipedia. I have no reason to believe that User:Flyer22 Reborn is unique, or even particularly interesting. If this is an environment where the bigger bully is always going to come out on top, I am not interested in being either bully or victim.
Nkofa (talk) 20:21, 4 January 2020 (UTC)
- Hi, User:Nkofa. You say "What follows relies almost entirely on my imperfect memory; I did not at any point keep a diary of my grievances." The "history" system here means you don't need to keep a diary. But when you bring grievances here, you do need to go back in history to make it possible for other users of the noticeboard to see what, specifically, happened; you need to provide diffs. There isn't a single diff in your long text above, nor more than one clickable article name (qualified with a "possibly"). Please see Wikipedia:Simple diff and link guide. If you make the readers here do all the work, you may not get much response. Also, are you aware of the list of your own contributions, top right on every page..? That should be helpful in finding the best diffs. Bishonen | talk 21:18, 4 January 2020 (UTC).
- Nkofa, why did you lie on your user page and say,
This is my first day here
? And why did you say,I am not certain what I am doing yet
, when you are an experienced editor with over 4,400 edits? - I think this report about Flyer22 Reborn is retaliatory. It is, of course, totally unsupported and subjective. Weeb Dingle's habit is to leave rants on talk pages, with no reference to sources and hardly any to Wikipedia policies or guidelines, expounding their personal opinions about how an article should be written. At sexuality topics, Flyer22 Reborn is usually one of the first to respond (to whoever starts a discussion). In these cases other editors often show up as well, and - very importantly - they likewise show no support for Weeb Dingle's ideas. I am sure that in every case, it would turn out that Flyer22 Reborn had edited the article and/or commented on its talk page long before Weeb Dingle ever showed up, hence she was already watching it. So, that's not following or hounding.
- Here are the cases I have dealt with Weeb Dingle; in these you can see clearly the pattern I outlined above:
- The problem is Weeb Dingle, and this is further confirmed by the previous times this user has been taken to ANI by Flyer22 Reborn and Pepperbeast. In the first, Tomwsulcer commented and Doc James closed it; in the second, Black Kite closed it. Doug Weller was also there. Weeb Dingle has also received warnings on their talk page from Toddst1, Doc James, Black Kite, and Flyer22 Reborn.
- Now this user is asking to edit however they want without interference? I don't think so. It makes no sense that they should show up at articles Flyer22 Reborn is already at and ask her to refrain from commenting on this user's ideas when there is no evidence of hounding. And now they say they would happily take up the Weeb Dingle account again given the opportunity?
- I suggest the admins do the following: (1) Block indefinitely the Weeb Dingle account to prevent any further evasion of scrutiny by switching back should the password be 'remembered'. Alternatively, if there is some way to send Nkofa the Weeb Dingle password, Nkofa could be blocked instead and they could be told to stick to the original, primary account. Assuming the former, (2) Require Nkofa to state clearly on their user page they formerly edited under Weeb Dingle, and to edit the Weeb Dingle user page to state that this person is now editing under Nkofa. (3) Warn this user strongly about their attempting to evade scrutiny, about misuse of talk pages, and about their failure to treat Wikipedia as a collaborative environment. Note that I would support even stronger sanctions should others feel they are appropriate. -Crossroads- (talk) 00:08, 5 January 2020 (UTC)
yah I posted on his talk page how to request a lost Password but .... he's lying, all you have to do is look at Weeb Dingle User contributions which ends December 21 ... last I checked Thanksgiving was in November Jena (talk) 02:40, 5 January 2020 (UTC)
Weeb Dingle's unfounded claims of hounding were addressed before. Anyone can go to an article like Romance (love) and see who was there first via the edit history. They can also look at the talk page and see what happened. How Weeb Dingle acted from the start. His password explanation doesn't hold up for reasons already noted. Flyer22 Reborn (talk) 06:16, 5 January 2020 (UTC)
- Nkofa or "Weeb Dingle", after reading all of this, it looks to me like your current user page is a big fat flagrant lie. I have got to admit, I really do not think that flagrant liars should be permitted to edit Wikipedia, because such people cannot be trusted about anything. So, please explain why the community of editors who tell the truth should allow you to continue editing alongside us? Cullen328 Let's discuss it 08:53, 5 January 2020 (UTC)
- Piling on the above, regarding "All I want is to be left alone to edit.". This is a wiki, so that won't happen. Other people is supposed to do their best to improve stuff, including your edits, here. Gråbergs Gråa Sång (talk) 10:15, 5 January 2020 (UTC)
- Weeb Dingle/Nkofa as others have said, your explanation doesn't make much sense considering you were editing as recently as December 21 with the Weeb Dingle account, despite losing access "around Thanksgiving Day" and this is in November or October depending on what country you're referring to. It also doesn't explain why you claimed on your Nkofa user page that December 22 was you first day or you are "now here" (which I think is clearly meant to be "new here"). Other parts of your comment strongly suggest your intention was to create a new account to avoid scrutiny of your editing here. Even editors making a legitimate Wikipedia:Clean start should generally avoid misleading about their history and especially when it comes to why they have a new account. Of course it is impossible to make a legitimate clean start if you are editing the exact same article, and started editing with your new account the day after your last one started editing. I strongly suggest you think carefully about any further comments, since anything but honesty is not likely to go down well and you're clearly on thin ice. Nil Einne (talk) 11:23, 5 January 2020 (UTC)
72.185.118.31
72.185.118.31 (talk · contribs) seems to have made only disruptive edits. These last days he has been warned a few times not to make WP:ERA changes. See also the telling change he made (twice) to his talkpage, proving that he is not willing to abide by our MOS guidelines on this issue. Perhaps it is time to block this editor for a month or so, just to get the point across? Debresser (talk) 00:14, 5 January 2020 (UTC)
- Non-admin response: Looking through their talk page and contributions, I wonder if this user is interested in being here to build an encyclopedia or here to cause disruption. After continuing to maintain a disruptive presence after being blocked, it seems that this user creates more work for others rather than improving WP. Perhaps they need a longer block or blocked indefinitely.–CaroleHenson (talk) 00:30, 5 January 2020 (UTC)
2001:E68:540E:8007:FC2D:19D:2A9B:5C48
user:2001:E68:540E:8007:FC2D:19D:2A9B:5C48 is adding unsourced content after her final warning. CLCStudent (talk) 15:33, 5 January 2020 (UTC)
Whydopeoplebother
User:Whydopeoplebother keeps removing or refactoring other users' talk page comments at Talk:Video game exploit. He has been warned by me and User:S0091 to quit, but has blanked his talk page of the warnings and has continued his behavior. His userpage states "A veteran gamer of 30+ years and an experienced game designer. I won't bother replying to complaints about edits, I only remove misinformation and provide more accurate diagnostics. Don't like it? too bad. I'm here to provide educational material, not comply to the bias of the toxic or uninformed." Can an admin try to discuss this with this user, as warnings have not solved the issue? Hog Farm (talk) 05:08, 5 January 2020 (UTC)
- I went ahead and blocked them for 31 hours, with an explanatory note. The user page pretty well says it all. Perhaps someone with better interpersonal skills can reach them.-- Deepfriedokra 05:19, 5 January 2020 (UTC)
- Deepfriedokra, I have left a friendly note on their talk, hopefully that will engage a dialogue. Captain Eek Edits Ho Cap'n!⚓ 06:49, 5 January 2020 (UTC)
- Although point blank removing the comments was clearly inappropriate, I'm not sure that any of those comments are useful for further development of the article. And as they are now all at least 10 years old, I've archived them all. Nil Einne (talk) 10:51, 5 January 2020 (UTC)
- User blanked their talkpage. They do not seem to be interested in communication.--WaltCip (talk) 16:36, 5 January 2020 (UTC)
- I just saw that too. Pinging Hog Farm so they are aware as well. Appreciate the effort CaptainEek and Nil Einne. Not sure where to go with this now. Wait and see? S0091 (talk) 18:13, 5 January 2020 (UTC)
- I guess just wait out the block and see what the user does after the block expires? Maybe since the talk page comments they were riled up about were archived, the user will desist. Hog Farm (talk) 18:18, 5 January 2020 (UTC)
- (EC) I would say yes. Editors who refuse to communicate are frustrating and not editing with the collaborative spirit required but I'm reluctant to advocate a block for it unless it's causing problems. The talk page issue is hopefully resolved now that I archived the page. I wasn't aware the editor was also edit warring on the article until now. If they return to that when their block expires, then I longer block is likely in order. If not, we can only hope they don't repeat similar problems elsewhere, and also start to communicate a lot better. If they do earn another block, I would support quick escalation given that their lack of communication makes it difficult to know if they are going to improve. Nil Einne (talk) 18:28, 5 January 2020 (UTC)
- The one positive is that we know they saw the messages. Hopefully something will sink in. Fingers crossed, anyway. S0091 (talk) 18:38, 5 January 2020 (UTC)
- I just saw that too. Pinging Hog Farm so they are aware as well. Appreciate the effort CaptainEek and Nil Einne. Not sure where to go with this now. Wait and see? S0091 (talk) 18:13, 5 January 2020 (UTC)
- User blanked their talkpage. They do not seem to be interested in communication.--WaltCip (talk) 16:36, 5 January 2020 (UTC)
- Although point blank removing the comments was clearly inappropriate, I'm not sure that any of those comments are useful for further development of the article. And as they are now all at least 10 years old, I've archived them all. Nil Einne (talk) 10:51, 5 January 2020 (UTC)
- Deepfriedokra, I have left a friendly note on their talk, hopefully that will engage a dialogue. Captain Eek Edits Ho Cap'n!⚓ 06:49, 5 January 2020 (UTC)
