Jump to content

User talk:Fuzheado/Archive 11

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


Wikidata weekly summary #354

Nomination for deletion of Template:US Congress member archive

Template:US Congress member archive has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Zackmann (Talk to me/What I been doing) 19:54, 7 March 2019 (UTC)

This Month in GLAM: February 2019





Headlines
Read this edition in fullSingle-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #355

Your draft article, Draft:Jane Chu

Hello, Fuzheado. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Jane Chu".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. Dolotta (talk) 16:11, 13 March 2019 (UTC)

Wikidata weekly summary #356

Wikidata weekly summary #357

User:Necrothesp

Since you are the original blocking Admin, just to let you know I've unblocked User:Necrothesp now that they have regained control of their account and set a new much more secure password. Just wanted to inform you. Let me know if there are any issues. Canterbury Tail talk 11:19, 26 March 2019 (UTC)

Facto Post – Issue 22 – 28 March 2019

Facto Post – Issue 22 – 28 March 2019

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.

When in the cloud, do as the APIs do

Half a century ago, it was the era of the mainframe computer, with its air-conditioned room, twitching tape-drives, and appearance in the title of a spy novel Billion-Dollar Brain then made into a Hollywood film. Now we have the cloud, with server farms and the client–server model as quotidian: this text is being typed on a Chromebook.

File:Cloud-API-Logo.svg
Logo of Cloud API on Google Cloud Platform

The term Applications Programming Interface or API is 50 years old, and refers to a type of software library as well as the interface to its use. While a compiler is what you need to get high-level code executed by a mainframe, an API out in the cloud somewhere offers a chance to perform operations on a remote server. For example, the multifarious bots active on Wikipedia have owners who exploit the MediaWiki API.

APIs (called RESTful) that allow for the GET HTTP request are fundamental for what could colloquially be called "moving data around the Web"; from which Wikidata benefits 24/7. So the fact that the Wikidata SPARQL endpoint at query.wikidata.org has a RESTful API means that, in lay terms, Wikidata content can be GOT from it. The programming involved, besides the SPARQL language, could be in Python, younger by a few months than the Web.

Magic words, such as occur in fantasy stories, are wishful (rather than RESTful) solutions to gaining access. You may need to be a linguist to enter Ali Baba's cave or the western door of Moria (French in the case of "Open Sesame", in fact, and Sindarin being the respective languages). Talking to an API requires a bigger toolkit, which first means you have to recognise the tools in terms of what they can do. On the way to the wikt:impactful or polymathic modern handling of facts, one must perhaps take only tactful notice of tech's endemic problem with documentation, and absorb the insightful point that the code in APIs does articulate the customary procedures now in place on the cloud for getting information. As Owl explained to Winnie-the-Pooh, it tells you The Thing to Do.

Links

If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 11:45, 28 March 2019 (UTC)

Wikidata weekly summary #358

Wikidata weekly summary #359

This Month in GLAM: March 2019





Headlines
  • Albania report: WikiFilmat SQ - new articles about the Albanian movie industry!
  • Armenia report: Art+Feminism+GLAM, Collaboration with Hovhannes Toumanian museum
  • Australia report: Art+Feminism 2019 in Australia
  • Brazil report: The GLAM at USP Museum of Veterinary Anatomy: a history of learnings and improvements
  • Colombia report: Moving GLAM institutions inside and outside Colombia
  • Czech Republic report: Edit-a-thon Prachatice
  • France report: Wiki day at the Institut national d'histoire de l'art; Age of wiki at the Musée Saint-Raymond
  • India report: Gujarat Vishw Kosh Trust content donation to Wikimedia
  • Italy report: Italian librarians in Milan
  • Macedonia report: WikiLeague: Edit-a-thon on German Literature
  • Netherlands report: WikiconNL, International Womens Day and working together with Amnesty, Field study Dutch Libraries and Wikimedia
  • Serbia report: Spring residences and a wiki competition
  • Sweden report: UNESCO; Working life museums; Swedish Performing Arts Agency shares historic music; Upload of glass plates photographs
  • UK report: Wiki-people and Wiki-museum-data
  • USA report: Women's History Month and The Met has two Wikimedians in the house
  • Wikidata report: Go Siobhan!
  • WMF GLAM report: Structured Data on Wikimedia Commons; Bengali Wikisource case study
  • Calendar: April's GLAM events
