This is an archive of past discussions with User:Slashme. 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.
Upcoming: WikiArabia, in Cairo, Egypt, on 23-25 October. They're looking for a volunteer to give a Wikidata workshop. Please contact them if you're interested!
The Gene Wiki: Using Wikipedia and Wikidata to organize biomedical knowledge August Wikimedia Research Showcase (second half), presented by Andrew Su, about how GeneWiki is using Wikidata. Video on YouTube
Citation.js: Endpoint on RunKit shows a demo REST API to convert Wikidata entries into BibTeX, Bib.TXT, citations, and CSL-JSON.
The organization team is still looking for sponsors to support the event and provide even more awesome stuff to the attendees. If your company can support the WikidataCon, please get in touch with Lydia.
Seeing the enthusiasm of the community for the WikidataCon, we raised our attendees limit from 150 to 200 persons. The last tickets will be released on September 1st. People who registered on the waitlist will be notified when a ticket is available.
The program committee is currently reviewing and organizing the submissions. We will contact the speakers soon, and publish the program in the beginning of September (around 6th).
We're looking for a keynote speaker who could bring an external point of view on ontologies. If you know interesting people, feel free to help
Looking into not showing language fallback hints for dialects to make the UI less cluttered for them and make it less necessary to enter labels and descriptions for them (phabricator:T174318)
Wrapping up our experiments with the new front-end technologies
Open Library, the biggest resource of freely-licensed books, now links to Wikidata (through Reasonator) and to VIAF (example here; see "Wikidata" in the right-hand column).
With 200 attendees, the WikidataCon is now complete. Thanks all for your enthusiasm \o/ If you registered on the waitlist or submitted a talk, check your mailbox for more information.
The WikidataCon program will be released this week, and we will call for volunteers soon
Looked into all the things necessary to make it possible to store forms and senses on Lexeme pages.
Worked more on caching constraints checks results which is needed to enable constraints checks for all logged-in users (phabricator:T173696)
Making progress on checking constraints also on qualifiers and references (phabricator:T168532)
Removed language fallback hints for dialects to make the UI less cluttered for them and make it less necessary to enter labels and descriptions for them (phabricator:T174318)
Fixed an issue that links to an item were not showing the label when it pointed to a redirect (phabricator:T96553)
Unrecognized input in entity selectors will be highlighted in red (phabricator:T170531)
Added an additional normalization for page titles when linking pages on Wiktionary via Cognate (phabricator:T172987)
The API will not only output the hashes for qualifier snaks, but also for main snaks as well as references snaks (phabricator:T174692). Note that hashes (other than IDs) are not meant to be stable identifiers, and should not be stored for a longer time.
Snak hashes will also appear as part of CSS classes in entity pages (phabricator:T171725)
I apologize, I really don't know what I'm doing on here yet. I was just testing things out and I keep getting myself deleted. :( Is this where I am supposed to leave messages? Krystyana at Scilligence (talk) 20:48, 7 September 2017 (UTC)Krystyana at Scilligence
There are three main ways to contact a user on this site:
You can link to their name, so for example you can alert me by typing [[User:Slashme]] into a comment on a talk page.
You can leave a message on their talk page, like you did now.
You can use the "email this user" link in the left-hand menu if for some reason you don't think they'll get messages on Wikipedia or if you want to communicate privately.
So, thanks for making contact. I know that Wikipedia can be a bit confusing, so I'd like to help you make some edits that actually stick around and don't get deleted. If you tell me about a topic that you find interesting, I can point you at an article in that general area which needs help. Then when you make the edit, let me know and I'll check it out and give you feedback. Or otherwise, if you have a non work-related topic that you feel is badly represented or not represented at all on Wikipedia, I can help you to draft an article about it.
Another option is to create a diagram or illustration for an article that needs more than just words. I've done quite a bit of that, but I'm just an amateur, unlike you :-] --Slashme (talk) 21:01, 7 September 2017 (UTC)
You replaced the distinct content of the article and redirected it to Cannabis in South Africa because you believed it to be a wrongful fork. Please note that the Daggafarianism article is a focused on the evolution of the contemporary cannabis culture of South Africa in relation to the history of cannabis laws and racism in South Africa. You had not acted within the guidelines of Wikipedia when you performed this action. You made a claim and gave no notice before removing content. However you are also part of the discussion to remove the Afrikaans version. Why delete the English version if you feel that you acted appropriately why not also remove the Afrikaans version. As a seasoned editor and Founder of the Afrikaans Wikipedia you know beter and should know its not ok to remove content especially where it is a distinct article not in violation of fork guidelines. If you wanted to contend the notability of a neologism then the appropriate action is to nominate the page for deletion. I cannot let this action go without review by a steward who does not have a conflict of interest eg. already participating in nominations for deletion of the same article in another language.
Please find this as my notice of intent to file a complaint. I welcome your reply but feel an impasse has been reached.
You might have mistaken me for someone else. I'm not a founder of the Afrikaans Wikipedia. I've only recently started regularly editing there.
I still think that the content that you have developed under the Daggafari article could be dealt with in a section of the Cannabis in South Africa article. You say that a deletion discussion would be more suitable than simply creating a redirect, so I'll do that and link you in.
You say that you would like to file a complaint against me. There are a number of levels of dispute resolution open to you. I would welcome a third opinion or a discussion at the DRN, so please do so if you think it would be valuable. --Slashme (talk) 06:52, 9 September 2017 (UTC)
(talk page stalker) Hi Mickey, Here is the message I sent to you on FB when you were having the same problem on the Afrikaans Wikipedia, the contents of which I feel apply here too. Ok...so just a quick scan over the lead and a few things come to mind immediately. Your sources are all either self published or from FB and don't constitute reliable sources. While you may have 35 references, there are only 14 available to most people. As far as the article itself goes, a lot of its content could be in the "Dagga" article rather as the content has little to do with the actual term "daggafarian/daggafari" and more to do with the history of weed in SA. In fact, very little below the lead makes any mention of the term or its coining. I would be inclined to rather create an article called "Die geskiedenus van Dagga in SA". That way it would be more encyclopedic which would satisfy the editors who are calling you out the notability issue (this would be my main issue too). I'm not sure the term is notable enough (yet) to warrant inclusion into an encyclopedia (as a stand-alone article). You need several reliable sources that demonstrate its prolific use in daily culture and I'm not sure you will. There are other MOS (manual of style issues, but those can be resolved. Much like grammar and punctuation). It can be tough getting started on Wikipedia especially with a topic like dagga, maybe more so on the Afrikaans one. While I fully support legalisation in SA, the quality of Wikipedia standards for articles remains paramount to me and unfortunately would support this articles deletion as it stands. Robvanvee09:04, 9 September 2017 (UTC)
Please review the article it focuses on the evolution of the contemporary cannabis culture of South Africa in relation to the history of dagga laws and racism. You guys keep confusing the guidelines for Facebook references. It doens't state that Facebook references are NEVER allowed, because there are valid reason to include Facebook references where it doesn't refer to scientific facts or self-research neither of which is implied by the references. Although I have a COI doesn't mean I cannot contribute to the article. The self published sources are the main source that describe the definition of the word. How can only 14 references be available to most? All references exist and are available to all. If you support the deletion please raise your nomination on the nomination for delete. That the history content is unrelated is just your opinion when it is the history, the law and racism that shapes the current dagga culture. And this history is required to understand this evolution. As the creator of the Dagga Couple pages you are suppose to know how many times they have used this word. Please provide the references that are available. This is valid POV fork and shouldn't be lumped in the atrociously structured article Cannabis in South Africa which seems to be a list of cannabis related topics in South Africa and not a proper article. The coining of the term is addressed in the introduction that leads up to the revolution and evolution of the dagga culture that starts with the history. Its not completed but although it also stands a full article in it's current state. A term doesn't have to be used daily to prove notable. Notability doesn't expire. Sorry but it seems your opinion is not really based on Wikipedia guidelines. Further the use of self published sources as used in the article do not violate the Wikipedia guidelines, "Self-published and questionable sources may be used as sources of information about themselves"--Mickey ☠ Dangerez12:39, 9 September 2017 (UTC)
My bad, " founder member and former director of Wikimedia South Africa" - Slashme
Hi, User:K175 has blocked me and left me without the ability to edit my own talkpage on af.wiki. Please notify the community about the RfC I've opened on meta. Thank you. --Nazeer (talk) 19:49, 9 September 2017 (UTC)
The program of the WikidataCon is now published on-wiki. You will find there a lot of different formats, topics and speakers, during the two days of the conference.
The event is now complete, no more tickets available. The last tickets have been attributed to the first persons who registered on the waitlist. If some more seats get free because another attendee cancels participation, the next person on the waitlist will be informed.
Hello Slashme, thank you for your efforts reviewing new pages!
Backlog update:
The new page backlog is currently at 14304 pages. We have worked hard to decrease from over 22,000, but more hard work is needed! Please consider reviewing even just a few pages a day.
Currently there are 532 pages in the backlog that were created by non-autoconfirmed users before WP:ACTRIAL. The NPP project is undertaking a drive to clear these pages from the backlog before they hit the 90 day Google index point. Please consider reviewing a few today!
Technology update:
The Wikimedia Foundation is currently working on creating a new filter for page curation that will allow new page patrollers to filter by extended confirmed status. For more information see: T175225
General project update:
On 14 September 2017 the English Wikipedia began the autoconfirmed article creation trial. For a six month period, creation of articles in the mainspace of the English Wikipedia will be restricted to users with autoconfirmed status. New users who attempt article creation will now be redirected to a newly designed landing page.
Before clicking on a reference or external link while reviewing a page, please be careful that the site looks trustworthy. If you have a question about the safety of clicking on a link, it is better not to click on it.
To keep up with the latest conversation on New Pages Patrol or to ask questions, you can go to Wikipedia talk:New pages patrol/Reviewers and add it to your watchlist.
Rolled out more fine-grained usage tracking on Greek Wikipedia. This will lead to less irrelevant changes showing up in watchlist and recent changes on those projects. We're testing this on Greek Wikipedia to see if the solution we have scales before rolling it out further. (phabricator:T151717)
Adding an API module to copy a statement from one item to another (phabricator:T55619)
Working more on checking constraints also on qualifiers and references (phabricator:T168532)
Added support for the Creator namespace to the constraints check for Commons links (phabricator:T176062)
Found a post you made on Reddit - what you do there is awesome, and I bet Commons is super appreciative, but on behalf of the English Wikipedia - thank you! -- There'sNoTime(to explain)16:39, 26 September 2017 (UTC)
Hey! Like pretty much all Wikipedian politics geeks, I'm a big fan of your parliament diagram maker. Of course, it's possible to alter the number of seats on each wing row when creating a Westminster-style diagram, but (as far as I know) not on the arch-style diagram. However, recently I saw a user who had altered the number of rows in a 100-seat arch diagram, from the automatic 6, to 5. It would be useful to know how to do that, but since I haven't seen any buttons or switches on the site, I thought I'd just have to ask the creator himself. Is it a built-in feature that I just haven't found, or do you think the user I mentioned did it manually? Thank you! :) — Μαρκος Δ22:48, 28 September 2017 (UTC)
Hi @Μαρκος Δ: I stared out by doing some trigonometry, and I calculated beforehand how many rows I need to fit in a given number of seats - so 1 row can take up to 3 seats; two rows up to 15; 3 up to 33; etc. I see that in my code, I had written:
Each row can contain pi/(2asin(2/(3n+4i-2))) spots, where n is the number of rows and i is the number of the current row.
Anyway, I then just look up how many seats I have to lay out, and run the equations to calculate their locations. It's as simple as that. If I have less spots than I have room for in the diagram (e.g. I have 30 spots and there is room for 33 in a 3-row diagram), I space them out more widely.
My calculation says that 5 rows can take 95 seats, so if someone really did lay out 100 seats in a 5-row diagram, I'm guessing that they probably put 5 seats at the end by hand? --Slashme (talk) 23:07, 28 September 2017 (UTC)
Thanks for the reply! Here is the diagram in question, by the way. The user who did it has now told me that he did it manually (by first making a 129-seat diagram, then removing the sixth and outermost row, leaving only 100 from the five inner ones). I think both his and my reasoning for trying to change the number of rows is related to that wider spacing you mentioned; in some diagrams (mostly those with few total seats), the gaps become very wide. A good example of that would be a 35-seat diagram. While a 33-seat one, on the other hand, is much smoother-looking and less scattered, in a sense. But of course, as you explained with your formula, there is after all a good and logical reason for wider spacing in some diagrams. Thanks again :) — Μαρκος Δ13:34, 29 September 2017 (UTC)
A barnstar for you!
The Real Life Barnstar
Thanks for getting me back in to Wikipedia! I saw your r/askreddit reply and decided to become active on Wikipedia again. Thanks again! Llacb47 (talk) 19:23, 29 September 2017 (UTC)
@Llacb47: Wow, that's awesome!! Thank you for this message - it means more to me than any Reddit gold ever could. If anyone is mean to you on here, or you feel like Wikipedia becomes boring, or you don't know what to edit, drop me a note and I'll give you a boost. --Slashme (talk) 19:34, 29 September 2017 (UTC)
Wikidata weekly summary #280
Here's your quick overview of what has been happening around Wikidata over the last week.
Added a css class to values that link to redirects so they can more easily be identified by editors who want that for maintenance work (phabricator:T70567) Thanks Matej!
Finishing touches on adding full URIs for external identifiers to our RDF export so we're good citizens of the semantic web (phabricator:T121274)
Added a new mw.wikibase.getAllStatements Lua function in addition to the existing getBestStatements, that returns all statements regardless of their rank (phabricator:T176124)
Looking into an issue where unwanted email notifications are being sent (phabricator:T174794)
Upcoming: WikidataCon, Berlin, 28-29 October (sold out)
We will have two exciting keynotes. The first keynote speaker is Fabian M. Suchanek, professor at Télécom Paris Tech University, working on the knowledge base YAGO. The second keynote speaker is Michael Kreil, datajournalist working on the project Data Sciences and Stories.
Please volunteer for some tasks at the conference if you are attending.
Breaking change: "wb_entity_per_page" table will not be updated and replicated on ToolLabs anymore
A mw.wikibase.getLabelByLang Lua function will be added (phabricator:T173262)
The mw.wikibase.sitelink Lua function will accept a second parameter with the global identifier of a wiki (e.g. "enwiki") to link to (phabricator:T142903)
Had to temporarily turn off showing Wikidata's changes on Commons and Russian Wikipedia because of database issues. We're working on turning it back on.
Continued work on persistently storing edits to Forms on Lexemes
Finishing work on checking constraints on qualifiers and references with the constraint checks gadget
Fixed a bug where notification emails for Wikidata changes were sent when they shouldn't have been (phabricator:T174794)
Full URIs for external identifiers will soon be in the RDF export (phabricator:T121274)
Monthly Tasks
Add labels, in your own language(s), for the new properties listed above.
Is it possible somehow to use the legend template you got out of "tools.wmflabs.org/parliamentdiagram" and convert it to a parliament diagram.
I ask this because i made pretty large parliament diagram some time ago but it didn't work, the archdiagram didn't generate/there was some error but i could copy the legend template. And i am now wondering if there is some way to take the legend template and convert into a diagram.
So for example if you have "legend|#AD4308|Party 1: 20 seats" "legend|#F13D4C|Party 2: 80 seats"(replace " with the curly brackets) could you somehow make this into a parliament diagram without putting in all the values manually?
Hi Carlpm01, I could write a quick-and-dirty interface that allows that. To generate a diagram, at the moment, it sends a POST request to the python script with the form "Party 1, 20, #AD4308; Party 2, 80, #F13D4C". Basically, I could create a page which contains a Javascript script that grabs the template code and calls the diagram script with the corresponding request string. I just have to think through the security implications of allowing a user to provide an arbitrary string to my python script. I mean, I think the user could already do that with a specially crafted website, but it's been a while since I looked at the code. I'll give this some thought over the weekend and let you know if I decide to implement it. --Slashme (talk) 17:05, 16 October 2017 (UTC)
Wikidata weekly summary #282
Wikidata weekly summary #282
Here's your quick overview of what has been happening around Wikidata over the last week.
Upcoming: WikidataCon, Berlin, 28-29 October (sold out)
If you organize a local event for the Wikidata birthday, feel free to add it on the events page and the birthday page
A blog post describing Textes d'affiches, a tool using Wikidata to show movies and the works they are adapted from, developed during a hackathon at the national French library (by Shonagon, in French)
Hello Slashme, thank you for your efforts reviewing new pages!
Backlog update:
The new page backlog is currently at 12,878 pages. We have worked hard to decrease from over 22,000, but more hard work is needed! Please consider reviewing even just a few pages a day.
We have successfully cleared the backlog of pages created by non-confirmed accounts before ACTRIAL. Thank you to everyone who participated in that drive.
Technology update:
Primefac has created a script that will assist in requesting revision deletion for copyright violations that are often found in new pages. For more information see User:Primefac/revdel.
General project update:
The Article Wizard has been updated and simplified to match the layout style of the new user landing page. If you have not yet seen it, take a look.
To keep up with the latest conversation on New Pages Patrol or to ask questions, you can go to Wikipedia talk:New pages patrol/Reviewers and add it to your watchlist.
More work on checking constraints on qualifiers and references (phabricator:T168532)
Now caching constraints results to make it ready for rollout for more users
Continued work on more fine-grained usage tracking so we better know which parts of an item is used on an article on Wikipedia and the other sister projects
Improved the way Wikidata changes are shown in watchlist and recent changes on Wikipedia and Co so they are more in-line with the other changes (phabricator:T48329, phabricator:T50684) Thanks Matej!
Upcoming : Wikidata and Wiki Loves Monuments editathon in Berlin, 24-26 November (in German). We're looking for trainers to explain the basic use of QuickStatements, Open Refine and Mix'n'Match. If you want to join, please contact MB-one
Wikidata's birthday
The fifth anniversary of Wikidata was celebrated, as every year, with a lot of presents, events and stories. You can find an overview on the birthday page.
inventaire.io CC0 Wikidata-ready NDJSON and TTL dumps are now accessible at dumps.inventaire.io
You can now move claims to new items with moveClaim.js. You can do so by typing "new".
Prefix search on Wikidata (wbsearchentities API) now is using ElasticSearch as backend. This should improve search quality and also is more flexible and tunable.
If you want to review what happened during the WikidataCon, here is the list of all the sessions, with slides, notes and videos, when available
Release of wikidata-edit v2.0.0: brings qualifiers and references support, and a few breaking changes. See changelogs
Release of wikidata-cli v5.0.0: brings qualifiers and references support, multi-entity summary|label|description|description requests, a new `edit-item` command, and a few breaking changes. See changelogs
The Cebuano and Swedish wikis have a lot of bot-created content which is unconnected to other wiki articles. A good way to tackle that problem is by checking constraint violations for property GeoNames ID.
Latitudes, longitudes, as well as coordinate precisions have accidentally been exported to RDF as xsd:decimal, and are going to be exported as xsd:double soon (phabricator:T179228)
Continue on refactoring PropertySuggester-python for better maintainability and performance (phab:T179664)
Make AffectedPagesFinder take DESCRIPTION_USAGE into account (phab:T176417)
Accessing mw.config.get( 'wbEntity' ) will trigger a deprecation warning, gadgets and user script should use the wikibase.entityPage.entityLoaded hook instead (phabricator:T169771)
Work on caching constraint check results (phab:T179849) and indicating that they are cached (phab:T179844)
Work on JSON-LD support in the Purtle library used for exports (gerrit:379669)
Wikibase code base does not use Composer class autoloading any more (phabricator:T180067) as another step towards getting rid of our own build process and being more in line with the rest of Wikimedia
Monthly Tasks
Add labels, in your own language(s), for the new properties listed above.
Hey Slashme. Having noticed you are on the afrikaans wiki, I'm curious to know why after so many "delete" nominations the daggafarianisme article is still there? The nomination process was started in August and seems to have stagnated. Your thoughts? Robvanvee11:41, 21 November 2017 (UTC)
Hello, Slashme. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Working on fixing a regression after a change in MediaWiki core that makes edit links show up on diff pages (phabricator:T181807)
More work on persistent editing of statements on Forms of a Lexeme (specifically phabricator:T180467)
Improved size of the diff that we sent to Wikipedia and co for changes happening on Wikidata. This is one more needed step towards only showing meaningful edits in the watchlists and recent changes there. (phabricator:T113468)
Incoming:Next Structured Commons IRC office hour will be on Tuesday, February 13, 2018, at 18:00 UTC.
Past: Tech-talk about knowledge technologies, featuring Wikidata, DBpedia, and Histropedia at Jakarta Digital Valley, Jakarta, Indonesia on Dec 8, 2017. Slides are available at Slideshare link.
Structured Data on Commons: Participate in this survey to help the team understand which tools and functionalities are most important to the Commons and Wikidata communities
QuickStatements now has a CSV-like import function (under "import commands")
Hello Slashme, thank you for your efforts reviewing new pages!
Backlog update:
The new page backlog is currently at 12713 pages. Please consider reviewing even just a few pages each day! If everyone helps out, it will really put a dent in the backlog.
Currently the backlog stretches back to March and some pages in the backlog have passed the 90 day Google index point. Please consider reviewing some of them!
Outreach and Invitations:
If you know other editors with a good understanding of Wikipedia policy, invite them to join NPP by dropping the invitation template on their talk page with: {{subst:NPR invite}}. Adding more qualified reviewers will help with keeping the backlog manageable.
New Year New Page Review Drive
A backlog drive is planned for the start of the year, beginning on January 1st and running until the end of the month. Unique prizes will be given in tiers for both the total number of reviews made, as well as the longest 'streak' maintained.
Note: quality reviewing is extremely important, please do not sacrifice quality for quantity.
General project update:
ACTRIAL has resulted in a significant increase in the quality of new submissions, with noticeably fewer CSD, PROD, and BLPPROD candidates in the new page feed. However, the majority of the backlog still dates back to before ACTRIAL started, so consider reviewing articles from the middle or back of the backlog.
The NPP Browser can help you quickly find articles with topics that you prefer to review from within the backlog.
To keep up with the latest conversation on New Pages Patrol or to ask questions, you can go to Wikipedia talk:New pages patrol/Reviewers and add it to your watchlist.
Final step towards being able to store statements on Forms of a Lexeme
Disabled RDF support for Lexemes as the mapping isn't defined yet (phabricator:T182660)
Adding some more smart tracking for Lua usage so we better know which properties from an item are used on a Wikipedia article even when the whole item is loaded (phabricator:T179923)
Hello Slashme, thank you for your efforts reviewing new pages!
Announcing the NPP New Year Backlog Drive!
We have done amazing work so far in December to reduce the New Pages Feed backlog by over 3000 articles! Now is the time to capitalise on our momentum and help eliminate the backlog!
The backlog drive will begin on January 1st and run until January 29th. Prize tiers and other info can be found HERE.
Awards will be given in tiers in two categories:
The total number of reviews completed for the month.
The minimum weekly total maintained for all four weeks of the backlog drive.
NOTE: It is extremely important that we focus on quality reviewing. Despite our goal of reducing the backlog as much as possible, please do not rush while reviewing.
.png){kind=link}
