Forces must be conspiring against WSTFTD: They're red-Xing the pics.

[Aristus]

I have repaired today's thread. But I wonder if some mutton-headed right-wing hacker is fiddling with the picture links. :tinfoilhat:

[GoddessOfGuinness]

1. WSTFTD?

[Aristus]

2. William Shakespeare's Thought For The Day.

Every couple of weeks, I'll post a pic that'll get zapped soon after. It's very frustrating.

[GoddessOfGuinness]

12. Thank you!

I'm terrible at figuring out which word goes with the letters! :dunce:

[CaliforniaPeggy]

3. That is weird, huh?

So when you initially post the pic, it shows up?

And then later it disappears?

That is truly weird!

Wish you could find out what's happening!


:hug:

[Aristus]

4. Yeah. I always preview a pic before posting the daily thread.

I'm able to avoid *this link contains an illegal code* warnings and so on. Three or four times, I have posted a thread, visible picture and all, only to have it red-X'ed by the middle of the morning. Sometimes a pic comes and goes, as if the site the picture is linked from was taken down by the owner for routine maintenance. But a few pics have disappeared for good, rendering the corresponding post in my journal pretty well incomprehensible. :grr:

[mainegreen]

5. Perhaps your bumping up against your browser cache

or a proxy cache? It would look OK in preview, but once your cache expires, it would try to pull up the image and then fail.

:shrug:

[Aristus]

7. Um...I don't even know what that means.

By 'browser cache' do you mean images that are hosted by Google? How do they expire? Wouldn't the poster of the original image just put it up or take it down as he/she chooses?

[mainegreen]

11. If you view an image directly in your browser first

this will create a 'cache' of that image associated with the images address. So when you post a link to that image in DU your browser will pull that image out of your cache and not from the originating site. However, once that 'cache' of the image expires, either after a certain amount of time or after closing the browser, the next time you try to pull it up the site hosting the image may prevent you from seeing it, especially if that site has monitoring that only allowed pages on that site to pull up images from that site. It's called anti-leeching and is pretty common. It trips me up quite a bit.

[Briarius]

6. perhaps you should copy the picture to your webspace or photobucket

then you're not dependent on someone else's picture hosting and you're not using their bandwidth.

[Aristus]

9. That's a good idea. So once a picture has been copied to my

photobucket account, it can't be zapped even if the original image is taken down by the person who posted it in the first place?

[Briarius]

14. yep

right click on the image you want, save it to your computer and then upload it to photobucket. It won't get zapped and if you accidentally delete it from photobucket you'll still have a copy!

[Call Me Wesley]

8. Open a photobucket account and host your pics there,

instead of remote linking them. So you can be sure no one messes with them. :hi:

[Aristus]

10. Okay, I'll try that from now on. I already have an account with

Photobucket. So I guess I'll start doing that tomorrow.

[rug]

13. Methinks

Something is rotten in the state of Denmark.

Hamlet (I, iv, 90)