User talk:Shibbolethink

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.

This is an old revision of this page, as edited by Shibbolethink (talk | contribs) at 18:41, 11 December 2022 (→‎A barnstar for you!: reply (CD)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

D/S
notice for any topic related to science, medicine, or anything that might remotely be considered a conspiracy theory, don't bother. I'm already aware. You may point to this notice if it ever comes up.

WPMED
Hot Articles:

118 edits PACE trial
112 edits Timeline of the COVID-19 pandemic in the Republic of Ireland (2020)
79 edits Hypnotic Ego-Strengthening Procedure
67 edits Timeline of the COVID-19 pandemic in the Republic of Ireland (2021)
62 edits Ageusia
54 edits Otis Clapp
54 edits Alcohol (drug)
47 edits Usha Desai
42 edits Ab Sadeghi-Nejad
39 edits Parkinson's disease

These are the articles that have been edited the most within the last seven days. Last updated 6 May 2024 by HotArticlesBot.


3 vs 2 is consensus?

Please explain to me how this RM discussion, where two were in favour and two against, with the latter putting significantly more effort and rationale in their argumentation, is considered consensus to move:

Talk:S.M.A.R.T.#Requested_move_28_October_2022. It seems to me that the discussion was merely a charade, in reality older and higher privileged editors simply made a decision and that was that. I think it at least should be relisted again. Regards. --Mango från yttre rymden (talk) 21:00, 12 November 2022 (UTC)[reply
]

Cc Shibbolethink. For future reference, the closer's talk page or Wikipedia:Move review is the standard way to challenge move requests. * Pppery * it has begun... 21:02, 12 November 2022 (UTC)[reply]
Hey @Mango från yttre rymden, how's it going. The proper procedure for this kind of thing is to first go to the closer's talk page (@Shibbolethink in this case) and try to resolve it there. And then if that doesn't work, to head over to Wikipedia:Move review and make a claim for why the close should be overturned. I'm going to move this over to my talk page and answer there. — Shibbolethink ( ) 21:13, 12 November 2022 (UTC)[reply]

Okay so here's my response. This is a consensus because, per

WP:NOTAVOTE. The clarity of argument, strength of policy, procedures, and the amount it is convincing to uninvolved editors is how consensus is decided on wikipedia. In the case of this move, I had relisted it once, to try and gain more input. And the only input that was received (from an uninvolved editor, mind you) was in favor of the move. Next, as @Pppery
pointed out in the discussion, it is true that WP:NATURALDIS supersedes WP:COMMONNAME in this case. And other editors agreed with them.

Avoiding ambiguity is one of the #1 things we do when we decide titles on wikipedia. We don't want visitors to end up on the wrong page, and we definitely don't want them to end up on the wrong page without an easy way to get to the right one. Hence, we have disambiguation pages for exactly this reason. This is a perfect example of how to use disambiguation pages. Multiple pages have S.M.A.R.T. as an acronym. And ACROTITLE tells us not to use the periods, but also WP:PRECISE tells us to use the most precise possible title to avoid ambiguity. Hence, the policies in this case favor the move.

These policy arguments were also the most influential on the uninvolved users who joined the discussion (e.g. @

WP:RM
explicitly discourages second relists when it is unlikely a more robust consensus will develop. We had extremely little input in this discussion, it seems even my pings to related pages did not draw a lot of interest. So a relist would not have made sense. It was also clear to me that we had a consensus, from uninvolved input and clarity of policy arguments.

However, you are absolutely free to disagree, and pursue this further at Wikipedia:Move review. Good luck and I hope you find what you're looking for here on wikipedia.— Shibbolethink ( ) 21:13, 12 November 2022 (UTC)[reply]

The Church of jesus Christ of Latter-day Saints

Hello. This is Jgstokes. I have been a Wikipedia editor for the last 15 years. Much of my work here has focused on articles about

good faith efforts to change the mid-sentence capitalization of "The" in the name of the Church. I am not familiar with the policies cited that led to the consensus to use the lower casse "t" in the name of the Church in mid-sentence. So I wanted to reach out to you on this, based on FormalDude's recommendation. The Church itself is an incorporated entity, and all sources covering developments relating to the Church use the upper case in reference to the full name of the Church. With that in mind, whenever you are able to do so, could you provide me with a more complete explanation on the decision that was made? I have no desire to be a nuisance, but I was unable to participate in the original discussion on this, so I would like some clarification on these points. Take whatever time you might need to reply. I look forward to dialoguing more with you in the future on this. Thanks for your time. Jgstokes (talk) 08:19, 17 November 2022 (UTC)[reply
]

