Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
faq:misc [2018/10/31 01:52] – Added a "No Guest" FAQ digital manfaq:misc [2019/01/29 02:36] – [SBBSList] Updated with links to dynamically generated HTML versions of the list digital man
Line 69: Line 69:
 ([[module:sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should ([[module:sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should
 be automatically exported to the DOVE-Net SYNCDATA echo which will then be be automatically exported to the DOVE-Net SYNCDATA echo which will then be
-propagated to [[bbs:Vertrauen]] and every other BBS on DOVE-Net. The ''sbbslist.html''+propagated to [[bbs:Vertrauen]] and every other BBS on DOVE-Net. The ''[[http://synchro.net/sbbslist.html|sbbslist.html]]''
 page is automatically generated on Vertrauen every night at midnight page is automatically generated on Vertrauen every night at midnight
-(Pacific time), so wait a day or so for your entry to appear on the list.+(Pacific time), so wait a day or so for your entry to appear on the list. You can also check a dynamically generated HTML BBS list [[http://cvs.synchro.net/sbbslist.ssjs|here]] or [[http://web.synchro.net/?page=More/999-sbbslist.xjs|here]].
 If it doesn't appear, verify that that your BBS entry was properly If it doesn't appear, verify that that your BBS entry was properly
 exported (as a message) to the SYNCDATA message area. The timed events exported (as a message) to the SYNCDATA message area. The timed events
Line 187: Line 187:
 The result **is** a "//valid return address for the originating network//", in that a FidoNet NetMail sent to this address will normally reach the sysop of the originating node (in the example case, me). But the //originating// network might **not** be an FTN network. There is **nothing** in FTS-9 that specifies the form or content of the ''origaddr'' field. In fact, it mentions the use of "double-quotes" and how they must be escaped if part of the address. When is the last time you saw quotes of any kind in an FTN address? Clearly the author was leaving this definition open to non-FTN addresses. And again, it's only a "should" clause anyway. This field could only contain the GPS coordinates of my birthplace and would still be completely within the requirements of the specification. The result **is** a "//valid return address for the originating network//", in that a FidoNet NetMail sent to this address will normally reach the sysop of the originating node (in the example case, me). But the //originating// network might **not** be an FTN network. There is **nothing** in FTS-9 that specifies the form or content of the ''origaddr'' field. In fact, it mentions the use of "double-quotes" and how they must be escaped if part of the address. When is the last time you saw quotes of any kind in an FTN address? Clearly the author was leaving this definition open to non-FTN addresses. And again, it's only a "should" clause anyway. This field could only contain the GPS coordinates of my birthplace and would still be completely within the requirements of the specification.
      
-The serial number (''serialno'') field generated by Synchronet and its utilities is a mathematical sum of the area-unique ''<msgnum>'' and a number derived from the date and time the message was created so as to maximize the use of the allocated 32-bits. The serial number will by unique among all the messages generated by a Synchronet-system in a single message area (echo), but is not guaranteed to be unique, by itself, among //all// the FTN-connected message areas of a single Synchronet-system. The ''serialno'' field //alone// does **not** constitute a unique message identifier, so don't try to use it as one!+The serial number (''serialno'') field generated by Synchronet and its utilities is a mathematical sum of the area-unique ''<msgnum>'' and a number derived from the date and time the message was created so as to maximize the use of the allocated 32-bits. The serial number will be unique among all the messages generated by a Synchronet-system in a single message area (echo), but is not guaranteed to be unique, by itself, among //all// the FTN-connected message areas of a single Synchronet-system. The ''serialno'' field //alone// does **not** constitute a unique message identifier, so don't try to use it as one!
  
 **But it doesn't //look// like other other FTN MSGID's!?!** **But it doesn't //look// like other other FTN MSGID's!?!**
faq/misc.txt · Last modified: 2023/12/16 00:03 by digital man
Back to top
CC Attribution 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0