There’s always vaultwarden.

Especially on mobile.

Mumble is another strong, open source, self-hosted option.

Disagree. I prefer XML for config files where the efficiency of disk size doesn’t matter at all. Layers of XML are much easier to read than layers of Json. Json is generally better where efficiency matters.

They were legally not allowed to as part of an agreement to not be s monopoly and allow competition.

This is the biggest reason I don’t own a smartwatch yet. I want to own my own health data, and not have it locked into Fitbit or Google.

You can use both on your phone to sync with each of them, yes. Immich and Google Photos won’t communicate directly (and don’t need to).

It’s a good idea in case your Google account ever gets banned. (Say you issue a chargeback against Google Wallet or something.)

I have a lot of experience with both. As a tech savvy user, I slightly prefer KeePass. Syncing between devices is slightly more painful, but I find it to be more reliable, and it doesn’t have the attack surface that Bitwarden does. (While encrypted, Bitwarden still really wants a web server and a local database connection.)

VaultWarden is probably better for those who can’t be bothered to move a file around and want direct browser integration. With KeePass when you need a password, you’ll make sure the username has focus and then alt+tab to KeePass and hit “autofill”. Some sites won’t take “username{tab}password{enter}” and you’ll have to customize the configuration.

VaultWarden is better at prompting you to add new passwords. I prefer the workflow that’s encouraged by KeePass, where you open the app first and use the app to open the URL. (You can do this in VaultWarden too, but it’s less obvious.)

For images I highly recommend Immich. It’s the Google Photos equivalent, and it works excellently.

I use SyncThing for documents, but photos from my phone go to Immich.

VaultWarden if you want all the features without paying $40/year.

Otherwise Bitwarden will either allow you to self-host OR allow you to share passwords with one other person (using their server), but not both.

VaultWarden just unlocks all the features.

I don’t agree, but it’s a unique, interesting thought that I can upvote.

If my job didn’t pay me, I would have certainly burned out years ago. For one, I’d need another job.

Fewer people will get into unraid. Natural churn will happen. The OS will slowly die, and as it dies usability will get worse.

Not many people are going to choose the subscription Linux over a free Linux.

And the bittorrent-like concept has issues that many people won’t want to subject themselves to.

How many people are seeding what videos now?

I am a dev, but not a Rust dev.

Rust, Go, and C# look like the future to me. Everyone is moving to strongly typed, explicitly typed languages for a reason.

Rust is as fast as it gets, and much much safer and easier than C or C++ at the cost of slightly odder syntax than higher level languages.

Microsoft has done great things with C# and open source and multi-platforming. It’s the easiest, quickest, safest way to develop business applications. The performance is really pretty good until you compare it to Rust.

Go is between the two, but probably a little closer to Rust.

Other languages will stick around the same way Fortran has still been in use despite being deprecated for 30 years. But really nobody should be developing anything new in PHP.

While I generally agree with you, you can’t call that a strange take.

Their views are concerning, but so far I haven’t seen them trying to force their views anywhere yet. And having a fork as a real option helps mitigate a lot of that risk.

I’m certainly okay with the $50k/year they’re trying to make for working on this full time. I’d be fine with triple that.

If it gets out of hand, we have options. They’re aware of that (in fact offered it), and have been acting appropriately afaik.