Currently *watch uses it's own buffers meaning that the notifications are only sent when all clients are detached and one attaches. It doesn't send anything to second attaching client if one client is always connected.
I think it should use query buffers now that we have them and they are more intelligent or alternatively look at client ids and remember those.
I think that query buffers are preferable, but if it's not possible and the module cannot remember different cliend ids, I think it could do the same as e.g. chanfilter and clientbuffer and have commands for adding/removing client ids.
- From https://github.com/znc/znc/issues/965
Currently *watch uses it's own buffers meaning that the notifications are only sent when all clients are detached and one attaches. It doesn't send anything to second attaching client if one client is always connected.
I think it should use [query buffers](http://wiki.znc.in/Query_buffers) now that we have them and they are more intelligent or alternatively look at client ids and remember those.
I think that query buffers are preferable, but if it's not possible and the module cannot remember different cliend ids, I think it could do the same as e.g. [chanfilter](http://wiki.znc.in/Chanfilter) and [clientbuffer](http://wiki.znc.in/Clientbuffer) and have commands for adding/removing client ids.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23918212-watch-use-query-buffers-instead-of-own-implementation-send-messages-to-all-detached-clients-when-they-appear?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:93713055 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently *watch uses it's own buffers meaning that the notifications are only sent when all clients are detached and one attaches. It doesn't send anything to second attaching client if one client is always connected.
I think it should use query buffers now that we have them and they are more intelligent or alternatively look at client ids and remember those.
I think that query buffers are preferable, but if it's not possible and the module cannot remember different cliend ids, I think it could do the same as e.g. chanfilter and clientbuffer and have commands for adding/removing client ids.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.