Wikipedia:Move review/Log/2023 April: Difference between revisions

Content deleted Content added

Inline

Revision as of 17:40, 18 April 2023

< 2023 March	Move review archives	2023 May >

2023 April

Grey Goose (vodka) (closed)

Withdrawn – Decision endorsed —Locke Cole • t • c 16:00, 10 April 2023 (UTC)[reply]

The following is an archived debate of the move review of the page above. Please do not modify it.

(involved) BilledMammal relisted the discussion after nine days, after which there was one additional !vote supporting the move. This was originally closed as rough consensus to move by CityUrbanism. After being listed at WP:RM/TR in uncontroversial moves, it was challenged and an opposing !voter replied to the discussion without disclosing their involvement, and between that discussion and a discussion on the closers talk page, they withdrew their close. Not counting the involved editor, there was only one editor who had a concern about the closure, and given that it was relisted and the only additional !vote was a support, this looks like forum shopping (trying to get someone else who might agree with the involved editor to close it in their favor). I believe the result should be overturned to the original result and the move performed as shown by the strong consensus in favor. —Locke Cole • t • c 14:57, 9 April 2023 (UTC)[reply]

16:06 – Original close as moved.

16:10 – Original closer requests technical help at WP:RMT to implement the outcome of their close, in line with WP:RMNAC.

17:13 – Uninvolved editor Dr. Vogel intervenes at WP:RMT by expressing their concern that the close may have been wrong; this is equivalent to Dr. Vogel doing the same thing on the closer's talk page.

17:27 – Original closer calls up a random administrator using Template:Admin help, to review their close.

17:32 – Involved editor In ictu oculi also intervenes at WP:RMT, asserting that the close was wrong, but does not move the request to contested requests; that's the same as if an involved editor complained to an RM closer about their close on their talk page.

17:44 – Uninvolved editor EdJohnston (administrator) tells the original closer that *if they feel* that someone else should reclose, they can self-vacate (not even going so far as to recommend undoing the close).

17:53 – Original closer, having the choice of undoing their close or directing In ictu oculi to start a move review, chose the former.

The RM was then reclosed as 'no consensus'. So this was just like someone complaining to a closer on their talk page, and that closer choosing to reopen the discussion. It doesn't matter if the person complained is involved; RM participants who are not happy with the outcome can absolutely complain. Nothing prevented the original editor from following through with their technical request. The post-MR technical request was not moved to contested requests, and it was not really contestable on that level. The closer made the choice of their own will. So the process was fine.

Red Slash's close is reasonable. So I endorse. —Alalch E. 16:12, 9 April 2023 (UTC)[reply]

Endorse - Uninvolved. This is a somewhat ~~gray area~~ Grey Area of policy, which isn't quite as prescriptive as either side might make it out to be. Opinions were split about how to interpret existing guidance, with some good and some bad arguments made all around. I think a no consensus close is a reasonable way to go, keeping the main title a disambiguation. — Rhododendrites ^talk \\ 16:56, 9 April 2023 (UTC)[reply]
Endorse, uninvolved. This can be revisited in some future period. BD2412 T 03:26, 10 April 2023 (UTC)[reply]

The above is an archive of the move review of the page listed in the heading. Please do not modify it.

Hindu terrorism

The non-admin closure of this move request that changed Saffron terror to Hindu terror with the claim that there is "rough consensus" is nothing but a blatant misleading WP:SUPERVOTE.

I initiated discussion on the closing editor's talk page[1] and so far I have only found them to be giving more weight to their own definitions and standards instead of those that are generally accepted. When shown how the closure was factually incorrect, their argument was these points were "never raised or discussed in the RM discussion" and their "my usage of "rough consensus" is meant to indicate my stance that, while I did ultimately find a consensus (by examining and appraising the range of arguments made in the RM discussion itself, as discussed in my closing statement), I also wanted to make clear that it was a close call."[2]

I am also highlighting that 3 options were mostly discussed. Retaining "Saffron terror" had the largest support, while some had supported "Hindu terror"/"Hindu terrorism" and "Hindutva terror" but "Hindu terrorism" didn't have the largest support. It's beyond necessary that this supervote should be overturned. Capitals00 (talk) 18:32, 2 April 2023 (UTC)[reply]

