Hosting cost: $0.
Some details: https://fabian.social/posts/2020-11-07-ipfs-blogging.html
Example: https://fabian.social/photography/2021-01-15-incidentes-vial...
If one has a super low traffic site and is already hosting themselves (whether on a home computer or VPS), what’s the benefit of IPFS? My understanding is that if a file isn’t popular, it’ll be served by your own IPFS node/pulled from your local web server, which seems redundant to me.
(I totally get the use case for popular files; it’s awesome for that!)
> Centralized personal sites/blogs become fragile and expensive while a decent(ralized) alternative (like what is in use here) is anti-fragile and inexpensive.
> The only costs are the domain registration and running my own computer (where the IPFS daemon takes less than 1% of my cpu usage and 200 MB of memory) and some bandwidth.
> The more popular something is, the more peers replicate it.
> As such more bandwidth and redundant fetch locations become available that could get the content to you (the reader) at lower latencies. (It is challenging to do a hug of death / slashdotting on such sites/blogs)
I think it would be really cool if there some super easy way to do IPFS blogging. Some GUI or CLI that you point at a repo for the source, then a host with a username, password or SSH key, a dropdown with your domain name registrar and your username+password, and finally a big "deploy" button.
DNS-link is no fun setting up and maintaining. Sure, you can write your own scripts and connect everything to a CI/CD, but for budding developers that's a lot of work.