Another thing I noticed with ipfs cannot load/see files on chrome type browsers unless I have something in my configs that don't make possible to load them ._.
Discussion
I wish we had something better :sad_joshu:
I think it is ipfs.io issue. Also for purposes of thumbnails and link previews the filename parameter does not work the same as if the filename is part of the URL path.
Go check my profile, all of my pictures are on ipfs. Can you see them?
I'm using default settings btw this parameter ?filename= removing manually still won't load, and is not the first time someone says that. I was reading about it and seems that only works if you have domain name.
What I do is redirecting to ipfs.io from my own domain with slightly different URL structure. That seems to work on Nostr quite well and gives me the control to change the target if ipfs.io stops working.
This how it looks on noStrudel and for Amethyst could see it without problems
This is truly odd. IPFS and Nostr seem to be such a good combo... At least on the paper.
Maybe is the browser, I'm just checking with librewolf now and.. 
Yes is blurry according noStrudel default settings without login, but are loading without issues.
So here it works because my URLs are having the image extension directly in the path and not as parameter. That would be the default Nostrudel and Amethyst functionality... The other thing is why it does not work in Chrome. Maybe they are blocking ipfs headers. I will have to test it.
noStrudel wont recolonize a url as an image unless its path ends with a .png, .jpg, or any other image ext. It can see the "filename=" part of the url but it ignores it for now
This was mostly for security reasons, I didn't want to make the app auto load any url since it could easily load a 1GB file only to find out its not an image