Nitter on Docker Swarm

Are you becoming increasingly wary of Twitter, post-space-Karen? Try Nitter, a (read-only) private frontend to Twitter, supporting username and keyword search, with geeky features like RSS and theming!

Nitter is a free and open source alternative Twitter front-end focused on privacy and performance, with features including:

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 rate limits or developer account required)
Lightweight (for @nim_lang, 60KB vs 784KB from twitter.com)
RSS feeds, Themes, Mobile support (responsive design)

Nitter Requirements

Preparation

Setup data locations

First we create a directory to hold the data which Redis will cache for nitter:

mkdir /var/data/nitter

Create config file

Nitter is configured using a flat text file, so create /var/data/config/nitter/nitter.conf from the example at in the repo, and then we'll mount it (read-only) into the container, below. Here's what it looks like, if you'd prefer a copy-paste (the only critical setting is redisHost be set to redis)

[Server]
address = "0.0.0.0"
port = 8080
https = true  # disable to enable cookies when not using https
httpMaxConnections = 100
staticDir = "./public"
title = "example.com's nitter"
hostname = "nitter.example.com"

[Cache]
listMinutes = 240  # how long to cache list info (not the tweets, so keep it high)
rssMinutes = 10  # how long to cache rss queries
redisHost = "redis" 
redisPort = 6379
redisPassword = ""
redisConnections = 20  # connection pool size
redisMaxConnections = 30
# max, new connections are opened when none are available, but if the pool size
# goes above this, they're closed when released. don't worry about this unless
# you receive tons of requests per second

[Config]
hmacKey = "imasecretsecretkey"  # random key for cryptographic signing of video urls
base64Media = false  # use base64 encoding for proxied media urls
enableRSS = true  # set this to false to disable RSS feeds
enableDebug = false  # enable request logs and debug endpoints
proxy = ""  # http/https url, SOCKS proxies are not supported
proxyAuth = ""
tokenCount = 10
# minimum amount of usable tokens. tokens are used to authorize API requests,
# but they expire after ~1 hour, and have a limit of 187 requests.
# the limit gets reset every 15 minutes, and the pool is filled up so there's
# always at least $tokenCount usable tokens. again, only increase this if
# you receive major bursts all the time

# Change default preferences here, see src/prefs_impl.nim for a complete list
[Preferences]
theme = "Nitter"
replaceTwitter = "nitter.example.com" 
replaceYouTube = "piped.video" 
replaceReddit = "teddit.net" 
proxyVideos = true
hlsPlayback = false
infiniteScroll = false

Nitter Docker Swarm config

Create a docker swarm config file in docker-compose syntax (v3), something like the example below:

version: "3.2" # https://docs.docker.com/compose/compose-file/compose-versioning/#version-3

services:

  nitter:
    image: zedeus/nitter:latest
    volumes:
      - /var/data/config/nitter/nitter.conf:/src/nitter.conf:Z,ro
    deploy:
      replicas: 1
      labels:
        # traefik
        - traefik.enable=true
        - traefik.docker.network=traefik_public
        - traefik.http.routers.nitter.rule=Host(`nitter.example.com`)
        - traefik.http.routers.nitter.entrypoints=https
        - traefik.http.services.nitter.loadbalancer.server.port=8080
    networks:
      - internal
      - traefik_public

  redis:
    image: redis:6-alpine
    command: redis-server --save 60 1 --loglevel warning
    volumes:
      - /var/data/nitter/redis:/data
    networks:
      - internal

networks:
  traefik_public:
    external: true
  internal:
    driver: overlay
    ipam:
      config:
        - subnet: 172.16.24.0/24

Serving

Launch Nitter!

Launch the Nitter stack by running docker stack deploy nitter -c <path -to-docker-compose.yml>, then browse to the URL you chose above, and you should be able to start viewing / searching Twitter privately and anonymously!

Now what?

Now that you have a Nitter instance, you could try one of the following ideas:

Setup RSS feeds for users you enjoy following, and read their tweets in your RSS reader
Setup RSS feeds for useful searches, and follow the search results in your RSS reader
Use a browser add-on like "libredirect", to automatically redirect any links from twitter.com to your Nitter instance

Summary

What have we achieved? We have our own instance of Nitter¹, and we can anonymously and privately consume Twitter without being subject to advertising or tracking. We can even consume Twitter content via RSS, and no unhinged billionaires can lock us out of the API!

Chef's notes 📓

Tip your waiter (sponsor) 👏

Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏

Employ your chef (engage) 🤝

Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.

Learn more about working with me here.

Flirt with waiter (subscribe) 💌

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.

Your comments? 💬