Jump to content

User talk:Zazpot/Archive 6

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1←Archive 4Archive 5Archive 6Archive 7Archive 8→Archive 10

Wikidata weekly summary #314

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • IRC office hour, on May 29th at 18:00 (UTC+2, Berlin time), on the IRC channel #wikimedia-office. Special topic: Lexemes on Wikidata
  • Development
    • Deployed and activate WikibaseLexeme on wikidata.org so you can now store the first lexicographical data on Wikidata (phab:T191457)
    • Fixing the encoding issues on labels of items linked on Lexemes (phab:T195470, phab:T195359)
    • Fixed an issue that was preventing adding Forms and Lexemes in statements (phab:T195402)
    • Suppressed the browser's autocomplete that covers WikibaseLexeme's suggestion on Special:NewLexeme (phab:T195383, phab:T191526)
    • Worked on a bug about representation overwriting other representation with the same language code (phab:T193636)
    • Changed title of the field of a lemma language to make it less likely for people to add a translation as a second Lemma (phab:T193603)
    • Working on the RDF mapping of WikibaseLexeme (phab:T160260)
    • Working on implementing fulltext search for Lexemes (phab:T189739)
    • Working on showing Lemmas for linked Lexemes instead of just their ID on special pages like Special:AllPages (phab:T195382)
    • Fixing issues that happened after dropping an index from the wb_terms table (phab:T194270, phab:T195642, phab:T195611)
    • Made constraint check result appear directly after adding a new statement (phab:T194247)
    • Working on looking up entities by external identifiers on Special:Search (phab:T99899)
    • Added Docker image to Wikibase website (phab:T189936)
    • Added WikibaseImport script to Docker images to make it easier for people to start their own Wikibase install with some data imported from Wikidata (phab:T192080)

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.


Proposed deletion of Bar sinister (disambiguation)

Notice

The article Bar sinister (disambiguation) has been proposed for deletion. The proposed deletion notice added to the article should explain why.

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. —Sangdeboeuf (talk) 09:28, 4 June 2018 (UTC)

Wikidata weekly summary #315

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • The API respond for maxlag will in the future also include the dispach lag (phab:T194950)
    • Add Elastic and CirrusSearch in the Wikibase Docker image (phab:T192813)
    • Add OAuth extension to wikibase bundle container (phab:TT192364)
    • Work on showing constraints in the QueryService (phab:T194762)
    • Make the PropertySuggester use CirrusSearch (phab:T195490)
    • Add integer constraint in the constraint checks (phab:T167989)
    • Add “citation needed” constraint type (phab:T195052)
    • Make Special:EntityData should handle form IDs (phab:T192149)
    • Fix encoding problems for labels displayed in Lexemes (phab:T195359)
    • Improve the text in the grammatical feature field (phab:T193604)
    • Work on showing Lemma on Special:AllPages and other pages (phab:T195382)
    • Work on better handling use of statements linking to Lexemes on client (phab:T195615)
    • Fix a bug that breaks Lexeme when language or lexical category items don't have a label (phab:)

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.


Wikidata weekly summary #316

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Press, articles, blog posts
    • Learning to Generate Wikipedia Summaries for Underserved Languages from Wikidata, presented at the Conference of the North American Chapter of the Association for Computational Linguistics by Lucie Kaffee and Hady Elsahar (see the poster and the paper)
  • Development
    • Developing a prototype for usability testing for how the term box (labels, descriptions, aliases) could work on mobile
    • Investigating how we can do the display of items (their label and sometimes description when linked to in a statement or in listings like Recent Changes) in a way that is less of an issue for the database
    • Working on including the dispatch lag in the maxlag API to make it easier for bots to see when they should stop editing because of performance reasons (phabricator:T194950)
    • Working on adding a Lua function to check if an item is a subclass/instance of another one (phabricator:T179155)
    • Created an API that returns constraint violations for an item in TTL format in preparation for making constraint violations queryable in the query service (phabricator:T194762)
    • Started planning for support for Senses
    • Added more helpful text on Special:NewLexeme to make it easier to understand what information is required (phabricator:T193602)
    • Working on pre-filling the spelling variant for a new Form's representation (phabricator:T195708)
    • Worked on showing the Lemma of a Lexeme instead of just its ID in Special:AllPages, Recent Changes and diffs (phabricator:T191600, phabricator:T195382, phabricator:T195511)
    • Made the representation of a Form in a diff link to the Form (phabricator:T195512)
    • Fixed an issue on the Wikipedias and co when a statement in an item that was used there linked to a Form or Lexeme (phabricator:T195615)
    • Made the "publish" button stay disabled for a Lexeme's header when there is nothing to save (phabricator:T196342)

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.


