Nitter.net images not embedding on Discord #804
Labels
No labels
accessibility
bug
discussion
documentation
enhancement
feature parity
good first issue
help wanted
question
rss
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
PAS/nitter#804
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.jpgin 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
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.
I've made my bot upload Nitter's image to imgur for now and embed that.
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?
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.
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.178comes up with crawl-35-227-62-178.ptr.discord.com,dig -x 35.196.132.85comes up with crawl-35-196-132-85.ptr.discord.com.Is there any follow up or fix on this subject?