I want to host a HTML file under a domain I own, without needing any central server/organization and without a static IP.
What are my options?
So far, IPFS seems the best. I can put my file on the decentralized network by running my own node and use a TXT DSN entry to point that to my domain (https://docs.ipfs.io/how-to/websites-on-ipfs/link-a-domain/#domain-name-service-dns)
Any other alternatives?
I'm looking for something simpler and accessible (explaining IPFS, even for techy people, takes a lot).
boosts appreciated ✨
That depends on Cloudflare, right?
I want to avoid central servers / organizations like Cloudflare, GitHub pages etc. I'm looking for something as decentralized as possible.
@jonatasbaldin note that doing it this way makes gateway.ipfs.io a single point of failure for your website. If it goes down, your website goes down, and fixing that requires you to modify your DNS, which might take a while to propagate.
I think combining these approaches could be a winner. Hit me up if you'd like to test it out.
@jonatasbaldin also, the `gateway.ipfs.io` CNAME thing relies on CNAME-at-apex-domain, which is non-standard and basically only supported by CloudFlare:
DNS is a more mature space with somewhat stricter rules and with way more resilient infrastructure (both in technical and political sense).
For example, DNS anycast cloud operators would not even *dream* of "blocking" a zone delegated by a registry they service. Web CDN operators do an almost exactly analogous thing for websites they front for on a regular basis.
DNS DDoSes happen, and sometimes they do create disruption, but the sheer size of traffic needed to disrupt DNS operations of any reasonably-sized provider for long enough to cause TTLs to lapse and create actual problems for end users is... orders of magnitude higher than traffic that brings down a standard WordPress site (if you have a WP site, link it on fedi and see it struggle).
@neil @jonatasbaldin finally, mitigations against certain (let's call them that) attacks are already deployed with DNS. DNS-level censorship is seriously threatened by DNS-over-HTTPS and DNSSEC, for instance. Both Chrome/Chromium and Firefox deployed DoH already, meaning that state-level DNS censorship is becoming difficult.
At the same time, state actors can now easily afford the hardware to do DPI on the (unencrypted!) TLS ClientHelo and thus just drop HTTPS requests that they don't like.
Finally, cost of DNS hosting is non-existent. Cost of HTTPS hosting for a website that needs to be able to handle traffic spikes and DDoSes can rise surprisingly fast.
Perhaps I should blog about this?
Of course if the registry/registrar decide to (or are forced to) take a website down, the website goes down. But that's also true for any provider of any service, web hosting included.
On the other hand, it became much harder to censor a site on DNS level *without* registry/registrar cooperation. Azerbaijans and UKs of this world can't just block/alter queries, since more and more of them go through DoH.
what do you think of corporations pushing the boundaries of RFCs like that?
if you haven't told me, it would take a long time to realize that the combination of CNAME-apex-domain is only valid at Cloudflare
@jonatasbaldin it's a classic Embrace-Extend-Extinguish, and I have no love for it at all.
And what I find as problematic is FLOSS projects like IPFS buying into that and promoting that.
I think more providers are starting to support CNAME-at-apex, but that's going to cause pain:
That's one of the reasons I started LibResilient - to have a website on IPFS without relying on DNS hacks or going through centralized gateways.
@jonatasbaldin The other options I know of are Dat & (if you loosen criteria slightly) Tor Hidden Services. But I don't think those work outside of unmodified web browsers.
The Tor recommendation only does away for the need for a static IP address, making it easier to host the site at home.
@alcinnz yeah, I want things to be accessible enough, you know?
a solution that could be as simple as GitHub pages or Netifly 🤔
@jonatasbaldin have you considered hypercore (A.k.a DAT)? https://hypercore-protocol.org/
It's the foundation of Beaker Browser.
I personally host my website on https, but also on IPFS and Hypercore.
The main problem with those two technologies is the need of a specific client wich is not common yet.
Anyway, someone has to use a tech to make it reach mainstream.
@j thanks, I'll check it out!
I like ur last phrase, on mainstream tech. I really hope I can find a solution as simple as GH pages or Netifly, but I believe we are a long way from that 😓
INDIEWEB.SOCIAL is an instance focused on the #Openeb, #Indieweb, #Fediverse, #Mastodon #Selfsovereign #identity (#SSI), #Humanetech and #Calm technologies evolution.