| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fix usage string |  JustAnotherArchivist | 2019-12-02 | 1 | -1/+1 |
| | | |||||
| * | Add example config file | JustAnotherArchivist | 2019-12-02 | 1 | -0/+21 |
| | | |||||
| * | Confirm message delivery by periodic PINGs | JustAnotherArchivist | 2019-12-02 | 1 | -3/+29 |
| | | | | | | | 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. | ||||
| * | Refactor into more flexible tool supporting multiple endpoints and channels ↵ | JustAnotherArchivist | 2019-12-02 | 2 | -246/+375 |
| | | | | | (nodeping2irc -> http2irc) with no-downtime config changes using a TOML config file and SIGUSR1 to reload and adapt accordingly | ||||
| * | Move hardcoded data to command-line arguments | JustAnotherArchivist | 2019-10-05 | 1 | -14/+43 |
| | | |||||
| * | Cleanup | JustAnotherArchivist | 2019-10-04 | 1 | -11/+4 |
| | | |||||
| * | Add fake IRC server for testing/dev | JustAnotherArchivist | 2019-10-04 | 1 | -0/+50 |
| | | |||||
| * | Replace message queue with own implementations that permits putting messages ↵ | JustAnotherArchivist | 2019-10-04 | 1 | -3/+85 |
| | | | | | back on the queue | ||||
| * | Initial commit | JustAnotherArchivist | 2019-10-04 | 1 | -0/+135 |
 |
index : ~klea/http2irc.git | |
| https://gitea.arpa.li/ArchiveTeam/http2irc copy for development |
| aboutsummaryrefslogtreecommitdiff |