Someone clicks a link to a public post on X, hits the login wall, and pastes the URL into xcancel.com instead. On Monday that worked again [5]. Every request goes through Nitter's own backend, so X never sees the reader's address or browser fingerprint, and there is nothing to log into and no way to post [11][12]. What Nitter takes away is the tracking and the account requirement on posts that are already public, which are the parts X monetises [13].
So count what the letter bought. The letters went out on 24 August [9]. The notice appeared two weeks later, on a Monday [1], and by the Tuesday the repository was publicly accessible with no archive notice [6]. That is roughly 15 days [22], and read-only rather than removed, because archiving a repository freezes it instead of deleting it [7].
A platform's legal file records only that the demand was made and the project went dark. The actual events were narrower: one maintainer stopped hosting, a single repository lost write access, and the best-known third-party instance came back first.
What has actually been closing Nitter instances is the platform's unofficial API, not the letters. Nitter reads X through it, X keeps changing it, so each round of restrictions forces a rebuild [14], and the operators of public instances, not the maintainer, carry most of that cost, which is why the count of working instances has been falling for years independent of any letter [15]. Reader numbers do not exist in any of this. The only quantity anyone can trend is the supply side, the instances still answering, and it points down [23]. The counterparty to X Corp's lawyers is a pseudonymous maintainer with a donations page [21].
Since zedeus has not said what the advice was [1], TNW offers the wider legal weather as context rather than explanation: in July a US court dismissed Google's DMCA claims against SerpApi, a company built on scraping Google's own results [16], and Oxylabs raised $130mn from Warburg Pincus in July at a $3.6bn valuation on the premise that gathering public web data at scale is a legitimate business [17]. The Register, which reported the reversal, asked X for comment and had no response [4]. A cease-and-desist letter is a demand rather than a judgment, and X has not sued [18].
For any team depending on someone else's access to platform content, two measurements sort the risk, and they fail in different ways. First, how long access actually stops when a letter reaches the party you depend on: here, about 15 days [22]. Second, who funds the rebuild when the platform changes an undocumented interface: here, unpaid instance operators [15]. A dependency that is cheap on the first measure and expensive on the second stops being maintained one operator at a time, rather than dying in court. The figure worth carrying in a continuity plan is the cost of the rebuild you would otherwise be waiting on a volunteer to finish.
