Privacy Guides
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
Btw OP, you can export from Google Auth. and it will give you a big QR code that you can just snap with Aegis, in case you didn't know already.
No need to transfer one-by-one.
You just need to get the code off your phone first.
Err.. how do I get it off my phone tho?
A marker and steady hands.
🤣
There are several ways! First, take a screenshot (power + vol. ~~up~~ down is the shortcut for me, not sure if this is an Android default).
Then email it to yourself, or plug in your phone with UTP to a computer and move it out of the picture folder, or print from your phone to a wifi-enabled printer, or use something like Google Keep and sync it to your computer, etc.
Not sure if you're joking but thankfully you can't take a screenshot of Google Auth.
And emailing it would completely defeat the purpose of 2FA
Oh goodness, why didn't I think of emailing it to myself. 🤣 Thank you for the tip, I'll do that in the morning after I wake up.
The mental image of me looking at a qr code on my phone screen, and only then wondering how I would catch that on the phone's camera did make me laugh.
😂
What I did was take a screenshot and then scan the photo via Aegis
Doesn’t that defeat the whole purpose though? I would regenerate each OTP “string”, for lack of a better way to say it, rather than bringing them over as Google already has that data.