Skip to content

v2.5.4 - Support node 0 on DH+, allows spaces in tag attribute string
Compare
Choose a tag to compare
@kyle-github kyle-github released this 14 Nov 04:30
· 1 commit to release since this release
v2.5.4
e43d3b9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This has two main fixes/enhancements:

  • Allow spaces in some parts of the tag string. Spaces are stripped from the attribute names. Spaces are allowed between parts of a path. I probably will not go further than that as it would prevent spaces from being used in attribute values. Thanks to user @igal92 for bringing this up a long, long time ago.
  • Allow the use of DH+ node 0 (zero). This was brought up a long time ago by @jimk907. There was some logic in the set up of DH+ bridging that was using the node ID as a sort of flag to determine whether a path had a DH+ bridge in it. I suggest that you do not use node ID 0 in your DH+ networks. I seem to remember that it is special in some way. But if you do, it is now supported.

Contributors

jimk907 and igal92
Assets 13