On 08 Mar 2022, Jay Harris said the following...
 
 JH> On 08 Mar 2022, IB Joe said the following...
 JH>  
 JH>  IJ> I have a question, g00r00 can answer, or anyone for that matter... Is
 JH>  IJ> there any reason why in the year 2022 other BBSes cannot support ANSI
 JH>  IJ> the message bases/readers.
 JH> 
 JH> Modern BBS packages support ANSI in the message bases.  Even some
 JH> "legacy" BBS packages support ANSI in the message bases (some with more
 JH> success than others) while other BBS packages won't display ANSI at all
 JH> (showing nothing but garbly goop).
 JH> 
 JH> Since this is a federated network and we can't control who sees what on
 JH> which system we tend to cater to the lowest common denominator.
 JH> 
 JH> Some message networks allow ANSI in certain bases only (BBS ads for
 JH> example) while others encourage adding an [ANSI] tag in the subject so
 JH> those that can't display ANSI can skip those messages.
 JH> 
 JH> 
 JH> Jay
 JH> 

Interesting... I still run a copy of WINServer and any time I read ANSI on that BBS it's messed up, pushes the header up.  Recently MRO, a Synchronet SysOp was complaining that there was a hidden clear screen code within my ANSI ad... This could explain the headers disappearing... I have finally had that come to Jesus moment with WINServer... May delete it forever... But Synchronet puzzles me So... Rob et. al. actively works on that project and you'd think that's where I wouldn't have an issue.  I don't think about things, because Mystic handles this flawlessly...


:) , thanx for your response ...

IB Joe
AKA Joe Schweier
SysOp of Joe's BBS
-=JoesBBS.com=-

... What do you mean, QWK? It took me over an hour to read!

--- Mystic BBS v1.12 A48 2022/02/09 (Windows/64)