Context on lastdisconnect replication
Bug #402441 reported by
Jeremy Nickurak
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| CtrlProxy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
As it is, lastdisconnect replays text immediately following the disconnect, but nothing before. This replayed text can be difficult to recognize as part of a conversation without the previous lines. Ideally a small portion (10-15 lines, or 5-10 minutes?) of the text leading up to the disconnect should be included as well, to give the replayed text context, and provide continuity between sessions. It's also easy in the event of a client crash to miss messages that occur after a UI failure, but before the disconnect.
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in ctrlproxy: | |
| status: | In Progress → Triaged |
| Changed in ctrlproxy: | |
| assignee: | Jelmer Vernooij (jelmer) → nobody |
To post a comment you must log in.
delaying to 3.1