Comment (involved). I was also quite surprised with the close of "rough consensus", when there were 7 opposes, and 6 supports (including the nominator). There were no frivolous votes that I could see. I think the closer overinterpreted the arguments made. The nominator worked hard to sway the opponents, but it didn't make much headway. I think "no consensus" is the obvious result. -- Kautilya3 (talk) 22:57, 2 April 2023 (UTC)[reply]
Overturn to no consensus - Uninvolved except insofar as I made a comment when this came up over at ANI. I have a hard time seeing consensus in favor of "Hindu terrorism" (or much of anything) in that discussion. Some people argued for/against WP:CONSISTENT, some people argued for/against WP:COMMONNAME, some people argued for/against WP:RECOGNIZABLE, there was a side discussion about the proposed name being tainted by political rhetoric, and there was an alternative provided which seemed to get a good amount of support (including some who disagreed on the rest). It's not surprising that "Hindutva terrorism" proved an acceptable compromise for many, since the very first sentence of the article makes clear that it's in fact Hindutva terrorism that's the subject (i.e. it's about a form of religious nationalist terrorism, not religious terrorism). All of this is to say there's not really consensus there for anything. IMO the most appropriate outcome would be "no consensus to move, with a recommendation to start a new move request to see if there's consensus for a move to 'Hindutva terror[ism]'". Adding: to be clear, I'm not saying this was a supervote. I just don't think the closing statement got it right. — Rhododendrites ^talk \\ 23:21, 2 April 2023 (UTC)[reply]
(edited the article) Overturn to no consensus per Rhododendrites. Not such a bad summary of the discussion, but a strangely bad final conclusion regarding consensus. I'll add: The burden is on move proponents to create a consensus that the proposed name is the common name, it isn't enough to assert that the current name is not the common name. Furthermore the predominant subject of the article is the term itself, its origins and usage. This is significantly a WP:WORDISSUBJECT-type article (... is a term used for ...), and there is a longstanding dispute about how it should actually be written, and how the subject should be formulated. It's illogical then to say that the term is not the common name for the term. —Alalch E. 00:27, 3 April 2023 (UTC)[reply]
On a note of clarification, about 50% of the article is about terror incidents, so the notion that the article is just about a term is dispelled by the content itself. As sources such as this one make plain, the original title is just a nickname. Iskandar323 (talk) 06:24, 3 April 2023 (UTC)[reply]
Endorse: (Involved, nominator) I couldn't really tell which way this discussion would go, mainly because the votes were roughly balanced, and a lot of closers just do a vote count or hedge with a 'no consensus'. However, I was pleasantly surprised to see the closer go over the discussion with some rigor and assess the discussion based on the strength of the arguments with respect to policy. As a roughly even split numerically, the closer was within their rights to resolve upon a rough consensus based on policy strength. In no way did the closer overturn an overwhelming numerical superiority of oppose votes, such that the close could be considered a WP:SUPERVOTE, nor did they ignore policy and the proper weighting of the discussion. On the contrary, they appear to have put significant effort into the close. The closer also correctly appraised that a number of the oppose votes here were largely frivolous in nature. First there were the oppose votes that claimed the existing title was the WP:COMMONNAME, despite this being clearly refuted in the opening evidence. Then there were complaints that no WP:RS used the proposed term, another argument dispelled by the opening evidence. And then there were the arguments that the term was invented by the BJP, which was again belied by the opening evidence. Given how riddled the discussion was with flawed assertions, the closer did an admiral job picking through it. Iskandar323 (talk) 06:03, 3 April 2023 (UTC)[reply]

Just to point out, among many other faults, this comment glosses over the fact that the "opening evidence" was picked apart fairly early in the discussion; it also falsely claims that the closer believed the votes to be frivolous - I have not found such a statement from the closer either in the close or in the discussion on their TP, and it seems inappropriate to assume as such. Captain Jack Sparrow (talk) 07:31, 4 April 2023 (UTC)[reply]

You are welcome to your opinion, but I personally saw no picking apart, just cherrypicking. Iskandar323 (talk) 18:29, 4 April 2023 (UTC)[reply]

Cherry picking would be to talk about the opinion part of a comment, but to ignore the part of putting words in someone else's mouth :) . Captain Jack Sparrow (talk) 20:01, 4 April 2023 (UTC)[reply]

