| |
In lugnet.off-topic.debate, Larry Pieniazek writes:
> In lugnet.off-topic.debate, Richard Noeckel writes:
> > Some answers to your questions;
> >
> > Why general: because I posted a general question.
> > Why post the link: because by saying that there’s an issue in
> > Brickshelf would cause people to flood over there to see what's amiss.
> > (By saying there’s a fire in Brickshelf everyone would turn around and
> > check, but, by posting a question directly regarding the situation would
> > hopefully incur some help.)
> >
> > > a lot better by dropping a note to Kevin
> >
> > That's a good idea, to inform the Brickshelf administrator of the problem.
> > Yet, I was unaware of who the administrator was, and I didn’t know how to
> > contact him.
>
> That raises a good point. The logical place to look for contact info
> specific to a site is typically the site's "front door", in this case
> www.brickshelf.com (contrast with LUGNET(tm) which has a clear way to
> contact admins on the front page... the "feedback" link)
>
> There is no contact info on that front door page of Brickshelf(tm) nor any
> obvious link to follow to find it... That's possibly a failing. You sort of
> have to be an "insider" to know what Kevin's email is. As it turns out,
> there is no contact info on the front page of the most likely LUGNET
> newsgroup that one might think to look in:
> http://news.lugnet.com/announce/brickshelf/... one could search that group
> to try to determine who the owner of Brickshelf(tm) was... but that's sort
> of inferring from what is said rather than solid info.
>
> A public way to find Kevin's contact info is to follow this link
> http://www.brickshelf.com/scans/README
>
> but that too is not at all obvious to the casual user, it's pretty obscure.
>
> So yes, the suggestion of dropping Kevin a note depends on *knowing* how to
> do that. But one STILL could just have posted a "how do I contact the admin
> of Brickshelf" instead of posting the link (and, mea culpa, I and others
> shouldn't have included the link in my reply). That note in and of itself
> would not have been a "fire" call as you refer to above.
>
> Kevin probably should fix that lacking.
>
> > Plus, I also wanted to understand the reasoning behind the individuals
> > purpose!
>
> Why? Or in other words, who cares? LUGNET is not a psychology site.
Well, it looks like problem solved...but you are right (and not trying
to compound the issue by "slapping richards hand", as several hands already
did)
I totally agree with Lar on the info at hand....sure there was a
problem that needed to be addressed immediately, and you are also right
that there is no immediate way to contact Kevin, in case an issue like
this would come up, especially for the relative "uneducated" (as far as
contact info to Kevin)
So I can understand Richards dilemma, but pointing to filth on Lugnet
probably violates the TOS as much as posting it yourself, as it allows
greater access to minors to see the trash, especially in Lugnet.General.
Well, I think the initial issue is resolved. However, as the main forebearers
of the Community Policing advocates (you, as in Larry P, and Tim Courtney)
should probably come up with some simple FAQ's and some procedures to make
sure that if something like this happens again....there is something in
place....and that it is posted in an appropriate spot.
Benjamin Medinets
|
|
Message has 1 Reply:
 | | Q Re: ?
|
| "Benjamin Medinets" <bmedinets@excite.com> wrote in message news:GruEy2.EHG@lugnet.com... (...) Yeah. The whole thing is a tricky situation, lets let that part of it die and work to come to an agreement on how to effectively deal with situations (...) (23 years ago, 20-Feb-01, to lugnet.off-topic.debate)
|
Message is in Reply To:
| | Re: ?
|
| (...) That raises a good point. The logical place to look for contact info specific to a site is typically the site's "front door", in this case www.brickshelf.com (contrast with LUGNET(tm) which has a clear way to contact admins on the front (...) (23 years ago, 20-Feb-02, to lugnet.off-topic.debate)
|
37 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
|
|
|
|
