HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
zedeus
nitter
Nim2019–2026
zedeus / nitter · Archived

nitter

Alternative Twitter front-end

161Distinct people
200Mentions
3Explicit recommenders
14.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Alternative Twitter front-end

GitHub

Where it is used

The last source check was inconclusive. This does not establish whether a product uses it.

What people are saying

It's a privacy-friendly Twitter mirror (no tracking, no JS, no login required). Highly recommended. Incidentally, 'nitter.net' isn't the only deployment. See here for a long…

arrowsmith used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year200 dated mentions

Observed mentions: 2019-11-14 14:12:28 UTC to 2026-10-23 13:47:03 UTC.

02040602019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 32 mentions; 2 submissions, 30 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 35 mentions; 1 submissions, 34 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 56 mentions; 8 submissions, 48 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 33 mentions; 3 submissions, 30 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 19 mentions; 4 submissions, 15 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC523
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1129
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC32230
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC35134
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC56848
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC33330
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC927
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC19415

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Nitter NoteOn 24 August 2026, cease and desist letters were sent by X Corp. demanding a permanent takedown of Nitter instances and the project's repository. UPDATE 10 October 2026: I'm seeking funding and legal help. See nitter.net for more details. A free and open source alternative Twitter front-end focused on privacy and performance. Inspired by the Invidious project. Features No JavaScript required Zero 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 (instance-specific, often disabled due to abuse) Themes Mobile support (responsive design) AGPLv3 licensed, no proprietary instances permitted Roadmap Embeds (see https://github.com/zedeus/nitter/wiki/Embeds-guide) Account system with timeline support Donations BTC: bc1qpqpzjkcpgluhzf7x9yqe7jfe8gpfm5v08mdr55 ETH: 0x24a0DB59A923B588c7A5EBd0dBDFDD1bCe9c4460 XMR: 42hKayRoEAw4D6G6t8mQHPJHQcXqofjFuVfavqKeNMNUZfeJLJAcNU19i1bGdDvcdN6romiSscWGWJCczFLe9RFhM3d1zpL SOL: FF5bheiD5AqPEdc3eyjymJ8AoMRF1hS78Ht6FiSZZF1t $Nitter: 4fSxCKc91ELQYVdv3tmHW8R15KoALPwEngyoQe1Xpump ZEC: u1vndfqtzyy6qkzhkapxelel7ams38wmfeccu3fdpy2wkuc4erxyjm8ncjhnyg747x6t0kf0faqhh2hxyplgaum08d2wnj4n7cyu9s6zhxkqw2aef4hgd4s6vh5hpqvfken98rg80kgtgn64ff70djy7s8f839z00hwhuzlcggvefhdlyszkvwy3c7yw623vw3rvar6q6evd3xcvveypt Resources The wiki contains a list of instances and browser extensions maintained by the community. Why? It's impossible to use Twitter without JavaScript enabled, and as of 2024 you need to sign up. For privacy-minded folks, preventing JavaScript analytics and IP-based tracking is important, but apart from using a VPN and uBlock/uMatrix, it's impossible. Despite being behind a VPN and using heavy-duty adblockers, you can get accurately tracked with your browser's fingerprint, no JavaScript required. This all became particularly important after Twitter removed the ability for users to control whether their data gets sent to advertisers. 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. Screenshot Installation Dependencies libpcre libsass redis/valkey 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 libsass-dev. Redis is required for caching and in the future for account info. As of 2024 Redis is no longer open source, so using the fork Valkey is recommended. It should be available on most distros as redis or redis-server (Ubuntu/Debian), or valkey/valkey-server. Running it with the default config is fine, Nitter's default config is set to use the default port and localhost. Here's how to create a nitter user, clone the repo, and build the project along with the scss and md files. # useradd -m nitter # su nitter $ git clone https://github.com/zedeus/nitter $ cd nitter $ nimble -l build -d:danger --mm:refc $ nimble -l scss $ nimble -l md $ cp nitter.example.conf nitter.conf 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 ./nitter or using the systemd service below. You should run Nitter behind a reverse proxy such as Nginx or Apache for security and performance reasons. Docker Page for the Docker image: https://hub.docker.com/r/zedeus/nitter 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: cp nitter.example.conf nitter.conf If you're using the prebuilt image without a local clone, download nitter.example.conf and save it as nitter.conf instead. To build and run Nitter in Docker: docker build -t nitter:latest . docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d --network host nitter:latest A prebuilt Docker image is provided as well: 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 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. systemd 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 Logging Nitter currently prints some errors to stdout, and
Read the full README on GitHub

What Hacker News says

33 sources
In what way did what Musk did with Twitter-now-X not work? He bought the platform with the intent to open up the window of allowed discourse to that allowed by the law instead of that demanded by the ideology of the platform owners. This mostly succeeded, the level of censorship on the platform has been radically reduced. You may not like the result because you happened to be ideologically aligned with the previous platform owners but that does not make it invalid, it just means the platform no longer shields you from those who walk different paths. Does this mean X is a good place to frequent? No, it does not, just like Twitter wasn't a good place to frequent. I only ever used Twitter passively and I only ever use X in the same way. I do not post and I have no interest in doing so, I do however like that X now allows different viewpoints
Read the rest
. While I do not like the increased amount of spam, shitposts, crypto scams and other nuisances which came with the opening up of the platform I see this as a temporary problem which can be solved just like spam on email no longer is a problem - I have been self-hosting my mail since the early 90's and saw the rise of spam as well as its current defeat (which may be temporary due to the ascent of generative AI but that is another story for another time) on my own server. So, yes, X mostly works, at least for me. I only use it by following links in articles, I never use the site directly, only through a self-hosted Nitter [1] instance, I do not log in nor do I respond to anything. Maybe things are different for those who live on the platform but... maybe that is not a good thing to do anyway? [1] https://github.com/zedeus/nitter
In And now we see what is possible
Nitter worked by signing in with special "guest accounts" that I think were given to fresh downloads of the mobile apps.[0] Last year, X fully disabled that functionality, which left most Nitter instances broken. At that point, the developer publicly abandoned/ended the project. The couple of instances floating around that still work are, to my knowledge, forks of the original Nitter that have been upgraded to work with a pool of manually created X accounts, which is a relatively expensive and fragile approach that most instances probably aren't up for taking. [0] https://github.com/zedeus/nitter/issues/983#issuecomment-168...
In Show HN: Meet.hn – Meet the Hacker News community in your city
Based on the page source, that's based on Nitter, which is increasingly challenged by recent Twitter developments. From page source: <meta property="og:site_name" content="Nitter" /> Nitter: "Guest accounts have been removed, they weren't just led to believe that. With real accounts getting rate limited immediately and likely banned, I don't see any path forward for Nitter." <https://github.com/zedeus/nitter/issues/983#issuecomment-191...> Via: <https://news.ycombinator.com/item?id=39161194> That said ... for now, yes, that does actually show the relevant image links in context, which is helpful.
In Google Strategy Doc from Antitrust Proceedings
Something went wrong, but don’t fret — let’s give it another shot. Firefox’s Enhanced Tracking Protection (Strict Mode) is known to cause issues on x.com Not to single out twitter because a lot of web sites simply appear as a blank page. The only winning move is not to play. How about a nice game of chess? But if you must: https://github.com/zedeus/nitter/wiki/Instances At the moment, this worked for me: https://xcancel.com/soren_iverson/status/1801253187602788424...
In Please maintain eye contact for the duration of the ad
Don't use Youtube without going through a proxy like Invidious [1] or Newpipe Don't use {site} Search without going through a proxy like SearxNG [2] Don't use TwiXXer without going through a proxy like Nitter - this has gotten more difficult lately but it still works as long as you feed the daemon some registered accounts. Video does not work at the moment but that seems to be fixable. Don't use Reddit without going through a proxy like libreddit [4] Start noticing the pattern? Maybe it is time to start producing promotional posters: The only thing to come between you and ADS could be a proxy / ADS. I'ts just not worth the risk ADS / New rules for a sane net / Sane net protects you, your partner and your community A proxy here and a filter there, ADS nowhere The more you tighten your grip, ${site}, the more viewers will slip through your
Read the rest
In Mobile Ad Blocker Will No Longer Stop YouTube's Ads

Showing the 15 most recent of 33 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.