I understand the concern, and also why the LDS official church-made style guide uses the capital T in its official name, to differentiate itself from other LDS churches in the early movement, to show its followers it is the "one true Church", etc. I honestly and truly do not care much either way, but I do think it's important that wikipedia be
WP:THE and the similar situations we have for The Coca-Cola Company (List of assets owned by the Coca-Cola Company) or The Crown (List of current viceregal representatives of the Crown).
I understand why the LDS leadership would want to have this capitalization, I understand why these are the rules for the church itself. But on Wikipedia, we have conventions and rules which seek to encyclopedically describe all of our content in the same neutral manner. And that requires us to sometimes use wikipedia-specific conventions to the great consternation of the things, organizations, and people that we cover here. — Shibbolethink ( ) 13:52, 17 November 2022 (UTC)[reply
]

Feedback request: Politics, government, and law request for comment

Your feedback is requested at

removing your name.

Message delivered to you with love by Yapperbot :) | Is this wrong? Contact my bot operator. | Sent at 19:31, 19 November 2022 (UTC)[reply

]

Hymns of the Church of Jesus Christ of Latter-day Saints (1985 book):

I see you considered the capitalization here. What made you decide to go back to the lower case the?Naraht (talk) 14:57, 21 November 2022 (UTC)[reply]

WP:BRD — Shibbolethink ( ) 05:28, 22 November 2022 (UTC)[reply
]

The Signpost: 28 November 2022

Articles you might like to edit, from SuggestBot

We are currently running a study to evaluate the effectiveness of alternative algorithms for providing personalized task recommendations through SuggestBot. Participation in the study is voluntary. Should you wish to not participate in the study, or have questions or concerns, you can find contact information in the consent information sheet.

Note: All columns in this table are sortable, allowing you to rearrange the table so the articles most interesting to you are shown at the top. All images have mouse-over popups with more information. For more information about the columns and categories, please consult the documentation and please get in touch on SuggestBot's talk page with any questions you might have.

