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
Kittybox uses very short-lived access tokens (7 days) and long-lived refresh tokens. The intended behavior is for an app to refresh its token once it expires, to prevent an accidentally leaked token from allowing long-term access to my website. Quill doesn't seem to do so, resulting in errors and need to re-authenticate manually every seven days.
While I could special-case Quill's client ID, I feel like showing preferential behavior for clients using outdated standards might do more harm than good to the ecosystem, therefore I am filing this as an issue for Quill instead.
The text was updated successfully, but these errors were encountered:
Kittybox uses very short-lived access tokens (7 days) and long-lived refresh tokens. The intended behavior is for an app to refresh its token once it expires, to prevent an accidentally leaked token from allowing long-term access to my website. Quill doesn't seem to do so, resulting in errors and need to re-authenticate manually every seven days.
While I could special-case Quill's client ID, I feel like showing preferential behavior for clients using outdated standards might do more harm than good to the ecosystem, therefore I am filing this as an issue for Quill instead.
The text was updated successfully, but these errors were encountered: