• docs/doordrop_ini.md

    From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Oct 1 13:35:41 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/0248569e08a9dcb57719369a
    Added Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.7, renamed from DROPFILE.INI

    The customary file name is now DOORDROP.INI and the environment variable DOORDROP_INI. DROPFILE.INI was too close to the DROPFILE.### of DTS-0001,
    the 1992 named-value proposal the draft cites as prior art, and the
    rename comes before more implementations hardcode the old name (one
    host already shipped against draft 0.3 under it).

    The document moves to docs/doordrop_ini.md. The status section records
    the old names so readers of earlier drafts and that implementation can
    connect the two, and the naming open question is closed.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Oct 1 13:35:41 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/4faf457476657584a07bd244
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.7: add ATASCII

    ATASCII joins the character set names for COMM_CHARSET and TERM_CHARSET
    and the TERM_TYPE tokens, modelled on PETSCII: it is a glyph set and a control-code set at once, with 0x9B as end of line. The can't-use-this-
    charset message rule notes that CR LF shows as graphics on an ATASCII
    terminal. Closes the ATASCII open question; Synchronet never writes it.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Oct 1 13:35:41 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/943ea2fe7aea9d2cc06b76cf
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.7: why FILE_UTF8 rather than FILE_CHARSET

    Close the "other file encodings" open question with the reason: a bool
    the host may only set for a door that declared UTF-8 support keeps the
    decoding burden on the host, which can always transcode to CP437 or
    UTF-8, whereas an open-ended charset name would oblige every door to
    handle or refuse whatever a host might write.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Oct 1 20:45:34 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c3fc2fd1248277547a68e89a
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.7: FILE_TIME is a datetime, not ascii

    Add a datetime type, YYYY-MM-DDThh:mm:ss with an optional UTC offset in
    RFC 3339 form, and give FILE_TIME that type instead of carrying its
    shape in prose under an ascii type. Nothing a producer writes changes.
    The date type stays date-only; a reader wanting only the date of a
    datetime takes the text before the T, as NuSkooler suggested on the
    GitHub mirror.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Oct 1 20:45:34 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/806df3e58bf8190825904e41
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.7: COMM_TYPE is what the door sees

    Say that an emulator's TCP connection back to the host is not the
    door's comm type: a DOS door on a DOSBox null-modem port still sees a
    COM port, so its type is fossil or uart. Narrow the connect-back open
    question to a native door that connects itself, note that no known
    door or host does, and list what such a type would need.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Oct 2 13:33:51 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/6be4cdaf0f99c0a86f03811b
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.8

    Incorporate Deuce's review on r/bbs (2026-10-02):

    - PETSCII and ATASCII are families of character sets, not single
    mappings; the names say which family, a door confines itself to what
    the members share, and a later draft may add a way to name a member
    - USER_KEY is required (unless local): the host, which knows whether its
    user numbers are reused, derives a never-reused key, so a door always
    has one field to key per-user data on
    - TERM_COLORS names which SGR color methods the terminal honors (8, 16,
    256, 16777216), replacing the claim that every ANSI terminal has the
    CGA palette; 8 covers terminals that render SGR 1 as bold, not bright
    - FILE_TIME is required: it is the moment TIME_LEFT was measured, and a
    door whose clock agrees with the host's may subtract the time since
    - The path type names the encoding the door's runtime expects for file
    names (POSIX bytes, the Windows ANSI code page, the DOS path), and a
    path that can't be represented is left out
    - The file's encoding is stated as a rule (UTF-8 iff a line is exactly
    FILE_UTF8=1), and comparisons are exact except IANA charset names
    - A door that looks the file up by name looks for DOORDROP.INI in that
    exact spelling; no case folding
    - The key-prefix trade is stated plainly

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Oct 2 13:33:51 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/12c2e1b1959b6b994440a2d1
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.8: name the PETSCII and ATASCII members

    The bare names now mean the member everyone implements, the C64 set and
    the standard Atari 8-bit set, and a producer that knows the connection
    uses another member names it with a hyphen after the family:
    PETSCII-C128, PETSCII-VIC20, PETSCII-PET, ATASCII-INTL. A consumer that
    doesn't know a member falls back to the family. The PETSCII case modes
    are runtime-switched, so they are never named, and TERM_TYPE carries
    only the family. Answers Deuce's point that the names were ambiguous.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Oct 2 15:10:06 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/01b8eb2fcc5b8aa6fa6ccdee
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.8: FILE_UTF8 depends on the door, not content

    Say that a producer sets FILE_UTF8 from the door's declared UTF-8
    support, writing 1 even when every text value in a session happens to
    be ASCII, so the key is stable across runs of the same door and a door
    can rely on it rather than inspect the text.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Fri Oct 2 19:25:26 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/406810c707725dc9fd960608
    Modified Files:
    docs/doordrop_ini.md
    Log Message:
    docs: DOORDROP.INI draft 0.8: sections mandatory to write, optional to read

    State the asymmetry in one sentence, answering Deuce's question on r/bbs
    of whether a compliant reader could fail on a compliant writer's file:
    every producer writes section headers, so a reader that requires them
    and one that ignores them both parse every conforming file.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net