Open justinsteven opened 10 years ago
Seems reasonable to me! behind the scenes it might not even be in that format (because that could be user-specific) so it could just mean that a subset of a message, that comes in JSON format, should be decrypted.
When reconnecting to a bouncer, it may spit back "playback" that was missed while disconnected from the bouncer. This playback might be prefixed by a timestamp, and will appear to come from the name of the person who sent the message.
For example, some redacted timestamped playback received and shown by irssi upon reconnecting to bouncer:
= 17:33:41 < alice> [06:50:24] {"h":"HASH","a":"DATA","s":"SALT"}
That is:
= irssi-timestamp < sender-name> [bouncer-timestamp] {aescrypt json}
I propose that this json should be decrypted as usual.