Rough notes on building a serverless application runtime on top of ipfs - p2p applications are much more complicated than I assumed, especially if you want them to work in the browser (less reliable, no tcp) - IPFS has done a lot of the work for us: libp2p, discovery, gateways, highlevel clients that work in node, browser and golang. - My initial goal was to build an application runtime for replacing this microblog (currently I run a server for it) - Realizing this was a larger effort than I assumed, and since the use case is more theoretical/personal than general, I want to wait until there is more interest from developers so we can collaborate The more general goal: - was to make it easy for me to host my microblog, so I could spend less time thinking about the hosting, and also so I could distribute it as an application for end users to run their own blogs - Essentially, I wanted to make the server part easier, and with ipfs I was hoping to get rid of it altogether - Towards this end, I'm going to refocus on an idea called "deploynow" which aims to make it easy to package existing software and run it in containers on an end-users device, but without them having to learn about docker. To learn more start here: https://github.com/ipfs-examples/helia-examples/tree/main/examples/helia-101 Reading Links: - https://docs.ipfs.tech/reference/js/api/ - https://docs.ipfs.tech/reference/http/gateway/ - https://docs.ipfs.tech/reference/kubo/cli/