This change adds ".m4s" and ".mp4" to the regex that modifies m3u8 playlist files proxied from twitter, and adds ".m4s" to the list of extensions proxied through nitter. The net effect is the new video format that twitter is using now should be supported.
|7 days ago|
|.github||4 months ago|
|public||3 months ago|
|src||7 days ago|
|tests||6 months ago|
|tools||2 years ago|
|.gitignore||2 years ago|
|.travis.yml||4 months ago|
|Dockerfile||6 months ago|
|LICENSE||2 years ago|
|README.md||3 months ago|
|config.nims||6 months ago|
|nitter.conf||4 months ago|
|nitter.nimble||6 months ago|
|screenshot.png||2 years ago|
|start.sh||12 months ago|
A free and open source alternative Twitter front-end focused on privacy.
Inspired by the Invidious project.
- All requests go through the backend, client never talks to Twitter
- Uses Twitter's unofficial API (no rate limits or developer account required)
- Lightweight (for @nim_lang, 60KB vs 784KB from twitter.com)
- RSS feeds
- Mobile support (responsive design)
- AGPLv3 licensed, no proprietary instances permitted
- Account system with timeline support
- Archiving tweets/profiles
- Developer API
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 Nitter you need a Nim installation, see nim-lang.org for details. It is possible to install it system-wide or in the user directory you create below.
To compile the scss files, you need to install
libsass. On Ubuntu and Debian,
you can use
Redis is required for caching and in the future for account info. It should be
available on most distros as
Running it with the default config is fine, Nitter's default config is set to
use the default Redis port and localhost.
Here's how to create a
nitter user, clone the repo, and build the project
along with the scss.
# useradd -m nitter # su nitter $ git clone https://github.com/zedeus/nitter $ cd nitter $ nimble build -d:release $ nimble scss $ mkdir ./tmp
Set your hostname, port, HMAC key, https (must be correct for cookies), and
Redis info in
nitter.conf. To run Redis, either run
redis-server --daemonize yes, or
systemctl enable --now redis (or
redis-server depending on the distro). Run Nitter by executing
using the systemd service below. You should run Nitter behind a reverse proxy
such as Nginx or Apache for
To build and run Nitter in Docker:
docker build -t nitter:latest . docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d -p 8080:8080 nitter:latest
A prebuilt Docker image is provided as well:
docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d -p 8080:8080 zedeus/nitter:latest
Note the Docker commands expect a
nitter.conf file in the directory you run them.
To run Nitter via systemd you can use this service file:
[Unit] Description=Nitter (An alternative Twitter front-end) After=syslog.target After=network.target [Service] Type=simple # set user and group User=nitter Group=nitter # configure location WorkingDirectory=/home/nitter/nitter ExecStart=/home/nitter/nitter/nitter Restart=always RestartSec=15 [Install] WantedBy=multi-user.target
Then enable and run the service:
systemctl enable --now nitter.service
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
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*