Created attachment 214729 [details]
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.
Created attachment 215562 [details]
pounce 1.3p1 diff
Updated to 1.3p1.
Take it. I am juggling with the svn diff output to include it in git and update to the latest version, but the calico and pounce rc scripts are missing. Do you have them at hand?
Created attachment 224759 [details]
Update to 2.3
Port updated to the latest version, tweaks to cope with libretls / libressl as done for catgirl. I removed the rc scripts since they do not exist.
I still need to setup all this to confirm it's working as expected. In the meantime, if you can provide the rc scripts, I will be happy to reintroduce them.
Created attachment 224762 [details]
Update to 2.3 with openssl path fix
Meh, the full path to openssl depends on the version of openssl used.
I see that the rc-scripts where probably not the easiest way to manage multiple instances of pounce, and where removed… Do you intend to push catsit in the FreeBSD ports?
BTW: I am running this code now (without calico: single server), seems to be smooth so far :-P Thanks!
Yeah I removed the rc scripts since they were hacky and I had them in-repo which isn't where they belong. They could maybe be pulled out of git history: <https://git.causal.agency/pounce/tree/rc.d?id=b93f3f96845fc1fa1f1b80829f3573a11b13b907>, although I don't think they're quite accurate anymore either since pounce now wants to load configuration from ~/.config.
catsit does a better job, but I guess I'm hesitant about adding an extra port for a rather particular process supervisor and creating a soft dependency on it. On the other hand, it would be awkward to package pounce without a reasonable way to run it. I kind of feel like I'd be imposing on the ports tree by requiring some special method to run my software. Really depends on how much demand there is to run pounce on FreeBSD, I suppose.
I have not tried the rc scripts yet: when I saw they where prune in favor of catsit I directly though that making catsit available in the ports might be something you are interested in. In any case, that's not incompatible for pounce/calico rc scripts.
AFAIAC, I currently run a single instance of pounce in tmux, so my needs are minimal and the rc-scripts will be enough.
With the support of ~/.config, maybe we must ensure that $HOME is properly set. I'll give it a try in the next few days.
Created attachment 224917 [details]
Patch for pounce 2.3
Latest patch that also set $HOME to the correct value.
I am running this with the following in rc.conf:
And ~romain/.config/pounce/freenode has the following:
host = chat.freenode.net
nick = smortex
user = smortex
pass = secret
join = #riemann,#voxpupuli
save = freenode
local-ca = auth.pem
local-cert = freenode.irc.blogreen.org.crt
local-priv = freenode.irc.blogreen.org.key
local-host = freenode.irc.blogreen.org
Does this look reasonable for you?
I think everything related to pounce_chdir/ETCDIR/"etc/pounce" should probably be removed, since pounce now looks in $HOME instead of CWD. I'd like to add some documentation to the rc scripts too that I used to have in the manual somewhere, I'll try to update the patch with both.