Jump to content

User talk:Mdaniels5757/Archive 3

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
< User talk:Mdaniels5757

This is an old revision of this page, as edited by ClueBot III (talk | contribs) at 02:47, 17 August 2020 (Archiving 2 discussions from User talk:Mdaniels5757. (BOT)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Archive 1Archive 2Archive 3Archive 4Archive 5→Archive 10

8'46"

Hi there. Can you elaborate more on your close rationale for Talk:Eight_minutes_46_seconds#Requested_move_10_June_2020? Paintspot initially raised concerns at a subsequent RM for that page (since withdrawn), but I also have similar questions. To me, it seemed that there was no guideline-based support at the subthread Talk:Eight_minutes_46_seconds#Sanity_break to spell out "Eight"; one person initally said it was based on the AP-based MOS, but they withdrew their support. Others !votes for "eight" were not based on a guideline, while I explained that our MOS had no preference for this case, which one other agreed and nobody rebutted. Thanks in advance. Regards.—Bagumba (talk) 08:12, 18 June 2020 (UTC)

  • Hi Bagumba. Thanks for reaching out. In summary, I found (and retrospectively numbered) (1.) a strong consensus to move away from 8'46" to (in regex form) /(8|Eight) minutes( and)? 46 seconds/, and (2.) a somewhat weak consensus that the value represented by the word "eight" should be spelled out in the title. Since I don't think the former is in dispute (although I'd be happy to provide a more detailed explanation of that if you wish), a more detailed explanation of only the latter follows.
Background: the guidelines are a mess on this. Going off of any version of MOS:NUM between May 29 and June 15, it's not clear that the relevant portion of MOSNUM applies to titles at all. (The "generally, in article text" part of MOS:SPELL09 applies only to, well, article text. However, the "notes and exceptions" section that could otherwise apply doesn't say so. But it makes no sense to have the scope of the exceptions exceed the scope of the rule! Further complicating matters, one of the exceptions is that "proper names, technical terms, and the like are never altered", and the examples are links to and/or titles of Wikipedia articles, so maybe it does apply?) However, even assuming the MOS applies, the MOS doesn't tell us much of use when the integer we need to decide how to represent is expressible by the word "eight", only that "figures or words may be used with unit names ([n] minutes or [number] minutes), within the guidelines above" (but "the guidelines above" say "Integers from zero to nine are spelled out in words"). Given all of this, I weighted appeals to MOS for this portion of the discussion less than I normally would. For obvious reasons, for question 2, I weighted discussion that took place after "Eight minutes forty-six seconds" was proposed more than discussion that took place before the proposal (although I did take the reasoning of each participant into account in evaluating the question, even if they did not participate in the later discussion).
Turning to the the discussion of question 2 itself: I found that the consensus was clearly for one of what User:EEng numbered B2 and B3 (with, perhaps, an "and" thrown in, but there was minimal discussion on that). Both were well-argued, to the point that my weightings based on the strength of both arguments were equal. However, B2 received the support of 4 in the subthread, and B3 received the support of only two (counting yours as B3). That would be a fairly strong consensus, but given the goings-on outside of the subthread, I think it was weaker (but still there). An aside: WP:NCDURATION wasn't mentioned as far as I noticed, probably because its examples don't really seem to consider shorter periods of time. We should probably work on that if there is a consensus either way.
All of that being said, I think that there is actually a chance that a RM squarely focused on the following two questions would reach a different result, at least on one of them: (a) Should the integer represented by the word "eight" be expressed as "8" or "eight"? and (b) Should the word "and" go between "minutes" and "46"? I wouldn't be too opposed to one being started on that; although I think the differences are minor enough that it might not be worth the effort, others may not agree.
I hope the above is helpful. Please let me know if you have any further questions, or if you have any interest in working on making this labyrinth of MOS/Naming Conventions a bit less labyrinthian. Best, --Mdaniels5757 (talk) 15:02, 18 June 2020 (UTC)
Thanks for closing this. FWIW, my !vote was for "8 minutes and 46 seconds", which wasn't any of the "A" or "B" options. I read the "sanity break" thread and nothing therein persuaded me to change my !vote (which was based on common name, with examples provided). I count more than half a dozen editors voting the same way I did. I didn't realize that my vote would be weighed less because it came before the sanity break section. Frankly I didn't think I had to comment again because "8 minutes and 46 seconds" had such a large lead in terms of votes over any other option presented. Don't get me wrong, I think your rationale above is well reasoned and extremely thorough. You've clearly put a lot of thought into the close, for which I'm grateful. And I'm a big believer in "not a vote". Levivich [dubious – discuss] 15:11, 18 June 2020 (UTC)
Fair enough, and I'm sorry for that. I think I did fully consider your non-vote, and I should probably further elaborate on how exactly I did that weighting. There were effectively three questions to answer in the RM yes, I did list only two above.... Abandoning my labelling from above, they were: (a) Should the title have "minutes" and "seconds"? (per MOS:UNITNAMES) (b) Should the first integer be spelled out? and (c) Should the word "and" be between "minutes" and "46"?. The non-votes in before the section break fully considered issue (a), and I fully took those comments into account on that issue. However, the non-votes before the section break (with a couple of exceptions) did not discuss issues (b) and (c), and therefore, I did not take those particular non-votes into account on determining those issues. I did, however, fully take into account your WP:COMMONNAME argument, which, although having merit, was not discussed by others (although it was seconded). Your argument is why I described the consensus on issues (b) and (c) as weak, and why it could change.
Turning to the my closure's result itself: Although I think there was a consensus on (b) and (c) in the direction that I closed it, I think a "no consensus" close would have also been reasonable for those issues (I still don't think there was a positive consensus for your version, given the section break discussion). However, that would raise the question: "What should the article be renamed to, given the consensus on (a) being that there are serious other issues with the title?". Although I'm not convinced I should undo my closure (because there would be a second RM either way), in retrospect, I probably should not have closed the discussion at all. Instead I should have acted as a facilitator, asking others who had not yet discussed (b) and (c) to do so, and trying to further develop discussion on the WP:COMMONNAME argument. That would have probably led to a more robust consensus, one way or another. Thoughts, @Levivich? (also, please let me know if you want me to stop pinging you...) --Mdaniels5757 (talk) 15:56, 18 June 2020 (UTC)
I think your analysis is solid. I agree it comes down to (b) and (c), or "eight/8" and "and". From a COMMONNAME perspective, the "and" bit could go either way: some sources include "and", others omit it. I view that as a "tie", which can be broken by MOS in preference for omitting the "and", basically per EEng's arguments. The "Eight/8" part is the tougher one for me. It seems to me that "8" is far preferred by sources, especially in titles of works (i.e. headlines). MOS clearly says "eight". Part of me thinks, "Well AT is a policy and MOS is a guideline", but I generally dislike "its only a guideline" arguments. There's something to be said for "we should write it the right way even if no one else does". But that seems to go against COMMONNAME. Do you see it that way on the "eight/8" issue? As COMMONNAME-vs-MOS? In the end, if this were to be pursued further, it seems like a relist (with a helpful relisting statement to guide further discussion, as you suggest) is more efficient than a second RM or an MR. On the other hand, I think this is a purely stylistic and not-at-all-substantive titling dispute (unlike, say, "death of..." v. "murder of..."), so I'm personally rather ambivalent about whether further discussion would be productive, or whether we should just "make a call" (as you have done) and move on. (And no I appreciate the pings, thank you, and WarGames is a classic!) Levivich [dubious – discuss] 16:17, 18 June 2020 (UTC)
@Levivich: Agreed on both counts. If people want that relist, I'll do it, but I agree that it might not be worth it. --Mdaniels5757 (talk) 19:22, 18 June 2020 (UTC)
A relist could be an option, but with an WP:IAR of not reverting back to 8'46", for which it's unanimous that it's wrong.—Bagumba (talk) 05:06, 19 June 2020 (UTC)
IMO the article ought to be merged anyhow, and may very well be. BTW turns out it's not 8 minutes and 46 seconds, it's 7 minutes and 46 seconds, and I think that will dampen the lasting significance of this slogan. Or maybe everyone will just update their signs. We'll see. [1] Levivich [dubious – discuss] 05:20, 19 June 2020 (UTC)
It's independent of the close, at any rate.—Bagumba (talk) 05:26, 19 June 2020 (UTC)
@Levivich: Throwing a wrench into the AT vs MOS debate, it's never been clear if AT applies to styling of titles. These options are all the same time duration, and moreorless read the same as a title. They are just styled differently. For the names of works e.g. books, films, songs, etc." we typically defer to the styling of the original. But this about Floyd is more of a descriptive idea as opposed to a title of a work. Anyways, this was all not part of the RM discussion.—Bagumba (talk) 05:01, 19 June 2020 (UTC)
Thank you Bagumba! The reason I opened up that "part 2" Requested move is because a majority of people seemed to prefer the consistent numerals ("8 minutes 46 seconds") over the combined half-and-half version (among the other reasons listed at the withdrawn move request). Paintspot Infez (talk) 17:58, 18 June 2020 (UTC)
@Mdaniels5757: I appreciate the response. Yes, my main concern is your point 2 re: "eight" vs. "8". A few responses to some of your comments: ... it's not clear that the relevant portion of MOSNUM applies to titles at all: Perhaps, but I don't think that was a point brought up by the participants. Given all of this, I weighted appeals to MOS for this portion of the discussion less than I normally would.: But I don't believe any participants said "don't follow the MOS because it doesn't make sense." Thus, I don't think it should be a factor in the close. I weighted discussion that took place after "Eight minutes forty-six seconds" was proposed more than discussion that took place before the proposal: I don't see why they would be given additional weight. There wasn't any inherent bad assumption made earlier nor any quideline oversights. This also presupposes that there is WP:SILENT support of later comments, but participants typically dont check back unless they are pinged. However, B2 received the support of 4 in the subthread ...: I see only 2: intially it was EEng, VikingB, and Psiĥedelisto—I consider EEng to have withdrawn that support. Those 2 didn't elaborate on why they liked one over the other. Blaylockjam10 and I provided a rationale for our choice of "8", and mentioned that its allowable per the MOS. Of course, discussions aren't a pure !vote count either. I think that there is actually a chance that a RM squarely focused on the following two questions would reach a different result ... I don't see the arguments supporting "eight" being stronger, and are in the minority of the entire discussion. I think we do go with the majority in that case, but it is fair for mention in the close about no prejudice on a further narrow discussion on "eight" vs "8". Regardless of how you view the weighting now, you do need to expand the close's rationale and mention any acceptable RM options that could be opened and not be considered disruptive. Regards.—Bagumba (talk) 04:50, 19 June 2020 (UTC)
@Bagumba: Thanks for your response. I've added to my closure rationale and expressed approval/non-opposition for a more focused RM here. Best, --Mdaniels5757 (talk) 15:55, 20 June 2020 (UTC)
  • I understand I'm pinged in here somewhere but when I went looking I got disoriented and became dizzy. All I can say is if you guys try to add in the comma or the and I'll sic the MOS mob on you. EEng 21:12, 18 June 2020 (UTC)
    Oh, well, dear, worry not, my friend, for I can say, without a doubt, "Bagumba and Mdaniels and Paintspot and I would never do such a thing." Levivich [dubious – discuss] 21:35, 18 June 2020 (UTC)

