mvolz@wikimedia.org
User Details
- User Since
- Oct 15 2014, 9:50 PM (626 w, 3 d)
- Availability
- Available
- IRC Nick
- Mvolz
- LDAP User
- Mvolz
- MediaWiki User
- Mvolz (WMF) [ Global Accounts ]
Thu, Oct 15
Wed, Oct 14
@WMDE-Fisch This is going to be relevant for you too... GET for pdfs will be huge (but maybe we can carve that out specifically?)
Tue, Oct 13
It turns out that for biodiversitylibrary, they return a 302 and not >400 so this solution does not work for them either. It's kind of looking like we should, for the time being, go back to using HEAD and possibly in the future move some of this logic into the Zotero fork.
Just for context how this was created, we have production logs that show real errors that production is actually encountering. https://logstash.wikimedia.org/app/dashboards#/view/5eaf4e40-f6b6-11eb-85b7-9d1831ce7631
Mon, Oct 12
We are registered with them, yes.
Fri, Oct 9
Thu, Oct 8
FYI someone created a gadget to do this and posted it on diff https://diff.wikimedia.org/2026/10/06/autocitewikidata-making-automatic-citations-connected-with-wikidata/
Mon, Oct 5
Sat, Oct 3
Fri, Oct 2
Wed, Sep 30
Tue, Sep 29
Request submitted, awaiting response.
Mon, Sep 28
Sun, Sep 27
Sat, Sep 26
Fri, Sep 25
Wed, Sep 23
Thanks, a follow up on the weird behaviour - I'm not sure it should have it's own ticket! But actually, a cache wouldn't have helped in this case after all :/. It turns out the url I thought was the "same" were all slightly different, it was cycling through different dates. There was only one duplicate.
Not sure when this got fixed but doesn't seem to happen anymore. Still not on ECS but we'll get there... eventually... in T409432
Tue, Sep 22
Mon, Sep 21
Thanks, I was waiting to hear the results of the discussion from api-platform before starting on implementation - did there ever end up being a discussion about this? What was the outcome?
Fri, Sep 18
Plausibly dupe of T383668, but I hadn't thought through the implications to these formats.
Sep 17 2026
Sep 16 2026
Deployed, with OpenLibrary at lowest priority, and also thank you to Library of Congress for giving us higher rate limits which made this less risky :).
We currently fallback on user entered urls if the canonical one doesn't exist, so we should still implement some at least rudimentary form of tracking parameter removal at present regardless. There are also some libraries now that do this, i.e. but would need security approval I think i.e. https://github.com/ClearURLs/Rules
Sep 14 2026
Ticket above says it's about bullseye and because it's EOL, but above is bookworm and I have builds failing on trixie, too... both gitlab and gerrit...
Dupe of T437069 maybe?