One question could be wow we can get translated placename labels from Wikidata on Kartographer. Currently, it uses only OSM translations and in perfect world it could use Wikidata for failback if there is no translation in OSM.

• https://phabricator.wikimedia.org/T305609

Would it be possible to do a unified "UI" for both where HTML would be the same and the difference would be in the CSS and in javascript?

Added map tiles to the checklist as maptiles are missing for sms and sun languages. Least smn should have maptiles as there is https://smn.wikipedia.org so there should be full language support.

Currently works for me in toolforge db. Thanks to everybody involved for fixing this.

I think that it is useful is finnish wikipedia and 99% of the the times the feature is usefull. Last 1% is that there is vandalism which would be reverted / hidden if it would be visible in wikitext. Biggest useases are that users can get some hint what was deleted so admins don't need to tell it (ie. it is good for transparency). In admin point of vier it is also useful for finding deleted pages afterwards if you need undelete it.

I see no reason why a tool couldn't use a tool-specific account for

queries like that.

@Gehel: WCQS is not currently accessible from tools and WCQS federation is currently one way only: Wikidata -> WCQS but WCQS -> Wikidata is not possible.

Just to note, there is other bot code/frameworks than the pywikibot too. As the mainline pywikibot is tied to being scriptable bot by the login handling then the all other use cases are using custom login routines. Either on based on pywikibot, but most likely to something else. My point here is that the "pip install -U pywikibot" works only on limited number of use cases.

There is now enabled by default CSS gadget in Wikimedia Commons for making Upload Wizard more mobile friendly.

• https://commons.wikimedia.org/wiki/MediaWiki:Gadget-uploadWizardMobile.css

How you are planning to handle the use federated queries? Afaik tool creators will just rout the queries through Wikidata or some other endpoint which is without authentication? In other hand if you are blocking federated queries from Wikidata in example, then the service just is bad.

Just FYI, it seems that there is still links to Special:ReviewedVersions in UI in production per discussion in fiwiki.

@JeanFred I didn't create new ticket yet, but would it be possible to update the Mirador and Universal viewer to latest versions? Current ones are old and least Mirador latest has lot better mobile support now. Also latest Tify viewer would be nice addition for the viewers.

in Wikimania Hackathon we started to do IIIF support for viewing photos. Sirukisu code http 404 file not found handler which will download automatically missing images from Wikimedia Commons and converting them to pyramid TIFFS, Zache converted photos already in Ajapaik to pyramid TIFF-format and wrote basic IIIF presentation API descriptions for files. Puik participated in planning

And just for documenting. In Wikimedia Hackathon 2021 in MAy this upload script was done and the geojson albums were documented after the hackathon

• https://github.com/zache-fi/FinnaUploadBot/blob/main/upload_mfa_to_commons.py
• https://github.com/Ajapaik/ajapaik_flutter_app/wiki/Album-documentation

Ok, Finally solved this and I was upload the file. I was puzzling why the Create page which is required for uploading files was missing from granted rights when I was logging in even when it was defined in consumer creation. I finally were able to figure out that the "createeditmovepage was missing from the requested Scope when i logged in.

Yes, thank you. It would work prefectly

Next try. It seems (T245475) that A checkbox is visible: "Allow consumer to specify a callback in requests and use "callback" URL above as a required prefix." doesnt work so I changed the callback url to be literally same that it is in redirect url.

The first one didn't work. I think that the problem is that the callback url was incorrect and it was not trivial to change it in application side (i need to update codebase) so made another provider application with correct callback url I hope.

@Ederporto did you get this working? My first guess would be that you should check that Oauth-login works (url below) and after this is confirmed then i would try to solve upload. I was stuck with Oauth because I tried to do Oauth1 login with Oauth2 tokens and login failed because that. This could be your error too.

Multichill's SDC editing with pywikibot code as a reference

• https://github.com/multichill/toollabs/blob/master/bot/commons/depicts_monuments.py

Same method as a blog post

• https://byabbe.se/2020/09/15/writing-structured-data-on-commons-with-python

This affects the query service which uses the formatter URL to render the URI.

I think that this will still work as an example for reading CSV/TSV row by row and updating wikidata based on values from the file.

Is it possible to behave / look like normal notifications (ie upper div box in beginning of the page) and then use CSS/Javascript to modify that for getting the low profile functionality for the wikis/user who like to have low profile ui?

Unwanted regression. CSS-classes for the lines in the history/recentchanges etc lists which will tell if the revision is reviewed or not is gone. An example light blue lines in this screenshot for the edits reviewed by Opa.

Given the context above, it may be worth considering whether to focus this change to focus only on newcomers. In this way, the more experienced editors would still get opportunities to contribute in a way that better suits them.

Hmm, If I understand this correctly the "sighted" (stable version) is enough for Google News and it doesn't use quality tier for aggregating news. It woud be nice to confirm somehow.

Another example case from finnish Wikipedia

