[ soapbox-pub/ditto ] Fix notification dot reappearing after marking as read
Remove the invalidateQueries call in markAsRead that raced with the
setQueriesData(false) update. The invalidation triggered an immediate
refetch whose queryFn closure still held the old notificationsCursor
(from a render before the settings cache update propagated). That stale
refetch re-queried the relay with the old since value, found the same
unread events, returned true, and overwrote the false just set --
causing the dot to reappear.
https://github.com/soapbox-pub/ditto/commit/2f1bf0bca5f5f3f0d259368c74980fd8010593e1
nostr-summary / Nostr Summary
npub10l…sv2ux
2026-04-03 02:03:42 UTC
Author Public Key
npub10l479fv64qn03a3n0dqsryu74tyzl48xef0nc7u0z09q8tfx72ls7sv2uxSeen on
wss://relay.damus.ioPublished at
2026-04-03 02:03:42 UTCEvent JSON
{
"id": "6f69a927fd887d99c8f11dd631591ed77966a2d107bcef5e70a5552a637750d0",
"pubkey": "7febe2a59aa826f8f6337b4101939eaac82fd4e6ca5f3c7b8f13ca03ad26f2bf",
"created_at": 1775181822,
"kind": 1,
"tags": [
[
"proxy",
"https://github.com/soapbox-pub/ditto/commit/2f1bf0bca5f5f3f0d259368c74980fd8010593e1",
"web"
]
],
"content": "[ soapbox-pub/ditto ] Fix notification dot reappearing after marking as read\n\nRemove the invalidateQueries call in markAsRead that raced with the\nsetQueriesData(false) update. The invalidation triggered an immediate\nrefetch whose queryFn closure still held the old notificationsCursor\n(from a render before the settings cache update propagated). That stale\nrefetch re-queried the relay with the old since value, found the same\nunread events, returned true, and overwrote the false just set --\ncausing the dot to reappear.\n\nhttps://github.com/soapbox-pub/ditto/commit/2f1bf0bca5f5f3f0d259368c74980fd8010593e1",
"sig": "780b391116c6917cdd197399be8bca831e387e582a687a52781fc1397ed9bd105dde2d1527e751e11a705bb7faa99a4f300284b034fc8c7418e9b49ccb3301f9"
}