4 ms·

There were some workarounds, most buried in here: https://github.com/zedeus/nitter/issues/983 https://github.com/zedeus/nitter/issues/983

• chatmasta 2y ago
  No need for workarounds. Only the flagship nitter.net was blocked. Nitter is an open source project and maintains a list of working instances on its wiki: https://github.com/zedeus/nitter/wiki/Instances https://github.com/zedeus/nitter/wiki/Instances
  • deleted 2y ago
    [deleted]
  • KTibow 2y ago
    I remember hearing something like "the way Nitter worked, guest accounts, was shut down and the 3 instances that remain work by using selfbotting" a while ago, it's logical although I haven't verified it
    • chatmasta 2y ago
      What’s selfbotting? Based on the name it sounds like something that requires me to surrender my own authentication token to some automation service… but that’s definitely not the case for these alternative Nitter frontends. I’m not sure how Twitter ultimately blocked them. It would be pretty embarassing (for Twitter) if it were a simple IP block of the Nitter.net servers, but that doesn’t seem too out of whack with Musk’s history of litigating bot behavior…