"The Quiet Renovation at Bitwarden" (it isn't good)
If you are interested in privacy you are probably interested in password storage ... plus I wanted everyone to know about the inevitable future enshitification of this product. Spread the word and replacement recommendations are welcome too.
The Quiet Renovation at Bitwarden - ByteHaven - Where I ramble about bytes
Back in March, I wrote about Bitwarden doubling their Premium price — and specifically how they did it. Buried in a feature announcement. Priced in fake...ByteHaven - Where I ramble about bytes
like this

DashboTreeFrog
in reply to RotatingParts • • •Croquette
in reply to DashboTreeFrog • • •hypnicjerk
in reply to Croquette • • •willington
in reply to DashboTreeFrog • • •That's the difference between libre software and merely open source software.
Libre licenses make it hard or impractical to close the source at a later date.
Open source licenses are much more permissive and allow any entity to produce a closed source derivation at any time.
Libre licenses are all about strategically protecting the software commons from privatization.
tehsYs
in reply to RotatingParts • • •slampisko
in reply to tehsYs • • •Nothing has beaten KeePass for me so far. It takes a bit of setting up if you want your database to sync among all your devices, but in other aspects it's perfect for me
EDIT: In case you're curious, I use KeePassXC on PC, KeePassDX on Android, and Syncthing to sync the database.
comrade_twisty
in reply to slampisko • • •What drove me (and my family) from KeePass to Bitwarden was the family sharing and survivor access.
Until KeePass supports these it's not really up to par with Bitwarden.
Especially digital legacy management is a must have for a well rounded password manager.
JillSteinsPuckeredAnus
in reply to comrade_twisty • • •comrade_twisty
in reply to JillSteinsPuckeredAnus • • •bitflip
in reply to slampisko • • •Auli
in reply to slampisko • • •BrilliantBadger
in reply to slampisko • • •I use both same products, just manually copy to phone periodic as my vault is pretty static
Made the move from bitwarden not that long ago, actually a bit before their price increase (just timing not because of it). Nothing bad about BW to say, it worked great for me for years.
My motivation was wanting my password manager fully offline.
Keepass are fantastic programs, and actually now more pleased with my move after seeing some negative moves from BW I needn't be concerned with
+1 for Keepass!
test_ [none/use name]
in reply to tehsYs • • •The author wrote a guide to self-hosting VaultWarden
blog.ppb1701.com/self-hosting-…
Self-Hosting Vaultwarden - Taking Back Password Management: Part 8 of “Building a Resilient Home Server” Series - ByteHaven - Where I ramble about bytes
ByteHaven - Where I ramble about bytesThurstylark
in reply to test_ [none/use name] • • •FoundFootFootage78
in reply to tehsYs • • •Tundra
in reply to RotatingParts • • •psono.com/
privacyguides.org/en/passwords…
Psono - Self Hosted and Open Source Password Manager for Companies
psono.comEgonallanon
in reply to Tundra • • •thefactremains
in reply to RotatingParts • • •Open Source Password Manager for Teams | Passbolt
Passboltonlinepersona
in reply to thefactremains • • •GrapheneOSRuinedMyPixel
in reply to thefactremains • • •Mr_WorldlyWiseman
in reply to RotatingParts • • •SocialistVibes01
in reply to RotatingParts • • •girsaysdoom
in reply to SocialistVibes01 • • •Self-Hosting Software and Services - Privacy Guides
Privacy GuidesJul (they/she)
in reply to RotatingParts • • •Vaultwarden will survive. Since the client is open source, once they close the API and break compatibility of the clients with Vaultwarden, the old version of the app can simply be forked and rebranded. I also do hope that the KeyGuard app will continue to support vaultwarden as well since if bitwarden closes the API and makes a breaking change, as is likely to happen, it will break KeyGuard as well, but it will still work with VaultWarden for some time.
The real issue is that many people who are using Bitwarden aren't savvy enough to host Vaultwarden in a secure way. Many people are careless with things like secret keys and such and dont know how to properly secure a web facing app or a VPN into their local network. But anyone who self hosts should result learn those things anyway. This one just happens to be a particularly high risk since it contains all of your passwords for everything else.
twoBrokenThumbs
in reply to Jul (they/she) • • •TheMadCodger
in reply to twoBrokenThumbs • • •Jason2357
in reply to TheMadCodger • • •nibbler
in reply to Jul (they/she) • • •Just learned about KeyGuard. But I dislike their LICENSE:
All Rights Reserved
Jul (they/she)
in reply to nibbler • • •asdfasdfasdf
in reply to Jul (they/she) • • •We really need a VaultWarden paid service, if there isn't anything against doing so in the license.
I don't know why the server needs any specialized software at all though. In the end, if it's just some password history, why not just have a client that allows generic storage backends and you can upload to Filen or S3 or whatever else you use?
Jul (they/she)
in reply to asdfasdfasdf • • •It uses a database and it's totally possible to use SQLite as the database and sync that elsewhere. You could then find or make a small client that just accesses that db directly rather than a web service, I suppose. Though there are already several apps out there that store passwords locally and their data files can be synced, if that's what you want.
But if you're doing that then you may not be using this in the most common way or may not understand the risk involved. This is likely to have every one of your logins, not just a single login that may or may not be used on other sites, but the specific username and password and which site it's associated with. On addition to access to those accounts, this links all of your accounts to a single identity which companies spend billions to do with advertising IDs, cookies, embedded scripts, and lots of other, usually shady, practices. This is a gold mine, though usually only for one or a few users, so generally not a major target unless you're being targeted personally for some reason. So, even if they don't get the passwords, th
... Show more...It uses a database and it's totally possible to use SQLite as the database and sync that elsewhere. You could then find or make a small client that just accesses that db directly rather than a web service, I suppose. Though there are already several apps out there that store passwords locally and their data files can be synced, if that's what you want.
But if you're doing that then you may not be using this in the most common way or may not understand the risk involved. This is likely to have every one of your logins, not just a single login that may or may not be used on other sites, but the specific username and password and which site it's associated with. On addition to access to those accounts, this links all of your accounts to a single identity which companies spend billions to do with advertising IDs, cookies, embedded scripts, and lots of other, usually shady, practices. This is a gold mine, though usually only for one or a few users, so generally not a major target unless you're being targeted personally for some reason. So, even if they don't get the passwords, they've now linked every account you have on every site to your identity.
If you are allowing the database to be relatively easily obtained by syncing it to a central location accessible over the internet, a bad actor who gets it can even take their time brute forcing any encryption that may be present in the database, but if you don't keep encryption keys only on your local device because you want to be able to use it elsewhere, then you probably stored the keys along with the db and they dont even have to bother with that, or if it uses password based encryption, they just have to guess or brute-force a single password.
If it's behind a properly secured web service, then even if they find an exploit in the server software, they likely have to do many queries over time to get much data and the server can mitigate that risk and/or alert the owner about new logins and such. A database in the hands of the bad actor can't complain about too many attempts to access it or notify anyone that it's been copied.
So, IMHO, it's a bad idea to use synced local password managers unless you have a very robustly secure way of storing the database and the encryption keys.
asdfasdfasdf
in reply to Jul (they/she) • • •Yeah I was imagining a system more like Password Store - use Git to version control secrets which are encrypted using some form of asymmetric encryption.
You store the private key somewhere you control, like a USB drive or something. Same as Bitwarden's master password.
Jul (they/she)
in reply to asdfasdfasdf • • •Yeah, there's still a risk if you're exposing the encrypted passwords. For example there is still some risk that governments have backdoors in some kinds of encryption, which of course means other malicious actors do as well. And there's still brute forcing which is mitigated with a webserver layer in front of the raw data.
But there are lots of existing applications for that like keypass and its forks. Vaultwarden is more about the web services front end to the data than the data storage itself. And a web service benefits from a relational database over a flat file.
WhyJiffie
in reply to Jul (they/she) • • •afaik everything is encrypted. not like a big blob, but the properties of items are encrypted separately, if the encrypted export format has anything to do with the database structure
Jul (they/she)
in reply to WhyJiffie • • •Dultas
in reply to Jul (they/she) • • •Jul (they/she)
in reply to Dultas • • •fira
in reply to RotatingParts • • •DaGammla
in reply to fira • • •PrivacyDingus
in reply to DaGammla • • •Howdy, I work at Proton, this is incorrect: proton.me/blog/proton-non-prof…
A nonprofit is the largest voting shareholder of Proton.
Proton is transitioning towards a non-profit structure
Andy Yen (Proton)DaGammla
in reply to PrivacyDingus • • •PrivacyDingus
in reply to DaGammla • • •shortwavesurfer
in reply to RotatingParts • • •Keepassdx (AOSP, spydroid)
Keepassium (SpIOS)
Carlos Solís
in reply to shortwavesurfer • • •shortwavesurfer
in reply to Carlos Solís • • •eneff
in reply to shortwavesurfer • • •Carlos Solís
in reply to shortwavesurfer • • •altphoto
in reply to RotatingParts • • •I just tested aliasvault and its pretty good. You can even just import your pre-enshitification Vaultwarden export file.
One thing I noticed though is that your entries must have a collection or else they don't export. But close to easy as pie to leave vaultwarden behind with their Nazi CEO.
onlinepersona
in reply to altphoto • • •like this
Carlos Solís likes this.
altphoto
in reply to onlinepersona • • •onlinepersona
in reply to altphoto • • •altphoto
in reply to onlinepersona • • •onlinepersona
in reply to altphoto • • •altphoto
in reply to onlinepersona • • •They website says they are not but there's is an employee of bitwarden who is allowed to contributed.
I don't know. I will be on my toes at any notion of Nazi CEO contribution or attribution.
sakuraba
in reply to altphoto • • •calm.like.a.bomb
in reply to onlinepersona • • •(des)mosthenes
in reply to RotatingParts • • •youmaynotknow
in reply to (des)mosthenes • • •You still have some time to decide which route to go. If you're on the free version, stay there, but start looking for alternatives.
Proton Pass is an option. KeePass with Syncthing works great, but it is a dramatically different and more involved workflow.
I am using both, and deleted my Bitwarden account yesterday the moment I heard about this.
Also, I can't suggest enough that you export all your credentials to an encrypted json file every now and then, and store it on an offline storage device. This is important.
like this
Carlos Solís likes this.
Bluewing
in reply to (des)mosthenes • • •n1ckn4m3
in reply to (des)mosthenes • • •Dultas
in reply to n1ckn4m3 • • •kazerniel
in reply to n1ckn4m3 • • •Not sure if all tech, but definitely the ones that just want to grow grow grow. A counterexample (so far) is the Obsidian team.
100% user-supported
Steph Ango(des)mosthenes
in reply to (des)mosthenes • • •JakenVeina
in reply to RotatingParts • • •potustheplant
in reply to JakenVeina • • •AHemlocksLie
in reply to potustheplant • • •dogs0n
in reply to AHemlocksLie • • •WireGuard 🥹
AHemlocksLie
in reply to dogs0n • • •potustheplant
in reply to AHemlocksLie • • •AHemlocksLie
in reply to potustheplant • • •potustheplant
in reply to AHemlocksLie • • •There's this wild technology called a hotspot. You can use your already authenticated device to give another device access to your services indirectly.
That level of security is exactly the same as exposing your password manager to the "fucking" internet. Not sure why you criticized it before when you (incorrectly) assumed that I was doing that.
AHemlocksLie
in reply to potustheplant • • •There's also this dated technology called a wired connection that some other dated technologies require. Since I don't get to choose every device I interact with or depend on, that's not always available.
I would disagree. A Bitwarden instance identifies itself as such to every visitor that comes by. It advertises itself as a particularly high value target. By contrast, a lot of what a NextCloud instance hosts is often personal and more valuable to the user than a hacker, so it does not become clear if there's anything of value inside.
It also decreases the attack surface of my password manager itself because there are fewer features in it that may have a potential exploit. Even if an attacker compromises the NextCloud instance, that may grant access to the file itself, but they still have to contend with the entire security of the password manager. No
... Show more...There's also this dated technology called a wired connection that some other dated technologies require. Since I don't get to choose every device I interact with or depend on, that's not always available.
I would disagree. A Bitwarden instance identifies itself as such to every visitor that comes by. It advertises itself as a particularly high value target. By contrast, a lot of what a NextCloud instance hosts is often personal and more valuable to the user than a hacker, so it does not become clear if there's anything of value inside.
It also decreases the attack surface of my password manager itself because there are fewer features in it that may have a potential exploit. Even if an attacker compromises the NextCloud instance, that may grant access to the file itself, but they still have to contend with the entire security of the password manager. No device will ever make any contact with the server for password purposes other than to sync the database file, and there's no web interface to inject a password stealing JavaScript file.
potustheplant
in reply to AHemlocksLie • • •EDIT: Forgot to mention the worst part about KeePassXC. It's vibecoded crap.
Hotspot does not imply that it needs to be wifi. You can share your internet connection via usb tethering too. (also a wild new technology, I know)
This ignores how modern internet attacks work. Hackers don't sit around manually browsing websites. Automated botnets scan the entire IPv4 address space 24/7 looking for specific software signatures or known unpatched vulnerabilities. If a Nextcloud exploit drops today, a bot will breach the server before the hacker even knows what is stored inside.
Also,
... Show more...EDIT: Forgot to mention the worst part about KeePassXC. It's vibecoded crap.
Hotspot does not imply that it needs to be wifi. You can share your internet connection via usb tethering too. (also a wild new technology, I know)
This ignores how modern internet attacks work. Hackers don't sit around manually browsing websites. Automated botnets scan the entire IPv4 address space 24/7 looking for specific software signatures or known unpatched vulnerabilities. If a Nextcloud exploit drops today, a bot will breach the server before the hacker even knows what is stored inside.
Also, advertises itself to whom? I'm not exposing it to the internet. How many reports can you find of people getting their Vaultwarden instance hacked? This is a lot of assumptions that don't track with reality.
You're putting your database file in nextcloud. That increases the attack surface of your solution, a lot.
That's *exactly *what a client for vaultwarden does...
Vaultwarden has a web interface, true. It's also true that I've literally never used it for anythin other than creating the users. I haven't opened it in years.
You're choosing a very petty and small hill to die on, dude. Just admit that you prefer doing it your way even if there are better alternatives.
AHemlocksLie
in reply to potustheplant • • •Some environments restrict USB access for security reasons. Some environments don't have extra ports to spare. Sometimes, I just don't have the right cable on hand even if the environment is otherwise fine.
... Show more...No, I'm well aware of that. I mean that when the inevitable scans come, the Vaultwarden instance will freely identify itself as such. An attacker would automate the breach if they detected my NextCloud instance and had an exploit ready, but then what? The contents are too unpredictable to have a one size fits all approach
Some environments restrict USB access for security reasons. Some environments don't have extra ports to spare. Sometimes, I just don't have the right cable on hand even if the environment is otherwise fine.
No, I'm well aware of that. I mean that when the inevitable scans come, the Vaultwarden instance will freely identify itself as such. An attacker would automate the breach if they detected my NextCloud instance and had an exploit ready, but then what? The contents are too unpredictable to have a one size fits all approach from there. Even if they scan all the servers they breach for password databases, they have to contend with the fact that they still have no means to try to intercept the password. They may have a slightly easier time obtaining the database, but cracking a huge pile of password databases is an infeasible task.
Yes, if I did it the way you want, I could avoid exposing it and allowing it to advertise itself, but then I would be unable to access it without a VPN or other networking tool.
I never said that Vaultwarden had been hacked. I said essentially that Vaultwarden is a single point of failure that I do not want to risk exposing to the wider internet, and I don't want to hide the services behind a VPN because that can complicate access. It's a little less secure, but what's the point of security if I can't actually use it myself?
Of the overall system, yes. Of the password database itself, not really. Slightly less potential security through lack of access, but with a sufficiently secure password, cracking it isn't realistic. That becomes exponentially more true if you've got a huge pile of password databases you need to crack, as would most likely be the case for anyone who breached my server.
Yes, and you're just about get to the problem I have with the client if you'd finish my sentence before you got smug with me.
And it's great that for your personal use case, that works our for you. But before you decide to act like a smug asshole, maybe consider that not every situation can resolve as cleanly as yours. There are a lot of reasons that restricting access to a VPN can at times be limiting. Sure, at home on your own hardware, not really, but some people need the same tools for different purposes in different environments.
Just think beyond your own experiences and accept that other people have different needs than you for a variety of reasons that they can't always control.
potustheplant
in reply to AHemlocksLie • • •Where are you even trying to use your password manager???? You're absolutely batshit dude. I'm not reading this wall of text.
AHemlocksLie
in reply to potustheplant • • •potustheplant
in reply to AHemlocksLie • • •You should also not be ysing a corporate laptop for your private stuff. If you do need to use it, you can do use the password manager the old way, just read from your phone and manually type it in.
Lastly, since you're proposing a corporate scenario, you wouldn't be able to install a random program on your laptop. IT would either block the installation or you'd have to explain why you're installing random programs on your work computer.
This is getting pathetic dude, just move on.
AHemlocksLie
in reply to potustheplant • • •Yeah, but some stuff kinda blurs the line, and some stuff is just useful both places. It's not ideal, but I can maintain some separation with different NextCloud users and different database files.
... Show more...Portable versions of password managers work sometimes. There are browser extensions you might be able to use. Most notably, both of these are more likely to be authorized than a VPN tunnel into my personal machines if I even need authorization for them. In some places and jobs, you might get a little influence over what gets installed, within reason, and an open source, strictly offline pa
Yeah, but some stuff kinda blurs the line, and some stuff is just useful both places. It's not ideal, but I can maintain some separation with different NextCloud users and different database files.
Portable versions of password managers work sometimes. There are browser extensions you might be able to use. Most notably, both of these are more likely to be authorized than a VPN tunnel into my personal machines if I even need authorization for them. In some places and jobs, you might get a little influence over what gets installed, within reason, and an open source, strictly offline password manager is less of a threat than a VPN connection to an uncontrolled endpoint. I might be able to get a Vaultwarden client, but then I'm back to exposing Vaultwarden to the open internet, which was what I didn't want to do.
dogs0n
in reply to AHemlocksLie • • •AHemlocksLie
in reply to dogs0n • • •dogs0n
in reply to AHemlocksLie • • •AHemlocksLie
in reply to dogs0n • • •dogs0n
in reply to AHemlocksLie • • •That's a fair point, I was mostly pointing out in the original comment that VPNs are an option that stops your password manager being exposed to the internet (though if their NextCloud IS exposed to the internet and is syncing their password db, then there is not much difference).
Plus you can tunnel traffic that needs to go to your VPS through the VPN, leaving all other traffic untouched (ie not tunneled), if you are worried about leaving it connected by accident. This would be max convenience.
AHemlocksLie
in reply to dogs0n • • •dogs0n
in reply to AHemlocksLie • • •Any password manager could be comprimised. A bug could even be installed on your system or malware. What's the difference?
NextCloud doesn't know how you open the password db, but KeePass (for example) does, so the master pass comprimise would be with that.
Specifically the syncing part being done with any tool, doesn't matter.
Who or how are you thinking Vaulwarden is being comprimised?
AHemlocksLie
in reply to dogs0n • • •dogs0n
in reply to AHemlocksLie • • •AHemlocksLie
in reply to dogs0n • • •potustheplant
in reply to AHemlocksLie • • •You need two apps though and I personally have more faith in vaultwarden being stable than nextcloud.
Glad your "fucking" password manager isn't exposed to the internet. Mine isn't exposed either since I use tailscale to access it. Your comment leads me to believe that your NextCloud instance IS exposed to the internet. Wouldn't that mean that if a hacker gets access to your account they could also get your keepass file as well?
AHemlocksLie
in reply to potustheplant • • •I just typed out a response to most of this, and rather than repeat all that, I'll copy a link here lemmy.zip/comment/26557132
A lot of it can be summed up in that compromising Vaultwarden means everything is screwed while compromising NextCloud is mainly a minor inconvenience. It provides neither information about the database's password nor any avenue to attempt to intercept the password.
AHemlocksLie
I just typed out a response to most of this, and rather than repeat all that, I'll copy a link here lemmy.zip/comment/26557132
A lot of it can be summed up in that compromising Vaultwarden means everything is screwed while compromising NextCloud is mainly a minor inconvenience. It provides neither information about the database's password nor any avenue to attempt to intercept the password.
AHemlocksLie
2026-05-19 15:16:51
potustheplant
in reply to AHemlocksLie • • •EDIT: Forgot to mention the worst part about KeePassXC. It's vibecoded crap.
I replied to that comment. You're assuming that compromising vaultwarden is somehow easier than compromising nextcloud. No idea why. Intercept the password where? I'm using a local client and only syncing the vault. You seem to be pretty unfamiliar with how vaultwarden works.
AHemlocksLie
in reply to potustheplant • • •No, I'm assuming that compromising NextCloud is less devastating than compromising Vaultwarden, so I'm taking a calculated risk that my database's password is secure enough to offset the slightly increased risk of access to the encrypted database because I don't always get to choose all the software I get to use in every environment I work with, so I might have to use the web client if I can't get the local client.
As for you only using the local client, congrats, we don't always get to choose what we use outside the home.
boonhet
in reply to potustheplant • • •Is RiiR still all the rage? Perhaps it's time to oxidize KeePass. There are a few libraries for kdbx files and at least one ready-made CLI.
nibbler
in reply to JakenVeina • • •John
in reply to JakenVeina • • •sakuraba
in reply to John • • •John
in reply to sakuraba • • •cyberpress.org/hackers-exploit…
thehackernews.com/2023/05/keep…
Hackers Exploit KeePass Password Manager to Distribute Malware and Harvest Credentials
Mandvi (Cyber Press)sakuraba
in reply to John • • •thanks!
edit: oh it's phishing via ads, you could say OBS Studio has been 'hacked' in the same way
the second case assumes your computer is already compromised, I think at that point a RAM dump with my master password would be the last of my problems
hellinkilla [they/them, they/them]
in reply to JakenVeina • • •RotatingParts
in reply to JakenVeina • • •JakenVeina
in reply to RotatingParts • • •KeePass is just an app that opens files, so yeah, you can access it on as many devices that you want yo setup file syncing with. Syncthing seems to be a popular choice.
You can setup vaults to be accessible with multiple passwords, if that fits your criteria. Me, I already share the vault with my wife, so that mostly covers the need for emergency access by someone else. If I ever wanted more, I'd probably just put some basic info into my will about how to access the file.
yuman
in reply to RotatingParts • • •if you were looking for an excuse to torpedo this abomination, here it is. hosting this gargantuan stack just for an encrypted csv file? at least the client (electron) gobbles up RAM like it's free while being bug-compatible with whatever chrome version was current half a year ago.
sadly, news ain't great on the other side of the fence - keepassXC dev is all-in on vibeshitting; latest non-polluted version is 2.7.9.; works fine and the stuff they're working on is pretty far from essential. some unknown folks forked it but who's to say what their expertise is.
never thought I'd disable my autoupdate timers but here we are. keep your eyes open.
oneser
in reply to yuman • • •Croquette
in reply to oneser • • •This is my unverified understanding of the situation.
KeepassXC team added Copilot to their workflow to manage PRs and code some basic (according to KeepassXC) stuff.
yuman
in reply to oneser • • •the dev vibecodes; I make a distinction between using the crap as a boilerplate helper and a full-blown agentic "hey computer, do this but do it super-good!". not only that, they got a super-asshole vibe as they removed claude traces from the repo and then flaunted that it's so people won't know what parts were vibeshat. "good luck finding the cutoff point", I'm paraphrasing here.
to each their own, but that's a hard pass for that fork from me.
like this
potatoguy likes this.
Jason2357
in reply to yuman • • •like this
potatoguy likes this.
potustheplant
in reply to yuman • • •What do you mean by "gargantuan" stack? I have a single docker container for vaultwarden that was very easy to set up and it uses less than 100mb of ram.
Not sure about the client claims though. I haven't really looked into it that much. Are you saying all versions of the client and extensions of BitWarden have issues?
Betinem
in reply to RotatingParts • • •Hey Login seems promising
Free for private users, hosted in germany and end2end
heylogin.com/en
heylogin
www.heylogin.commagnue
in reply to RotatingParts • • •AGD4
in reply to magnue • • •helpImTrappedOnline
in reply to RotatingParts • • •Its like AI decided that word gets the most clicks and its showing up everywhere.
BrilliantBadger
in reply to helpImTrappedOnline • • •Yeah its like those sports headlines where they try vibe you up for some trash talk
"Player A had a perfectly blunt statement about Player B"
Only to read & find out they said Player B was great, such drama lol
All just rage bait everywhere, AI or human that's the clicks plan
diaphragm w*rkplace
in reply to RotatingParts • • •Voxel
in reply to RotatingParts • • •My first 100 days at Bitwarden | Bitwarden
Bitwardendantheclamman
in reply to Voxel • • •Brainsploosh
in reply to Voxel • • •Not very trust inspiring. There's a lot of flowery words encircling enshittification.
It does claim to want to always offer a free tier, but all the new values and buzzwords are funneled towards the paid versions.
Tinkerer
in reply to RotatingParts • • •tomatolung
in reply to Tinkerer • • •The Article says:
... Show more...The Article says:
godsammitdam
in reply to Tinkerer • • •It shouldn't in theory. Worst case is if bitwarden closes source, just fork the latest current open version and use it.
Ideally, a group, either independent or joining with vaultwarden devs, can build/maintain the frontend for vaultwarden that is bitwarden.
belated_frog_pants
in reply to RotatingParts • • •sakuraba
in reply to RotatingParts • • •osanna
in reply to sakuraba • • •sudoer777
in reply to RotatingParts • • •jsnfwlr
in reply to sudoer777 • • •sudoer777
in reply to jsnfwlr • • •jenesaisquoi
in reply to RotatingParts • • •purplemonkeymad
in reply to jenesaisquoi • • •jenesaisquoi
in reply to purplemonkeymad • • •Carlos Solís
in reply to RotatingParts • • •Sensitive content