💾 Archived View for wilw.capsule.town › notes › nitter.gmi captured on 2024-05-10 at 11:03:02. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-04-19)
-=-=-=-=-=-=-
When browsing Twitter [1], I use a self-hosted Nitter [2] instance. Nitter allows you to browse Twitter using a more privacy-respecting front-end.
To run Nitter, create a `docker-compose.yml`:
version: "3" services: nitter: image: zedeus/nitter:latest ports: - "8085:8080" volumes: - ./nitter.conf:/src/nitter.conf:ro depends_on: - nitter-redis restart: unless-stopped nitter-redis: image: redis:6-alpine command: redis-server --save 60 1 --loglevel warning volumes: - ./nitter-redis:/data restart: unless-stopped
Simply bring up the service, navigate to the IP address or domain, and get started.
I run Nitter in my Tailscale network and so do not bother with TLS certificates. If needed, I recommend using Traefik [3] to manage and provision the certificates.