| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Clean up logging |  JustAnotherArchivist | 2019-12-27 | 1 | -36/+48 |
| | | |||||
| * | Add a way to pass additional arguments into the module | JustAnotherArchivist | 2019-12-22 | 1 | -9/+23 |
| | | |||||
| * | Add support for transformation/translation modules that do arbitrary request ↵ | JustAnotherArchivist | 2019-12-22 | 1 | -7/+54 |
| | | | | | | | processing to generate the message Fixes #3 | ||||
| * | Support web server config changes | JustAnotherArchivist | 2019-12-19 | 1 | -8/+12 |
| | | |||||
| * | Make logging configurable through config file | JustAnotherArchivist | 2019-12-18 | 1 | -7/+32 |
| | | |||||
| * | Fix InvalidStateError in MessageQueue when the IRC server closes the connection | JustAnotherArchivist | 2019-12-16 | 1 | -2/+2 |
| | | |||||
| * | Get rid of the SimpleNamespace for configuration since it complicates config ↵ | JustAnotherArchivist | 2019-12-16 | 1 | -31/+20 |
| | | | | | | | change detection SimpleNamespace's documentation does not say anything about equality tests, which is why the update_config methods checked the relevant values using a tuple instead. But as more config values are added, this makes the comparisons unnecessarily long. A dict simplifies this. As a side-effect, the constraints of the maps keys being a valid identifier are no longer relevant either. | ||||
| * | Catch config errors on reload | JustAnotherArchivist | 2019-12-15 | 1 | -1/+5 |
| | | |||||
| * | Wait for connection registration before trying to join channels and send ↵ | JustAnotherArchivist | 2019-12-15 | 1 | -3/+5 |
| | | | | | messages | ||||
| * | Handle prefixed messages from the server | JustAnotherArchivist | 2019-12-15 | 1 | -0/+3 |
| | | |||||
| * | Add CertFP support | JustAnotherArchivist | 2019-12-15 | 1 | -3/+52 |
| | | |||||
| * | Use plain text message payloads instead of JSON | JustAnotherArchivist | 2019-12-02 | 1 | -13/+18 |
| | | |||||
| * | Fix usage string | JustAnotherArchivist | 2019-12-02 | 1 | -1/+1 |
| | | |||||
| * | 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 | 1 | -0/+375 |
| (nodeping2irc -> http2irc) with no-downtime config changes using a TOML config file and SIGUSR1 to reload and adapt accordingly | |||||
 |
index : ~klea/http2irc.git | |
| https://gitea.arpa.li/ArchiveTeam/http2irc copy for development |
| aboutsummaryrefslogtreecommitdiff |
path: root/http2irc.py