Bug 30765

Summary: Add most-available-requested-presence
Product: Telepathy Reporter: Danielle Madeley <danielle>
Component: tp-glibAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: danielle
Version: git master   
Hardware: Other   
OS: All   
URL: http://git.collabora.co.uk/?p=user/danni/telepathy-glib.git;a=shortlog;h=refs/heads/most-available-requested-presence
Whiteboard:
i915 platform: i915 features:

Description Danielle Madeley 2010-10-11 01:21:04 UTC
Both as get_most_available_requested_presence() and most-available-requested-presence-changed.
Comment 2 Simon McVittie 2010-10-11 03:37:27 UTC
Is this just a workaround for the API proposed in Bug #24104 not having been finished/implemented yet?
Comment 3 Danielle Madeley 2010-10-11 17:25:27 UTC
(In reply to comment #2)
> Is this just a workaround for the API proposed in Bug #24104 not having been
> finished/implemented yet?

I don't think so.

It comes from https://bugzilla.gnome.org/show_bug.cgi?id=550502

When we call tp_account_manager_set_all_requested_presences(), we then let Empathy update to the most-available-presence, however this creates a confusing display issue when a given presence (i.e. hidden) is not available on all Connections. e.g. if the user has a Salut connection the most-available-presence is 'dnd'. The solution we've proposed is to check for any accounts that mismatch between the requested presence and the current presence, and display a warning to the user when this case arises.
Comment 4 GitLab Migration User 2019-12-03 20:04:07 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-glib/issues/44.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.