On Sunday, November 4th apam was heard saying...
 Ap> Sorry to hear about your crash. It can be completely demoralizing when 
 Ap> you lose a whole chunk of work on something.

Yeah I guess it was lucky that it happend around Halloween-ish time when I'm
super busy with prop projects anyway hehe


On Sunday, November 4th apam muttered...
 Ap> As for the syncterm issues, I always build syncterm from the latest daily 
 Ap> source and it now works with Magicka (LibSSH which is OpenSSL based I 
 Ap> think). Though it never used to with the 1.0 version. I just tried the 
 Ap> latest version on Xibalba, and it didn't work must be some weird bug in 
 Ap> cryptlib or node.js ssh. Don't know if that helps at all, you've probably 
 Ap> already made all those observations  Oh the other thing LibSSH works 
 Ap> with Xibalba too (ie MagiTerm works)

I ended up sending Deuce a mail, then right after that I had a revolution: What
 if it just does't agree with some of the algorithms. So, I enabled everything
SSH2 supports (vs the default set) and viola! It seems for e.g. SyncTERM wants
to use older (deprecated, really) KEX, cipher, etc. I'll have to send Deuce a
updated mail on that. For now, ENiG will support them as well by default but
let users override in their config.hjson files.


On Sunday, November 4th apam was heard saying...
 Ap> I need to rewrite MagiTerm. It's performance is bad, I only really 
 Ap> noticed when I tried it on my Raspberry PI. Also thinking about adding 
 Ap> telnet support, but it's hard to get motivated as SyncTerm works so well 
 Ap> on most of the platforms I use.

Well I hope you get back to it. I quite like MagiTerm  At some point, I'd
really like to turn VTX into a client side application with a phone book/etc.
Codewar65 has done an amazing job with it (and I hope he continues) and IMO
it's the best web client... but having a phone book and the like would be
great.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
 * Origin: After Hours|The Villages,FL|afterhours-bbs.com (1:123/130)