It was very clearly advertised as experimental and insecure:
Warning
Private message and channel features have not received external security review and may contain vulnerabilities. Do not use for sensitive use cases, and do not rely on its security until it has been reviewed
There’s definitely no law in the US. In fact the vast majority of Android device bootloaders come locked. Pretty much just Pixels and Galaxies that allow this.
That’s fair.
Fuuuuuck outta eah
I think you got it backwards. What are some categories an adult would never watch? Fucking Dora the Explorer and Blues Clues and the like. Although it’s very likely they just play it from their account for their kids.
Yes you’re missing a lot. SimpleX even has a directory bot to find public group chats.
Again, we were talking about the back.
Did you have a question?
Yes it is. Once again, we were talking about on the back.
Cases need a notch to expose the power button
I don’t see why that’s a problem.
Can’t use the power button to lock the screen while fingerprint unlock is enabled, because it immediately unlocks itself with the fingerprint.
Sounds like you just had a shitty phone, that shouldn’t happen.
Accidentally unlocks itself way often when putting it in my pocket than with the back reader.
Again, shitty phone. You’re supposed to actually push the button to unlock it. Don’t understand why your finger would be on the back of the phone when putting it in your pocket anyway.
This thread is just a reminder of how terrible phones have become.
Strangely it’s usually only the cheap phones that include these premium features.
on the back of the phone.
EuropeEveryone needs to drop Microsoft ASAP
FTFY
Yes it’s tied to your identity. That’s what PII is. It’s also not tied at all to your OS.
IMEI is PII
According to the users in that issue, the mere application of the API is illegal, as is the dependency. Sooo I dunno what kind of PACs there are in the EU but I would be leaning on and contributing to those.
Please don’t link to Reddit. Context below:
The EU is currently developing a whitelabel app to perform privacy-preserving (at least in theory) age verification to be adopted and personalized in the coming months by member states. The app is open source and available here: https://github.com/eu-digital-identity-wallet/av-app-android-wallet-ui.
Problem is, the app is planning to include remote attestation feature to verify the integrity of the app: https://github.com/eu-digital-identity-wallet/av-app-android-wallet-ui?tab=readme-ov-file#disclaimer. This is supposed to provide assurance to the age verification service that the app being used is authentic and running on a genuine operating system. Genuine in the case of Android means:
The operating system was licensed by Google
The app was downloaded from the Play Store (thus requiring a Google account)
Device security checks have passed
While there is value to verify device security, this strongly ties the app to many Google properties and services, because those checks won’t pass on an aftermarket Android OS, even those which increase security significantly like GrapheneOS, because the app plans to use Google “Play Integrity”, which only allows Google licensed systems instead of the standard Android attestation feature to verify systems.
This also means that even though you can compile the app, you won’t be able to use it, because it won’t come from the Play Store and thus the age verification service will reject it.
The issue has been raised here https://github.com/eu-digital-identity-wallet/av-app-android-wallet-ui/issues/10 but no response from team members as of now.
Some people already are
But the point of LoRa is in the name, long range. Wifi barely reaches outside my house. Also a WiFi mesh is dependent on a variety of complicated and proprietary networks and systems while meshtastic is entirely independent.
Did you have a question?