Read this edition in fullSingle-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #360

Wikidata weekly summary #361

Wikidata weekly summary #362

Facto Post – Issue 23 – 30 April 2019

Facto Post – Issue 23 – 30 April 2019

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.

Completely clouded?
Cloud computing logo

Talk of cloud computing draws a veil over hardware, but also, less obviously but more importantly, obscures such intellectual distinction as matters most in its use. Wikidata begins to allow tasks to be undertaken that were out of easy reach. The facility should not be taken as the real point.

Coming in from another angle, the "executive decision" is more glamorous; but the "administrative decision" should be admired for its command of facts. Think of the attitudes ad fontes, so prevalent here on Wikipedia as "can you give me a source for that?", and being prepared to deal with complicated analyses into specified subcases. Impatience expressed as a disdain for such pedantry is quite understandable, but neither dirty data nor false dichotomies are at all good to have around.

Issue 13 and Issue 21, respectively on WP:MEDRS and systematic reviews, talk about biomedical literature and computing tasks that would be of higher quality if they could be made more "administrative". For example, it is desirable that the decisions involved be consistent, explicable, and reproducible by non-experts from specified inputs.

What gets clouded out is not impossibly hard to understand. You do need to put together the insights of functional programming, which is a doctrinaire and purist but clearcut approach, with the practicality of office software. Loopless computation can be conceived of as a seamless forward march of spreadsheet columns, each determined by the content of previous ones. Very well: to do a backward audit, when now we are talking about Wikidata, we rely on integrity of data and its scrupulous sourcing: and clearcut case analyses. The MEDRS example forces attention on purge attempts such as Beall's list.

Links

If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 11:27, 30 April 2019 (UTC)

ArbCom 2019 special circular

Icon of a white exclamation mark within a black triangle
Administrators must secure their accounts

The Arbitration Committee may require a new RfA if your account is compromised.

View additional information

This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:30, 4 May 2019 (UTC)

Administrator account security (Correction to Arbcom 2019 special circular)

ArbCom would like to apologise and correct our previous mass message in light of the response from the community.

Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.

We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.

For the Arbitration Committee, -Cameron11598 21:03, 4 May 2019 (UTC)

Wikidata weekly summary #363

Category:Fashion executives has been nominated for discussion

Category:Fashion executives, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Rathfelder (talk) 14:37, 8 May 2019 (UTC)

This Month in GLAM: April 2019





Headlines
Read this edition in fullSingle-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #364

Facto Post – Issue 24 – 17 May 2019

Facto Post – Issue 24 – 17 May 2019
Text mining display of noun phrases from the US Presidential Election 2012

The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Semantic Web and TDM – a ContentMine view

Two dozen issues, and this may be the last, a valediction at least for a while.

It's time for a two-year summation of ContentMine projects involving TDM (text and data mining).

Wikidata and now Structured Data on Commons represent the overlap of Wikimedia with the Semantic Web. This common ground is helping to convert an engineering concept into a movement. TDM generally has little enough connection with the Semantic Web, being instead in the orbit of machine learning which is no respecter of the semantic. Don't break a taboo by asking bots "and what do you mean by that?"

The ScienceSource project innovates in TDM, by storing its text mining results in a Wikibase site. It strives for compliance of its fact mining, on drug treatments of diseases, with an automated form of the relevant Wikipedia referencing guideline MEDRS. Where WikiFactMine set up an API for reuse of its results, ScienceSource has a SPARQL query service, with look-and-feel exactly that of Wikidata's at query.wikidata.org. It also now has a custom front end, and its content can be federated, in other words used in data mashups: it is one of over 50 sites that can federate with Wikidata.

