Shitter – A Nitter Fork
A fork of the discontinued Nitter project, “Shitter” aims to keep a privacy‑friendly, read‑only alternative front end for Twitter/X alive, with many self-hosted instances and community-maintained lists and status pages. Commenters explore how such instances are trivially spun up yet frequently taken down, propose load-balancing and multiplexing schemes, and note technical quirks like image loading and tracking protection. Much of the debate centers on whether it is ethical or necessary to keep engaging with Twitter/X—now owned by Elon Musk and widely associated with far-right politics—or to abandon the platform entirely in favor of decentralized or competing networks such as Mastodon and Bluesky.
Project Purpose and Fork Status
- Shitter is a fork of Nitter, an alternative front-end for X/Twitter.
- Original Nitter is described as discontinued; Shitter exists to continue development and instance availability.
- Some commenters criticise the README for not clearly explaining how the fork differs from Nitter or why it was created, suggesting the HN interest is partly due to the name.
Hosting, Instances, and Architecture
- Nitter/Shitter are easy to self-host since the source is public; domain takedowns affect public instances more than the code.
- Running a personal instance is described as trivial, but:
- There is still reliance on X/Twitter authentication.
- Many individual instances would effectively be many X accounts, which can be blocked, leading to a “cat-and-mouse” dynamic.
- Suggestions appear for a load-balancing “multiplexer” that would front many instances, auto-health-check them, and pool accounts. Existing redirectors are mentioned but criticized as too simple and unreliable.
- A separate HN thread is referenced claiming there are more working instances now than before takedowns; a wiki and status page of instances are linked.
Usability and Technical Issues
- A user reports images not loading on some Shitter instances in Firefox but working in Chrome.
- Others explain this is likely due to images not being proxied and Firefox’s enhanced tracking protection blocking X/Twitter resources.
Naming and Branding Reactions
- Many commenters joke about the “Shitter/Xitter” naming and puns on “X”.
- Some wish for a “normal” name but note trademark concerns with using “Twitter.”
Ethical and Political Debate Around X/Twitter
- Strong disagreement over whether there is “no reason” to use or support tools for a platform owned by a “far right” figure versus the practical need to access content still locked into X.
- Some see these front-ends as a way to consume necessary or useful information (including corporate, government, and emergency updates) without directly engaging with X, its ads, or account requirements.
- Others argue for total avoidance, likening X to extremist or Nazi spaces and claiming engagement only fuels attention and propaganda.
- Alternatives (Bluesky, Mastodon, Threads, Lemmy, etc.) are debated:
- Critiques: moderation problems, perceived ideological bias, fragmented policies, and defederation “drama.”
- Defenses: decentralization as a strength; ability to choose communities and policies.
- Broader frustration emerges over social-network fragmentation: multiple competing platforms, incompatible communities, and no clear replacement for Twitter’s former centrality.