Comment on Concerns Raised Over Bitwarden Moving Further Away From Open-Source

• jasep@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

  The downside to Keepass is it is not self hosted, as in it’s designed to run locally per device. Yes, you can put the database file on a network and have multiple clients from different operating systems access the database, but you will end up with collisions and database issues. Ask me how I know.

  Running cross platform Keepass (and it’s various forks) is absolutely doable, but it is not as seemless as BitWarden. I’m running self hosted VaultWarden and I’m hoping to run it for a long time as it’s much easier than Keepass.

  source

  • thayerw@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

    For what it’s worth, I only ever had sync issues when sharing a database between devices with transient connectivity. Once I introduced an always-on instance of Syncthing, collisions were a thing of the past.

    We’ve been using KeePass trouble-free for many years now, sharing a single database across more than 6 devices, with frequent use and modification.

    source

    • clmbmb@lemmy.dbzer0.com ⁨4⁩ ⁨weeks⁩ ago

      Syncthing just announced they won’t develop their Android app anymore. 🫤

      source

      • thayerw@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

        Noooo! Ugh, that’s so disheartening to hear but I can’t fault imsodin for his reasons. I sincerely hope that someone steps up to the plate, even if only for the F-Droid releases.

        For anyone else interested, the discussion is taking place here:

        forum.syncthing.net/t/…/7

        source
      • gazby@lemmy.dbzer0.com ⁨4⁩ ⁨weeks⁩ ago

        Ah shit, I hadn’t heard that. Another one bites the dust because of Google’s Play Store insanity. Maybe SyncThing-Fork will continue? 🤞

        Source: forum.syncthing.net/t/…/23002

        source
      • hunkyburrito@lemm.ee ⁨4⁩ ⁨weeks⁩ ago

        While the official syncthing-android is no longer being updated, syncthing-forksyncthing-fork is still going strong

        source
    • gazby@lemmy.dbzer0.com ⁨4⁩ ⁨weeks⁩ ago

      KeePassXC here, ÷1 for the exact same issue with the exact same solution (ST with an always-on “server”) 👍

      source
  • PureTryOut@lemmy.kde.social ⁨4⁩ ⁨weeks⁩ ago

    Eh, I have used KeepassXC over multiple machines using NextCloud to sync it for years now and have never had any conflict.

    source

    • somenonewho@feddit.org ⁨4⁩ ⁨weeks⁩ ago

      This. I have been running it the same way for some time now. Even if you change something on one machine and something else on another nextcloud will just happily inform you of the conflict and then you can open both databases and cherry pick. Never had corruption issues.

      source