On 06 Dec 2021, g00r00 said the following...
g0> Mystic has unique article IDs across all message bases and messages and the
g0> server is capable of properly responding to them but its disabled.
That's cool to hear at least. I hadn't guessed it was developed that far.
g0> The problem I face before I can enable it is this: JAM message bases do
g0> not have any sort of message serialization other than the message number
g0> which can change (making it not useful). Because of this, every message
g0> must have a MSGID (even local messages) for this system to work.
g0> ...
g0> Long story longer, that is the challenge: Making sure MSGID exists on every
g0> message on your BBS. The limitation isn't on the NNTP side of things at
g0> this point. I can make sure Mystic does it but for those who use third
g0> party utilities that could be problematic.
g0> I am not sure how various newsreaders treat messages without an article
g0> ID (ie an article ID of <0>).
Yeah third party tossers would certainly throw a monkey wrench regardless of
what Mystic does. Without a stored MSGID you could possibly use other fields to
generate a consistent NNTP message ID on the fly but then the question would be
what fields are sufficiently static and up to the task? Some combination of
datewritten + sendername + the message base name?
AFAIK at least for the Mozilla-based readers, they would treat everything with
message ID 0 as the same message, making the first article downloaded with ID 0
"it" for all of them. So yeah that'd probably be worse.
... DOS=HIGH? I knew it was on something...
--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)
|
