README(7) FreeBSD Miscellaneous Information Manual README(7)

IRC pouncer :3

pounce(1) is a multi-client, TLS-only IRC bouncer. It takes a simple approach, using a multiple-consumer ring buffer and the IRCv3.2 server-time extension to communicate with clients.

pounce requires LibreSSL (-ltls) and targets FreeBSD. It can also be built on Darwin or GNU/Linux by copying the appropriate file to config.mk and modifying as needed. On FreeBSD, processes are sandboxed with capsicum(4). On other systems, who knows what might happen?

As a former znc(1) user, I was dissatisfied with the multi-client experience it offered. I wanted to connect from both my laptop and my phone and have full chat history on both. With znc(1), my options were either having both clients spammed with redundant history every time they connect, or having one client consume the buffer and the other get no history at all.

With a multiple-consumer ring buffer, each client has its own place in the history and can be brought up to date independently. Additionally, by expecting clients to implement the server-time extension, all events can be accurately replayed, rather than being limited to messages.

declarations and common functions
configuration and event loop
local server binding
remote server connection
remote client connections
state shared between clients
buffer between server and clients
getopt_long(3)-integrated configuration parsing
SNI socket dispatch
compatibility with lesser operating systems
FreeBSD rc(8) scripts

The upstream URL of this project is ⟨https://git.causal.agency/pounce⟩. I'm happy to receive contributions in any form at <june@causal.agency>. For sending patches by email, see ⟨https://git-send-email.io⟩.

calico(1), pounce(1)

Central logging with full-text search: litterbox

January 17, 2020 Causal Agency