Skip Navigation

User banner
The 8232 Project
The 8232 Project @ Charger8232 @lemmy.ml
Posts
75
Comments
503
Joined
1 yr. ago

  • Yes, but it's a bit involved to automate it. KeePassXC has a less technical recommendation here

  • Yeah, true story. Really weird.

  • Steam and Spotify are notorious for this.

  • Don't let perfect be the enemy of good.

  • I actually considered sticking it on a floppy disk I have. It really is a wonder how Linux is able to recognize floppy disks immediately...

  • It shouldn't take up too much space. My personal password file is under 2 KB, so for you it may be 1 MB at most.

  • What about your Lemmy account?

  • But the bad aspects of cloud services worry me a little about this

    KeePassXC is entirely local.

  • I guess the reasons I would make would be not all accounts are web-based, and using a browser for anything other than browsing is a bad idea. Browsers aren't exactly focused on keeping passwords safe, so why not use a tool designed for it? Don't keep all your eggs in one basket

    P.S. Yes, FIDO2 is much more supported

  • Clarification: They reuse the same password (such as "Password") and whenever they create an account they have to add special characters (like "Password1&" if numbers and #@&%$ were required) and when they login they forget which special characters were required by that service, meaning they don't know which special characters to append to their generic password to successfully login. The solution was to screenshot every password requirement for every service and still try to remember which characters were used.

    But yes, there is an unrelated frustration where password requirements aren't presented upfront.

  • Why weren't any backups created?

  • If you want, you can port your Bitwarden passwords over to a different password manager such as KeePassDX, which also supports security keys. I'm not sure if this is a solution you want, but it might work!

  • Hello! I'm sorry to hear you are experiencing issues switching to GrapheneOS. I understand that can be frustrating, especially with how much of a privacy boost it is compared to iOS. I have used iOS my entire life, so I know it inside and out. When I heard about GrapheneOS over a year ago, I decided that I also wanted to switch. I spent multiple months learning everything I could about GrapheneOS and Android, just to give myself an idea of if I might like it. I even bought a $30 test Android phone to get familiarity with Android.

    The thing is, I never expected it to be a one-to-one with iOS, and I expected issues to happen. I learned about potential issues and looked for solutions or forums where I can ask about such problems. I also spent that time (very) slowly convincing my friends to use Signal, but some still use iMessage. It's not an easy switch from iOS! With that said, I have a few things that may help you.

    1. Don't worry! Switching from iOS to any Android is difficult, and will take more than a week. You have to have the mindset of really making it work and making sacrifices. The thing is, even if it doesn't work, its ok to switch to iOS. Make a threat model. If iOS is what you're comfortable with, that's ok! We don't all have to use GrapheneOS
    2. Prepare Make a list of apps you will use once you switch, test out apps on an Android emulator or test phone, and see what works best for you. Not everything has to be open source, and some stuff will require Google. Tinker around and make a map of how you will set things up (apps, profiles, etc.) If you find that there are things you just can't live without, you can either switch back to iOS or have iOS as a secondary phone for those apps.
    3. Security keys If your security keys are causing you problems, consider one that acts over USB-C. If that still doesn't work, ask the GrapheneOS community for help at https://discuss.grapheneos.org/ You can still use iOS as a secondary device for logging into the services that you use security keys for.
    4. Degoogling Because GrapheneOS has such great sandboxing, using sandboxed Google Play is generally safe. It's still degoogled, but you ensure that any compatibility is met by isolating Google related things. You can even put those apps on a separate profile for further isolation. I know, it's uncomfortable to know something Google related is running in the background, but unfortunately that's the state of things. Some other custom ROMs have their own implementation of Google Play (See here)
    5. Contacting others I wasn't able to switch everybody to Signal, and for the ones I couldn't switch you can use a burner phone, MySudo, iOS as a second device, or https://jmp.chat/ to message them. In iOS 18, iPhones will also support RCS, meaning you can contact them with Android without using SMS. Again, this sucks, but you should take care of your own privacy and let them have their own journey.
    6. Banking apps Banking apps have been a common issue on GrapheneOS. Without specifics, I can't comment, but I suggest reaching out to their forum at https://discuss.grapheneos.org/ for help. If that doesn't work, use iOS as a second device for banking.
    7. iOS-specific features Android is not a one-to-one comparison to iOS, but what it makes up for is that any features you want can be quickly added by anyone. However, because the aim of GrapheneOS is a little different, it might be a while before user experience features are added. As for the keyboard, you can replace the default keyboard with ones that suit your needs. HeliBoard is a good one, although I don't know if it has the specific feature you described. These features may be a sacrifice you have to take, unfortunately.

    Again, if GrapheneOS simply doesn't work out for you you can always switch back to iOS. Good luck!

  • "Holy shit this guy programs games to play them what a chad." - MigratingtoLemmy

  • It stems from a blind hatred for GrapheneOS and its users as a whole.

  • I have wondered why they haven’t taken the opportunity to come out with a Graphene-lite for non-Pixels

    The issue I see is simply a lack of developers to do so. Trying to split the team between two mostly different projects would most likely cripple both.

  • This spreadsheet is a very helpful comparison of the different messaging apps. I've been using SimpleX for quite some time now, and the only issue I have is some lag on the iOS client.