Kyle Fuller

Something like the following would be a start at supporting the current behaviour alongside returning promises (or using async function as the hook): ```diff diff --git a/src/transaction-runner.js b/src/transaction-runner.js index cbdf1cc..b391165...

To link together these issues, I believe implementing this will depend on https://github.com/irssi/irssi/issues/912.

> Stuff that requires message-tags has the extra complexity of having to get that to the scripts api while not breaking compatibilty (can't just add an extra param). I have...

With echo-message you'll also get the message back as a success, and then also the 412 error. The message will get added to the buffer to be played back to...

I've tried to reproduce this by following steps outlined in description without success on ZNC 1.8.1. @wodim could you include a list of the loaded modules too? It might be...

I think this is a bit of a larger problem than just away, there's various states that a client may have which are not reset upon disconnect, or new connection....

Something along the lines of the following should do it. ```diff diff --git a/src/Client.cpp b/src/Client.cpp index 1fdb2aa4..ddb18016 100644 --- a/src/Client.cpp +++ b/src/Client.cpp @@ -716,6 +716,8 @@ void CClient::HandleCap(const CMessage& Message)...

On point 3, I'm slightly concerned with size limits for push payloads where duplicating information will half the total capacity for each notification. For Palaver we have less than 4KB...

One other point to add in regards to Atheme compatibility, is that the `founder` of a channel may be set to a group (in which the migration script will raise...

In terms of the prior art in Palaver's push spec, here's the things I'd consider could do with re-thinking: 1. Ignore nicks should become hostmasks (`*!*@test.com`). These should match and...