[8.0.2] - 2024-01-25

Fixed

• Fix race condition preventing message listeners from being set.

[8.0.0] - 2023-10-17

Changed

• Upgraded cabal-core to latest, to bring in hyperswarm changes.

[7.3.2] - 2022-10-31

Fixed

• Fix unhandled promise rejection when initializing a Client instance with a cabal name that can't be resolved. (Handles case of being unable to resolve a key. (#94) (Kira Oakley))

[7.3.1] - 2022-05-26

Fixed

• Fix crash when creating new PM (Reorder PM null check (#91) (Daniel Chiquito))

  The previous ordering would cause an exception even if the null check was triggered.

[7.3.0] - 2022-05-24

Changed

• Use getter for PMChannelDetails.joined (#89) (Daniel Chiquito).

  The getter refers to the CabalDetails instance which holds the settings for the cabal to determine if the private message channel should be considered joined or not.

  This has the side affect of requiring the CabalDetails when initializing the PMChannelDetails, which involves changing the constructor signature.

  This is technically a breaking change, however ChannelDetails is an internal implementation concern of cabal-details and not intended to be one of the public facing api functions.

Added

• Add methods to read/write a settings file (#89) (Daniel Chiquito)
• Add dependency on js-yaml (#89) (Daniel Chiquito)
• Leaving private messages functionality (#89) (Daniel Chiquito & cblgh)

Fixed

• Potential issue upstream in cabal-core when receiving ill-formatted PMs (e6e7308) (cblgh)

[7.2.2] - 2021-12-16

Fixed

• remove duplication of channel events (0caff38) (@khubo)

[7.2.1] - 2021-12-11

Changed

• getChannels: add onlyJoined param (1bb9d3d) (@cblgh)

[7.2.0] - 2021-11-23

Changed

• bump cabal-core to 15.0.0 (only changes were to pm api) (#82) (@cblgh)

• disallow channel names == hypercore key, support latest core pm format (#82) (@cblgh)

  • A new convention was introduced to limit malicious use in clients: Channel names conforming to the hypercore public key format are forbidden in cabal-client as names for regular channel names (i.e. no channel names that are 64 hex characters)—these are restricted to private channels only (namely: one per person you are chatting with, the name being their public key (or yours, from their perspective))

• Revert "only add message listener when we're adding a new channel" (1bf10a9) (@cblgh).

  This reverts commit 1dbd522.

  It seems this commit introduced a regression in functionality such that messages do not appear in channels (#78) and might also be responsible for a similar bug in cabal-desktop@6.0.8

  It would be good to only add the relevant message listeners, instead of duplicates, but I think it will have to be done anew with fresh eyes.

Added

Adds support for cabal-core's private message:

• a new CabalDetails.publishPrivateMessage function has been added
• CabalDetails.getPrivateMessageList returns a list of channel names corresponding to ongoing PMs for the local user
• CabalDetails.isChannelPrivate(channel) returns true if the passed in channel is a private message channel, false otherwise
• CabalDetails.publishMessage now redirects a published message to publishPrivateMessage if it is used to post a message to a private message channel
• publish-private-message, private-message events are now emitted
• the PMChannelDetails has been added to enable support for private message channels with minimal duplicated functionality
• CabalDetails.getChannels(opts) was extended with an option includePM to include private message channels in the returned result
• PMs are moderation aware: if you hide a user the channel is hidden and no subsequent PMs will be displayed in your client

For more information, see the API documentation.