Well-advised move?

May I assume here that you were not aware that Charles XV is called Charles IV in Norway, and that that one probably should not have been on that list? His grandfather Charles XIV John of Sweden has a similar feature & was not moved. Could you reverse Charles XV and give us a chance to discuss that aspect? --SergeWoodzing (talk) 13:58, 20 June 2020 (UTC)

help

I know my page that I created was declined to publish, what can I do or fix that can be done to correct it, so that it could be published. Thanks — Preceding unsigned comment added by Raymond Ramos r2fx (talk • contribs) 16:41, 21 June 2020 (UTC)

@Raymond Ramos r2fx: Hi. I have a couple of suggestions, but first, are you Raymond Ramos (the person whose article you created)? (Also, please remember to sign your talk messages with four tildes (~)). Best, --Mdaniels5757 (talk) 14:52, 22 June 2020 (UTC)

Talk:Conventional PCI

Hi Mdaniels5757,
The Talk doesn't redirects to Talk:Peripheral Component Interconnect, I think needs to be move or merge by an admin. — YoungForever(talk) 00:45, 25 June 2020 (UTC)

Wikidata weekly summary #423

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Ptable displays the periodic table automatically extracted from information provided by Wikidata; it also provides a check that all the elements are there with some basic properties. Additional pages provide charts of the nuclides under different criteria such as half-life. Each element or nuclide is linked to its Wikidata item for more information or to edit if necessary.
  • Development
    • More work on the consistent design system (Phabricator board)
    • More work on decoupling the different Wikibase extensions from each other
    • Polishing the first step of Federation (using Wikidata's Properties in another Wikibase installation) (incl. preventing users from selecting a federated property with a non-supported data type (phab:T252012) and preventing users from accessing Special:NewProperty when federation is enabled (phab:T255576) and viewing a list of all properties when federation is enabled (phab:T246339))
    • Continuing research and interviews around the topic of making it easier to access Wikidata's data for programmers
    • Doing first testing of mockups and prototypes of the first version of the Query Builder - coding can start soon
    • Convert a few properties from string to external identifier: Linguasphere code (P1396), KOATUU identifier (P1077) and ISIN (P946)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

You've got mail!

Hello, Mdaniels5757. Please check your email; you've got mail! The subject is Paul again....
Message added 15:03, 13 July 2020 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

——Serial # 15:03, 13 July 2020 (UTC)

Wikidata weekly summary #424

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: New co-facilitator introductions and tools for editathons, 14 July. Agenda
    • Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #12, 18 July Facebook, YouTube
    • Past: Celtic Knot Wikimedia language conference, online, July 9-10. Videos, documentation and slides of sessions are accessible from the program page.
  • Tool of the week
    • DragNDrop.js makes it possible to show a Wikipedia article and drag items to Wikidata.
  • Development
    • Continued building out documentation for Federated Properties (phabricator:T255651) and making interface improvements to the first stage of the feature (incl. phabricator:T246886, changes to special pages that interact with both Items/Properties, and phabricator:T255581, changes to Special:ListDataTypes when federation is enabled)
    • More work on the consistent design system
    • More work on decoupling the different Wikibase extensions from each other to make development easier
    • Finalizing research and interviews to better understand what could be improved in the way developers access Wikidata's data (APIs, SPARQL)
    • Testing the first prototype of the Simple Query Builder with some editors to get final input before coding starts
    • Sorting of language links on Wikipedia and the other Wikimedia projects was broken (presumably by a change in MediaWiki core). A fix is being worked on. (phabricator:T257625)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

False lead in sock-puppeting investigations

Hi; I have a block through my phone's IP for sockpuppeting from user Berean Hunter (https://en.wikipedia.org/wiki/User:Berean_Hunter). I took a look at their talk page and saw a lot of discussion of an investigation into it mostly in a conversation with you so I figured I'd reach out to you too. I just wanted to point out that that block was misguided. I don't even think I've made more than one edit on my phone ever, so after looking up what sock-puppeting is, I figure my phone was probably one of the IPs being abused by the puppeteer. It's not a huge deal, as I said I rarely edit from my phone anyway and obviously can still edit from my computer. It looked like the investigation had some false leads so I am hoping it's helpful in tracking the issue down to let you know my IP isn't the source of the problem. I'll be emailing Berean Hunter to let them know too. — Preceding unsigned comment added by 71.95.53.175 (talk) 19:57, 25 June 2020 (UTC)

Closed discussion

I noticed that you recently closed the discussion at Talk:2014 ICC Awards, but the 2015 LG ICC Awards redirect still exists. Given the 2015 ceremony wasn't sponsored by LG Electronics, would you also be willing to help me delete it? — 29cwcst (talk) 23:10, 25 June 2020 (UTC)

Scripts++ Newsletter – Issue 16

News and updates associated with user scripts from the past two months (May and June 2020).

Hello everyone and welcome to the 16th issue of the Wikipedia Scripts++ Newsletter:

If anyone else would like to contribute to future issues, please comment at Wikipedia talk:Scripts++. --DannyS712 (talk) 20:13, 30 June 2020 (UTC)

Talk:List of fictional trans characters

Hi there, I didn't see that there was a discussion over changing the article title to contain the word "trans", and I was surprised that this was the case. Given that there were two comments in support and two in opposition, I'm reopening the discussion and will be reverting the title to the original, through the appropriate channels. Onetwothreeip (talk) 22:21, 2 July 2020 (UTC)

@Onetwothreeip: Your math is off. Three (including the nominator, but not including the nominator's second !vote) people were in favor of "trans" and 2 were opposed. Of course, consensus is not a matter of counting votes, and even if the !votes were 2-2, I would have found that the contention that "List of fictional trans characters" is ambiguous lacks merit, that WP:PRECISION (policy) says that "Usually, titles should unambiguously define the topical scope of the article, but should be no more precise than that", and weighed !votes accordingly. If you believe that I assessed the consensus there incorrectly, or that there was significant additional information not discussed, you are welcome to explain in more detail here, and, if needed, list my closure for move review. However, simply reopening the discussion would be out of process, and adding a non-vote to a closed discussion fruitless. Best, --Mdaniels5757 (talk) 01:05, 3 July 2020 (UTC)
To be clear I am not including the nominator and I am not including myself either. There was clearly no consensus at the time, and more views should have been countenanced. I would agree that "transgender" is more precise than "trans", particularly in this context. Onetwothreeip (talk) 09:12, 3 July 2020 (UTC)
@Onetwothreeip: Thanks for your response. First of all, closers should include the nominator in assessing consensus, and I believe I properly did so. I think that there was a consensus at the time, both numerical (unweighted based on strength of arguments) and weighted. Per WP:MRV, if you wish to challenge my closure, please state here, with details, how I "did not follow the spirit and intent of WP:RMCI" or "was unaware of significant additional information not discussed in the page move discussion". Best, -Mdaniels5757 (talk) 15:40, 3 July 2020 (UTC)
I have no issue with including the view of the nominator, and I do not think you have failed to follow the spirit or intent of policy. What I am saying is that there was clearly no strong consensus either in support or against, and in regular circumstances more participants should have been included. I'm simply notifying you of this as a courtesy to you. Thanks. Onetwothreeip (talk) 22:05, 3 July 2020 (UTC)

Thanks

Thanks for closing and moving the RM for Climate Pledge Arena. Someone moved it earlier today before the discussion closed, and I had to move it back. I couldn't close it myself as was involved in the discussion. I was pretty sure it would close as a move (that's what I would have done anyway), but in such cases procedure needs to be followed. Thanks again. - BilCat (talk) 00:37, 4 July 2020 (UTC)

@BilCat: You're welcome! --Mdaniels5757 (talk) 00:38, 4 July 2020 (UTC)

RM template

Hi. Re this, sure, a single request works fine, but multiple requests generate a 'wrong page' error. — kwami (talk) 01:04, 4 July 2020 (UTC)

@Kwamikagami: Yes. When using {{subst:RMassist}} (for technical requests only), you must use one template per request. Thus, Special:Diff/965888008 was four {{subst:RMassist}} uses. Note, however, that {{subst:Requested move}} (for starting new discussions only), allows multiple pages to be nominated for discussion in one template call. Best, --Mdaniels5757 (talk) 01:09, 4 July 2020 (UTC)

My bad. Thanks. I'll just enter multiple copies of the template next time. — kwami (talk) 01:12, 4 July 2020 (UTC)

Wikidata weekly summary #425

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming: The First Wikidata Workshop: Second Call for Papers. Papers due: August 10, 2020 | Workshop date: October 29, 2020
    • Upcoming: next Wikidata office hour, July 21st at 16:00 UTC (18:00 CEST) in the Wikidata Telegram group. Query Service special with guests from WMF Search Team.
    • Upcoming: Wikidata Lab XXIV: Posicionamento digital relativo with Ederporto - July 23 17:00 UTC (14:00 BRT). In this technical training, we'll study the possibilities and functionalities of relative digital positioning in images and do practical activities on this topic using historical photographs of the city of São Paulo. The event will be held in Portuguese. Join us!
    • Upcoming video: July 21 - Wikipedia Weekly Network - Entity Schemas and Shape Expressions (ShEx) Facebook YouTube
    • Upcoming video: July 25 - Wikipedia Weekly Network - LIVE Wikidata editing #13 Facebook YouTube
    • Upcoming: Kidok-Workshop, online workshop about church building data. In German, non-native users welcome. Currently looking for a date in the upcoming week and people to help!
    • Upcoming video: Beyond Wikipedia - Knowledge that even a computer can understand. July 22, 2020 at 17:00 UTC. In this talk, Zbyszko Papierski will present Wikidata Query Service as one way that developers can interact with Wikidata.
  • Development
    • More work on the consistent design system
    • More work on decoupling the different Wikibase extensions from each other to make development easier:
    • Prepare the first development phase for the Simple Query Builder
    • Reference game: run a scraper, work on a dashboard that will gives an overview of the potential references that have already been judged in the game
    • Fix a bug related to maximum limit of search results (phab:T256885)
    • Resolve some configuration issues regarding Entity Sources (phab:T254315)
    • Federated Properties:
      • Changes to special pages that interact with both items/properties when federation is enabled (phab:T246886)
      • Changes to Special:ListDatatypes when federation is enabled (phab:T255581)
    • Add new monolingual language codes: mic (Miꞌkmaq), gil (Kiribati)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

A Barnstar for you!

The Diligent Librarian Barnstar
For exemplary service at the Resource Exchange, tirelessly delivering the reliable sources on which this encyclopedia depends, please accept this award. :) Specifically, thanks for fulfilling RX requests that otherwise would have been closed as stale. Keep up the good work! MrLinkinPark333 (talk) 16:39, 8 July 2020 (UTC)

