A privacy- and performance-focused alternative Twitter front-end that is free and open source.
Nitter is an alternative Twitter front-end that is free and open source with an emphasis on performance and privacy.
The Invidious project served as inspiration.
- Clients never communicate with Twitter; all requests are processed through the backend.
- Using the unauthorised Twitter API.
- Light weight(For @nim lang, 60KB vs. 784KB via twitter.com).
- RSS feed.
- Themes Support for mobile.
- No permissible proprietary instances under the AGPLv3 licence.
A community-maintained list of nitter instances and browser extensions may be found on the wiki.
It will soon be possible to follow other Twitter users and maintain a tidy chronological timeline without having a Twitter account thanks to the addition of a straightforward account structure.
How to install Nitter?
There are three code dependencies.
You require a Nim installation to compile Nitter; more information is available at nim-lang.org. You can install it in the user directory you create below or on the entire system. You need to install libsass in order to compile the scss files. You can utilise libsass-dev on Debian and Ubuntu systems.
Redis is necessary for account information now and in the future. Most distributions should have redis or redis-server (Ubuntu/Debian) available. Running it with the default configuration is acceptable because Nitter is configured to use localhost and the default Redis port.
Why use Nitter?
Creating a nitter account, cloning the repository, and building the project along with the scss and md files are all demonstrated here.
# useradd -m nitter
# su nitter
$ cd nitter
$ nimble build -d:release
$ nimble scss
$ nimble md
$ cp nitter.example.conf nitter.conf
In nitter.conf, specify your hostname, port, HMAC key, https (which needs to be accurate for cookies), and Redis information. Run redis-server —daemonize yes or use systemctl enable —now redis to launch Redis. Use the systemd service listed below to launch Nitter instead of typing./nitter. For security and performance reasons, you should run Nitter behind a reverse proxy like Nginx or Apache.
To run Nitter with Docker
Redis must first be installed and operated independently before Nitter can be launched with Docker. See the instructions below for running Redis using Docker.
Nitter must be created and operated in Docker.
docker build -t nitter:latest .
docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d –network host nitter:latest
Additionally, a pre built Docker image is offered:
docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d –network host zedeus/nitter:latest
Using docker-compose to run both Nitter and Redis as different containers: Change redisHost from localhost to nitter-redis in nitter.conf, then run:
docker-compose up -d
Remember that the nitter.conf file must exist in the location where you run the Docker commands.
You can use the following service file to run Nitter with Systemd:
Description=Nitter (An alternative Twitter front-end)
# set user and group
# configure location
No real logging implemented
There is currently no meaningful logging system in place, and Nitter broadcasts some problems to stdout. You can check if Nitter is operating with systemd by typing journalctl -u nitter.service. You can use the following command if the Docker image is running: docker logs —follow [container id for nitter]
docker logs –follow *nitter container id*