• https://fi.wikipedia.org/w/index.php?title=John_Jairo_Arias_Tasc%C3%B3n_%27Pinina%27&oldid=19654768

In T277883#6932372, @Ladsgroup wrote:

So another point to clean up is rights, we have these rights:

• "validate",
  • God like, full review right on everything. Can be dropped once we removed tiers and dimensions.

In Finnish Wikipedia, they are used so that there is some set of articles (say featured articles) which edits are checked as normally for vandalism and then there is also the slower round where users are doing time to time more deeply checking what is changed after last quality revision.

I understand. But the choice here is not between "having tiers" and "not having tiers". It's between "not having tiers" and "undeploying flaggedrevs". The code under the hood is a big mess. My suggestion is to remove the tiers (and keep levels for now) and if needed:

• Either implemented later in a better way inside flagged revs
• or have a new small self-contained extension to handle that. I know there was some efforts in WMF to write something to allow users mark a revision/page in a structured way but I think this is out of scope of this extension. the extension job is about "pending changes" and should only do that (and do it well)

Ah, you mean that if the user can still select "well-sourced" when the user is reviewing then it is good enough(?) I try to explain again what I tried to say earlier.

Hmm, it seems that seeing the info requires suitable user group. However here is screenshot

Not sure if I was able to follow you on how you defined "tiers". In fiwiki there is in user interface

• stable = alias for any review
• checked = levels 1, 2
• quality = level 3

Right. You know that least fiwiki is using more than two levels.... I may not even be against axing the levels, but I was thinking that I was in some level to following what is happening with FlaggedRevs and it would be nice to even to hear or participate to the discussion where you are deciding things.

@Jdforrester-WMF if we are keeping levels inside single dimension it would be more useful to keep quality and pristine and link them together in documentation.

"SimpleUI" will currently break the fiwikis page layout as it will collide with some templates. "Non-simple UI" aka basic text box works well when the number of the pages where it is visible is low (like it is in fiwiki) and it will actually notify users that there is new changes to users to check.

I would keep the wording same as in documentation. Ie. "Flagged revisions will no longer have multiple tags like "accuracy", "tone" or "depth" and will only have single tag"....

Bug confirmed with Windows 7 and chrome 89.0.4389.82. It seems that if the link is in the bottom line then it is not activated when mouse cursor is hovered over the link. Link cannot be clicked either.

If somebody is fast enough, then there is still time to drop application to this years software/research project grants. Deadline is today 16.3.2021.

@Ladsgroup just some notes:

This is summary by Kyykaarme of the reasons why the community wants to disable the invitations to translate articles.

@Jdforrester-WMF Why WMF is not able to fund developing FlaggedRevs (or replacement)?

I copied the acceptance criteria from the older ticket as these are merged. Feel free to edit them, but if you are dropping the "if the local wiki configuration allows to, users can publish translations anonymously" then please give some well-thought rationale for it as it feels like a point where there is a collision between what user communities think and technical design.

Root cause for the problem could be race condition when configuration values are merged (Warning: this was not never validated)

• https://phabricator.wikimedia.org/T237191#5910406

In T121797#1980980, @Bawolff wrote:

Not sure if we would be able to do that kind of comparison in a SQL query (but the power of SQL keeps surprising me).

I looked into this a little while back. Usually for these types of hashes, you want to find everything within a certain hamming distance of the current hash, which is very difficult to index for in sql.

Very low tech workaround for decreacing the current load could be generating unsanitized id / timestamp pair tables where user could query possible min/max values for the primary ids. This could be even compacted so that it would contain only one pair per day.

Yes, the connection was started after your "Tue, Feb 2, 3:53 PM" comment.

Thanks for fixing. I was able to log in but connection (or timeouts) is still little bit shaky.

Seems to be down

Sure, in July 2019 when i wrote the comments the rev_actor fields werent documented

• https://www.mediawiki.org/w/index.php?title=Manual:Revision_table&oldid=3266294

I just tested Phash (ImageHash.py :s implementation) and for detecting duplicates it would be huge improvement compared to SHA1 even if it would be used for testing the exact matches which would be fast using SQL. There would be false negatives though.

Ok, thanks. By default pythons ImageHash librarys pHash length is 64 bit and even if I change it longer it doesn't generate same hashes. So it is confirmed that its pHash and JImageHash PerceptiveHash doesn't generate same hashes.

Hi, is it possible to get some phash hash values for pictures in Wikimedia Commons? I would like to see if the JImageHash would generate compatible hash values with Pythons Imagehash, but I expect that it doesn't do that.

• https://github.com/JohannesBuchner/imagehash

Use case example

In T215858#6744188, @Jhernandez wrote:

In T215858#6742843, @Zache wrote:

Is it possible to get information how big the commons/wikidata tables are on the disk? (ie. which are the problematic tables in the replication point of view)

The tables individually I'm not sure. The databases for sure. What would that info help with?