irc.binrev.net

34 posts in this topic

Due to some unfortunate incidents with the administrators of CryptIRC, BinRev has moved its official IRC server. You will need to reregister your handles and channels. Work is still being done on the IRC server, including stats and kwotes. Please be patient as we work to resolve any bugs and add necessary features. The new server is located at irc.binrev.net. You can join in the same channel as always (#binrev). Please start making the transition off CryptIRC and on to irc.binrev.net.

Share this post

Link to post

Share on other sites

Due to some unfortunate incidents with the administrators of CryptIRC, BinRev has moved its official IRC server. You will need to reregister your handles and channels. Work is still being done on the IRC server, including stats and kwotes. Please be patient as we work to resolve any bugs and add necessary features. The new server is located at irc.binrev.net. You can join in the same channel as always (#binrev). Please start making the transition off CryptIRC and on to irc.binrev.net.

Thanks for the patience and all you do to further the community.

I have created an offical HPR channel for all of you HPR fans (all two of you perhaps.... ) swing by #HPR on the new IRC server and chat with the admins and hosts of HPR.

Share this post

Link to post

Share on other sites

Nothing sinister. We just outgrew the server and had needs that we wanted to administer for ourselves. We will now be able to put up some new features that we control and maintain. We will announce them as they get installed instead of teasing in advance...although I guess that is a tease in and of itself.

For now, we are setting up channel for the assorted BinRev meetings as well as a few other topical channels. If anyone has any specific requests for channels (nothing illegal like warez), please let us know.

In the meantime, services are up and running and everyone should register at irc.binrev.net and idle with the rest of us.

Share this post

Link to post

Share on other sites

SSL is currently enabled, but the firewall rules keep getting reset, blocking SSL. Use non-SSL (port 6667) for now.

If anyone is having problems reaching it on TCP Port 6667, you could be getting blocked by your firewall. Try www.firebind.com to determine if 6667 is "open" to the Internet or not. You should be able to do http://www.firebind.com/6667 and get immediate results.

Firebind tests whether your IP device can make outbound connections to the Internet or not. It's not a port scanner - instead it's a "path scanner."