Burner account getting blocked quickly
DrSocket opened this issue · comments
Hi, Do you know something about the rate limit? It's amazing you manage to keep a public instance running with 1 account. My accounts get blocked often with:
"status_code: 200, msg: Twitter responded with an error: AuthorizationError: Authorization: Denied by access control: To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account."
How do you handle this?
Thank you
(I realise this is not really an 'Issue', let me know if there is a better way to contact you to ask a question)
Well I used to use multiple accounts (but not many) and they do indeed get rate limited fairly quickly. Some accounts seem to have been locked and the instances that were linked to that account broke but others just kept working or got that message as well and I had to either confirm a captcha or just ignore it and the instance just kept working anyway.
You can contact me by email or on matrix https://privacydev.net/contact.html