Ditto!

The Guidance Barnstar
Thanks for your sterling work! That was great stuff, much appreciated, and so prompt too. Many thanks indeed! Although I'll be cursing you tomorrow when, yet again, I don't get any work done  ;) All the best! ——Serial # 17:38, 9 July 2020 (UTC)

A barnstar for you!

The Barnstar of Diligence
For fulfilling WP:RX's trickiest requests—thank you! czar 19:36, 11 July 2020 (UTC)

Move of page pantsdrunk

You recently closed my move request of pantsdrunk to kalsarikännit as "do not move". If you read User:Urjanhai's comments, he suggests that kalsarikänni without the "t" is a better move target, as that's what the original Finnish article fi:kalsarikänni uses. So I wish to propose a new move to kalsarikänni. JIP | Talk 12:53, 12 July 2020 (UTC)

@JIP: Feel free to propose such a move if you wish in the future, but I don't think that it's likely to gain consensus based on the recent discussion, which I read as your nomination, 1 !vote being neutral on which language to use but saying that a different Finnish word should be used instead, and 2 !votes opposing a move to a non-English word per WP:USEENGLISH. I suggest waiting a few weeks first, and then arguing that there is WP:DIVIDEDUSE in English-language sources (assuming that this is true) in your nomination. Best, --Mdaniels5757 (talk) 14:21, 12 July 2020 (UTC)
I can confirm also here, as I said in comment to the request, that I don't have and will not have any opinion concerning the question whether or not the name of the article should be translated or not in en-wikipedia. I only told my opinion about the question, what form of the word should be used if the untranslated name would be chosen to be used in the name of the article. As a non native speaker of english I really do not have any competence to assess this question in this particular case.--Urjanhai (talk) 17:47, 12 July 2020 (UTC)

