Iny my opinion T412542: Rethink protocol support for OAuth apps should be added to the subtasks. Non-WMF mobile apps have to use the registration-form at https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose to use OAuth2. But that registration form doesn't allow custom uri-schemes currently, which are required for OAuth to work with mobile apps.

I was wondering if there is a already a timeline for this. :)

@SuperHamster thanks!

In T413570#11650315, @AlexisJazz wrote:

Maybe T414048 and/or T418346 are related somehow? There seems to be an overarching theme of browser-specific 429 errors in the past few months?

Btw. I released on new version of CommonsFinder that sends referer-headers with all network requests: https://github.com/nylki/CommonsFinder/commit/3c1727a7768b9dc3bf76d4982219f550b649832a

In T167947#11536938, @Pigsonthewing wrote:

Is there a reason hashes could not be held in a property in Structured Data ("SDC"), added by bots?

This would not only be interesting for discovering and searching for similar images or duplicates, but also to prevent/inform about potential accidental uploads of identical images.

Hi @Jonesey95 !
Do you have a link to the commit or ticket (if it's public)? :)

@SuperHamster Btw. I noticed that since ~ yesterday it appears to now work on my setup again without setting a referrer.

In T413570#11494643, @SuperHamster wrote:

Ah! I resolved the 429 issue on my end. My webapp uses Helmet.js, which defaults to hiding the Referrer header when loading external files. I started allowing the Referrer header to be sent when loading upload.wikimedia.org images and images are loading fine again (and I'm now back to using upload.wikimedia.org instead of thumb.php). I'm guessing with whatever recent changes were done to keep AI scrapers at bay, the Referrer header became a more important heuristic.

hi @Joe and @TheDJ,
Thanks for sticking with me! I was indeed wrong about the empty body.
I created a minimal iOS sample app without any 3rd-party libraries to reproduce the issue, this time logging a body.
If you like, you can clone and compile yourself: https://github.com/nylki/CommonsImage429ReproApp

In T413570#11491805, @TheDJ wrote:

The response body is empty when this happens

That seems unlikely to me. Maybe your framework is one of those that doesn't handle response bodies when encountering errors. I remember that even 15 years ago this was already an issue with iOS apps and required custom code to able to access the data of the error response.

In T413570#11486635, @Joe wrote:

Can you please report the full error message you get in the response body? Thanks

After writing the ticket, I had the idea to test if it is indeed the User-Agent header that causes the 429 and it appears to make a difference.
I changed it from
CommonsFinder/1 (https://github.com/nylki/CommonsFinder) iOS 26.1.0
to
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:146.0) Gecko/20100101 Firefox/146.0

Hi there, I am the developer of CommonsFinder. Sorry to re-open this issue, but I just noticed the second point in the ticket description:

In T390302#10700265, @HNordeenWMF wrote:

In T390302#10689365, @Commander_Keane wrote:

I believe iOS devices default to HEIF file format which can be patent encumbered: T211745

Hi @Commander_Keane great flag, that will need to be a subtask for the prototype. My understanding is we could use APIs to perform file conversion to JPEG and PNG, or UIKit has some methods we could leverage.

In T211745#4816164, @IM3847 wrote:

Yeah , they can be converted but they are loosing sensitive information like location, date etc...