IPFS is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we highlight some of the development that has happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on GitHub or join us on IRC (#ipfs on the Freenode network).
If you would like to get this update as an email, sign up for our weekly newsletter!
Here are some of the highlights for the January 25th sprint:
finishevent on the
createWritableStreamresult due to internal issues in streams and the way
.endis handled. So @dignifiedquire wrote this module that fixes this and now allows us to test all parts of js-ipfs in the browser using IndexedDB as the storage.
_dnslink.). This allows users to alias (using CNAME) their domain to gateway.ipfs.io while still being able to to set the dnslink to content they wish. Also, @whyrusleeping has an open PR to pull libp2p out of go-ipfs and put it into a module on gx, the IPFS native package manager. This is part of a larger effort to whittle go-ipfs down into smaller, extensible modules. Finally, @whyrusleeping did a clean up of the go-ipfs pull requests, closing all pull requests or pinging their authors for updates as needed.
ipfs mountinterface. Join in to voice your thoughts here.
Across the entire IPFS GitHub organization, the following people have committed code, created issues, or made a comment on GitHub between January 25th (noon, GMT) and February 1st. We're autogenerating this list using this tool, so please let us know if your name isn't here.
Thanks, and see you next week! If you have cool things to share for the next weekly, drop us a line in the next weekly sprint issue!