Endorse. (Involved, original closer) I readily acknowledge that this was a close call, but I think the arguments in favor of the move had a small yet meaningful advantage in strength. Once the inconclusive lines of argument had been factored out, the supporters of the move still had policy-backed arguments to turn to (WP:RECOGNIZABLE and WP:PRECISE in particular). Meanwhile, the arguments against the move – while they were reasonable – did not provide a similar policy basis. Thus, I ultimately found it reasonable to close in favor of the argument that was more directly grounded in titling policy. ModernDayTrilobite (talk • contribs) 13:56, 3 April 2023 (UTC)[reply]

Overturn to no consensus (commented to oppose) The close was detailed which is good but it was inaccurate reading of the overall discussion. There was clearly zero consensus for any page move. REDISCOVERBHARAT (talk) 16:16, 3 April 2023 (UTC)[reply]

Endorse. <uninvolved> When policy-based arguments tip the scale, then there is a strong community consensus that's been garnered. This is never an easy call when some editors locally disagree with that community consensus. This was a good and reasonable close. P.I. Ellsworth , ed. ^{put'er there} 16:22, 3 April 2023 (UTC)[reply]

Overturn to no consensus. (uninvolved) The arguments in favor relied heavily on Google n-grams. Opposing editors objected that mere word counts did not take into account recentism, quality, and overall context of sources using particular terms. The closer disregarded those objections on the basis that certain terms existed in the 1940s, but this shows a lack of consideration for the full nuances of the objections. Sennalen (talk) 19:10, 3 April 2023 (UTC)[reply]

Overturn to no consensus (involved, voted oppose) (1) Noting that among the six support votes, two (1 2) were completely based on WP:CONSISTENT, and another two (1 2) mentioned it as part of their reason to support move. The closer themselves noted that WP:CONSISTENT does not support either title—which would mean that those two support votes did not support the move, while the other two partly did not. (2) As I already noted on the RM, most of the article is about the term (i.e. the former, original title) and its usage, and the contention around the term, which a commenter above said makes it “significantly a WP:WORDISSUBJECT-type article”. Obviously, if the term is the subject, then the term should be title. The part of the article that is not about the term is just a detailed section about three individual bomb blast cases, all three of which have their own articles. In other similar articles, such as Islamic terrorism, you don’t find similar content forking, at best one or two lines describing terrorist incidents. (3) The closer has mentioned two reasons for the close: recognisability and precision. WP:RECOGNISE was mentioned in one support vote and implied in another (both of these also mentioned WP:CONSISTENT, which the closer says does not support either title) while WP:PRECISE was implied in one (“very hesitant”) support vote. The main support arguments, including the nom, were based on WP:COMMONNAME and WP:CONSISTENT, not these two. Little or no discussion on the RM about whether or not these two apply. That does not equal “rough consensus to move.” I’d argue that if recognisability is the issue, then Hindu extremism (one of the redirects to the page) is as viable, if not more, as the new title. It is wider in scope and probably better defined in reliable scholarship. Similar arguments for other titles exist for precision. The lack of discussion on these two policy in the RM is because the support votes using these themselves were relying half on the other two guidelines, and not because they indisputably apply. The close is based on the assumption that they do. UnpetitproleX (talk) 00:22, 4 April 2023 (UTC)[reply]
Overturn to no consenses (involved) The close seemed like a supervote. Statements like "Opponents of the move largely sought to criticize the proposed title, "Hindu terrorism", rather than to give affirmative cases for retaining "Saffron terror" " (which is exactly what you are required to do when voting oppose in a move request, and can in no way be held against those who voted oppose) are inconsistent with how WP policy works.

Further, "rough consensus" cannot be established when there are clear, non trivial arguments that the proposer has failed to satisfy (which include, but are not limited to, the fact that the proposer claimed their entire premise was based on WP:NDESC - a policy that has nothing to do with the move request, as discussed in the section below the MR; The fact that the proposers have not yet been able to define what even is Hindu Terror, so on ans so forth)

Lastly, the criteria used by the closer, highlighted in the first paragraph, revolves around why they consider "Saffron Terror" to not be the perfect title; It in no way implies that the proposed title is a better one. Indeed, the question of why "Hindu Terror" is a better title does not even feature in the justification of the move, and even the words "Hindu Terror" are not to be found in the description of the rationale behind the move.Captain Jack Sparrow (talk) 07:20, 4 April 2023 (UTC)[reply]

The "affirmative cases" argument is a case of poor phrasing on my part, and did not form a meaningful part of my actual thinking in the close. For more detail, see my discussion of that point during the earlier discussion on my talk page (diff here). ModernDayTrilobite (talk • contribs) 16:53, 4 April 2023 (UTC)[reply]

