nitter
nitter copied to clipboard
zedeus
Nitter.net images not embedding on Discord
Hi there,
I'm having a strange issue on Discord when trying to use a Nitter Image URL such as https://nitter.net/pic/media%2FFqfM3xIXoAINbKM.jpg in a Embed. The image will not appear however any other image jpg from the web works just fine:
Nitter Image Test
A random JPG from Wikipedia
I asked in a development server on Discord and was told
that host may have some sort of hotlink protection or something that prevents the image from being loaded from another host just tried it and it also won't embed, so its an issue with the image or the image host
So I'm just opening this to ask whether that is the case. Thanks.
No idea why this is, another host (nitter.nl) with no unnecessary security headers also won't embed.
As of today, Discord released an Embed Debug tool. Custom instance embeds work fine, however, when debugging why nitter.net images still won't embed using the debug tool, I got this reason from the debugger @zedeus
I guess it's probably due to the IP address/range being blocked by my extensive cloud blocking rules. Any idea which IP(s) they might use to pull embeds?
I guess it's probably due to the IP address/range being blocked by my extensive cloud-blocking rules. Any idea which IP(s) they might use to pull embeds?
Not sure which exact ones. All I know is they use Google Cloud and Cloudflare as far as their infrastructure goes.
That's tricky, I don't want to unban GCP ranges because of all the abuse that comes from them, not sure what to do about this.
That's tricky, I don't want to unban GCP ranges because of all the abuse that comes from them, not sure what to do about this.
If you're talking about DDoS attacks, it might be useful to put nitter.net behind CloudFlare too. If it's something else, you could report it to GCP via their Abuse Report Form. However, I understand how this could be tedious. I guess we could keep this issue open and pin it in that case.
Can you configure your firewall to do a reverse DNS lookup on the connecting address?
In my quick testing, I saw discord crawling from 35.227.62.178 and 35.196.132.85 with UA Mozilla/5.0 (compatible; Discordbot/2.0; +https://discordapp.com).
dig -x 35.227.62.178 comes up with crawl-35-227-62-178.ptr.discord.com, dig -x 35.196.132.85 comes up with crawl-35-196-132-85.ptr.discord.com.
