Release v2.8.5 (Stable) · ipfs/ipfs-companion

Highlight: TCP transport (Brave only)

This release enables P2P connectivity over TCP when embedded JS IPFS in Brave is used.

Enabled TCP transport thanks to chrome.sockets.tcp* #754
LAN Discovery of go-ipfs with chrome.sockets.udp #754
enabled WAN peer discovery via community ws-star servers to provide best-effort backup for non-LAN peer discovery
enabled preload via *.preload.ipfs.io (makes it easier to share files on the go)
enabled delegated routing (delegated DHT for peers & content) via go-ipfs at *.delegate.ipfs.io

Known Issues

init of embedded node may take a few seconds more than expected
js-libp2p-mdns is unable to start active service if port 5353 is already taken, making DNS discovery passive
- ws-star signaling services are used as additional discovery method. If both nodes are in the same network, they should connect directly over TCP (ws-star used only for signaling)
js-ipfs does not ship with DHT yet, delegated routing via *.delegate.ipfs.io is used for now
Some features of ipfs-webui may not work (latency column on Peers screen etc)
Sometimes browser action does not work: until we fix this, disabling and enabling IPFS Companion via Brave Settings is a quick way to make it work again immediately

Progress on Brave can be tracked in: #716

How to opt-in in Brave

Stable release of IPFS Companion can be enabled via Brave Settings (chrome://settings/extensions):

By default, it works like regular ipfs-companion and External node is used.
Brave users can opt-in and try Embedded + chrome.sockets (see /docs/node-types for more details):

Other

feat: new Web UI v2.5.3
chore: simplify build (#762)
fix: add bundle:fennec (#762, fix for #761)
switch to release version of Hapi.js with hapijs/hapi#3946
chore: dependency updates
i18n: synchronized translations
- How can I add/improve translation for my language?