Okay, let's do that with a retention policy. GRW shows history and diffs, for all events.
Discussion
Had to keep it in the browser DB, for now. Just to get it going. I guess I can check all of the backend relay and database implementations, to see if any have retention policies, but it's simpler to just do the local cache and then pull from a remote relay.
Otherwise, it's more 🍝 code.
And it would quickly turn into a lot of data, even with compression.
Don't want to encourage people to keep important things on their local machine, if they're not a sys admin. Just want to keep the things they have been working on, lately, handy and offline -accessible, not run a local archive.