It would be a useful feature to support an option to set a maximum number of times for buffers to be replayed before they are considered probably seen and cleared. For example, I host a ZNC instance for someone who moves around a lot on a laptop, and so sometimes repeatedly receives replayed PMs as I have set it to use clearpmbufferonmsg due to messages sometimes otherwise getting lost due to poor-quality connections; I have explained why this is preferable to their previous situation of messages sometimes getting silently dropped, but they suggested this to me and I could not find a way to do it myself on 1.6.
It would be a useful feature to support an option to set a maximum number of times for buffers to be replayed before they are considered probably seen and cleared. For example, I host a ZNC instance for someone who moves around a lot on a laptop, and so sometimes repeatedly receives replayed PMs as I have set it to use clearpmbufferonmsg due to messages sometimes otherwise getting lost due to poor-quality connections; I have explained why this is preferable to their previous situation of messages sometimes getting silently dropped, but they suggested this to me and I could not find a way to do it myself on 1.6.
<!-- github-sync-id:201909519 -->
add an option to not send the buffer upon connection, but still keep it
"Number of times to send" looks like yet another workaround, which doesn't solve the problem fully, but adds more complexity anyway
The proper fix would be:
1. support https://github.com/ircv3/ircv3-specifications/pull/292 on both ZNC and client
2. add an option to not send the buffer upon connection, but still keep it
"Number of times to send" looks like yet another workaround, which doesn't solve the problem fully, but adds more complexity anyway
<!-- github-comment-id:275879691 -->
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.
It would be a useful feature to support an option to set a maximum number of times for buffers to be replayed before they are considered probably seen and cleared. For example, I host a ZNC instance for someone who moves around a lot on a laptop, and so sometimes repeatedly receives replayed PMs as I have set it to use clearpmbufferonmsg due to messages sometimes otherwise getting lost due to poor-quality connections; I have explained why this is preferable to their previous situation of messages sometimes getting silently dropped, but they suggested this to me and I could not find a way to do it myself on 1.6.
The proper fix would be:
"Number of times to send" looks like yet another workaround, which doesn't solve the problem fully, but adds more complexity anyway