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

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

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

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

https://gitlab.synchro.net/main/sbbs/-/commit/dcaccecb5f7029edab20a8eb
Modified Files:
docs/doordrop_ini.md
Log Message:
docs: DOORDROP.INI draft 0.8: a door that can't decode UTF-8 rejects it

Remove the sentence 01b8eb2fcc (doors-3-clip, 2026-10-02) added saying FILE_UTF8 depends on the door, not the content, and that a door can rely
on it rather than inspect the text. What a producer writes depends on its configuration, and the wording invited a door to assume an encoding from
its own configuration instead of reading the key. ASCII is valid either
way, so the key needs no stability across sessions.

In its place: a door that can't decode UTF-8 MUST reject a file with FILE_UTF8=1. Doors are not required to support UTF-8.

Say the Synchronet implementation's FILE_UTF8 depends on the door's configuration rather than on the door.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net