Views/Day Quality Title Tagged with…
44 Quality: Low, Assessed class: Start, Predicted class: Start Alay (talk) Add sources
63 Quality: Medium, Assessed class: B, Predicted class: C Association for Research and Enlightenment (talk) Add sources
48 Quality: Low, Assessed class: Stub, Predicted class: Start Amano-Iwato (talk) Add sources
15 Quality: Low, Assessed class: NA, Predicted class: Start The Legend and the Hero 2 (talk) Add sources
22 Quality: Low, Assessed class: Stub, Predicted class: Start Pipa Jing (talk) Add sources
12 Quality: Medium, Assessed class: Start, Predicted class: C Yei Theodora Ozaki (talk) Add sources
50 Quality: Medium, Assessed class: NA, Predicted class: C Tenome (talk) Cleanup
35 Quality: High, Assessed class: NA, Predicted class: GA Electoral history of the Libertarian Party (United States) (talk) Cleanup
690 Quality: Medium, Assessed class: Stub, Predicted class: B Mythic humanoids (talk) Cleanup
36 Quality: Medium, Assessed class: C, Predicted class: C Siraya language (talk) Expand
75 Quality: Medium, Assessed class: C, Predicted class: C Debate on traditional and simplified Chinese characters (talk) Expand
34 Quality: Medium, Assessed class: C, Predicted class: C Unit of selection (talk) Expand
9 Quality: Medium, Assessed class: NA, Predicted class: C 1924 United States Senate election in Iowa (talk) Unencyclopaedic
104 Quality: Medium, Assessed class: C, Predicted class: C Banchō Sarayashiki (talk) Unencyclopaedic
712 Quality: Medium, Assessed class: Start, Predicted class: C Kumiho (talk) Unencyclopaedic
56 Quality: High, Assessed class: Start, Predicted class: GA Frozen zoo (talk) Merge
280 Quality: Medium, Assessed class: Start, Predicted class: C Fringe science (talk) Merge
1,257 Quality: Medium, Assessed class: C, Predicted class: B Shapeshifting (talk) Merge
69 Quality: Medium, Assessed class: Start, Predicted class: C History of education in China (talk) Wikify
678 Quality: Medium, Assessed class: Start, Predicted class: C Phonetic transcription (talk) Wikify
33 Quality: Medium, Assessed class: Start, Predicted class: C Mark Doty (talk) Wikify
3 Quality: Low, Assessed class: Stub, Predicted class: Stub Greenville Wildlife Park (talk) Orphan
13 Quality: Medium, Assessed class: Start, Predicted class: C Mongolian cosmogony (talk) Orphan
2 Quality: Low, Assessed class: Stub, Predicted class: Stub Bear Ridge (talk) Orphan
6 Quality: Low, Assessed class: Stub, Predicted class: Stub Keigo Seki (talk) Stub
4 Quality: Low, Assessed class: Stub, Predicted class: Stub 1818 United States House of Representatives election in Louisiana (talk) Stub
8 Quality: Low, Assessed class: Stub, Predicted class: Start 1929 United States House of Representatives elections (talk) Stub
4 Quality: Low, Assessed class: Start, Predicted class: Start 1812 United States House of Representatives elections in Louisiana (talk) Stub
58 Quality: Medium, Assessed class: Stub, Predicted class: C Gun (Chinese mythology) (talk) Stub
6 Quality: Low, Assessed class: Stub, Predicted class: Start 1818–1819 United States House of Representatives elections in Massachusetts (talk) Stub

SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. We appreciate that you have signed up to receive suggestions regularly; your contributions make Wikipedia better — thanks for helping!

If you have feedback on how to make SuggestBot better, please let us know on SuggestBot's talk page. -- SuggestBot (talk) 23:27, 28 November 2022 (UTC)[reply]

ArbCom 2022 Elections voter message

Hello! Voting in the

2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users
are allowed to vote. Users with alternate accounts may only vote once.

The

topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy
describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review

NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 01:23, 29 November 2022 (UTC)[reply
]

Feedback request: Religion and philosophy request for comment

Your feedback is requested at

removing your name.

Message delivered to you with love by Yapperbot :) | Is this wrong? Contact my bot operator. | Sent at 05:32, 29 November 2022 (UTC)[reply

]

Your page move closure

About your closure at Talk:1788–89 United States House of Representatives elections#Requested move 19 November 2022, hope you will consider reopening and relisting that one, because a) all those page moves may have been ill-advised, and b) I would like a say in the matter and I don't think there was consensus for the page moves. In the first place, you brought up CONSISTENCY, which was not mentioned by any of the participants in the RM discussion and does not apply. Even if we were to go by the MOS:DATERANGE community consensus (which also does not apply), the only exception to the preferred state of non-abbreviated years (1881–1882, not 1881–82) requires us to ask what the convention is in reliable sources. Since that convention might be one thing for, say, sports articles, it could be something different for, say, political articles, because the sources for each kind of article would give a different convention. That is why CONSISTENCY was not raised in the RM discussion.

Most importantly, an editor raised the main red flag: editor

ed. put'r there 19:05, 30 November 2022 (UTC)[reply
]

