- 0 Followers
- 0 Following
- 1 Posts
Sometimes that hoop is simply pressing regular - followed by <space>, and autocorrect does the rest. At least in the Microsoft office suite with English language setting
In Norway, the trolley coined gained popularity as society went mostly cashless, yet the trolleys demanded their token. An earlier factor was that it was annoying to make sure you always had a coin of the correct denomination (physical size). Trolley coins can be part of your keychain, or won’t be accidentally used to buy a newspaper before going to the grocery store.
Most people still return the trolley and slide it in, like civilized humans should
Wasn’t one of the very first things Trump2.0 did January 2025 to fire a lot of institutional leaders and install his loyalists?
And the whole DOGE affair triggered more leadership change?
The assumption is that the native passkey manager on the device (iPhone, android, windows) would sync the passkeys (to Apple , Google, Microsoft) for protection against device failure and easy of use across devices. Or you risk loosing your accounts if you loose your device.
Dont they all sync to the respective cloud services?
iOS vault -> synced apple cloud
Android vault -> synced with Google cloud?
Windows Hello -> synced with Microsoft account?
And if they’re not synced, that’s even worse. Loose your device and loose your account. Or keep track of which of your 5 devices are have keys for which of your 150 accounts
A cursory search lead to this thread from 2024 community.bitwarden.com/t/…/74800
where an employee stated
I’ll note that policy wise nothing changed. The referenced issue is a packaging bug, but the goal still is the dual licensing model, with the core being open source, and some (mostly enterprise) features being source-available.
Both the client and server are mostly open source. Some server features are paywalled. The alternative Vaultwarden server is fully open source, and much lighter on system resources.
Have there been any recent licensing shenanigans with BitWarden?
Concerns Over Bitwarden Moving Away from Open Source: What Does Our Future Hold?
Hello Bitwarden community, I have recently heard some concerns regarding Bitwarden moving away from its open-source model, and I wanted to discuss this topic with all of you. In particular, the recent addition of the “bitwarden/sdk-internal” dependency to the Bitwarden client and the accompanying licensing changes have raised some questions about what this shift might mean for us. I’m wondering how the limitation of the SDK to only work with Bitwarden’s products might affect us as users. This ...
A key for each service for each device is too impractical in real life.
Getting a new device would mean logging in to hundreds of services to link up the new device. Or somehow keep track of which services have keys with which devices. And signing up to a new service would mean having to remember to generate keys for a a handfull of devices, some of which might not be available at the time (like a desktop computer at home when you are out). Or you risk getting logged out if you loose the one device that had a key for that particular service.
I agree passkeys can make sense with something like BitWarden or KeyPassX. Something that is FOSS, and is OS and device agnostic, and let’s you sync keys across devices. And should have independent backups too. Sync is not backup.
I use BitWarden too. OS , device and browser agnostic is a win
But I imagine the vast amount of people will use whatever their platform is pushing, so Apple Google or Microsoft. And in 5 years time “3rd party passkeys” are not “secure enough” and blocked by the OS. (Ok that’s a bit tinfoil hat, but Google’s recent Android app developer verification scheme is fresh in mind)