Bug 360924 - Join events are hidden even with "nick active within last..."
Summary: Join events are hidden even with "nick active within last..."
Status: CONFIRMED
Alias: None
Product: konversation
Classification: Applications
Component: ircview (show other bugs)
Version: 1.6
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: argonel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-23 22:48 UTC by Oleh Prypin
Modified: 2020-11-21 06:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleh Prypin 2016-03-23 22:48:01 UTC
When the settings "Hide Join/Part/Nick events" "Except for watched nicks active within the last day" are enabled, Join events are never shown, while the other two kinds of events are shown correctly for recently active users.

This is especially bad and misleading when someone is doing a quick reconnect: you only see them leave and think they are gone.

Reproducible: Always

Steps to Reproduce:
This requires an interaction of two IRC clients/users. They will be shown as [A] and [B].
[A]:
1. Join any IRC channel in Konversation
2. Go to Configure -> Behavior -> Chat Window
2.1. Check "Hide Join/Part/Nick events"
2.2. Check "Except for watched nicks active within the"
[B]:
3. Join the same IRC channel
4. Send any message
5. Leave the channel ([A] sees the Part notification)
6. Join the same IRC channel ([A] doesn't see the Join notification, which is the problem)



Actual Results:  
Join events are never shown when "Hide Join/Part/Nick events" is active. Only Part and Nick events are shown when "Except for watched nicks active within the" is active.

Expected Results:  
Join events for recently active nicknames should be shown with "Hide Join/Part/Nick events" "Except for watched nicks active within the..." active

This happens because all information about a nickname's last activity is deleted when it leaves. I tried to fix this but there doesn't seem to be a nice and simple solution. The objects that store this information really need to be deleted.
Comment 1 Justin Zobel 2020-11-21 06:59:12 UTC
Confirmed this is still an issue on 1.7.7.