Hi,
It'd be awesome if it was possible to get highlight notifications across networks.
E.g. I have my ZNC set up to connect to 5 networks and I'm only connected to my ZNC network A.
Then someone on network B could highlight me and I'd get a notification on my client that only is connected to network A, so I can know there's something going on and I can connect to network B.
Hi,
It'd be awesome if it was possible to get highlight notifications across networks.
E.g. I have my ZNC set up to connect to 5 networks and I'm only connected to my ZNC network A.
Then someone on network B could highlight me and I'd get a notification on my client that only is connected to network A, so I can know there's something going on and I can connect to network B.
## <bountysource-plugin>
There is a **[$5 open bounty](https://www.bountysource.com/issues/1442867-add-cross-network-support-to-the-watch-module?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:29745793 -->
This would be very helpful and this would probably mean user level module which would also help a lot.
It seems like I am just putting exact same config to all network instances or forgetting it and wondering why they don't work and returning to those sometime long time later.
The example would also help as my ZNC is on 8 networks and with phone I am on 4 (both numbers include BitlBee) and it's not entirely impossible that someone says something on some other network that I should be aware of or reply to.
This would be very helpful and this would probably mean user level module which would also help a lot.
It seems like I am just putting exact same config to all network instances or forgetting it and wondering why they don't work and returning to those sometime long time later.
The example would also help as my ZNC is on 8 networks and with phone I am on 4 (both numbers include BitlBee) and it's not entirely impossible that someone says something on some other network that I should be aware of or reply to.
<!-- github-comment-id:79287819 -->
What is currently the best way to handle the following situation?
Two clients: WeeChat & Communi Sailfish
Communi Sailfish doesn't support highlighting on anything else than nick
8 networks
Having alert for alternative nicks and specific words like !ops in addition to %nick% on specific channels?
I think this issue/user level *watch would make it easier and I think currently I would be forced to write rules to some text file and copy-paste it to all networks or to /allserv.
What is currently the best way to handle the following situation?
- Two clients: WeeChat & Communi Sailfish
- Communi Sailfish doesn't support highlighting on anything else than nick
- 8 networks
- Having alert for alternative nicks and specific words like `!ops` in addition to _%nick%_ on specific channels?
I think this issue/user level *watch would make it easier and I think currently I would be forced to write rules to some text file and copy-paste it to all networks or to /allserv.
https://github.com/znc/znc/issues/965 would also be very helpful when phone is offline.
<!-- github-comment-id:116208061 -->
The only potential issue I see is having all watch notifications on all networks, but I wouldn't mind that so much, notify_connect has the same issue and I don't have problems with it either.
Looking from user side it wouldn't need small changes
```
2015-09-17 13:17:43+0300 < *highlight> -Euforia:#channel- Mikaela: blah!
2015-09-17 13:18:02+0300 < *highlight> <Euforia:#channel> Mikaela: blah!
```
would become
```
2015-09-17 13:17:43+0300 < *highlight> -freenode:Euforia:#channel- Mikaela: blah!
2015-09-17 13:18:02+0300 < *highlight> <freenode:Euforia:#channel> Mikaela: blah!
```
The only potential issue I see is having all watch notifications on all networks, but I wouldn't mind that so much, notify_connect has the same issue and I don't have problems with it either.
<!-- github-comment-id:141037231 -->
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.
Hi,
It'd be awesome if it was possible to get highlight notifications across networks.
E.g. I have my ZNC set up to connect to 5 networks and I'm only connected to my ZNC network A.
Then someone on network B could highlight me and I'd get a notification on my client that only is connected to network A, so I can know there's something going on and I can connect to network B.
There is a $5 open bounty on this issue. Add to the bounty at Bountysource.
This would be very helpful and this would probably mean user level module which would also help a lot.
It seems like I am just putting exact same config to all network instances or forgetting it and wondering why they don't work and returning to those sometime long time later.
The example would also help as my ZNC is on 8 networks and with phone I am on 4 (both numbers include BitlBee) and it's not entirely impossible that someone says something on some other network that I should be aware of or reply to.
What is currently the best way to handle the following situation?
!opsin addition to %nick% on specific channels?I think this issue/user level *watch would make it easier and I think currently I would be forced to write rules to some text file and copy-paste it to all networks or to /allserv.
https://github.com/znc/znc/issues/965 would also be very helpful when phone is offline.
This comment might be useless, but possibly shows the issue more clearly.
dumps
chatspike
dereferenced
freenode
oftc
pirateirc
the first rule as you might see is in all networks with
/allserv, but the optimal case would beas those channels exist only in one network or I am not in the other networks I wouldn't have to do so much work in all networks.
Looking from user side it wouldn't need small changes
would become
The only potential issue I see is having all watch notifications on all networks, but I wouldn't mind that so much, notify_connect has the same issue and I don't have problems with it either.