Also due to recent work, ChanServ/NickServ are sadly unavailable. This is because of some yet unlocated bug that slipped into the new WeIRCd development version used on the server that trashes the services bots. I assume I'll be able to fix it in a day or two - please excuse the inconvenience.

Thanks to Xjs and all the others (ZNC devs!) for help with getting SSL to work!

Regarding our server software, we might soon have reverse lookups of IPs for proper hosts of guest users since that's what I'm working on these days. That will hopefully make banning spammers easier.

The most important fixes are:

• The windows GUI will no longer crash when browsing the settings
• A crash issue triggered by ISON has been resolved
• Fixes in the MODE parser and general IRC command parser
• ChanServ will now properly save changed topics
• Services operators can now finally force channels to be dropped through ChanServ

And apart from that other minor fixes and improvements have been done (you can look at the detailed changelog here).

Although you will find many, many traces of it, please note serverlinking is NOT working at all and still extremely under construction - it is being worked on though and as I run out of other things to do I will eventually get it done :-P

Also the graphical admin panel is at the moment missing a lot of options. This will be fixed aswell with the coming releases so that admin accounts, listener ports and all this can be edited through it.

The website can't be saved in such a case. But multiple chat servers that form together a bigger network are a wonderful way to provide more redundancy and substitute chatting places when the main server which hosts channel/nick registration services and website goes down. A website and NickServ/ChanServ downtime isn't nearly as bad as the complete chat being gone.

Therefore, this did pressure me again to jump back into server linking support for WeIRCd. I am going for the TS6 protocol, although ircd-ratbox and others of the mulitple IRCds that already support this protocol are probably not to be linked with WeIRCd as WeIRCd will extend the protocol to support halfop status. Maybe there will be a hack to link anyway, we'll see.

At the moment, work is still being done at the basic facilities: the config parser and a module api for linking modules, so basically any kind of linking (also to other services like messengers) will be possible through a plugged-in module. I hope to engange in the first linking tests in the close future though.

There are no security updates, only a memory leak fixed - so updating is still advised.

I'm not having too much time so investigation needs to wait a bit. I'll most likely have more time on Friday to find out more on this. Sorry for the long downtime, I'm just pretty busy so it took some time until I noticed the server was gone.