Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Will the new Twitter API policy impact Nitter? #783

Closed
Tiv0w opened this issue Feb 2, 2023 · 14 comments
Closed

Will the new Twitter API policy impact Nitter? #783

Tiv0w opened this issue Feb 2, 2023 · 14 comments

Comments

@Tiv0w
Copy link

Tiv0w commented Feb 2, 2023

Twitter Dev account tweeted today that there will soon be no free access API anymore: https://nitter.net/TwitterDev/status/1621026986784337922#m

My school project is heavily reliant on Twitter (it's a requirement from the school), and deprecating the free access, I'm seeking alternatives. And one possibility would be to host my own Nitter instance and scrape it after (if the project still functions given this new Twitter information).

So I'm asking this to know if I should invest dev time into scraping my own Nitter instance or if I'm better off waiting for more news?
Thanks in advance for the reply.

(And thanks for Nitter, I only consume Twitter through Nitter instances for my personal entertainment.)

@zedeus
Copy link
Owner

zedeus commented Feb 2, 2023

It's very unlikely Nitter will be affected since the APIs aren't used in the official way with developer credentials. I'm slowly moving stuff to use their newer GraphQL APIs anyway, so if it breaks it'll be fixed soon-ish.

@jman-schief
Copy link

@zedeus since there is no open pull request for the GraphQL API migration, I'll leave a comment here. It would be great if you can document the GraphQL queries that Nitter will do - so that it's clearer how to reproduce them. From my personal experience, when I work on GraphQL sometimes it's difficult to reverse-engineering the code into the original gql query to reproduce the behaviour.

What do you think?

Thanks for Nitter, of course :)

@halictuz
Copy link

halictuz commented Feb 2, 2023

It's very unlikely Nitter will be affected since the APIs aren't used in the official way with developer credentials. I'm slowly moving stuff to use their newer GraphQL APIs anyway, so if it breaks it'll be fixed soon-ish.

How does it look from a legal standpoint now that Twitter is owned by Elon and is a private company. Did they actually change their view on such things like Nitter?

@BartTerpstra
Copy link

@halictuz
the "Developer Agreement", last modified 23 januari 2023, does contain the following clause.

"II. Restrictions on Use of Licensed Materials
A. Reverse Engineering and other Restrictions:
You will not or attempt to (and will not allow others to) [...]
c) use or access the Licensed Materials to create or attempt to create a substitute or similar service or product to the Twitter Applications; "

so 🤷

@zedeus
Copy link
Owner

zedeus commented Feb 3, 2023

I'm not bound by that developer agreement, so whatevs.

@zedeus
Copy link
Owner

zedeus commented Feb 3, 2023

@jman-schief It's not a real GraphQL API, it's really just an RPC-like API on a /graphql/ route, so the implementation isn't quite as complex.

@jadedgnome
Copy link

jadedgnome commented Apr 6, 2023

as of 2 hours ago, nitter no longer displays NSFW tweets unless you click the search option but don't actually search.

@UmBottesWillen
Copy link

Apart from the issue mentioned above, I also noticed that instances other than the official nitter.net instance, even up-to-date ones, will sometimes error out when trying to access pages of NSFW accounts. This issue is not guaranteed to occur, but it happens regularly enough since the announced Twitter API change.
Only the following message will be displayed:

Tab title: Jester route exception

An error has occured in one of your routes.

Detail: fatal.nim(53) sysFatal
asyncfutures.nim(389) read
asyncfutures.nim(389) read
asyncfutures.nim(389) read
index 0 not in 1 .. 12

@zedeus
Copy link
Owner

zedeus commented Apr 20, 2023

This will be fixed by #812 which I will merge soon. Twitter just banned unauthenticated access to the endpoint used for search, so I'm replacing it in that PR as well.

@sawtoothpuma
Copy link

Any updates yet? I want to view age restricted content but don't want to create an account to do so.

@Trit34
Copy link

Trit34 commented May 10, 2023

Any updates yet? I want to view age restricted content but don't want to create an account to do so.

Use PrivacyDev’s instance, then. But beware of the rate limit!

@innov8tor3
Copy link

@zedeus , first up thanks for Nitter.

I notice the Twitter Nitter account is now blocked.

I love the idea of Nitter instances on GitHub, is there a way to map all the instances, so folk can navigate if they need to?

And apologies, I don't properly understand Github. It would be great if the answer is here, but I am effectively wearing a blindfold, and would need very simple instruction, if possible.

Thanks again.

@zedeus
Copy link
Owner

zedeus commented May 17, 2023

@innov8tor3

I notice the Twitter Nitter account is now blocked.

What account? There is no account for Nitter.
Here's a list of instances: https://github.com/zedeus/nitter/wiki/Instances

@zedeus
Copy link
Owner

zedeus commented Jul 6, 2023

The answer was no, thankfully.

@zedeus zedeus closed this as completed Jul 6, 2023
@zedeus zedeus unpinned this issue Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants