pull down to refresh

No, only this account
50 sats \ 19 replies \ @sox 4 Aug
Interesting, it's strange that you're not subscribed to that territory but still receive push notifications.
Both the notifications and push notifications gather data from the server based on the premise that you are indeed subscribed to the territory. They only differ in filtering: notifications page won't show you posts that are outlawed, freebies, not yet paid; push notifications will instead do.
reply
150 sats \ 18 replies \ @ek 4 Aug
I was able to reproduce the bug with a subscription but a new post isn't showing up in /notifications
edit: Ohh, but can't explain why he even received a push notification without an apparent territory subscription (separate bug)
reply
0 sats \ 0 replies \ @ek 4 Aug
mhh ok, I think that wasn't the bug you saw, I only didn't see the notification because of the default cost filter of 10, and the post cost was 1 sat.
reply
0 sats \ 15 replies \ @sox 4 Aug
Wait!
Subscribing to a territory won't change the status on the territory header until the next full refresh
But you are indeed subscribed:
reply
reply
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 :/
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