IRC formalization #8

Open
opened 1 year ago by DarkFeather · 0 comments
Owner

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

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).
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.