DiscussMormonism.com

Yes, I know this doesn't belong here. I wanted Shades to see it and have a chance to explain/describe what he thinks happened where others can see it so folks understand what happened, too. Is this something the system did? If so, how and why did it? Is this mod action? If so, why?

http://mormondiscussions.com/discuss/viewtopic.php?t=6406&sid=b3d0cf87eb68dc275183368aad74c1c4

Just for clarity, I posted two photos of the same person in a bikini. Both images came from google.com. One photo was X'd out while the other wasn't.

Thanks!

They're both Xed out. Sometimes sites won't let you link to them to view photos. That's probably what happened. Why don't you just find a different picture?

Moniker wrote:They're both Xed out. Sometimes sites won't let you link to them to view photos. That's probably what happened. Why don't you just find a different picture?

They both posted the first time. Do you know why?

No, I don't know why that occurs. Yet, it's happened to me before, as well. It's usually a site that just won't allow you to link. I just go find a different photo and move on. :)

Moniker is somewhat right, but it's a little more pervasive than a site merely disallowing you from image leeching.

To whit, anytime you create a link to a photo that's no longer there, Windows will automatically replace the image with a miniature red "X" on a white background.

For example, let's say I create the following link:

[ img ]http://www.thissitedoesnotexist.com/thisimagedoesnotexist.jpg[ img ]

Guess what shows up?



You linking a picture from Google was half the problem. It often caches images for its index, which remain in place even after the image on the host site is long gone for whatever reason.

So expect lots of red "x"s when you link an image from Google. No need to blame anyone on this site.