Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: wij <wyniijj5@gmail.com>
Newsgroups: comp.theory
Subject: Re: Incorrect requirements --- Computing the mapping from the input
 to HHH(DD)
Date: Mon, 12 May 2025 08:33:50 +0800
Organization: A noiseless patient Spider
Lines: 75
Message-ID: <f5a9ca0c0edaeb582b14c3babee27e25d41fc953.camel@gmail.com>
References: <vv97ft$3fg66$1@dont-email.me>
	 <09cea75db07408dc9203aca3fb74408ad3a095b4.camel@gmail.com>
	 <vvoubl$3qtsi$1@dont-email.me>
	 <bc4fb153ff914177dba706ce6e0dfb467e2126eb.camel@gmail.com>
	 <vvp04i$3r5li$3@dont-email.me>
	 <853816e160c7b3fe75c71f0728e72989d9fb2e41.camel@gmail.com>
	 <vvp1fm$3r5li$4@dont-email.me>
	 <b049926b61baa5d69d11655a8af06e537b7acd71.camel@gmail.com>
	 <vvqga9$gldn$3@dont-email.me>
	 <41e08841caf0d628beb5105bc78531a412eea440.camel@gmail.com>
	 <vvql3p$gldn$15@dont-email.me>
	 <cb999b6746607a1445c196e485a2c1124eaee8b5.camel@gmail.com>
	 <vvqnev$i5d0$3@dont-email.me>
	 <07c4f2302645a7e58957b5e5bffed80397a6ddae.camel@gmail.com>
	 <vvr0ot$k9nu$1@dont-email.me>
	 <04bd32e2a5572305de0376f9569172932ffb252f.camel@gmail.com>
	 <vvr2ov$khl4$2@dont-email.me>
	 <72f8c8295d3a0ff265a67b0de838516ade16c6d5.camel@gmail.com>
	 <vvr6lj$lieg$1@dont-email.me>
	 <8667c45172be6519444525c30d280cde06d77e2b.camel@gmail.com>
	 <vvr8dj$lu2b$1@dont-email.me>
	 <7281f97665272ea0eb85e56940648f6c807b0b8e.camel@gmail.com>
	 <vvralq$me5h$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Injection-Date: Mon, 12 May 2025 02:33:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="c80d5b5e9f515b03afe08cc6985dc17b";
	logging-data="692129"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18VJD8SLpbbZV482DVV5IzE"
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41)
Cancel-Lock: sha1:RstteWvHILarMEsNmb+bRK63j6k=
In-Reply-To: <vvralq$me5h$1@dont-email.me>

On Sun, 2025-05-11 at 18:08 -0500, olcott wrote:
> On 5/11/2025 5:50 PM, wij wrote:
> > On Sun, 2025-05-11 at 17:30 -0500, olcott wrote:
> > > On 5/11/2025 5:11 PM, wij wrote:
> > > > On Sun, 2025-05-11 at 17:00 -0500, olcott wrote:
> > > > [cut]
> > > > > > > ZFC corrected the error in set theory so that
> > > > > > > it could resolve Russell's Paradox. The original
> > > > > > > set theory has now called naive set theory.
> > > > > > >=20
> > > > > > > I corrected the error of the HP that expects
> > > > > > > HHH to report on behavior that is different
> > > > > > > than the behavior that its input actually
> > > > > > > specifies.
> > > > > >=20
> > > > > > Specificly, "Halt(D)=3D1 iff D() halts" is an error?
> > > > > > And it should expect: Halt(D)=3D1 iff POOH(D)=3D1 (correct prob=
lem)?
> > > > > >=20
> > > > >=20
> > > > > Yes that is an error because the behavior that
> > > > > the input to HHH(DDD) specifies is the behavior
> > > > > that HHH must report on.
> > > >=20
> > > > If so, how do we know a given function e.g. D, halts or not by givi=
ng it to H,
> > > > i.e. H(D)? Wrong question (according to you)?
> > >=20
> > > H and D is too vague and ambiguous.
> > > We know that the input to HHH(DDD) specifies
> > > a non-halting sequence of configurations.
> > >=20
> > > We know that the input to HHH1(DDD) specifies
> > > a halting sequence of configurations.
> > >=20
> > > > Instead, every time we want to know whether D halts or not,
> > >=20
> > > When we intentionally define an input to attempt
> > > to thwart a specific termination analyzer THIS DOES
> > > CHANGE THE BEHAVIOR.
> > >=20
> > > If we let people run uploaded programs on our
> > > network we need to know if these programs are
> > > going to halt.
> > >=20
> > > Unless HHH(DDD) rejects its input as non-halting
> > > HHH will continue to eat up network resources.
> >=20
> > But, according to POOH, if D going to eat up network resources, it have=
 to
> > happen when we run POOH(D), because you said D's halting property only
> > valid to H.
> >=20
>=20
> If we want to prevent this kind of denial of service
> attack HHH must be able correctly handle inputs that
> are trying to thwart it or HHH fails.
>=20
> When HHH is our official denial of service attack
> preventer it either rejects its input DDD as non
> halting or it gets stuck in recursive emulation
> thus fails.
>=20
> It always has been the requirement that a termination
> analyzer was required to report on the behavior that
> its input actually specifies.
>=20
> This is a subtle nuance of functions computed by
> models of computation that no one bothered to
> pay attention to because they didn't know it made
> any difference.
>=20

Is DDD a virus?