Login
You're viewing the functional.cafe public feed.
  • Nov 3, 2026, 6:46 PM

    @pojntfx It's a bit different for browsers because you can freely install an actually good browser on any device (a check for a certain API or feature would go by engine not browser), you can't freely relock your bootloader on most phones and no custom OS can freely get verified by Google.

    Edit: also, secure cookie storage is kind of a big deal, nobody should use browsers that can't store session data properly.

    💬 1🔄 0⭐ 2

Replies

  • Nov 3, 2026, 8:09 PM

    @asterisk Agree re:you not using an insecure browser, obviously. Remote attestation of the device running a browser was actually attempted by Google as something to be introduced as a web standard but thankfully failed, to work around this they are now doing it via reCaptcha (which requires an Android device with a locked bootloader, Google account, and OS image signed by Google)

    💬 1🔄 3⭐ 4
  • Nov 4, 2026, 3:13 AM

    @pojntfx And Mozilla wants to bring it back to life but using your activity on other sites instead (judged by a third-party moderator): hacks.mozilla.org/2026/06/pact

    the reCAPTCHA thing isn't quite true, the bootloader only needs to be locked and Play Services needs to be installed, it works on GrapheneOS. It's also a bit iffy and you're still not asked to mobile verify very often (if the automated half thinks you're not a bot you won't be asked), plus reCAPTCHAv2 is being phased out and replaced with Cloudflare Turnstile and hCAPTCHA.

    💬 0🔄 0⭐ 1