reSubscribeInFlightSubscriptions re-sends the REQ with the same sub id and the exact same filters. Nothing repositions since.
Two consequences on mobile, where the socket dies every time the app is backgrounded:
- A subscription carrying a
limit silently loses the middle of the gap: per NIP-01 the relay returns only the N most recent stored events, so a long background period drops everything older than those N.
- A subscription with a fixed
since re-downloads the whole history since that point on every reconnect. Duplicates are only dropped at the very end of the pipeline, after signature verification and cache write, so the cost is real and grows with session length.
reSubscribeInFlightSubscriptionsre-sends the REQ with the same sub id and the exact same filters. Nothing repositionssince.Two consequences on mobile, where the socket dies every time the app is backgrounded:
limitsilently loses the middle of the gap: per NIP-01 the relay returns only the N most recent stored events, so a long background period drops everything older than those N.sincere-downloads the whole history since that point on every reconnect. Duplicates are only dropped at the very end of the pipeline, after signature verification and cache write, so the cost is real and grows with session length.