The human factor comes to bear through the front end, which combines a link to the HTML version of a paper, text mining results organised in drug and disease columns, and a SPARQL display of nearby drug and disease terms. Much software to develop and explain, so little time! Rather than telling the tale, Facto Post brings you ScienceSource links, starting from the how-to video, lower right.

ScienceSourceReview, introductory video: but you need run it from the original upload file on Commons
Links for participation

The review tool requires a log in on sciencesource.wmflabs.org, and an OAuth permission (bottom of a review page) to operate. It can be used in simple and more advanced workflows. Examples of queries for the latter are at d:Wikidata_talk:ScienceSource project/Queries#SS_disease_list and d:Wikidata_talk:ScienceSource_project/Queries#NDF-RT issue.

Please be aware that this is a research project in development, and may have outages for planned maintenance. That will apply for the next few days, at least. The ScienceSource wiki main page carries information on practical matters. Email is not enabled on the wiki: use site mail here to Charles Matthews in case of difficulty, or if you need support. Further explanatory videos will be put into commons:Category:ContentMine videos.


If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery

MediaWiki message delivery (talk) 18:52, 17 May 2019 (UTC)

Wikidata weekly summary #365

Wikidata weekly summary #366

Your close

Your close can't be serious, right? I thought your first one was weak because it ignored naming conventions and was simply a matter of voting, but this takes the cake. I hope you revert yourself or else you'll get the record for the quickest close overturned at WP:MR Calidum 20:41, 27 May 2019 (UTC)

You are free to do what you like. However, the quick re-listing of the move request which looks like nothing more than a repeat of the previous debate calls into question the exercise of good faith. Without providing any new insights, ask yourself whether it is a good use of the community's time to replay the entire debate. @Ahecht, Marc Lacoste, and BilCat: -- Fuzheado | Talk 09:37, 30 May 2019 (UTC)
What is this about? Thanks. - BilCat (talk) 13:03, 30 May 2019 (UTC)
This is regarding Calidum's creation of Talk:Boeing_737_MAX#Requested_move_25_May_2019, my closing it [2], then it being reopened again [3]. -- Fuzheado | Talk 15:30, 30 May 2019 (UTC)
Ok, thanks. The whole 737 MAX page has become for to politicized for me to be comfortable editing it, so I'm no longer watching the article/talk page. On the move discussion, if someone had an issue with how it was closed several weeks ago, it should have been taken to Move Review at that time, which would have decided if the move was closed improperly or not. - BilCat (talk) 22:14, 30 May 2019 (UTC)
@Calidum: - The RM has been closed [4] -- Fuzheado | Talk 10:21, 1 June 2019 (UTC)
  • So, do I need to remind you that Wikipedia is not a democracy, so basing consensus on percentages instead of relevant policy is flawed? Should I also remind you that the "policy" you cite is not a policy but a mere suggestion (and consensus can change)? Calidum 14:19, 1 June 2019 (UTC)
    • Feel free to continue doing what you judge as the best use of your time. -- Fuzheado | Talk 16:39, 1 June 2019 (UTC)

Move review for Boeing 737 MAX

An editor has asked for a Move review of Boeing 737 MAX. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Calidum 21:13, 1 June 2019 (UTC)

Wikidata weekly summary #367

Fuzheado, The Purple Barnstar

The Purple Barnstar
No matter what the outcome of the move discussion is, I award Fuzheado The Purple Barnstar for remaining cool at Wikipedia:Move_review/Log/2019 June#Boeing 737 MAX despite being unfairly and incorrectly accused of misuse, when their intention was to procedurally close arguments which clearly and unambiguously had no consensus. My message to Fuzheado is my faith in the user and their ability to handle admin tools remains, and I hope this incident will not stop the user from closing other move discussions. Remain confident, and I hope to see you around. Optakeover(U)(T)(C) 18:07, 8 June 2019 (UTC)

This Month in GLAM: May 2019





Headlines
Read this edition in fullSingle-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #368

