They all want all of the poor people dead. They are wagging war on us.
this post was submitted on 15 May 2026
544 points (99.1% liked)
Selfhosted
50711 readers
999 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
For once ADHD preventing me from completing a migration is a boon, I guess I'll move back to keepass
Ah shit. Here we go again!
Can anyone say “Enshittification”!
Enshitification coming right up!
Move to KeePassXC or its recent LLM-free fork while you still can, because at some point Bitwarden is going to try to go closed-source again.
Oh crap, how's KeePass got an LLM involved‽ Time to look into this now...
I did find https://codeberg.org/ChiPass/ChiPass , but it looks like a very new project.
Once again, enshittification by the fucking suits.
Early on I decided to use only KeePass for full personal control instead of an online service. Didn't regret making that decision.
Fuck
Vaultwarden here I come
No, KeePass. Fully open source, no cloud involved in any way, unless you want something to sync your data (the server only ever sees your encrypted database - all encryption and decryption is done locally). You can also host your own sync server using any of a variety of different protocols.
Going to need to work on migrating
@palmtrees2309@lemmy.world
Yep. Seconding this!
KeePass + Syncthing is the best.
Back up the database(s) regularly. (Syncthing can also retain x number of versions and things like that, but also do your own 3-2-1 backups.)
You can use something as simple as a Pi, or an old laptop, or even an old phone if you get creative, as an always-on syncthing server to keep them synchronized. KeePassXC even has a fancy integration with Firefox, so all you gotta do is unlock your database and click autofill on websites.
Yup, been doing this combo for 5-6 years now.
I use KeePassXC on desktop and KeePassDX on Android. No issues whatsoever.
I do have a NAS so that's my "always on" device for Syncthing. Everything syncs up within like 10-15 seconds when a device connects.
I also use a key file as a pseudo 2FA that I keep on a flash drive, so you'd need my master password and my key file to unlock the database.
I use KeePass + KeeAnywhere. KeeAnywhere will sync with a wide variety of cloud storage providers. Or your own S3 data bucket server (can be self hosted or on Amazon), if you prefer. Does pretty much the same thing though with versioning. Auto filling in Firefox is done with KeePassHttp-connector on the Firefox side and the KeePassHTTP plugin in KeePass. Similar to what you describe.
load more comments
(1 replies)
Jesus, I'm tired of switching password managers.
KeePassXC + KeePassDX is probably the best option, with the downside of no way to sync easily (syncthing is probably the best option there)
I might switch back at some point, been getting frustrated with the bitwarden extension performance always being so poor.
My first password manager was KeePassXC.
Hooked it up with Syncthing, and I've never had issues aside from the occasion database duplicate.
Right, and it has a neat merge-database feature anyway, so no excuses for those holding back!
I use KeePass with KeeAnywhere. KeePass can natively sync over network share, FTP, or WebDav. With plugins, it can sync over SSH, FTPS, Amazon S3 compatible buckets (including open source compatible versions you host yourself), Azure, Box, Dropbox, Google Drive, OneDrive, and more.
Yeah the performance is what made me install the desktop app, but then it's 1gb in size
load more comments
(9 replies)
load more comments
(32 replies)
Has Vaultwarden said anything yet? I imagine that, if necessary, given that bitwarden's client is still open, at the point they choose to try and close it, we, the users, can fork it and establish it for vaultwarden, correct? Or, maybe even the vaultwarden team will think about forking it themselves and making a light client as well to pair with the current server.
But Vaultwarden can exist without "leeching" they just haven't needed to yet. That's more symbiotic than parasitic. The parasite class just took over Bitwarden after all.
load more comments
(7 replies)
Glad I started using Vaultwarden a while back. Just need to find better apps for android and Firefox I guess because I'm guessing they're going to try to break compatibility.
vauktwarden needs bitwarden though
They responded on reddit and walked some of it back as an "oversight": https://www.reddit.com/r/Bitwarden/comments/1tdvnh7/comment/olznwcv/. Allegedly, I'm too lazy to verify.
A change that would require intent to make is not a mistake or oversight.
This sucks. I committed to Bitwarden years ago and now am going to have to switch before they lock me in the garden.
They also haven’t addressed the removal of inclusion and transparency from their goals.
EDIT: They did. They said it’s “less of a priority”. The article I shared has been updated. I smell corporate bullshit though. “Oversight” this, “priority shift” that, they’d have to work hard to gain any trust back.
view more: next ›