I really like this article from Rohan D "Every Phone Should Be Able to Run Personal Website". In it, they make the convincing case that phones are perfectly capable of hosting websites and - if we want more people to escape the walled-gardens - this could be a good way to get people back into […]
@Edent Great post, if only our telephones could be the general purpose computers they were born to be!
In practice, I think you've hit the nail on the head with the protocol and security issues. You can 100% self host on a #Pinephone. Just not on anything that will run your banking apps.
There's a need for a new protocol approach that includes buffering if you want to cover the downtime/out of signal or battery case. One neat partial solution would be failover #DNS to a self hosted backup.
Here’s an overview of the Let’s Encrypt DNS challenge type in case you haven’t seen it: letsencrypt.org/docs/challenge-types/#dns-01-chal…
Basically, when Traefik goes to request or renew a certificate, Let’s Encrypt tries to look up a special DNS record on your domain so you can prove that the request for the certificate is legit. To make that work, Traefik first hits your DNS provider via API and temporarily inserts that special record so it’s there when Let’s Encrypt performs the lookup for it. In my particular case, I’m using self-hosted PowerDNS and it’s built-in API (configured to only respond via a Wireguard tunnel). But you don’t have to self-host DNS for this to work… Traefik has a long list of supported providers: doc.traefik.io/traefik/https/acme/#dnschallenge
What VPN do you use to hide traffic from your ISP? (upload.wikimedia.org)
Docker & Reverse Proxies (kbin.social)
Mooching off this other post...