Refinements that could be made:
- Only show the optional date if needed
- Change program labels according to the selected discipline
- A more experimented js dev could probably improve the code a lot.
Refinements that could be made:
It is a blocking issue in so far that an item can only link to one page on a given wiki. If several languages are covered on one wiki then we also usually have the case that we have two pages for one concept on that wiki that would both need to be linked in the same item.
I just ran into a problem with the URL shortener: my query was simply too long to be crunched by TinyURL (and most other URL shorteners for that matter, the only one I tried that worked was cpc.cx)
Do we have an estimate of the number of automatic merge per month and how many are bad (i.e "reverted"/links split again in separate items)?
The question of "making it harder for newbies" could also be solved through T174345 (i.e. a proper user right, not a "gadget-not-by-default" hack.)
It would be great if the script allowed to create a new item even if there are (irrelevant) results.
I added the tag because it is a function in the API on the projects (for example here), but if I was wrong, please feel free to remove it.
I don't think there is a specific page for merge requests, but I think the requests for deletions page can be extended to that (deletions requests with "duplicate" as a reason are basically merge requests anyway).
Given how many newcomers use the ~~~~ to sign in Flow messages, some sort of notice would be great.
Done. Thank you for the tip, I didn't know we had a Wikimedia CDN.
So this would be a totally new namespace? Like [[U123456789]] instead of [[Q123456789]]?
I totally disagree with this proposal. How long before these items would be used to doxx the real identity of users, and/or their religion/sexual orientation?
This is the one featured in the logoat: https://thenounproject.com/search/?q=goat&i=853142 (it should be green though)
"Francophone welcome corner" is there, but really it's more like "Brittophone welcome corner".
It doesn't appear to be correct Windows-1252 either.
Anybody interested is free to follow https://translatewiki.net/wiki/Translating:New_project and give this a shot.
The first step is for Phabricator to give translatewiki.net staff push access to their repository.
I also think this task should have a higher priority, especially now that an important community page (https://www.wikidata.org/wiki/Wikidata:Bistro) uses it. Right now, the message sent by this "Lowest" priority is that the only language that matters in the community is English.
Instead of a URL shortener, wouldn't a Quarry-like (quarry.wmflabs.org) interface a solution? It would permit to save queries, share them, even fix typos in them without changing the public URL.
"Should users have a limit? " → What problem would it solve, exactly?
@Ash_Crow Can you please check again? It seems ok for me now. Maybe it wasn't deployed yet when you checked.
" The link behind the icon is clickable now."
Nope, it's not.
@Urbanecm : the discussion is currently running at https://meta.wikimedia.org/wiki/Meta:Babel#Kartographer_extension
Same problem with French. I tried to search for wd:île (island) and it didn't work.
Hi, I was thinking: would it be possible to have a distinct 'super-history' page that includes the changes made to all transcluded content (templates, data from WD, transcluded articles, images (both local and from Commons), without cluttering the normal history page?
I do not think this is a good idea to log changes made on Wikidata in the history of the articles themselves.