pull down to refresh

0 sats \ 15 replies \ @sox 4 Aug \ parent \ on: Stacker Saloon
Wait!
Subscribing to a territory won't change the status on the territory header until the next full refresh
But you are indeed subscribed:
write
preview
100 sats \ 14 replies \ @ek 4 Aug
yeah this is probably a separate bug
reply
0 sats \ 8 replies \ @WeAreAllSatoshi 4 Aug
I didn’t follow all of this discussion. Do you think you’ve identified the issues for my specific case?
reply
50 sats \ 7 replies \ @ek 4 Aug
No, I was not :/
reply
201 sats \ 6 replies \ @WeAreAllSatoshi 4 Aug
Testing?
reply
150 sats \ 5 replies \ @ek 4 Aug
Oh, no, but we deployed Declarative Web Push. It should only affect iOS 18.4+ though 🤔
Was it only one notification?
/cc @sox
reply
150 sats \ 2 replies \ @ek 4 Aug
Could be that you got unlucky and we sent out a push notification with the new format while the old service worker was still running on your device
If that's the case, it shouldn't happen again
view all 2 replies
50 sats \ 0 replies \ @sox 4 Aug
Ah, damn I forgot that old service workers might still receive these new payloads that they can’t recognize.
Visiting SN will update the service worker, also the background updates will probably update it… I hope. I think I should’ve pushed this in two phases (maximum compatibility -> less bloat)
reply on another page
100 sats \ 0 replies \ @WeAreAllSatoshi 4 Aug
Yes just one
reply on another page
0 sats \ 4 replies \ @ek 4 Aug
Can you reproduce what you meant? I think I got confused by what I saw. I thought I saw me not being subscribed to ~security, but not sure if I really wasn't subscribed or not.
The button seems to reflect the state correctly:
also still correct after page reload
reply
100 sats \ 3 replies \ @sox 4 Aug
The action is correctly represented, it's client-side navigation that breaks the state
reply
119 sats \ 1 reply \ @ek 4 Aug
ohhh, I see
reply
50 sats \ 0 replies \ @sox 4 Aug
Subscribing to a territory won't change the status on the territory header until the next full refresh
I actually thought something different was happening, but when I tried again I discovered this different little behavior
reply
0 sats \ 0 replies \ @sox 4 Aug
lol wrong vid sorry, fixed
reply