Log | Files | Refs

commit 1579cb0aa3e44a5a8e5d4d461154e7e507d2def6
parent ec8b7da2bf81ef9c5b36dbfd5bd4414689dc412d
Author: Josuah Demangeon <>
Date:   Sun, 19 Apr 2020 12:12:42 +0200

add more words about jj

Mwiki/jj/ | 45+++++++++++++++++++++++++++++++++++----------
1 file changed, 35 insertions(+), 10 deletions(-)

diff --git a/wiki/jj/ b/wiki/jj/ @@ -9,6 +9,33 @@ simply logs the output of each channels to plain files. [jj]: [irc]: +Instead of being an ncurse program that runs into tmux(1), jj works as an +applicative router. A router for ISO layer 7. You may already know "applicative +routers" for different protocols already: + + * SMTP: [OpenSMTPD][m1], [qmail]][m2], [Postfix][m3]... + * HTTP: [nginx][h1], [lighttpd][h2], [relayd][h3], [haproxy[h4]... + * SIP: [OpenSIPS][s1], [Kamailio][s2]... + * IRC: [ngircd][i1], [hybridircd][i2]... + +[m1]: +[m2]: +[m3]: +[h1]: +[h2]: +[h3]: +[h4]: +[s1]: +[s2]: +[i1]: +[i2]: + +IRC itself is much of a routing protocol server-side: routing messages to +the right client. Another aspect of applicative routing is client-side. + +Much like ii or sic, and all the modular bots in the wild, the jj acts as +a is a client-side IRC router through hooks and log files. + How jj works ------------ @@ -196,16 +223,14 @@ Instead of going with tmux for handling all the log files to follow, I went with the approach of reading all channels of all networks in a same stream, showing a headers for each channel (at least in my fork of jjp): - - 00:12:30 TikityTik: it's like having a bad fever dream with this ISP - - - 00:12:34 cinap_lenrek: when usb is enabled sounds like a vm? - 00:12:36 cinap_lenrek: whats the context? - - - 00:12:36 thrig: Logan Runners? - 00:12:37 epsilonKNOT: with blackjack and hookers + == == + 00:12 ikityik: it's like having a bad fever dream with this ISP + == == + 00:12 cicl: when usb is enabled sounds like a vm? + 00:12 cicl: whats the context? + == == + 00:12 thrig: Logan Runners? + 00:12 knot: with blackjack and hookers To avoid being bothered with too many channels at once, it takes a list of find(1) -path $filters as argument that will match the name of the