Things have been going well for me, using docker-mailserver.

I followed the setup guide, did everything in the DKIM, DMARC and SPF documentation page. The initial setup required more involvement from me than your standard docker-compose self-hosting deployment, but I got no issues at all (for now, fingers crossed) after the initial setup : I never missed any inbound e-mails, and my outbound e-mails have not been rejected by any spam filter yet.

However, I agree with everyone else that you should not self-host an important contact address without proper redundancy/recovery mechanism in case anything goes wrong.

You should also understand that self-hosting an email address means you should never let your domain expire to prevent someone from receiving emails sent to you by registering your expired domain. This means you should probably not use a self-hosted e-mail to register any account on services that may outlive your self-hosted setup because e-mail is frequently used to send password reset links.

I will definetly look into this. I’ve been using tube archivist for a while now, but it eats so much RAM (especially the Elastic search dependency IIRC)!

I did not try it out yet, but I will make sure I do. I love a lot of things about the approach you described

I admit they hid it pretty well, but look again. Radworks, the entity behind Radicle, is a DAO, which makes anything they do related to cryptocurrencies

Can you elaborate?

I was under the impression that there was some kind of consensus around rust being one of the safest languages to use. However, I’ve seen comments about rust being bad pop up in a few threads lately but they never explain why they think so.

For anyone who wonders, this is related to cryptocurrencies

I had a great time using Qubes. It made me learn about the Xen hypervisor and CoW filesystems.

However, if OP complains about build times being too long on their CPU, I’m not sure they will get Qubes running smoothly on the same hardware. I’m especially worried about every VM besides dom0 being software rendered.

Github is not really independent from Git, it’s a git provider. (you could see it as Github being to Git what Gmail is to e-mails)

Each time you send a packet over the internet, several routers handle this packet without touching the source and destination IP addresses.

There is nothing stopping him from configuring the VPS in a way that forwards packets from the home server, rewriting the destination IP (and optionally destination port as well) but leaving the source IP intact.

For outgoing packets, the VPS should rewrite the source (homeserver) IP and port and leave the destination intact.

With iptables, this is done with MASQUERADE rules.

This is pretty much how any NAT, including ones behind home routers, work.

You then configure the homeserver to use the VPS as a gateway over wireguard, which should achieve the desired result.

Not so long ago, while trying to turn a side project of mine into a package, I bind mounted my home directory into a chroot.

Guess what happened when I rm -rfed the chroot…

The readme mentions “transcription time on CPU” so it’s probably running locally