• docs: DOORDROP.INI draft 0.8: FILE_UTF8 depends on the door, not conte

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Oct 5 11:54:31 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/01b8eb2fcc5b8aa6fa6ccdee975458604d68e458#note_10607

    Agreed. I've removed the sentence. A door that can't decode UTF-8 now MUST reject a file with `FILE_UTF8=1`, so the key stays the only authority on the encoding.

    -- *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Sat Oct 3 05:42:38 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/01b8eb2fcc5b8aa6fa6ccdee975458604d68e458#note_10603

    `The value depends on the door`

    No, it doesn't. The *correct* value depends on the door, but the value depends on the configuration of the producer which now *must* be correct...

    `a door can rely on it rather than inspect the text`

    Suggesting the door can ignore the key and just read the mind of the producer is terrible guidance... it effectively creates two separate dropfile formats with the same name, one in CP437 and the other in UTF-8.
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)