Nice, thanks; that’d be totally fine by me for now!

Why does this smell like a data trap? Haha… Do you operate this? TBH, I really don’t know a lick of how this stuff works, which is why I’m asking around…

Wait, I don’t understand. Why do you need to do so much account-sharing? I never had half of that… and if connecting is just once in a blue moon, then it shouldn’t need something like group creds anyway, right?

Oops, I thought you were talking about long-term storage of files in general, like videos and docs or something, not a password database! Never mind.

It doesn’t need any hardware that I can think of, but yeah, that’s true: one would need to do a lot of DIY.

Fair. I’ve clearly not worked at a place like this before!

Oh, well, I’m talking about not having to password-lock and unlock your stuff constantly. For long-term storage, sure, that’s fine; anything else would be way too tedious, though, no? I guess it depends on your use case and if you could locally automate the locking and unlocking or something.

Solid question; there are only third-party apps. A recent discussion in !syncthing@lemmy.ml led me to most recently adopt BasicSync, which is incredibly low-profile and is probably the closest thing we can get to it.

However… if you want to get as pure as possible, you can apparently run Syncthing’s Linux version directly in Termux on Android without the need for a dedicated Android app. There are also entire alternatives to Syncthing like syncspirit (which can also be run through Termux and which I’m considering trying as well).

Off-topic: how is Password Store better than KeePassXC?

Right, and it has a neat merge-database feature anyway, so no excuses for those holding back!

But your argument falls apart against something like Syncthing’s discovery networks combined with send-/receive-only folder types, which use no cloud yet allow the automatic, passive propagation of file updates to different users’ devices… right? No cloud, no self-hosting, yet automatic syncing across multiple devices…

I don’t know if their behavior over the transition was ever explained but at least it was legit, last I read.

Are you calling me a liar? That’s pretty weird; it’s not like I’m telling you to stick to passwords while I move to passkeys. With that said, though, get Bypass Paywalls Clean (Mozilla-only, as far as I know) and you’ll never see another paywall again. I forgot about having that.

Just don’t let Microsoft or Apple tie them to your device. You don’t have to do that.

The problem is that this is where it’s eventually going to lead to.

Hmm, interesting, though isn’t that a fault of the organization not having an account-linking system so that each person could have their own credentials but can still access the unified content? This workaround seems… flimsy, unless I’m not picturing a legit scenario in which no other method is as good, or something.

Whoa, thanks. I had no idea this was a thing…

You don’t need to self-host at all! Daisy-chain your needed files via Syncthing and Syncthing-Fork. That’s literally what I do with KeePassXC and KeePassDX, keeping everything offline.

Okay. You first.

What is “collaboration” in this context?

They’re also dragging their feet on passkey support

As… they… should, forever.

Syncthing is the way to leave Google Drive, etc.