Hacker News new | past | comments | ask | show | jobs | submit login

Indeed, I do remember why Beaker dropped IPFS support. Basically, it comes down to the URL structure and how we structure them in the IPFS ecosystem, which is not super easy to integrate with browsers today. There is some logs about the discussion over at Github: https://github.com/beakerbrowser/beaker/issues/2

There is a open feature request for (re)adding IPFS support to Beaker as well, if someone feels a bit experimental with adding IPFS support to a Electron application: https://github.com/beakerbrowser/beaker/issues/480 Reach out to me if you feel interested in helping out and I can point you in the right direction. Email is in my profile.

Re: IPNS is currently slow: Yes, it is. Apologies for that, it definitely has to get faster to be really useful. The network has grown a lot and we are working on improving the performance of IPNS, both for adding the records and reading them. Currently the adding of records is slower than reading, as reading now uses pubsub to push updates and making it a lot faster than before.

We do have more solutions in mind for IPNS performance and still doing research on the best way of implementing them.

If you haven't seen IPFS pubsub before, I urge you to take a look, as it gives you the ability of doing communication with a large number of nodes cheaply.

So while IPFS started out as a distributed file system with naming on top, we now have more functionality for handling dynamic data and working on making it even easier to build applications with just IPFS.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact