Subj : MRC Module
To   : Digital Man
From : echicken
Date : Wed Feb 23 2022 03:59:27

  Re: MRC Module
  By: Digital Man to echicken on Tue Feb 22 2022 18:15:46

 DM> Does it barf if a user sends a message containing a '~' character maybe?

Technically not barfing (as in crashing or doing anything it shouldn't) - these lines are illegal; it's logging but otherwise ignoring them.

The protocol description I was given in 2019 says:

- Each 'message' is a single line of seven ~ delimited fields
- Each message is terminated with a ~ and a newline
- No field may contain the ~ character
- Only ASCII 32-125 are permitted in any field
 - Some fields only allow ASCII 33-125
- Any message not conforming to the above must be dropped

I have a suspicion that these are long messages being broken up into multiple lines, with subsequent lines lacking all but the "message text" field. Very possibly the protocol was amended to allow this but I didn't hear about it (or
ignored it).

Or there's a busted client out there sending bad messages.

I've heard of two people working on MRC-related things in recent months. If these errors are new, maybe they're related. (Meatlotion, are you reading this?)

That's it for this edition of the MRC super funtime show. Thanks for tuning in.
  
---  
echicken   
electronic chicken bbs - bbs.electronicchicken.com
---
 þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.