Subj : Re: Nightmares / Dreams
To   : Andre
From : echicken
Date : Mon Apr 04 2022 13:17:11

  Re: Re: Nightmares / Dreams
  By: Andre to Spectre on Sat Apr 02 2022 20:16:41

 Sp>> Bzzzzt, Syncterm is only as good as what is sending the data, any
 Sp>> legacy 

 An> Yes, that's what I said. When you use Synchronet with SyncTERM, you don't
 An> have the problem. 

I'll only add translation of encoding *upon posting* to webv4 if the BBS can tell me that a message area requires it, and if the BBS won't do it for me. My preference is to alter the original content only when necessary, and then at the last possible moment.

There may be other steps I need to take, like adding metadata to the message to identify its encoding, but I'm pretty sure Synchronet already does that for me.

In an ideal dreamworld the message would be saved raw and untranslated and only mutated as needed. This would happen at one of these stages, by order of preference:

1) By the client prior to display to the user
2) By the BBS prior to sending to the client
3) By the BBS when saving/importing the message
4) By the uplink prior to sending to the BBS
5) By the originating system prior to exporting to the network
6) By the originating system prior to saving the message
7) By the client prior to posting the message

I get that steps 1 and 2 may not be achievable, that steps 3 and 4 are unlikely, and that leaves people using older software in the lurch, but meh. I don't want to pander to the lowest common denominator just to avoid the odd garbled character.

I'd prefer that systems not alter my words if at all possible, and that they be displayed in their original form whenever possible.
  
---  
echicken   
electronic chicken bbs - bbs.electronicchicken.com
 * Origin: electronic chicken bbs - bbs.electronicchicken.com (21:1/164)

.