That's interesting cause on a a bigger german website we are trying to figure out how to get that firsty thing working with removable eUICCs since Feb the 16th. The only person that reported there that eSIM.me is working for them used a smartphone with a built-in eUICC for "looking at the app and receiving activation code" and after that put in the eSIM.me into a Galaxy S10.

Everybody else that wrote something about working or not working — no matter if they use products from eSIM.me, 5ber or sysmocom — wrote that it isn't working for them. Even when installing the profile with the static activation code from within the APK — that can be found when using apktool on the APK and a bit of grep — I wasn't able to get a data connection with the profile deployed to the sysmoEUICC1-C2G. Btw. firsty seems to use Vodafone here.

However, firsty support answered today that they "are looking into support for these use cases, so stay tuned!"

myDealz? :) You can spoof the app to "detect" a compatible device on a rooted phone by hooking bv.b class and returning true in frida or XPosed

»they do in fact have the expertise necessary to decide whether JPEG-XL is something they want to do?« The problem is that they do have the people with expertise but those were not asked. For example, the AVIF team at Google does not have the expertise — they have proven that publicly (there was a AVIF vs JXL comparison thing that got put out) and later on an response they gave to Sneyers (the response got shared on Discord).

»it's less savings than AVIF, of course,« In most cases JPEG XL will save you more than AVIF.

Those words were about the JPEG recompressor (Brunsli) specifically, which saves about 22% but has a smoother transition from today's .jpg world than any of the new lossy formats; you can bit-for-bit reconstruct the original JPEG from the Brunsli-compressed one, and it's certainly much faster than AVIF to encode with CPUs. You can even insert Brunsli as a Content-Encoding that's transparent to the user (so right click still saves .jpg), and Chrome had an issue open to consider doing that before they backed out JXL support.