Wikidata weekly summary #369

Wikidata weekly summary #370

Wikidata weekly summary #371

Administrators' newsletter – July 2019

News and updates for administrators from the past month (June 2019).

Administrator changes

removed 28bytesAd OrientemAnsh666BeeblebroxBoing! said ZebedeeBU Rob13Dennis BrownDeorDoRDFloquenbeam1Flyguy649Fram2GadfiumGB fanJonathunderKusmaLectonarMoinkMSGJNickOd MishehuRamaSpartazSyrthissTheDJWJBscribe
1Floquenbeam's access was removed, then restored, then removed again.
2Fram's access was removed, then restored, then removed again.

Guideline and policy news

  • In a related matter, the account throttle has been restored to six creations per day as the mitigation activity completed.

Technical news

  • The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Community feedback is invited.

Miscellaneous


Sent by MediaWiki message delivery (talk) 21:19, 1 July 2019 (UTC)

Wikidata weekly summary #372

This Month in GLAM: June 2019





Headlines
Read this edition in fullSingle-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Thank you for your interest in WikiLoop

Hi @Fuzheado:,

Very happy to see that you signed-up for WikiLoop. Our most recent development is focusing on wikiloop battlefield, I wonder if you have tried it out? We look forward to early feedback as we are actively iterating on it. Thank you! Xinbenlv (talk) 05:02, 9 July 2019 (UTC)

@Xinbenlv: Yes! I've been using it and I think it's a great step in the right direction. Some things I noticed:
  • It would be good to explain when mousing over the icons of faces and cloud what they mean. Right now all I see is "from WMF ORES score" and even though I'm familiar with ORES, I'm not sure what these mean.
  • If the username of the person who made the edit in question has no user page, it would be nice to display the name in red (See "User:Jkmistry17") because for vandal fighting, it helps to see whether the person editing is very new and a red userpage link helps in determining this.
  • I *think* I know what "Overriden" means (someone else has acted on it already) though this is a bit confusing. Perhaps a better or more detailed message here?

Great work though. A really useful tool. -- Fuzheado | Talk 10:55, 9 July 2019 (UTC)

  • @Fuzheado:Great, thanks for the feedback! I have created bug tracking for these suggestions and it should be rolled out in upcoming releases soon! Xinbenlv (talk) 01:59, 10 July 2019 (UTC)
  • {{ping}|Fuzheado}, Hi Fuzheado, thank you for your feedback. Here is my improvement per your feedback: I add hover-explanation and link to the ORES scores. And have been planning adding ability to show user information. My question for you is, what's a better message for "Overriden?" Xinbenlv (talk) 21:33, 10 July 2019 (UTC)
@Xinbenlv:, regarding "overriden", I would suggest simply "Reverted" unless there's another state for the edits.--Jorm (talk) 21:35, 10 July 2019 (UTC)
@Jorm:, thank you. I like it and I wish to, but technically we don't know if it was actually reverted or just happen to be behind a new incoming edit revision. What should we do then? Xinbenlv (talk) 22:04, 10 July 2019 (UTC)
@Xinbenlv: Maybe try "addressed", then? If you can be verbose, "addressed or passed"--Jorm (talk) 22:22, 10 July 2019 (UTC)
@Jorm: I don't think addressed is a good term, either, because maybe the next edit revision is simply irrelevant. I actually want to say that "because a new revision has come, you can no longer directly revert this revision you are looking at." What do you think? Xinbenlv (talk) 23:37, 10 July 2019 (UTC)
@Xinbenlv: Then you want the word “stale” or a variation thereof. Note that you can often still directly revert edits even if someone has edited overtop of it. It’s alsp possible to see if they were reversions. --Jorm (talk) 23:57, 10 July 2019 (UTC)
@Jorm: stale' sounds good to me, or maybe "obsolete" (sounds a bit technical)? Xinbenlv (talk) 23:59, 10 July 2019 (UTC)

Wikidata weekly summary #373

Wikidata weekly summary #374

Wikidata weekly summary #375