(In reply to comment #6)
> The normal way to list channels in a dedicated IRC client like irssi is with
> "/list PATTERN", which lists channels matching PATTERN (which is a shell-style
> glob, I think?).
Actually, this isn't how this works: LIST only supports specifying a single channel name, to get its number of occupants and topic (or an error if it doesn't exist).
Some, but not all, servers run an ‘alis’ bot that you can query with.
What we should do is what irssi does to selectively enable the “not a good idea” warning: send LUSERS to the server while connecting, and look at the RPL_LUSERCHANNELS message in the reply to see how many channels there are. If that number is over some threshold, don't offer RoomList channels.
Later we could add a way to query; that could be made selectively available by looking for a user called 'alis', maybe.
(In reply to comment #6)
> The normal way to list channels in a dedicated IRC client like irssi is with
> "/list PATTERN", which lists channels matching PATTERN (which is a shell-style
> glob, I think?).
Actually, this isn't how this works: LIST only supports specifying a single channel name, to get its number of occupants and topic (or an error if it doesn't exist).
Some, but not all, servers run an ‘alis’ bot that you can query with.
What we should do is what irssi does to selectively enable the “not a good idea” warning: send LUSERS to the server while connecting, and look at the RPL_LUSERCHANNELS message in the reply to see how many channels there are. If that number is over some threshold, don't offer RoomList channels.
Later we could add a way to query; that could be made selectively available by looking for a user called 'alis', maybe.