But that did seem to be the criteria which was used as your logic for the move, though perhaps not intentionally. The arguments that you stated as having guided your opinion both revolved around particular flaws of the current title, not the merits of the proposed title. The same arguments were also raised against the proposed title, which were not considered in the close. For example, in terms of Recognizability, those supporting the title were not even able to find enough good sources to properly define what "Hindu Terror" actually was; And in terms of Precision, they also failed to show that the term is indeed accurate to the topic, with no good source to show that.

It may not have been a conscious supervote, but I think you did lend an unfair weight to the arguments on the side of those proposing. Captain Jack Sparrow (talk) 20:12, 4 April 2023 (UTC)[reply]

Your comment about recognizability is not about precision. The term "Hindu terrorism" is self-explanatory, like any other term combining 'religion + terrorism' to anyone. A spade is a spade stuff. All religions have extremists and all religions have the potential for a minority of their extremists to commit acts of terror. Not really news. I would have to question any line of argumentation that seeks to slyly question the validity of the term despite clear evidence of usage in sourcing for far longer than the prior term. Murmurings along such lines are highly questionable with respect to NPOV. Editors should take care to ensure that they are not simply parroting documented ideological dogma, e.g.: The BJP’s stated position, in each case, has been to reject any link between religion and acts of terror [...,] attack the very phrase “Hindu terrorism,” and to claim that it is a myth conjured up by the Congress” [3] Iskandar323 (talk) 04:52, 5 April 2023 (UTC)[reply]

Lots of fluff but no substance. You have repeated this argument over and over, to the point of bludgeoning; And it was clearly explained to you why you were wrong, and how nationalism cant be clubbed with religion, at another one of your move requests which was closed as not moved. Captain Jack Sparrow (talk) 09:42, 5 April 2023 (UTC)[reply]

When you leave no room for a diversity of opinion by accusing others of being wrong, presumably because you think you are right, you beg a response. Religious nationalism is just a politicized religious movement whose proponents hold the ideological goal of better combining their religious beliefs with the function of the state - a pretty common religious fantasy. Wordplay really. One could just as easily posit the term "Islamic nationalist terror" to describe the Islamic State for seeking a theocratic state. Indeed, the parallels to other "nationalist terrorisms" have already been drawn. Iskandar323 (talk) 12:07, 5 April 2023 (UTC)[reply]

Again, too many words for too little value. If you are saying religious nationalism is the same as religion alone, you are just plain wrong (as pointed out to you in the linked discussion above); If you are not claiming that, then this comment is pointless. Captain Jack Sparrow (talk) 17:16, 5 April 2023 (UTC)[reply]

A separate point was being made there related to ethnicity. Unrelated. Iskandar323 (talk) 18:01, 5 April 2023 (UTC)[reply]

Both were discussed, and you failed to counter either.Captain Jack Sparrow (talk) 09:10, 6 April 2023 (UTC)[reply]

I'm involved, and so am genuinely unsure of how to call this, and am not going to !vote. However, I want to point out that weighting arguments by policy is exactly what a closer is supposed to do, and doing so is not evidence of supervoting; quite the opposite. As such, at least a few opinions here aren't based in policy, which is unsurprising, given that many comments in the move discussion were not, either. FWIW; if this is overturned to no consensus, I would recommend a new RM specifically to settle the Saffron terror vs Hindutva terrorism question, leaving out Hindu terrorism entirely. The three-way split makes this harder to assess. Vanamonde (Talk) 16:53, 5 April 2023 (UTC)[reply]
Overturn (relist). Supervote. Non-admins are not entitled to admin discretion to call a rough consensus. A rough consensus is a divination of where the closer thinks it is headed, even though it is not there yet. Let the close add there !vote and see where the discussion goes. Don’t close as “no consensus”, the discussion is not finished. —SmokeyJoe (talk) 10:18, 11 April 2023 (UTC)[reply]
- It was opened on 25 Feb and relisted twice. When it was relisted the second time, there had been no comments at all in 9 days. In the time after relisting, there was just one comment (by one of the already-active participants) and then nothing for 11 days until it was closed. I don't think more relisting is the answer here. — Rhododendrites ^talk \\ 13:32, 11 April 2023 (UTC)[reply]
  User:ModernDayTrilobite, in their close, injected sufficient more input to justify the relist. SmokeyJoe (talk) 21:15, 11 April 2023 (UTC)[reply]
  
  If not relisted, then, I read it as a clear “no consensus”. SmokeyJoe (talk) 14:05, 12 April 2023 (UTC)[reply]
