On conflict keep both of them. Bitwarden’s usecase (compared to other sync products) has the leniency of offering 2 logins for the same thing. So during sync, if there is a conflict, BW will update the existing entry with one of the devices (sync is done in an ordered way, no matter what the order might be), and then will create a new entry (or 6 new entries, if the same thing is modified in 6 different offline devices) for every conflict. Maybe update the name with (Offline Conflict), or maybe add a tag (when those will be available) for offline conflict.
OFC, if all the edits are exactly the same, then BW should not create identical duplicates.
First, thank you for building such a robust and secure password manager. Bitwarden continues to impress with its transparency and feature set.
One important feature that would significantly improve usability is full offline support. Currently, when the app is used without internet connectivity, functionality is limited to read-only mode. This creates challenges in restricted or offline environments, where creating, editing, or deleting vault items becomes impossible.
Enabling a true offline mode with full vault editing capabilities would bring Bitwarden in line with other leading password managers and greatly enhance usability in low- or no-connectivity scenarios.
Many users - including myself - would benefit greatly from the ability to manage vault items offline. Once connectivity is restored, the app could automatically sync any changes with the Bitwarden servers, ensuring consistency without compromising security.
I read this whole thread, but unfortunately I haven’t found an answer for my particular use-case yet. So I hope that you might have some ideas.
I’m running the Bitwarden unified self-hosted deployment on my Raspberry Pi 4 at home which works like a charm. I’ve been travelling for three months now and although I had some doubts at the beginning, I never got logged out within Bitwarden’s Android app, i.e. I could use it without any issues
What I’ve been missing, however, is the possibility to create a new vault entry while being offline during my vacation. Instead, I had to use a temporary KeePass file and do all the stuff manually after coming back home
I don’t have any sophisticated needs, I’m more on the very basic end of Create a very new vault entry or edit an existing one, and sync it when being online again back home. In my case, there won’t be any sync conflicts (since nobody else is at home and can change the online vault entry meanwhile ), etc. A simple “last one wins” approach would be totally sufficient.
As a software developer I’m fully aware that the whole topic of replication and synchronization is a beast on it’s own when looking at it with a holistic approach. So you probably have a lot of things to take into account.
Nonetheless, I’d like know what you’d suggest in this case. The very important thing for me is that everything happens offline, i.e. I neither want to temporarily move my passwords into the cloud nor I want to expose my Raspberry Pi (hosting Bitwarden at home) to the internet.
), etc. A simple “last one wins” approach would be totally sufficient.