--- title: Nitter, XCancel Shutdown Over Cease-And-Desist | daily.dev description: Nitter is a free, open source, privacy-focused alternative front-end for Twitter, requiring no JavaScript and routing all requests through a backend to prevent... canonical: https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Nitter, XCancel Shutdown Over Cease-And-Desist | daily.dev og:description: Nitter is a free, open source, privacy-focused alternative front-end for Twitter, requiring no JavaScript and routing all requests through a backend to prevent... og:url: https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy og:image: https://api.daily.dev/og/posts/4KEASvwOy.png og:image:alt: Nitter, XCancel Shutdown Over Cease-And-Desist og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Nitter, XCancel Shutdown Over Cease-And-Desist **[Lobsters](https://daily.dev/sources/lobsters)** · 5 min read · 0 upvotes · 0 comments ## Summary Nitter is a free, open source, privacy-focused alternative front-end for Twitter, requiring no JavaScript and routing all requests through a backend to prevent tracking. It is lighter and faster than the official site. However, a notice states that on 24 August 2026 X Corp. sent cease and desist letters demanding a permanent takedown of Nitter instances and the project's repository. The page also covers installation via source build, Docker (multi-arch amd64/arm64), and systemd, along with donation options and roadmap items like an account system and archiving. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did X Corp send cease and desist letters to Nitter in August 2026? X Corp sent cease and desist letters on 24 August 2026 demanding a permanent takedown of Nitter instances and the project's repository itself. Nitter is an open source, privacy-focused alternative Twitter front-end that scrapes Twitter's unofficial API without a developer account, avoids JavaScript and ads, and is roughly 15 times lighter than twitter.com. _Anyone tracking the fate of self-hosted privacy tools like Nitter can follow updates on daily.dev._ ### How do you run Nitter with Docker and Redis? Nitter requires Redis (or the Valkey fork, since Redis is no longer open source) running separately, plus a nitter.conf file copied from nitter.example.conf before starting the container. The published zedeus/nitter:latest image is multi-arch, running natively on amd64 and arm64, and can be run standalone with docker run or alongside Redis via docker-compose by setting redisHost to nitter-redis. _Developers setting up self-hosted services like Nitter can track deployment tips on daily.dev._ ### Why is Nitter lighter and faster than the official Twitter website? Nitter serves pages using around 60KB of data compared to 784KB from twitter.com for the same profile, making it roughly 15 times lighter on average, with timelines loading 2-4x faster. It achieves this by avoiding JavaScript and ads entirely, and by having the backend handle all requests to Twitter's unofficial API so the client never talks to Twitter directly. _Those comparing privacy-respecting front-ends against bloated official sites can dig deeper on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 6 discussions and 181 comments across lobsters, hackernews (as of 2026-08-29). **TL;DR:** Reactions are split between nostalgia for Nitter as a fast, private, ad-free way to read Twitter without an account, and some indifference or even satisfaction that a platform many see as a 'cesspool' loses a workaround; most substantive discussion is archival, focused on how Nitter worked technically rather than mourning its loss. **Sentiment:** 30% positive · 45% mixed · 25% skeptical **The case for** - Valued for being lightweight, ad-free, JS-free, and not requiring a Twitter account to read content. - Useful for RSS feeds and following accounts without algorithmic clutter. - Seen as good open-source engineering (Nim-based, tiny Docker footprint, simple to self-host). - Supported adversarial interoperability and reduced Twitter's tracking/reach. **The pushback** - Some feel losing Nitter is a net win since it forces more people off Twitter entirely. - Relied on scraping/guest-token tricks that were always fragile and vulnerable to being cut off. - Concerns about instance rate limiting and the sustainability of public mirrors. - Losing tools like this is viewed as a broader loss for interoperability and open access, even by people who dislike Twitter. **By community** - lobsters (mixed): Some welcome the shutdown as reducing Twitter's reach, while others mourn it as a loss for adversarial interoperability. - hackernews (mixed): Long-running threads mix nostalgia and technical appreciation for Nitter with side discussions on alternatives, redirect extensions, and its scraping-based fragility. **Hottest debate:** Whether losing Nitter is actually bad, since some see it as a tool that extended Twitter's reach while others value it purely as user-empowering interoperability. **Open questions** - Will any alternative front-end or bridge (e.g., Fediverse mirrors) emerge to replace Nitter's functionality? - How was Nitter's unofficial API/guest-token access sustained for so long, and why wasn't it cut off sooner? **Highlights** > as much as i appreciated these resources, good riddance. Twitter is a cesspool and if they want to force people to log in to view stuff that’s fine by me, anything that even marginally reduces the platform’s reach is good. > — [jkachmar on lobsters · 7 points, 2 comments](https://lobste.rs/s/zfhall/nitter_xcancel_shutdown_over_cease#c_iplfuv) > A loss for adversarial interoperability is a loss. Yeah, twitter sucks, but it sees this as a win. > — [landon on lobsters · 1 points](https://lobste.rs/s/zfhall/nitter_xcancel_shutdown_over_cease#c_g9htsj) > When Nitter first came around, it was incredible. It really goes to show just how easy it would be for Twitter to provide a fast and accessible version of their site if that was their goal. Too bad it isn’t and Nitter instances will forever run into rate limiting. > — [jchw on hackernews · 5 comments](https://news.ycombinator.com/item?id=28294976) > Where does the authorization token come from? I notice it appears in quite a few projects on e.g. GitHub. https://github.com/zedeus/nitter/blob/8836cf51e8a6b385e1ac0a... The project is cool. The de-crapified interface is nice (no weird JavaScript loading, no nags to login, t.co). But that also makes me think that the hosted version (nitter.net) is pretty doomed, since it directly undermines Twitter commercially. > — [regecks on hackernews · 1 comments](https://news.ycombinator.com/item?id=21850045) **Source threads** - [lobsters](https://lobste.rs/s/zfhall/nitter_xcancel_shutdown_over_cease) · 23 points · 3 comments - [hackernews](https://news.ycombinator.com/item?id=28294099) · 274 points · 100 comments - [hackernews](https://news.ycombinator.com/item?id=21849744) · 195 points · 76 comments - [hackernews](https://news.ycombinator.com/item?id=33782722) · 9 points · 0 comments - [hackernews](https://news.ycombinator.com/item?id=35955394) · 7 points · 0 comments - [hackernews](https://news.ycombinator.com/item?id=21535453) · 5 points · 2 comments --- Tags: [#privacy](https://daily.dev/tags/privacy), [#twitter](https://daily.dev/tags/twitter) [View this post on daily.dev](https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Nitter, XCancel Shutdown Over Cease-And-Desist","url":"https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy"},"datePublished":"2026-08-28T09:08:54.698Z","dateModified":"2026-08-29T00:28:43.103Z","description":"Nitter is a free, open source, privacy-focused alternative front-end for Twitter, requiring no JavaScript and routing all requests through a backend to prevent...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c6f49c43204fc504e5fb8c3b7c676443?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c6f49c43204fc504e5fb8c3b7c676443?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"privacy,twitter","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Nitter, XCancel Shutdown Over Cease-And-Desist"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/nitter-xcancel-shutdown-over-cease-and-desist-4keasvwoy#faq","mainEntity":[{"@type":"Question","name":"Why did X Corp send cease and desist letters to Nitter in August 2026?","acceptedAnswer":{"@type":"Answer","text":"X Corp sent cease and desist letters on 24 August 2026 demanding a permanent takedown of Nitter instances and the project's repository itself. Nitter is an open source, privacy-focused alternative Twitter front-end that scrapes Twitter's unofficial API without a developer account, avoids JavaScript and ads, and is roughly 15 times lighter than twitter.com. Anyone tracking the fate of self-hosted privacy tools like Nitter can follow updates on daily.dev."}},{"@type":"Question","name":"How do you run Nitter with Docker and Redis?","acceptedAnswer":{"@type":"Answer","text":"Nitter requires Redis (or the Valkey fork, since Redis is no longer open source) running separately, plus a nitter.conf file copied from nitter.example.conf before starting the container. The published zedeus/nitter:latest image is multi-arch, running natively on amd64 and arm64, and can be run standalone with docker run or alongside Redis via docker-compose by setting redisHost to nitter-redis. Developers setting up self-hosted services like Nitter can track deployment tips on daily.dev."}},{"@type":"Question","name":"Why is Nitter lighter and faster than the official Twitter website?","acceptedAnswer":{"@type":"Answer","text":"Nitter serves pages using around 60KB of data compared to 784KB from twitter.com for the same profile, making it roughly 15 times lighter on average, with timelines loading 2-4x faster. It achieves this by avoiding JavaScript and ads entirely, and by having the backend handle all requests to Twitter's unofficial API so the client never talks to Twitter directly. Those comparing privacy-respecting front-ends against bloated official sites can dig deeper on daily.dev."}}]} ```