min

joined 1 year ago
[–] min@lemmy.sdf.org 4 points 1 week ago
[–] min@lemmy.sdf.org 1 points 2 weeks ago

Do note, because it's using email, the recipient and sender are not private, along with the time, and probably the relative size of the messages.

The specific content of each message should be private as long as the encryption is done well. I haven't looked at it so I don't know if it implemnts safeguards to verify who you're messaging with (besides using the email address) and I don't know if it uses PFS (Perfect Forward Secrecy) to protect against a key getting compromised.

[–] min@lemmy.sdf.org 3 points 3 weeks ago (2 children)

https://github.com/rsmsctr/vaultwardenGuide

It doesn't cover backups though. It uses Caddy instead of NGINX, and it uses DuckDNS to point a subdomain to your private IP address of your Vaultwarden server, so it will only be accessible in your LAN.

[–] min@lemmy.sdf.org 3 points 4 weeks ago (1 children)

Maybe surprisingly, it is actually a technique to limit interruptions, specifically because you are only working on your current task for 25 minutes. It makes it much easier to not switch tasks in the middle because your next time to switch tasks is less than 25 minutes away. For example, if you're in a task writing a report and you remember that you were supposed to send an email, you write down the email task to do later and don't worry about it because if it's important than you will pick it for your next pomodoro. This allows you to stay focused on the report you're writing for this pomodoro.

[–] min@lemmy.sdf.org 8 points 4 weeks ago (1 children)

I've been researching zero-trust for my homelab recently and I'm considering OpenZiti instead of Cloudflare since I think it can all be self-hosted. The BrowZer from OpenZiti is especially interesting to me. The fact that I'm behind CGNAT is a hurdle though.