This is an archive of past discussions with User:Mdaniels5757. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
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)
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)
@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)
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. EEng21: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)
@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)
Hi User:YoungForever. Yeah, I wondered what was up with that. I checked through the history when performing my post-move cleanup, and saw that what was at Talk:Peripheral Component Interconnect pre-move had text before, so I chose to leave it. However, what I didn't notice was that it actually was from a copy/paste move (ugh). Since there were no attribution issues, I've created that redirect now. Best, --Mdaniels5757 (talk) 00:59, 25 June 2020 (UTC)
Wikidata weekly summary #423
Here's your quick overview of what has been happening around Wikidata over the last 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.
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)
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.
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)
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)
Hi. I'm afraid I can't help you with this, I don't have the needed permissions. I hope Berean Hunter can resolve your issue. --Mdaniels5757 (talk) 22:00, 25 June 2020 (UTC)
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)
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) FacebookYouTube
Upcoming video: July 25 - Wikipedia Weekly Network - LIVE Wikidata editing #13 FacebookYouTube
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!
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)
@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)
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.
Upcoming: Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Liam Wyatt on WikiCite and its future plans, ways to get involved, and discussions that are happening in the community, 28 July. Agenda
Past: Wikidata and Wikibase office hour with a focus on the Query Service, July 21st. Notes of the discussions
Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #14, August 1 FacebookYouTube
Library’s linked-data project gets new grant. "Known as Linked Data for Production, the project is part of a long-term collaboration among Cornell University Library, Stanford Libraries and the School of Library and Information Science at the University of Iowa. Through linked data, information about books and other items in library records will be enhanced by related information from external online sources". By Jose Beduya
Wikidata Training Workshop 1, by Canadian Arts Presenting Association
Part 1 - Introduction to Wikidata - YouTube (En, Fr)
Part 3 - Components of a Wikidata item - YouTube (En, Fr)
Video: Wikidata Lab XXIV on relative digital positioning (in Portuguese). YouTube
Video: Women Writers in Review: Integrating special collections into Wikidata. YouTube
Video: Wikipedia Weekly Network - Entity Schemas and Shape Expressions (ShEx) FacebookYouTube
Video: Wikipedia Weekly Network - LIVE Wikidata editing #13 FacebookYouTube
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.
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
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 mots17:14, 20 July 2020 (UTC)
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.
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)
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.
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]
Video: Wikipedia Weekly Network - QuickStatements and Distributed Wikidata games Facebook, YouTube
Video: Collaboration, contribution and use of Wikidata and Wikipedia by academic libraries (in Greek). YouTube
Librarians work to broaden Vanderbilt’s research reputation with Wikidata tools. "To speed up the creation of metadata about faculty and their publications, Steven Baskauf, data science and data curation specialist for libraries, developed “VanderBot,” a set of scripts that can read and write to Wikidata, greatly improving the efficiency by which Vanderbilt’s faculty are discoverable through Wikidata".
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?
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)
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.
Broken off from the above "Unblock request (autoblocked)" section
Wait, what? I came by here to say "oh you got a bot too!"--and saw this, and as chance would have it, I blocked a whole bunch of Whazzas the other day. Small world! Drmies (talk) 01:44, 6 August 2020 (UTC)
You don't have admin glasses yet so you can't see my log, but there's Whazza2 and Whazza3 in there. BTW I'm convinced they are incarnations of an older sock, someone who edits road articles, but I can't remember who that was. Get yourself those special glasses! Drmies (talk) 01:49, 6 August 2020 (UTC)
@Drmies: Who knows, maybe in that September flight! Although, thinking more about it, perhaps a bit later—I'd probably need to create 2 GAs or 1 FA first if I wanted to pass, as that seems to be a baseline for RFA passage recently. (I also ought to do it anyways—I've been meaning to do meaningful content creation for a while.) --Mdaniels5757 (talk) 01:55, 6 August 2020 (UTC)
What people will want to see is that you have a sense of what article writing is about. You don't need an FA or a GA for it, although that would help, but many RfA regulars do look at editors like you with some reservations (I just went through your contributions) and will think you won't be able to imagine what it's like to write, and so you might not have the appropriate...what's the word, sympathy for content contributors. But that kind of experience is not hard to get. I mean, The Afersata: an Ethiopian novel and Because of Women are still redlinks--how crazy is that? Anyway, you certainly can make a case that you can put the tools to good use with all this "maintenance" stuff that you do, the tech stuff. I was looking at your rights, and people who trusted you enough to grant you various powers include Primefac, TonyBallioni, Xaosflux, Stwalkerster, and Zzuuzz--those are big names.
Stop, I'm blushing :). To be honest, I wasn't really considering making Wikipedia:Requests for adminship/Mdaniels5757 blue anytime soon, but perhaps I will after making a couple articles (I could try to run without that experience, but I imagine my chances in an RfA would be significantly lower, and I ought to do so anyways). --Mdaniels5757 (talk) 03:02, 6 August 2020 (UTC)
More potential redirects to Template:End
Per your recent TFD which ended in a useful set of redirects, I stumbled across a couple more. These 12 results may need to be checked to see which ones are truly identical to {{end}}, but most of them appear to be (the Ratings table template appears to have additional code). – Jonesey95 (talk) 14:00, 6 August 2020 (UTC)
G13 Eligibility Notice
The following pages will become eligible for CSD:G13 shortly.
Video: Editing Wikidata with information from Son jarocho (in Spanish). YouTube
Tool of the week
Entity Explosion: a new multilingual Chrome browser extension. "Taking the power of Wikidata with me wherever I go across the web!". Uses API calls to the Wikidata Query Service to match the URL you are browsing on to a Wikidata item, and then displays data and links to other sites about the same entity. (Video)
Fixed a bug where a length limit for strings seems to have reverted itself back from 1500 to its default 400 (phabricator:T259440)
Fixed a bug that Wikibase is not always adding &redirect=no in situations when MediaWiki usually does (phabricator:T255387)
Wrapping up the initial work on the design system so it is ready for use in the first new feature (Query Builder)
Fixed the serialization of statements on Forms and Senses not containing the datatype (phabricator:T249206)
Wrapping up work on the first version of Federated Properties so that other Wikibase installations can use Wikidata's Properties instead of having to maintain their own
Worked on ensuring the data from the linked data interface at Special:EntityData is always up to date after an edit has been made (phabricator:T128486)
Enabling clients to use Lua to request labels, descriptions and aliases in some (often minority) languages even when they are not content languages (phabricator:T259340, phabricator:T260118)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
If you revert an edit using the undo link your edit is marked with an undo tag. This will now only happen if you don't change anything in the edit window before publishing the undo. This is to keep users from marking edits as undos when they actually do something else. [2]
The new OOUI version will not work with Internet Explorer 8. This means the wikis will look strange and not work well in Internet Explorer 8. This was reported in Tech/News/2020/17. This is because keeping the wikis working with very old browsers creates other problems. [3]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 August. It will be on non-Wikipedia wikis and some Wikipedias from 19 August. It will be on all wikis from 20 August (calendar).
Future changes
All wikis will be read-only for a few minutes on September 1. This is planned between 13:30 and 15:30 UTC. More information will be published in Tech News and will also be posted on individual wikis next week. This is a reminder. You can help by translating the announcement message. [4][5]
Why would you substitute {{Hot100brasil.com}} when it was deleted because such a notice was unnecessary. Now we still have the notice but we can't easily update it. I think it should just be removed. --Trialpears (talk) 14:24, 9 August 2020 (UTC)
Sarasua, Cristina, & Mietchen, Daniel. (2020, August). Multilingual Structured Climate Research Data in Wikidata - The Community Perspective. Zenodo. http://doi.org/10.5281/zenodo.3994272
Mietchen, Daniel, & Sarasua, Cristina. (2020, August). Multilingual Structured Climate Research Data in Wikidata - The Data Perspective. Zenodo. http://doi.org/10.5281/zenodo.3994266 (also on YouTube)
Video: How to add missing descriptions to Wikidata using QuickStatments tool (in Arabic) - YouTube
Video: Wikipedia Weekly Network - LIVE Wikidata editing #16 Facebook, YouTube
Video: Introduction to Wikidata (in Malayalam) - YouTube
Video: Wikidata editing basics (in Chinese) - YouTube
Tool of the week
Sophox allows for SPARQL querying of Wikidata and OpenStreetMap in a single query
Other Noteworthy Stuff
Two new grant programs from WikiCite, in support of open citations and linked bibliographic data.
Full documentation, eligibility requirements, selection criteria, program design principles, and contacts at the links. Apply by 1 October.
e-Scholarships [per-diem calculated on your city; 1-5 people (single, or as a 'remote group') for 2-4 days, for COVID-era "stay at home" projects. Paid in advance living allowance, no expense report required.]
Finished working on ensuring Labels of Items in some unusual, often minority, languages are still available on Wikipedia and other clients (phabricator: T259340)
Fixed error messages for API modules that will not work with the first version of Federated Properties (phabricator:T258558)
Working on improving how ORES judges the quality of an Item to make it more accurate
Started coding on Automated Configuration Discovery to make it easier for tool builders to make their tools work for other Wikibase instances as well
Thank you for your efforts in stepping up to mediate a dispute between two Template editors. I appreciate your objectivity, wisdom, and good faith attempts to move things forward without admin intervention. It seems like you were on the right track to resolving the dispute and I 100% would have closed the thread in deference to your mediation if another admin had not interjected in order to threaten one party. Thus a bilateral warning had to be issued for the sake of fairness. Anyway, this kind of stepping-up to mediate disputes is rare and it is very much appreciated. Thanks again, and keep up the good work. ~Swarm~{sting}05:34, 16 August 2020 (UTC)
Hi, I was going to advise you to refrain from closing discussions when you don't have the technical access to fully carry out the closure yourself, even if it seems like a no-brainer. (Referencing Wikipedia:Templates_for_discussion/Log/2020_August_20#Template:Tfd_instructions.) However, a superficial review of your contributions to date makes me think you might be an asset to the project as an administrator. Any reason you haven't yet put yourself forward for the mop? Aervanath (talk) 22:40, 21 August 2020 (UTC)
@Aervanath and Bradv: Thank you both for saying this. I'm considering doing so soon™, but want to have more substantial content creation work first (both because it'd be useful at RfA, and any successful RfA of mine would probably make my content contributions more sparse). Also, with regard to NACs as delete, my understanding was that delete closures of TfDs are acceptable per Wikipedia:Non-admin closure#Templates for discussion. However, a review of the relevant RfC shows that those are only for orphan closures. I'll seek clarification on WT:TFD on which is accurate. Best, —Mdaniels5757 (talk • contribs) 15:58, 22 August 2020 (UTC)
File:Milwaukeebears.png FFD close
I get your close of this file, but just want to point out that file was already licensed as PD when it was nominated; so, it technically can't be a candidate for PD. The problem was that the nominator was trying to apply WP:NFCC to a file that isn't subject to NFCC; that's equivalent to applying BLP to an article or article content not covered by BLP. If the nominator had challenge the file's PD license, then that would've be an acceptable nomination; it might still have been misguided, but that could've been discussed. Trying to claim NFCC applies to files that aren't non-free, however, is non-starter and there's nothing to discuss.
Finally, just a personal observation so please only take it as such; it might be better to word your close a little more neutrally so that it doesn't seem like a WP:SUPERVOTE. I get there's a lot of frustration with what's happened here withe these nominations; if you want to say the file's obviously "PD-logo", however, it would probably be better to do so as a WP:!VOTE instead. -- Marchjuly (talk) 01:04, 23 August 2020 (UTC)
I just want to add that I appreciate you taking the time to try and help sort some of these files out. Some probably needed to be discussed, but the sheer number of files nominated on that day means it's going to take more time than perhaps is usually needed to figure out what those files are. -- Marchjuly (talk) 01:13, 23 August 2020 (UTC)
Upcoming: live SPARQL queries on Twitch and in French by Vigneron, September 1 at 18:00 CEST
Upcoming: WMF search platform team office hour, September 2nd at 17:00 CEST (15:00 GMT). Etherpad, Google Meet. You can come and chat about the Wikidata & Commons Query Service.
Upcoming video: Wikipedia Weekly Network - LIVE Wikidata editing #18 Facebook, YouTube, September 5 at 19.00 UTC
Upcoming: Onam label-a-thon (September 1st and 2nd): Online label-a-thon to improve Wikidata items related to Kerala and Malayalam on this Onam holidays.
Wikidata for Firefox is a browser extension that displays Wikidata items while browsing the web, adds missing IDs and extracts information from websites to Wikidata.