I'm a senior software engineer with 8 years of experience, primarily focused on backend development, systems architecture, web scraping/reverse engineering, performance optimization, and infrastructure. I work best in small teams where I can operate autonomously and take ownership of difficult problems end-to-end.
I'm the developer of Nitter (https://github.com/zedeus/nitter), an open-source alternative frontend for X/Twitter that I developed and operated for 7 years. At its peak it served millions of users and had a large community around it. I maintained it through major changes to X's infrastructure, including reverse engineering, API usage, caching, performance optimization, anti-bot/WAF systems, and production infrastructure. It was ultimately shut down following legal threats from X.
Outside of Nitter, I've worked on internal logistics systems, APIs and integrations, cloud infrastructure, automation, and various other backend systems. I'm particularly interested in difficult technical problems where I can have substantial ownership, whether that's backend/infrastructure, data acquisition and scraping, developer tooling, or AI-related systems.
I'm anonymous here because of the nature of Nitter and the legal situation surrounding it. I'm happy to verify my identity privately and can provide my CV and additional details by email. Anonymity would not be a requirement after employment.
I'm open to full-time employment or contract work.
The repo being archived happened after that UPDATE post that you mention. So the project has gone from suspended, to un-suspended, and now it's suspended again (and the repo got archived this time).
Edit: I see I'm being downvoted for just providing facts, so here's some evidence: you can see on the main project page that the repo was archived on 11 Sep[0]. Looking in the commits, the "UPDATE" message was commited on 6 Sep[1].
There's plenty of other instances running on nitter, some secret/invite only (and as such more chance to fly under the radar). The code is open source: https://github.com/zedeus/nitter albeit X DMCA'd the repo.
Nitter's author has suggested at least once that due to problems with Nim, a rewrite in Go is in the works:
"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."
Cool to see such a notable Nim based project continue! It's unfortunate that X tries to block Nitter so often, but zedeus always seems to find a path around technical or now legal issues.
From HN's PoV, the issue is that there aren't well-known workarounds which can be used for X.com / Twitter.com submissions. HN's principle concern is more that any discussion on such posts will largely revolve around the regwall / paywall, which doesn't advance HN's own prime directive: <https://news.ycombinator.com/item?id=27901918>
Every individual running their own instance would be the equivalent of every individual having their own Twitter account, which defeats the purpose.