IRC formalization #8

New Issue

DarkFeather · 2020-08-27T05:45:21-05:00

DarkFeather commented

2020-08-27 05:45:21 -05:00

We need to formalize a role to install our IRC services. Each should be encapsulated in a handler.

InspIRCd (core transport)
Anope (IRC services)
KiwiIRC (web access)
Discord-IRC (cloud mirror interface)
TheRaven (IRC bot)
BitBot (Gitea chatops)

We've debated on deploying a ZNC service alongside InspIRCd, but I think this violates our no-log stance. Clients can set up their own logs if they want and resume connections, but I want to keep this away from the server.

I'm not going to formalize Discord-Werewolf yet, since it's fragile.

We need to formalize a role to install our IRC services. Each should be encapsulated in a handler. * InspIRCd (core transport) * Anope (IRC services) * [KiwiIRC](https://github.com/prawnsalad/KiwiIRC.git) (web access) * [Discord-IRC](https://github.com/reactiflux/discord-irc.git) (cloud mirror interface) * [TheRaven](/AniNIX/TheRaven) (IRC bot) * [BitBot](https://github.com/jesopo/bitbot) (Gitea chatops) We've debated on deploying a ZNC service alongside InspIRCd, but I think this violates our no-log stance. Clients can set up their own logs if they want and resume connections, but I want to keep this away from the server. I'm not going to formalize Discord-Werewolf yet, since it's [fragile](https://foundation.aninix.net/DarkFeather/migration-tracking/issues/11).

DarkFeather added this to the Kanban project 2022-08-04 00:40:39 -05:00

Sign in to join this conversation.