Asshole

You really make me mad. Just let me edit Barney you old hag. You could probably be my dad tbh. Ireallyreallyreallyloveharryedwardstyles (talk) 02:27, 14 July 2020 (UTC)

A message from Sonther4ever

Help us to fix information. We are in contact with friends from Alberto Carpani and we are already tired to read that wikipedia is spreading wrong information about his death. Unfortunately any tabloid which is not a reliable source, published lies, but not even the source taken for that tells that Alberto had COVID-19, his test was negative, he died due different health problems. Now his fans are confused because the info from wikipedia is very wrong. What can we do in order to solve this problem? Please we will appreciate your help, more than rules, this is a human issue.--Sonther4ever (talk) 02:34, 14 July 2020 (UTC)

  • Hi User:Sonther4ever. In order to prevent misinformation, Wikipedia requires that all information be properly sourced. I've changed the wording to "lung infection" in order to accurately reflect the cited source. Additional information should not be added unless cited to a reliable source. Best, --02:42, 14 July 2020 (UTC)

Wikidata weekly summary #426

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • We would love suggestions for tools to include in this section of the weekly summary. Please add your suggestions directly under Status updates/Next#Backlog after checking that the tool isn't already listed.
  • Development
    • Changed the size of image previews to 1024 in the gallery view of the query service to avoid some images not loading sometimes (phabricator:T258241)
    • Added an actual space between the entity title and the name of the fallback language (if any), so that the fallback language isn't selected anymore when double-clicking the entity title for copying (phabricator:T256857)
    • Fixed the directionality of text pieces in placeholders that mix LTR and RTL (phabricator:T253812)
    • Continued work on first pieces of design system to make coding new features easier in the future
    • Continued untangling the code of Wikibase Client and Wikibase Repo to make it easier to develop on them
    • Finished first piece of research on how to make it easier to access Wikidata's data for programmers - more work to be done
    • Preparing to start coding on the Query Builder to make it easier to create queries without having to know SPARQL
    • Finished running the scraper that gets potential new references for unreferenced statements and preparing it for publishing

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Administrators' newsletter – August 2020