For what it's worth, my intention with the term "rough consensus" was merely the sense described in the last sentence of WP:ROUGHCONSENSUS: Sometimes the term rough consensus is used to indicate a slight consensus. If the term has any further nuances beyond that, I wasn't aware of them and didn't intend to invoke them. ModernDayTrilobite (talk • contribs) 01:12, 12 April 2023 (UTC)[reply]

I strongly disagree with that; with very few exceptions non-admins are allowed to close any discussion an admin is permitted to close, and that includes close discussions. BilledMammal (talk) 02:01, 12 April 2023 (UTC)[reply]
You are unfamiliar with the term “admin discretion”?

Close discussions are not the same as rough consensus. A close discussion may nevertheless be a consensus. A rough consensus is not a consensus. It’s an almost-consensus that someone with authority may use their discretion to cut short continued discussion, in the interest of moving on to more important matters. SmokeyJoe (talk) 14:04, 12 April 2023 (UTC)[reply]
You are drawing procedural distinctions that do not exist in practice. Discussion outcomes exist on a spectrum, from the clearest consensus to a lack thereof. Somewhere on that spectrum is the threshold for making a change on Wikipedia versus not. Any user is able to determine whether that threshold is met; we suggest that contentious discussions be left to admins only to ensure an experienced closer, and that the closer can take any flak that ensues; we do not have special powers to create consensus that non-admins cannot. Vanamonde (Talk) 17:23, 12 April 2023 (UTC)[reply]
There is important subtle meaning to the terminology. Rough consensus is, and always has been, reserved for admins to make a discretionary call. The point of calling a rough consensus is to say “Enough!” “We haven’t reached a consensus, but more investment in discussing it would be a net negative, and so I’m using admin discretion to call a particular result even if it is slightly arbitrary”. It is used where the discussion is becoming a waste of time, but a decision is needed. Admittedly it has fallen out of common use in favour of near endless relisting, and also RM and MR have wandered away from the formalities of proper closings.

Non admins are not entitled to call a “rough consensus”. The closer has admitted that they meant “slight consensus”, so all is well. That is defensible. Personally, I am not convinced that it was a slight consensus, as he injected too much debatable analysis, but if he !voted that analysis, and was not then disagreed with, that would be a consensus. The advice of WP:Supervote is that where in such close cases, a closer should !vote instead.

If others think that he did call an accurate slight consensus, that’s fine. It was very close. I call it a Supervote because I can easily believe that a different closer might have called it “no consensus”. SmokeyJoe (talk) 06:15, 13 April 2023 (UTC)[reply]
While I partially disagree with it (I think if the vast majority of closers would have closed a discussion differently we should overturn, even if the close could be seen as reasonable) the standard isn't that a different closer might have closed it differently, its that the close was unreasonable. I'm not seeing that here. BilledMammal (talk) 12:24, 13 April 2023 (UTC)[reply]

"Rough consensus is, and always has been, reserved for admins to make a discretionary call." that's just wrong. WP:CONSENSUS says nothing like that. Of course the deletion guidelines for admins refer to admins and not editors; that page does not discuss more general closes. If you have any basis in policy for what you're saying, now is the time to demonstrate it. Vanamonde (Talk) 15:00, 13 April 2023 (UTC)[reply]

I call it a Supervote because I can easily believe that a different closer might have called it “no consensus”
with love, bro, any activity that requires critical analysis is going to lead to different people coming to different conclusions. Red Slash 05:55, 17 April 2023 (UTC)[reply]
Indeed. The answer, if such a detail critical analysis is required, !vote that analysis and see if the next participant agrees or disagrees.

The closer should be the least important participant in the discussion. Less important than any contributing participant. In this RM, the closer supervoted.

I’m not convinced that he supervoted the wrong way. I am convinced that the discussion does not look like a consensus. SmokeyJoe (talk) 11:04, 17 April 2023 (UTC)[reply]
Endorse. I considered closing this myself but decided against doing so as a move I participated in was referenced by editors in this move and though I felt that my arguments there were not applicable to this move request it was still too close to WP:INVOLVED for my comfort. If I had closed it, my assessment would have been similar, with a rough consensus against the current title based on strength of argument; while a no consensus result was possible, the result the closer found was permissible and in my opinion correct. BilledMammal (talk) 02:04, 12 April 2023 (UTC)[reply]
Overturn to no consensus. (Uninvolved) I don't see the consensus the closing editor is talking of. 117.228.212.65 (talk) 09:50, 12 April 2023 (UTC)[reply]
I trust the closer will give this first and only edit by an IP user all the attention it deserves. Iskandar323 (talk) 09:56, 12 April 2023 (UTC)[reply]

