IRC bouncer
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
Causal Agent 90da3f7341
Mention the name CertFP in SASL EXTERNAL guide
12時間前
rc.d Set up /var/run/calico and /usr/local/etc/pounce 2週間前
.gitignore Revert "Test getopt_config" 6日前
Darwin.mk Assume LibreSSL from brew on Darwin 1週間前
LICENSE Change license to GPLv3 1週間前
Linux.mk Use -l:filename in Linux.mk 1週間前
Makefile Revert "Test getopt_config" 6日前
README.7 Add capsicum note to README 1週間前
bounce.c Request NAMES on sync by default 3日前
bounce.h Request NAMES on sync by default 3日前
calico.1 Document calico service configuration 1週間前
client.c Add concept of passive clients 3日前
compat.h Fix compat.h for #defined strlcpy 1週間前
config.c Revert "Test getopt_config" 6日前
dispatch.c Declare more missing functions and deal with lack of SO_NOSIGPIPE 1週間前
local.c Rename listen to local 1週間前
pounce.1 Mention the name CertFP in SASL EXTERNAL guide 12時間前
ring.c Save and load full struct timeval 3日前
server.c Change license to GPLv3 1週間前
state.c Request NAMES on sync by default 3日前

README.7

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

NAME
     pounce – IRC pouncer :3

DESCRIPTION
     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 config.mk
     and modifying as needed.  On FreeBSD, processes are sandboxed with
     capsicum(4).  On other systems, who knows what might happen?

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

FILES
     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

SEE ALSO
     calico(1), pounce(1)

Causal Agency                  November 10, 2019                 Causal Agency