| date | permalink | title | description | author | header_image | tags | |
|---|---|---|---|---|---|---|---|
2018-07-29 |
/42-js-ipfs-0-31/ |
js-ipfs 0.31.0 released |
Alan Shaw |
/header-image-js-ipfs-placeholder.png |
|
Restoring IPFS magic one alakazam at a time...no we're not talking pokemon.
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>They grow up so fast 😿 #JS #IPFS 0.31 has been released into the wild with added connectivity magic dust 🧚 and support for raw leaves 🌿 in your DAGs. Just in time for the Decentralized Web Summit 2018! More info in the release issue https://t.co/QfVL7TrSte @IPFSbot #DWebSummit pic.twitter.com/Mv4RPvayA4
— Alan Shaw (@_alanshaw) July 29, 2018
Recent infrastructure changes to the nodes IPFS runs as gateways meant that they couldn't be used as bootstrapper nodes. This was bad news bears for js-ipfs since it doesn't yet have a DHT to discover content. So not being able to connect to the nodes that have a lot of the content meant the chances of js-ipfs finding content on the network took a turn for the worse.
Good news though! Brand new dedicated nodes have been provisioned that are connected to the gateway nodes and can be used by js-ipfs to bootstrap itself as well as, get this, preload content you add to IPFS! That's right, when you add stuff to your IPFS, the preload nodes are prompted to slerp it up automatically so that it can be shared instantly with other IPFS nodes on the network.
Raw leaves are much healthier for you because they don't lose their vitamins during the cooking process. Seriously though. They're great if you want to stream raw data (like video) out of your IPFS without the overhead of unpacking protobufs. They're also useful when you need to put your data in a data store that only deals with raw data, like a URL.
We have these now! Just pass --raw-leaves=true when adding content to IPFS and leaves of the DAG(s) you create will contain just the raw data.
- A new configuration property
preloadhas been added to the options provided to the IPFS constructor. Content added to IPFS using the following APIs will be automatically preloaded on a set of IPFS nodes. To lean more about how to configure this feature, check the IPFS constructor docs.dag.putblock.putobject.newobject.putobject.patch.*files.add*files.writefiles.mvfiles.cp
- The
--raw-leavesoption has been enabled forfiles.add
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 wantedlabel 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.