summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorLuke Bratch <luke@bratch.co.uk>2019-09-07 12:43:04 +0100
committerLuke Bratch <luke@bratch.co.uk>2019-09-07 12:43:04 +0100
commite4d1706031540ae74ff104c44adeb735ee0bfcf4 (patch)
tree46e12bb133f0810bf9f535ad8f34a7415746c31f /TODO
parent38bd2b2761b7d0f556945ffad78f73536e12e157 (diff)
Add a configuration option to include the date in the timestamp when replaying the replay log.
Diffstat (limited to 'TODO')
-rw-r--r--TODO4
1 files changed, 2 insertions, 2 deletions
diff --git a/TODO b/TODO
index 4e76790..0714ace 100644
--- a/TODO
+++ b/TODO
@@ -4,8 +4,6 @@ Support arrays or similar in the configuration file (for nick(s), connectcommand
All the TODOs sprinkled throughout the code!
-Option to include date in replay log replay.
-
(I think) replay log can cause non-existent user to appear in channel (e.g. ~19:00 on 12/08/2019 for me)
Do server operator messages and commands work?
@@ -13,3 +11,5 @@ Do server operator messages and commands work?
(I vaguely recall) some unwanted stuff (channel ban info?) was relayed to another client upon a client connecting.
PM replay chat in a channel (or perhaps a random channel?) e.g. replay on 06/09/2019 at 17:05 from 13:49 in #insomnia - maybe a client thing.
+
+Ensure replayed lines don't exceed IRC message maximum length due to inserted time/datestamp.