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

js-ipfs 0.29.0 release blog post #163

Merged
merged 4 commits into from
Jun 7, 2018
Merged

js-ipfs 0.29.0 release blog post #163

merged 4 commits into from
Jun 7, 2018

Conversation

daviddias
Copy link
Contributor

@daviddias daviddias commented May 28, 2018

Anyone available to do a proof read?

@daviddias
Copy link
Contributor Author

Build is failing with

image


### 🏎 Bitswap is 30% faster

Bitswap is now 30% thanks to fixing a bug on [js-ipfs-bitswap](https://github.com/ipfs/js-ipfs-bitswap/pull/175#issuecomment-390957244) that was causing every message to be sent individually.
Copy link
Contributor

Choose a reason for hiding this comment

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

Typo "Bitswap is now 30% thanks" -> "Bitswap is now 30% faster, thanks"


### ☎️ Circuit Relay was merged in

Circuit Relay enables connectivity between any two nodes through a third relay node. This ensures connectivity in almost every scenario, that is, as long as peers can connect to some public IP node. Learn how to use it [here](https://github.com/ipfs/js-ipfs/tree/master/examples/circuit-relaying). This was one of the two features that js-ipfs was missing to get full connectivity.
Copy link
Contributor

Choose a reason for hiding this comment

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

I feel like this needs more bravado. This is BIG news! Maybe first item? More emoji? Mention NAT traversal?

Copy link

Choose a reason for hiding this comment

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

It is indeed a big deal. We should be careful to mention that we still need a go release to work out all the issues with go interop.

RE: NAT traversal, we might want to say that our next steps are building on top of circuit with true NAT traversal with the use of UPnP and NAT-PMP, which will allow opening external ports on the users router as well as the possibility of using techniques such as dial me back once a ports are mapped and a circuited connection is established - all this might require a new blog post tho 😉.

Copy link

@dryajov dryajov left a comment

Choose a reason for hiding this comment

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

LGTM, other than the point brought up by @alanshaw

@alanshaw
Copy link
Contributor

Also Node.js 10 support... 😉

@alanshaw
Copy link
Contributor

alanshaw commented Jun 7, 2018

ping @diasdavid

@daviddias
Copy link
Contributor Author

We pack all the patch features into the minor release announcement.

I don't want to make Circuit Relay super super flashy (it is already highlighted) because go-ipfs 0.4.15 hasn't been released yet (necessary for circuit relay to have interop) and we don't have DHT yet. Let's make a super flashy announcement when a browser node can connect to any node :)

@daviddias daviddias merged commit da539bc into master Jun 7, 2018
@ghost ghost removed status/in-progress In progress stage: skeleton labels Jun 7, 2018
@daviddias daviddias deleted the post/js-ipfs-0.29 branch June 7, 2018 12:48
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.

3 participants