Subj : FSP-10xx-1: BBSID Kludge Specification
To   : Alexey Vissarionov
From : Rob Swindell
Date : Wed Dec 27 2023 18:52:35

  Re: FSP-10xx-1: BBSID Kludge Specification
  By: Alexey Vissarionov to Rob Swindell on Wed Dec 27 2023 01:22 pm

 > Good ${greeting_time}, Rob!
 >
 > 26 Dec 2023 15:05:26, you wrote to All:
 >
 >  RS> Since BBSes that support QWK packet technology must
 >
 > Must?
 >
 >  RS> already have a globally unique ID (the so-called BBS-ID or "Board ID"
 >
 > What happens if a BBS lacks such ID?

The QWK packet standard requires a BBS ID. If a BBS supports QWK, it must have one.

 >  RS> from which their QWK packet files are named),
 >
 > What if BBS doesn't use QWK?

Then the BBS may not have a need for a BBS ID.

 >  RS> it made logical sense to reuse this same ID as the method of
 >  RS> correlating any message received via FidoNet with the avatar data
 >  RS> stored
 >
 > Where?

Out of scope of the document.

 >  RS> for the message author.
 >
 > Author or BBS?

Avatars are associated with an author which is a user on a BBS.

 >  RS> BBSID: <bbs-id>
 >  RS> Where <bbs-id> is a string of between 2 and 8 monocased ASCII
 >  RS> characters, begining with an alphabetic character (betweeen 'A' and
 >  RS> 'Z' inclusive).
 >
 > The word "monocased" reduces the characters to letters.
 >
 >  RS> Only MS-DOS compatible filename characters may be included in a
 >  RS> BBS-ID.
 >
 > DOSes are dead for over 20 years. What is the reason for such limitation?

The same answer I gave previous, for QWK packet compatibility.
-- 
                                            digital man (rob)

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 55.9øF, 90.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.