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.
> X has documentary evidence that you are scraping X Data, circumventing X’s API access controls and rate limits, accessing X using X accounts and session tokens in violation of X’s rules, and republishing X Data to the public. X’s Terms of Service, Developer Agreement, and Developer Policy strictly forbid such conduct. See https://x.com/en/tos (“[C]rawling or scraping the Services in any form . . . is expressly prohibited.”). By your own description, Nitter “uses Twitter’s unofficial API” and routes all requests through your servers, and requires operators to supply real X accounts to function.
> Your actions constitute a flagrant breach of the contractual and legal obligations you agreed to when accessing the X services. Your actions also violate various state and federal laws, including, but not limited to, the Texas Harmful Access by Computer Act (§ 143.001 and § 33.02) and the Lanham Act (15 U.S.C. §§ 1114, 1125).
Maybe you don't use it very often? For months before the recent chaos it was very reliable. The fact that it's working today is only because I fixed it, Twitter didn't change anything.
Timelines are usually blank, to the point that I have removed it from the rotation of instances in my browser redirector extension. I assumed this was a result of being rate limited by Twitter.
I will admit that since I did remove it from the rotation, I don't see it that often these days, mostly when others link to it and then I navigate to a timeline.
I’ve had timelines/tweets fail to load, but a refresh fixed it quickly. If this was a consistent problem did you consider opening an issue to see if they could improve the website?
It's disabled on nitter.net to reduce load while this new solution is being tested.
Check the instance list for updated instances, most of them have RSS enabled: https://github.com/zedeus/nitter/wiki/Instances
I'm not sure why this is down-voted despite it being posted by what looks like the original developer according to their username: https://github.com/zedeus/nitter
This isn't actually true, the "Instance has been rate limited" error was a false flag. It turned out to be a bug in the API token parser, found and fixed by a contributor. Nitter instances have yet to run into a real rate limit.
Remote: Yes
Willing to relocate: Depends, open to travel
Technologies: Go, TypeScript, Node.js, Deno, Nim, Python, PostgreSQL, Redis, GCP, Docker, Terraform, Caddy, Linux/VPS infrastructure, REST, GraphQL, Shopify, AI/LLMs
Résumé/CV: Can provide via email
Email: [email protected]
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.
reply