I noticed that but that is what happend when I plugged
irc.synchro.net into hexchat in the server name field and told it to
connect. I did *not* put *any* info in there for
endofthelinebbs.com.
I can only assume that came from the host end as I only saw that response the one time it connected. The other few times, when it got other errors or timed-out, that erroneous address didn't show up.
Simple turn off TLS in the IRC client and it'll use TCP port 6667 (didn't I already explani this?) and work. Or heck, just use the IRC option from the cha
menu on your own BBS!
I noticed that but that is what happend when I plugged irc.synchro.net into hexchat in the server name field and told it to connect. I did *not* put *any* info in there for endofthelinebbs.com.
irc.synchro.net is a rotating hostname, it points to *all* of the IRC servers (and there's a lot of them). That can be seen using tools like nslookup, host, dig, etc.:
Do you remember when you ranted about facebook? File this under the same BS. If it was my project and a contributor decided they didn't want to bother following along in the BBS support echo... you know, for a BBS software project... they'd be off the project.
Re: Re: letsyncrypt issue By: Dumas Walker to DIGITAL MAN on Sat Feb
14 2026 09:28 am
Do you remember when you ranted about facebook? File this under the
same BS. If it was my project and a contributor decided they didn't
want to bother following along in the BBS support echo... you know,
for a BBS software project... they'd be off the project.
So I'm fired? That should improve things around here.
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 13 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 32:31:48 |
| Calls: | 211 |
| Files: | 21,502 |
| Messages: | 80,995 |