| |
In lugnet.publish, Alan Carmack writes:
> In lugnet.publish, Todd Lehman writes:
> > In lugnet.admin.general, Alan Carmack writes:
> > > First, be careful to read the Lugnet Use Agreement. Anything you post on
> > > your "personal" lugnet page grants Lugnet *and* third-parties a
> > > non-exclusive license to reproduce, edit, post your material on the web and
> > > on any communications media.
> >
> > Actually, that doesn't apply to off-site content you might link to or embed
> > on a page, for example images. It applies only to data sent to and stored
> > on the server: messages posted, files uploaded, data inputted, or other
> > communications. The FTX FAQ contains more information:
> >
> > http://www.lugnet.com/publish/ftx/faq/
>
> I guess I will have to read the User Agreement more carefully. Or maybe it
> was worded so I misunderstood it, given that I got 2 hours sleep last. Which
> sort of sux because I had done 4 pages on my lugnet site, with images from
> offsite--when I suddenly read the User Agreement and thought that anything
> posted to the site would be "liable" to non-exclusive license by you and
> "third parties." You are saying this does not apply to photos I embed on my
> pages that are located off lugnet? So you cannot repost them, in any way or
> form, in any communication media, without my prior notice?
Not the images per se, no. You aren't granting permission to actually
publish raw JPEG (or GIF, or whatever) images from the server or from
anywhere else. But you are granting the right to publish, adapt, etc.
the content that you do submit (i.e., news postings or FTX pages) which
might _reference_ your images. For example, the webserver needs to be able
to reformat, adapt, archive, etc. your FTX pages in normal operation.
In fact, every single time an FTX page is displayed, the webserver is
adapting your content on-the-fly from FTX format to HTML format.
With regard to images, basically, you're granting permission to refer to
your image (at a specific URL only) on LUGNET pages perpetually. Now, if
you delete a webpage that someone else had included a specific revision
number of on their webpage, it'll still be around -- it won't be broken
content, but if you move your actual off-site image to a different URL
without updating your FTX page to point to the new URL, then the image link
would break, and permission to refer to the image at the old location would
still be valid, but the image just wouldn't be there. You would have to
upload new FTX content referring to the image at the new URL if you wanted
to give permission to refer to the image at its new location if you moved
it. So, in effect, if you wanted to, you could effectively cease publishing
your images on LUGNET web pages simply by deleting the image from your
webserver or moving them to a new different location.
However, if you actually upload an actual image file to the LUGNET webserver,
for example a photo you took of a LEGO set for the sets database, then that
falls under the perpetual permission stuff, because it's content you actually
uploaded, as opposed to content you're referring to off-site.
> With the
> exception, I guess of that weird word that means something roughly to the
> effect of embedding someone else's lugnet page into yours (I did not read
> that part of the user guide closely, as it did not pertain offhand to me).
Right. Third parties in this case, for example, are other users. You could
create an FTX page that included one of someone else's personal FTX pages --
if you wanted to -- without having to ask them. That's OK because that
person has granted permission for adaptations of their content (including
their content in your content is a simple adaptation). In cases where this
occurs, the copyright notice at the bottom of the page includes your name
and the name of the person whose content you have included. There is also
an automatic link to "break out" back to their content only. (That's the
little blue box along the right.)
Ted Nelson, who coined the term Hypertext 30 years before the WWW arose,
calls this "transclusion" of content, and the concept of indirectly granting
other people permission to include your content "transcopyright."
http://www.lugnet.com/publish/ftx/guide/transclusion
http://www.xanadu.com/TECH/xuTech.html
http://www.sfc.keio.ac.jp/~ted/TPUB/TPUBsum.html
http://www.sfc.keio.ac.jp/~ted/transcopyright/transcopy.html
(Actually, LUGNET's form of transclusion and transcopyright is vastly inferior
compared to Nelson's hypertext theory, but we had to work within the standard
confines of HTML and the WWW.)
--Todd
|
|
Message is in Reply To:
 | | Re: Announcement: Member pages
|
| (...) was worded so I misunderstood it, given that I got 2 hours sleep last. Which sort of sux because I had done 4 pages on my lugnet site, with images from offsite--when I suddenly read the User Agreement and thought that anything posted to the (...) (24 years ago, 1-Mar-01, to lugnet.publish, lugnet.admin.general)
|
14 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
