Nitter

Running a Nitter instance now requires real accounts, since Twitter removed the previous methods. This does not affect users. For instructions on how to obtain session tokens, see Creating session tokens. A free and open source alternative Twitter front-end focused on privacy and performance. Inspired by the Invidious project. No JavaScript or ads All requests go through the backend, client never talks to Twitter Prevents Twitter from tracking your IP or JavaScript fingerprint Uses Twitter's unofficial API (no developer account required) Lightweight (for @nim lang, 60KB vs 784KB from twitter.com) RSS feeds Themes Mobile support (responsive design) AGPLv3 licensed, no proprietary instances permitted The wiki contains a list of instances and browser extensions maintained by the community. Using an instance of Nitter (hosted on a VPS for example), you can browse Twitter without JavaScript while retaining your privacy. In addition to respecting your privacy, Nitter is on average around 15 times lighter than Twitter, and in most cases serves pages faster (eg. timelines load 2-4x faster). In the future a simple account system will be added that lets you follow Twitter users, allowing you to have a clean chronological timeline without needing a Twitter account. To compile the scss files, you need to install libsass . On Ubuntu and Debian, you can use libsass-dev . Here's how to create a nitter user, clone the repo, and build the project along with the scss and md files. NOTE: The published image is multi-arch — zedeus/nitter:latest runs natively on both amd64 and arm64 . To run Nitter with Docker, you'll need to install and run Redis separately before you can run the container. See below for how to also run Redis using Docker. First create your config file. The Docker commands mount it into the container, so it has to exist on the host beforehand. If you've cloned the repo: If you're using the prebuilt image without a local clone, download nitter.example.conf and save it as nitter.conf instead. Using docker-compose to run both Nitter and Redis as different containers: Change redisHost from localhost to nitter-redis in nitter.conf , then run: Note the Docker commands mount nitter.conf (and sessions.jsonl for docker-compose) from the directory you run them in. If a mounted file doesn't exist, Docker silently creates a directory in its place and the container fails with not a directory: Are you trying to mount a directory onto a file . Remove that directory and create the file as shown above. Nitter currently prints some errors to stdout, and there is no real logging implemented. If you're running Nitter with systemd, you can check stdout like this: journalctl -u nitter.service (add --follow to see just the last 15 lines). If you're running the Docker image, you can do this: docker logs --follow nitter container id