Show HN: Twitter API Reverse Engineered

Post by JeremyNT » Thu, Apr 13, 2023, 3:44 PM UTC

dawnerd wrote: post #18

Nothing new. Nitter for example has been using these endpoints for a while.

Post by v0idzer0 » Thu, Apr 13, 2023, 5:22 PM UTC

JeremyNT wrote: post #31

dawnerd wrote: post #18

Nothing new. Nitter for example has been using these endpoints for a while.

It continues to surprise me that Elon hasn't shut out Nitter yet. Maybe there's just not enough engineering talent left at Twitter to do it.

Post by jjulius » Thu, Apr 13, 2023, 5:27 PM UTC

v0idzer0 wrote: post #34

ck2 wrote: post #11

If this can be built, build a twitter clone. As each big entity/celebrity quits twitter or starts having serious conflicts, approach them to cross-post their content to the new clone site. In a year the masses will follow. Once Musk misses a billion-dollar-per-year payments a few times to the Saudis they will own twitter and then it will be like TikTok censorship the next time they murder a journalist they disagree w…

Do you really expect the richest man in the world to miss payments? He has enough money to buy Twitter 4 more times

Post by dariusj18 » Thu, Apr 13, 2023, 8:59 PM UTC

xeromal wrote: post #30

userbinator wrote: post #28

Earlier quoted context omitted.

How is it "stealing" to access a service you already have access to for free? Go to twitter.com in a browser. This is just a different type of browser. Physical analogies never work right with digital data.

I'm sure companies wouldn't mind if a singular person was doing singular things with the API, but when someone uses this API to behave like more than 1 person is where companies get annoyed. To use an annoying analogy or two, take a penny leave a penny but someone shoves their hand in there and takes all of it. It costs money to service requests and twitter et all make that money back through advertising and subscrip…

Post by 1vuio0pswjnm7 » Fri, Apr 14, 2023, 1:33 AM UTC

1vuio0pswjnm7 wrote: post #16

wolfgang42 wrote: post #6

Earlier quoted context omitted.

For some reason Twitter’s frontend uses a hard-coded bearer token, at least for anonymous users. You’ll see exactly the same string if you load a Twitter page and look at the XHR requests in your own browser. (It seems to change occasionally, but old ones keep working in my experience.)

FWIW, I have never logged in to Twitter and I have always been able to retrieve all tweets. At first, I used mobile.twitter.com in a text-only browser, no token required. Since they started using GraphQL, I retrieve tweets as JSON. They have changed the token once. The current one is Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA IME, the old token will…

   #!/bin/sh
   test $# -gt 0||exec echo usage: $0 query
   DATA=$(echo '{"query":"'$@'","analyticsTags":["web"],"page":0,"hitsPerPage":30,"minWordSizefor1Typo":4,"minWordSizefor2Typos":8,"advancedSyntax":true,"ignorePlurals":false,"clickAnalytics":true,"minProximity":7,"numericFilters":[],"tagFilters":["story",[]],"typoTolerance":"min","queryType":"prefixNone","restrictSearchableAttributes":["title","comment_text","url","story_text","author"],"getRankingInfo":true}');
   HOST=uj5wyc0l7x-3.algolianet.com
   _PATH="/1/indexes/Item_production_sort_date/query?x-algolia-agent=Algolia%20for%20JavaScript%20(4.0.2)%3B%20Browser%20(lite)&x-algolia-api-key=8ece23f8eb07cd25d40262a1764599b1&x-algolia-application-id=UJ5WYC0L7X"
   # HTTP client (curl)
   #curl -A "" -d "$DATA" "https://$HOST$_PATH"
   # TCP client
   #echo "
   #foreground=no
   #[x]
   #accept=127.0.0.8:80
   #client=yes
   #connect=167.114.119.142:443
   #options=NO_TICKET
   #options=NO_RENEGOTIATION
   #renegotiation=no
   #sni=
   #sslVersion=TLSv1.3
   #" |stunnel -fd 0;
   #tr @ '\r'