You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Rhizome manifest version number is currently implemented as GMT time in milliseconds since the standard Unix epoch. The date field can be made optional for users who do not wish to expose the time at which their anonymous posts were made, but the version field is not optional for Rhizome. Therefore, it must be re-implemented to not reveal anything about the time or place of authorship, or even the number of revisions.
The proposed design is:
use a 56-bit unsigned integer for version numbers
initialise the version of every new bundle with a random integer in the approximate range 1e4 - 1e6 (32 bits)
increment the version on every revision by a random integer in the range 1 - 1e6 (32 bits)
use an unsigned comparison between version numbers in Rhizome
handle version overrun by simply not allowing the version number to wrap -- the “update bundle” operation fails with an error (which should be extremely rare)
When this is done, the BAR format may have to be updated. See issue #19.
The text was updated successfully, but these errors were encountered:
The Rhizome manifest version number is currently implemented as GMT time in milliseconds since the standard Unix epoch. The date field can be made optional for users who do not wish to expose the time at which their anonymous posts were made, but the version field is not optional for Rhizome. Therefore, it must be re-implemented to not reveal anything about the time or place of authorship, or even the number of revisions.
The proposed design is:
When this is done, the BAR format may have to be updated. See issue #19.
The text was updated successfully, but these errors were encountered: