Closed rccar401 closed 3 weeks ago
Burner accounts, for some reason, are prone to getting suspended easily. I've tested it. But one weird thing is, my permanent accounts work fine, even after all this time. By permanent, I mean the accounts which is intermittently use to access Twitter from a browser. Maybe it's because of the fact that burner account are easy to detect based on the HTTP requests they make.
I'm trying to find a way to bypass or atleast mask their activity. Any insights will be valuable.
Ahh gotcha, thanks! That makes a ton of sense-- I'll switch over to permanent account and see if that helps. I saw some Reddit posts about fresh accounts getting flagged for ban more often than old accounts, so that's potentially the root cause?
Another quick q-- are you able to sign in via phone number via npx rettiwt auth login
or is that method for email only?
Love this project btw, thanks for all the work you're doing
I saw some Reddit posts about fresh accounts getting flagged for ban more often than old accounts, so that's potentially the root cause?
I guess yes, atleast that's what has been happening to me throughout my testing. I've been using this with my primary Twitter account with my own name on it, and it's been working consistently without any issues, since the conception of this library.
are you able to sign in via phone number via npx rettiwt auth login or is that method for email only?
Phone number in place of email should work (assuming 2FA isn't required).
I'm working on a fairly small project and already have seen accounts get suspended while using rettiwt.tweet.search via node. I've now created 6 burner accounts and generated tokens for each but after a few days of use they get suspended.
I'm not using a proxy or anything like that, which might be causing the issue? It's not at a crazy scale or anything right now, and I haven't been rate limited yet (only banned).