- cross-posted to:
- privacyguides@lemmy.one
- foss@beehaw.org
- cross-posted to:
- privacyguides@lemmy.one
- foss@beehaw.org
For those not aware nitter is an opensource twitter frontend which has no ads or javascript.
Now it also bypasses the rate limits and other restrictions.
Amazing! I can’t wait to read about how they solved this. The devs were coming up with some very creative solutions the last I looked.
Great work to all the contributors!
Just phenomenal work; how could they even scrape data? When Musk restricts the API.
Don’t need API access to scrape data. That’s the whole point of scraping - you’re indistinguishable from regular traffic. Nitter could even impersonate a Google search crawler if they want.
I could be wrong but when looking at the changed code, it still uses a token, specifically on this line. It’s possibly using user routes instead of the actual paid API, but it’s hard to tell without knowing twitter’s API in depth. Also it’s not possible to get everything just by web scraping, especially after they locked everything behind logins. AFAIK the most you can do is impersonate search crawling and get singular tweets or profile bios.
Now it also bypasses the rate limits and other restrictions.
Man, that’s another win for the free and libre clones!
No account requirement and it works way faster and more cleanly than official Twitter too, for me.
Let’s hope they don’t throw a fit like Google is doing.
oh fr?! that’s great news! surprising too. no idea how they managed it, but i sure am glad they did!
From what I have heard, Twitter quietly went back on its decision to force you to make an account if you want to view a tweet.
I stopped checking twitter when nitter stopped working, great that is back
Uses a new bearer token and a new set of updated endpoints. Only thing missing is search.
Can someone who’s less stupid than me at programming explain this? From my understanding “endpoints” is a term related to APIs but… nitter just scrapes the site, doesn’t use the twitter API in any way
EDIT: nvm, the readme says they do use an “unofficial twitter api” of some sort