June 2018

Stop icon

Your recent editing history at GNU Privacy Guard shows that you are currently engaged in an edit war. To resolve the content dispute, please do not revert or change the edits of others when you are reverted. Instead of reverting, please use the talk page to work toward making a version that represents consensus among editors. The best practice at this stage is to discuss, not edit-war. See BRD for how this is done. If discussions reach an impasse, you can then post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.

Being involved in an edit war can result in your being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you don't violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly. Bbb23 (talk) 11:39, 14 June 2018 (UTC)

@Bbb23: I'm not sure that reverting spam counts as edit-warring. Plus, I did contact the user(s) whose edits I was reverting, numerous times, in an effort to get them to stop. (They did not reply.) And I did request and receive page protection; but the editor just registered an account and continued to make the same edits. That is one of the reasons I filed an SPI, so that they could be shown to be IPSOCKing, because otherwise the IP edits would have to be considered as coming from separate users, and hence would not be considered to break 3RR. But you declined the SPI. Had I not reverted Er22chi's edits, prompting them to revert my reversions, you might not have been in a position to report them at the edit-warring noticeboard. Fortunately, another editor has now (finally) blocked Er22chi, albeit only for 48 hours.
Anyhow, if you have a concrete suggestion about how I could have handled this better, and without being slapped with the template above, I would welcome it. If not, then please could you withdraw that template? Thanks, Zazpot (talk) 14:17, 15 June 2018 (UTC)
I'm sympathetic, but the kind of edits you were reverting are not exempt from edit-warring in my view. I would have stopped at two reverts and dealt with the user in some other fashion. I gave you the warning because I wanted you to stop. I gave them the warning as well, they didn't stop, they got blocked. I would have blocked them myself, but because I had also reverted, I was WP:INVOLVED and couldn't. If after the block expires, the user reinstates the material, I would immediately report them to WP:AN3 - it's not necessary to wait until they breach 3RR again.--Bbb23 (talk) 14:29, 15 June 2018 (UTC)
@Bbb23: thanks for your reply. You say, "I would have stopped at two reverts and dealt with the user in some other fashion." What would that other fashion be? This is a serious question. I want to keep fighting vandalism and spam on Wikipedia, but being accused of edit-warring for doing so leaves me feeling that this is a "damned if you do, damned if you don't" situation. Zazpot (talk) 15:59, 15 June 2018 (UTC)
There are many instances where resolving a problem like this one is not easy. All experienced editors have dealt with it. It may be frustrating, but you simply can't edit-war regardless. In this case, you should try to work it out directly with the editor. If they don't respond or it fails, take them to ANI, partly for the spam and partly for the lack of cooperation by the other editor.--Bbb23 (talk) 18:39, 15 June 2018 (UTC)
@Bbb23: as I already stated, I did not "edit war regardless"; IMO, I did not edit-war at all, merely reverted obvious spam. As I also already stated, I did "try to work it out directly with the editor". So, neither of those two pieces of advice help me to learn, nor do they answer the question that I asked you.
You say that I could have taken the issue to ANI... Well, OK, maybe next time I encounter something like this I will do that, as you say, after two reverts. But I suspect that I might not be taken seriously on so little evidence. SPI seemed like a better first port of call, because the IP socking looked obvious and a checkuser could have confirmed it: this would have given me solid evidence to bring to ANI afterwards if necessary. But as I say, you dismissed my SPI request.
In a nutshell, I do feel you rather shot the messenger here, by slapping me with that template. For the reasons I gave above, the template seems inappropriate here, and moreover it feels deeply unappreciative given the effort I put into addressing that spammer. I would remain grateful if you would withdraw it. Zazpot (talk) 20:55, 17 June 2018 (UTC)

