Enhancement #464
closed
Revaluating our IRC server software
100%
Description
I'm willing to stop maintaining this software which is badly maintained. The authors are not responsive, do not do much maintenance by themselves, and do not seem really willing to integrate proposed patches.
We should reevaluate existing and alive solutions. Having working SSL links is a requirement
Maybe using a software used by another large network would help having a properly maintained software, but it could also mean being exposed to the same security problems.
Updated by Marc Dequènes over 9 years ago
- Related to Bug #79: IRC S2S SSL linking does no work added
Updated by Marc Dequènes almost 9 years ago
Pilou suggested InspIRCd + Anope (or Atheme).
Updated by Marc Dequènes almost 7 years ago
- Status changed from New to In Progress
- Assignee set to Marc Dequènes
I looked into it and stumble onto the IRCv3 initiative.
Charybdis is the server reference and being a fork from Ratbox it would not require much configuration change. Nevertheless I'm not comfortable with this code, knowing there was TLS linking problems in Ratbox and that's a feature we'd like to have. Also the modularity of Inspircd is interesting and the project much better documented.
Anope is not well documented compared to Atheme.
Inspircd is listed as legacy support for IRCv3 specs but in fact it is no longer true: https://ircv3.net/software/servers.html
(the feature liasted as Extras/git are all in the main codebase now).
So I've decided to give a try to Inspircd+Atheme. I plan to shutdown the services (we can live without it) and take one of the servers out of rotation to convert it. I'll announce changes to the users soon.
Updated by Marc Dequènes almost 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Branch set to irc_improvements
Here it is, with Ansible rules.
Updated by Marc Dequènes over 4 years ago
- Entity changed from DuckCorp to MilkyPond