Posted on 01/01/2013 9:31:56 AM PST by ShadowAce
You in old school...
We in new school...
AAAAAARRRRRRGHH!
I see yer timbers be shiverin’!
Thanks. Will check it out. Looks good.
I’m trying to post a photo. I usually don’t have problems, but I had to post the photo on Flickr to get the URL. But I can’t post it on Free Republic. Can anyone open this link and advise me how to post the photo myself? Thank you. Here’s a link:
http://www.flickr.com/photos/99613645@N02/9407286838/
The code is:
<img border=0 src="http://farm4.staticflickr.com/3727/9407286838_dc85246cef_b.jpg">
Flickr doesn't want you posting its sacred content. So, they put barriers in place to keep you from discovering the URL of the images. Such as trapping right-clicks. But, obviously, you see the image in your browser. So, your browser obviously knows the URL ... You just need to find out what your browser downloaded!
E.g., on Firefox, you can right-click on the page, and select Page Info and look through the Media tab until you find the image.
Or, on Chrome, you can right-click and select Inspect Element and select the Resources tab and drill down through the images until you come to the right one. Or you can browse the document tree until you find the proper image element.
Once you've got the actual URL to the image itself (as opposed to the page hosting the image), it's simple to make an image tag, as above.
Still had some problems. I followed your code, but I think you mentioned something about right clicking.
I just noticed you had the correct URL and I didn’t. I’m clueless, how can I find the correct URL address?
<img src="http://www.flickr.com/photos/99613645@N02/9407286838/" border="0">
That URL won't work in an IMG element. That's the URL to the page, the front door, if you will, on which the image is posted. You want the URL of the image itself! Which is contained within the page.
When a site doesn't want you copying (e.g., Flickr or Snopes), the key is to reverse-engineer the page to see how it's actually built.
Both Chrome and Firefox have good reverse-engineering tooling. You just need to get familiar with it.
E.g., on Chrome, you can do ⌘-Shift-J. This will land you on the Developer Tools window looking at the JavaScript Console (the last tab over). Click the Resources tab and see a list of all the stuff downloaded to make up the page. At the top will be a Frames folder. Opening this, you can drill down and find Images folders and browse those to find the image in question.
Or, alternatively, you can click the Elements tab. Here you can inspect the document tree and see how the page is constructed, element within element. It helps to have two monitors Inspector in one, page in the other. If you see an interesting image URL, you can click it in the Inspector and see the actual image to which it resolves. If it's the right one, copy its URL, and paste into your FR post.
The way the Chrome Inspector is supposed to work is, you right-click the element on the page that interests you and select Inspector. That lands you in the document tree open to the element of interest (or close). However, if the page has been hacked ala Flickr or Snopes, they will have replaced the right-click menu. So, that doesn't work. However, bringing up the JavaScript Console still does, and you can get to where you need from there!
Here’s the related link.
Correction: ⌘-Alt-J.
The menu item is View|Developer|JavaScript Console or Tools|JavaScript Console (Shift-Ctrl-J on Ubuntu).
.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.