– IRC News

All about Internet Relay Chat

UnrealIRCd Makes a Drastic Change

UnrealIRCd has decided to make a drastic change in it’s project. They decided to, instead of writing a new Unreal4 in C++ Aspects, to instead fork InspIRCd; a completely modular IRCd that has been gaining interests over the years. This change is due in large because of Syzop going inactive (Article) and their only being one head developer (Stskeeps) left to run the projects.

UnrealIRCd has decided the following with their projects. To produce 3.2.* a bit further, scrap Unreal3.3* (for now) and to keep the main focus on Unreal4, which they feel will be a big hit in the IRC community. “The goals for that project currently is to produce a 3.2.8, which may be the last in that branch – we have practically given up on trying to improve further on the basic things of the IRCd” explains Stskeeps. “The existing 3.3.* code will be turned into a 3.2.8 instead“. But don’t worry, Unreal still plans on releasing bug & security fixes for Unreal3, because they couldn’t expect everyone to just halt their networks.

I went on to ask Stskeeps what other reasons they decided to fork InspIRCd, and the response is in conjunction with Syzop leaving. “In the light that we simply don’t have the manpower to start something properly from scratch and complete it – and the Unreal3.* branch going towards a slow halt / brick wall which we cannot pass, we have decided to do a radical change in strategies.” Stskeeps goes on explaining, “For years now InspIRCd has been a recode in C++ of IRCd, targetting modularity and “fresh” code – and this IRCd has many facets that are alike UnrealIRCd, so through some talks, we have decided to fork InspIRCd for Unreal4 – creating a user experience that uses InspIRCd inside, but feels to client/admin as an UnrealIRCd.”

A lot of people may be thinking, “Is this a way to take down InspIRCd?” No, quite the opposite. “This is not a unfriendly fork or us trying to steal InspIRCd’s sunshine – we are working together with InspIRCd to cover the entire IRCd feature spectre, so people can run InspIRCd bare, or colourful (Unreal)” explains Stskeeps.

Also, UnrealIRCd has given InspIRCd proper credit for the fork, to ensure that it’s a friendly fork. In their /Credits, for Unreal4, users will see:

* Based on the original code by the InspIRCd development team

* (C) 2002-2007 InspIRCd Development Team

* –

Which is what the InspIRCd team members wanted, and Unreal was more then happy to provide.

So, as UnrealIRCd focuses on it’s new projects, and it’s old ones, I’m sure we can all expect the IRC community to change drastically, and, for the best.

A few side notes for those running InspIRCd and/or UnrealIRCd. Unreal4 will be able to link to InspIRCd if they’re running the same modules. The idea is to make them compatible incase either of the projects do end up dying. Also, you can take modules from either party to the IRCd they want. UnrealIRCd is also planning on being able to line Unreal3* and Unreal4* which, if they work it out, will be able to link to InspIRCd.

Article written by Bricker

Syzop resigns his position on the UnrealIRCd project

Today, In an unexpected announcement on their homepage and an email to all the official testers, Syzop has officially resigned his position as Head Coder and maintainer of Unreal 3.2*. “Having severe wrist issues (RSI) has forced me to have surgery, but the doctors don’t know if that will help” says Syzop, now former coder of UnrealIRCd project.

“I’m not sure if I’ll ever (be able to) get back, and if so, in what kind of shape or form (I certainly would love to get back)” explains Syzop. With Unreals’ recent “call for help”, I think a lot of people have been anticipating this would happen, but I don’t think any body knew it would be this fast.

However, Syzop wants to be sure to thank all the help he’s received and asks that if you are still interested in the UnrealIRCd project, to step forward.

As for Unreal3.2* & Unreal3.3*, Stskeeps will be the maintainer and do all of the administrative tasks. “I’ll still be selling my paid modules, but nothing else relating to the project for now” explains Syzop. For some, this may end up being a good thing, but for most of the IRC community, they fear what will become of the UnrealIRCd project.

Stskeeps wasn’t around to make any statements based on the many questions users are asking, but those of you who are interested should keep up with the website and forums. In a final message from Syzop, “Various people have jumped in to help with coding after my request last month, so I don’t think the existence of Unreal will be in any danger”. I guess only time will tell, but for those of you wishing all the best to Unreal and Syzop, all you can do now is pray, or help.

Article by Bricker

AngryWolf quits Unreal Module development

On his website AngryWolf announced he will stop development of modules for the popular UnrealIRCD server package. “I’ve been so busy for more than one month that I couldn’t do any updates on the site and on my modules since then”, AngryWolf explains. “I just can’t do these anymore. They mean too much work for me, even because I’m having university.”

One of the Unreal developers Codemastr said in a reaction: “He did a lot of good for Unreal. He was the first one, outside of the Unreal developers, to write modules. I think it was because of him that so many people are now writing modules. I know of many people who don’t even look at the module documentation when they want to write a module, instead they just look at Angrywolf’s existing ones and base it on them.”

The reason for AngryWolf to start module development was “to bring out more of a Hungarian IRC network than UnrealIRCd had offered me that time.” At first he modified the IRCD code, but later changed to using modules as that gave him more possibilities to add new features. “Then, since I noticed that what I code might be useful to others, I shared them with the public.”

Some of the modules he is most proud of himself includes the module that lists available ircoperators with the /ircops command, and jointhrottle which was also considered to be included into the IRCD by one of the developers, Syzop. “Of course, m_chgshois, which you can use to change anyone’s SWHOIS information, also proved to be helpful, but only on those networks not having Anope IRC Services, because it has an extra module for that purpose.”

One of the more controversial modules AngryWolf coded was the m_spy module, of which we posted an article with a interview with him on January 8th of this year. “I can still hear/see opinions like ‘you shouldn’t have coded it’. I was thinking for a long time that even thought people say such things about the module, it could do more good than harm, but I had to be disappointed. Now I admit it was a very bad idea even to bring that module into existence.” AngryWolf as a result removed the possibility to download the module from his website and you have to privately contact him to get the module after that.

There are no current plans to continue development of existing modules made by AngryWolf, and no plans exist for development to be taken over by another person. “Of course I allow anyone to use, improve and update my codes, what I only require is my name represented in their works to indicate, I did something, too”, AngryWolf explained.

“Sorry a lot, and thanks to everyone for helping and supporting me. This page will be closed soon”, the announcement on AngryWolf’s website ends.