News for hackers. Stuff that matters.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by SoftTalker on Monday October 05, 2026 @10:18AM (#49965233)
All of those things are possibilities with any phone. If you're not prepared for the loss/damage/failure of your phone that's on you.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grahamburger on Monday October 05, 2026 @11:52AM (#49966506)
Definitely a good idea to plan on this at all times. In my case this looks like:

* All photos auto upload to Google photos

* All other important files are in a syncthing folder with at least two other devices (laptop+desktop)

* 2fa in Authy with cloud-sync

* Passwords on Firefox sync

* Google Fi is my carrier, and pulls eSIM when I log in to the app even without my old phone

* Google voice number is my main phone number. I don't lose access to incoming or outgoing sms or voice calls if I lose my phone.

In a pinch, I can buy a cheap prepaid phone and sim while traveling and be fully functional and reachable. I've had to do this before, and while I probably wouldn't go to the trouble for work, I feel compelled to be at least reachable for family.

I've thought about de-googling this further; photos could go straight into syncthing and I could port my # to a generic SIP provider that offers SMS. So far neither have seemed quite worth the trouble.

I've always felt very uncomfortable treating my phone as anything other than a rather overpowered thin-client.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by SoftTalker on Monday October 05, 2026 @12:03PM (#49966670)
One flaw in that is that Google Voice or other VOIP provider numbers are often rejected for 2FA or account validation.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grahamburger on Monday October 05, 2026 @12:03PM (#49966681)
Sometimes, yes, but not that often IME. Maybe 10-15% of the time.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by mattwad on Monday October 05, 2026 @12:00PM (#49966616)
I recommend you get off Authy - they don't have a browser extension or a desktop client, and surprise they don't have a way to export your codes either. I had to send them a GDPR data request, and then Claude decrypted the csv file they sent. I now use Ente and it's so nice having 2fa inside a browser extension. I can also export the secrets at will.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by __aru on Monday October 05, 2026 @04:08PM (#49969950)
Keepass is also a good alternative to Authy, caveat being you need some way to sync the db file between devices.

I personally use Keepass for 2FA, Bitwarden for passwords. It's worked great for me so far, and I expect to stay with this setup for the foreseeable future.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by pimeys on Monday October 05, 2026 @04:47PM (#49970462)
Yubikeys can store 2fa codes. You just install their app from F-Droid and show the NFC key to get the codes.

Now the codes are with you and not in your phone or in the cloud.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by someonebaggy on Monday October 05, 2026 @10:36AM (#49965466)
They are stronger possibilities once you know they are going to happen eventually, not just that they could theoretically happen.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by shermantanktop on Monday October 05, 2026 @09:04PM (#49972891)
Frequency x severity. Frequency is underestimated in the long term because human intuition is bad at estimating risk over large time scales.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by hbn on Monday October 05, 2026 @10:59AM (#49965741)
Yes but I don't want my phone to be lost or destroyed or stolen. So using a phone that will likely fail until it does so is not taking preventative measures.