Unless that’s a disguised redirect link, I’m wondering if the server somehow mistakenly hosted it here. Or possibly the image was already hosted on Lemm.ee, and the server software decided to list the match link rather than the new one you provided.
If it sounds like I’m trying to make something out of nothing, I’m just concerned that there might be an image loophole attackers might use, as with what happened to Lemmy.World some weeks back.
It is interesting indeed. This particular image has not been hosted on lemm.ee before, as I’m the one who uploaded it to pixelfed.social, and linked to it in the post. The server does seem to host a shrunk down version of it (the thumbnail is https://lemm.ee/pictrs/image/5fdd577a-609b-409c-8811-ff59a0443f1b.webp?format=webp&thumbnail=256). If you remove the thumbnail part of the query string, you get a full-size image, but a much smaller size than the original hosted on pixelfed.
This particular image has not been hosted on lemm.ee before, as I’m the one who uploaded it to pixelfed.social
I’m guessing that means you’re also the image creator, otherwise you wouldn’t be sure nobody had uploaded it here before, right?
In any case, my first thought would be to try to do a test, replicating the event to see if the same thing happens again. Unfortunately, it looks like pixelfed.social is closed to new accts, so I suppose it would need to be someone already with an acct there. Feel like giving that a whack?
If so, there’s a junk community here that would make for a good testing ground. I just whipped up a test image with the same dimensions as yours, and right about the same size here.
if it’s not convenient for you to do a test at this time, maybe you could clue me in as to how to make a pixelfed.social acct?
Thanks, interesting. I’m not sure what’s happening, but it also seems to be hosted right here, scaled down 50k: https://lemm.ee/pictrs/image/5fdd577a-609b-409c-8811-ff59a0443f1b.webp
Unless that’s a disguised redirect link, I’m wondering if the server somehow mistakenly hosted it here. Or possibly the image was already hosted on Lemm.ee, and the server software decided to list the match link rather than the new one you provided.
If it sounds like I’m trying to make something out of nothing, I’m just concerned that there might be an image loophole attackers might use, as with what happened to Lemmy.World some weeks back.
It is interesting indeed. This particular image has not been hosted on lemm.ee before, as I’m the one who uploaded it to pixelfed.social, and linked to it in the post. The server does seem to host a shrunk down version of it (the thumbnail is https://lemm.ee/pictrs/image/5fdd577a-609b-409c-8811-ff59a0443f1b.webp?format=webp&thumbnail=256). If you remove the thumbnail part of the query string, you get a full-size image, but a much smaller size than the original hosted on pixelfed.
I’m guessing that means you’re also the image creator, otherwise you wouldn’t be sure nobody had uploaded it here before, right?
In any case, my first thought would be to try to do a test, replicating the event to see if the same thing happens again. Unfortunately, it looks like pixelfed.social is closed to new accts, so I suppose it would need to be someone already with an acct there. Feel like giving that a whack?
If so, there’s a junk community here that would make for a good testing ground. I just whipped up a test image with the same dimensions as yours, and right about the same size here.
if it’s not convenient for you to do a test at this time, maybe you could clue me in as to how to make a pixelfed.social acct?