Persistence of Packet Feed and Visualization on Frontend Reload #5

Closed
opened 2026-10-05 01:51:48 +02:00 by adam · 1 comment
Owner

The packet feed and its visualization do not persist when the frontend is reloaded. Is this the expected behavior?

The packet feed and its visualization do not persist when the frontend is reloaded. Is this the expected behavior? <!-- github-sync-id:3913982472 -->
adam closed this issue 2026-10-05 01:51:48 +02:00
Author
Owner

Yes, it is. All decryptable packets (messages, both group and DM) are saved to the backend, and adverts and path packets update contact routing etc., but ultimately, the remainder are not functional. So, the correct/necessary effects of the packets are persisted, but it does not retain ALL raw packets it hears. The packet display on the frontend is just a streaming version of what the backend processes, and is not persisted in its raw form.

Yes, it is. All decryptable packets (messages, both group and DM) are saved to the backend, and adverts and path packets update contact routing etc., but ultimately, the remainder are not functional. So, the correct/necessary effects of the packets are persisted, but it does not retain ALL raw packets it hears. The packet display on the frontend is just a streaming version of what the backend processes, and is not persisted in its raw form. <!-- github-comment-id:3874671119 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#5