Subj : sbbsecho and bad packets
To   : deon
From : Digital Man
Date : Tue Oct 07 2025 22:23:24

  Re: sbbsecho and bad packets
  By: deon to Digital Man on Wed Oct 08 2025 01:36 pm

 >   Re: sbbsecho and bad packets
 >   By: Digital Man to deon on Tue Oct 07 2025 03:34 pm
 >
 > Howdy,
 >
 >  >  > I'm not seeing what you are seeing - but ok.
 >
 >  > FSP-1042 (still in draft stage) has the packed message header more
 >  > clearly defined:
 >
 > Yup, but its a proposal and not a standard. I dont want this to lead into an
 > interpretation of the standards debate - that never ends well.

My point was that it was another developer's interpretation of the packet standard (not mine) and it's gone through the FTSC review process (such that it is anyway), so I think there's pretty solid consensus that "this is the way". I would be interested to know what software it is that's not NUL-terminating the DateTime in the packed-message headers.

 >  > I think you have that backwards, the DateTime must be a null terminated
 >  > string: exactly 19 characters followed by a NUL.
 >
 > I dont believe I do - its not how I understand FTS-1.
 >
 > Anyway, you've made your position clear - I'll leave it to the uplink to
 > address with their software's developer, if it is in fact still being
 > developed and/or if they care.

Okay, and if you find out for sure what software that is, please let me know.
-- 
                                            digital man (rob)

This Is Spinal Tap quote #8:
Derek Smalls: Making a big thing out of it would have been a good idea.
Norco, CA WX: 62.1øF, 85.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.30-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.