A page you started (Foldering) has been reviewed!

Thanks for creating Foldering, Zazpot!

Wikipedia editor Nick Moyes just reviewed your page, and wrote this note for you:

Please fix the references. Bare urls aren't desirable in new articles as they are prone to link rot. As this is a very new term, I'm sure you'd agree this is worthy of addressing. Expand it a bit more and it could make a good WP:DYK.

To reply, leave a comment on Nick Moyes's talk page.

Learn more about page curation.

Nick Moyes (talk) 19:15, 17 June 2018 (UTC)

@Nick Moyes: see User:Zazpot#Why_do_I_use_bare_URLs?. Thanks, Zazpot (talk) 21:03, 17 June 2018 (UTC)
@Zazpot: Well, I regard that rationale simply as lazy, sloppy and somewhat arrogant on your part. You clearly expect others to trot along behind you, tidying up after you because you can't be bothered to do it yourself. No, I'm sorry, despite the fact that some other user may well sort out the weaknesses in your edits, that's a poor attitude in my book from an experienced editor, and I hope you will see sense and have more pride in the pages you create in future. Thanks, Nick Moyes (talk) 22:10, 17 June 2018 (UTC)
@Nick Moyes: here is an earlier formulation of my rationale. Perhaps you will find it more satisfying. It, too, is a reasoned argument. Casting aspersions ("lazy", "sloppy", "somewhat arrogant") is not, and in my book is much more worthy of being called "a poor attitude ... from an experienced editor". If you still disagree, then let's just leave it here. Regards, Zazpot (talk) 22:54, 17 June 2018 (UTC)
@Zazpot: Thank you. I think we'll just leave it there. Regards, Nick Moyes (talk) 23:07, 17 June 2018 (UTC)

Wikidata weekly summary #317

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Wikibase meetup on June 17-19 in Berlin
    • Past: Wikidata Lab VIII in São Paulo
      • Images, metadata, and gamification of Wikidata by Magnus Manske (video, slides)
      • Discovering and modeling knowledge in Wikidata by Andrew Lih (video, slides)
  • Development
    • Prototype for mobile termbox
    • Moving away from wb_terms table
    • Continued work on making WikibaseLexeme compatible with Wikibase clients (T195615)
    • Error handling and usability for entering lemmas was improved (T196342, T197453)
    • Lexemes no longer randomly pop up in rdf dumps (T194627)

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.


Wikidata weekly summary #318

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Include Wikibase dispatch lag in API "maxlag" enforcing (phab:T194950)
    • Run full constraint check when saving a statement (phab:T194760)
    • Show map on items to preview coordinates (phab:T184933)
    • Implement property scope constraint to say if a property should be used on main snak qualifiers or references (phab:T197473)
    • Investigate on replacements for some parts of wb_terms table (phab:T197161)
    • Fix a UI glitch on Lexeme editing interface (phab:T195298)
    • Add names and descriptions for Lexeme, Form and Sense datatypes on Special:ListDatatypes (phab:T189935)
    • Display a warning message and prevent entering of lemmas with the same spelling variant (phab:T195372)
    • Work on showing description in Item selector in Special:NewLexeme (phab:T165597)

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.


Facto Post – Issue 13 – 29 May 2018

Facto Post – Issue 13 – 29 May 2018
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.
Respecting MEDRS

Facto Post enters its second year, with a Cambridge Blue (OK, Aquamarine) background, a new logo, but no Cambridge blues. On-topic for the ScienceSource project is a project page here. It contains some case studies on how the WP:MEDRS guideline, for the referencing of articles at all related to human health, is applied in typical discussions.

