~steering/bitbot.git/modules/ircv3_labeled_responses.py, branch master Unnamed repository; edit this file 'description' to name the repository. https://cgit.space/~steering/bitbot.git/atom/modules/ircv3_labeled_responses.py?h=master 2019-12-10T05:27:35Z move core modules to src/core_modules, make them uneffected by white/black list 2019-12-10T05:27:35Z jesopo 2019-12-10T05:27:35Z urn:sha1:638eee0d685c06d258cb55287204ca97bca7c344 change labeled-response WARN logging to DEBUG - it's mostly unimportant 2019-11-04T10:17:47Z jesopo 2019-11-04T10:17:47Z urn:sha1:754269576ae257d4ffb2efe143b43d8114780a44 make labeled-response depend on batch 2019-06-23T08:44:59Z jesopo 2019-06-23T08:44:59Z urn:sha1:59432a4815666f84d653d5c32d8389eb0b193480 set echo-message response ID to the ID of the original message 2019-06-21T17:22:36Z jesopo 2019-06-21T17:22:36Z urn:sha1:81ca751d964411093bce8b13a149aaea60458bf3 Adda system of aliases for CAPs, mostly for changeable draft specs and creating 2019-06-21T16:15:46Z jesopo 2019-06-21T16:15:46Z urn:sha1:8a0d99f9699b3cb27908fee0e485faf028d3e6fe dependence between moving specs Show which server a label warning is for 2019-06-21T10:11:21Z jesopo 2019-06-21T10:11:21Z urn:sha1:4690f3f45dc820ddf6b4b5a2d2466514f7da71d9 Add an export for IRCv3 CAPs 2019-06-20T15:52:23Z jesopo 2019-06-20T15:52:23Z urn:sha1:24cdff9e44c8afdbb6a1289b8da451ec1d0ba9af Return all caps through received.cap.ls|new and check if valid in line_handler, 2019-06-16T14:33:20Z jesopo 2019-06-16T14:33:20Z urn:sha1:5fa3d66a39dc22bff9a1d0345ebb70448b060e82 remove server.cap_started WARN log (instead of exception) when we receive an unknown label 2019-06-12T14:36:59Z jesopo 2019-06-12T14:36:59Z urn:sha1:7324a05d3e12fffb4aaa00a8331651e5b9c85be0 WARN when we see 10 labeled-responses while waiting for a response to a line 2019-06-05T11:11:14Z jesopo 2019-06-05T11:11:14Z urn:sha1:8a536c3ac523f5b67527fce8f0fb5d159aa5a80b