Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #40066 > unrolled thread
| Started by | olcott <NoOne@NoWhere.com> |
|---|---|
| First post | 2021-09-28 22:20 -0500 |
| Last post | 2021-10-01 16:40 -0400 |
| Articles | 20 on this page of 325 — 13 participants |
Back to article view | Back to comp.theory
Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-09-28 22:20 -0500
Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-28 22:47 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-09-29 06:28 -0400
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <news.x.richarddamon@xoxy.net> - 2021-09-29 07:52 -0400
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-09-29 23:48 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-29 18:19 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-09-29 20:20 -0400
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-09-30 02:36 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-29 20:39 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-09-29 21:50 -0400
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-09-30 02:57 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-29 21:11 -0500
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-09-30 03:42 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-29 21:52 -0500
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-09-30 17:35 +0100
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] olcott <NoOne@NoWhere.com> - 2021-09-30 12:08 -0500
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 00:14 +0100
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] olcott <NoOne@NoWhere.com> - 2021-09-30 18:58 -0500
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 02:50 +0100
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] olcott <NoOne@NoWhere.com> - 2021-09-30 21:07 -0500
Re: Clarification of Linz Ĥ Description (V2) [ dishonest dodge ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 03:22 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-30 17:12 -0500
Re: Clarification of Linz Ĥ Description (V2) André G. Isaak <agisaak@gm.invalid> - 2021-09-30 16:55 -0600
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-30 18:21 -0500
Re: Clarification of Linz Ĥ Description (V2) André G. Isaak <agisaak@gm.invalid> - 2021-09-30 18:18 -0600
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-30 19:26 -0500
Re: Clarification of Linz Ĥ Description (V2) André G. Isaak <agisaak@gm.invalid> - 2021-09-30 18:39 -0600
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-30 19:54 -0500
Re: Clarification of Linz Ĥ Description (V2) André G. Isaak <agisaak@gm.invalid> - 2021-09-30 19:07 -0600
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-09-30 20:27 -0500
Re: Clarification of Linz Ĥ Description (V2) André G. Isaak <agisaak@gm.invalid> - 2021-09-30 19:40 -0600
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-09-30 21:38 -0400
Re: Clarification of Linz Ĥ Description (V2) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2021-10-01 15:12 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 09:36 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 11:44 -0400
Re: Clarification of Linz Ĥ Description (V2) Jeff Barnett <jbb@notatt.com> - 2021-10-01 10:45 -0600
Re: Clarification of Linz Ĥ Description (V2) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2021-10-02 01:09 +0100
Re: Clarification of Linz Ĥ Description (V2) [ basis of my rebuttal ] olcott <NoOne@NoWhere.com> - 2021-10-01 22:42 -0500
Re: Clarification of Linz Ĥ Description (V2) [ basis of my rebuttal ] Richard Damon <Richard@Damon-Family.org> - 2021-10-02 06:58 -0400
Re: Clarification of Linz Ĥ Description (V2) Andy Walker <anw@cuboid.co.uk> - 2021-10-01 17:27 +0100
Re: Clarification of Linz Ĥ Description (V2) Jeff Barnett <jbb@notatt.com> - 2021-10-01 10:55 -0600
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 12:04 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 13:17 -0400
Re: Clarification of Linz Ĥ Description (V2) [ key basis of refutation ] olcott <NoOne@NoWhere.com> - 2021-10-01 12:30 -0500
Re: Clarification of Linz Ĥ Description (V2) [ key basis of refutation ] Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:18 -0400
Re: Clarification of Linz Ĥ Description (V2) [ key basis of refutation ] olcott <NoOne@NoWhere.com> - 2021-10-01 15:25 -0500
Re: Clarification of Linz Ĥ Description (V2) [ key basis of refutation ] Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:49 -0400
Re: Clarification of Linz Ĥ Description (V2) Andy Walker <anw@cuboid.co.uk> - 2021-10-01 21:09 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 15:23 -0500
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 21:32 +0100
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 15:46 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:55 -0400
Re: Clarification of Linz Ĥ Description (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 00:13 +0100
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 13:11 -0400
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 12:18 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 13:22 -0400
Re: Clarification of Linz Ĥ Description (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 12:43 -0500
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:26 -0400
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <Richard@Damon-Family.org> - 2021-09-30 21:35 -0400
Re: Clarification of Linz Ĥ Description (V2) Richard Damon <news.x.richarddamon@xoxy.net> - 2021-09-30 06:25 -0400
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-09-29 06:26 -0400
Re: Clarification of Linz Ĥ Description wij <wyniijj@gmail.com> - 2021-10-01 09:12 -0700
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 11:46 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 13:19 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 12:41 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:34 -0400
Re: Clarification of Linz Ĥ Description Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 21:44 +0100
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 15:58 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 17:18 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 16:28 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 17:58 -0400
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 18:00 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 17:21 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 18:34 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 17:46 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 19:04 -0400
Re: Clarification of Linz Ĥ Description [ key difference ] olcott <NoOne@NoWhere.com> - 2021-10-01 18:20 -0500
Re: Clarification of Linz Ĥ Description [ key difference ] Richard Damon <Richard@Damon-Family.org> - 2021-10-01 20:27 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 17:10 -0500
Re: Clarification of Linz Ĥ Description Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-01 23:22 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] olcott <NoOne@NoWhere.com> - 2021-10-01 17:29 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-01 19:12 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 01:08 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] olcott <NoOne@NoWhere.com> - 2021-10-01 22:38 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-02 06:34 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 17:10 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) olcott <NoOne@NoWhere.com> - 2021-10-02 11:58 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 22:59 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) olcott <NoOne@NoWhere.com> - 2021-10-01 23:10 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 06:54 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) olcott <NoOne@NoWhere.com> - 2021-10-02 09:16 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) olcott <NoOne@NoWhere.com> - 2021-10-02 09:26 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 11:08 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) olcott <NoOne@NoWhere.com> - 2021-10-02 10:29 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 12:02 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) olcott <NoOne@NoWhere.com> - 2021-10-02 11:39 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 13:04 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) olcott <NoOne@NoWhere.com> - 2021-10-02 12:32 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 13:50 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) olcott <NoOne@NoWhere.com> - 2021-10-02 13:08 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 14:40 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) olcott <NoOne@NoWhere.com> - 2021-10-02 13:47 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 15:42 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) olcott <NoOne@NoWhere.com> - 2021-10-02 14:54 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V4) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 16:14 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-02 15:50 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Jeff Barnett <jbb@notatt.com> - 2021-10-02 15:12 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <news.x.richarddamon@xoxy.net> - 2021-10-02 17:53 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-02 17:20 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-02 15:43 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-02 17:43 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-02 19:19 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-02 17:52 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-02 18:27 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] DV <xlt.pjw@gmail.com> - 2021-10-11 06:32 -0700
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-11 20:08 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] DV <xlt.pjw@gmail.com> - 2021-10-11 19:02 -0700
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-11 22:24 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Jeff Barnett <jbb@notatt.com> - 2021-10-11 22:30 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-12 02:41 -0700
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-12 08:35 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-12 18:59 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-13 10:14 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 12:15 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-13 12:17 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 14:37 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-13 13:57 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 16:49 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-13 18:31 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-13 18:01 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-13 21:09 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 22:33 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-13 20:37 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 20:08 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-14 01:24 -0700
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-14 09:57 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-14 16:06 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-14 17:47 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-14 17:32 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-14 19:27 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-14 18:59 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <news.x.richarddamon@xoxy.net> - 2021-10-15 00:29 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-15 09:47 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-15 11:17 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-15 10:39 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-15 12:16 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-15 12:27 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] André G. Isaak <agisaak@gm.invalid> - 2021-10-15 12:31 -0600
Re: Clarification of Linz Ĥ Description [ untainted decision ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-15 22:31 +0100
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-15 22:18 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <news.x.richarddamon@xoxy.net> - 2021-10-15 23:30 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-16 04:11 -0700
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-16 08:07 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 10:30 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-16 17:28 +0100
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-15 22:22 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 10:39 -0400
Re: Clarification of Linz Ĥ Description [ correct halt deciding criteria ] olcott <NoOne@NoWhere.com> - 2021-10-16 10:47 -0500
Re: Clarification of Linz Ĥ Description [ correct halt deciding criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 12:05 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-16 17:27 +0100
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-16 10:49 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 12:10 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-16 17:27 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-16 13:07 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 18:39 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-16 18:41 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 22:24 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-16 22:40 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-16 21:44 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] André G. Isaak <agisaak@gm.invalid> - 2021-10-16 21:34 -0600
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-16 22:59 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-17 08:02 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] André G. Isaak <agisaak@gm.invalid> - 2021-10-17 10:17 -0600
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-18 09:00 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] André G. Isaak <agisaak@gm.invalid> - 2021-10-18 08:54 -0600
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-18 21:11 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-19 09:51 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] olcott <NoOne@NoWhere.com> - 2021-10-19 10:36 -0500
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-19 17:44 +0100
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-19 19:21 -0400
Re: Clarification of Linz Ĥ Description [ conclusive proof ] Richard Damon <Richard@Damon-Family.org> - 2021-10-17 07:57 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-17 00:49 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-16 19:52 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-17 16:03 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-17 12:02 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-17 13:36 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-18 01:47 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-18 10:07 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-18 13:56 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 07:22 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 07:24 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 07:26 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-19 16:10 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-19 10:26 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 09:17 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 09:20 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-19 17:42 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 10:36 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 11:16 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-19 23:53 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-19 16:50 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-20 02:29 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-20 04:14 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-20 05:41 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-20 06:29 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-20 09:01 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-20 12:13 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Alan Mackenzie <acm@muc.de> - 2021-10-20 20:01 +0000
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-20 13:37 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] Alan Mackenzie <acm@muc.de> - 2021-10-22 16:56 +0000
Re: Clarification of Linz Ĥ Description [ correct criteria ] DV <xlt.pjw@gmail.com> - 2021-10-22 12:33 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-20 08:29 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 20:04 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-20 19:29 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Jeff Barnett <jbb@notatt.com> - 2021-10-20 23:23 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-21 01:52 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Jeff Barnett <jbb@notatt.com> - 2021-10-21 02:05 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-21 07:45 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-10-21 05:18 -0700
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-20 08:35 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-18 23:59 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-19 09:10 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-19 17:55 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-19 12:17 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-19 19:12 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-20 02:21 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 08:57 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 09:13 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 10:25 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 09:42 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 10:51 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 10:46 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 11:53 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 11:04 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 12:37 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 11:55 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 13:15 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 13:00 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 15:00 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 14:06 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 15:34 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 15:40 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 16:59 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 16:52 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 18:04 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 20:23 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-21 01:01 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 15:06 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 14:32 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 16:55 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ André is lost? ] André G. Isaak <agisaak@gm.invalid> - 2021-10-20 16:50 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 19:46 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-21 01:00 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 19:23 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 20:35 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 19:46 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 21:10 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 20:23 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 21:40 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 21:22 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 22:56 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 22:00 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 23:36 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-21 02:37 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-20 21:18 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-20 23:05 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-21 10:45 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] olcott <NoOne@NoWhere.com> - 2021-10-21 09:04 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Richard Damon <Richard@Damon-Family.org> - 2021-10-21 19:15 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ SELF-EVIDENT TRUTH ] olcott <NoOne@NoWhere.com> - 2021-10-21 18:30 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ SELF-EVIDENT TRUTH ] olcott <NoOne@NoWhere.com> - 2021-10-21 18:33 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ SELF-EVIDENT TRUTH ] Richard Damon <Richard@Damon-Family.org> - 2021-10-21 23:03 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost? ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-22 03:19 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] olcott <NoOne@NoWhere.com> - 2021-10-21 21:33 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Jeff Barnett <jbb@notatt.com> - 2021-10-21 21:59 -0600
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-23 00:57 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] olcott <NoOne@NoWhere.com> - 2021-10-22 23:19 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Richard Damon <Richard@Damon-Family.org> - 2021-10-23 08:58 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-25 00:30 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] olcott <NoOne@NoWhere.com> - 2021-10-25 09:46 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Richard Damon <Richard@Damon-Family.org> - 2021-10-25 19:13 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-26 01:46 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ][ Ben is lost! ] olcott <NoOne@NoWhere.com> - 2021-10-25 20:02 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-19 21:19 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-18 21:15 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-19 07:34 -0400
Re: Clarification of Linz H^ Description [ correct criteria ] Mikko <mikko.levanto@outlook.com> - 2021-10-17 15:01 +0300
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-17 09:06 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-17 09:27 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-17 16:09 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] olcott <NoOne@NoWhere.com> - 2021-10-18 09:09 -0500
Re: Clarification of Linz Ĥ Description [ correct criteria ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-18 23:59 +0100
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-18 21:20 -0400
Re: Clarification of Linz Ĥ Description [ correct criteria ] Richard Damon <Richard@Damon-Family.org> - 2021-10-17 13:12 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-14 23:28 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] olcott <NoOne@NoWhere.com> - 2021-10-15 09:37 -0500
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-15 12:18 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-14 22:58 -0400
Re: Clarification of Linz Ĥ Description [ untainted decision ] Richard Damon <Richard@Damon-Family.org> - 2021-10-13 14:49 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 16:14 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) olcott <NoOne@NoWhere.com> - 2021-10-02 10:31 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) André G. Isaak <agisaak@gm.invalid> - 2021-10-02 09:58 -0600
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) olcott <NoOne@NoWhere.com> - 2021-10-02 11:23 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 12:44 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V3) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 23:00 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 11:15 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 17:34 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 12:48 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 21:15 +0100
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) olcott <NoOne@NoWhere.com> - 2021-10-02 16:02 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Richard Damon <Richard@Damon-Family.org> - 2021-10-02 17:30 -0400
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) olcott <NoOne@NoWhere.com> - 2021-10-02 12:12 -0500
Re: Clarification of Linz Ĥ Description [ Are we there yet ? ] (V2) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-10-02 22:26 +0100
Re: Clarification of Linz Ĥ Description André G. Isaak <agisaak@gm.invalid> - 2021-10-01 12:26 -0600
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 13:42 -0500
Re: Clarification of Linz Ĥ Description André G. Isaak <agisaak@gm.invalid> - 2021-10-01 13:07 -0600
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 14:18 -0500
Re: Clarification of Linz Ĥ Description André G. Isaak <agisaak@gm.invalid> - 2021-10-01 14:34 -0600
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 15:52 -0500
Re: Clarification of Linz Ĥ Description André G. Isaak <agisaak@gm.invalid> - 2021-10-01 16:17 -0600
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 17:23 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 18:36 -0400
Re: Clarification of Linz Ĥ Description olcott <NoOne@NoWhere.com> - 2021-10-01 17:48 -0500
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 19:15 -0400
Re: Clarification of Linz Ĥ Description Richard Damon <Richard@Damon-Family.org> - 2021-10-01 16:40 -0400
Page 8 of 17 — ← Prev page 1 … 6 7 [8] 9 10 … 17 Next page →
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2021-10-14 18:59 -0600 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <skajq6$dkg$1@dont-email.me> |
| In reply to | #40397 |
On 2021-10-14 18:27, olcott wrote:
> On 10/14/2021 6:32 PM, André G. Isaak wrote:
>> On 2021-10-14 16:47, olcott wrote:
<snippage>
>> I simply want you to explain how a TM is supposed to use your 'machine
>> addresses' to determine whether a given TM description is the same as
>> another or not.
No response?
How does a Turing Machine -- a *real* turing machine -- determine
whether a description of a TM which it is given as input is a
description of itself as opposed to some other TM?
>>> This would not be feasible unless we at least define TM's with RAM.
>>
>> Which means you're no longer talking about TMs.
>>
>>>> If you refer to {current_state, current_input} as a "machine
>>>> address" and arbitrarily map the states and inputs to integers
>>>> beginning at one, then any two TMs with the same number of states
>>>> and the same number of symbols will generally have identical sets of
>>>> "machine addresses"
>>>
>>> They will be located at different places in RAM.
>>
>> TMs don't have RAM.
>>
>>> 2.3 Random Access Turing Machines
>>> The reason we don’t like Turing Machines is because
>>> they have a ridiculous memory model. We solve this
>>> by allowing random access to the tapes.
>>> http://www.cs.cmu.edu/~odonnell/toolkit13/lecture05-anonymous.pdf
>>
>> The model described in the above link, despite the name used, is not a
>> class of Turing Machines. It also doesn't lend to what you are trying
>> to do since the indices used refer to positions on the *tape*, which
>> don't correspond to what you are calling 'machine addresses'. All
>> copies of H_Hat copied to the tape will be at different locations on
>> the tape and thus will have different indices.
>
> Yes that is what I mean by machine addresses.
Before you claimed that a "machine address" was a {current_state,
current_input} pair. That's not the same as a tape index. And Turing
Machines don't have tape indices.
>>
>>>> regardless of what the TMs actually do. So how does this help you to
>>>> determine whether two machines are the same or not?
>>>
>>> We know that two machines are the same when the only way that we
>>> execute TM's is by simulating their machine description
>>
>> What do you mean 'the only way'? Linz's H is *not* simulated. It is an
>> actual Turing Machine. In your model, the *input* description given to
>> H is simulated.
>
> Linz explicitly specified that H is any TM that gets the right answer.
> He is incorrect that H does not exist.
>
>>
>>> and the second copy of the machine description is the other machine.
>>
>> I can't figure out what you mean by the above. What is 'the other
>> machine'?
> Look at your own words and see.
That's non-responsive.
André
--
To email remove 'invalid' & replace 'gm' with well known Google mail
service.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <news.x.richarddamon@xoxy.net> |
|---|---|
| Date | 2021-10-15 00:29 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <skb02i$4j2$1@dont-email.me> |
| In reply to | #40397 |
On 10/14/21 8:27 PM, olcott wrote: > Linz explicitly specified that H is any TM that gets the right answer. > He is incorrect that H does not exist. So, will you show an ACTUAL Turing Machine that gets the right answer? Not just something you claim must be sort of like a Turing Machine that givs something you hand wave to claim is the right answer. This is, of course, impossible, but you will try to make something that sort of seems to be the right answer, but you will hide the problems with a bunch of smoke. The key point that you seem to miss is that since H for you case only needs to get ONE machie right, H could just as easily ignore its input and give the 'right' answer. But Linz has shown that whatever answer H gives, it will be wrong by the nature of the construction of H^. You need to add all your unneeded complexity to try to justify that a wrong answer is right and that you get to change the rules, which you don't get to. H(P,I), to be right, must ALWAYS return the same answer when given the same P and I, and that answer must correspond to the actual behavior of P(I) when run as an independent computation. This applies even if P includes as part of its algorithm a copy of the algorithm of H, and if I is a representation of P, which includes a copy of the algorithm of H. This is NOT grounds for an emergency decleration of 'Pathology' and a suspension of the rules. This is just part of the allowable inputs that H must be able to get right, which it can't. The fact that a naive implementation of H will get stuck is NOT grounds to change the definition, it just shows that a naive implementation fails to meet the requirements (as will ANY actual implemwentation). The argument that no H can possible simulate its input to a halting state is NOT proof that any of the H^s are non-halting, it just doesn't follow, as ANY implementation of H that does actually abort its simulation and answer non-halting BY NATURE OF THE CONTSTURCITON OF H^ creates an H^ that is Halting, as that is what the actual machihe will do, regardless of the fact that the PARTIAL simulation done by that H aborts before it gets there. Remember, you FIRST need to define what H's algorithm is, THEN create the H^ based on it. H doesn't get to 'adapt' itself to H^, any such 'adaptation' needs to be pre-builtin to its algorithm, and H^ thus gets to use it.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-15 09:47 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <N5qdndGlmrMCCfT8nZ2dnUU7-WHNnZ2d@giganews.com> |
| In reply to | #40401 |
On 10/14/2021 11:29 PM, Richard Damon wrote: > On 10/14/21 8:27 PM, olcott wrote: > >> Linz explicitly specified that H is any TM that gets the right answer. >> He is incorrect that H does not exist. > > So, will you show an ACTUAL Turing Machine that gets the right answer? > > Not just something you claim must be sort of like a Turing Machine that > givs something you hand wave to claim is the right answer. > > This is, of course, impossible, but you will try to make something that > sort of seems to be the right answer, but you will hide the problems > with a bunch of smoke. > > > The key point that you seem to miss is that since H for you case only > needs to get ONE machie right, H could just as easily ignore its input > and give the 'right' answer. > > But Linz has shown that whatever answer H gives, it will be wrong by the > nature of the construction of H^. > Superficial analysis seems to indicate this, yet this is merely superficial analysis. Only categorically exhaustive reasoning can test every possibility that can possibly exist and do this in finite time. To reduce the amount of time to test every possibility that can possibly exist we test categories of possibilities. Once a whole category fails all of the possibilities in this category can be dismissed. Only when we have tested the exhaustively complete set of mutually exclusive categories can we say that a thing is truly analytically impossible. For the halting problem the key category that was never exhaustively tested is the category of a simulating halt decider. > You need to add all your unneeded complexity to try to justify that a > wrong answer is right and that you get to change the rules, which you > don't get to. > > H(P,I), to be right, must ALWAYS return the same answer when given the > same P and I, and that answer must correspond to the actual behavior of > P(I) when run as an independent computation. > > This applies even if P includes as part of its algorithm a copy of the > algorithm of H, and if I is a representation of P, which includes a copy > of the algorithm of H. > > This is NOT grounds for an emergency decleration of 'Pathology' and a > suspension of the rules. This is just part of the allowable inputs that > H must be able to get right, which it can't. > > The fact that a naive implementation of H will get stuck is NOT grounds > to change the definition, it just shows that a naive implementation > fails to meet the requirements (as will ANY actual implemwentation). > > The argument that no H can possible simulate its input to a halting > state is NOT proof that any of the H^s are non-halting, it just doesn't > follow, as ANY implementation of H that does actually abort its > simulation and answer non-halting BY NATURE OF THE CONTSTURCITON OF H^ > creates an H^ that is Halting, as that is what the actual machihe will > do, regardless of the fact that the PARTIAL simulation done by that H > aborts before it gets there. > > Remember, you FIRST need to define what H's algorithm is, THEN create > the H^ based on it. H doesn't get to 'adapt' itself to H^, any such > 'adaptation' needs to be pre-builtin to its algorithm, and H^ thus gets > to use it. -- Copyright 2021 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-15 11:17 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <rYgaJ.185989$rl3.116675@fx45.iad> |
| In reply to | #40403 |
On 10/15/21 10:47 AM, olcott wrote: > On 10/14/2021 11:29 PM, Richard Damon wrote: >> On 10/14/21 8:27 PM, olcott wrote: >> >>> Linz explicitly specified that H is any TM that gets the right answer. >>> He is incorrect that H does not exist. >> >> So, will you show an ACTUAL Turing Machine that gets the right answer? >> >> Not just something you claim must be sort of like a Turing Machine >> that givs something you hand wave to claim is the right answer. >> >> This is, of course, impossible, but you will try to make something >> that sort of seems to be the right answer, but you will hide the >> problems with a bunch of smoke. >> >> >> The key point that you seem to miss is that since H for you case only >> needs to get ONE machie right, H could just as easily ignore its input >> and give the 'right' answer. >> >> But Linz has shown that whatever answer H gives, it will be wrong by >> the nature of the construction of H^. >> > > Superficial analysis seems to indicate this, yet this is merely > superficial analysis. Only categorically exhaustive reasoning can test > every possibility that can possibly exist and do this in finite time. Right, and there are only 4 possible behaviors that H can have. It can halt in the state qy. It can halt in the state qn. It can halt in some other state and fail to meet its requirements. It can fail to halt in any state and fail to meet its requirements. What other possibility do you see for H to do. This IS a Categorically Exhaustive Reasoning. > > To reduce the amount of time to test every possibility that can possibly > exist we test categories of possibilities. Once a whole category fails > all of the possibilities in this category can be dismissed. > > Only when we have tested the exhaustively complete set of mutually > exclusive categories can we say that a thing is truly analytically > impossible. For the halting problem the key category that was never > exhaustively tested is the category of a simulating halt decider. > But, 'simulating halt deciders' are presumably a subset of the set of all halt deciders, and since the analysis was done for the set of ALL halt deciders, it included you case of 'simulating halt deciders'. The above set IS a Mutually Exclusive and Exhaustive set of categories. Please name a behavior that is NOT in that list, or a behavior that is in two of the items. If H applied to <H^> <H^> says qy, then H^ will loop forever, and H was wrong, and thus failed to meet its requirements. If H applied to <H^> <H^> says qn, then H^ will halt and H was wrong, and thus failed to meet its requirements. If H applied to <H^> <H^> halts in some other state, then H failed to meet its requirements If H applied to <H^> <H^> does not halt at all, then H failed to meet it rquirements. In EVERY case, and all cases have been considered, H has not meet its requirements, we have exhaustively proved that NO H can be created that will meet the requirements, and thus the set of H's that meet the requirments is empty. Note, the fact that a naive implementation of a simulating halt decider will naturally end up in the 4th case doesn't provide justification to change the requirements, it just says that method naturally fails to meet the requirements.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-15 10:39 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <J7adnSQaOvADPfT8nZ2dnUU7-QmdnZ2d@giganews.com> |
| In reply to | #40404 |
On 10/15/2021 10:17 AM, Richard Damon wrote: > > On 10/15/21 10:47 AM, olcott wrote: >> On 10/14/2021 11:29 PM, Richard Damon wrote: >>> On 10/14/21 8:27 PM, olcott wrote: >>> >>>> Linz explicitly specified that H is any TM that gets the right answer. >>>> He is incorrect that H does not exist. >>> >>> So, will you show an ACTUAL Turing Machine that gets the right answer? >>> >>> Not just something you claim must be sort of like a Turing Machine >>> that givs something you hand wave to claim is the right answer. >>> >>> This is, of course, impossible, but you will try to make something >>> that sort of seems to be the right answer, but you will hide the >>> problems with a bunch of smoke. >>> >>> >>> The key point that you seem to miss is that since H for you case only >>> needs to get ONE machie right, H could just as easily ignore its >>> input and give the 'right' answer. >>> >>> But Linz has shown that whatever answer H gives, it will be wrong by >>> the nature of the construction of H^. >>> >> >> Superficial analysis seems to indicate this, yet this is merely >> superficial analysis. Only categorically exhaustive reasoning can test >> every possibility that can possibly exist and do this in finite time. > > Right, and there are only 4 possible behaviors that H can have. > > It can halt in the state qy. > It can halt in the state qn. > It can halt in some other state and fail to meet its requirements. > It can fail to halt in any state and fail to meet its requirements. > > What other possibility do you see for H to do. > > This IS a Categorically Exhaustive Reasoning. H applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to H.qy because Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn https://www.researchgate.net/publication/351947980_Halting_problem_undecidability_and_infinitely_nested_simulation -- Copyright 2021 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-15 12:16 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <UPhaJ.11419$yk1.10216@fx13.iad> |
| In reply to | #40406 |
On 10/15/21 11:39 AM, olcott wrote: > On 10/15/2021 10:17 AM, Richard Damon wrote: >> >> On 10/15/21 10:47 AM, olcott wrote: >>> On 10/14/2021 11:29 PM, Richard Damon wrote: >>>> On 10/14/21 8:27 PM, olcott wrote: >>>> >>>>> Linz explicitly specified that H is any TM that gets the right answer. >>>>> He is incorrect that H does not exist. >>>> >>>> So, will you show an ACTUAL Turing Machine that gets the right answer? >>>> >>>> Not just something you claim must be sort of like a Turing Machine >>>> that givs something you hand wave to claim is the right answer. >>>> >>>> This is, of course, impossible, but you will try to make something >>>> that sort of seems to be the right answer, but you will hide the >>>> problems with a bunch of smoke. >>>> >>>> >>>> The key point that you seem to miss is that since H for you case >>>> only needs to get ONE machie right, H could just as easily ignore >>>> its input and give the 'right' answer. >>>> >>>> But Linz has shown that whatever answer H gives, it will be wrong by >>>> the nature of the construction of H^. >>>> >>> >>> Superficial analysis seems to indicate this, yet this is merely >>> superficial analysis. Only categorically exhaustive reasoning can >>> test every possibility that can possibly exist and do this in finite >>> time. >> >> Right, and there are only 4 possible behaviors that H can have. >> >> It can halt in the state qy. >> It can halt in the state qn. >> It can halt in some other state and fail to meet its requirements. >> It can fail to halt in any state and fail to meet its requirements. >> >> What other possibility do you see for H to do. >> >> This IS a Categorically Exhaustive Reasoning. > H applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to H.qy > because Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn Then H is not a computation, since the copy of H at H^.qx gave a different answer than H does interdependently. You H is using the wrong 'definition' of the problem. It is just POOP. H needs to answer what its input would do as an independent machine, not what its INCOMPLETE simulation showed. It gives the wrong answer. FAIL. BY DEFINITION. > > https://www.researchgate.net/publication/351947980_Halting_problem_undecidability_and_infinitely_nested_simulation > >
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-15 12:27 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <h_haJ.82961$tG6.1172@fx39.iad> |
| In reply to | #40406 |
On 10/15/21 11:39 AM, olcott wrote: > On 10/15/2021 10:17 AM, Richard Damon wrote: >> >> On 10/15/21 10:47 AM, olcott wrote: >>> On 10/14/2021 11:29 PM, Richard Damon wrote: >>>> On 10/14/21 8:27 PM, olcott wrote: >>>> >>>>> Linz explicitly specified that H is any TM that gets the right answer. >>>>> He is incorrect that H does not exist. >>>> >>>> So, will you show an ACTUAL Turing Machine that gets the right answer? >>>> >>>> Not just something you claim must be sort of like a Turing Machine >>>> that givs something you hand wave to claim is the right answer. >>>> >>>> This is, of course, impossible, but you will try to make something >>>> that sort of seems to be the right answer, but you will hide the >>>> problems with a bunch of smoke. >>>> >>>> >>>> The key point that you seem to miss is that since H for you case >>>> only needs to get ONE machie right, H could just as easily ignore >>>> its input and give the 'right' answer. >>>> >>>> But Linz has shown that whatever answer H gives, it will be wrong by >>>> the nature of the construction of H^. >>>> >>> >>> Superficial analysis seems to indicate this, yet this is merely >>> superficial analysis. Only categorically exhaustive reasoning can >>> test every possibility that can possibly exist and do this in finite >>> time. >> >> Right, and there are only 4 possible behaviors that H can have. >> >> It can halt in the state qy. >> It can halt in the state qn. >> It can halt in some other state and fail to meet its requirements. >> It can fail to halt in any state and fail to meet its requirements. >> >> What other possibility do you see for H to do. >> >> This IS a Categorically Exhaustive Reasoning. > H applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to H.qy > because Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn > > https://www.researchgate.net/publication/351947980_Halting_problem_undecidability_and_infinitely_nested_simulation > > Second argument. You 'CLAIM' that (a) the exact same code exists at H^.q as at H.q0 and the following, and (b) that the tape is identical for the two machines. This means that as we trace the execution of thw two machines, we will always be in the equivalent states with the tape being identical for the two machines. For one machine to end at qy and the other at qn, at some point, this equivalence MUST be broken. For this to happen, either there is a difference in the state transition table of the two machines at that state are different, thus (a) wasn't true, or the tape at the read heads differ, saying (b) wasn't true. Thus either your claim that you build H^ correctly is false, or your claim that H behaves differently in the two cases is fails, or you claim that H even exists is false. Note, ALL you work is in another computation formulation than Turing Machines, with a claim that it is equivalent to the needed machines. This non-existence just shows that your claim of the equivalent machine in the right form is false. The fact that you have shown an utter lack of understanding of what a Turing Machine actually is means this is really a likely possibility.
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2021-10-15 12:31 -0600 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <skchd5$e63$1@dont-email.me> |
| In reply to | #40406 |
On 2021-10-15 09:39, olcott wrote: > On 10/15/2021 10:17 AM, Richard Damon wrote: >> Right, and there are only 4 possible behaviors that H can have. >> >> It can halt in the state qy. >> It can halt in the state qn. >> It can halt in some other state and fail to meet its requirements. >> It can fail to halt in any state and fail to meet its requirements. >> >> What other possibility do you see for H to do. >> >> This IS a Categorically Exhaustive Reasoning. > H applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to H.qy > because Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn You still don't grasp that a TM stands computes a *mathematical* function. A mathematical function is a *fixed* set of ordered pairs expressing a mapping from the domain to the codomain. Since what you call Ĥ.qx is simply H with the final qy state replaced by an infinite loop, then if your H is actually a computation corresponding to the halting function it *must* be the case that: (a) H transitions to H.qy if and only iff Ĥ.qx enters an infinite loop. (b) H transitions to H.qn if and only if the Ĥ.qx transitions to Ĥ.qn. It doesn't matter whether H decides by using simulation, or by using some other form of analysis, or by consulting bear entrails. If H is actually a computation and Ĥ is constructed as in the Linz proof then both a and b *must* be true. André -- To email remove 'invalid' & replace 'gm' with well known Google mail service.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2021-10-15 22:31 +0100 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <877dee9drf.fsf@bsb.me.uk> |
| In reply to | #40406 |
olcott <NoOne@NoWhere.com> writes: > ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn Or, to put it more exactly, Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn and, if you kept the annotation that you dishonestly keep omitting, you'd see why no TM can behave in this way: Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. All the old threads where this (and the other arguments) were explained to you are still there where you walked away form them. The mistakes don't go away just because you take a break. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-15 22:18 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <OOudnc6IkMsU2ff8nZ2dnUU7-cvNnZ2d@giganews.com> |
| In reply to | #40426 |
On 10/15/2021 4:31 PM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn > > Or, to put it more exactly, > > Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn > > and, if you kept the annotation that you dishonestly keep omitting, > you'd see why no TM can behave in this way: > -----------------0---1--2---------- > Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn > if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. > If and only if (1) simulated by (0) does not halt on (2) > All the old threads where this (and the other arguments) were explained > to you are still there where you walked away form them. The mistakes > don't go away just because you take a break. > -- Copyright 2021 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <news.x.richarddamon@xoxy.net> |
|---|---|
| Date | 2021-10-15 23:30 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <skdgvt$f45$1@dont-email.me> |
| In reply to | #40433 |
On 10/15/21 11:18 PM, olcott wrote: > On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >> >> Or, to put it more exactly, >> >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> >> and, if you kept the annotation that you dishonestly keep omitting, >> you'd see why no TM can behave in this way: >> > -----------------0---1--2---------- >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >> > If and only if (1) simulated by (0) does not halt on (2) The actual question that H is supposed to answer is what the machine given as a representation does when run as an independent machine. It does NOT matter what you (0) does, it matters what the ACTUAL H^ does when given <H^> as its input. That would be what the H^.q0 at the very beginning of the line ends up doing at the very end. You are stuck on the WRONG question, so you get the WRONG ansswer. It is just POOP. That is why you need to add so much 'garbage' to you 'proof', to try to hide that you are working on the wrong problem. From every thing that has been shown. it is clear that H^ applied to <H^> goes to H^.qx and then to H^.qn and Halt. Thus question of what H applied to <H^> <H^> SHOULD give is Halt, but it give Non-Halting, and thus is WRONG. YOU DON'T GET TO CHANGE THE QUESTION JUST BECAUSE YOU FIND THE PROBLEM TO BE IMPOSSIBLE. The 'Pathological' entanglement is perfectly legal, and the challenge is that H needs to figure out how to handle this case, it isn't allowed to change the rules just because it has lost. That is the behavior of the 5 year old throwing the board and declaring that the game is stupid but he has won when he sees that he is going to lose. > >> All the old threads where this (and the other arguments) were explained >> to you are still there where you walked away form them. The mistakes >> don't go away just because you take a break. >> > >
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2021-10-16 04:11 -0700 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <e14be68b-5f95-45f9-9c92-4c72ae848142n@googlegroups.com> |
| In reply to | #40435 |
On Saturday, 16 October 2021 at 04:30:07 UTC+1, Richard Damon wrote: > > That is the behavior of the 5 year old throwing the board and declaring > that the game is stupid but he has won when he sees that he is going to > lose. > Or a 5 year old playing noughts and crosses with his ten year old brother. His brother tells him that, however he moves, he can never win. The five year old doesn't believe it, because he regularly beats other five year olds, and his parents. And because, well, it's an established game. But however he moves, his ten year old brother can always counter him.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-16 08:07 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <aqmdnfpcj8s8U_f8nZ2dnUU7-TfNnZ2d@giganews.com> |
| In reply to | #40435 |
On 10/15/2021 10:30 PM, Richard Damon wrote: > On 10/15/21 11:18 PM, olcott wrote: >> On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >>> olcott <NoOne@NoWhere.com> writes: >>> >>>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >>> >>> Or, to put it more exactly, >>> >>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>> >>> and, if you kept the annotation that you dishonestly keep omitting, >>> you'd see why no TM can behave in this way: >>> >> -----------------0---1--2---------- >>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >>> >> If and only if (1) simulated by (0) does not halt on (2) > > > The actual question that H is supposed to answer is what the machine > given as a representation does when run as an independent machine. > So you stupidly deny that the simulation of the TM description of a TM by a UTM is not computationally equivalent to the direct execution of the TM. That is pretty basic stuff to get wrong thus gutting your credibility. > It does NOT matter what you (0) does, it matters what the ACTUAL H^ does > when given <H^> as its input. > > That would be what the H^.q0 at the very beginning of the line ends up > doing at the very end. > > You are stuck on the WRONG question, so you get the WRONG ansswer. > > It is just POOP. > > That is why you need to add so much 'garbage' to you 'proof', to try to > hide that you are working on the wrong problem. > > From every thing that has been shown. it is clear that H^ applied to > <H^> goes to H^.qx and then to H^.qn and Halt. Thus question of what H > applied to <H^> <H^> SHOULD give is Halt, but it give Non-Halting, and > thus is WRONG. > > YOU DON'T GET TO CHANGE THE QUESTION JUST BECAUSE YOU FIND THE PROBLEM > TO BE IMPOSSIBLE. > > The 'Pathological' entanglement is perfectly legal, and the challenge is > that H needs to figure out how to handle this case, it isn't allowed to > change the rules just because it has lost. > > That is the behavior of the 5 year old throwing the board and declaring > that the game is stupid but he has won when he sees that he is going to > lose. > >> >>> All the old threads where this (and the other arguments) were explained >>> to you are still there where you walked away form them. The mistakes >>> don't go away just because you take a break. >>> >> >> > -- Copyright 2021 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-16 10:30 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <NlBaJ.188317$rl3.126831@fx45.iad> |
| In reply to | #40437 |
On 10/16/21 9:07 AM, olcott wrote: > On 10/15/2021 10:30 PM, Richard Damon wrote: >> On 10/15/21 11:18 PM, olcott wrote: >>> On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >>>> olcott <NoOne@NoWhere.com> writes: >>>> >>>>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >>>> >>>> Or, to put it more exactly, >>>> >>>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>>> >>>> and, if you kept the annotation that you dishonestly keep omitting, >>>> you'd see why no TM can behave in this way: >>>> >>> -----------------0---1--2---------- >>>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>>> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >>>> >>> If and only if (1) simulated by (0) does not halt on (2) >> >> >> The actual question that H is supposed to answer is what the machine >> given as a representation does when run as an independent machine. >> > > So you stupidly deny that the simulation of the TM description of a TM > by a UTM is not computationally equivalent to the direct execution of > the TM. That is pretty basic stuff to get wrong thus gutting your > credibility. But H is NOT a UTM, because its simulation does not match the behavior of the actual machine. In fact, your statement is part of the proof that your logic is invalid, but you assume that H acts like a UTM, but the machine it simulates acts differently then the machine does when actually run. A UTM doesn't stop simulating until the machine it is simulating reachs a halt state, even if that takes forever, which is NOT what H does. Your 'proof' of what H does is flawed, as it looks at the behavior of a machine different then the one it is given, as it presumes a different behavior for the copies of itself in that machine then it has for itself. A difference in behavior between a claimed UTM and the machine itself doesn't redefine what the machine did, it disproves the claim that the thing was a UTM.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2021-10-16 17:28 +0100 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <87ee8l7x3v.fsf@bsb.me.uk> |
| In reply to | #40433 |
olcott <NoOne@NoWhere.com> writes: > On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >> Or, to put it more exactly, >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> and, if you kept the annotation that you dishonestly keep omitting, >> you'd see why no TM can behave in this way: >> > -----------------0---1--2---------- >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >> > If and only if (1) simulated by (0) does not halt on (2) That's the wrong annotation. See the previous threads you abandoned if you have any interesting in learning why. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-15 22:22 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <cLadnb_3Fc4U2Pf8nZ2dnUU7-LXNnZ2d@giganews.com> |
| In reply to | #40426 |
On 10/15/2021 4:31 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn
>
> Or, to put it more exactly,
>
> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn
>
> and, if you kept the annotation that you dishonestly keep omitting,
> you'd see why no TM can behave in this way:
>
> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn
> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt.
>
-------------0----1--2
Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn
if (and only if) (1) simulated by (0) applied to (2) does not halt.
> All the old threads where this (and the other arguments) were explained
> to you are still there where you walked away form them. The mistakes
> don't go away just because you take a break.
>
--
Copyright 2021 Pete Olcott
"Great spirits have always encountered violent opposition from mediocre
minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-16 10:39 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <ouBaJ.90940$jm6.27297@fx07.iad> |
| In reply to | #40434 |
On 10/15/21 11:22 PM, olcott wrote: > On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >> >> Or, to put it more exactly, >> >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> >> and, if you kept the annotation that you dishonestly keep omitting, >> you'd see why no TM can behave in this way: >> >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >> > > -------------0----1--2 > Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn > if (and only if) (1) simulated by (0) applied to (2) does not halt. > WRONG (0) is NOT a UTM The criteria for proper behavior is either The Machine described by (1) <which is H^> applied to (2) does not halt, which is the machine started at the very beginning of the line. Or it could be if (1) (2) simulated by a REAL UTM does not halt The key here is that answer that (0) is supposed to give is NOT based on what (0) itself does, but on what (1) (2) actually does under a REAL UTM or the actual machine. The 'Halting Behavior' of the input must be only a function of that input, and NOT anything about the specifics of the machine making the decision as the question is about the property of the computation represented, not the decider.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2021-10-16 10:47 -0500 |
| Subject | Re: Clarification of Linz Ĥ Description [ correct halt deciding criteria ] |
| Message-ID | <ifGdnS3sxr6zaff8nZ2dnUU7-LHNnZ2d@giganews.com> |
| In reply to | #40440 |
On 10/16/2021 9:39 AM, Richard Damon wrote: > On 10/15/21 11:22 PM, olcott wrote: >> On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >>> olcott <NoOne@NoWhere.com> writes: >>> >>>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >>> >>> Or, to put it more exactly, >>> >>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>> >>> and, if you kept the annotation that you dishonestly keep omitting, >>> you'd see why no TM can behave in this way: >>> >>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >>> >> >> -------------0----1--2 >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> if (and only if) (1) simulated by (0) applied to (2) does not halt. >> > > > WRONG (0) is NOT a UTM > When-so-ever the pure simulation of a TM description by a simulating halt decider never reaches its final state whether or not this simulation is terminated by this simulating halt decider this simulating halt decider correctly terminates this simulation and reports that this TM description never halts on its input. Ĥ.q0 ⟨Ĥ0⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn // This is correct. if (and only if) simulated ⟨Ĥ1⟩ applied to ⟨Ĥ2⟩ never reaches its final state -- Copyright 2021 Pete Olcott "Great spirits have always encountered violent opposition from mediocre minds." Einstein
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2021-10-16 12:05 -0400 |
| Subject | Re: Clarification of Linz Ĥ Description [ correct halt deciding criteria ] |
| Message-ID | <BLCaJ.1497$ui1.475@fx15.iad> |
| In reply to | #40443 |
On 10/16/21 11:47 AM, olcott wrote: > On 10/16/2021 9:39 AM, Richard Damon wrote: >> On 10/15/21 11:22 PM, olcott wrote: >>> On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >>>> olcott <NoOne@NoWhere.com> writes: >>>> >>>>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >>>> >>>> Or, to put it more exactly, >>>> >>>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>>> >>>> and, if you kept the annotation that you dishonestly keep omitting, >>>> you'd see why no TM can behave in this way: >>>> >>>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>>> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >>>> >>> >>> -------------0----1--2 >>> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >>> if (and only if) (1) simulated by (0) applied to (2) does not halt. >>> >> >> >> WRONG (0) is NOT a UTM >> > > When-so-ever the pure simulation of a TM description by a simulating > halt decider never reaches its final state whether or not this > simulation is terminated by this simulating halt decider this simulating > halt decider correctly terminates this simulation and reports that this > TM description never halts on its input. Except that H is not a 'Pure Simulation", as it decides to abort it simulation, and thus is, by definition, a Pure Simulation. It is NOT q question of 'whether or not this simulation is terminated by this simulating halt decider", because BY DEFINITION this is a fixed fact. Your H provided DOES abort the simulation, and thus is NOT a UTM, and this makes H^ be a Halting Computation. You don't understand what you are 'proving'. All you have proved is that ANY variation of H that you design will also either abort its simulation too soon and not see the halting behavior that does exist in the resulting H^, or that H will never answer the question. No simulation that aborts its simulation proves non-halting by the fact that it did not reach a halting state. The question that the algorithm of H is SUPPOSED to answer is the halting behavior of the Computation that it is give, AS AN INDEPENDENT COMPUTATION, i.e. what it will do when run as a actual machine. > > Ĥ.q0 ⟨Ĥ0⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn // This is correct. > if (and only if) simulated ⟨Ĥ1⟩ applied to ⟨Ĥ2⟩ never reaches its final > state > WRONG. Since at H^.qx is NOT a UTM, then the simulation at H^.qx does NOT reflect that actual behavior of H^ applied to <H^>. The answer of that the algorithm of H is supposed to give is about the Halting Behavior of the Computation, AS AN INDEPENEDENT COMPUTATION. That Computatation when performed is to Halt with an answer, and thus, the right answer is Halting.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2021-10-16 17:27 +0100 |
| Subject | Re: Clarification of Linz Ĥ Description [ untainted decision ] |
| Message-ID | <87k0id7x4w.fsf@bsb.me.uk> |
| In reply to | #40434 |
olcott <NoOne@NoWhere.com> writes: > On 10/15/2021 4:31 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> ... Ĥ.qx applied to ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to Ĥ.qn >> Or, to put it more exactly, >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> and, if you kept the annotation that you dishonestly keep omitting, >> you'd see why no TM can behave in this way: >> Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn >> if (and only if) Ĥ applied to ⟨Ĥ⟩ does not halt. >> > > -------------0----1--2 > Ĥ.q0 ⟨Ĥ⟩ ⊦ Ĥ.qx ⟨Ĥ⟩ ⟨Ĥ⟩ ⊦ Ĥ.qn > if (and only if) (1) simulated by (0) applied to (2) does not halt. That's the wrong annotation. See the previous threads you abandoned if you have any interesting in learning why. -- Ben.
[toc] | [prev] | [next] | [standalone]
Page 8 of 17 — ← Prev page 1 … 6 7 [8] 9 10 … 17 Next page →
Back to top | Article view | comp.theory
csiph-web