The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: [email protected]
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
π¬Matrix Chat
π°Our communities below
Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.
Our Communities
Lemmy App List
Chat and More
I like the idea of passkeys, but one thing that I'm still not clear on is what happens to them when I get a new phone.
It says the passkeys are stored on the device, so would I need to keep my previous phone around to be able to sign in on the new phone?
Password managers like 1Password and Bitwarden support it already or are planning to in the near future, so you will be able to sync them across devices. And I'm pretty sure they will be stored in the iCloud and Google password managers as ways to lock in users even more
I'm waiting until Bitwarden supports passkeys before diving in. From what I could tell, they are aiming to release in late October this year, but I'm not certain. (ie - should be imminent).
I use Bitwarden, so that will make things easy.
Thank you!
Exactly what I've been doing. I don't like them being saved on-device, and I don't want to create multiple, so 1password handles it for me. Has been really convenient, however only around 10 platforms total have let me add a passkey, out of some 1300 passwords I have registered. Quite a slow rollout
I'm with ya. I need to see kind of how it pans out. How smooth it is, how device changing works, how in general sites handle lost passkeys. Then I'll decide. I want security but I'm also not looking for even more hassle then my current method of strong passwords and 2FA.
Keys, like everything in digital devices, are just strings of data. So if they are on device, it's the matter where they are stored on the device.
Google and Apple implementations are going to store them in secure TPM chip, basically once written there should be no way (people knowing darker side of TPM can disagree) to get them back. But, if I understand correctly, there is no forced way how to store them in the spec, there can just be a way Google implement it in such a way, hope they add open API to Android.
It's 1s and 0s all the way down (notwithstanding qbits...). But it all comes down to workflow and reducing friction of use securely. How will Bitwarden (and others) sit within the process? That remains to be seen. In the meantime, I'm going to see how it goes as I'm not switching gears until I have a thorough understanding of the actual implementation wrt general operation, multiple devices, family accounts (Bitwarden 'organizations'), backups and recovery, and how to teach and support non-tech-savvy family members through the change).
It absolutely looks promising, but too risky to be bleeding edge.
I won't begin using passkeys until keepass supports them and I don't know when that will be.
Same here. Though this transition in general will take forever as you'll always have that one odd site that doesn't support passkeys even when it gains mass adoption.
