Nitter: Update Oct 10th seeking funding and legal help

Original Article ↗ Hacker News Discussion ↗

An open-source project called Nitter, which provides a privacy-friendly, account-free front end to X (formerly Twitter), is seeking funding and legal support after receiving cease-and-desist threats from X. Commenters debate whether such a service can operate legally given X’s terms of service, API restrictions, and potential CFAA or copyright issues, with some arguing it’s akin to an ad blocker or proxy for user-owned content and others seeing it as clear contract violation. The exchange highlights broader tensions over who controls access to social media “public squares,” the role of terms of service as de facto law, and whether civil-disobedience-style tools like Nitter deserve financial and legal backing.

Purpose and Value of Nitter

  • Described as a free, open-source alternative front-end for X/Twitter.
  • Lets people read public posts without an account, ads, tracking, or running X’s JavaScript.
  • Seen as useful because journalists, executives, governments, and other “important” actors still post there, sometimes exclusively.
  • For some, Nitter is the only way they’ll open an X link; they refuse to create an account but still want primary sources.

Funding, Sustainability, and VC Talk

  • Skepticism that users will donate enough; bystander effect and expectation of free use.
  • Some suggest VC money, but others say there’s no real monetization path and massive legal risk, so it’s unlikely.
  • One commenter claims to have made a large crypto donation, indicating at least some serious financial support.

Legality and Terms of Service

  • Major disagreement:
    • One side: Nitter is essentially an unauthorized proxy/scraping mirror; violates ToS, possibly CFAA; cannot be run legally and has “no case”.
    • Other side: X doesn’t own most of the content, only a license; user-generated content vs NYT/CNN-style first-party content matters; legal situation “complicated” and Nitter may be in a strong position.
  • Debate over whether ToS are real contracts, how clickwrap works, and whether violating ToS is “illegal” vs just creating civil liability.
  • Questions about copyright standing if X adds exclusive content programs.
  • Some think EFF/FSF’s absence signals weak legal prospects; others note they have limited resources.

Ethics, Public Square, and Civil Disobedience

  • Many see Nitter as akin to ad blocking: a user-agent choice, morally fine, especially when governments or public institutions use X as a primary channel.
  • Others argue X needs revenue, bypassing it is wrong, and “don’t use it” is the correct stance.
  • Strong disagreement about whether private platforms acting as “town squares” should be regulated as utilities or left alone.
  • Some frame supporting Nitter as resistance to an abusive platform owner; others call that reckless and unfairly risky for the maintainer.

Technical and Operational Notes

  • Nitter currently works by using authenticated sessions/accounts on the server side; essentially a proxy.
  • Suggestions to harden it “like Pirate Bay”: many fronting servers, rotating domains, hydra-style proliferation.
  • Some worry domain seizures and convenience loss would still kill user adoption.