date | permalink | title | description | author | header_image | tags | |
---|---|---|---|---|---|---|---|
2018-09-11 |
/43-js-ipfs-0-32/ |
js-ipfs 0.32.0 released |
Alan Shaw |
/header-image-js-ipfs-placeholder.png |
|
A pinch of IPNS, some chunking of files and you'll have a delicious IPFS stew for supper.
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>Better head over to your nearest modules'R'us store because #JS #IPFS 0.32 has hit the shelves. We got #IPNS, custom chunking & loads more goodies. Enjoy 🍦! P.S. more info here: https://t.co/sU0GorC0l7 … #libp2p #fingerprinting #rabin pic.twitter.com/PcPXS8fVMl
— Alan Shaw (@_alanshaw) September 11, 2018
IPNS has it's foot in the door, and it's coming in! In this release IPNS works for your local node. It means you can now publish records to your local repo and read them back. There's still some way to go but you know the saying right, "from small beginnings comes great IPNS"?
In preparation for IPNS landing, we've rolled out a partial implementation of the resolve
command. The idea of the resolve command is to figure out the underlying hash of the content referred to by an IPNS name or an IPFS path.
The new resolve command can resolve paths like /ipfs/QmRootHash/path/to/file
to /ipfs/QmFileHash
and will soon be able to deal with IPNS names in an upcoming release.
We made it even easier to create your libp2p bundle! If you're looking to create a completely custom libp2p bundle then you can now pass a function in place of your libp2p config which should return your libp2p bundle. It's passed useful information like the IPFS node peer ID so you should be able to build your bundle exactly the way you want! You're welcome 😁
Slice and dice your DAG nodes the way you want™️. When adding data to your IPFS node you can now specify the size of the chunks it creates from your data or even use rabin
fingerprinting to create some fancy variable length chunks for better deduping.
Rabin is a native module and must be compiled on your system when you run npm install ipfs
. Native modules depend on specific languages and tools to be pre-installed on your computer and because of this has been made an optional dependency. That means that it's 👌 if it fails to install, it just won't be available to use in IPFS. If you're thinking of using rabin chunking then be sure to check that it installed properly in your install logs.
Check out the docs for the files.add
chunker
option for more.
- Added
ipfs.name.publish
andipfs.name.resolve
. This only works on your local node for the moment until the DHT lands. API docs can be found here. - Added
ipfs.resolve
API. Note that this is a partial implementation allowing you to resolve IPFS paths like/ipfs/QmRootHash/path/to/file
to/ipfs/QmFileHash
. It does not support IPNS yet. ipfs.files.add*
now supports achunker
option, see the API docs for details
Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:
- Check the issues with the
help wanted
label at the Ready column in our waffle board - https://waffle.io/ipfs/js-ipfs?label=help%20wanted - Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/pm/#all-hands-call
- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
- Join the discussion at http://discuss.ipfs.tech/ and help users finding their answers.
- Join the ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 and be part of the Sprint action!
The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.tech. We are also available at the #ipfs channel on Freenode.