News and updates for administrators from the past month (July 2020).

Administrator changes

added Red Phoenix
readded Euryalus • SQL
removed Jujutacular • Monty845 • Rettetast • Madchester

Oversight changes

readded GB fan
removed Keegan • Opabinia regalis • Premeditated Chaos

Guideline and policy news

Sent by MediaWiki message delivery (talk) 08:21, 1 August 2020 (UTC)

A message from Dirt07

mate why dont u just leave me alone u absolute yeet bag go play fortnite or something Dirt07 (talk) 06:23, 3 August 2020 (UTC)

Some stroopwafels for you!

dees are for u u retard Dirt07 (talk) 06:25, 3 August 2020 (UTC)

Sock tags

Please don't modify sock tags placed by Checkusers or SPI Clerks; if you think an error has been made, it's best to ask the editor who placed the tag as opposed to editing it directly. In this case, I specifically omitted the "blocked" parameter as it adds the statement that the account was blocked as a result of checkuser confirmed socking, which is not the case. The account was blocked as WP:NOTHERE and was later confirmed to be socking.-- Jezebel's Ponyobons mots 17:14, 20 July 2020 (UTC)

@Ponyo: Understood, sorry about that. --Mdaniels5757 (talk) 17:18, 20 July 2020 (UTC)
No worries, it was clearly done in good faith.-- Jezebel's Ponyobons mots 17:47, 20 July 2020 (UTC)

