So, after being utterly pissed about what Google did with HttpClient v4, I spent yesterday on upgrading to HttpClient v5 (did not notice it coming out of beta in February). Good news is, my SSL spoofing code still works. Curious news is that Google changed something about the logging process (again). Previously, if they detected that you are not on Android, you’d be stuck in an endless CAPTCHA loop. Now you just get a plain HTTP 403 with a details message of “Bad authentication” (which is kinda accurate). Looks like what I initially thought to be a red herring was actually just a bug. Of course, this keeps me from properly testing the new CAPTCHA code path…
Anyway, no reason to be alarmed, this doesn’t affect Raccoon.
Gotta vent, cover your ears.
I actually really hate the colorscheme of DummyDroid. I somehow managed to more or less copy the SUN Microsystems colorscheme by accident - and that already looked dated 20 years ago.
Well, if anyone has a good suggestion on how DummyDroid (and therefore the Raccoon apkdownloader should look in the future, contact me!
I’d really love to work a bit on Text Fiction. Bringing GLULX Support to Android would be great. Though I’m afraid adding another engine basically comes down to writing another app.
Fun fact: developing an app like Text Fiction is an upfront investment of around 40k €. I still get spam emails from scavengers trying to buy it off me for a couple hundred bucks.
Hm, France published its version of the corona virus warn app. Seems like I should add a commenting/rating feature to Raccoon. This is probably one of those things where you should be allowed to voice concerns, even if you don’t have the app installed (not that having an app installed is a meaningful requirement for allowing reviews in the first place).
With Android and Play, figuring out device compatibility is somewhat of a black art. Which really just is a nice way for saying 'the whole Android ecosystem is one giant compatibility hack'.
Ha! Fun! When you ask Google Play for anything, you get a binary blob in response which must be parsed, using the protobuf library. There are two version of that library available (v2.x and v3.x) that implement version 2 and 3 of the protocol buffer language respectively. Since the two languages are incompatible with each other, I always assumed that the libraries would be as well, but that’s not the case! Version 3.x of the library is actually backwards compatible and able to properly handle blobs created with v2.x!
Why is this so great? Well, Play is inherently tied to version 2 of the language, but the v2.x library lacks a lot of useful features, such as the ability to export a binary blob to JSON. You can only format a message as plain text which kinda looks like JSON, but won’t be parseable. For small stuff that’s sufficient, but you are completely at a loss when dealing with something bigger, such as search results.
We all know the problem: Google Play only allows us to download apps, compatible with our device and accessible from our current location. Well, that can be helped.