0.20.0

Breaking changes

• 🔐 Auto encrypted sessions - SDPs are now always encrypted by default with a key derived from the app ID and room name. The key can be reverse engineered using these parameters, but it's better than flooding relays with plaintext session descriptions. For extra security, use a custom password argument.

Improvements

• makeAction() now has referential equality when called multiple times with the same name argument. This makes it better suited for reactive frameworks. Thanks to @rogersanick for suggesting it.
• Room leave events should fire reliably in Firefox when a peer closes the window or refreshes. (#77)

0.19.0

Improvements

• Shared peering logic - This release streamlines and consolidates all the different code for interfacing with strategy relays into a single place. This means that peering strategies are now much simpler and it's significantly easier to write new ones (or in future releases, mix and match strategies with the same group of peers). Previously, duplicated logic existed between various strategy modules, but going forward any fixes for deadlocks, race conditions, etc. will benefit all strategies.
• More reliable/faster room entrance/exit events - Joining, leaving, and re-joining rooms should be noticeably faster and more reliable due to the strategy logic overhaul.
• Better support for SSR frameworks - While it isn't working on Node quite yet (but getting closer), you can now import Trystero in Node without causing problems, which avoids the need for workarounds for shared code in SSR frameworks.
• 🪐 IPFS - The IPFS strategy had been broken but is now working again.

New features

• ⚡️ Supabase strategy - A new connection strategy is now available using Supabase, an open-source BaaS built on Postgres.
• Incorrect password handling - joinRoom() now accepts a third argument, a function that will be called if a user tries to join a room with a password that doesn't match other users (docs).

0.18.0

New features

• 🐦 Nostr strategy - A new connection strategy is now available using Nostr, a decentralized network protocol with many public relays.
• Unified relay API - The BitTorrent, Nostr, and MQTT strategies now take relayUrls and relayRedundancy options, so there is shared terminology across strategies and a smaller configuration API. These strategies also expose a getRelaySockets() function that returns a map of URLs to WebSockets.
• Bug fix: Action sender functions can now send empty strings
• Torrent tracker failures are now logged with their URLs

Breaking changes

• 🌊 BitTorrent strategy
  • trackerUrls has been renamed relayUrls
  • trackerRedundancy has been renamed relayRedundancy
  • getTrackers() has been renamed getRelaySockets()
• 📡 MQTT strategy
  • brokerUrls has been renamed relayUrls
  • brokerRedundancy has been renamed relayRedundancy

0.17.0

New features

• 📡 MQTT strategy - A new connection strategy is now available using MQTT, an open protocol for IoT device communication. Thanks to @freehuntx for suggesting the approach.

0.16.0

• (🪐 IPFS) swarmAddresses in IPFS config has been replaced by libp2pConfig

0.15.2

• (🪐 IPFS) Overhauled IPFS strategy
• (🔥 Firebase) Updated to firebase@^10.6.0

0.15.1

• (🔥 Firebase only) fixed getOccupants()

0.15.0

• joinRoom() and makeAction() are now idempotent when called with the same namespaces which allows you to use them as React hooks. See the readme for details. Thanks to @rogersanick for proposing a solution.

0.14.0

• The Firebase strategy now requires passing the full databaseURL as the appId to joinRoom() (either with or without the https:// prefix), e.g. 'trystero-demo.firebaseio.com, not just 'trystero-demo'. This allows support for other regions which use different url structures. Thanks to @matthewjumpsoffbuildings for diagnosing and proposing a fix.

0.13.0

New features

• getTrackers() (🌊 BitTorrent only) Returns an object of BitTorrent tracker URL keys mapped to their WebSocket connections. This can be useful for determining the state of the user's connection to the trackers and handling any connection failures. (Thanks to @jeremyckahn for implementing)