Not to flame you, but really just an HTML form was all you needed? It’s a super simple feature…

I’m attracted to it because of the posix backend. Did anyone try it? Is it stable?

For reference, https://owncloud.dev/architecture/posixfs-storage-driver/

Indeed! Before I was relying on the listing’s of linuxserver.io , yunohost , casa os , etc .

Nice write-up. I’d take this as a blueprint. Anyone can swap 3rd-party services to their like (e.g. headscale, xmpp bot on that vps, backblaze s3, etc.) and extend upon (e.g. oidc providers, mailboxes, arr suite, etc.)

A cheap VPS with headscale. Or just ZeroTier.com free plan.

Oh, fair point. Perhaps rclone.org then! :O

Syncthing. Look no further, just check the “untrusted device” so that you don’t give unencrypted data to your friend’s disk.

This! And, baby-steps: don’t go about installing every app you see. Try backup strategies, put them to test (bring service down and up again with data from backup). Play, have fun.

He asks whatever model is running behind either system to do the comparison and pastes the text. It’s full of errors, like perplexica saying farfalle doesn’t use LLM. Meanwhile, I just checked and it supports anything from ollama to groq (gpt4o, sonnet, etc.)

This post is ultra low quality.

I use anzo and as password an empty string. It’s never been guessed :p

I am very much looking for feedback on this self-proclaimed simple oidc. Authentik is not as bad as Keycloak, but from what I reckon theres still room for improvement! -fingers crossed-

This is oooold. Like in, it was superseded long agooo.

using Tor is enough meta data if you were to use it to safeguard from some actors (e.g. state). I’m just saying from the perspective of some of the hypothetical personas as defined by Tor project itself. If it were to boil this down to me, I would rather live without the correlation attacks (e.g. ISP giving me seemingly random disconnects) and just do my casual reading on cracking on the clear-net.

Plus, just connecting to Tor is very much a huge exposure imho. I’d use a VPN. Now, if I’m having a VPN, probably wireguard, why would I need Tor? Some providers grant you the ability to interconnect devices under your account. So, just run the VPN on the server. This is why I love NordLynx. It’s just like tailscale.

I might try vaultwarden myself, given that my life partner is always asking me for some platform password I already shared. Is possible to use just on LAN to sync and keep using the passwords from the android client while out of reach? I was just reading about 30-days sessions in the docs. Apparently, yes. That’s huge (for me, I’d like not to expose anything, even with VPN)

The syncthing server only gives metadata (no files, only IPs) between the devices, so they can connect to each other. And it’s self-hostable.

I said my needs. I was just sharing. Hardly understanding your normal use case of 10-50 users on a same kdbx. The best you could do is having multiple kdbx, fro subgroups of users. Since not everyone should have the master password to all those kdbx… But I am sure that if those were my needs I’d jump to vaultwarden too. That’s why I specifically added the disclaimer sentences on my post. I didn’t mean to rob vaultwarden of its value. Just pointed out the tradeoff. Your comments adds on to those tradeoffs, they’re just different solutions with different pros and cons. The user who mentioned using vaultwarden behind a VPN gave great input, I wasn’t considering that. Anyway, have a nice day.

Not to flame on anyone, and without reading the details on the specific CVE. But, to share as an advice: this reason is why I prefer keepass + syncthing for my needs. Security for a full blown web app is not trivial and has a bigger “attack surface” than a kdbx file moving p2p through my devices via syncthing.

You want a bridge. Like Jabagram or Emulsion. But there’s a limited set of features that will work. For example, reactions or group admin on telegram can’t be easily replicated over xmpp. And, in any case, we are talking more about having messages and media on both rooms, on either side, replicated. That way, users on telegram (e.g. your friend) can talk to users on xmpp (e.g. you). Reliability for bridges is not good, there are glitches and messages that doesn’t make it to the other side, whichever that is. I’d say you prefer to self-host xmpp with cherry-picked extensions, like snikket.org

Check “green blue” deployment strategy. This is done by many businesses, where an interrupted service might mean losing a sale, or a client forever… I tried it sometime witj Nginx but it was more pain than gain (for my personal use)