http2irc

688 KiB

Auteur	SHA1	Message	Date
JustAnotherArchivist	8f069ccac1	Catch config errors on reload	il y a 4 ans
JustAnotherArchivist	a888c9b9cb	Wait for connection registration before trying to join channels and send messages	il y a 4 ans
JustAnotherArchivist	86746f55a0	Handle prefixed messages from the server	il y a 4 ans
JustAnotherArchivist	03dfcf3e79	Add CertFP support	il y a 4 ans
JustAnotherArchivist	542cdb7140	Use plain text message payloads instead of JSON	il y a 4 ans
JustAnotherArchivist	abe75596c8	Fix usage string	il y a 4 ans
JustAnotherArchivist	8e5fbe765d	Confirm message delivery by periodic PINGs This assumes that a PONG response from the server means the connection is still intact. The messages could still have been dropped for weird reasons, but short of using a second client to confirm the delivery directly, there is no better option to test this. RFC 1459 actually specifies that "servers should not respond to PING commands". However, this recommendation has been removed in RFC 2812, and in practice, all common IRC servers seem to respond to PINGs.	il y a 4 ans
JustAnotherArchivist	e9a7780450	Refactor into more flexible tool supporting multiple endpoints and channels (nodeping2irc -> http2irc) with no-downtime config changes using a TOML config file and SIGUSR1 to reload and adapt accordingly	il y a 4 ans