view the rest of the comments
Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
that is a very hot take. besides just personal use (bitwarden open source), 1password allows my work team to have our passwords, 2fa codes, backup codes, credit cards, addresses, all in one secure place, where we can add/remove people and grant access as needed. Our solution before was having one person in charge of the 2fa codes (which sucked, cuz sometimes they werent around/available), and plain text documents in our project management tool (which sucked, cuz people would accidentially delete parts of the doc, anyone could view the whole thing and leave it open, etc.). and thats not to mention that we werent doing the basics, like generating strong unique passwords for each service.
And having all those eggs in one basket is a risk. What is the plan for when 1password has any issues?
there will always be a worst case scenario no matter what solution we choose. 1password going down is less likely then a rogue employee (we’ve had a few), or a breach/issue with a much less secure platform that doesn’t specialize in sensitive data collection.
I think it is better to plan for the breach/issue/villain then to assume it will not happen. I don't think 1password will stop a rogue employee or a protected info breach (I think everyone has had their info got by this point). I get people like these programs but I hope the same people have a backup plan.