Bug 86390 - Kopete shouldn't show "status changes" on IRC chan joins
Summary: Kopete shouldn't show "status changes" on IRC chan joins
Status: CONFIRMED
Alias: None
Product: kopete
Classification: Applications
Component: IRC Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-01 17:57 UTC by Malte S. Stretz
Modified: 2021-03-09 22:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Malte S. Stretz 2004-08-01 17:57:29 UTC
Version:           0.8.922 (CVS >= 20040717) (using KDE 3.2.92 (3.3 beta2), Gentoo)
Compiler:          gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.7-gentoo-r10

To see what I mean, join a crowded channel like #gentoo-dev on freenode. The first thing you'll see are oodles of "Foo is now away" or "Foo os now Op".

Those are actually no status changes as the initial status is queried at that moment.
Comment 1 Jason Keirstead 2004-08-01 18:00:37 UTC
Yes. Status changes should be disabled for the first few seconds after a user has joined the KMM.

This code, however, needs to go into libkopete. There is no way for the IRC plugin to cause Kopete to not print these status changes.
Comment 2 Richard Smith 2004-08-03 01:23:06 UTC
I have a proposal which I'm calling 'onlineStatusFor' which I think would solve this, by making the contacts start with the right status, so no status change ever occurs. To me this makes sense, since no status change actually does occur. Another change which would help here would be for libkopete to not notify on changes from Unknown to non-Unknown.
Comment 3 Justin Zobel 2021-03-09 22:41:08 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.