GoFuckYourself.com - Adult Webmaster Forum - View Single Post - Why hotlinking is perfectly legal for 2257

Pipeline Q · 06-22-2005, 10:22 PM

ORIGINAL QUESTION-----
[Note that this has nothing to do with illegal bandwidth theft.]

The basic question is this; Considering the inner workings of the internet, if Domain A hotlinks to images on Domain B, is Domain A considered the "publisher" of those images served and owned by Domain B once they load into the browser?

Real life analagy... A newspaper instead of printing a photo leaves a blank space that reads, "Go to 12 Main Street and get their photo of the bird and glue it here." Once that photo is glued on, the newspaper certainly isn't the publisher of it even if they instructed it to be placed there.

Can this translate into internet hotlinking terms?

RESPONSE 1------
Sounds like a legal question to me, but if I were to guess I'd say that the owner of the server space that serves up the file is the publisher.

RESPONSE 2-----
The entity responsible for sending the data to the browser is the publisher regardless of whose webpage it appears on.
Webpages are not marked by resemblance to PDF files or the like in that what appears on the screen is not contained and served in a single file. It is remarkably unremarkable that a single webpage have multiple publishers.

Illustrations of this include third party content services that webmasters may deploy such as stock tickers, ad agencies and RSS feeds. The approved direct linking (i.e., hotlinking) of images also falls into this "third party content services" category.

Since you asked for a technical explanation as to why this is, here it is in simplified terms.

1) Browser submits request for source code file from server.
2) Server grants request and sends source file to browser containing page layout and recommended content information.*

* Any content that a source file directly contains or links to is considered recommended since it's display is ultimately the decision of the user or browser.

3) Browser processes source code and renders initial layout (e.g., tables) including textual content within the source file.

The role of the main webpage ends herein even though direct links have yet to be requested, granted/denied or processed.

4) Browser requests image data from image server.
5) Image server grants request and sends image data to the browser.

To be considered the publisher of any data, you must be the entity receiving the request from the browser, making the decision to grant or deny the request and finally the one to send the data.

Throughout this process the main webpage did not take part in any of those three events. So we conclude that they can not be the publisher of the images.

However, this is dependent upon no contractual agreement being in place for the image server to distribute images owned by the main webpage. A webhost can not be considered a publisher. In that case, the main webpage would have control over the image server and they would be the publisher of any direct linked images on that server.

06-22-2005, 10:22 PM
Pipeline Q Confirmed User Join Date: Dec 2004 Posts: 3,891	ORIGINAL QUESTION----- [Note that this has nothing to do with illegal bandwidth theft.] The basic question is this; Considering the inner workings of the internet, if Domain A hotlinks to images on Domain B, is Domain A considered the "publisher" of those images served and owned by Domain B once they load into the browser? Real life analagy... A newspaper instead of printing a photo leaves a blank space that reads, "Go to 12 Main Street and get their photo of the bird and glue it here." Once that photo is glued on, the newspaper certainly isn't the publisher of it even if they instructed it to be placed there. Can this translate into internet hotlinking terms? RESPONSE 1------ Sounds like a legal question to me, but if I were to guess I'd say that the owner of the server space that serves up the file is the publisher. RESPONSE 2----- The entity responsible for sending the data to the browser is the publisher regardless of whose webpage it appears on. Webpages are not marked by resemblance to PDF files or the like in that what appears on the screen is not contained and served in a single file. It is remarkably unremarkable that a single webpage have multiple publishers. Illustrations of this include third party content services that webmasters may deploy such as stock tickers, ad agencies and RSS feeds. The approved direct linking (i.e., hotlinking) of images also falls into this "third party content services" category. Since you asked for a technical explanation as to why this is, here it is in simplified terms. 1) Browser submits request for source code file from server. 2) Server grants request and sends source file to browser containing page layout and recommended content information.* * Any content that a source file directly contains or links to is considered recommended since it's display is ultimately the decision of the user or browser. 3) Browser processes source code and renders initial layout (e.g., tables) including textual content within the source file. The role of the main webpage ends herein even though direct links have yet to be requested, granted/denied or processed. 4) Browser requests image data from image server. 5) Image server grants request and sends image data to the browser. To be considered the publisher of any data, you must be the entity receiving the request from the browser, making the decision to grant or deny the request and finally the one to send the data. Throughout this process the main webpage did not take part in any of those three events. So we conclude that they can not be the publisher of the images. However, this is dependent upon no contractual agreement being in place for the image server to distribute images owned by the main webpage. A webhost can not be considered a publisher. In that case, the main webpage would have control over the image server and they would be the publisher of any direct linked images on that server.