I do not believe that IPs should be entitled to !vote in these discussions, or indeed to edit anywhere in projectspace. IP editors lack accountability. There may be someone with an involved history. They may be editing logged out in violation of WP:SOCK. Some IPs claim a philosophical objection to registering, but they could at least sign with a nickname to identify themself as an individual. SmokeyJoe (talk) 06:19, 13 April 2023 (UTC)[reply]

Disagree with args that tend to belittle IP editing. Such registration elitism is not in accord with WP:AGF, nor does WP:5P4 make any such distinction. Perhaps mine is a different experience, since I began editing WP when it was only three or four years old and didn't register until early 2009. Few of us probably remember the tremendous amount of battleground behavior that took place back then, which is the main reason I avoided registering. Heh... back then I stuck to a lot of CE and vandaledit blasting, a lot of F-word removals and such, I mean almost nobody had any respect for Jimbo's Giant Jigsaw back then! Sock concerns? Seems to be just as easy to sock-edit with an anonymous registered username as for an IP usernumber. Truth be told, opinion-weight should probably be as different for IP editors such as the above as it would be for an obviously inexperienced registered editor unless the IP editor has a proven track record. Guess what I'm sayin' is that the distinction should be by perceived experience level and, unless they show otherwise, IP editors should be given the benefit of the doubt. P.I. Ellsworth , ed. ^{put'er there} 10:58, 13 April 2023 (UTC)[reply]

To be honest, the first thing I did when I saw this comment was to check if the CT area had IP restrictions, and was surprised to see it didn't. This is a user at an IP address that has been used solely to vote, at a move review, from the get-to ... which is obviously not 'I'm new to Wikipedia' behaviour, and isn't likely a 'don't bite the newby' situation. Sock risk high. Iskandar323 (talk) 11:25, 13 April 2023 (UTC)[reply]

Could be an unregistered editor whose IP recently changed and has a track record under several IP numbers. I tried to keep track of my own changing IP addresses back then, but my provider kept changing the numbers so often that I stopped. BotD, BotD, BotD! P.I. Ellsworth , ed. ^{put'er there} 12:02, 13 April 2023 (UTC)[reply]

According to whatismyipaddress it is likely static. BilledMammal (talk) 12:24, 13 April 2023 (UTC)[reply]

Hey, now that's an interesting IP finding website. It brings up my present IPv6 address, which my system config tells me is a temporary (dynamic) IP. That website, however, says that my IP address is "likely static". Hmmm... BotD, BotD, BotD! P.I. Ellsworth , ed. ^{put'er there} 14:25, 13 April 2023 (UTC)[reply]

And to address the IP editor's concern, policy-based arguments carry the weight of WP:COMMUNITYCONSENSUS. P.I. Ellsworth , ed. ^{put'er there} 11:30, 13 April 2023 (UTC)[reply]

Overturn to no consensus (uninvolved) There was no consensus for moving the page to any of the proposed titles. The closing note was big but it still failed to point out the arguments that were made against the page moves. desmay (talk) 18:40, 16 April 2023 (UTC)[reply]
Endorse. <uninvolved> Interesting close, votes were analyzed by closer according to their weight. Precise titles on Wikipedia are necessary given it's English Wikipedia where titles should be recognizable rather than going after google hits and as someone pointed out in discussion as well that analysis of google hits also bring current title with more results. It was fairly a reasonable close. 2402:E000:629:49BF:0:0:0:1 (talk) 03:19, 18 April 2023 (UTC)[reply]

If you read the discussion, you will realise that neither was the title accurate, nor recognisable and the argument of it being more common was also shredded apart due to the data being manipulated incorrectly by the person who had made that claim. Captain Jack Sparrow (talk) 06:31, 18 April 2023 (UTC)[reply]

@CapnJackSp: Stop bludgeoning the process with your, at this point, tiresomely over-reiterated personal opinions laced with aspersions. WP:NPA aside, masquerading your views as if they are statements of fact is unconstructive. Iskandar323 (talk) 07:58, 18 April 2023 (UTC)[reply]

