apparently when you delete 4k tweets per hour you get put in the api penalty box for a bit.
-
@matthiasott just a seemingly well-regarded script I found in some blog post that appeared to do what I'd expect... fetch latest 20 at a time, post a delete to each ID, do it again. It hit the rate limit after a while though.
-
-
@matthiasott no but that looks like a good one to try because I'm noticing very old tweets are still findable via google even though they don't show on my profile. That script looks helpful in that it uses your archive for IDs and avoids the fetches
-
@scottjehl I’m trying it right now. Had to restart it twice, but so far, my account is still reachable and it is still deleting…
-
@matthiasott working for me too! thanks for that
-
@scottjehl When I read @luca‘s name I knew it might be worth a try. He also created the fantastic Fedifinder (until Elon killed the API).
-
@matthiasott @luca Seems to work great. Deleted about 14k so far here
-
@scottjehl @luca It stopped a few times over here. But after switching from Safari to Chrome, it has deleted >6000 Tweets and is still running
-
@matthiasott @scottjehl Chrome dies at around 10k Tweets. Firefox can handle 100k+ in one go.
Someone reported that X Corp has a secondary limit for requests and adding a short pause may make the whole process smoother. If you see a lot of 429 errors, maybe add that pause: https://github.com/lucahammer/tweetXer/issues/14
-
@luca @scottjehl Thanks!
