Anope Support > 1.6.x (Read Only)

Anope Channel Mode Problem - Bug?

<< < (2/3) > >>

FiXato:
So the best way to solve this would be if it was handled by the IRCd?
That the IRCd would remember what the last modes were and handle them at the moment the IRCd tries to create the channel (but not yet actually creates it) for the user, and if the user doesn't match the requirements for the last modes (ie. not invited itself, not on a SSL connection or not using the channelkey), deny access as it normally would?

[Edited on 2006.2.16 by FiXato]

whoaboy:
Hrm, interesting.  The main reason I'm asking this question is because I'm considering switching to an IRCd that supports SSL connections (UnrealIRCd).  I've been using IRCu with SRVX services for about 2 years now and SRVX only really supports IRCu so I in turn must look for a new services package as well.

SRVX supports mode retention even while the channel is empty which is why I became used to this behavior.  I am no IRCd developer, but my best guess is that they are able to provide this functionality by having ChanServ join registered channels thus preventing a channel from ever becoming truly empty.

I'm not suggesting that SRVX is better, I'm just explaining how another services package handles this issue and why I would be asking about it.

FiXato:
so I take it that with srvx/ircu the registered channels are never empty and thus will always appear in a /list? (Which is not what most servers would want.. and which could be done with anope as well with inhabitregisteredchannels)

whoaboy:

--- Quote ---Originally posted by FiXato
so I take it that with srvx/ircu the registered channels are never empty and thus will always appear in a /list? (Which is not what most servers would want.. and which could be done with anope as well with inhabitregisteredchannels)
--- End quote ---
Yes, that's correct.  Due to ChanServ joining registered channels and preventing a channel from becoming empty, channel modes are preserved.  This does also allow for registered channels to appear in a /list even when empty of "real" users.  Athough I don't see any real negative impact as /list supports -min and -max command, so a simple "/list -min 2" would remove any channels with a single user in them.

I was unaware of a inhabitregisteredchannels command(?), and after searching for that in services and the conf file in Anope, I was unable to locate it.  Could you tell me where I could find this setting/command?

whoaboy:

--- Quote ---Originally posted by Rob
If services do attempt to handle this, and kick the user out of the channel, the channel becomes empty again, as such the modes are lost, and the user can re-join the channel - repeat this a few zillion times, like say someones script with autojoin, and you get the problem :/
--- End quote ---
Well, I was thinking more along the lines of the modes being in place at all times, thus preventing the user from even being able to go through the join/kick process in the first place.

Exactly like when a channel is set as +i (invite) and when an uninvited user attempts to join, they simply are denied access without ever joining the channel.

[Edited on 20-2-2006 by whoaboy]

Navigation

[0] Message Index

[#] Next page

[*] Previous page