FYI to journalists who've taken up @1password on their commendable, generous offer of free service for journalists: If you get an e-mail saying your free trial of #1Password for Families is ending, you should read that confusing message as your cue to e-mail support there to confirm that you still work as a journalist. In my case, the rep said they couldn't follow links sent via mail, but sending PDFs of my author pages at my clients sufficed to get my 100% discount reinstated.
Getting pretty glum about 1Password 7 being EOLed and them breaking the browser extension on purpose. I do not want to sync my vault to their storage or use their new slow bad app. What’s your favorite #1Password replacement?
Google's passkeys, introduced in 2022, have become a popular and secure alternative to traditional passwords, being used over 1 billion times across 400 million-plus Google accounts. These passkeys, which rely on fingerprints, face scans, or PINs for authentication, are faster and more resistant to phishing than passwords. Google plans to integrate passkeys into its Advanced Protection Program, enhancing security for high-risk users. Additionally, third-party password managers like Dashlane and 1Password can now support passkeys, further expanding their use. The technology is supported by major companies like eBay, Uber, PayPal, and Amazon, indicating a shift towards passkey-based authentication as a more secure and efficient method.
Somebody should release a wrapper around #1Password's op CLI tool, which adds new features but is also only available if you live in the US Midwest. One Password Extended, or ope.
It is a little crazy that I’ve moved my entire digital life to #1password. Like I don’t know any passwords anymore. I don’t store SSH keys anywhere else. It is a complete trust in a platform I rarely bestow but tbh they’ve never let me down. It just always works. Best subscription I have.
Someone posted their #1Password Watchtower score a couple of weeks ago, and this inspired me… current progress shown in the photo. The little yellow bit on the right showing weak passwords are for some internal not-connected devices. Amazing how many logins are for sites that no longer exist.
Now that all major desktop browsers support #Passkeyscaniuse.com/passkeys is there an effort happening to create browser level APIs open to everybody to ensure passkeys can be used effectively?
While #1Password open sourced their implementation blog.1password.com/passkey-cra… of #passkey-crates the question is: is any work happening on Passkey APIs for browser extensions (i.a. password managers) to use.
While it is great to see big tech move the needle on this and announce their implementations and push this technology, it is a pity those efforts seem to focus around siloing and limiting passkey usage to their implmenetation / tech.
For example Apple makes it impossible for e.g. @keepassxc to generate passkeys in the browser.
Are there plans to work on open browser APIs? is there any public info / efforts you are aware of and can share @rmondello? Specifically for #macOS it would be great if Passkey creation / authentication could be used via Apple APIs.
Looks like #1Password fixed a medium-term bug re: frequent inability to 'see' biometric unlock options (eg, #AppleWatch). Nice! Sometimes things /do/ get better instead of worse 🙃
↓ Us when we found out Kolide is being acquired by @1password
When you team up with a company that’s so aligned with your values (like privacy, security, and always serving people first) you can’t help but get excited about the journey ahead.
I'm curious to know how others version control their private configuration files / docs / wiki. For now, I've created a #Gitea#Docker stack on my home network. Instead of copying the files I want to track into another folder and pushing from there, I've created hard links. Any other suggestions? #git#config#versioncontrol#linux@gitea
@5am I use @gitea (self hosted) and keep all my #k8s (k3s, actually) and whatnot in different projects. I use #1password’s op command to inject secrets into the various #yaml files. I use just to automate common tasks. It all works great.
Well I've completed my migration from #1Password to #bitwarden and while there are clearly gaps in the functionality (tags for instance) I don't think there are any showstoppers here - for me anyway.
The killer function for me is the ability to configure a login based on the port number as well as the domain - as a developer localhost:1234 and localhost:9876 are different but 1P listed all localhost logins!
The browser extension and android app work well and I've not had any issues so far.
And if you aren't using 1Password already to store and sync your SSH keys, or to be your SSH agent, or to use those keys to sign your #git commits... you're really missing out!
As a developer the biggest irritation I have with #1Password is that it doesn't take ports into account when displaying suggested logins; so logins saved for localhost:1234 will also be displayed for localhost:9876.
I mentioned it on the birdsite a while ago and they responded saying such a feature would be useful but it never materialised.
Thinking about moving to #bitwarden but initial testing shows the same limitation - unless there is a setting somewhere.
Disappointed to report that the glory days of #AgileBits (aka the makers of #1Password who have abandoned AgileBits and just become 1Password the Company) are over.
1Password had been showing early signs of #Enshittification with the update from version 7 to version 8.
As of today I can tell it's turning into nagware: treating the UI as a billboard for advertising, and most obviously & predictably boiling the frog via a rentier capitalism subscription model, despite prior assurances.
LOL. Purely coincidental I'm sure, but it takes some Google prompt engineering to search for 1Password employee union and NOT get recommended the #1Password Careers page as the first result 🤔
> "1Password" "employee union"
☝️ that works, well, as of 2024-01-14. Anyhow…
An Employee Union is absolutely a way to slow down #Enshittification, possibly a way to prevent it, and MAYBE a way to cure it. An employee union and a consumer union: a one-two-punch to counter shareholder myopia.
I realized I'd gone from feeling vigilance was enough with the #1Password#enshittification trajectory to realizing I'd now have to start planning to retool my 1Password-centric workflow, which I'd also roped my husband into.
We're already subscribers; I won't feel like that was forced on me. It will depend on how much they squeeze the pricetag and how much they try and covertly advertise to me and subvert my attention.
I hope I have years with them still. Time enough for them to unionize :)
I've (perhaps naively) been adding my TOTP #2FA secrets into my #1Password vault for the sake of convenience, but am now looking to switch them out to a separate 2FA app/manager so it's actually 2FA. Can anyone on the #fediverse recommend me one?