xK - IRC daemon, bot, TUI client and its web frontend

	Commit message (Collapse)	Author	Age	Files	Lines
*	xC: use the relay protocol's RPC for pings	Přemysl Eric Janouch	2022-09-08	1	-0/+2
\|
*	xC/xP: mark highlights and buffer activity	Přemysl Eric Janouch	2022-09-08	1	-1/+17
\| \| \| \|	And more or less finalize out the protocol for this use case.
*	xP: implement buffer line leakage	Přemysl Eric Janouch	2022-09-07	1	-0/+1
\| \| \| \|	Rather than on redisplay, these get cleared on reconnect.
*	xP: implement tab completion	Přemysl Eric Janouch	2022-09-06	1	-0/+2
\| \| \| \| \| \| \| \|	Currently it only goes for the longest common prefix. Refactor WebSocket handling into an abstraction for our protocol. The Go code generater finally needed fixing.
*	xC/xP: pass timestamps with millisecond precision	Přemysl Eric Janouch	2022-09-06	1	-1/+1
\| \| \| \|	Future-proofing the protocol.
*	xC/xP: turn the action asterisk into a rendition	Přemysl Eric Janouch	2022-09-05	1	-0/+1
\|
*	Start X11 and web frontends for xC	Přemysl Eric Janouch	2022-09-05	1	-0/+120
	For this, we needed a wire protocol. After surveying available options, it was decided to implement an XDR-like protocol code generator in portable AWK. It now has two backends, per each of: - xF, the X11 frontend, is in C, and is meant to be the primary user interface in the future. - xP, the web frontend, relies on a protocol proxy written in Go, and is meant for use on-the-go (no pun intended). They are very much work-in-progress proofs of concept right now, and the relay protocol is certain to change.