The Madshrimps Silentium case review has returned to the web

[Guest]

Archived from groups: alt.comp.hardware.pc-homebuilt (More info?)

I understand there was a scripting error on the Madshrimps site, which
has been corrected.

 

[Guest]

Archived from groups: alt.comp.hardware.pc-homebuilt (More info?)

"Felger Carbon" <fmsfnf@jfoops.net> wrote:

> I understand there was a scripting error on the Madshrimps site,
> which has been corrected.

So your three new posts in three hours were based on a
misunderstanding.






>
>
>
>
> Path: newssvr17.news.prodigy.com!newsdbm02.news.prodigy.com!newsdst01.news.prodigy.com!newsmst01b.news.prodigy.com!prodigy.com!newscon06.news.prodigy.com!prodigy.net!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread3.news.pas.earthlink.net.POSTED!468f3ae9!not-for-mail
> Reply-To: "Felger Carbon" <fmsfnf jfoops.net>
> From: "Felger Carbon" <fmsfnf jfoops.net>
> Newsgroups: alt.comp.hardware.pc-homebuilt
> Subject: The Madshrimps Silentium case review has returned to the web
> Lines: 4
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> Message-ID: <5C3Ne.8882$RS.8822 newsread3.news.pas.earthlink.net>
> Date: Thu, 18 Aug 2005 17:31:45 GMT
> NNTP-Posting-Host: 4.255.45.65
> X-Complaints-To: abuse earthlink.net
> X-Trace: newsread3.news.pas.earthlink.net 1124386305 4.255.45.65 (Thu, 18 Aug 2005 10:31:45 PDT)
> NNTP-Posting-Date: Thu, 18 Aug 2005 10:31:45 PDT
> Organization: EarthLink Inc. -- http://www.EarthLink.net
> Xref: newsmst01b.news.prodigy.com alt.comp.hardware.pc-homebuilt:443558
>

 

[Guest]

Archived from groups: alt.comp.hardware.pc-homebuilt (More info?)

"John Doe" <jdoe@usenet.love.invalid> wrote in message
news:Xns96B6E00D2F194wisdomfolly@207.115.63.158...
> "Felger Carbon" <fmsfnf@jfoops.net> wrote:
>
> > I understand there was a scripting error on the Madshrimps site,
> > which has been corrected.
>
> So your three new posts in three hours were based on a
> misunderstanding.

If you call a negative review not being available via the obvious
route (direct search engine look-up) but available thru a back-door
(indirect, secondary search engine look-up) a misunderstanding, then
OK it was a misunderstanding. I personally would call it a problem -
one which has been explained to me as being due to a scripting error,
not a misunderstanding. I have not yet figured out how and why the
secondary path I discovered to the negative review was not _also_
blocked by the scripting error. I guess that must be a
misunderstanding too.