Because you either need an announce URL or publishing your torrent to the DHT for your friends to be able to peer with you.

Seeding copyrighted material using a public announce URL or the DHT will get you in trouble in most western countries.

ENS stands for Ethereum Name Service

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.

Downvoted for cropping out the reference to the original…

At this point, I don’t know if you are trolling or not. You keep saying that this is nothing like timezones, while describing something that really looks like timezones to anyone else reading it.

Do you suggest we all use one unique time, regardless of local solar time? Or do you suggest we all use our own local solar time, based on each person’s exact longitude on the globe, regardless of borders and current timezones ?

Are you suggesting something like continuous timezones? Thanks for bringing this nightmare to a whole new level! :)

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

Lol I almost fell for it. I just Ctrl+F’d the link, no occurence of “tab” in the press release :D

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.

What do you mean? Are you talking about the hash being spoofed?