AniNIX/IRC: Migrate from Discord+bridge+KiwiIRC to Fluxer+lightening #48

Open
opened 2026-07-03 13:07:38 -05:00 by DarkFeather · 1 comment
Owner

Today, I have a split stack:

  • InspIRCd runs my underlying daemon
  • Anope manages channels & user authentication to AniNIX/Password (LDAP)
  • Bots provide services
    • TheRaven has my developed utility
    • bitbot offers webhooks
    • npm's discord-irc provides a bridge between cloud Discord and my daemon.
  • KiwiIRC provides a limited webapp access for users.

The problem is that Discord is becoming increasingly problematic, from breaches leaking user data to intrusive age verification that is fundamentally incompatible with the 4th & 5th Amendments and my user ethics.

I should be migrating my community to a better self-hosted stack.

This will require #17 prior to deployment, with the Docker requirements for both the bridge & Fluxer. When the new ecosystem is up...

  • I'll set a date to cut the community over & mark the Discord server read-only.
  • I'll swap the web config from Kiwi to Fluxer
  • I can then decom the old components (discord-irc, KiwiIRC, etc.)
Today, I have a split stack: * InspIRCd runs my underlying daemon * Anope manages channels & user authentication to AniNIX/Password (LDAP) * Bots provide services * TheRaven has my developed utility * bitbot offers webhooks * npm's discord-irc provides a bridge between cloud Discord and my daemon. * KiwiIRC provides a limited webapp access for users. The problem is that Discord is becoming increasingly problematic, from [breaches](https://discord.com/press-releases/update-on-security-incident-involving-third-party-customer-service) leaking user data to intrusive [age verification](https://support.discord.com/hc/en-us/articles/30326565624343-How-to-Complete-Age-Assurance-on-Discord) that is fundamentally incompatible with the 4th & 5th Amendments and my user ethics. I should be migrating my community to a better self-hosted stack. * I will replace both Discord & KiwiIRC with [Fluxer](https://docs.fluxer.app/operator/get-started/) * I will still stitch IRC to Fluxer with [Lightening bridge](https://williamhorning.dev/lightning/bridge/hosting) This will require #17 prior to deployment, with the Docker requirements for both the bridge & Fluxer. When the new ecosystem is up... * I'll set a date to cut the community over & mark the Discord server read-only. * I'll swap the web config from Kiwi to Fluxer * I can then decom the old components (discord-irc, KiwiIRC, etc.)
DarkFeather added the Blocked label 2026-07-03 13:07:38 -05:00
DarkFeather added this to the Kanban project 2026-07-03 13:07:38 -05:00
Author
Owner

I may be able to drop bitbot and the ravensend-daemon functionality if Fluxer can receive the necessary webhooks from the rest of the stack at the time.

I may be able to drop bitbot and the `ravensend-daemon` functionality if Fluxer can receive the necessary webhooks from the rest of the stack at the time.
Sign in to join this conversation.