REPLY: 2:221/1.58@fidonet ef616eac
MSGID: 1:153/7001 sTW6u3OA
CHRS: UTF-8 4
-={ 2021-04-13 21:15:41.032014984+00:00 }=-

Hey August!

 AA> Is that a way to reduce the probability of collisions within a
 AA> certain span of allotted time?

Good question.  I've heard of a few different methods for doing this none of
which I am currently deploying.  Mind you I take care of MSGIDs in the
creation of the MSG so the possiblity of collisions is near zero.  There is a
way but if that happens then it is a signal that something is seriously wrong
on my system.  It has yet to happen.

Just for fun here is the output of 10 potential MSGID serailno's, the first
column being unixtime 32-bit hex based, the second being the random 8
character [:alnum:] regex dealies;

60760e0b kUBdI5RO
60760e0b G5T1LBae
60760e0b mFSS1Gxc
60760e0b Daxpq9EE
60760e0b XVCgstYj
60760e0b uWuB7Jqj
60760e0b J0qZbQIo
60760e0b kGrnLcEZ
60760e0b NQGnXOVM
60760e0b kK7htVJO

Note that only one method produced zero collisions while the other produced
nothing but collisions.  Based on this very simple test the random 8 character
[:alnum:] regex thingies are obviously superior.


Life is good,
Maurice

... Lofdædum sceal in mægþa gehwære man geþeon.
    By praiseworthy deeds shall one prosper among peoples everywhere.
--- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
 * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 129/305 153/105
SEEN-BY: 153/135 757 802 7001 226/30 227/114 229/101 424 426 452 664
SEEN-BY: 229/700 1016 1017 240/5832 249/206 317 400 261/38 282/1038
SEEN-BY: 301/1 317/3 322/757 342/17 200 633/280
PATH: 153/7001 757 229/664 426