This is a forked repository for individual purpose with some missing features.

To use full-fledged version refer to: https://github.com/bocchilorenzo/ntscraper

This is a simple library to scrape Nitter instances for tweets. It can:

• search and scrape tweets with a certain term

• search and scrape tweets with a certain hashtag

• scrape tweets from a user profile

• get profile information of a user, such as display name, username, number of tweets, profile picture ...

If the instance to use is not provided to the scraper, it will use a random public instance. If you can, please host your own instance in order to avoid overloading the public ones and letting Nitter stay alive for everyone. You can read more about that here: https://github.com/zedeus/nitter#installation.

First, initialize the library:

from ntscraper import Nitter

scraper = Nitter(log_level=1, skip_instance_check=False)

The valid logging levels are:

• None = no logs
• 0 = only warning and error logs
• 1 = previous + informational logs (default)

The skip_instance_check parameter is used to skip the check of the Nitter instances altogether during the execution of the script. If you use your own instance or trust the instance you are relying on, then you can skip set it to 'True', otherwise it's better to leave it to false.

Then, choose the proper function for what you want to do from the following.

github_hash_tweets = scraper.get_tweets("github", mode='hashtag')

bezos_tweets = scraper.get_tweets("JeffBezos", mode='user')

Parameters:

• term: search term
• mode: modality to scrape the tweets. Default is 'term' which will look for tweets containing the search term. Other modes are 'hashtag' to search for a hashtag and 'user' to scrape tweets from a user profile
• number: number of tweets to scrape. Default is -1 (no limit).
• since: date to start scraping from, formatted as YYYY-MM-DD. Default is None
• until: date to stop scraping at, formatted as YYYY-MM-DD. Default is None
• near: location to search tweets from. Default is None (anywhere)
• language: language of the tweets to search. Default is None (any language). The language must be specified as a 2-letter ISO 639-1 code (e.g. 'en' for English, 'es' for Spanish, 'fr' for French ...)
• to: user to which the tweets are directed. Default is None (any user). For example, if you want to search for tweets directed to @github, you would set this parameter to 'github'
• filters: list of filters to apply to the search. Default is None. Valid filters are: 'nativeretweets', 'media', 'videos', 'news', 'verified', 'native_video', 'replies', 'links', 'images', 'safe', 'quote', 'pro_video'
• exclude: list of filters to exclude from the search. Default is None. Valid filters are the same as above
• max_retries: max retries to scrape a page. Default is 5
• instance: Nitter instance to use. Default is None and will be chosen at random

Returns a dictionary with tweets and threads for the term.

You can also scrape multiple terms at once using multiprocessing:

terms = ["github", "bezos", "musk"]

results = scraper.get_tweets(terms, mode='term')

Each term will be scraped in a different process. The result will be a list of dictionaries, one for each term.

NOTE: only run the multiprocessing code in a if __name__ == "__main__" block to avoid errors. With multiprocessing, only full logging is supported. Also, the number of processes is limited to the number of available cores on your machine. Finally, you could experience more rate limiting with multiprocessing (still investigating this).

bezos_information = scraper.get_profile_info("JeffBezos")

Parameters:

• username: username of the page to scrape
• max_retries: max retries to scrape a page. Default is 5
• instance: Nitter instance to use. Default is None

Returns a dictionary of the profile's information.

random_instance = scraper.get_random_instance()

Returns a random Nitter instance.

Due to recent changes on Twitter's side, some Nitter instances may not work properly even if they are marked as "working" on Nitter's wiki. If you have trouble scraping with a certain instance, try changing it and check if the problem persists.

• For Tweets:
  • Removed pools and queues to enable Serverless Deployments
• For Customized Responses:
  • If an account is suspended, the returned message in response is: "Account is suspended"
  • If an account is protected, the returned message in response is: "Account is protected"
  • If an account doesn't have tweets in the specified duration, the returned message is: "Account does not have tweets"
  • Otherwise, the returned message is: "Account does not exist"
• Now you can scrape a single tweet using fn call: get_user_tweet(user_name, tweet_id, instance)