js-ipfs 0.25.0 blog post

[daviddias]

No description provided.

[mishmosh]

"some careful refactoring"

[mishmosh]

"your own custom repo, you can now:" (if this is a new improvement/simplification?)

[mishmosh]

Is this a good time to add our "contributor thank you" section? Can be simple to start, e.g.:

Thank you to the ## contributors to this release, and to all past and future contributors of jp-ipfs 🎉:
@username1 @username2 etc.

[daviddias]

We can create a list but at the risk of being incomplete. (Which would be a bummer if someone is left out).

I really want to do that though, to make that work extremely well it would be important to have:

• lint the commit messages to follow the same standard
• have a tool that tracks all the contributions in the dep tree

[mishmosh]

That makes sense, I'm ok with punting until later. Maybe we can hack on it during lab week :)

…

On Wed, Jul 12, 2017 at 12:11 PM, David Dias ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In content/post/28-js-ipfs-0.25.md <#128 (comment)>: > + +The JavaScript implementation of libp2p received a lot of love recently, including the addition of Tutorials. You can consult all the details on the Log entry of libp2p's Captain.log - libp2p/js-libp2p#6 (comment) + +### 🏎 SPDY is out of the mix and there goes browserify-zlib special shimming. + +SPDY has been removed from the default browser bundle in favor of supporting `libp2p-multiplex` only. SPDY was the Stream Muxer of js-ipfs since almost the beginning, but since go-ipfs never got a complete implementation of SPDY, we ended up switching to `libp2p-multiplex` to guarantee interop between implementations. What this means is that you will continue to see the interop, but now your browser bundle will be significantly lighter. + +### 📞 wrtc, the WebRTC module for Node.js is now optional + +`wrtc`, a module that enables js-ipfs Node.js nodes to speak WebRTC, has been excluded from the default list of modules so that Linux users can have a better time when using js-ipfs natively. You can still bring it back and now not only use `wrtc` but you can also use `electron-webrtc`, the other WebRTC module for Node.js See how to achieve that in the project's README - https://github.com/ipfs/js-ipfs#advanced-options-when-creating-an-ipfs-node. + +Note, this doesn't change the behavior in the browser. Browser nodes will still continue to use WebRTC by default. + + +If you run into any hurdles, please open an issue on [ipfs/js-ipfs/issues](https://github.com/ipfs/js-ipfs). + We can create a list but at the risk of being incomplete. (Which would be a bummer if someone is left out). I really want to do that though, to make that work extremely well it would be important to have: - lint the commit messages to follow the same standard - have a tool that tracks all the contributions in the dep tree — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#128 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPtpCWMpWY2USRh-mUR-x0qJc7Npb0mks5sNPAZgaJpZM4OVQjf> .