Skip to content
This repository was archived by the owner on Apr 16, 2021. It is now read-only.

Ann post for js-ipfs 0.26 #144

Merged
merged 4 commits into from
Sep 13, 2017
Merged

Ann post for js-ipfs 0.26 #144

merged 4 commits into from
Sep 13, 2017

Conversation

daviddias
Copy link
Contributor

Left:

  • Update post with tweet on release day.

Copy link
Contributor

@mishmosh mishmosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Small grammar edits, inline.
  • Love the shout outs to contributors!
  • Also really like the "Preview" section. It serves the extra purpose of calling out project priorities -- are there any issues for the upcoming improvements that could use more help? Could be a good time to invite people to contribute.

author: David Dias
---

Today, we've released js-ipfs 0.26.0. This release brings bug fixes, perf improvements, git support, http gateway and more!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use full word "performance"


# 🔦 Highlights

Here are some of the highlights for this new js-ipfs release. There were plenty more bug fixes, tiny perf improvements, doc improvements and others all across the js-ipfs module ecosystem. A really BIG THANK YOU to everyone that has been contributing with code, tests, examples and also bug reports! They help us identify situations that we miss with out tests.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spell out full word "performance"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with out -> without (one word)


With reports such as https://github.com/ipfs/js-ipfs/issues/952, we started investigating what were the actual culprits for such memory waste that would lead the browser to crash. It turns out that there were two and we got one fixed. The two were:

- browserify-aes - @dignifiedquire identified that there were a lot of Buffers being alocated in browserify-aes, the AES shim we use in the browser (this was only a issue in the browser) and promptly came with a fix https://github.com/crypto-browserify/browserify-aes/pull/48 👏🏽👏🏽👏🏽👏🏽
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alocated -> allocated (two l's)


### New InterPlanetary Infrastructure

You might have noticed some hiccups a couple of weeks ago, that was due to a revamp and improvement in our infrastructure that separated Bootstraper nodes from Gateway nodes. We've now fixed that by ensuring that a js-ipfs node connects to all of them. More nodes on https://github.com/ipfs/js-ipfs/issues/973 and https://github.com/ipfs/js-ipfs/pull/975. Thanks @lgierth for improving IPFS infra and for setting up all of those DNS websockets endpoints for js-ipfs to connect to :)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use period instead of comma here:
weeks ago. That was due to a revamp...


### Now js-ipfs packs the IPFS Gateway as well

You read it right! Now, js-ipfs packs the IPFS Gateway and launches it when you boot a daemon (`jsipfs daemon`). With this, you can use js-ipfs to access content in the browser just like you use to do in go-ipfs or use js-ipfs as a complete solution to add content in the network and preview it without leaving JS land, it is great for tooling. This was a [awesome contribution from @ya7ya and @harshjv](https://github.com/ipfs/js-ipfs/pull/968) that spent a lot of time adjusting and iterating on the implementation to make sure it would fit with the structure of js-ipfs, 👏🏽👏🏽👏🏽👏🏽.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. use period instead of comma before "it is great for tooling".
  2. use "an awesome" instead of "a awesome" because next word (awesome) starts with a vowel
  3. use "who spent" instead of "that spent" because it was people who spent a lot of time, etc.


# 🌱 Future

We have so much stuff in the pipeline, some of it almost got into this release but we eventually decided to defer it to a next release and make sure everyone would have access to the goodies in the _highlights_ section. That said, expect the following and more to come in a future release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

current: "in the pipeline, some of it"
new: "in the pipeline. Some of it"


### Circuit Relay

Circuit Relay is almost here, @dryajov showed us a demo of it working on the last IPFS All hands, you can watch it on the uploaded recording in YouTube https://youtu.be/chAXj_vsR2s?t=25m01s. Since then, @dryajov @stebalian and @vyzo have been working on making sure interop is fully tested.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

old: "almost here, @dryajov"
new: "almost here. @dryajov"

old: "IPFS All hands, you can"
new: "IPFS All Hands, and you can" (capital H in Hands. also add 'and' to connect the phrases, or if you prefer can separate into different sentences)

@daviddias
Copy link
Contributor Author

Thank you so much for your review (and tips!) @mishmosh :D

I've also added a section to invite contributors. Will do the rest of the release dance now and come back to publish this post :)

@daviddias daviddias merged commit db862bd into master Sep 13, 2017
@daviddias daviddias deleted the post/js-ipfs-0.26 branch September 13, 2017 08:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants