Open Bug 252848 Opened 15 years ago Updated 4 years ago

feature to suppress or route joins, leaves, kills, etc in Chatzilla (message filtering)

Categories

(Other Applications :: ChatZilla, enhancement)

enhancement
Not set

Tracking

(Not tracked)

People

(Reporter: madodel, Unassigned)

References

(Blocks 4 open bugs)

Details

Attachments

(1 file, 2 obsolete files)

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a2) Gecko/20040719
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a2) Gecko/20040719

I'd like to see the ability in Chatzilla to suppress specific message types, or
route them to a specific tab.  For example Join, Leave and Nick change messages
should be able to be suppressed.   IRCops Wallops might be routed to the server
tab, rather then the current window. I asked on #Chatzilla and was told there
was no preference setting for this and no easy way to do this if at all, at present.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: OS/2 → All
Hardware: PC → All
Product: Core → Other Applications
I will be trying my hand on this for a few weeks (hopefully it won't take
longer, but well...).

My current idea is to use an interface similar to mailnews message filtering,
and allow to copy/move/remove messages back and forth, but I was thinking it
might also be nice to allow specific things to flash the window, make a sound,
or replace words in the message (if the message contains word X, censor that
word to **** or something, similar to bug 119173)

Storage of these rules would use the js object serialiser James Ross wrote. I'm
marking depends only for that bug, but I think the following bugs may be solved
entirely or at least profit from work on this bug:
bug 119173
bug 91447 (not at all sure, it looks like not much code went in for this anyway)
bug 252300
bug 294404
Status: NEW → ASSIGNED
Depends on: 296702
Summary: [ENH] feature to suppress or route selected messages in Chatzilla. (Joins, Leaves, Kills, etc) → feature to suppress or route selected messages in Chatzilla. (Joins, Leaves, Kills, etc)
I was fairly sure I actually took the bug the first time I touched it.
Apparently not. Sorry for bugspam.
Assignee: rginda → gijskruitbosch
Status: ASSIGNED → NEW
Blocks: 297293
Blocks: 297292
*** Bug 294404 has been marked as a duplicate of this bug. ***
Blocks: 302425
Blocks: 285270
Blocks: chatzilla1.0
I got a personal email from Eyal asking if there had been any progress. I regret to say that the answer is mostly 'no', but on the plus side, I'm determined to start work on this after January 6th. Also, we now have a text serializer, so storing all this information is more straightforward then it would have been when this bug was filed, so that should certainly help.

Lastly, there was/is some discussion about what to support and what not to support, and various other arguments about how the architecture should work, on http://wiki.mozilla.org/ChatZilla:Message_Filter
I could swear I'd seen progress on this somewhere, but I must have dreamt it. :)

Can anything useful that can be borrowed from mailnews filters?
You had probably seen stuff on the wiki. I've been busy with lots of other stuff for some time, but there's a deadline now, or rather, there's supposed to be a deadline. Which is 4 weeks from now, on the release console.

Mailnews is no use because it implements filters in compiled code, so there is nothing to borrow really. Maybe, just maybe, I can reuse some filter manager XUL, but even that would probably take me just as long to write myself, instead of screwing with their implementation.
See also:
http://lxr.mozilla.org/seamonkey/source/mailnews/base/search/public/
http://lxr.mozilla.org/seamonkey/source/mailnews/base/search/resources/content/

On the other hand, I've been growing increasingly sceptical over the performance hit this is going to cause, but I guess we need to look at things one step at a time...
Oops. Make that 3 weeks just to be clear. Apologies for all the bugspam.
(In reply to comment #6)
> I could swear I'd seen progress on this somewhere, but I must have dreamt it.

ah, I was thinking of Bug 321837 (which indeed would be nice to have on branches)


(In reply to comment #7)
> You had probably seen stuff on the wiki. I've been busy with lots of other
> stuff for some time, but there's a deadline now, or rather, there's supposed to
> be a deadline. Which is 4 weeks from now, on the release console.

deadline?

Blocks: 119173
So, since there was this idea that I wasn't doing anything, I guess it might be nice to show what I have right now. It's far from complete, and some of it is really temporary hackery that needs to be fixed to happen properly, but this should give some ideas. As for the weird brace matching making the last bit of the patch hard to read, you'll have to blame diff I'm afraid (or tell me the magic option to make it do it better).
Summary: feature to suppress or route selected messages in Chatzilla. (Joins, Leaves, Kills, etc) → feature to suppress or route joins, leaves, kills, etc in Chatzilla (message filtering)
Attached patch [not for checkin] updated patch (obsolete) — Splinter Review
People kept editing __display, so the old patch bitrotted quite a lot. This one should apply cleanly again. Still not done yet, though. Maybe (hopefully) I'll have time in the Christmas holidays.
Attachment #220416 - Attachment is obsolete: true
Depends on: 361914
Blocks: cz-a11y
Still need to doublecheck sounds, check for random edge cases I forgot about, and poke saving/loading - oh, and no UI yet. But other than that, as far as I can tell this is at least a usable patch.
Attachment #248463 - Attachment is obsolete: true
Blocks: 420851
No longer blocks: 297292
QA Contact: samuel → chatzilla
"conference mode" can do this
(In reply to comment #13)
> "conference mode" can do this

Conference mode is not as configurable as this.
I apologise for reviving this old bug.
Realistically, I'm not working on this.

A more sensible path forward might be to fix the deps with individual preferences. :-\
Assignee: gijskruitbosch+bugs → nobody
You need to log in before you can comment on or make changes to this bug.