Tags

0.9.4

0.9.3

LXMF beta 0.9.3

This release fixes a single bug.

**Changes**
- Fixed missing PN configuration unpack from cached announce data on incoming sync auto-peering if peer wasn't already discovered and peered.

0.9.2

LXMF beta 0.9.2

This release fixes a compatibility issue with Python 3.14 and ensures correct data persistence on SIGTERM or SIGINT shutdowns

**Changes**
- Fixed invalid multiprocessing start method for Python 3.14
- Fixed down-chain exit handlers not being called under some forced shutdown circumstances

0.9.1

LXMF beta 0.9.1

***Hotfix Release** for 0.9.0 released earlier today! The initial upload had a bug that would cause message stamps to get overwritten by propagation stamps (in client outbound processing) if deferred stamp generation was enabled. Please upgrade to this version on any **clients** immediately. Propagation nodes running 0.9.0 are not affected, but I'd recommend upgrading anyway! My apologies for the extra updating ;) This was a complex release, and of course a bug had to sneak in!*

This release comes with significant upgrades to propagation node functionality and efficiency. The sync and peering system for propagation nodes has been ugpraded, making it much faster and more efficient. Most importantly, propagation stamps have now been implemented, similar to the direct peer-to-peer message stamp functionality already present. From now on, clients will compute a propagation stamp for each message sent to the propagation network, which nodes can check for validity. Stamp generation is computationally costly, but very easy to validate for nodes processing messages, making it much more expensive to spam and abuse the network. Stamp and peering costs can be configured individually by node operators, which allows each network to find its own consensus and react in real-time to load, capacity and use.

If you want to get started with this new functionality already, the best place to start is to read the updated `lxmd` configuration file. I will have a full explanation of all the new options out shortly, but the config file comments should give you the most necessary information.

**Warning!** While this release is fully compatible with previous LXMF versions for all direct and peer-to-peer delivery, propagation-node functionality is **not** backwards compatible for this release, since the signalling, sync and peering system has been significantly redesigned and improved. Clients using LXMF versions prior to 0.9.0 will not be able to send messages via 0.9.0+ propagation nodes, although they will be able to *download* messages from them for now. Propagation nodes still on version prior to 0.9.0 will not be able to sync with nodes from 0.9.0 forward, and newer nodes will also not offer any messages to older versions. Nodes running older versions will automatically see new versions as presenting a de-peering request, and stop sending them messages. If you update to LXMF 0.9.0, make sure to update all your devices to retain full propagation node functionality! Updated versions of Sideband and Nomad Network supporting the new functionality will be released shortly.

**Changes**
- Added ability to include node names in propagation node announces
- Added ability to query and control remote `lxmd` instances
- Added new `lxmd` command line options for triggering peer sync and removing peers
- Improved `lxmd` status and peer status output
- Implemented propagation stamp system
- Implemented automatic client-side propagation stamp generation and cost resolution for outbound propagation messages
- Implemented propagation node peering key computation and validation
- Implemented remote propagation node sync request validation using peering keys and throttling
- Improved peer configuration resolution time significantly by using cached announce app data and network queries, instead of waiting for announces to arrive
- Implemented automatic legacy node de-peering once node is upgraded to 0.9.0+
- Implemented automatic peer breaking if peered nodes moves outside of auto-peering range
- Implemented client-side duplicate detection and signalling on propagation node message download
- Improved auto-peering on inbound sync
- Added support for getting transient message stamp values to the API
- Significantly improved propagation node announce data structure, paving the way for future functionality and improvements
- Added separate propagation message size and propagation node sync size limits
- Significantly improved propagation node convergence
- Fixed a bug where propagation node messagestore messages would always get deleted if the path to the messagestore directory contained an underscore.
- Fixed a bug in the initial 0.9.0 release that could cause message stamps to get overwritten by propagation stamps.

0.9.0

LXMF beta 0.9.0

This release comes with significant upgrades to propagation node functionality and efficiency. The sync and peering system for propagation nodes has been ugpraded, making it much faster and more efficient. Most importantly, propagation stamps have now been implemented, similar to the direct peer-to-peer message stamp functionality already present. From now on, clients will compute a propagation stamp for each message sent to the propagation network, which nodes can check for validity. Stamp generation is computationally costly, but very easy to validate for nodes processing messages, making it much more expensive to spam and abuse the network. Stamp and peering costs can be configured individually by node operators, which allows each network to find its own consensus and react in real-time to load, capacity and use.

If you want to get started with this new functionality already, the best place to start is to read the updated `lxmd` configuration file. I will have a full explanation of all the new options out shortly, but the config file comments should give you the most necessary information.