Close to home also, a template, called {{medrs}} for short, is used to express dissatisfaction with particular references. Technology can help with patrolling, and this Petscan query finds over 450 articles where there is at least one use of the template. Of course the template is merely suggesting there is a possible issue with the reliability of a reference. Deciding the truth of the allegation is another matter.

This maintenance issue is one example of where ScienceSource aims to help. Where the reference is to a scientific paper, its type of algorithm could give a pass/fail opinion on such references. It could assist patrollers of medical articles, therefore, with the templated references and more generally. There may be more to proper referencing than that, indeed: context, quite what the statement supported by the reference expresses, prominence and weight. For that kind of consideration, case studies can help. But an algorithm might help to clear the backlog.

Evidence pyramid leading up to clinical guidelines, from WP:MEDRS
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) 18:19, 29 June 2018 (UTC)

Wikidata weekly summary #319

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Celtic Knot Conference, dedicated to Wikimedia projects and minority languages, July 5-6, in Aberystwyth (Wales). A lot of Wikidata workshops will take place during this event.
  • Development
    • Working on prefilling spelling variant of new form representation (phab:T195708)
    • Start breaking down stories in order to implement Senses
    • Finding a better solution for dewiki's Modul:Wikidata isParent (phab:T179155)
    • Adding support for linking to a particular statement (phab:T169224)
    • Implement property scope constraint (phab:T197473)
    • Track maxlag for wikidata on grafana dashboard (phab:T196868)

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.


Wikidata weekly summary #320

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Making progress towards being able to query for constraint violations in the query service
    • Included the dispatch lag in the maxlag parameter to give better feedback to tools and bots if they can edit at the moment (phab:T194950)
    • Added support for linking to a particular statement (not just a statement group) (phab:T169224)
    • Set up L as an alias for the Lexeme namespace (phab:T195493)
    • Worked on making lexical category, language and grammatical feature show up on WhatLinksHere (phab:T195302)
    • Worked on Persistent IDs for Senses (phab:T198033)
    • Improve placeholder text for Lexeme language and lexical category field on Special:NewLexeme (phab:T195439)
    • Show description on the item selector on Special:NewLexeme (phab:T165597)
    • Add "mis" language code to the list of language code options on Special:NewLexeme (phab:T194771)

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.


Wikidata weekly summary #321

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Worked on persistent storage for Senses on Lexemes - started by giving them a stable ID (phabricator:T198033)
    • Adding "mis" language code to the list of language code options on Special:NewLexeme (phabricator:T194771)
    • Made the Items used for Language, Lexical Category and Grammatical Feature show up on Special:WhatLinksHere (phabricator:T195302)
    • When adding a new Form the spelling variant is now filled out automatically based on the Lemma's (phabricator:195708)

Facto Post – Issue 14 – 21 July 2018

Facto Post – Issue 14 – 21 July 2018
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.
Plugging the gaps – Wikimania report

Officially it is "bridging the gaps in knowledge", with Wikimania 2018 in Cape Town paying tribute to the southern African concept of ubuntu to implement it. Besides face-to-face interactions, Wikimedians do need their power sources.

Hackathon mentoring table wiring

Facto Post interviewed Jdforrester, who has attended every Wikimania, and now works as Senior Product Manager for the Wikimedia Foundation. His take on tackling the gaps in the Wikimedia movement is that "if we were an army, we could march in a column and close up all the gaps". In his view though, that is a faulty metaphor, and it leads to a completely false misunderstanding of the movement, its diversity and different aspirations, and the nature of the work as "fighting" to be done in the open sector. There are many fronts, and as an eventualist he feels the gaps experienced both by editors and by users of Wikimedia content are inevitable. He would like to see a greater emphasis on reuse of content, not simply its volume.

If that may not sound like radicalism, the Decolonizing the Internet conference here organized jointly with Whose Knowledge? can redress the picture. It comes with the claim to be "the first ever conference about centering marginalized knowledge online".

Plugbar buildup at the Hackathon
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) 06:10, 21 July 2018 (UTC)

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Zazpot/Archive_6&oldid=1145684786"