ardi60@reddthat.com to Technology@lemmy.worldEnglish · 24 hours agoGoogle's shocking developer decree struggles to justify the urgent threat to F-Droidwww.neowin.netexternal-linkmessage-square180linkfedilinkarrow-up1953arrow-down14
arrow-up1949arrow-down1external-linkGoogle's shocking developer decree struggles to justify the urgent threat to F-Droidwww.neowin.netardi60@reddthat.com to Technology@lemmy.worldEnglish · 24 hours agomessage-square180linkfedilink
minus-squareFutileRecipe@lemmy.worldlinkfedilinkEnglisharrow-up15·20 hours ago These things will very likely not work on non-proprietary devices. Depends on your bank. Most work on alternate OS (like GrapheneOS), and of course some don’t. https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/ If an app (especially bank) doesn’t work, I forward them this and try to ELI5 that their current method is flawed and less secure: https://grapheneos.org/articles/attestation-compatibility-guide
minus-squareprogandy@feddit.orglinkfedilinkEnglisharrow-up2·17 hours agoWhich is fine and all, but then you still have to run a release built and signed by the grapheneos devs.
Depends on your bank. Most work on alternate OS (like GrapheneOS), and of course some don’t. https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
If an app (especially bank) doesn’t work, I forward them this and try to ELI5 that their current method is flawed and less secure: https://grapheneos.org/articles/attestation-compatibility-guide
Which is fine and all, but then you still have to run a release built and signed by the grapheneos devs.