3 ms·
I can't reproduce the text mangling mentioned in this article. For example, if I try generating a QR code for "https://fooco.at https://fooco.at": https://char
by omoikane 5y ago
I can't reproduce the text mangling mentioned in this article. For example, if I try generating a QR code for "https://fooco.at https://fooco.at":
https://chart.googleapis.com/chart?chl=https://fooco.at&cht=qr&chs=256x256 https://chart.googleapis.com/chart?chl=https://fooco.at&cht=...
I see that when scanned, I get the same "https://fooco.at https://fooco.at" string back, as opposed to "foo.co.at"
- pks016 5y agoInteresting. When I scanned I got foo.co.at. I'm on Pixel 5, Android 12.
- readams 5y agoIt's only when viewed in the Camera app and not in Lens or other readers. I made the same mistake :-)
- slyall 5y agoDefinitely broken for me. Running Andriod 12 on a Pixel 4a. I get the same for fooco.nz , foonet.nz, foodmil.nz and foogov.nz . But not the more obscure foogen.nz and fooiwi.nz. .nz only did 3lds for a long time. 2LDs are only about 5 years old.
- joshspankit 5y agoPulled out an Android 12 Pixel 3 to test, and also got ‘foo.co.at’
- noah_buddy 5y agoThe Pixel 3 particularly has been mangled by updates. Someone previously mentioned something along the lines of: if a company bundles security issues and UI changes together, they don't actually care about security, they're just using it as a stick to keep you on the planned obsolescence treadmill. It doesn't even have to be intentional acts to degrade a phone, just make each patch consume more resources (under the auspices of "feature development") and you'll eventually strangle out any old devices once they're not powerful enough to run. Meanwhile, my phone app on my pixel has gotten increasingly buggy and unstable, sometimes breaking outright, over the years.
- tata71 5y agoGrapheneOS.org, stability like nothing else I've used, ease of installation literally couldn't be better.