pass this around your to your friends. somebody made an anon 500 donation so I am doubling the bounty to fix husky and bring it at least somewhat feature parity with pleroma, mitra whatever. husky is a great client but it needs serious TLC. if anyone else wants to drop one or two into this I will match it too

RT: https://poa.st/objects/54336782-ec6e-411d-bc8f-2a2519c59bac
anime graf mays 🛰️🪐@graf@poa.st
If you or somebody you knows wants to maintain husky again I'll throw some cash at it I know others that would tip that jar too.

RT: https://poa.st/objects/4a9acd9b-7bfd-44f9-8ec6-0a6b1eb10b6b

Replying to @⁨graf@poa.st⁩

@graf There was a problem with sessions - Husky didn't handle token expiration correctly: https://github.com/captainepoch/husky/issues/162

But I don't use it myself, maybe this has been fixed already

Mitra uses access tokens with an expiration time and when a token expires, protected API endpoints start returning 401 Unauthorized. When that happens, Husky stops refreshing timelines but doesn't ...GitHubLog out when access token expires? · Issue #162 · captainepoch/huskyMitra uses access tokens with an expiration time and when a token expires, protected API endpoints start returning 401 Unauthorized. When that happens, Husky stops refreshing timelines but doesn't ...by silverpill

Replying to @⁨silverpill@mitra.social⁩

@silverpill @graf >But I don't use it myself, maybe this has been fixed already

I tested on master branch and it seems not fixed. I set the expiration time to 60 seconds in the Mitra profile, but Husky stays logged in even after the token expires; it seems like this feature hasn't been implemented yet. If I remember correctly, Tusky has already implemented this, as soon as the token becomes invalid, it immediately pops up a dialog asking you to log in again.