v0.7.2
Stability improvements.
Changed
- Prevent multiple tabs from trying to use the same PeerId
- Prevent locks for Merkle sync from being held indefinitely
- Reduce GossipSub penalties for misbehaving peers
- Default to using browser-to-server WebSocket transport; only use browser-to-browser WebRTC if
enableWebRTC: true
is set in the config- You should use WebSocket for production applications now.
- Note that using WebSocket means you must use a replication server (i.e.
canvas cli
or another persistent node in the cloud). See below for a universal solution to this.
- Applications now start libp2p automatically
app.start/stop()
have been moved toapp.libp2p.start/stop()
but are no longer needed.
- Adds a
heartbeat
message type, in preparation for live presence support.
Added
@canvas-js/replication-server
: A universal replication server that watches a discovery topic and saves and replicates all actions on all topics broadcast to it.- If you configure any application with the universal replication server's discovery topic, the application will automatically be replicated.