If you trust the site and are happy for images to be permanently hotlinked, then you could add neo.life to the disabled image download domains to stop Discourse attempting to download them.
Interesting⌠I tried to do what you suggested (adding neo.life to the disabled image download domains), then opened the post and re-saved it , but the problem is still evident.
Do I need the http:// in front of the domain for it to work properly?
To fix an existing post after changing the site setting, youâll have to click the , then âRebuild HTMLâ. I just did that on your post above and itâs looking ok here. Can you try that on your site?
This one looks like it has a slightly different cause. Iâve tracked it down a problem in one of Discourseâs dependencies. Weâre tracking this, and will try to get a fix or workaround in place. Thanks for the report!
We recently fixed some issues oneboxing guardian, eg:
The one from MIT is happening cause they send through a favicon to a missing image. We plan to fix this by simply never rendering these broken chains in oneboxes.