A message from Danoxmas

Hi mdaniels!

Thanks for adding the show's poster for me, I wanted to change it to the vertical poster but eventho I've made over 10 edits and have had an account for longer than 4 days I can't seem to be able to upload images. When I go to the upload page it says "You do not have permission to upload this file, for the following reason: The action you have requested is limited to users in one of the groups: Autoconfirmed users, Administrators, Confirmed users.". What else do I have to do? Anyway, here's the file.

https://images.squarespace-cdn.com/content/v1/5dc207498d34bc5e5954261d/1578084877647-33TY2C6IH4FRGYQ9MCF4/ke17ZwdGBToddI8pDm48kHnK_yRjKo-bFO7w2t_TctF7gQa3H78H3Y0txjaiv_0fDoOvxcdMmMKkDsyUqMSsMWxHk725yiiHCCLfrh8O1z5QHyNOqBUUEtDDsRWrJLTmFrKkuyfqIWRdt3lCufLMAYxkVXQVnyOOcDD0H6-K9i1XVgpZWnxX8LTaGv2X84Wz/mr+inbetweennn_.jpg Danoxmas (talk) 18:53, 19 July 2020 (UTC)

Hi Danoxmas. Your account needs to be exactly four days old to have the permission to upload files. Looking at the logs, you will have that permission in about three hours (July 19, 23:40 UTC). Since it will be so soon, if it's alright with you, I'll let you upload the file yourself then. Best, --Mdaniels5757 (talk) 20:37, 19 July 2020 (UTC)
Oh wow I was close then haha. Well I just uploaded the poster I want for the page but I can't seem to figure out how to swap out the horizontal one currently being used with the vertical poster I just uploaded? — Preceding unsigned comment added by Danoxmas (talk • contribs) 18:44, 20 July 2020 (UTC)
@Danoxmas: The way you swap it out is by changing a field of the infobox, which I've gone ahead and done here. Note that you also always have to add a rationale on how the file complies with our non-free content policy, which I've done here.) Also, remember to sign your messages to others with four tildes (~). Best, --Mdaniels5757 (talk) 21:03, 20 July 2020 (UTC)