**Warning!** While this release is fully compatible with previous LXMF versions for all direct and peer-to-peer delivery, propagation-node functionality is **not** backwards compatible for this release, since the signalling, sync and peering system has been significantly redesigned and improved. Clients using LXMF versions prior to 0.9.0 will not be able to send messages via 0.9.0+ propagation nodes, although they will be able to *download* messages from them for now. Propagation nodes still on version prior to 0.9.0 will not be able to sync with nodes from 0.9.0 forward, and newer nodes will also not offer any messages to older versions. Nodes running older versions will automatically see new versions as presenting a de-peering request, and stop sending them messages. If you update to LXMF 0.9.0, make sure to update all your devices to retain full propagation node functionality! Updated versions of Sideband and Nomad Network supporting the new functionality will be released shortly.

**Changes**
- Added ability to include node names in propagation node announces
- Added ability to query and control remote `lxmd` instances
- Added new `lxmd` command line options for triggering peer sync and removing peers
- Improved `lxmd` status and peer status output
- Implemented propagation stamp system
- Implemented automatic client-side propagation stamp generation and cost resolution for outbound propagation messages
- Implemented propagation node peering key computation and validation
- Implemented remote propagation node sync request validation using peering keys and throttling
- Improved peer configuration resolution time significantly by using cached announce app data and network queries, instead of waiting for announces to arrive
- Implemented automatic legacy node de-peering once node is upgraded to 0.9.0+
- Implemented automatic peer breaking if peered nodes moves outside of auto-peering range
- Implemented client-side duplicate detection and signalling on propagation node message download
- Improved auto-peering on inbound sync
- Added support for getting transient message stamp values to the API
- Significantly improved propagation node announce data structure, paving the way for future functionality and improvements
- Added separate propagation message size and propagation node sync size limits
- Significantly improved propagation node convergence
- Fixed a bug where propagation node messagestore messages would always get deleted if the path to the messagestore directory contained an underscore.

0.8.0

LXMF beta 0.8.0

This release fixes a bug and improves recovery time when delivery links are unexpectedly closed during transfer.

**Changes**
- Fixed a potential division by zero
- Added retry of path request on unexpectedly closed link
- Updated RNS dependency version

0.7.1

LXMF beta 0.7.1

This release fixes a single bug.

**Changes**
- Fixed inactive link cleanup timing source

0.7.0

LXMF beta 0.7.0

This is a compatibility release for AES-256 encryption added in RNS `0.9.5`.

**Changes**
- Added support for AES-256 link and packet modes
- Updated required RNS version to `0.9.5`

0.6.3

LXMF beta 0.6.3

This release updates the default configuration file.

**Changes**
- Added options to the default configuration file
- Added message ingest API option

0.6.2

LXMF beta 0.6.2

This release significantly improves overall network peering topology, and speeds up optimal peering configuration discovery for the netwok as a whole.

**Changes**
- Redesigned peer rotation to be much faster and more responsive to real-time network conditions
- Improved handling of message queues for peers with low transfer limits
- Added lxmd status query API function
- Fixed a potential division by zero bug

0.6.1

LXMF beta 0.6.1

This release significantly improves memory consumption on propagation nodes, and adds a few new configuration options to `lxmd`.

**Changes**
- Improved memory consumption for propagation nodes
- Added ability to configure static peers
- Added ability to specify maximum number of peers

0.6.0

LXMF beta 0.6.0

This release improves propagation node sync efficiency, and adds better signalling for message transfers.

**Changes**
- Added ability to cancel outbound messages
- Added message rejection signalling if message exceeds transfer limit
- Added sync transfer rate to propagation node peer stats
- Improved propagation node sync efficiency by sorting peers according to STR
- Added handling of corrupted transient ID cache

0.5.8

LXMF beta 0.5.8

This release improves reliability of propagation node message synchronisation.

**Changes**
- Improved duplicate message detection over longer timeframes
- Added propagation node announce data validation to announce handler

0.5.7

LXMF beta 0.5.7

This release fixes a single bug.

**Changes**
- Fixed missing byteorder argument on stamp value calculation

0.5.6

LXMF beta 0.5.6

This release fixes a single bug.

**Changes**
- Fixed incorrect progress value on path waiting for outbound messages

0.5.5

LXMF beta 0.5.5

This release fixes a number of bugs.

**Changes**
- Fixed a bug in inbound ticket cleaning
- Fixed a bug that could cause propagation node peer destinations to be created before identity was resolved
- Fixed a bug that could cause existing propagation node links to be torn down if the propagation node address was updated with the same address

0.5.4

LXMF beta 0.5.4

**Changes**
- Improved opportunistic delivery performance

0.5.3

LXMF beta 0.5.3

**Changes**
- Added path rediscovery during opportunistic delivery if path fails

0.5.2

LXMF beta 0.5.2

**Changes**
- Added backchannel delivery over already established links
- Improved opportunistic delivery logic and performance
- Improved logging
- Fixed a bug in the stamp cost extractor function

0.5.1

LXMF 0.5.1

**Changes**
- Fixed a bug that would prevent running multiple LXMRouter instances within the same program.