Sometimes you even get to show off the cool, useful shit you built for them!

Sometimes I’ll copy paste the error message back to them. Apparently it works better when it’s in a text message.

It’s not impossible. There are a lot of crypto grifters who have been prepping to scam the American government.

I realized immediately, read the comment, and then went back to look for a deeper meaning. It wasn’t there.

I realized immediately, read the comment, and then went back to look for a deeper meaning. It wasn’t there.

At the time, everything HTTP was supposed to be public.

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.

Sure, but how much of that is justification and backpedaling?

If it’s worth a commit, it’s worth a description. “Address vulns” “fix config” “remove files”. It doesn’t take much. Even if it’s just “more address vulns”.

But shouldn’t be. How hard is it to summarize your work in a few words? Even a bad description is more memorable than a hash.

I’d rather add more Jira stories.

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.

For what? To keep track of who’s drinking coffee? Are you charging for coffee?