North Carolina, United States
Graduate DevOps Software Engineer at Inmar Intelligence
~whereswaldon, I've been thinking about the best way to remove the nodes from old status messages and it occurred to me: should we modify the relay to not transmit expired messages? Consider a user being online for an hour, accumulating a number of status messages in the forest. At any point in time, only one node in the set should have any meaning; it's of no use to transmit messages that are not relevant, right? This solves only part of the problem; when expired nodes are evicted client-side, they don't get infinitely re-sent to the client as they'll have already expired.
We will still need to extend some interface to allow for the deletion of nodes from an archive. I'm still not sure where the best place for that it, yet.
If you can't connect to the relay, there isn't currently any visual indication that you're "offline" or disconnected. There should be some UI feature that indicates as such. One idea may be to change the color of the banner bar to Red, similar to how k9s handles it. Another may be to add a message to the top bar. However the indication, it should also be reflected in the Settings, when you click "connect".
Can this be marked as resolved?
Nevermind. I thought new messages became automatically selected.
REPORTED RESOLVED INVALID
If you open the context menu on a message m1 and reply to m1 with message m2, m2 becomes selected/focused. However the context menu is attached to m1. This would not be an issue, since both m1 and m2 share the same ancestry. However the context menu is open and m2 is selected, so if you attempt to copy m2's contents m1's contents are copied instead.