User talk:TheDJ

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Welcome to my talk page !

Script redirection request[edit]

Hi. You previously been willing to redirect unmaintained, widely used user scripts to maintained ones. Would you be willing to do so for User:Ucucha/duplinks.jsUser:Evad37/duplinks-alt.js? Ucucha's version hasn't been updated since 2011 (except for your fixes in 2017), and problems keep coming up at User talk:Ucucha/duplinks that have been fixed in my version. Many users are already using my version [1]. Cheers, - Evad37 [talk] 01:18, 24 January 2019 (UTC)

Ucucha is minimally/marginally active, so perhaps it'd be better to discuss with them directly? AFAICT they haven't been pinged in a while. ~ Amory (utc) 02:47, 24 January 2019 (UTC)
Oops, forgot to check their general activity level; I've now asked at User talk:Ucucha#duplinks. - Evad37 [talk] 03:12, 24 January 2019 (UTC)

Facto Post – Issue 20 – 31 January 2019[edit]

Facto Post – Issue 20 – 31 January 2019
Logo for ContentMine ScienceSource.svg

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.
Back numbers are here.

Everything flows (and certainly data does)

Recently Jimmy Wales has made the point that computer home assistants take much of their data from Wikipedia, one way or another. So as well as getting Spotify to play Frosty the Snowman for you, they may be able to answer the question "is the Pope Catholic?" Possibly by asking for disambiguation (Coptic?).

Amazon Echo device using the Amazon Alexa service in voice search showdown with the Google rival on an Android phone

Headlines about data breaches are now familiar, but the unannounced circulation of information raises other issues. One of those is Gresham's law stated as "bad data drives out good". Wikipedia and now Wikidata have been criticised on related grounds: what if their content, unattributed, is taken to have a higher standing than Wikimedians themselves would grant it? See Wikiquote on a misattribution to Bismarck for the usual quip about "law and sausages", and why one shouldn't watch them in the making.

Wikipedia has now turned 18, so should act like as adult, as well as being treated like one. The Web itself turns 30 some time between March and November this year, per Tim Berners-Lee. If the Knowledge Graph by Google exemplifies Heraclitean Web technology gaining authority, contra GIGO, Wikimedians still have a role in its critique. But not just with the teenage skill of detecting phoniness.

There is more to beating Gresham than exposing the factoid and urban myth, where WP:V does do a great job. Placeholders must be detected, and working with Wikidata is a good way to understand how having one statement as data can blind us to replacing it by a more accurate one. An example that is important to open access is that, firstly, the term itself needs considerable unpacking, because just being able to read material online is a poor relation of "open"; and secondly, trying to get Creative Commons license information into Wikidata shows up issues with classes of license (such as CC-BY) standing for the actual license in major repositories. Detailed investigation shows that "everything flows" exacerbates the issue. But Wikidata can solve it.

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) 10:53, 31 January 2019 (UTC)

Administrators' newsletter – February 2019[edit]

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

ANEWSicon.png

Administrator changes

added EnterpriseyJJMC89
readded BorgQueen
removed Harro5Jenks24GraftR. Baley

Interface administrator changes

removedEnterprisey

Guideline and policy news

  • A request for comment is currently open to reevaluate the activity requirements for administrators.
  • Administrators who are blocked have the technical ability to block the administrator who blocked their own account. A recent request for comment has amended the blocking policy to clarify that this ability should only be used in exceptional circumstances, such as account compromises, where there is a clear and immediate need.
  • A request for comment closed with a consensus in favor of deprecating The Sun as a permissible reference, and creating an edit filter to warn users who attempt to cite it.

Technical news

  • A discussion regarding an overhaul of the format and appearance of Wikipedia:Requests for page protection is in progress (permalink). The proposed changes will make it easier to create requests for those who are not using Twinkle. The workflow for administrators at this venue will largely be unchanged. Additionally, there are plans to archive requests similar to how it is done at WP:PERM, where historical records are kept so that prior requests can more easily be searched for.

Miscellaneous

  • Voting in the 2019 Steward elections will begin on 08 February 2019, 14:00 (UTC) and end on 28 February 2019, 13:59 (UTC). The confirmation process of current stewards is being held in parallel. You can automatically check your eligibility to vote.
  • A new IRC bot is available that allows you to subscribe to notifications when specific filters are tripped. This requires that your IRC handle be identified.

