snscrape

Anyone who monitors what is being sent from their own computers over their own networks sees the Bearer token. Everyone, including any member of the public, who visits twitter.com gets the same Bearer token. No need to have an "account" with Twitter or to be "logged in". One can simulate this with cURL. js=$(curl -sA "" https://twitter.com|grep -m1 -o "https://abs.twimg.com/responsive-web/client-web-legacy/main[^\"]*"); curl -A "" $js|tr , '\n'|grep -o \"AAAA.*\" The same Bearer token value is used by people around the web for retrieving public tweets. It's public information. For example, https://stackoverflow.com/questions/61140863/python-download... https://github.com/twintproject/twint/raw/master/twint/run.p... https://pypi.org/project/ScrapeTweets/ https://stackoverflow.com/questions/67137294/twitter-scrapin... https://githu

I've been using this https://github.com/JustAnotherArchivist/snscrape and with 5 threads and no vpn, just my laptop, have been getting about 1 million tweets a day (vs 1000 before being rate limited on the api). Lots of fun

I hope you’ll get a better answer, but a minimal solution is to use snscrape (https://github.com/JustAnotherArchivist/snscrape) to download a raw JSON dump of a user timeline. Some caveats: 1. This doesn’t work for all users (e.g. some accounts seem to remain deindexed after unsuspensions). 2. While you can get rid of 90% of the file size by removing fluff columns (e.g. related to processing media and emojis), keep a backup. When importing such JSON, I unwittingly did a lossy data type conversion, and it can be irreparable once the tweets are deleted. $ snscrape --progress --jsonl twitter-user jack > jack.json [PS With courtesy rate limiting, depending on the account size, you may then script a way to send each tweet URL for archival in the Wayback Machine.]