note that this is not related to the specific tweet being linked to; nitter.it is currently sending this HTTP 451 in response to every URL:
(as other comments in this thread have pointed out, the particular tweet in OP’s link is still on twitter and still available via other nitter instances)
note that this is not related to the specific tweet being linked to; nitter.it is currently sending this HTTP 451 in response to every URL:
(as other comments in this thread have pointed out, the particular tweet in OP’s link is still on twitter and still available via other nitter instances)