From Newsgroup: alt.bbs.synchronet
Dear All,
<context>
As I build my way through self-hosting, I realize that one software package cannot fit all the requirements. So I started hosting auxiliary services around synchronet, and I handle the auth of those services with openldap.
One of those services is an internal IRC server. I speculate that most of my potential users will be computer-illiterates with little patience to learn stuff (even if my ultimate goal is to teach them all that, while learning most ef it too). So to have some modern chat feeling (remember chatlog, multiple device, same appearance), I have successfuly setup a ZNC bouncer accessuble from the outside, that auths to openldap.
Feeling great about this little success, in an effort to unify this auth scheme, I tried to switch from the internal synchronet's irc server to an inspircd server.
</context>
However, because inspircd is utf8, and irc.js is cp437, I have some encoding issues that I have tried to quickly patch this way:
* function get_command `line.sock.recvline` has an extra step: `utf8_decode`
* function send_cmd `sock.send` has an extra step before: `utf8_encode`
Typing all this twice (the editor crashed in between), I wonder:
1) why is irc.js sending cp437 and not utf8 ? it seems to me that always sending utf8 would improve compatibility with existing servers there
2) is replacing synchronet's irc's server a good idea ? it seems to me that having one single way of authentificating per service-type would save me some troubles later, but as I am pretty new to IRC hosting, maybe you have some advices and stories to share related to this ?
Thanks in advance for your answers and precious knowledge there,
Best,
martylake
--- Synchronet 3.19a-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California -
telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113