Bug 37298

Summary:	Add a flag in Message_Key for message sent form another terminal
Product:	Telepathy	Reporter:	Nicolas Dufresne <nicolas>
Component:	tp-spec	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Nicolas Dufresne 2011-05-17 15:12:30 UTC

On some protocols, like Skype, when messages are sent from another protocol, the messages are also sent to all other connected terminals. This allow keeping all the computers/phone/tablet on sync in a way you can switch from one to another and not loose the context.

On the N900 those messages are simply sent as new messages with the annoying side effect that the phone notify you of a new message, while in fact it is you that sent the message from you computer.

What I'm proposing is to add a flag to Message_Key headers that would serve this purpose. I have two options in mind.

1) A very specific flag similar to "echoed", that would applied for the type of message described before
2) Or a more generic one like "no-notify", that can be used for any new messages that do not really require user attention.

Comment 1 Simon McVittie 2011-05-18 01:52:30 UTC

It's not at all clear to me that these should be represented as a message being received at all? Why aren't they just signalled as a message being sent?

(One possible answer would be "sent messages on a new channel aren't state-recoverable". I think maybe that's the real bug...)

Comment 2 Nicolas Dufresne 2011-05-18 11:32:55 UTC

(In reply to comment #1)
> It's not at all clear to me that these should be represented as a message being
> received at all? Why aren't they just signalled as a message being sent?

What that mean "signalled as a message being sent" in Telepathy point of you ? This is not at all covered by the spec. Also, having delivery report for message that actually never been sent is hard to handle.

> 
> (One possible answer would be "sent messages on a new channel aren't
> state-recoverable". I think maybe that's the real bug...)

What that mean ? Can you elaborate ?

Comment 3 GitLab Migration User 2019-12-03 20:24:16 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-spec/issues/116.

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.