Do people have a good strategy for syncing content through nostr?
For Mutiny when we sync nwc, dm, etc we save the highest timestamp of the event we last synced, however this doesn't work the best because relays send us them in descending order so if the app is closed before we process all the events, we do not fully sync all the events.
Have been thinking of switching it to instead have it save the last timestamp of the last EOSE we received. To try to better ensure we sync every message first.
Does anyone else have a better strategy?
benthecarman / Carman
npub1u8…6turz
2024-05-10 16:47:11
Author Public Key
npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turzPublished at
2024-05-10 16:47:11Event JSON
{
"id": "572c0f8f386443c5761eeb750bff15f3f2a34653e067d2904d87deec86a8cacb",
"pubkey": "e1ff3bfdd4e40315959b08b4fcc8245eaa514637e1d4ec2ae166b743341be1af",
"created_at": 1715359631,
"kind": 1,
"tags": [],
"content": "Do people have a good strategy for syncing content through nostr?\n\nFor Mutiny when we sync nwc, dm, etc we save the highest timestamp of the event we last synced, however this doesn't work the best because relays send us them in descending order so if the app is closed before we process all the events, we do not fully sync all the events.\n\nHave been thinking of switching it to instead have it save the last timestamp of the last EOSE we received. To try to better ensure we sync every message first.\n\nDoes anyone else have a better strategy?",
"sig": "3c4dee0637edcd134ca4439d75d8abe5d6791ee20c851d0c27f44db612e559b2b24607fa35b1b9805736e859fdbddb9ef429e3fdf6a01d3511470662ad93e706"
}