mirror of
https://github.com/ipfs/kubo.git
synced 2025-06-29 01:12:24 +08:00
36
CHANGELOG.md
36
CHANGELOG.md
@ -1,6 +1,6 @@
|
|||||||
# go-ipfs changelog
|
# go-ipfs changelog
|
||||||
|
|
||||||
## 0.4.18-rc2 2018-10-26
|
## 0.4.18 2018-10-26
|
||||||
|
|
||||||
This is probably one of the largest go-ipfs releases in recent history, 3 months
|
This is probably one of the largest go-ipfs releases in recent history, 3 months
|
||||||
in the making.
|
in the making.
|
||||||
@ -19,22 +19,22 @@ solves many of the long standing issues with TCP.
|
|||||||
|
|
||||||
For us, this means (eventually):
|
For us, this means (eventually):
|
||||||
|
|
||||||
* Fewer local resources. TCP requires a file-descriptor per connection while
|
* **Fewer local resources.** TCP requires a file-descriptor per connection while
|
||||||
QUIC (and most UDP based transports) can share a single file descriptor
|
QUIC (and most UDP based transports) can share a single file descriptor
|
||||||
between all connections. This should allow us to dial faster and keep more
|
between all connections. This should allow us to dial faster and keep more
|
||||||
connections open.
|
connections open.
|
||||||
* Faster connection establishment. When client authentication is included, QUIC
|
* **Faster connection establishment.** When client authentication is included,
|
||||||
has a three-way handshake like TCP. However, unlike TCP, this handshake brings
|
QUIC has a three-way handshake like TCP. However, unlike TCP, this handshake
|
||||||
us from all the way from 0 to a fully encrypted, authenticated, and
|
brings us from all the way from 0 to a fully encrypted, authenticated, and
|
||||||
multiplexed connection. In theory (not yet in practice), this should
|
multiplexed connection. In theory (not yet in practice), this should
|
||||||
significantly reduce the latency of DHT queries.
|
significantly reduce the latency of DHT queries.
|
||||||
* Behaves better on lossy networks. When multiplexing multiple requests over a
|
* **Behaves better on lossy networks.** When multiplexing multiple requests over
|
||||||
single TCP connection, a single dropped packet will bring the entire
|
a single TCP connection, a single dropped packet will bring the entire
|
||||||
connection to a halt while the packet is re-transmitted. However, because QUIC
|
connection to a halt while the packet is re-transmitted. However, because QUIC
|
||||||
handles multiplexing internally, dropping a single packets affects only the
|
handles multiplexing internally, dropping a single packets affects only the
|
||||||
related stream.
|
related stream.
|
||||||
* Better NAT traversal: TL;DR: NAT hole-punching is significantly easier and, in
|
* **Better NAT traversal.** TL;DR: NAT hole-punching is significantly easier
|
||||||
many cases, more reliable with UDP than with TCP.
|
and, in many cases, more reliable with UDP than with TCP.
|
||||||
|
|
||||||
However, we still have a long way to go. While we encourage users to test this,
|
However, we still have a long way to go. While we encourage users to test this,
|
||||||
the IETF QUIC protocol is still being actively developed and *will* change. You
|
the IETF QUIC protocol is still being actively developed and *will* change. You
|
||||||
@ -52,10 +52,10 @@ so you can enable it and still talk to nodes using the floodsub algorithm. You
|
|||||||
can find instructions to enable gossipsub in go-ipfs
|
can find instructions to enable gossipsub in go-ipfs
|
||||||
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#gossipsub).
|
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#gossipsub).
|
||||||
|
|
||||||
Messages are now, finally, signed by their authors. While signing has been
|
Messages are now signed by their authors. While signing has now been enabled by
|
||||||
enabled by default, strict signature verification has not been and will not be
|
default, strict signature verification has not been and will not be for at least
|
||||||
for at least one release (probably multiple) to avoid breaking existing
|
one release (probably multiple) to avoid breaking existing applications. You can
|
||||||
applications. You can read about how to configure this feature
|
read about how to configure this feature
|
||||||
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#message-signing).
|
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#message-signing).
|
||||||
|
|
||||||
#### Commands
|
#### Commands
|
||||||
@ -83,8 +83,8 @@ bafybeicg2rebjoofv4kbyovkw7af3rpiitvnl6i7ckcywaq6xjcxnc2mby
|
|||||||
|
|
||||||
The refactored `ipfs p2p` command allows forwarding TCP streams through two IPFS
|
The refactored `ipfs p2p` command allows forwarding TCP streams through two IPFS
|
||||||
nodes from one host to another. It's `ssh -L` but for IPFS. You can find
|
nodes from one host to another. It's `ssh -L` but for IPFS. You can find
|
||||||
documentation in
|
documentation
|
||||||
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#ipfs-p2p)).
|
[here](https://github.com/ipfs/go-ipfs/docs/experimental-features.md#ipfs-p2p).
|
||||||
It's still experimental but we don't expect too many breaking changes at this
|
It's still experimental but we don't expect too many breaking changes at this
|
||||||
point (it will very likely be stabilized in the next release). Quick summary of
|
point (it will very likely be stabilized in the next release). Quick summary of
|
||||||
breaking changes:
|
breaking changes:
|
||||||
@ -122,9 +122,9 @@ directories and tiny files.
|
|||||||
|
|
||||||
#### IPNS
|
#### IPNS
|
||||||
|
|
||||||
You can now, finally, publish and resolve paths with namespaces *other* than
|
You can now publish and resolve paths with namespaces *other* than `/ipns` and
|
||||||
`/ipns` and `/ipfs` through IPNS. Critically, IPNS can now be used with IPLD
|
`/ipfs` through IPNS. Critically, IPNS can now be used with IPLD paths (paths
|
||||||
paths (paths starting with `/ipld`).
|
starting with `/ipld`).
|
||||||
|
|
||||||
#### WebUI
|
#### WebUI
|
||||||
|
|
||||||
|
@ -4,6 +4,6 @@ package ipfs
|
|||||||
var CurrentCommit string
|
var CurrentCommit string
|
||||||
|
|
||||||
// CurrentVersionNumber is the current application's version literal
|
// CurrentVersionNumber is the current application's version literal
|
||||||
const CurrentVersionNumber = "0.4.18-rc2"
|
const CurrentVersionNumber = "0.4.18"
|
||||||
|
|
||||||
const ApiVersion = "/go-ipfs/" + CurrentVersionNumber + "/"
|
const ApiVersion = "/go-ipfs/" + CurrentVersionNumber + "/"
|
||||||
|
Reference in New Issue
Block a user