Bitmessage v0.4.4 will be available next week. It will be a required release; you must upgrade sometime before 16 Nov 2014. After that date all nodes will switch to simplified message formats which are not compatible with older clients.
This release will contain a major protocol upgrade which accomplishes several goals:
- Support user-specifiable message expiration time rather than the current two-day setting. Users will be able to specify the length of time a message should be held by the network from several minutes to 28 days. Messages with a longer time-to-live will require more work to send while messages with a shorter time-to-live will be easier to send.
- Simplification of the various object types and signing schemes which will make implementing alternative clients easier.
- Cap the maximum message size at 256 KiB.
There isn't yet any user-interface to specify the time-to-live of a message; this will be added after the upgrade period.
This release does contain a new feature which can be used immediately: the ability to limit the network transfer rate.
Because message acknowledgments will be broken until both the sender and receiver of a message upgrade, we are letting you know about this release ahead of time so that the upgrade may be more swift. Interested individuals may review the source code here: https://github.com/Bitmessage/PyBitmess ... ts/ProtoV3
Freewheeling spot to chew the fat on anything cryptostorm-related that doesn't fit elsewhere (i.e. support, howto, &c.). Criticism & praise & brainstorming & requests for explanation... this is where it goes when it's hot & ready for action!
1 post • Page 1 of 1