HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
twintproject
twint
Python2018–2023
twintproject / twint · Archived

twint

An advanced Twitter scraping & OSINT tool written in Python that doesn't use Twitter's API, allowing you to scrape a user's followers, following, Tweets and more while evading most API limitations.

7Distinct people
10Mentions
0Explicit recommenders
16.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An advanced Twitter scraping & OSINT tool written in Python that doesn't use Twitter's API, allowing you to scrape a user's followers, following, Tweets and more while evading most API limitations.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2018-12-16 15:26:52 UTC to 2023-04-15 03:50:41 UTC.

01232018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC110
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

10 sources
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
Read the rest
In Show HN: Twitter API Reverse Engineered
"Basically anything but how Twitter currently does it." This is what I use when I need to look at a Twitter page. https://news.ycombinator.com/item?id=28071491 Saved in a script called "twt", usage as follows twt username |twt > 1.htm firefox ./1.htm Although I use a text-only browser not Firefox so its designed for that. Its not perfect but its better than anything else Ive seen short of https://github.com/twintproject/twint and its still faster and smaller than installing Python. The future of the web could be that users request JSON and then users create a page to their liking, client-side, using their own Javascript (or whatever language they want to use). As it stands, on todays web a "tech" company, often using Javascript, causes the users browser to request the JSON and then more downloaded Javascript, not controlled by th
Read the rest
e user, creates a user-hostile page for the user to consume the JSON. Its a Rube Goldberg machine designed for tracking and advertising, not users. Imagine if the user conscisouly requests the JSON and is then in control of designing the page for herself. What were tweets but short strings of text. Hard to believe that now looking at a Twitter page. Thats because the user isnt in control of the design. Remember the "tech" company does not own the data. Its public information. User-generated content wrapped in user-hostile, developer-generated markup.
In Show HN: TweeView – A Tree Visualisation of Twitter Conversations

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.