Account being logged out

[Somberor]

Does anyone else has an issue when his account is being logged out after some time and the session of ct0 and auth_token is not working anymore and requires relogin?

[cmj]

I've been trying to nail this down for a while. I manage many accounts, some old, some new, and it seems like newer accounts have their auth_tokens revoked every 30 days. My RSS CGI script cycles through roughly 10 accounts and only the newer ones have issues, as with providing new accounts with Nitter instances (using cookies, not oauth_tokens).

I use the v1/verify_credentials endpoint and pass the auth_token to it to verify if it's still valid. I think it's a pretty simple call to check if the token is valid; or just use any 401 and use that to re-auth. It would also have to check if the account is suspended, which verify_credentials does.

Here's a basic example https://github.com/cmj/twitter-tools/blob/main/auth/verify_credentials.sh

That said, I think any account that doesn't show activity these days within a 30-day period will have to re-auth. Presumably their bot-mitigation stuff.

[Somberor]

Do you know when does VerifyCredentials executed on the site itself? (what action uses that endpoint)

…

On Wed, 15 Jan 2025 at 3:16 cmj ***@***.***> wrote: I've been trying to nail this down for a while. I manage many accounts, some old, some new, and it *seems* like newer accounts have their auth_tokens revoked every 30 days. My RSS CGI script cycles through roughly 10 accounts and only the newer ones have issues, as with providing new accounts with Nitter instances (using cookies, not oauth_tokens). I use the VerifyCrendentials endpoint and pass the auth_token to it to verify if it's still valid. I think it's a pretty simple call to check if the token is valid; or just use any 401 and use that to re-auth. It would also have to check if the account is suspended, which VerifyCredentials does. Here's a basic example https://github.com/cmj/twitter-tools/blob/main/auth/verify_credentials.sh — Reply to this email directly, view it on GitHub <#288 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFUEC3BHKSD7CBGL6U4X5T2KWZG7AVCNFSM6AAAAABVF4LT5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJRGQZTCOJTGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>