adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-11-03 08:02:19 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

feat: Persistant package data #115

New Issue
Closed
opened 2026-10-05 01:57:46 +02:00 by adam · 1 comment
adam commented 2026-10-05 01:57:46 +02:00
Owner
Copy link
Copy source

I would like to see a feature of persistance of package data for the Pakage Feed and Mesh Visualizer view, in some way.
This should solve the problem that both views are empty after opening a new browser session. After an amount of time both views are filled slowly with data. Is there a way that these views are populated with data, directly after opening, e.g. with the data of the last hour (or another configurable rolling time window)?

I would like to see a feature of persistance of package data for the Pakage Feed and Mesh Visualizer view, in some way. This should solve the problem that both views are empty after opening a new browser session. After an amount of time both views are filled slowly with data. Is there a way that these views are populated with data, directly after opening, e.g. with the data of the last hour (or another configurable rolling time window)? <!-- github-sync-id:4206022303 -->
adam closed this issue 2026-10-05 01:57:46 +02:00
adam commented 2026-10-05 01:57:47 +02:00
Author
Owner
Copy link
Copy source

It would be possible, but both these views are only meaningfully usable with very very recent data -- the visualizer is basically broken with more than a hundred nodes or so, and the raw packet feed isn't very useful with 500 historical entries showing. So, that's not a feature I'm going to implement at this time because it means a fair amount of plumbing (new fields to save, new bulk data endpoints, deciding what to do with analytics) for features that basically have zero benefit with historical data. Sorry!

It would be possible, but both these views are only meaningfully usable with very very recent data -- the visualizer is basically broken with more than a hundred nodes or so, and the raw packet feed isn't very useful with 500 historical entries showing. So, that's not a feature I'm going to implement at this time because it means a fair amount of plumbing (new fields to save, new bulk data endpoints, deciding what to do with analytics) for features that basically have zero benefit with historical data. Sorry! <!-- github-comment-id:4189066789 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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