How can you ever learn the risks of exposing ports if all answers are “if you don’t know you shouldn’t do it”?

The post explicitly recommends ONLY exposing the wireguard port, not 80/443/22 which one should usually not do anyways. Very different things!

Clippy was the pretext not the goal

Yeah it’s good to have a system separate from the main server. It’s always so frustrating having to debug wireguard issues cause there’s some problem with docker

Ssh behind a wire guard VPN server is technically more secure if you don’t have a key-only login, but a pain if the container goes down or if you need to access the server without access to wireguards VPN client on your device.

And the company came under fire again in 2018 after The Wall Street Journal revealed it was allowing third-party developers to trawl users’ Gmail inboxes, to which Google responded by reminding users it was within their power to grant and revoke those permissions.

So you can remove those permissions, just that it’s enabled by default. Shitty design, but it’s not mandatory to enable those, just like how you are not forced to use edge when you get a Windows computer.

Mullvad is in a 14 eye yet is extremely respected in the community.

Use syncthing to sync and monitor your backups.

Syncthing backup server for your important files.

Cloudflare, namecheap, GoDaddy, domain.com, they all offer dns I think. Some of them are supported by Dyndns; you can find a list of supported providers.

So they profit from high-profile commercial users to subsidize the free tier (proxy, tunnels) and cheap DNS. What’s wrong with that? It’s not like we absolutely need those (proxy is nice but you can use vps, tunnels are also offered by ngrok).

Cloudflare

I tried using it a while back but went back to Mail app. Will try again, esp since I’m planning to move to Ubuntu as the main os.

Any outlook alternative that doesn’t look pre-dotcom? I really liked the Microsoft Mail app for its simplicity and the ability to have multiple inboxes, it’s a shame it is being replaced by outlook.

But the protocol has already been published and there’s not much changes needed (except maybe the quantum layer?). Charging a custom license would only push the others to develop a different protocol, one that might not be as private compared to Signal.