it’s not just lemmy; HTTPS websites aren’t allowed to serve HTTP content
developer.mozilla.org/en-US/docs/…/Mixed_content
Comment on Welp, guess I'm going to hell
xusontha@ls.buckodr.ink 1 year agoI already fixed it, but I didn’t know that! That’s really cool!
mounderfod@lemmy.sdf.org 1 year ago
user224@lemmy.sdf.org 1 year ago
Sorry, my bad. And thanks for the info.
mounderfod@lemmy.sdf.org 1 year ago
No worries, I find the intricacies of protocols like this super interesting 😊
user224@lemmy.sdf.org 1 year ago
You can also embed images inside links, by the way (click the button):
Get Firefox
[![Get Firefox](https://i.imgur.com/KpmYhB1.gif)](https://getfirefox.com)
Also if say you have image/animation/audio/video link without extension (e.g.: .jpg), you can fool Lemmy using a fragment identifier at the end of URL
#.jpg
which would usually be used to jump to the fragment id in document. e.g.:https://example.org/image#.jpg
xusontha@ls.buckodr.ink 1 year ago
Wowzers that’s fancy, I’ll have to save that for the future
x4740N@lemmy.world 1 year ago
Now I’m wondering if someone in bad faith could link an tracking image and just rip ip addressees in the background
I guess it depends on if lemmy clients query the link of the embedded image or just grab a cached version from lemmy
user224@lemmy.sdf.org 1 year ago
Images in comments don’t get cached, so absolutely yes. But I mean, public IP + User Agent is like minimum of information anyway. Any website you visit gets it.