Subj : testing CHRS kludge
To   : Nick Andre
From : August Abolins
Date : Mon Jun 08 2020 17:45:00

Hello Nick!

 AA>> Just testing see what CHRS kludge this message..

 NA> This isn't because of that stupid discussion in the Fido test echo,
 NA> is it?

LOL

The "5667.fidotest at 4:801/194" != "5667.fidotest@4:801/194" thread is  
stupider.

But.. CHRS info is very useful.


 NA> Don't worry about the CHRS kludge. The people that complain the
 NA> loudest about it have no life, big Dutch suspenders and an idea that
 NA> we will have 30,000+ nodes suddenly sign up tomorrow.

LOL

Come on.. you can't blame a guy for his passion and excitement for IPv6  
and the sudden opening of doors and the additional IoT devices to a local  
network that it implies.

But wrt "fido", I don't think IPv6 is a game changer by any stretch of the  
imagination.

Wrt CHRS kludge, most content here would be good ol' ascii (thus, US- 
ASCII).  But on occassion when a high ascii char slips in, then atleast  
IMB437 makes better sense.  No?


 NA> Even the lack of the MSGID/REPLY kludge is not a big deal, at least for
 NA> me.

Well... here I must disagree just a little but hopefully not so much as to  
tarnish our friendship. ;)   Graphical threading is really cool!  ..and a  
convenient way to navigate a thread if required and/or find a spawned  
message without having to do text searches. It's also really handy to be  
able to identify a specific message by the 8-char "serialno".


 NA> (We can move this thread to MIN_BBS?)

Well..  I never had to "move this thread" with a message that I've already  
started to reply to in one echo, and *not* have the other echo configured  
yet.   But hopefully, I'll figure this out.

[...]

I think I figured it out!


  ../|ug

--- OpenXP 5.0.44
 * Origin: my little micronet point (618:510/1.1)

.