bf4a589fc5
Accept TLS-encrypted connections from IRC clients. Auto-generates a self-signed EC P-256 listener certificate (bouncer.pem) when no custom cert is provided. Remove CTCP response items from roadmap (stealth by design -- router already suppresses all CTCP except ACTION). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Tasks
Current
- P0: Core implementation (irc, config, proxy, network, client, server, router, backlog)
- P0: Unit tests (irc, config, backlog)
- P0: CLI and entry point
- P0: Stealth connect + probation state machine
- P0: Markov bigram nick generator
- P0: Local DNS resolution + multi-IP failover
- P1: Integration testing with live IRC server (Libera.Chat)
- P1: Verified SOCKS5 proxy connectivity end-to-end
- P1: Documentation update
- P1: Multi-network namespace multiplexing (
/networksuffixes) - P1: Bouncer control commands (25+ commands via
/msg *bouncer) - P1: NickServ auto-registration + email verification
- P1: SASL PLAIN + EXTERNAL (CertFP) authentication
- P1: Client certificate generation + fingerprint management
- P1: PING watchdog (stale connection detection)
- P1: IRCv3 server-time capability
- P1: Push notifications (ntfy/webhook)
- P1: hCaptcha auto-solving (NoCaptchaAI)
- P1: Background account farming (ephemeral connections)
- P1: Configurable operational constants
Next
- P2: Client-side TLS support
- P2: Channel key support
- P3: Systemd service file
- P3: Containerfile for podman deployment