| ▲ | bullen 2 hours ago | ||||||||||||||||
I would say: 1) Use HTTP (secure is not the way to decentralize). 2) Selfhost DNS server (hard to scale in practice). 3) Selfhost SMTP server (also tricky). 4) Know and backup your router (dd-wrt or iptables). JSON over HTTP is the way. XML is not bad for certain things too; even if I understand the legacy of abuse. | |||||||||||||||||
| ▲ | zrm 2 hours ago | parent | next [-] | ||||||||||||||||
> Use HTTP (secure is not the way to decentralize). This doesn't seem like useful advice. If you're going to use HTTP at all there is essentially zero practical advantage in not using Let's Encrypt. The better alternative would be to use new protocols that support alternative methods of key distribution (e.g. QR codes, trust on first use) instead of none. > Selfhost DNS server (hard to scale in practice). This is actually very easy to do. | |||||||||||||||||
| |||||||||||||||||
| ▲ | pixl97 2 hours ago | parent | prev [-] | ||||||||||||||||
1) so how do you validate the http the client receives is the http you sent? | |||||||||||||||||
| |||||||||||||||||