In the first place, you brought up CONSISTENCY, which was not mentioned by any of the participants in the RM discussion
CONSISTENCY says: We strive to make titles on Wikipedia as consistent as possible with other titles on similar subjects. Zzyx said: we should at least use the standard MOS:DATERANGE two-digit ending years format. Amakaru said: I definitely prefer a two-digit second year XXXX–XX where it's a pair of consecutive years. Zzyx also compared the use case to NBA seasons.
SUPERVOTE is when someone references an argument in the closing that was not made by any participants. That isn't the case here. Just because no one explicitly used the all caps shortlink doesn't mean that consistency wasn't a major argument in this discussion. It was.
Re: Carter's comments, no other discussion participants seemed to have found them particularly convincing. And as Zzyx says, these were elections that overall spanned two years, even if some seats were run in one year and the other in the next year. They were overall one "set" of elections. It was, as they say, " one series of elections that spanned two sequential years to elect a specific meeting of Congress" And that is what swayed subsequent commenters to support the move.
It appears to me, overall, that your request to relist is just dissatisfaction with how the consensus went down, not a procedural issue with the close. I don't think anything you bring up here was inadequately addressed in that original discussion, and I don't think a reopen is appropriate. An appropriate amount of time passed, eight editors participated in the discussion (more than most RMs), etc. Five explicitly in favor of the move and one supporting it while also supporting XXX-XXXX. Only a single editor was opposed, and their arguments didn't convince anyone else who participated. I don't think a relist is appropriate.
I would urge you to take this to move review if you think it's a reasonable case, but I disagree and will say something similar over there. — 
Shibbolethink ( ) 22:08, 30 November 2022 (UTC)[reply]
Oh no, put your mind at ease, Shibbolethink, as I highly respect your judgement. While I have taken a few RMs to MRV before, I doubt that I could build a case for this as an unreasonable closure. I would think that with editors like Amakuru in support, that most editors would agree that yours was a reasonable close. It's just that I think that more weight should have been given to Carter's argument, which effectively nullified both CONSISTENCY and DATERANGE. So had I closed this one, I would have called it "no consensus" for now, but that's just me. Just as one of the supporters indicated, it's just not that big a deal. Thank you for you consideration, and Happy Holidays!
ed. put'r there 15:35, 1 December 2022 (UTC)[reply
]
And you as well :) I will definitely take that under advisement in future closures, I think you're right and I definitely have been drifting towards more contentious closes, as a personal challenge. But I will definitely consider more relists moving forwards! — Shibbolethink ( ) 16:14, 1 December 2022 (UTC)[reply]

of sandbice and men

Of course, a man's sandbox is his castle, and far be it from me to pass judgment on someone else's castle -- I don't even know if it's a serious proposal or what -- but I think an RfC to deprecate ProPublica (based on stuff from 2016, no less) would be an absolute travesty, regardless of whether it went through or not. jp×g 04:23, 5 December 2022 (UTC)[reply]

Yeah, I mean probably not going to happen. I thought perhaps a "reliable except for reporting on scientific/data topics" would be the optimal middle ground that allows them to still be used for their extremely rigorous stories, but I have also seen quite a few examples of good science/health reporting, so I am not sure even that is a fair call.
My overall perspective is "they screwed up in these two instances" and we should just accept that as a reality, and that RSP is not really gospel. But that overall, ProPublica has an excellent reputation they completely fumbled in this instance, which will make me skeptically eye everything else, but not call it "unreliable". Not yet anyway. Ball's completely in their court if they end up screwing up worse after this. They already lost major grants... [1] (is that because SBF is bankrupt? Or because of their concerns over the reporting? Unclear. I would want them to be independent of funding, but I also personally would not fund an effort to investigate the origins where that was their first use of the money).
I absolutely adored ProPublica, have donated to them, read their newsletters, etc. Which was why this was such a shock. — Shibbolethink ( ) 06:02, 5 December 2022 (UTC)[reply]

