zedeus/nitter

Alternative Twitter front-end

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 23rd, 2026
Created on June 20th, 2019
Open Issues & Pull Requests: 153 (+0)
GitHub issues: Enabled
Number of forks: 1,369
Total Stargazers: 14,488 (+1)
Total Subscribers: 180 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.4 hours
Mean response time: 88.4 days
90th percentile: 241.7 days
Tracked items: 271

How this project is maintained

About 13% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "enhancement" is answered fastest, typically in about 2 days, while "feature parity" waits about 8 weeks. 80% of issues opened in the past year have been closed, leaving a working backlog. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 41
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 600 days
Stale 30+ days: 38
Stale 90+ days: 32

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (45)
  • bug (22)
  • feature parity (16)
  • rss (9)
  • help wanted (7)
  • discussion (2)
  • documentation (2)
  • accessibility (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Nitter is an alternative Twitter front-end focused on privacy and performance.

Nitter solves the problem of tracking and surveillance on Twitter by providing a privacy-respecting interface that requires no JavaScript, blocks ads, and routes all requests through a backend server so Twitter cannot track your IP address or browser fingerprint. The tool uses Twitter's unofficial API, eliminating the need for a developer account, and delivers pages significantly faster than the official site while consuming roughly fifteen times less bandwidth.

The project suits privacy-conscious users who want to browse Twitter without JavaScript execution or account creation, and those on bandwidth-constrained connections. Self-hosting an instance on a VPS is the intended deployment model. The tool is particularly valuable for users already employing VPNs and ad blockers who recognize that browser fingerprinting can still enable tracking despite those protections. A planned account system will eventually allow following users and building chronological timelines without a Twitter account. The README does not compare Nitter to other Twitter clients or front-ends.

The project maintains active development with ongoing feature work and community contributions. The tool has weathered significant external pressure, including legal action, yet continues operation and development. The codebase is written in Nim and requires compilation with dependencies including libpcre, libsass, and Redis or Valkey. Community members actively maintain a wiki documenting available instances and browser extensions for routing traffic through Nitter automatically.