Subj : Most recent message
To   : Maurice Kinal
From : Scott Street
Date : Sun Jun 07 2026 12:28 pm

 >> @MSGID: 1:266/625 6a2458e9f2b1d9e9

 MK> A 64-bit nanosecond unixtime?  If so you've convinced me to follow 
 MK> suit on my new experimental point. 


Well, not exactly; two values where computed and squished together, it really 
is: (unix time 32b)6a2458e9  (msg CRC32)f2b1d9e9

Though, it appears I read the spec and missed the fact that the serialno is 
only supposed to be 8 characters (which means 32b in hex). So I've got to 
rethink the MSGID generation.

 MK> Welcome to the 21st century ... just shy of 26 years too late.  Oh 
 MK> well, no time like the present eh?

We've got a few years before the unsigned 32 int runs out of space for the 
current time.  JAM uses a uint32_t for time.  It needs to be a uint64_t soon, 
before Feb 7, 2106.  One of the things on my back burner is to upgrade JAM's 
format for uint64 dates.  I'm on the fence about making the storage pointers 
64b, the 32b ones will still address 4Gb in a file and 4.2 million messages in 
a given message base. (64b file index could address 18billion terabytes -- 
which, according to Google, is more storage on all the planet.)

--- 
 * Origin: <=-[ The Digital Post ]-=> (1:266/625)

.