Feedback request: Politics, government, and law request for comment

Your feedback is requested at

removing your name.

Message delivered to you with love by Yapperbot :) | Is this wrong? Contact my bot operator. | Sent at 08:31, 6 December 2022 (UTC)[reply

]

Reger story

I read your user page, about waste of words, and there's a matching story involving Max Reger, for a smile (but it's better in German): He wrote to a critic: "I'm sitting in the smallest room of my house and have your review before me. I'll soon have it behind me." - Seriously: during the infoboxes case of 2013, I invented the 2 comments per discussion restriction, which the arbs then used against me, and I found: it's no restriction, it's a blessing. For the infobox discussion for the composer, however, it took a few more comments than 2 (but by then I was free of restrictions). - 10 out of 12 arbitration candidates don't see infobox battles and one didn't answer - interesting. -- Gerda Arendt (talk) 11:06, 6 December 2022 (UTC)[reply]

Please fix the description of my questions to the arb candidates (not the current arbs, but those seeking election). I didn't ask them to weigh in (arbs can't weigh in), I asked them for ideas to end this perennial conflict. So far: no idea. They don't even see a conflict. - When the first RfC for Olivier was closed, I asked them to look at it. Just now, I asked them to look again. I wonder if they'll still see no conflict. I stand by my one and only comment: the common belief has been that the principal editors decide, repeated in 2015, and I rested the Reger discussion on that premise: I was the principal editor, and I decided. Has anything changed? Should that be the premise? No answer from the candidates to this comment (which they should have seen if the looked carefully). I also stand by the last part of my comment: always a waste of time. Unless someone has a good idea for peace. --Gerda Arendt (talk) 14:13, 6 December 2022 (UTC)[reply]

Ah yes will do! Thank you thank you.
I love that story, it reminds me of
Gell-Mann amnesia. The idea that we read reviews and treatises of stuff from our own area of expertise, and think "wow this is total BS" and then we flip to the politics section or economy pages, and think "now this is what I like". lol. — Shibbolethink ( ) 15:46, 6 December 2022 (UTC)[reply
]

IP User

I would just ignore that IP user. I'm not sure what drama is behind the retired editor, but for whatever reason they have been super hostile. It's not even worth responding. From the very beginning from when I was introduced to that RfC I have been met with nothing but hostility. It's rather silly, but you can tell from the responses it's someone who isn't prepared to argue in good faith. Nemov (talk) 16:14, 6 December 2022 (UTC)[reply]

Yeaaaaaaah. I did actually look into their background of their old account and they got blocked like 5 times (and another time as an IP) for edit warring and for being so confrontational.
But I always need advice on how to not sweat those things, lol. Thank you. — Shibbolethink ( ) 16:18, 6 December 2022 (UTC)[reply]
I was thinking about going to the noticeboard about it, but it's probably a waste of time if the user has already walked away. The editor isn't going to convince anyone with that type of behavior. Nemov (talk) 16:22, 6 December 2022 (UTC)[reply]
Yeaaaaah, I usually find it's better to reserve that for the most egregious cases. Those noticeboards can be so contentious, it only helps to go if it's a situation where it's really really necessary. Otherwise, better let people talk up a storm of sound and fury signifying nothing, as they say. Glad someone else sees it for what it is, though. — Shibbolethink ( ) 16:48, 6 December 2022 (UTC)[reply]
I try to keep an eye on the infobox wars and came here to see if you have had the DS alert. It appears that you have not. I saw the notice up the top which doesn't cover infoboxes but I'll avoid an alert for now. Please stop mucking about with the IP's comments. I don't want to know the history but it's obvious there is an underlying feud which means you are not an impartial observer trying to help out with the talk page. The topic is under discretionary sanctions which means poking anyone, even IPs or returned users, is not on. If it really bothers you, try ANI, although you must know that is not appropriate for such silliness. What does it matter if you don't have the last word? Johnuniq (talk) 01:50, 8 December 2022 (UTC)[reply]

