You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice to have a way to specify how long Objects are valid before we need to refresh them. Probably per-protocol, and even may vary with protocols, eg ATProto commits and CID-based objects are permanent, records vary, and did:plc resolution is currently 24-72h ish (bluesky-social/atproto#1535). Also, if refresh fails, we can probably often use our stale stored version, but maybe not always?
The text was updated successfully, but these errors were encountered:
Would be nice to have a way to specify how long
Object
s are valid before we need to refresh them. Probably per-protocol, and even may vary with protocols, eg ATProto commits and CID-based objects are permanent, records vary, anddid:plc
resolution is currently 24-72h ish (bluesky-social/atproto#1535). Also, if refresh fails, we can probably often use our stale stored version, but maybe not always?The text was updated successfully, but these errors were encountered: