Arg. OK so Jetpack just hates this image in particular. No idea why. I’ve tried reuploading it (twice), and it doesn’t help. But at least the post I put up today doesn’t suffer from the same thing (as far as I can tell).
As for this one, I gave it alt text, so at least you see a link if the image fails to appear. Clicking that should display the image.
I see no image or broken image space marker.
Tried reloading the page but still no image.
If I right-click and “view page source,” I can scroll down till I find the jpg and click that, and the image shows on screen. (This is from the specific post page.)
Not quite sure what the concept here is to be honest. It sounds like someone might be trying to con people into “registering” by an improper method. But some details of their plan escape me.
BTW, is this image displaying OK? I had kind of a weird glitch when I posted it it, and my main browser doesn’t want to show it now, but if I use a different one it displays fine. So I’m hoping it’s just me… but let me know if it’s not showing up.
I’m getting similar results as you. The image fails to appear on Brave (though I can still click it and see it that way), but shows up just fine in other browsers like Firefox, Waterfox, and Chrome.
Well damn. I wish I had any idea what was wrong, I was poking around a little bit in my website settings today, but I don’t think I ultimately changed anything really.
I assumed that the PN Registration Office is actually closed, and this ad was created by somebody who is working there – possibly a security guard – who wants to get a collection of photos of real, amateur women and will intercept the letters before they are seen by returning workers. This feeling is enhanced by the fact that this ad contains the typos recieve and recieving, indicating that it did not go through the full proofreading process.
BTW: I am having definite problems with the picture here. It is not showing up either in the main blog or on this page; however, it shows up correctly if I click to see just the jpg (or select View Image). I have tried reloading both pages multiple times and also tried Restore Image, but nothing works.
I am running Firefox 77.0.1 (64-bit) in Windows 7.
However, a quick check indicates that the blog appears to be working correctly with
Google Chrome Version 83.0.4103.106 (Official Build) (64-bit)
and
Internet Explorer Version: 11.0.9600.19596
So, backstory: I noticed my bandwidth was still pretty high. My host suggested I use CloudFlare, but I’d really rather not, and it seems mostly redundant with JetPack. So I was experimenting with , hotlink protection as an alternative… But I swear I ended up leaving it how it was originally.
Doesn’t make too much sense either. If anything I was afraid I’d break it so JetPack couldn’t see the images, which would presumably make them invisible for everyone, not just certain browsers.
I’m hoping it’s just a one-off glitch, but that’s probably unrealistic. If the same thing happens again, I guess I’ve got some debugging to do tomorrow
Arg. OK so Jetpack just hates this image in particular. No idea why. I’ve tried reuploading it (twice), and it doesn’t help. But at least the post I put up today doesn’t suffer from the same thing (as far as I can tell).
As for this one, I gave it alt text, so at least you see a link if the image fails to appear. Clicking that should display the image.
I don’t see any alt link, either.
So for submitting a cursed image LOL
I see no image or broken image space marker.
Tried reloading the page but still no image.
If I right-click and “view page source,” I can scroll down till I find the jpg and click that, and the image shows on screen. (This is from the specific post page.)
Using the latest FF on Windows 10.
Not quite sure what the concept here is to be honest. It sounds like someone might be trying to con people into “registering” by an improper method. But some details of their plan escape me.
BTW, is this image displaying OK? I had kind of a weird glitch when I posted it it, and my main browser doesn’t want to show it now, but if I use a different one it displays fine. So I’m hoping it’s just me… but let me know if it’s not showing up.
Image looks just fine here…
I’m getting similar results as you. The image fails to appear on Brave (though I can still click it and see it that way), but shows up just fine in other browsers like Firefox, Waterfox, and Chrome.
Well damn. I wish I had any idea what was wrong, I was poking around a little bit in my website settings today, but I don’t think I ultimately changed anything really.
not showing on Edge either
I assumed that the PN Registration Office is actually closed, and this ad was created by somebody who is working there – possibly a security guard – who wants to get a collection of photos of real, amateur women and will intercept the letters before they are seen by returning workers. This feeling is enhanced by the fact that this ad contains the typos recieve and recieving, indicating that it did not go through the full proofreading process.
BTW: I am having definite problems with the picture here. It is not showing up either in the main blog or on this page; however, it shows up correctly if I click to see just the jpg (or select View Image). I have tried reloading both pages multiple times and also tried Restore Image, but nothing works.
I am running Firefox 77.0.1 (64-bit) in Windows 7.
However, a quick check indicates that the blog appears to be working correctly with
Google Chrome Version 83.0.4103.106 (Official Build) (64-bit)
and
Internet Explorer Version: 11.0.9600.19596
So, backstory: I noticed my bandwidth was still pretty high. My host suggested I use CloudFlare, but I’d really rather not, and it seems mostly redundant with JetPack. So I was experimenting with , hotlink protection as an alternative… But I swear I ended up leaving it how it was originally.
Doesn’t make too much sense either. If anything I was afraid I’d break it so JetPack couldn’t see the images, which would presumably make them invisible for everyone, not just certain browsers.
I’m hoping it’s just a one-off glitch, but that’s probably unrealistic. If the same thing happens again, I guess I’ve got some debugging to do tomorrow