Subject:
|
Re: Linking to LUGNET image files?
|
Newsgroups:
|
lugnet.admin.terms
|
Date:
|
Sun, 17 Sep 2000 21:02:14 GMT
|
Viewed:
|
5150 times
|
| |
|
|
[reposted with typo corrections]
In lugnet.admin.terms, Kyle D. Jackson writes:
> G'day Suzanne & Todd,
> This has probably been asked a million times. I couldn't find
> any info in the T.O.S. about it. Anyhow, is it okay to link
> to images on LUGNET, specifically from the sets database, on
> another website? At present this would be for items I want
> to post for sale on BrickBay, ebaY, etc.
If it's from the Partsref, any direct image links to the GIFs are OK (and I
think it specifically says that it's OK there and shows how to write the URL).
If it's from the sets database, there's a mechanism in the server to prevent
embedding of giant images on outside pages. The URLs of that type look like
this:
http://img.lugnet.com/display.cgi?set/.......stuff.......
Don't try to embed those -- you'll get the yellow frowny face.
But if you want to embed the 80x80 thumbnails or 200x200 medium-sized images,
I have no objection to that for auctions and marketplace stuff, as long as
you're not overly excessive or wasteful about it (like putting dozens and
dozens on a single page, etc.) Those URLs don't have the display.cgi part
on them. But they're also not guaranteed to stay working forever because
they have gunky filenames that will probably be reworked sometime.
Another option is to make a popup window like this one:
http://guide.lugnet.com/set/?q=7190&v=z
and launch it via a window.open() call in JS embedded in the <A HREF="...">
But most of all, I would recommend simply linking to the set page like this:
http://guide.lugnet.com/set/7190
and either embedding an 80x80 thumbnail via link or just giving a text link.
You might also want to look around on BrickShelf.com if it's an older set --
IIRC, the direct-image-linkage policy there is that, currently, Kevin doesn't
mind if people do it (I think).
> The source will be credited of course.
In the near-term, actually, I'd rather you didn't. If you're linking to an
HTML page where the image is contained, the origin of the page will be plenty
clear to the reader when the link is clicked. Alternatively, if you're
embedding an image via <IMG> (assuming you have permission), giving some sort
of link back to the origin would be polite.
But in terms of crediting, simply credit LEGO with ownership of the copyright
of the image (see below). And put that as close as possible to the image!
> Actually, that's another question. If
> I can do this, what do you recommend for the image credit?
> Saying "copyright LUGNET" doesn't sit well when it's a TLC
> product. Any advice?
I'd recommend saying something like "Image is Copyright © LEGO Company" or
simply "©LEGO" and place that text as close as possible to the image.
The HTML entity for the copyright symbol is: ©
(Note: If you link to a page in the sets DB on LUGNET, all of that is
automatically taken care of.)
--Todd
p.s. IANAL (I Am Not A Lawyer) and the above is not legal advice -- take it
as friendly experienced general non-legal advice. :-)
|
|
Message has 1 Reply:
 | | Re: Linking to LUGNET image files?
|
| (...) That is absolutely correct. I don't mind direct linking to anything on the website. The bandwidth from direct linking is very small compared with the overall traffic. Specifically, the scan library is a community resource so you should feel (...) (24 years ago, 5-Oct-00, to lugnet.admin.terms)
|
Message is in Reply To:
| | Linking to LUGNET image files?
|
| G'day Suzanne & Todd, This has probably been asked a million times. I couldn't find any info in the T.O.S. about it. Anyhow, is it okay to link to images on LUGNET, specifically from the sets database, on another website? At present this would be (...) (24 years ago, 17-Sep-00, to lugnet.admin.terms)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
