Since version 1.0 of ZNC local channels (channels beginning with &) are not displayed in the clients. Also, joining an &-channel always adds a new one to the znc config. With each join command an additional &-channel entry appears in the Web-UI of the used account. This is not an issue with the IRC server since it works perfectly without ZNC.
Since version 1.0 of ZNC local channels (channels beginning with &) are not displayed in the clients. Also, joining an &-channel always adds a new one to the znc config. With each join command an additional &-channel entry appears in the Web-UI of the used account. This is not an issue with the IRC server since it works perfectly without ZNC.
<!-- github-sync-id:9667210 -->
Since version 1.0 of ZNC local channels (channels beginning with &)
are not displayed in the clients.
Works for me on efnet. I did /join &test
Also, joining an &-channel always adds a new one to the znc config.
With each join command an additional &-channel entry appears in the
Web-UI of the used account.
How is it wrong? Why they should not be listed there?
04.01.2013 14:47, James Kirwill пишет:
> Since version 1.0 of ZNC local channels (channels beginning with &)
> are not displayed in the clients.
Works for me on efnet. I did /join &test
> Also, joining an &-channel always adds a new one to the znc config.
> With each join command an additional &-channel entry appears in the
> Web-UI of the used account.
How is it wrong? Why they should not be listed there?
<!-- github-comment-id:11875827 -->
They should be there, but only once! Each join command adds additional channel there with the same name. But the channel is still not displayed in the client. So users try to join again and again and then there are twenty &foobar in znc channels but none of them works.
They should be there, but only once! Each join command adds _additional_ channel there with the same name. But the channel is still not displayed in the client. So users try to join again and again and then there are twenty &foobar in znc channels but none of them works.
<!-- github-comment-id:11894379 -->
If I delete all &admins channels i the Web UI, joining works on the first connect to znc. But then on the second connect another &admins entry is created and the channel never shows up in the client.
Global modules:
+----------------+-----------+
| Name | Arguments |
+----------------+-----------+
| partyline | |
| webadmin | |
| lastseen | |
| modperl | |
| notify_connect | |
+----------------+-----------+
User modules:
+------------------+-----------+
| Name | Arguments |
+------------------+-----------+
| controlpanel | |
| autoattach | |
| autocycle | |
| autoreply | |
| chansaver | |
| clearbufferonmsg | |
| clientnotify | |
| listsockets | |
| notes | |
| perform | |
+------------------+-----------+
Network modules:
+---------------+-----------+
| Name | Arguments |
+---------------+-----------+
| autoop | |
| autovoice | |
| keepnick | |
| kickrejoin | |
| route_replies | |
+---------------+-----------+
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
| Name | Status | Conf | Buf | Modes | Users | ~ | & | @ | % | + |
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
| &admins | Trying | yes | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
If I delete all &admins channels i the Web UI, joining works on the first connect to znc. But then on the second connect another &admins entry is created and the channel never shows up in the client.
<!-- github-comment-id:11911771 -->
Uhm, I meant hostname...
I can try to setup ngircd 20 locally, but I still can't reproduce it myself. Also it may depend on settings of that exact server.
For now I can only say that multiple lines of the same channel sure look wrong.
Live server where I can reproduce it will help.
Uhm, I meant hostname...
I can try to setup ngircd 20 locally, but I still can't reproduce it myself. Also it may depend on settings of that exact server.
For now I can only say that multiple lines of the same channel sure look wrong.
Live server where I can reproduce it will help.
<!-- github-comment-id:11914230 -->
@DarthGandalf Thanks for reply. The hostname is irc.w3.org:6665. I'm not sure this issue is caused by ZNC or ngIRCd but thank you so much for helping!!
@DarthGandalf Thanks for reply. The hostname is irc.w3.org:6665. I'm not sure this issue is caused by ZNC or ngIRCd but thank you so much for helping!!
<!-- github-comment-id:13111563 -->
@DarthGandalf Hi sorry for pinging you but this issue still occurs on latest git build. Could you please check if what is wrong?
@DarthGandalf Hi sorry for pinging you but this issue still occurs on latest git build. Could you please check if what is wrong?
<!-- github-comment-id:18849229 -->
So, PREFIX=(qaohv)&@%+ CHANTYPES=#&+ on that network.
& is a mode prefix for "admin" there.
There is a special syntax PRIVMSG @#chan :hello which sends the message to all ops of the channel. And there is some code in ZNC which removes prefixes from channel names to make that syntax work (otherwise the channel @#chan isn't found in ZNC's list of chans).
Current situation of multiple &admins is wrong for sure (on ZNC side). Intersecting PREFIX and CHANTYPES aren't very good either (on IRCd).
So, PREFIX=(qaohv)~&@%+ CHANTYPES=#&+~ on that network.
& is a mode prefix for "admin" there.
There is a special syntax `PRIVMSG @#chan :hello` which sends the message to all ops of the channel. And there is some code in ZNC which removes prefixes from channel names to make that syntax work (otherwise the channel @#chan isn't found in ZNC's list of chans).
Current situation of multiple &admins is wrong for sure (on ZNC side). Intersecting PREFIX and CHANTYPES aren't very good either (on IRCd).
<!-- github-comment-id:18933800 -->
Ok, as @grawity pointed out, this is bug on ZNC side only, we should use STATUSMSG from 005: https://tools.ietf.org/html/draft-brocklesby-irc-isupport-03#section-3.16
<!-- github-comment-id:22980001 -->
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.
Since version 1.0 of ZNC local channels (channels beginning with &) are not displayed in the clients. Also, joining an &-channel always adds a new one to the znc config. With each join command an additional &-channel entry appears in the Web-UI of the used account. This is not an issue with the IRC server since it works perfectly without ZNC.
04.01.2013 14:47, James Kirwill пишет:
Works for me on efnet. I did /join &test
How is it wrong? Why they should not be listed there?
They should be there, but only once! Each join command adds additional channel there with the same name. But the channel is still not displayed in the client. So users try to join again and again and then there are twenty &foobar in znc channels but none of them works.
Show output of /znc listchans
And of /znc listmods
Global modules:
+----------------+-----------+
| Name | Arguments |
+----------------+-----------+
| partyline | |
| webadmin | |
| lastseen | |
| modperl | |
| notify_connect | |
+----------------+-----------+
User modules:
+------------------+-----------+
| Name | Arguments |
+------------------+-----------+
| controlpanel | |
| autoattach | |
| autocycle | |
| autoreply | |
| chansaver | |
| clearbufferonmsg | |
| clientnotify | |
| listsockets | |
| notes | |
| perform | |
+------------------+-----------+
Network modules:
+---------------+-----------+
| Name | Arguments |
+---------------+-----------+
| autoop | |
| autovoice | |
| keepnick | |
| kickrejoin | |
| route_replies | |
+---------------+-----------+
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
| Name | Status | Conf | Buf | Modes | Users | ~ | & | @ | % | + |
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
| &admins | Trying | yes | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
| &admins | Trying | | 16384 | | 0 | 0 | 0 | 0 | 0 | 0 |
+---------+--------+------+-------+------------------+-------+---+---+---+---+----+
If I delete all &admins channels i the Web UI, joining works on the first connect to znc. But then on the second connect another &admins entry is created and the channel never shows up in the client.
What IRC server is that?
ngircd 20
Uhm, I meant hostname...
I can try to setup ngircd 20 locally, but I still can't reproduce it myself. Also it may depend on settings of that exact server.
For now I can only say that multiple lines of the same channel sure look wrong.
Live server where I can reproduce it will help.
I'm also having this issue with ngIRCd 20.1.
@nunnun and can you tell the hostname as I asked before?
@DarthGandalf Thanks for reply. The hostname is irc.w3.org:6665. I'm not sure this issue is caused by ZNC or ngIRCd but thank you so much for helping!!
@DarthGandalf Hi sorry for pinging you but this issue still occurs on latest git build. Could you please check if what is wrong?
So, PREFIX=(qaohv)
&@%+ CHANTYPES=#&+on that network.& is a mode prefix for "admin" there.
There is a special syntax
PRIVMSG @#chan :hellowhich sends the message to all ops of the channel. And there is some code in ZNC which removes prefixes from channel names to make that syntax work (otherwise the channel @#chan isn't found in ZNC's list of chans).Current situation of multiple &admins is wrong for sure (on ZNC side). Intersecting PREFIX and CHANTYPES aren't very good either (on IRCd).
Ok, as @grawity pointed out, this is bug on ZNC side only, we should use STATUSMSG from 005: https://tools.ietf.org/html/draft-brocklesby-irc-isupport-03#section-3.16