Sent by MediaWiki message delivery (talk) 02:16, 4 February 2019 (UTC)

Talk page consult[edit]

[2] Yes, in fact I am watching #Parsoid-PHP on Phabricator, and I'm leaving an edit on this page having previewed it in WTE2017 ;). I mostly just did not want to get into the Javascript-PHP migration detail, since it was unimportant in context. --Izno (talk) 17:10, 26 February 2019 (UTC)

Facto Post – Issue 21 – 28 February 2019[edit]

Facto Post – Issue 21 – 28 February 2019
Logo for ContentMine ScienceSource.svg

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.
Back numbers are here.

What is a systematic review?

Systematic reviews are basic building blocks of evidence-based medicine, surveys of existing literature devoted typically to a definite question that aim to bring out scientific conclusions. They are principled in a way Wikipedians can appreciate, taking a critical view of their sources.

PRISMA flow diagram for a systematic review

Ben Goldacre in 2014 wrote (link below) "[...] : the "information architecture" of evidence based medicine (if you can tolerate such a phrase) is a chaotic, ad hoc, poorly connected ecosystem of legacy projects. In some respects the whole show is still run on paper, like it's the 19th century." Is there a Wikidatan in the house? Wouldn't some machine-readable content that is structured data help?

2011 photograph by Bernard Schittny of the "Legacy Projects" group

Most likely it would, but the arcana of systematic reviews and how they add value would still need formal handling. The PRISMA standard dates from 2009, with an update started in 2018. The concerns there include the corpus of papers used: how selected and filtered? Now that Wikidata has a 20.9 million item bibliography, one can at least pose questions. Each systematic review is a tagging opportunity for a bibliography. Could that tagging be reproduced by a query, in principle? Can it even be second-guessed by a query (i.e. simulated by a protocol which translates into SPARQL)? Homing in on the arcana, do the inclusion and filtering criteria translate into metadata? At some level they must, but are these metadata explicitly expressed in the articles themselves? The answer to that is surely "no" at this point, but can TDM find them? Again "no", right now. Automatic identification doesn't just happen.

Actually these questions lack originality. It should be noted though that WP:MEDRS, the reliable sources guideline used here for health information, hinges on the assumption that the usefully systematic reviews of biomedical literature can be recognised. Its nutshell summary, normally the part of a guideline with the highest density of common sense, allows literature reviews in general validity, but WP:MEDASSESS qualifies that indication heavily. Process wonkery about systematic reviews definitely has merit.

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) 10:02, 28 February 2019 (UTC)

Administrators' newsletter – March 2019[edit]

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

Guideline and policy news

Technical news

  • A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.

Arbitration

  • The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
    • paid-en-wp@wikipedia.org has been set up to receive private evidence related to abusive paid editing.
    • checkuser-en-wp@wikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.

Miscellaneous


Sent by MediaWiki message delivery (talk) 21:13, 4 March 2019 (UTC)

Orphaned non-free image File:IISER-Pune logo.png[edit]

⚠

Thanks for uploading File:IISER-Pune logo.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:28, 22 March 2019 (UTC)

citethispage-content[edit]

Hey Derk-Jan. A user has noticed that CiteThisPage has started failing to parse wikitext for BibTeX, see for example Special:CiteThisPage/Main Page. I looked into it and found you made a change to citethispage-content which may have caused this. I would test out undoing it and seeing if that fixes anything but my GEI flag was expired recently. --Krenair (talkcontribs) 01:40, 24 March 2019 (UTC)

Krenair, euh, that's weird... so a template transcluded pre takes the parsed variables and formats them inside pre, but a direct pre disables the wikitext parsing ??? —TheDJ (talkcontribs) 10:46, 24 March 2019 (UTC)
yuck, this is actually documented behavior.. We've created some messed up markup language..... —TheDJ (talkcontribs) 10:49, 24 March 2019 (UTC)
Don't use <pre>...</pre>, or attempt to play around with <nowiki>...</nowiki> and <code>...</code>. Just use <source lang=moin>...</source> and the whole lot is sent through unprocessed apart from syntax highlighting colours. --Redrose64 🌹 (talk) 15:04, 24 March 2019 (UTC)

Facto Post – Issue 22 – 28 March 2019[edit]

Facto Post – Issue 22 – 28 March 2019
Logo for ContentMine ScienceSource.svg

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.
Back numbers are here.

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.

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:46, 28 March 2019 (UTC)