Ah thanks for the help and being patient with me. One final question/request, I want the specific awards "AACTA" and "Logies to have Sub-heading 1 format size but can i have them removed the table contents? I'm fine with Awards having a section in the table of contents but i don't need the specific awards to show in the table of contents, i dont know how to edit the table of contents.

-Danoxmas — Preceding unsigned comment added by Danoxmas (talk • contribs) 02:20, 21 July 2020 (UTC)

@Danoxmas: There actually shouldn't be links in section headings, I've cleaned it up. --Mdaniels5757 (talk) 15:44, 21 July 2020 (UTC)

THANK YOU Danoxmas (talk) 18:19, 21 July 2020 (UTC) Dan

The Signpost: 2 August 2020

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 18:25, 2 August 2020 (UTC)

Wikidata weekly summary #428

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Wikibase Live Session - August 2020. This session had a few people present on some of their work with modeling GLAM data in Wikibase or Wikidata. (replay)
    • Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Daniel Mietchen and Lane Rasberry about Scholia, a project to present bibliographic information and scholarly profiles of authors and institutions, 11 August. [Agenda]
    • Upcoming: Online Wikidata editathon in Swedish #25, August 16
  • Development
    • finalized designs for the query builder to start coding at the beginning of September
    • wrapping up the initial work on the design system so that we can start using the first pieces of it in the query builder development
    • working on properly linking redirects in recent changes, watchlist and co (phabricator:T255387)
    • addressed remaining security review comments about the Wikidata Bridge so that we can deploy it finally on the first Wikipedia
    • fixed a bug where string values had the wrong length limit (phabricator:T259440)
    • finishing the work of untangling Wikibase Client and Wikibase Repository extensions to make development easier

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

WP:OP

Hello Mdaniels5757. Thanks for your interest in and helping out with WPOP (and remind me to add MrClog if they return). Please be sure you've read this page. It's traditional to issue a little test to potential verified users. I first note that there are two unofficial mottos when it comes to WPOP. The first is, be chill. The second is, don't sound confident when you're not. Without further ado, please tell me something about these IPs, in the context of OPs:

