🙌 👏💪
MollyM committed
Feb 22, 2019 at 19:23 UTC
6a8766629ea6bb79c7f9a00ce0fd9367633d87ec
1 file changed
+22
-22
CHANGELOG.md
+22
-22
@@ -3,14 +3,14 @@
3
## 0.4.19 2018-02-14 (unreleased)
4
5
We're happy to announce go 0.4.19. This release contains a bunch of important
6
-fixes and a slew of new and improved features. Please upgrade ASAP.
6
+fixes and a slew of new and improved features. Get pumped and upgrade ASAP to benefit from all the new goodies! 🎁
7
8
### Features
9
10
-#### Initializing With Random Ports
10
+#### 🔌 Initializing With Random Ports
11
12
-Go-ipfs can now be configured to listen on a random but _stable_ (across
13
-restarts) port using the new `randomports` configuration profile. This should be
12
+Go-ipfs can now be configured to listen on a random but _stable_ port (across
13
+restarts) using the new `randomports` configuration profile. This should be
14
helpful when testing and/or running multiple go-ipfs instances on a single
15
machine.
16
@@ -20,14 +20,14 @@ To initialize a go-ipfs instance with a randomly chosen port, run:
20
> ipfs init --profile=randomports
21
```
22
23
-#### Gateway Directory Listing
23
+#### 👂 Gateway Directory Listing
24
25
IPNS (and/or DNSLink) directory listings on the gateway, e.g.
26
https://ipfs.io/ipns/dist.ipfs.io/go-ipfs/, will now display the _ipfs_ hash of
27
the current directory. This way users can more easily create permanent links to
28
otherwise mutable data.
29
30
-#### AutoRelay and AutoNAT
30
+#### 📡 AutoRelay and AutoNAT
31
32
This release introduces two new experimental features (courtesy of libp2p):
33
AutoRelay and AutoNAT.
@@ -50,7 +50,7 @@ In this same config section, you may also notice options like `EnableRelayHop`,
50
* `EnableAutoNATService` -- Help _other_ nodes detect if they're behind a NAT
51
(disabled by default).
52
53
-#### Offline Operation
53
+#### 📵 Offline Operation
54
55
There are two new "offline" features in this release: a global `--offline` flag
56
and an option to configure the gateway to not fetch files.
@@ -75,9 +75,9 @@ Note: It doesn't _yet_ work with the `refs`, `urlstore`, or `tar` commands
75
On to the gateway, there's a new `Gateway.NoFetch` option to configure the
76
gateway to only serve locally present files. This makes it possible to run an
77
IPFS node as a gateway to serve content of _your_ choosing without acting like a
78
-public proxy.
78
+public proxy. 🤫
79
80
-#### Adding And Pinning Content
80
+#### 📍 Adding And Pinning Content
81
82
There's a new `--pin` flag for both `ipfs block put` and `ipfs urlstore add` to
83
match the `--pin` flag in `ipfs add`. This allows one to atomically add and pin
@@ -92,7 +92,7 @@ pinning content after adding it, it isn't pinned and running the garbage
92
collector will delete it. While technically documented in the `ipfs urlstore
93
add` helptext, this behavior was non-obvious and bears mentioning.
94
95
-#### File Listing
95
+#### 🗂 File Listing
96
97
The `ipfs ls` command has two significant changes this release: it reports
98
_file_ sizes instead of _dag_ sizes and has gained a new `--stream` flag.
@@ -129,7 +129,7 @@ total 28
129
```
130
131
This is now no longer the case. `ipfs ls` and `ls -l` now return the _same_
132
-sizes.
132
+sizes. 🙌
133
134
Second up, `ipfs ls` now has a new `--stream` flag. In IPFS, very large
135
directories (e.g., Wikipedia) are split up into multiple chunks (shards) as
@@ -143,9 +143,9 @@ However, the new `--stream` flag makes it possible to stream a directory listing
143
as new chunks are fetched from the network. To test this, you can run `ipfs ls
144
--stream --size=false --resolve-type=false
145
/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki`. You probably won't
146
-want to wait for that command to finish, Wikipedia has a _lot_ of entries.
146
+want to wait for that command to finish, Wikipedia has a _lot_ of entries. 😉
147
148
-#### HTTP Proxy
148
+#### 🔁 HTTP Proxy
149
150
This release sees a new (experimental) feature contributed by our friends at
151
[Peergos](https://peergos.org): HTTP proxy over libp2p. When enabled, the local
@@ -159,7 +159,7 @@ to other go-ipfs nodes via their gateways. For details, check out the
159
This release introduces quite a few performance/reliability improvements and, as
160
usual, fixes several memory leaks. Below is a non-exhaustive list of noticeable changes.
161
162
-#### DHT
162
+#### 📞 DHT
163
164
This release includes an important DHT fix that should significantly:
165
@@ -172,7 +172,7 @@ entire IPFS network. Yikes!
172
173
Relevant PR: https://github.com/libp2p/go-libp2p-kad-dht/pull/237
174
175
-#### Bitswap
175
+#### 🕸 Bitswap
176
177
Bitswap sessions have improved and are now used for _all_ requests. Sessions
178
allow us to group related content and ask peers most likely to _have_ the
@@ -189,13 +189,13 @@ us two significant benefits:
189
peers). We had to do this because we had to assume that _most_ peers didn't
190
have the requested block.
191
192
-#### Pubsub
192
+#### ‼️ Pubsub
193
194
This release includes some significant reliability improvements in pubsub
195
subscription handling. If you've previously had issues with connected pubsub
196
peers _not_ seeing each-other's messages, please upgrade ASAP.
197
198
-#### Reuseport
198
+#### ♻️ Reuseport
199
200
In this release, we've rewritten our previously error-prone `go-reuseport`
201
library to _not_ duplicate a significant portion of Go's low-level networking
@@ -206,11 +206,11 @@ In the past, our first suggestion to anyone experiencing weird resource or
206
connectivity issues was to disable `REUSEPORT` (set `IPFS_REUSEPORT` to false).
207
This should no longer be necessary.
208
209
-#### Badger Datastore
209
+#### 🐺 Badger Datastore
210
211
[Badger has reached 1.0][badger-release]. This release brings an audit and
212
numerous reliability fixes. We are now reasonably confident that badger will
213
-become the default datastore in a future release.
213
+become the default datastore in a future release. 👍
214
215
[badger-release]: https://blog.dgraph.io/post/releasing-v1.0/
216
@@ -222,12 +222,12 @@ the need for manual intervention when restarting an IPFS node after a crash.
222
223
### Refactors and Endeavors
224
225
-#### Commands Library
225
+#### 🕹 Commands Library
226
227
The legacy commands library shim has now been completely removed. This won't
228
mean much for many users but the go-ipfs team is happy to have this behind them.
229
230
-#### Base32 CIDs
230
+#### 🌐 Base32 CIDs
231
232
This release can now encode CIDs in responses in bases other than base58. This
233
is primarily useful for web-browser integration as it allows us to (a) encode
@@ -245,7 +245,7 @@ Specifically, this release adds two flags:
245
changes the _binary_ representation of the CIDs (which could have unintended
246
consequences).
247
248
-#### CoreAPI
248
+#### 🎛 CoreAPI
249
250
The work on the CoreAPI refactor ([ipfs/go-ipfs#4498][]) has progressed leaps and
251
bounds this release. The CoreAPI is a comprehensive programmatic interface