Re: Channelling the CB

My opinion was (and still is), based on the fact that the number of "regulars" chatting in the CB is ever increasing, while the medium itself is just not scalable, given the loadtimes, server responsiveness etc.

I quite like the sound of your proposed solution, though I'm not sure how it would look in practice, multiple sections in the CB nodelet? How would it fit on Fullpage chat ? How would the XML look, multiple tickers? etc. pp.

But, it appears tye has seen a large flaw in the idea, so it seems that if anything happens at all, it will have to be an external solution. The problem there (IMO), is getting users to use it.. Attempting to add an interface to IRC (or some such) transparently via a nodelet would create just as much traffic as if a chat server were running on the site itself, if not more, so that is out.

To those who say "It's just for chatting, go post an SoPW", I say: A lot of the questions that pop up in the CB are not perl related, or even programming related sometimes.. do you really want to see these as SoPWs? People recognise that there are many fine minds within reach, that may know an answer to a particular niggly question, and will share therir knowledge willingly.

In conclusion, I don't really know how to solve this dilemma, since it seems all solutions so far have some sort of snag. :( Maybe someone should get the oft-proposed MUD version of PM off the ground... (Don't look at me, please, I'm booked up until after the summer or so.. :)

Update:
I also forgot to refute: Suggesting that people "just use /ignore" doesn't solve any problems, since *me* not seeing the chatters doesnt mean they don't see each other, and thus my (or whomever others) questions still get drowned out. Apart from that, all /ignore does is make for very odd-looking conversations..

Comment on Re: Channelling the CB

Replies are listed 'Best First'.
Re^2: Channelling the CB by g0n (Priest) on Apr 28, 2005 at 16:42 UTC
How about, for an interim/compromise solution, a degree of filtering? /ignore "monk" is too granular if you want to ignore a whole conversation, & /chatteroff isn't granular enough. You could filter by creating a drop down in the nodelet, containing threads . & A-F. Then when the code displays entries in the CB, it could do `if ($_=~/^$cgi->param('cbfilter')){print $_}`. In the form, you could prepend each utterance with the character currently set as the filter, then people could change their filter settings to filter themselves out. "." of course would be intended to match all of them (not sure if that regex would interpret the . as any character without trying it, but you get my drift). That way the filter would persist in the form, but reset (to ".") each time you come to the monastery. g0n, backpropagated monk	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Channelling the CB
by g0n (Priest) on Apr 28, 2005 at 16:42 UTC

You could filter by creating a drop down in the nodelet, containing threads . & A-F. Then when the code displays entries in the CB, it could do if ($_=~/^$cgi->param('cbfilter')){print $_}. In the form, you could prepend each utterance with the character currently set as the filter, then people could change their filter settings to filter themselves out. "." of course would be intended to match all of them (not sure if that regex would interpret the . as any character without trying it, but you get my drift).

That way the filter would persist in the form, but reset (to ".") each time you come to the monastery.

g0n, backpropagated monk

[reply]
[d/l]