I absolutely do not want the last word! I don’t want it to appear I’ve replied to something I have intentionally ‘’not’’ replied to. I’m happy with the current state of things and have no interest in interacting with the ip user. I’m also not going to check each and every page to see if that IP range or user have ‘’ever’’ edited it! But I’m going to avoid it as much as is reasonably possible. Promise! I respect your opinion as an admin Johnuniq and I think you are right, it’s not worth it. Thanks for the note — Shibbolethink ( ) 02:41, 8 December 2022 (UTC)[reply]

Notice of noticeboard discussion

Information icon There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. Thank you. Nemov (talk) 21:21, 10 December 2022 (UTC)[reply]

Morphogenic field in action?

Hi! I see strange things. When I look at the bottom of this page Talk:Rupert Sheldrake/Archive 22, I see the last bit of our 999 discussion, under the heading "Semi-protected edit request on 24 February 2022" and a little more text. However, if I look at the wikitext [2] and scroll to the bottom, our entire 999 thread is there, afaict looking like it should, per archiving [3]. Is this local to me, or do you see the same? If so, why? Gråbergs Gråa Sång (talk) 12:00, 11 December 2022 (UTC)[reply]

Fixed! Somehow one of the ref names got screwed up, and was collapsing 1.5 sections into a citation field! I just removed the ref. Glad you caught that though :) And hopefully we don't see any more spooky action at a distance. — Shibbolethink ( ) 13:24, 11 December 2022 (UTC)[reply]
Well dowsed and great service to future WP-archeologists. Gråbergs Gråa Sång (talk) 16:53, 11 December 2022 (UTC)[reply]

Hi Shibbolethink, do you think perhaps that, from the edits on the talk page, 2A00:23C7:2B86:9801:DD88:3C8D:2FF1:1800 and 2A00:23C7:2B86:9800:1D4C:5458:CBD8:E267 might be the same person? Just wondering if you had any thoughts? Mattdaviesfsic (talk) 15:13, 11 December 2022 (UTC)[reply]

Yeeeaaaah. So that /64 range is the subject of an ongoing
WP:FAOWN. It’s a real quagmire of frustrations to interact with them, honestly. After I and another user posted some basic notices on their talk page and they noticed I had also participated in a few infobox discussions, they started saying I was “stalking” and “harassing” them and they felt “chilled” and “threatened”. Not even kidding. Really, truly, they have chased away any user who tries to edit “their” articles even in extremely minor ways. — Shibbolethink ( ) 16:12, 11 December 2022 (UTC)[reply
]
Forgot to mention that the user SchroCat had been blocked like 5 or 6 times on both that user and other IPs for exactly this behavior. — Shibbolethink ( ) 16:12, 11 December 2022 (UTC)[reply]
Wow, I didn't see all of that extremely long conversation with that IP range arguing with @DesertPipeline: on the Mooregate tube crash article from August 2021. Now I see why you asked if it was the same person, lol. Just more of the same from the same obstinate person, jumping around that /64 range. — Shibbolethink ( ) 17:19, 11 December 2022 (UTC)[reply]

A barnstar for you!

The Barnstar of Diligence
Cannot thank you enough for the dedication with which you have looked through swathes of edits from innumerable IPs today. I know you're currently writing up a block proposal so I hope this will go some way to being some form of motivation (although I'm fully aware this could very much distract your train of thought!) Enormous thanks once again! Mattdaviesfsic (talk) 18:00, 11 December 2022 (UTC)[reply]
Thanks!! :) I'm just happy there appears to be a gathering consensus that this side show is a distraction from the project and should be put in a drawer somewhere. Now I need to go back to my IRL work, lol. And thank you for your help on all this! — Shibbolethink ( ) 18:41, 11 December 2022 (UTC)[reply]