(and I may be tempted to find a few more). Responses may include, but are not limited to, Would you block, not block, or unblock? How long for? etc. Thanks. -- zzuuzz (talk) 19:31, 29 July 2020 (UTC)

  • @Zzuuzz: OK, here goes. Note that I assume that (except for entries I can see in the history log) each IP has no deleted contributions.
    • 36.74.53.222 (talk · contribs · WHOIS): IPcheck shows two vendors listed the IP as a proxy. A "nice"/non-invasive nmap scan shows filtered ports, but no open ports. Ports 80 and 443 were among those filtered ports, but I could not connect either directly or attempting to use the IP as a proxy. WHOIS and BGP data don't say anything useful that I can tell. I'd say the result was  Inconclusive, and would not block as a proxy (although, of course, the short vandalism block was a good call).
    • 122.155.168.74 (talk · contribs · WHOIS): I have two dueling theories of what's going on here. Based on WHOIS and BGP data, I first suspected that it's a webhost of some sort ("CLOUD" is in the network's name, and the ISP markets some cloud/hosting products). IPcheck shows that two vendors listed the IP as a proxy, which gave my suspicion some more weight. It also showed one vendor listing this a compromised server, however. A ("nice"/non-invasive) nmap scan shows some open ports that have been used in viruses/trojans, which gives the compromised server theory some more weight. Lacking enough evidence to make a decision either way on whether this is a {{colocationwebhost}} or a {{zombie proxy}}, I would conclude that this IP is  Likely something bad, err on the side of caution, and recommend a {{zombie proxy}} block for 1-6 months.
    • 69.10.203.202 (talk · contribs · WHOIS): The IP was recently blocked (globally and locally) as an open proxy. The ports ST47ProxyBot provided are now closed, so the original reason for the just-expired block is now invalid.
      I ran a check anyways. IPcheck shows IPQualityScore listing the IP as a proxy (IPQualityScore has the most false positives, in my experience). Additionally, the IP is listed on SPAMHAUS' CBL as being a part of a botnet as of July 17. Based on a desire to confirm SPAMHAUS' listing, I ran a nice/non-invasive nmap scan. I found that ports were open that variously suggested either a compromised machine or a webhost (mostly FTP, SSH, telnet, HTTP, and HTTPS, but also 5101 and 5431). I was unable to connect to the open HTTP(s) ports, either normally or as a proxy. For legal/ethical reasons, I did not attempt to connect to telnet, FTP or SSH. The IP has not edited since the last block. Given the array of open ports, I'd declare it  Possible that the IP some form of proxy. Given the lack of recent disruption, I'd recommend a requester to come back if the IP starts editing again.
      --Mdaniels5757 (talk) 20:25, 29 July 2020 (UTC)

Here's a quick response. 36.74.53.222 was an open proxy, used by a banned user who uses open proxies. It was almost certainly open on port 8080 until at least the following day. A short block was indeed appropriate, though it could have been a few days really. 122.155.168.74 was again used by a (different) banned user who uses open proxies (typically NordVPN). Confirmation of this one eludes me however... there are servers throughout the range, for example at 122.155.168.71 .. 75, 76, 78, ..., so I also conclude this is {likely}, and probably a commercial VPN. As for the final IP, I think that's a pretty good summary. I suspect there might be some ISP filtering proxy with some dodgy security, but that's just a quick guess. Possible it is. I'll be back, probably within a day or two. -- zzuuzz (talk) 21:05, 29 July 2020 (UTC)

Cameron Archer

How do I post this link to his thread correctly, then?

https://www.heroesandvillains.info/forumv3/index.php?topic=60091.0HVLegion (talk) 21:13, 31 July 2020 (UTC)

Hi User:HVLegion. It depends on what purpose the link is (e.g. to cite something, for further information, etc.). First, I have a question: do you have any kind of connection to heroesandvillains.info (like working for them, being an admin/moderator, etc)? --Mdaniels5757 (talk) 21:18, 31 July 2020 (UTC)

I am the Moderator 'Legion'.HVLegion (talk) 21:19, 31 July 2020 (UTC)

The purpose is to provide further information. HVLegion (talk) 21:20, 31 July 2020 (UTC)

@HVLegion: OK. Taking a closer look at the link, I think that that's something that Wikipedia avoids linking to. See WP:ELNOT numbers 10 and 11. --Mdaniels5757 (talk) 21:24, 31 July 2020 (UTC)

Message from User:AnomieBOT about Template:Twocopies

AnomieBot put a message on its talk page that pinged me about {{Twocopies}}, saying something about too many parameters. You removed the message. I would like to understand what happened. That template doesn't take parameters, and is just used to display an unpleasant message on a draft to the submitter of the draft. So am I correct then that the bot was confused, and you removed the message because the bot was confused? If not, please explain. Robert McClenon (talk) 21:30, 1 August 2020 (UTC)

@Robert McClenon: It has nothing to do with parameters, but rather substitutions. The bot is supposed to complain if the template is WP:TRANSCLUDED more than 5 times, so a human can modify its settings. However, since the bot was wrong about it being transcluded too much, I removed the warning. Cheers, --Mdaniels5757 (talk) 18:00, 2 August 2020 (UTC)
So the bot was confused. The template is marked as a subst-only template, and I have been letting the bot subst it, just because it is easier not to have insert the subst: before the name of the template. So if the bot is complaining for no real reason, I will let it complain and let it do its job. Robert McClenon (talk) 18:31, 2 August 2020 (UTC)

Unblock request (autoblocked)

This user's request to have autoblock on their IP address lifted has been reviewed by an administrator, who accepted the request.
Mdaniels5757 (block log • active blocks • global blocks • autoblocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))
Mdaniels5757 (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log)

Block message:

Autoblocked because your IP address was recently used by "Whazza1". The reason given for Whazza1's block is: "Sock puppetry by User:Itsrobloxhereyt".

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Mdaniels5757/Archive_3&oldid=973415234"