Posted by zImPatrick 17 hours ago
The code looks surprisingly easy to hack on: https://github.com/zedeus/nitter/blob/master/src/nitter.nim
"The long-term plan is to rewrite the source code in Go, as I'm no longer interested in using Nim. This isn't a small task, but building more features with the current state of things is painful. Before doing that I'll fix some feature parity issues, and work on some conveniences for instance operators. Stay tuned."
Nitter uses Jester which seems dead for sure, but doing static binaries is easy. Personally I just forked Mummy to continue as MummyNG since I prefer threaded servers so things like JSON parsing doesn’t cause latency issues.
Though that being written over a year ago it’s either not a high priority or harder than it seems. I’ll be curious to see which. LLMs make it easier than ever for others to contribute or to fix up deps.
It's a research project of its BDFL and he is alienating the most senior developers and contributors to Nim's ecosystems (ie Zedeus).
Door 2: improve x.com to be better than third-party sites.
Which is, Elon?
I suspect the original C&Ds were just their legal team wanting to "do something" upon hearing about Nitter somehow, and not Elon personally commanding them.
...and I noticed that X did bring back a (quite) limited JS-free "lite version" recently, so maybe they are changing for the better.
The word "project" doesn't make a clear distinction between the repo and the instances. Nitter is on good ground with respect to the repo. The instances will be much harder to defend. From that one sentence it isn't clear if this is what the legal advice says or not.
Nitter changed their design such that it now requires an X account to scrape through. This was to stay functional after X removed guest accounts. This exposes them to a legal attack through the terms of service that must be accepted for the account, and to technical attack by blocking the scraping accounts.
https://theintercept.com/2022/12/15/elon-musk-leaks-twitter/
Nitter might want to make sure that their scrapes are bit-identical to other accounts to defeat this.