Looks like the work around was removed in https://gerrit.wikimedia.org/r/#/c/operations/mediawiki-config/+/454785/

@Lydia_Pintscher was this work around removed? If that's the case there is no point keeping this open.

Investigation done. Mostly fixed

Or just rename the current list?

FYI On the mobile version of https://matrix.org/blog/home/ WMF is listed as user of Matrix.

In T216208#4959184, @Tagishsimon wrote:

Day 2 of no Quickstatements, no Listeria, no ETA for a resumption of service ... no comment from WMF on why what is a critical service - if we're taking this whole wikidata business at all seriously - is fritzed.

In T178144#4951191, @DonTrung wrote:

I would support closing this, but the license only reads that captions are covered under the CC-0 (Zero) license, shouldn't there be a more ambiguous wording which covers all future Structured Data on Wikimedia Commons?

Seems related to https://commons.wikimedia.org/wiki/User:Multichill/Using_OpenCV_to_categorize_files (see talk page too). Good hackathon project for Prague?

I think it's clarified, see the T215468 and the related task: Structured data is CC0. Would have been much nicer if this work was done before going live. Close this one?

What is the goal of this task? Does it still serve a purpose? It seems to be something old from 2015 without a clear goal. I would just close this story as invalid.

In T213571#4897591, @AlexisJazz wrote:

@Multichill where should I propose a change? It should be changed globally, so I guess somewhere on meta?

This change needs community consensus. Tagged it as such and marked it as stalled.

Babel templates are an indication to other users and the software in what languages you can interact and at what level. For example I have es-0 on my Wikidata user page because I sometimes interact in Spanish although that takes me a lot of effort. You can read more about it at https://meta.wikimedia.org/wiki/User_language

How is this a duplicate @Jdforrester-WMF ? This task talks about api modules, not about special pages.

In T143488#4843337, @Cyberpower678 wrote:

To answer your questions, IABot will be using the wbgetentities and wbeditentity API calls on MW.

In T143488#4677644, @Cyberpower678 wrote:

I am currently at that Hackathon in Thompson 150 right now. If you care to meet me during lunch break I will be happy to work on this with you.

Can someone point me to the current network layout? Vlans, ip space in use, what's used to route/filter traffic, etc.? Knowing the current situation is usually a good first step when designing a to be situation. Does Wikimedia have an overall architecture or architecture principles? That would be good input too.

In T210139#4793562, @Lucas_Werkmeister_WMDE wrote:

Why should we do this in the proxy? Much easier to do it in the web UI IMHO.

That was a question for @Smalyshev ^

Can we just add a simple rewrite rule on the proxy/webserver for now if it encounters https://query.wikidata.org/<something>?fbclid=<click id> to rewrite it to https://query.wikidata.org/<something> ? Otherwise we'll be stuck with this bug for ages

I wonder if @Anomie has any input on this.

In T209993#4765009, @Addshore wrote:

The RDF already contains this data so maybe it can be exposed in a similar format in the wikitext that serves as input for the abusefilter.

How is it represented in rdf?
The easiest way to represent this in abusefilter would probably be something like "pp:wb-claims:122" or something similar.

I would as a first version just lump everything together so at least the data is available to the abusefilter editors. The more advanced version should make the distinction between wikitext, wikibase text (in abusefilter it's no json anymore), etc.

@JeanFred https://tools.wmflabs.org/universalviewer/ just gives a blank page? Shouldn't it give some sort of interface?

That's awesome @JeanFred . I updated the property to use our own viewer.

In T151351#4735577, @Paladox wrote:

I don't think so? Closing as declined as it seems to have resolved it's self (no progress in a year and a bit)

@Denengelse do you still have issues or is this solved for you?

In T208292#4705393, @Xqt wrote:

Hm, this script never worked. Do we need it ;)

https://github.com/multichill/toollabs/blob/master/bot/wikidata/oorlogsmonumenten_import.py code I used for tsv generation and import

Scraped the Dutch Wikipedia. TSV @ https://tools.wmflabs.org/multichill/queries/nlwp/oorlogsmonumenten.tsv

Setup a query at https://tools.wmflabs.org/multichill/queries2/nlwp/links_naar_doorverwijspaginas.sql to run every day at 5 in the morning and afternoon (etc). That puts it at https://tools.wmflabs.org/multichill/queries2/nlwp/links_naar_doorverwijspaginas.txt . About 2000 pages.

In T143488#4132389, @Cyberpower678 wrote:

It's doable, but not easy. Wikidata has a different structure.

What year? This is under the 2018 workboard

In T195203#4664834, @Smalyshev wrote:

Tried it again with Curl and it seems to work OK. I suspect this is the same ALPN issue as in T202785: Federation request to https://ld.stadt-zuerich.ch/query fails.

And the table should probably be renamed from gb-sct to gb-sct-lb because we also have scheduled monuments, see T207067

Last part is to check enwp template with our configuration and do some last tweaks (removing multiple options for id fields and that kind of things). I hope to be doing that soon.

And https://en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Historic_sites/Unused_images_of_listed_buildings_in_Scotland&curid=35867555&diff=864167140&oldid=858922112 is suddenly much more work.

If this gets stuck on debugging on our side, I could probably ask around for contact details for the people running https://data.pdok.nl/sparql . On https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/Federation_report several other endpoints are also failing. Solving the pdok.nl problem might fix some of the others too.

In T122711#4659433, @cscott wrote:

...and adding .jsonld at the end should also work, right?

@Smalyshev what do you think? I haven't run into this myself. My feeling is that case insensitive is probably better, but would that require a lot of work?

Based on the responses this task description needs updating to make clear what the end result should be.

Fixing the lists right now. Example edit: https://en.wikipedia.org/w/index.php?title=List_of_listed_buildings_in_Oyne%2C_Aberdeenshire&type=revision&diff=864025741&oldid=857873175

Same change as T194346

New property proposed at https://www.wikidata.org/wiki/Wikidata:Property_proposal/Wikipedia_suggested_article_name

If all the generators listed on https://www.mediawiki.org/wiki/API:Querypage follow the same logic in Pywikibot as the unconnected pages one, than probably all of them have the same issue. Maybe make a new subclass QueryPageGenerator that wraps around https://www.mediawiki.org/wiki/API:Querypage ?

Changed https://www.wikidata.org/wiki/MediaWiki:Collabpad to "CollabPad (but it is a special page)" and that's now all over the place.

In T200339#4577502, @MichaelMaggs wrote:

Have I missed something?

In T163642#4503980, @Smalyshev wrote:

@Multichill I think with new description it is clearer what this is about.

I checked several systems and both run 2.7.6. . This task is way too soon. Come back in a couple of years. You're going way too fast on this dropping campaign.

In T200339#4552218, @Lokal_Profil wrote:

Thanks @Multichill for finding the source for this.

Not finding the header doesn't stop the page from being harvested, but not finding the row template does. In both cases redirects are not resolved so those entries are skipped.

{{HB Scotland header}} and {{HB Scotland row}} are still referred to from the template documentation so its unclear if a search/replace is desired.

I'll update the config to use the two target "HS listed building header" at least.

https://gerrit.wikimedia.org/r/#/c/pywikibot/core/+/371659/6/pywikibot/site.py sure looks like it. Good to see it implemented!

In T192912#4551136, @Framawiki wrote:

@Multichill is the error still given ? I've read somewhere that this hacky limitation was removed from wd.org