Administrators' newsletter – April 2019[edit]

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

Technical news

Arbitration

Miscellaneous

  • Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
  • As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.

Sent by MediaWiki message delivery (talk) 21:57, 7 April 2019 (UTC)

The Signpost v2[edit]

From what I can tell, you were one the main architect of the -v2 look of The Signpost. So I'm going to give you a heads up / chance to comment on User:Headbomb/New at the Signpost before it's published. In particular, I want to make sure this doesn't come across as criticism of the old work since there was clearly a lot of thought put into these templates. So if you could share some thoughts and impressions on this piece (@Resident Mario: too, if you were involved with -v2), that would be great. Headbomb {t · c · p · b} 03:42, 9 April 2019 (UTC)

Headbomb, yes, i wrote them a while back, to make the page more responsive on mobile devices. Now that we have TemplateStyles a lot of this can probably be seriously improved btw.. I guess v3 at some point ;) Did you check backwards compatibility with the old published archive btw ? Lastly the Newsroom and some of those other admin pages never got the full rework of v2. For instance they still contain huge tables wrapping everything that aren't really needed any longer. You can clearly see this on /Newsroom, where the progress bar is again narrow, due to the wrapping and even unbalanced table. I took a look at it yesterday, but couldn't complete in time to finish that up. —TheDJ (talkcontribs) 08:26, 9 April 2019 (UTC)
A v3 would be nice at some point I suppose, but v2 works pretty good. At least with the recent polish. Some of the code update is on purpose pointless, just so it's a bit clearer for someone who uses it to understand what's going on. Can't say I'm 100% happy with fullwidth=yes/no. Maybe that's something that should be switched to style=fullwidth / style=twocolumns, but it's working well now.
I was mostly looking for commentary on the write up, more than ruminations on the design, but it's not wrong to discuss that either :p. From my understanding of the -v2 design, everything should be backward compatible (I did spot checks as well), except in cases where someone forgot to balance divs. I'm not sure what you mean by the progress bar in the newroom. It you mean the deadlines, they looks fine here, but I'm on desktop monobook, and they're not really a -v2 thing. Headbomb {t · c · p · b} 09:51, 9 April 2019 (UTC)

Sort templates[edit]

Hey, I was browsing the deprecated template lists and noticed that you deprecated and edited most of the group of sort templates ({{Hidden sort key}}, {{Sort}}, {{Sortname}}, {{Hid}}). They still have a lot of transclusions and I couldn't understand what they were replaced with. Could you please explain this to me? --Gonnym (talk) 11:37, 14 April 2019 (UTC)

@Gonnym: data-sort-value where necessary; in many cases it's no longer necessary since the sortability Javascript does a better job sorting now than it did when all of those templates were written. See also Help:Sorting. --Izno (talk) 22:38, 14 April 2019 (UTC)
@Izno: but the templates already use data-sort-value, which is why I'm not sure what exactly is their replacement. --Gonnym (talk) 15:01, 15 April 2019 (UTC)
Gonnym, many of the templates were deprecated when the data-sort-value methodology they use right now (wrapping content, instead of marking the table cell) was not yet possible. Importantly all these templates, while no longer adding hidden sort keys, do still rely on textual sorting, while straight up data-sort-value and data-sort-type markers can use things like numerical sorting, which would make more sense. For that reason most are still deprecated. Templates like {{hidden sort key}}, {{hid}} and {{ntsh}} etc are deprecated because all sort keys are hidden now. As such a proper usage of {{sort}} or {{nts}} is preferable. I wouldn't object to removing the deprecation notice from sort and sortname, although I would suggest to keep a notice about using data-sort-value as the primary methodology. —TheDJ (talkcontribs) 09:21, 17 April 2019 (UTC)
Would a correct approach for TfD be to propose replacement of {{Hidden sort key}}, {{Sort}} and {{Hid}} with {{sort}}, and {{ntsh}} with {{Number table sorting}}? --Gonnym (talk) 10:06, 17 April 2019 (UTC)
Gonnym, seems about right. The issue is in replacing though. the hidden keys are usually a prefix to the value being 'masked' in sorting. Whereas the 'proper' templates need to 'wrap' the value being 'overridden'. That means some contextual interpretation of the intent of the author. As such an automated replacing of the templates might be difficult. —TheDJ (talkcontribs) 10:49, 17 April 2019 (UTC)