Appear to be logged in after revoking access to the session #258
Description
Describe the bug
After you revoke access to the session via https://bsky.social/account you still appear as logged in. Avatar is shown in the header and you can still perform actions that don't require an atproto connection just fine. However when you try to eg. write a record, it will fail.
To Reproduce
Steps to reproduce the behavior:
- Login
- Revoke session at https://bsky.social/account (or self hosted PDS equivalent)
- Refresh frontpage
Expected behavior
User is logged out.
Additional context
This is quite confusing considering we write to the PDS in the background, failures there aren't surfaced to the user currently. I think we can fix this bug simply by performing a request to check the session on page load, from the client would make sense so that we don't cause perf regression.