For users with a number of high-traffic channels it might make sense to have all the channels attached on desktop, but keep the list to bare minimum on mobile devices (possibly using with plugins that reattach on activity). That will allow more effective mode of operations on mobile clients due to much lower traffic.
For users with a number of high-traffic channels it might make sense to have all the channels attached on desktop, but keep the list to bare minimum on mobile devices (possibly using with plugins that reattach on activity). That will allow more effective mode of operations on mobile clients due to much lower traffic.
<!-- github-sync-id:56696924 -->
Alternatively, you can setup several per-client users, as described at http://wiki.znc.in/FAQ#How_to_store_private_messages_even_when_user_is_attached.2C_so_other_clients_can_see_them.3F
<!-- github-comment-id:73115589 -->
If you do this, you should be aware of https://github.com/znc/znc/issues/839 which means that you will stll see added timestamps if your client supports server-time and if it doesn't support that, you will see timestamps twice in buffer playback.
> Alternatively, you can setup several per-client users, as described at http://wiki.znc.in/FAQ#How_to_store_private_messages_even_when_user_is_attached.2C_so_other_clients_can_see_them.3F
If you do this, you should be aware of https://github.com/znc/znc/issues/839 which means that you will stll see added timestamps if your client supports server-time and if it doesn't support that, you will see timestamps twice in buffer playback.
<!-- github-comment-id:73180716 -->
@Mikaela why? Client users are always connected to the main user, so main user doesn't need to have any buffer itself, it just redirects all messages to client users, so it doesn't have much chance to add timestamps into message text. Also if you still afraid of getting second timestamp, you can always set both PrependTimestamp and AppendTimestamp to false.
@Mikaela why? Client users are always connected to the main user, so main user doesn't need to have any buffer itself, it just redirects all messages to client users, so it doesn't have much chance to add timestamps into message text. Also if you still afraid of getting second timestamp, you can always set both `PrependTimestamp` and `AppendTimestamp` to `false`.
<!-- github-comment-id:73197894 -->
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.
For users with a number of high-traffic channels it might make sense to have all the channels attached on desktop, but keep the list to bare minimum on mobile devices (possibly using with plugins that reattach on activity). That will allow more effective mode of operations on mobile clients due to much lower traffic.
There's a module for that: http://wiki.znc.in/Chanfilter (requires znc 1.6)
Alternatively, you can setup several per-client users, as described at http://wiki.znc.in/FAQ#How_to_store_private_messages_even_when_user_is_attached.2C_so_other_clients_can_see_them.3F
If you do this, you should be aware of https://github.com/znc/znc/issues/839 which means that you will stll see added timestamps if your client supports server-time and if it doesn't support that, you will see timestamps twice in buffer playback.
@Mikaela why? Client users are always connected to the main user, so main user doesn't need to have any buffer itself, it just redirects all messages to client users, so it doesn't have much chance to add timestamps into message text. Also if you still afraid of getting second timestamp, you can always set both
PrependTimestampandAppendTimestamptofalse.I think this was discussed at freenode on #znc some time ago.