ubuntu-phone team mailing list archive

["Marco A. Harrendorf" <marcokarlo@xxxxxx>]

Hello Roberto,

thank you very much for this clarification!
-- 
Marco A. Harrendorf



Am Samstag, den 18.07.2015, 23:44 +0200 schrieb Roberto Mier Escandón :
> Hello Marco:
> 
> Canonical server receives the notification from Telegram and push it to
> the proper device. The information into the notification is the one that
> Telegram sends to Canonical, that is simply forwarded.
> In the case of regular chats, Telegram notifification comes with the
> message content, but that doesn't happen in the case of secret chats. In
> that specific case, any relevant information related with the content of
> the message, the conversation, the participants, any chat identifier,
> etc.. is not included in the push notification. You can do a simple
> test: watch the difference between a notification content for a message
> in a regular chat compared with another belonging to a secret chat.
> So, if you're concerned about privacy i suggest you use secret chats
> that encrypts conversations end to end, being only the peers involve in
> conversation the only ones that have access to the messages.
> 
> On 18/07/15 21:23, Marco A. Harrendorf wrote:
> > Dear all,
> > 
> > from the last correspondence in regards to Telegram and other clients my
> > understanding was that a new Telegram message is processed at a
> > Canonical server and then a notification is shown in the indicator panel
> > by making use of a telepathy service.
> > 
> > Does this mean that, even if I am using a private chat in Telegram,
> > Canonical could in principle read the messages since they messages
> > handled and delivered by their server?
> > 
> > I would appreciate if anybody could shine some light on handling
> > notifications and the use of an intermittent Canonical server for
> > delivering notifications.
> > 
> > Thanks,
> > 
> > Marco
> > 
> > 
> >

Attachment: signature.asc
Description: This is a digitally signed message part