 | | Re: Policy clarification regarding catalogs
|
|
Ben Gatrelle wrote in message ... (...) page (...) pre- (...) there (...) That URL has been published and is clearly intended for public consumption. Frank Filz Posting from my Dad's (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) There's a difference? (I'm serious.) Anyway, Brad Justus' statement is about "images or material". (...) *shrug* Perhaps. The web site that was at <URL:(URL) isn't there any more. Doesn't mean I didn't mean to publish it. :) (...) I think I (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I would say definitely no, because the intention of the query mechanism is to accept arbitrary input. --Todd (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Heh heh. No no, I mean when you find some directory with 755 permissions (instead of 711 permissions) and it's got no index.html file, but it's got a home.html file linked to from elsewhere, and home.html contains links to 5 images in its (...) (27 years ago, 18-Dec-99, to lugnet.admin.general, lugnet.off-topic.debate)
|
| |
 | | Intellectual exercise (was Re: Policy clarification regarding catalogs)
|
|
If I were to post the results of this script: #!/usr/bin/perl for ($i=0;$i<1000000;$i++) { printf "(URL) $i; } to LUGnet, and some of the links that result happen to not have links on any of Lego's linked-from-the-main-page pages, would I be in (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I thought we were talking about links to images. (...) I think the fact that the images are *gone* now expresses an even stronger intent not to publish. :) (...) But if a web developer at some company makes an idiotic mistake like that (and (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) You mean you go back and see what you should have felt guilty about, in retrospect? I think that's going a bit overboard! (27 years ago, 18-Dec-99, to lugnet.admin.general, lugnet.off-topic.debate)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I didn't mean it quite that literally. Correcting an obvious typo or fixing broken \'s to /'s is something I think anyone could do without feeling guilt! :) I meant things like trying to guess names of files from partial information, or if (...) (27 years ago, 18-Dec-99, to lugnet.admin.general, lugnet.off-topic.debate)
|
| |
 | | Re: Language slipping?
|
|
(...) Oh come on. Please. You know as well as the rest of us that children _do_ know those words. The more you try to hide it, the earlier they know. Besides, the words themselves aren't the problem. It's the intent behind them. (...) Here, have a (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I'm coming to think so too. To me, this is fundamentally why we have a URLs -- Uniform Resource Locators. The ability to identify and access resources directly is a basic design decision underlying what makes the WWW what it is. If the intent (...) (27 years ago, 18-Dec-99, to lugnet.admin.general, lugnet.off-topic.debate)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I would almost certainly respect that. Unfortunately, that's not what is being said.. (...) Indeed. Jasper (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Probably. (...) Maybe you haven't spent much time on personal homepages. Misspelled links in the source are more common than correct ones, it sometimes seems. Oh, and of course all webdevelopment gets done on case-insenstive FAT16/32. And then (...) (27 years ago, 18-Dec-99, to lugnet.admin.general, lugnet.off-topic.debate)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Another example of this: what about a link to <URL:(URL) or <URL:(URL) Is it a violation of copyright to give these links to someone? (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Robotics subgroups by mail (was: sensors)
|
|
(...) I would think the support of Michael Gasperi and Brian Stormont would be important here, since this would be moving a certain amount of traffic down to a lower level rather than creating new traffic from scratch (where there is no loss but (...) (27 years ago, 18-Dec-99, to lugnet.robotics, lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Yeah, I'm probably getting all hot and bothered over nothing. *sigh* That's how it goes these days. You go to a club, you think they come onto you, and *bam*, there they take off with a vampire to slay an evil prehistoric monster. Jasper "be (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Hmmm.. I prefer to get my opinion out _first_, so that it can be considered in that sort of thinking ;) Jasper (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) If Lego changes their statement to be: "Out of politeness, please don't publish URLs not clickable through links on our pages", I would also be inclined to respect that. The "don't do this because it violates our legal rights" stuff is what (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) There were, however, images on the SW portion of lego.com which were being served from that webserver (IIRC, not www.lego.com, though). A simple view source revealed thew existece of that webserver. (...) Yeah. I wonder when I'm gonna get an (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) I don't think that's clear at all! It may be simply a matter of poor index design, or laziness. Luckily for my argument :) I have a great example of this already. <URL:(URL) is an intended-to-be-public website. Check out <URL:(URL): you won't (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|
| |
 | | Re: Policy clarification regarding catalogs
|
|
(...) Not necessarily. Does (URL) contain links to all the users /~user directories? In 90% of the cases, in my experience,. not. Same for ISPs. So 90% of the web is not intended to be seen by your logic. Security through obscurity is no security at (...) (27 years ago, 18-Dec-99, to lugnet.admin.general)
|