| Summary: | We should remember if there is some unread message when user logs out | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | Daniele E. Domenichelli <ddomenichelli> |
| Component: | general | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | dvratil, heri+kde, kde, mklapetek |
| Priority: | NOR | Flags: | kde:
Decision-Required+
|
| Version: | git-latest | ||
| Target Milestone: | Future | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Daniele E. Domenichelli
2012-06-20 19:16:35 UTC
Any idea how? Do you know if these messages are ack'ed or not? I'm moving this to 0.5 milestone as the stable branch does not receive any new features. All agree we should. Still needs a good proposal on how. Please add plans to this post. My rough and highly idealistic proposal: The approver could list of channelId (that's accountId+contactId) and timestamps of first unread message on each channel. On shutdown the list would be stored somewhere and on start up the approver would just read the list, query logger for message count since the timestamp and display the "incoming conversation(s)" tray icon. The question is how to force ktp-text-ui to load specific message count. Normally ktp-text-ui connects to an existing channel and displays all messages in the channel, but after restart the channel does not exist so we could probably add a DBus method to ktp-text-ui to open channel with specified contact and load specified amount of messages from the logger. Alternate plan: We block logout if there are unread messages? Like Kate does for an unsaved file. Sounds like a good idea, but before allowing logout, we should also set all the accounts offline, or we still be subject to race conditions That breaks "restore presence on login" no? Probably. We should disable that as well! :D I dislike the idea of blocking logout. Instead I like the idea about loading messages from the logger. P.S: Alternatively you could store the unread messages separately and just display that file on next boot. does the logger store if a message was read or not? How does empathy handle this? @Danielle: Nope. And I don't think there's any concept of read or unread messages in Tp at all. There is in Telepathy, the handler has to "acknowledge" each user to say the user has seen it. If we don't do this and close the channel mission-control presents the channel again. I agree that TelepathyLoggerQt doesn't have it. Has this actually been a problem? Or is it purely a hypothetical one? I don't see it as much different to when we receive a message when we're offline . The question is what happens to a message waiting in to-be-approved channel when mission-control/channel dispatcher quits (ie. a restart). Is it stored locally and recreated after restart or refetched from server upon reconnecting (the case of being offline) or is it just lost (the server thinks it was delivered)? Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Dear user, unfortunately Telepathy is no longer maintained. Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat. |