Ubuntu

Gwibber should not allow notification merging

Reported by Conscious User on 2009-12-22
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gwibber
Low
Unassigned
gwibber (Ubuntu)
Low
Unassigned

Bug Description

Very often, people post a sequence of various posts in a short period of time, but not all posts are on the same subject. When merged, such posts become a confusing mess in the notification bubble. Bug #499323 makes the situation even worse.

I believe microblog posts are designed to be self-contained and totally disabling merging makes more sense.

Conscious User (conscioususer) wrote :

I originally reported this for the 2.0 version in Ubuntu Karmic,
but I just want to register that the issue still happens in current
trunk as Lucid release is approaching.

Conscious User (conscioususer) wrote :

This bug is still present as of Lucid Alpha 3.

Boniek (boniek12p) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in gwibber (Ubuntu):
status: New → Confirmed
Changed in gwibber (Ubuntu):
importance: Undecided → Low
Omer Akram (om26er) wrote :

is this still an issue in 2.32 ? i have not seen it I think

Changed in gwibber:
importance: Undecided → Low
status: New → Incomplete
Conscious User (conscioususer) wrote :

@Omer,

I cannot be 100% sure as I'm still using Lucid, but by peeking at

http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/annotate/head%3A/gwibber/microblog/util/__init__.py

I can see that the usage of the 'x-canonical-append' is still there (lines 170, 171).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers