Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #156164 > unrolled thread
| Started by | olcott <NoOne@NoWhere.com> |
|---|---|
| First post | 2020-10-27 14:30 -0500 |
| Last post | 2020-11-06 20:35 -0800 |
| Articles | 5 on this page of 45 — 11 participants |
Back to article view | Back to comp.lang.c
Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 14:30 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 13:46 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:02 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 15:13 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 14:34 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:23 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 22:49 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:25 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 00:31 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-27 23:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:50 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 21:09 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:18 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 10:29 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 11:05 -0500
Re: Architectural design of a halting problem solution André G. Isaak <agisaak@gm.invalid> - 2020-10-29 10:55 -0600
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 12:52 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 13:25 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:27 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:54 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 18:43 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 16:57 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-27 21:45 -0400
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:28 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-27 21:55 -0500
Re: Architectural design of a halting problem solution Richard Damon <Richard@Damon-Family.org> - 2020-10-28 09:04 -0400
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution David Brown <david.brown@hesbynett.no> - 2020-10-28 15:12 +0100
Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-28 14:13 +0100
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 18:18 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-28 17:54 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:28 -0500
Re: Architectural design of a halting problem solution olcott <NoOne@NoWhere.com> - 2020-10-29 07:35 -0500
Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:00 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-10-29 08:48 -0600
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 15:17 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) olcott <NoOne@NoWhere.com> - 2020-10-29 11:13 -0500
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Manfred <noname@add.invalid> - 2020-10-29 19:20 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-29 18:55 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) David Brown <david.brown@hesbynett.no> - 2020-10-30 11:02 +0100
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 10:52 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-10-30 19:47 +0000
Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 19:40 +0100
Re: Architectural design of a halting problem solution jenniferjeson35@gmail.com - 2020-11-06 20:35 -0800
Page 3 of 3 — ← Prev page 1 2 [3]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2020-10-30 11:02 +0100 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <rngob0$ach$1@dont-email.me> |
| In reply to | #156269 |
On 29/10/2020 19:55, Mike Terry wrote: > On 29/10/2020 18:20, Manfred wrote: >> On 10/29/2020 4:17 PM, Mike Terry wrote: >>> On 29/10/2020 14:48, Joe Pfeiffer wrote: >>>> Mostowski Collapse <janburse@fastmail.fm> writes: >>>> >>>>> For gods sacke stop cross posting on 4 newsgroups. >>>>> >>>>> Especially comp.lang.prolog doesn't make much sense. >>>>> >>>>> RAM/RASP is probably best housed on comp.theory. >>>> >>>> Many people have asked this, and have made no impact on him. The best >>>> you can do is not interact with him on newsgroups where his >>>> crackpottery >>>> is off-topic (sadly, to the best of my knoweldge there is no >>>> alt.crackpot newsgroup, as that is the only one where he would >>>> really be >>>> on-topic). >>>> >>> >>> There IS an alt.crackpot newsgroup! :) Of course PO will not post >>> there. >>> >>> Anyway, the obvious solution to all this is that if someone doesn't >>> want to be bothered by PO crackpottery in a particular newsgroup, they >>> should just filter PO's posts from those groups. I find that "ignore >>> subthread" works best, as it also ignores any replies to PO. >>> >>> Mike. >>> >> >> The problem is that some repliers use poor newsreaders that break thread >> ID consistency, and their replies manage to get through the "ignore >> subthread" killfile directive. >> So, the advise still holds that those repliers should better remove the >> language groups from their replies, unless they aim at landing into the >> killfile themselves. > > Interesting - I'm not familiar with that problem. Perhaps you give me a > couple of recent examples of such responses, and the newsgroup where > you're seeing them? (msgid values would be enough) > > On the sci.math newsgroup I use ignore subthread fairly extensively and > it pretty much eliminates posts by the well-known trolls/crackpots. > Sometimes I think "why am I seeing this post about TrollPoster who's in > my filter?". But when I look closer I see it's not down to poor > newsreaders - typically it is either that the post is merely /about/ > TrollPoster and not actually a reply to her, or it is a reply to a > TrollPoster post from such a long time ago that it's not recorded in my > local newsreader. (Neither of these is down to posters using poor > newsreaders.) > The cause of this is not a problem with newsreaders - it is a problem with Olcott. Roughly speaking (assuming I understand it myself), it goes like this. First, he makes a cross-posting to several off-topic groups. Then someone tries to be helpful by replying to him with these extra groups removed, leaving only comp.theory (this is normally the correct way to handle bad cross-posting). But when Olcott replies again, he adds the off-topic groups once more. As far as anyone (or any newsreader) viewing these other groups is concerned, that reply from Olcott has come from nowwhere - it is not a reply to anything in the group, and it therefore counts as a new thread.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-30 10:52 +0000 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <87wnz8ugsy.fsf@bsb.me.uk> |
| In reply to | #156287 |
David Brown <david.brown@hesbynett.no> writes: > On 29/10/2020 19:55, Mike Terry wrote: >> On 29/10/2020 18:20, Manfred wrote: >>> On 10/29/2020 4:17 PM, Mike Terry wrote: <cut> >>>> ... I find that "ignore >>>> subthread" works best, as it also ignores any replies to PO. >>> >>> The problem is that some repliers use poor newsreaders that break thread >>> ID consistency, and their replies manage to get through the "ignore >>> subthread" killfile directive. <cut> >> Interesting - I'm not familiar with that problem. Perhaps you give me a >> couple of recent examples of such responses, and the newsgroup where >> you're seeing them? (msgid values would be enough) <cut> > The cause of this is not a problem with newsreaders - it is a problem > with Olcott. Roughly speaking (assuming I understand it myself), it > goes like this. > > First, he makes a cross-posting to several off-topic groups. Then > someone tries to be helpful by replying to him with these extra groups > removed, leaving only comp.theory (this is normally the correct way to > handle bad cross-posting). But when Olcott replies again, he adds the > off-topic groups once more. As far as anyone (or any newsreader) > viewing these other groups is concerned, that reply from Olcott has come > from nowwhere - it is not a reply to anything in the group, and it > therefore counts as a new thread. That is a problem with newsreaders. They should be able to see that these "replies from nowhere" are indeed all in one thread -- a thread that simply has some missing posts. This was normal in the old days with slow and sometimes unreliable feeds, and old newsreaders can usually fill in a thread as posts arrive, and happily work with threads that are sparse. They should be able to do this even in when the subject header gets edited. Maybe some newer ones can't? -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2020-10-30 19:47 +0000 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution) |
| Message-ID | <slrnrporet.2ptb.grahn+nntp@frailea.sa.invalid> |
| In reply to | #156288 |
On Fri, 2020-10-30, Ben Bacarisse wrote: > David Brown <david.brown@hesbynett.no> writes: ... > As far as anyone (or any newsreader) >> viewing these other groups is concerned, that reply from Olcott has come >> from nowwhere - it is not a reply to anything in the group, and it >> therefore counts as a new thread. > > That is a problem with newsreaders. They should be able to see that > these "replies from nowhere" are indeed all in one thread -- a thread > that simply has some missing posts. This was normal in the old days > with slow and sometimes unreliable feeds, and old newsreaders can > usually fill in a thread as posts arrive, and happily work with threads > that are sparse. They should be able to do this even in when the > subject header gets edited. Yes. It's simple: the References: header has[1] an incomplete list of postings on the path back to the original. Given a set of postings (with Message-Id and References headers) you can build a set of trees, with gaps if necessary. The hardest part may be protecting yourself from malicious postings which try to form a non-tree DAG, or introduce cycles, or something. > Maybe some newer ones can't? /Jorgen [1] From memory. The RFC would tell. -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | Mostowski Collapse <janburse@fastmail.fm> |
|---|---|
| Date | 2020-10-29 19:40 +0100 |
| Subject | Re: Stop crossposting you imbecil spammer (Re: Architectural design of a halting problem solution |
| Message-ID | <rnf2br$u35$3@solani.org> |
| In reply to | #156164 |
For gods sacke stop cross posting on 4 newsgroups. Especially comp.lang.prolog doesn't make much sense. RAM/RASP is probably best housed on comp.theory. olcott schrieb: > I am a brainless mud turtle
[toc] | [prev] | [next] | [standalone]
| From | jenniferjeson35@gmail.com |
|---|---|
| Date | 2020-11-06 20:35 -0800 |
| Message-ID | <98aa4ba2-14a0-4b1d-9db4-679f396bd98eo@googlegroups.com> |
| In reply to | #156164 |
On Wednesday, October 28, 2020 at 1:00:35 AM UTC+5:30, olcott wrote: > Intuitively, a decider should be a Turing machine that given an input, > halts and either accepts or rejects, relaying its answer in one of many > equivalent ways, such as halting at an ACCEPT or REJECT state, or > leaving its answer on the output tape.Yuval Filmus > https://cs.stackexchange.com/questions/84433/what-is-decider > > Yuval Filmus top 0.04% overall Assistant Professor in the Department of > Computer Science at the Technion. > > It is common knowledge that a halt decider with the following > architectural design can be thwarted by an input program that does the > opposite of whatever the halt decider decides: > > The halt decider divides all of its inputs into: > (a) HALTS > (b) DOES_NOT_HALT > > This brand new architectural design cannot be thwarted by the > conventional self-referential halting problem trick. With this design > there is no input that can be shown to be undecidable: > > The halt decider that divides all of its inputs into: > (a) INPUT_PROGRAM_ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED > (b) INPUT_PROGRAM_HAS_TERMINATED > > The redefined halt decider UTM executes its subordinate UTM one state > transition at a time until it detects non-halting behavior or its > subordinate UTM has terminated normally. > > If the halt decider UTM detects non-halting behavior of its subordinate > UTM it simply stops executing the subordinate and transitions to its own > final state of ABORTED_NON_TERMINATING_BEHAVIOR. > > If the subordinate UTM terminates normally the halt decider UTM > transitions to its own final state of SUBORDINATE_HAS_TERMINATED. > > -- > Copyright 2020 Pete Olcott
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.lang.c
csiph-web