Open susdos opened 1 year ago
I think it's because of some filter set by the instances.
I have some +18 RSS feeds (just gay porn, nothing of dubious legality like your example) and I noticed that half of them have not been updated for months, the feeds were valid but empty, the content is not visible on the web either. Pretty disgusting that there are no warnings anywhere, I think this is relevant.
I have been cleaning up, for now I have listed (privacydev.net, nitter.cz, poast.org, opnxng.com, ktachibana.party
) as uncensored, and (d420.de, mint.lgbt, x86-64-unknown-linux-gnu.zip, nohost.network, salastil.com, hostux.net, esmailelbob.xyz
) as censored.
In my case I had different results in the censored instances (perhaps different filters or updates) but your example matched in all of them; also on nitter.net, I hope @zedeus can confirm or disprove my guess.
It depends on what country the Nitter server is hosted in, there are no server-side filters.
Thanks for your answer! It is worth mentioning that even if it is an external cause and not intentional or a bug, there is some other variable, as I have checked the list of instances and there are different behaviors in the same country. Or perhaps they simply report a fake country.
Anyway, I will provide some links in case it is useful at any time, using the example of the previous user because it is conveniently very affected (not to open in public, it is a drawing pedo):
France: privacydev ✔️ hostux ❌
USA: ktachibana ✔️ freedit ✔️ salastil ❌ projectsegfau(US) ❌
India: projectsegfau(IN) ✔️ kavin ❌
I have been cleaning up, for now I have listed (
privacydev.net, nitter.cz, poast.org, opnxng.com, ktachibana.party
) as uncensored, and (d420.de, mint.lgbt, x86-64-unknown-linux-gnu.zip, nohost.network, salastil.com, hostux.net, esmailelbob.xyz
) as censored.
Unless you list the accounts you are scraping for us to investigate we can't do anything, there are many accounts that cause jester errors which may be the reason you're getting no data returns. For that matter I turned off my RSS endpoint again because its incompatible with my anti-scraping measures.
I've just run up a private Nitter instance on a server in my living room in Australia and I'm getting this same "tweet not found" error on tweets marked as sensitive. I'm using basic config with no rate-limiting measures or anything. I've done a little bit of testing based on the OP's tweet: Opening it in Twitter while logged in with sensitive media enabled - OK Opening it in Twitter with sensitive media disabled - displays a warning Opening it in a private window (not logged in) - Twitter says the tweet doesn't exist - which is what i assume is happening for me.
I've tested it on the first ten active public instances listed in the wiki plus a few further down the list and most of them will load the tweet but the servers located in Canada and Australia will not.
It depends on what country the Nitter server is hosted in, there are no server-side filters.
Should I take this to mean the issue is somewhere outside my network and there's no fix for it (short of routing through an international VPN or something)?
you can see the photo 1 tweet is viewable. due of new policy make it can't see the photo, so i used nitter to see it and now thats nitter just gives me "not found" but the tweet isn't deleted , why the F is nitter doing. the link is not corrupted.Please make nitter viewable on sensitive content , cuz i don't want to see the thing from below any more