Re: Test
  By: Michiel van der Vlist to Rob Swindell on Sun Jun 07 2020 11:04 am

 > Hello Rob,
 >
 > On Saturday June 06 2020 12:30, you wrote to me:
 >
 >  >> Your assertion is falsified by Tommi Koivula's observation that at
 >  >> least one software has problems with it.
 >
 >  RS> I just read back through Tommi's posts here and did not find any
 >  RS> observation of any problem with Synchronet/SBBSecho's FTN MSG-IDs. Are
 >  RS> you sure about that?
 >
 > Yes, I am sure.
 >
 >  RS> Purport is a verb: https://www.merriam-webster.com/dictionary/purport
 >
 >  RS> Synonym to "claim". And at least *I* (the author) claim that
 >  RS> Synchronet/SBBSecho implements FTS-9.
 >
 > Noted.
 >
 >  >> "Limited horizon" is a pleonasm. An horizon is always a limit. By
 >  >> definition.
 >
 >  RS> Speaking of "limited horizons", let's take a look at the MSG-ID of
 >  RS> your posted message: 2:280/5555 5edb7807
 >
 >  RS> Huh... that "53db7808" looks suspiciously like a Unix time_t value:
 >
 > Yes, it looks like it. So?

It's a known-to-be-broken method of MSG-ID serialno generation. So long as
we're talking about MSG-IDs, I just thought I'd mention it.

 >  RS> So what happens on *your* system when 2 users (if you have any) post a
 >  RS> message in the same message area within the same wall-clock second?
 >
 > All my users are assigned a point number and post using that point number.
 > No conflict.

And none of those users could post more than one message within the same
wall-clock second? On my system, that kind of thing happens all the time (e.g.
when a users uploads an offline reader reply packet).

 > As for messages posted from the same address in the same second: see
 > FRL-1029.002 4.8.

Your system doesn't appear to be using the method described in FRL-1029.002
4.8. I've read this document before. Its proposed solution (a single shared
serial number database file) would inject a major bottle-neck into any mass
mail transfer system.

 >  RS> You, my friend, have a broken FTN MSG-ID generation algorithm there on
 >  RS> *your* system.
 >
 > So prove it by showing two different messages originating from my system in
 > the last three years that have the same MSGID.

My system would throw-away the second message as a duplicate, so I would never
know about it.

                                            digital man

Synchronet/BBS Terminology Definition #66:
SEXYZ = Synchronet External X/Y/ZMODEM file transfer protocol driver
Norco, CA WX: 72.3øF, 52.0% humidity, 10 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux