0xpr03 / nitter-status Goto Github PK

I noticed that my instance is shooting up the list because I use a fork that I've updated after the latest official release.

Points for the version should probably cap at the official latest commit so forks don't get extra points for being based off a commit that took place later.

over the last several days, we have worked together to identify ways to limit scraping on nitter instances. one of which is to prevent http/1.0 and http/1.1 access to nitter.poast.org. because your status page does not honor the upgrade offered by the webserver, it's returned as offline but it's very much online, just refusing http/1.0 and http/1.1 connections

According to Nitter Instance Uptime & Health right now

An extra "Latest commit" or similar column with a checkmark showing whether the instance is running the latest commit from master

Similar to how it is on Nitter's about page, the version text should link to its commit which can easily be parsed from the same HTML element