Cache subscription time ranges? #775

Closed
opened 2024-06-08 12:45:21 +12:00 by mikedilger · 1 comment
mikedilger commented 2024-06-08 12:45:21 +12:00 (Migrated from github.com)

We no longer preserve the general feed. When you switch away and back, it reloads from scratch. This means more duplicate event downloading from relays.

If we had a per-relay per-filter cache of time ranges, we could modify filters to exclude time ranges we already asked for so we don't repeat these.

We no longer preserve the general feed. When you switch away and back, it reloads from scratch. This means more duplicate event downloading from relays. If we had a per-relay per-filter cache of time ranges, we could modify filters to exclude time ranges we already asked for so we don't repeat these.
mikedilger commented 2024-06-09 08:51:48 +12:00 (Migrated from github.com)

Instead I separated anchors. Each feed keeps it's own anchor and we preserve them between feed switches. Good enough.

Instead I separated anchors. Each feed keeps it's own anchor and we preserve them between feed switches. Good enough.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nostr/gossip#775
No description provided.