It's gotta be up there in the rarer status codes. Normally they'd just take it down or redirect it. There's really no reason to use 451 except as a way to obey the law passive aggressively.
It's not really an official code integrated into the RFC, it just exists as a proposal.
That said, the code starts with 4, so all browsers will recognize it as the same group of errors of "You're not getting data, sorry chummer." And while not official, the Firefox source code does have it as part of their explicitly called out status codes, so it could be argued that, at least in practice, it's already part of the standard.
It's a really silly status code, though, because now you have a web server / system making legal claims and most probably was not emitted by direct request of a lawyer to make a public statement. Also, 4 is supposed to be for client errors but here the client didn't actually do anything wrong in the request (and certainly has nothing it could possibly do to address it). It's probably better suited as a 5, where the server failed to serve.
One can install LibRedirect and in the options in the Twitter redirects page you can see all the different Nitter instances and it also says which ones use cloudflare. Just untick those for added privacy and to avoid this issue.
Nitter is an alternative front-end for Twitter; it can only load content on Twitter's servers for the user. It gained popularity because Twitter was overwhelmingly shit near the end.
I use nitter because if you scroll Twitter more than 2 pixels without being logged in it shits a giant pop-up onto your screen and doesn't let you proceed. I'm never making a Twitter account, fuck off.
It's a cry for help.
Never heard that code before.
It's gotta be up there in the rarer status codes. Normally they'd just take it down or redirect it. There's really no reason to use 451 except as a way to obey the law passive aggressively.
It's not really an official code integrated into the RFC, it just exists as a proposal.
That said, the code starts with 4, so all browsers will recognize it as the same group of errors of "You're not getting data, sorry chummer." And while not official, the Firefox source code does have it as part of their explicitly called out status codes, so it could be argued that, at least in practice, it's already part of the standard.
It's a really silly status code, though, because now you have a web server / system making legal claims and most probably was not emitted by direct request of a lawyer to make a public statement. Also, 4 is supposed to be for client errors but here the client didn't actually do anything wrong in the request (and certainly has nothing it could possibly do to address it). It's probably better suited as a 5, where the server failed to serve.
That sounds more like something caused by nitter.it's hoster, domain provider, Cloudflare, etc.
Found this report about some other service having a similar issue and it appears to be Cloudflare's fault: https://news.ycombinator.com/item?id=33667236
One can install LibRedirect and in the options in the Twitter redirects page you can see all the different Nitter instances and it also says which ones use cloudflare. Just untick those for added privacy and to avoid this issue.
Nitter is an alternative front-end for Twitter; it can only load content on Twitter's servers for the user. It gained popularity because Twitter was overwhelmingly shit near the end.
I use nitter because if you scroll Twitter more than 2 pixels without being logged in it shits a giant pop-up onto your screen and doesn't let you proceed. I'm never making a Twitter account, fuck off.
Not a word of it on github. Maybe some instance admin soyboys are protesting Twitter enforcing bans on CP.
List of nitter servers working. The major ones are down. And .net isn't working properly.