IRC bouncer
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
edef 973f19b4fe
Reference openssl(1) by absolute path
1 week ago
rc.d Set up /var/run/calico and /usr/local/etc/pounce 1 month ago
.gitignore Revert "Test getopt_config" 3 weeks ago Assume LibreSSL from brew on Darwin 1 month ago
LICENSE Change license to GPLv3 1 month ago Simplify 1 week ago
Makefile Reference openssl(1) by absolute path 1 week ago
README.7 Add capsicum note to README 3 weeks ago
bounce.c Reference openssl(1) by absolute path 1 week ago
bounce.h Reference openssl(1) by absolute path 1 week ago
calico.1 Document calico service configuration 1 month ago
client.c Fix wordcmp return value when the words have differing lengths 2 weeks ago
compat.h Fix compat.h for #defined strlcpy 1 month ago
config.c Revert "Test getopt_config" 3 weeks ago
dispatch.c Avoid a couple VLAs with constant size 2 weeks ago
local.c Avoid a couple VLAs with constant size 2 weeks ago
pounce.1 Mention the name CertFP in SASL EXTERNAL guide 2 weeks ago
ring.c Save and load full struct timeval 3 weeks ago
server.c Change license to GPLv3 1 month ago
state.c Declare globals as extern in headers, and define in source file 2 weeks ago


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

     pounce – IRC pouncer :3

     pounce 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
     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.

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

     calico(1), pounce(1)

Causal Agency                  November 10, 2019                 Causal Agency