The fact that the NGRAMS you used was wrong isnt my opinion, it is fact. Adding new search terms will distort the data, this isnt some new theory of mine. And it isnt NPA to say that the data was manipulated incorrectly. Manipulated is used in the same sense as handled, and I think you may have misunderstood it as an accusation of intentionally manipulating data to favour your side. I cannot say if it was intentional, but I can say with certainty that the data was handled wrongly.

At the same time, it is absurd to see an allegation of bludgeoning the process from you; A cursory reading of this page and the preceding MR (where there is only one oppose comment you have not replied to, repeating arguments over and over) makes clear who is actually bludgeoning. Captain Jack Sparrow (talk) 08:22, 18 April 2023 (UTC)[reply]

Funnily enough, when I checked the edit history it seems like this is the only edit that the IP has made. By your standards, this seemingly disqualifies their vote :) . Captain Jack Sparrow (talk) 08:27, 18 April 2023 (UTC)[reply]

'Manipulation' is obviously a term with negative connotations. Stop the trolling. Iskandar323 (talk) 08:32, 18 April 2023 (UTC)[reply]

Perhaps for those who dont have much experience dealing with data, or how its supposed to be treated while drawing any sort of observation from it. If you dont trust me, google for "Data Manipulation Courses". Captain Jack Sparrow (talk) 08:37, 18 April 2023 (UTC)[reply]

I indeed read the discussion and the same google hits claim was confirmed by another editor in the discussion, perhaps you missed that or he can tell whether it was data manipulation or you are casting aspersions here. Also I stressed on the title being precise and recognizable more than google hits thing. 2402:E000:629:49BF:0:0:0:1 (talk) 10:46, 18 April 2023 (UTC)[reply]

Endorse the move discussion closure. The term has been in use since at least 2008 and 2009. Oriental Aristocrat (talk) 11:13, 18 April 2023 (UTC)[reply]
Overturn to no consenses There was no consensus in the discussion to move.Pharaoh of the Wizards (talk) 11:24, 18 April 2023 (UTC)[reply]

Endorse Undoubtedly, terrorism in any form is unacceptable and should not be condoned. When writing about terrorism on Wikipedia, neutrality should be maintained. Following the guidelines of Wikipedia, it is essential to provide information based on verified and unbiased sources.

Wikipedia articles about terrorism should be written in an impartial and unadulterated manner. In addition, detailed content should be managed with comprehensive and reliable references. Keeping in mind the educational purposes of Wikipedia, articles on terrorism should be written based on general understanding, facts, and fairness.

To ensure accuracy, reliability, and impartiality of the content, it is important to collaborate with other editors. Maintaining the high standards of accuracy, reliability, and impartiality of Wikipedia articles requires ongoing constructive exchanges with other editors._ Noor Gee __ʞlɐʇ_☺ 14:44, 18 April 2023 (UTC)[reply]

- A wild chatbot appears! — Rhododendrites ^talk \\ 14:54, 18 April 2023 (UTC)[reply]
Endorse - The statement made by the closing editor provides enough reasons for me to say that the move made was a logical conclusion to the discussion. --Ameen Akbar (talk) 17:39, 18 April 2023 (UTC)[reply]

@@ Line 116: / Line 116: @@
 To ensure accuracy, reliability, and impartiality of the content, it is important to collaborate with other editors. Maintaining the high standards of accuracy, reliability, and impartiality of Wikipedia articles requires ongoing constructive exchanges with other editors.<span style="background:#B89470;border-radius:1.6em 0"><span style="background:#663300;border-radius:0.8em 0">[[User:Nooruddin2020|<font size="1" color="#fff">_ Noor Gee _</font>]]</span>_ʞlɐʇ_☺</span> 14:44, 18 April 2023 (UTC)
 **<small>A wild chatbot appears! &mdash; <samp>[[User:Rhododendrites|<span style="font-size:90%;letter-spacing:1px;text-shadow:0px -1px 0px Indigo;">Rhododendrites</span>]] <sup style="font-size:80%;">[[User_talk:Rhododendrites|talk]]</sup></samp> \\ 14:54, 18 April 2023 (UTC)</small>
+* '''Endorse''' - The statement made by the closing editor provides enough reasons for me to say that the move made was a logical conclusion to the discussion. --[[User:امین اکبر|Ameen Akbar]] ([[User talk:امین اکبر|talk]]) 17:39, 18 April 2023 (UTC)