• on what even is the limit to decidability?

    From dart200@user7160@newsgrouper.org.invalid to comp.theory on Thu Dec 4 00:22:24 2025
    From Newsgroup: comp.theory

    keep in mind: all real TMs exist, undecidable machines do not exist.

    see, if we do not have a general halting decider then there must be some
    input machine L, which is the first machine in the full enumeration
    who's halting semantics cannot be decided up for some kind of semantics
    (like halting).

    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none of
    those machines could be *real* machine L.

    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property that
    it cannot be decided upon by a halting decider ... but then next step in undecidable proofs is to declare the machine's non-existence, because an undecidable machine is also not a deterministic machine, which
    ultimately contradicts the fact that this limit machine L was suppose to actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think i'm
    wrong this time???
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Thu Dec 4 10:49:14 2025
    From Newsgroup: comp.theory

    dart200 kirjoitti 4.12.2025 klo 10.22:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    see, if we do not have a general halting decider then there must be some input machine L, which is the first machine in the full enumeration
    who's halting semantics cannot be decided up for some kind of semantics (like halting).

    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none of those machines could be *real* machine L.

    Not true. There are proofs of undecidability of Turing's circularity
    that son't use hypothetical machines but only quantification over
    Turing machines.
    --
    Mikko
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Thu Dec 4 01:10:06 2025
    From Newsgroup: comp.theory

    On 12/4/25 12:49 AM, Mikko wrote:
    dart200 kirjoitti 4.12.2025 klo 10.22:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some kind
    of semantics (like halting).

    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not true. There are proofs of undecidability of Turing's circularity
    that son't use hypothetical machines but only quantification over
    Turing machines.

    like what example?

    and u avoided most of the post
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Fri Dec 5 12:26:37 2025
    From Newsgroup: comp.theory

    dart200 kirjoitti 4.12.2025 klo 11.10:
    On 12/4/25 12:49 AM, Mikko wrote:
    dart200 kirjoitti 4.12.2025 klo 10.22:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not true. There are proofs of undecidability of Turing's circularity
    that son't use hypothetical machines but only quantification over
    Turing machines.

    like what example?

    The claim to be proven is: Every Turing machine fails as Turing
    circulate decider.

    One direct proof can be suumarized as:

    For every Turing machine H one can sonstruct a counter example M so
    that if H(M, M) accepts then M(M) runs forever and keeps writing
    final symbols but if H(M, M) rejects then M(M) halts.

    If H(M, M) neither accepts nor rejects it is not a Turing circularity
    (nor any other) decider. If H(M, M) accepts then M(M) is not Turing
    circular so H(M, M) is not a Turing circularity decider. If H(M, M)
    rejects then M(M) is Turing circuilar so H(M, M) is not a Turing
    circularity decider.

    So for H is not a Turing circularity decider.

    Because the proof was about every Turing machine H the conclusion is
    that no Turing machine is a Turing circularity decider.
    --
    Mikko
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory on Fri Dec 5 20:31:00 2025
    From Newsgroup: comp.theory

    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be some input machine L, which is the first machine in the full enumeration
    who's halting semantics cannot be decided up for some kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and
    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always answer
    for every input their given answer, ONE of those MUST be right, so there
    can not be a single specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property that
    it cannot be decided upon by a halting decider ... but then next step in undecidable proofs is to declare the machine's non-existence, because an undecidable machine is also not a deterministic machine, which
    ultimately contradicts the fact that this limit machine L was suppose to actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how are TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly irreconcilable nonsense. but bring it on my dudes, how do u think i'm
    wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced the intelegence of the world.

    The problem isn't that some given machine can't be decided if it halts
    or not, but that for every machine that claims to be a decider, there
    will be an input for which it gives the wrong answer, or it fails to
    answers.

    Now, a side effect of this fact, it becomes true that there exists some machine/input combinations that we can not know if they halt or not, but another side effect of this is we can't tell if a given machine is one
    of them, as by definition any machine we can't know if it halts or not,
    must be non-halting, as any halting machine can be proven to halt, just
    by running it for enough steps.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Fri Dec 5 23:34:06 2025
    From Newsgroup: comp.theory

    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some kind
    of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    so what is the *real* example of a machine that demonstrably cannot be
    decided upon???

    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of such machines that certainly can exist ... ???

    but like ok, if ur so certain they *must* exist, what is an example of
    one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always answer
    for every input their given answer, ONE of those MUST be right, so there
    can not be a single specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then next
    step in undecidable proofs is to declare the machine's non-existence,
    because an undecidable machine is also not a deterministic machine,
    which ultimately contradicts the fact that this limit machine L was
    suppose to actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think i'm
    wrong this time???


    And your problem he is you are working on the wrong problem, because "someone" has spewed out so much misinformaiton that he has reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    unlike polcott, i'm personally not sure what to do about godel's incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    i'm trying to address the theory of computing, not math as a whole


    The problem isn't that some given machine can't be decided if it halts
    or not, but that for every machine that claims to be a decider, there
    will be an input for which it gives the wrong answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this behavior demonstrably happens???

    sure you can throw around hypothetical examples of undecidable machines
    all day long, i've spent a lot of time considering them myself, probably
    more than you actually...

    but like what about a *real* machine, that *actually exists*???


    Now, a side effect of this fact, it becomes true that there exists some machine/input combinations that we can not know if they halt or not, but another side effect of this is we can't tell if a given machine is one
    of them, as by definition any machine we can't know if it halts or not,
    must be non-halting, as any halting machine can be proven to halt, just
    by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day
    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sat Dec 6 06:16:49 2025
    From Newsgroup: comp.theory

    On 12/6/2025 1:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    so what is the *real* example of a machine that demonstrably cannot be decided upon???

    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of such machines that certainly can exist ... ???

    but like ok, if ur so certain they *must* exist, what is an example of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be right,
    so there can not be a single specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then next
    step in undecidable proofs is to declare the machine's non-existence,
    because an undecidable machine is also not a deterministic machine,
    which ultimately contradicts the fact that this limit machine L was
    suppose to actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think i'm
    wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    unlike polcott, i'm personally not sure what to do about godel's incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    i'm trying to address the theory of computing, not math as a whole


    The problem isn't that some given machine can't be decided if it halts
    or not, but that for every machine that claims to be a decider, there
    will be an input for which it gives the wrong answer, or it fails to
    answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this behavior demonstrably happens???

    sure you can throw around hypothetical examples of undecidable machines
    all day long, i've spent a lot of time considering them myself, probably more than you actually...

    but like what about a *real* machine, that *actually exists*???


    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be
    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    It looks like I am first to have fully refuted the Halting Problem
    and Gödel's Incompleteness. They are both in the same paper.

    https://www.researchgate.net/publication/398375553_Halting_Problem_Proof_Counter-Example_is_Isomorphic_to_the_Liar_Paradox
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sat Dec 6 08:41:13 2025
    From Newsgroup: comp.theory

    On 12/6/25 4:16 AM, olcott wrote:
    On 12/6/2025 1:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    so what is the *real* example of a machine that demonstrably cannot be
    decided upon???

    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    but like ok, if ur so certain they *must* exist, what is an example of
    one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get wrong. >>>
    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    i'm trying to address the theory of computing, not math as a whole


    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a decider,
    there will be an input for which it gives the wrong answer, or it
    fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    but like what about a *real* machine, that *actually exists*???


    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be
    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    It looks like I am first to have fully refuted the Halting Problem
    and Gödel's Incompleteness. They are both in the same paper.

    https://www.researchgate.net/ publication/398375553_Halting_Problem_Proof_Counter- Example_is_Isomorphic_to_the_Liar_Paradox


    i'm not really refuting the halting problem there, rather presenting a fundamental contradiction with rejecting the premise of a general
    halting deciders, namely that non-existent machines would exist

    it doesn't impact godel's claims because the argument is at the level of computing machines, not more fundamentals claims
    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sat Dec 6 11:00:30 2025
    From Newsgroup: comp.theory

    On 12/6/2025 10:41 AM, dart200 wrote:
    On 12/6/25 4:16 AM, olcott wrote:
    On 12/6/2025 1:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not
    exist a "Program" (as defined by the theory, which are finite
    definite algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be >>>>> some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    so what is the *real* example of a machine that demonstrably cannot
    be decided upon???

    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    but like ok, if ur so certain they *must* exist, what is an example
    of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so
    none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a
    real machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that
    then cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine
    L that can't be decided, and in fact, there can't be such a machine,
    as there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get
    wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding. >>>>

    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property >>>>> that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM >>>>> semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots
    that i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet
    seen eye to eye enough for much influence to happen either way

    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    i'm trying to address the theory of computing, not math as a whole


    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong answer,
    or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    but like what about a *real* machine, that *actually exists*???


    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know
    if it halts or not, must be non-halting, as any halting machine can
    be proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last
    day


    It looks like I am first to have fully refuted the Halting Problem
    and Gödel's Incompleteness. They are both in the same paper.

    https://www.researchgate.net/
    publication/398375553_Halting_Problem_Proof_Counter-
    Example_is_Isomorphic_to_the_Liar_Paradox


    i'm not really refuting the halting problem there, rather presenting a fundamental contradiction with rejecting the premise of a general
    halting deciders, namely that non-existent machines would exist

    it doesn't impact godel's claims because the argument is at the level of computing machines, not more fundamentals claims


    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This can be directly implemented to make
    LLM systems much more reliable.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sat Dec 6 11:29:38 2025
    From Newsgroup: comp.theory

    On 12/6/2025 6:16 AM, olcott wrote:
    On 12/6/2025 1:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    so what is the *real* example of a machine that demonstrably cannot be
    decided upon???

    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    but like ok, if ur so certain they *must* exist, what is an example of
    one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get wrong. >>>
    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    i'm trying to address the theory of computing, not math as a whole


    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a decider,
    there will be an input for which it gives the wrong answer, or it
    fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    but like what about a *real* machine, that *actually exists*???


    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be
    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    It looks like I am first to have fully refuted the Halting Problem
    and Gödel's Incompleteness. They are both in the same paper.

    https://www.researchgate.net/ publication/398375553_Halting_Problem_Proof_Counter- Example_is_Isomorphic_to_the_Liar_Paradox


    Halting Problem Proof Counter-Example is Isomorphic to the Liar Paradox https://philpapers.org/archive/OLCHPP-3.pdf
    Same file without broken link
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 13:44:39 2025
    From Newsgroup: comp.theory

    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably cannot be decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an example of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and want to
    claim to be a correct halt decider, I can make a machine and input to
    give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be right,
    so there can not be a single specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then next
    step in undecidable proofs is to declare the machine's non-existence,
    because an undecidable machine is also not a deterministic machine,
    which ultimately contradicts the fact that this limit machine L was
    suppose to actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think i'm
    wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    Because it seems, you don't understand what the actual problem is, or
    how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it halts
    or not, but that for every machine that claims to be a decider, there
    will be an input for which it gives the wrong answer, or it fails to
    answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are you
    asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is universally correct, I can make an input that shows the claim to be wrong.

    Your problem is you have the question backwards. It isn't that there is
    a machine that no machine can get the right answer for, as that is
    clearly wrong, but there is no machine that can always get the right answer.

    I side affect of this, is that there WILL be machines that we can not
    know the answer for, but we can't know if a given machine is one of
    them, as knowing that lets you know what the answer is, as the only
    unknowable halting state machines are non-halting, as ALL halting
    machine can be shown to be halting by just running them till the halt.


    sure you can throw around hypothetical examples of undecidable machines
    all day long, i've spent a lot of time considering them myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least possibly, I
    am not sure if we can actually prove such an existance, only its
    potential to exist)



    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be
    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    No, the problem is you keep on looking for that which the theory says is unknowable. We can show that there are machines that we can not know the halting property of, but we can never know if a machine is in that class.

    We can know that no machine can be a correct decider, as for any claimed decider, we can show an input that it gets wrong. Thus no universally
    correct deciders, which IS the question possed by the problem.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 13:22:34 2025
    From Newsgroup: comp.theory

    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    Where do you see that?

    bro, none of the hypothetical machines talked about in undecidable
    proofs are executable, because their result cannot be decided

    what does machine: und = () -> halts(und) && loop_forever() do when
    executed? if that cannot be decided, then it cannot be executed either, because execution requires a decision on the next state, for any given
    current state.

    therefore the logic as written is not a real machine, as all *real*
    machines must be executable



    so what is the *real* example of a machine that demonstrably cannot be
    decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.

    it's not a straw man, it's a consequence of declaring that undecidable machines exist preventing a general halting decider

    ok ... so what is the first *real* machine that an attempt at creating a general halting decider cannot decide on ... ???

    certainly there must be some kind maximally effective halting decider,
    what is the first *real* *executable* machine U that said maximally
    effective decision algorithm cannot decide upon??? what does that look
    like?

    because it can't look any of the machines discussed in the proofs ...
    because those machines are all not executable, and therefore not real,
    and therefore cannot manifest in a full enumeration of turing machines



    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.

    ur not recognizing the consequences of accepting the proofs as true



    but like ok, if ur so certain they *must* exist, what is an example of
    one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and want to claim to be a correct halt decider, I can make a machine and input to
    give to it that it will get wrong.

    right but can any of those machines actually run???

    cause if not they don't exist.

    and if so, they cannot actually appear in the full enumeration of machine,

    and therefor a general halting decider, in regards to *real* machines,
    does not actually have to deal with them


    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get wrong. >>>
    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    Because it seems, you don't understand what the actual problem is, or
    how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a decider,
    there will be an input for which it gives the wrong answer, or it
    fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is universally correct, I can make an input that shows the claim to be wrong.

    Your problem is you have the question backwards. It isn't that there is
    a machine that no machine can get the right answer for, as that is
    clearly wrong, but there is no machine that can always get the right
    answer.

    I side affect of this, is that there WILL be machines that we can not
    know the answer for, but we can't know if a given machine is one of
    them, as knowing that lets you know what the answer is, as the only unknowable halting state machines are non-halting, as ALL halting
    machine can be shown to be halting by just running them till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least possibly, I
    am not sure if we can actually prove such an existance, only its
    potential to exist)



    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be
    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    No, the problem is you keep on looking for that which the theory says is unknowable. We can show that there are machines that we can not know the halting property of, but we can never know if a machine is in that class.

    We can know that no machine can be a correct decider, as for any claimed decider, we can show an input that it gets wrong. Thus no universally correct deciders, which IS the question possed by the problem.
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 13:41:05 2025
    From Newsgroup: comp.theory

    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not exist
    a "Program" (as defined by the theory, which are finite definite
    algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be
    some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably cannot be
    decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an example of
    one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-hypothetical
    forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and want to claim to be a correct halt decider, I can make a machine and input to
    give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so none
    of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a real
    machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that then
    cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine L
    that can't be decided, and in fact, there can't be such a machine, as
    there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get wrong. >>>
    That idea is just part of Peter Olcotts stupidity and misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property
    that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots that
    i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet seen
    eye to eye enough for much influence to happen either way

    Because it seems, you don't understand what the actual problem is, or
    how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a decider,
    there will be an input for which it gives the wrong answer, or it
    fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is universally correct, I can make an input that shows the claim to be wrong.

    Your problem is you have the question backwards. It isn't that there is
    a machine that no machine can get the right answer for, as that is
    clearly wrong, but there is no machine that can always get the right
    answer.

    I side affect of this, is that there WILL be machines that we can not
    know the answer for, but we can't know if a given machine is one of
    them, as knowing that lets you know what the answer is, as the only unknowable halting state machines are non-halting, as ALL halting
    machine can be shown to be halting by just running them till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least possibly, I
    am not sure if we can actually prove such an existance, only its
    potential to exist)



    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know if
    it halts or not, must be non-halting, as any halting machine can be

    bruh ... do u not recognize the inherent contradiction in say in all
    machines which can't know the halting of ... must therefore be
    non-halting???

    like u literally just decided what they all must be after claiming they
    are machiens which we cannot know the halting status of ...

    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last day


    No, the problem is you keep on looking for that which the theory says is unknowable. We can show that there are machines that we can not know the halting property of, but we can never know if a machine is in that class.

    We can know that no machine can be a correct decider, as for any claimed decider, we can show an input that it gets wrong. Thus no universally correct deciders, which IS the question possed by the problem.
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 17:21:16 2025
    From Newsgroup: comp.theory

    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    But "Undecidability" isn't about a particular "machine", but about a
    general problem, a total MAPPING of the (infinite) set of inputs to
    there respective output. It is the statement that there can not
    exist a "Program" (as defined by the theory, which are finite
    definite algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the
    problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible
    input machine).


    see, if we do not have a general halting decider then there must be >>>>> some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some
    kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a
    machine that it will give a wrong answer to (or fail to answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines that
    could not be decided upon, not only do not exist, they actually could
    not exist... and therefore they *do not* and *will not* come up in a
    full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably cannot
    be decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an example
    of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and want
    to claim to be a correct halt decider, I can make a machine and input
    to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on which
    machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so
    none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a
    real machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that
    then cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine
    L that can't be decided, and in fact, there can't be such a machine,
    as there are two poor deciders, we can all Yes, and No, that always
    answer for every input their given answer, ONE of those MUST be
    right, so there can not be a single specific machine that all get
    wrong.

    That idea is just part of Peter Olcotts stupidity and misunderstanding. >>>>

    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this property >>>>> that it cannot be decided upon by a halting decider ... but then
    next step in undecidable proofs is to declare the machine's non-
    existence, because an undecidable machine is also not a
    deterministic machine, which ultimately contradicts the fact that
    this limit machine L was suppose to actually *exist*, so how could
    it ever exist?

    and if the limit machine L does not actually exist, then how are TM >>>>> semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think
    i'm wrong this time???


    And your problem he is you are working on the wrong problem, because
    "someone" has spewed out so much misinformaiton that he has reduced
    the intelligence of the world.

    no bro, please read this carefully: these really are my own thots
    that i've mostly developed on my own without much external validation
    anywhere. polcott is an interesting character, but we haven't yet
    seen eye to eye enough for much influence to happen either way

    Because it seems, you don't understand what the actual problem is, or
    how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the
    Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong answer,
    or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are you
    asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is
    universally correct, I can make an input that shows the claim to be
    wrong.

    Your problem is you have the question backwards. It isn't that there
    is a machine that no machine can get the right answer for, as that is
    clearly wrong, but there is no machine that can always get the right
    answer.

    I side affect of this, is that there WILL be machines that we can not
    know the answer for, but we can't know if a given machine is one of
    them, as knowing that lets you know what the answer is, as the only
    unknowable halting state machines are non-halting, as ALL halting
    machine can be shown to be halting by just running them till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least possibly,
    I am not sure if we can actually prove such an existance, only its
    potential to exist)



    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt or
    not, but another side effect of this is we can't tell if a given
    machine is one of them, as by definition any machine we can't know
    if it halts or not, must be non-halting, as any halting machine can be

    bruh ... do u not recognize the inherent contradiction in say in all machines which can't know the halting of ... must therefore be non- halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it
    enough steps, as there must be some finite number of steps to run it
    till it halts, as that is the DEFINITION of Halting, and a finite number
    of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming they
    are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status. All we
    can know is we haven't found the status YET. Not knowN can be either
    halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone almost
    entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the last
    day


    No, the problem is you keep on looking for that which the theory says
    is unknowable. We can show that there are machines that we can not
    know the halting property of, but we can never know if a machine is in
    that class.

    We can know that no machine can be a correct decider, as for any
    claimed decider, we can show an input that it gets wrong. Thus no
    universally correct deciders, which IS the question possed by the
    problem.



    One way of looking at this, is we can take all machines, and we know
    that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3 categories
    (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as running
    them enough (but for a still finite number of steps) will reach the halt state, and thus it not yet being know is just because we haven't run it
    far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there exists a proof, to be discovered, that proves that it will not halt.

    For the Unknowable machines, they can't be Halting, as we showed that
    all halting machines are knowable by just running them long enough.
    There is nothing that says we must be able to find a proof of
    non-halting, and the fact that Halting is non-decidable seems to imply
    that this category can't be empty, or our decider just needs to apply
    the appropriate proof of non-halting to correctly decide. The fact that
    there are an infinite number of possible proofs may allow this category
    to be empty, but I am not sure you can prove that.

    As I point out, It can't be possible to prove that a machine is in this unknowable category, as only non-halting machines can be unknowable, and
    thus a proof that a machine is in this category can't be correct, or the
    whole logic system is proven inconsistant. This is similar to the point
    that Godel uses in his incompleteness proof, as if you could prove the sentence true, that proof creates the counter example that makes the
    sentence false, thus no proof can exist.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 16:57:42 2025
    From Newsgroup: comp.theory

    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.theory on Sat Dec 6 18:43:43 2025
    From Newsgroup: comp.theory

    On 12/4/2025 12:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist.

    Can you predict a TRNG?

    [...]
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 6 22:07:17 2025
    From Newsgroup: comp.theory

    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in Computation Theory, whicb is what "Decidability" is defined in.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sun Dec 7 13:28:43 2025
    From Newsgroup: comp.theory

    On 2025-12-06 at 14:16 olcott wrote a message with the subjec line
    "I am first to have fully refuted the Halting Problem".

    This subject line does not make sense. The expression "refuted the
    Halting Problem" does not mean anything. To refute a claim means
    to prove that the claim is false. But a problem does not claim and
    is neither true or false. Therefore it is a category error to say
    "refuted the Halting Problem".
    --
    Mikko
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sun Dec 7 14:07:28 2025
    From Newsgroup: comp.theory

    olcott kirjoitti 6.12.2025 klo 19.00:

    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.
    You should first present a "proof of concept" version with very small
    scope. For example, you could restrict to the following:

    The language has, in addition to the symbols of logic with equivalence,
    a constant symbol 1, a unary operator ', and a binary operator symbol *.

    The basic truths are:

    1. for every a, b, c: (a * b) * c = a * (b * c)
    2. for every a: 1 * a = a and a * 1 = a
    3. for every a: a * a' = 1 and a' * a = 1
    4. for every a and b: a * b = b * a

    Other truths are what can be inferred from above.

    When you have solved that a good next step is to remove the basic truth
    4. Then you can advance to systems with more functions and then to
    systems that cover wider ranges of topics.
    --
    Mikko
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 13:32:45 2025
    From Newsgroup: comp.theory

    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    1 HOME
    5 PRINT "ct_dr_fuzz lol. ;^)"
    6 P0 = 0
    7 P1 = 0

    10 REM Fuzzer... ;^)
    20 A$ = "NOPE!"
    30 IF RND(1) < .5 THEN A$ = "YES"

    100 REM INPUT "Shall DD halt or not? " ; A$
    110 PRINT "Shall DD halt or not? " ; A$
    200 IF A$ = "YES" GOTO 666
    300 P0 = P0 + 1
    400 IF P0 > 0 AND P1 > 0 GOTO 1000
    500 GOTO 10

    666 PRINT "OK!"
    667 P1 = P1 + 1
    700 PRINT "NON_HALT P0 = "; P0
    710 PRINT "HALT P1 = "; P1
    720 IF P0 > 0 AND P1 > 0 GOTO 1000
    730 PRINT "ALL PATHS FAILED TO BE HIT!"
    740 GOTO 10


    1000 REM Fin
    1010 PRINT "FIN... All paths hit."
    1020 PRINT "NON_HALT P0 = "; P0
    1030 PRINT "HALT P1 = "; P1
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 13:59:44 2025
    From Newsgroup: comp.theory

    On 12/6/25 2:21 PM, Richard Damon wrote:
    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist. >>>>>
    But "Undecidability" isn't about a particular "machine", but about
    a general problem, a total MAPPING of the (infinite) set of inputs
    to there respective output. It is the statement that there can not
    exist a "Program" (as defined by the theory, which are finite
    definite algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, the >>>>> problem is to be able to universally give that answer correctly in
    finite time. THAT can't be done (universally, i.e. for any possible >>>>> input machine).


    see, if we do not have a general halting decider then there must
    be some input machine L, which is the first machine in the full
    enumeration who's halting semantics cannot be decided up for some >>>>>> kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is a >>>>> machine that it will give a wrong answer to (or fail to answer), and >>>>
    let me boil this down:

    all "proven" examples of what are actually hypothetical machines
    that could not be decided upon, not only do not exist, they actually
    could not exist... and therefore they *do not* and *will not* come
    up in a full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably cannot
    be decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine that
    cannot exist, but from that we can just extrapolate *real* forms of
    such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an example
    of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and want
    to claim to be a correct halt decider, I can make a machine and input
    to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on which >>>>> machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so
    none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a
    real machine if the decider it was built on was an actual machine.


    so what is this proposed non-hypothetical *real* machine L that
    then cannot be decided?

    But that isn't the claim. It isn't that there is a specific machine >>>>> L that can't be decided, and in fact, there can't be such a
    machine, as there are two poor deciders, we can all Yes, and No,
    that always answer for every input their given answer, ONE of those >>>>> MUST be right, so there can not be a single specific machine that
    all get wrong.

    That idea is just part of Peter Olcotts stupidity and
    misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this
    property that it cannot be decided upon by a halting decider ...
    but then next step in undecidable proofs is to declare the
    machine's non- existence, because an undecidable machine is also
    not a deterministic machine, which ultimately contradicts the fact >>>>>> that this limit machine L was suppose to actually *exist*, so how >>>>>> could it ever exist?

    and if the limit machine L does not actually exist, then how are
    TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think >>>>>> i'm wrong this time???


    And your problem he is you are working on the wrong problem,
    because "someone" has spewed out so much misinformaiton that he has >>>>> reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own thots
    that i've mostly developed on my own without much external
    validation anywhere. polcott is an interesting character, but we
    haven't yet seen eye to eye enough for much influence to happen
    either way

    Because it seems, you don't understand what the actual problem is, or
    how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's just
    outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the
    Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong
    answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are
    you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is
    universally correct, I can make an input that shows the claim to be
    wrong.

    Your problem is you have the question backwards. It isn't that there
    is a machine that no machine can get the right answer for, as that is
    clearly wrong, but there is no machine that can always get the right
    answer.

    I side affect of this, is that there WILL be machines that we can not
    know the answer for, but we can't know if a given machine is one of
    them, as knowing that lets you know what the answer is, as the only
    unknowable halting state machines are non-halting, as ALL halting
    machine can be shown to be halting by just running them till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least
    possibly, I am not sure if we can actually prove such an existance,
    only its potential to exist)



    Now, a side effect of this fact, it becomes true that there exists
    some machine/input combinations that we can not know if they halt
    or not, but another side effect of this is we can't tell if a given >>>>> machine is one of them, as by definition any machine we can't know
    if it halts or not, must be non-halting, as any halting machine can be >>
    bruh ... do u not recognize the inherent contradiction in say in all
    machines which can't know the halting of ... must therefore be non-
    halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it
    enough steps, as there must be some finite number of steps to run it
    till it halts, as that is the DEFINITION of Halting, and a finite number
    of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming
    they are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status. All we
    can know is we haven't found the status YET. Not knowN can be either
    halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone
    almost entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the
    last day


    No, the problem is you keep on looking for that which the theory says
    is unknowable. We can show that there are machines that we can not
    know the halting property of, but we can never know if a machine is
    in that class.

    We can know that no machine can be a correct decider, as for any
    claimed decider, we can show an input that it gets wrong. Thus no
    universally correct deciders, which IS the question possed by the
    problem.



    One way of looking at this, is we can take all machines, and we know
    that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3 categories
    (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as running
    them enough (but for a still finite number of steps) will reach the halt state, and thus it not yet being know is just because we haven't run it
    far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there exists a proof, to be discovered, that proves that it will not halt.

    For the Unknowable machines, they can't be Halting, as we showed that
    all halting machines are knowable by just running them long enough.
    There is nothing that says we must be able to find a proof of non-
    halting, and the fact that Halting is non-decidable seems to imply that
    this category can't be empty, or our decider just needs to apply the appropriate proof of non-halting to correctly decide. The fact that
    there are an infinite number of possible proofs may allow this category
    to be empty, but I am not sure you can prove that.

    As I point out, It can't be possible to prove that a machine is in this unknowable category, as only non-halting machines can be unknowable, and thus a proof that a machine is in this category can't be correct, or the whole logic system is proven inconsistant. This is similar to the point
    that Godel uses in his incompleteness proof, as if you could prove the sentence true, that proof creates the counter example that makes the sentence false, thus no proof can exist.

    great so u've ended up in the situation of certainly believing in
    "unknowable" (yet certainly non-halting) machines,

    that you can't even prove exist,

    except for apparent demonstration with hypothetical machines that then
    can't even exist,

    i... just...

    /that is fucking crazy bro/

    *there has to be some machine L at which "unknowability" can be pointed
    to*, why?? because we can partially decide this function, then there
    must be some maximally partial decidable, and with that there *must* be
    some *real* *existent* machine L which that maximally partial
    decidability "breaks down" and cannot be decided upon!

    if ur theory can't tolerate that, THEN ITS BROKEN NUMBNUTS

    which it can't because if u could point that machine L, then according
    to u we'd know it was a non-halting machine, which contradicts it being machine L. so machine L, the first point were maximum decidability
    breaks down can't even be known!

    you can't even tell me what form a machine looks like when it's
    unknowable, because none of the arguments for undecidable machines
    utilize machines *that actually exist*, and furthermore, if u could
    point to one of these "unknowable" machines it would cease to be
    unknowable!!

    i'm sorry, this is like fucking believing in mathematical ghosts bro,

    LOGIC HAS LEFT THE DISCUSSION
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 17:41:46 2025
    From Newsgroup: comp.theory

    On 12/7/25 4:59 PM, dart200 wrote:
    On 12/6/25 2:21 PM, Richard Damon wrote:
    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not exist. >>>>>>
    But "Undecidability" isn't about a particular "machine", but about >>>>>> a general problem, a total MAPPING of the (infinite) set of inputs >>>>>> to there respective output. It is the statement that there can not >>>>>> exist a "Program" (as defined by the theory, which are finite
    definite algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not,
    the problem is to be able to universally give that answer
    correctly in finite time. THAT can't be done (universally, i.e.
    for any possible input machine).


    see, if we do not have a general halting decider then there must >>>>>>> be some input machine L, which is the first machine in the full >>>>>>> enumeration who's halting semantics cannot be decided up for some >>>>>>> kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is >>>>>> a machine that it will give a wrong answer to (or fail to answer), >>>>>> and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines
    that could not be decided upon, not only do not exist, they
    actually could not exist... and therefore they *do not* and *will
    not* come up in a full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably cannot >>>>> be decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine that >>>>> cannot exist, but from that we can just extrapolate *real* forms of >>>>> such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an example >>>>> of one???

    i'm not buying this whole if hypotheticals can be presented, then
    certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and
    want to claim to be a correct halt decider, I can make a machine and
    input to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on
    which machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely
    hypothetical machines, which then are declared to not exist, so >>>>>>> none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a
    real machine if the decider it was built on was an actual machine. >>>>>>

    so what is this proposed non-hypothetical *real* machine L that >>>>>>> then cannot be decided?

    But that isn't the claim. It isn't that there is a specific
    machine L that can't be decided, and in fact, there can't be such >>>>>> a machine, as there are two poor deciders, we can all Yes, and No, >>>>>> that always answer for every input their given answer, ONE of
    those MUST be right, so there can not be a single specific machine >>>>>> that all get wrong.

    That idea is just part of Peter Olcotts stupidity and
    misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this
    property that it cannot be decided upon by a halting decider ... >>>>>>> but then next step in undecidable proofs is to declare the
    machine's non- existence, because an undecidable machine is also >>>>>>> not a deterministic machine, which ultimately contradicts the
    fact that this limit machine L was suppose to actually *exist*, >>>>>>> so how could it ever exist?

    and if the limit machine L does not actually exist, then how are >>>>>>> TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly >>>>>>> irreconcilable nonsense. but bring it on my dudes, how do u think >>>>>>> i'm wrong this time???


    And your problem he is you are working on the wrong problem,
    because "someone" has spewed out so much misinformaiton that he
    has reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own thots
    that i've mostly developed on my own without much external
    validation anywhere. polcott is an interesting character, but we
    haven't yet seen eye to eye enough for much influence to happen
    either way

    Because it seems, you don't understand what the actual problem is,
    or how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's
    just outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the
    Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it
    halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong
    answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are
    you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim is
    universally correct, I can make an input that shows the claim to be
    wrong.

    Your problem is you have the question backwards. It isn't that there
    is a machine that no machine can get the right answer for, as that
    is clearly wrong, but there is no machine that can always get the
    right answer.

    I side affect of this, is that there WILL be machines that we can
    not know the answer for, but we can't know if a given machine is one
    of them, as knowing that lets you know what the answer is, as the
    only unknowable halting state machines are non-halting, as ALL
    halting machine can be shown to be halting by just running them till
    the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we can't
    know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least
    possibly, I am not sure if we can actually prove such an existance,
    only its potential to exist)



    Now, a side effect of this fact, it becomes true that there exists >>>>>> some machine/input combinations that we can not know if they halt >>>>>> or not, but another side effect of this is we can't tell if a
    given machine is one of them, as by definition any machine we
    can't know if it halts or not, must be non-halting, as any halting >>>>>> machine can be

    bruh ... do u not recognize the inherent contradiction in say in all
    machines which can't know the halting of ... must therefore be non-
    halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it
    enough steps, as there must be some finite number of steps to run it
    till it halts, as that is the DEFINITION of Halting, and a finite
    number of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming
    they are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status. All
    we can know is we haven't found the status YET. Not knowN can be
    either halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone
    almost entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the
    last day


    No, the problem is you keep on looking for that which the theory
    says is unknowable. We can show that there are machines that we can
    not know the halting property of, but we can never know if a machine
    is in that class.

    We can know that no machine can be a correct decider, as for any
    claimed decider, we can show an input that it gets wrong. Thus no
    universally correct deciders, which IS the question possed by the
    problem.



    One way of looking at this, is we can take all machines, and we know
    that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3 categories
    (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as running
    them enough (but for a still finite number of steps) will reach the
    halt state, and thus it not yet being know is just because we haven't
    run it far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there exists
    a proof, to be discovered, that proves that it will not halt.

    For the Unknowable machines, they can't be Halting, as we showed that
    all halting machines are knowable by just running them long enough.
    There is nothing that says we must be able to find a proof of non-
    halting, and the fact that Halting is non-decidable seems to imply
    that this category can't be empty, or our decider just needs to apply
    the appropriate proof of non-halting to correctly decide. The fact
    that there are an infinite number of possible proofs may allow this
    category to be empty, but I am not sure you can prove that.

    As I point out, It can't be possible to prove that a machine is in
    this unknowable category, as only non-halting machines can be
    unknowable, and thus a proof that a machine is in this category can't
    be correct, or the whole logic system is proven inconsistant. This is
    similar to the point that Godel uses in his incompleteness proof, as
    if you could prove the sentence true, that proof creates the counter
    example that makes the sentence false, thus no proof can exist.

    great so u've ended up in the situation of certainly believing in "unknowable" (yet certainly non-halting) machines,

    that you can't even prove exist,

    I don't need to prove they exist, as that isn't what the problem is
    talking about.

    Undecidabiity just means that you can't make a decider that gets all the answers right, and THAT is fully provable with a simple proof.

    The meta-logic to show that there exists some machines that we CAN'T
    know, is a different problem, and much more complicated.


    except for apparent demonstration with hypothetical machines that then
    can't even exist,

    i... just...

    /that is fucking crazy bro/

    It is the reasonable outcome of the fact that is reasonable to prove,
    that there can never be a machine that decides all input correctly, and
    thus the Halting Problem is undecidable.


    *there has to be some machine L at which "unknowability" can be pointed
    to*, why?? because we can partially decide this function, then there
    must be some maximally partial decidable, and with that there *must* be
    some *real* *existent* machine L which that maximally partial
    decidability "breaks down" and cannot be decided upon!

    Nope. To prove that it is undecidable, you just need to prove that no
    decider gets all answers right.

    It is theoretically conceivable that there could be a proof that can be discovered, but only after a potentially infinite search, for every machine.


    if ur theory can't tolerate that, THEN ITS BROKEN NUMBNUTS

    My theory can't tolerate what? That we might be able to know the answer
    to every possible instance, but that knowledge can't come from a finite machine?



    which it can't because if u could point that machine L, then according
    to u we'd know it was a non-halting machine, which contradicts it being machine L. so machine L, the first point were maximum decidability
    breaks down can't even be known!

    Right, we can't possible KNOW that a given machine is unknowable. As the meta-information defines the value of the question.

    Nothing wrong with that, it is just a property of unknowable things.


    you can't even tell me what form a machine looks like when it's
    unknowable, because none of the arguments for undecidable machines
    utilize machines *that actually exist*, and furthermore, if u could
    point to one of these "unknowable" machines it would cease to be unknowable!!

    So? You seem to be hung up on the side issue of the existance of
    unkmowable machines. We CAN say some things about their behavior, just
    not enough to know if a given machine is unknowable. This just comes
    from the incompleteness of logic in powerful enough systems.


    i'm sorry, this is like fucking believing in mathematical ghosts bro,

    LOGIC HAS LEFT THE DISCUSSION


    Only for you. it seems you just can't handle talking about things that
    are unknowable. By their nature, logic can't tell us much about them,
    only if the can/might exists. We know that there MUST be statements that
    are unprovable in truth value, and from more advance proofs, that even
    as we go down layers of meta-logic that might be able to prove some statements, there will ALWAYS be some statements that are unprovable,
    and if they are unprovable in ALL systems, they are unknowable.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 17:48:06 2025
    From Newsgroup: comp.theory

    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in
    Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    Nope, as it has an non-determinism/non-input that affects its behavior. Computation theory is about the mapping of input to output, so any non-determinism or dependency of a "non-input" isn't allowed, as the
    machine no longer "compute" a mapping.

    There ARE variants of computation theory that handles such machines, but
    not about individual runs, but about the collection of all runs. They
    "branch" the path at each non-deterministic point, and look at the final result, using a couple of different criteria.

    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or
    non-halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered
    interesting for the theory.


    1 HOME
    5 PRINT "ct_dr_fuzz lol. ;^)"
    6 P0 = 0
    7 P1 = 0

    10 REM Fuzzer... ;^)
    20 A$ = "NOPE!"
    30 IF RND(1) < .5 THEN A$ = "YES"

    100 REM INPUT "Shall DD halt or not? " ; A$
    110 PRINT "Shall DD halt or not? " ; A$
    200 IF A$ = "YES" GOTO 666
    300 P0 = P0 + 1
    400 IF P0 > 0 AND P1 > 0 GOTO 1000
    500 GOTO 10

    666 PRINT "OK!"
    667 P1 = P1 + 1
    700 PRINT "NON_HALT P0 = "; P0
    710 PRINT "HALT P1 = "; P1
    720 IF P0 > 0 AND P1 > 0 GOTO 1000
    730 PRINT "ALL PATHS FAILED TO BE HIT!"
    740 GOTO 10


    1000 REM Fin
    1010 PRINT "FIN... All paths hit."
    1020 PRINT "NON_HALT P0 = "; P0
    1030 PRINT "HALT P1 = "; P1

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 15:21:09 2025
    From Newsgroup: comp.theory

    On 12/7/25 2:41 PM, Richard Damon wrote:
    On 12/7/25 4:59 PM, dart200 wrote:
    On 12/6/25 2:21 PM, Richard Damon wrote:
    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not >>>>>>>> exist.

    But "Undecidability" isn't about a particular "machine", but
    about a general problem, a total MAPPING of the (infinite) set of >>>>>>> inputs to there respective output. It is the statement that there >>>>>>> can not exist a "Program" (as defined by the theory, which are
    finite definite algorithms) that can recreate the mapping.

    For halting, every given program is know to either halt or not, >>>>>>> the problem is to be able to universally give that answer
    correctly in finite time. THAT can't be done (universally, i.e. >>>>>>> for any possible input machine).


    see, if we do not have a general halting decider then there must >>>>>>>> be some input machine L, which is the first machine in the full >>>>>>>> enumeration who's halting semantics cannot be decided up for
    some kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there is >>>>>>> a machine that it will give a wrong answer to (or fail to
    answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines
    that could not be decided upon, not only do not exist, they
    actually could not exist... and therefore they *do not* and *will >>>>>> not* come up in a full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably
    cannot be decided upon???

    That isn't the question, so just a straw man. The issues isn't an
    example, but the full question.


    if you tell me: look at these hypothetical undecidable machine
    that cannot exist, but from that we can just extrapolate *real*
    forms of such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an
    example of one???

    i'm not buying this whole if hypotheticals can be presented, then >>>>>> certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and
    want to claim to be a correct halt decider, I can make a machine
    and input to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a
    machine that gets all input correct.


    what that input machine is, can very well differ depending on
    which machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely >>>>>>>> hypothetical machines, which then are declared to not exist, so >>>>>>>> none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a >>>>>>> real machine if the decider it was built on was an actual machine. >>>>>>>

    so what is this proposed non-hypothetical *real* machine L that >>>>>>>> then cannot be decided?

    But that isn't the claim. It isn't that there is a specific
    machine L that can't be decided, and in fact, there can't be such >>>>>>> a machine, as there are two poor deciders, we can all Yes, and
    No, that always answer for every input their given answer, ONE of >>>>>>> those MUST be right, so there can not be a single specific
    machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and
    misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this
    property that it cannot be decided upon by a halting decider ... >>>>>>>> but then next step in undecidable proofs is to declare the
    machine's non- existence, because an undecidable machine is also >>>>>>>> not a deterministic machine, which ultimately contradicts the >>>>>>>> fact that this limit machine L was suppose to actually *exist*, >>>>>>>> so how could it ever exist?

    and if the limit machine L does not actually exist, then how are >>>>>>>> TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly >>>>>>>> irreconcilable nonsense. but bring it on my dudes, how do u
    think i'm wrong this time???


    And your problem he is you are working on the wrong problem,
    because "someone" has spewed out so much misinformaiton that he >>>>>>> has reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own thots >>>>>> that i've mostly developed on my own without much external
    validation anywhere. polcott is an interesting character, but we
    haven't yet seen eye to eye enough for much influence to happen
    either way

    Because it seems, you don't understand what the actual problem is,
    or how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's
    incompleteness, and i'm not making claims about it because it's
    just outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the
    Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole

    But the theory of computing is based on logic that can express the
    Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it >>>>>>> halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong
    answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are
    you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim
    is universally correct, I can make an input that shows the claim to >>>>> be wrong.

    Your problem is you have the question backwards. It isn't that
    there is a machine that no machine can get the right answer for, as >>>>> that is clearly wrong, but there is no machine that can always get
    the right answer.

    I side affect of this, is that there WILL be machines that we can
    not know the answer for, but we can't know if a given machine is
    one of them, as knowing that lets you know what the answer is, as
    the only unknowable halting state machines are non-halting, as ALL
    halting machine can be shown to be halting by just running them
    till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them
    myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we
    can't know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least
    possibly, I am not sure if we can actually prove such an existance, >>>>> only its potential to exist)



    Now, a side effect of this fact, it becomes true that there
    exists some machine/input combinations that we can not know if
    they halt or not, but another side effect of this is we can't
    tell if a given machine is one of them, as by definition any
    machine we can't know if it halts or not, must be non-halting, as >>>>>>> any halting machine can be

    bruh ... do u not recognize the inherent contradiction in say in all
    machines which can't know the halting of ... must therefore be non-
    halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it
    enough steps, as there must be some finite number of steps to run it
    till it halts, as that is the DEFINITION of Halting, and a finite
    number of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming
    they are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status. All
    we can know is we haven't found the status YET. Not knowN can be
    either halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone
    almost entirely unnoticed besides a few "cranks" on the internet,

    none of which have put it so succinctly like i've done so in the
    last day


    No, the problem is you keep on looking for that which the theory
    says is unknowable. We can show that there are machines that we can >>>>> not know the halting property of, but we can never know if a
    machine is in that class.

    We can know that no machine can be a correct decider, as for any
    claimed decider, we can show an input that it gets wrong. Thus no
    universally correct deciders, which IS the question possed by the
    problem.



    One way of looking at this, is we can take all machines, and we know
    that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3
    categories (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as running
    them enough (but for a still finite number of steps) will reach the
    halt state, and thus it not yet being know is just because we haven't
    run it far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there
    exists a proof, to be discovered, that proves that it will not halt.

    For the Unknowable machines, they can't be Halting, as we showed that
    all halting machines are knowable by just running them long enough.
    There is nothing that says we must be able to find a proof of non-
    halting, and the fact that Halting is non-decidable seems to imply
    that this category can't be empty, or our decider just needs to apply
    the appropriate proof of non-halting to correctly decide. The fact
    that there are an infinite number of possible proofs may allow this
    category to be empty, but I am not sure you can prove that.

    As I point out, It can't be possible to prove that a machine is in
    this unknowable category, as only non-halting machines can be
    unknowable, and thus a proof that a machine is in this category can't
    be correct, or the whole logic system is proven inconsistant. This is
    similar to the point that Godel uses in his incompleteness proof, as
    if you could prove the sentence true, that proof creates the counter
    example that makes the sentence false, thus no proof can exist.

    great so u've ended up in the situation of certainly believing in
    "unknowable" (yet certainly non-halting) machines,

    that you can't even prove exist,

    I don't need to prove they exist, as that isn't what the problem is
    talking about.

    Undecidabiity just means that you can't make a decider that gets all the answers right, and THAT is fully provable with a simple proof.

    The meta-logic to show that there exists some machines that we CAN'T
    know, is a different problem, and much more complicated.


    except for apparent demonstration with hypothetical machines that then
    can't even exist,

    i... just...

    /that is fucking crazy bro/

    It is the reasonable outcome of the fact that is reasonable to prove,
    that there can never be a machine that decides all input correctly, and
    thus the Halting Problem is undecidable.


    *there has to be some machine L at which "unknowability" can be
    pointed to*, why?? because we can partially decide this function, then
    there must be some maximally partial decidable, and with that there
    *must* be some *real* *existent* machine L which that maximally
    partial decidability "breaks down" and cannot be decided upon!

    Nope. To prove that it is undecidable, you just need to prove that no decider gets all answers right.

    It is theoretically conceivable that there could be a proof that can be discovered, but only after a potentially infinite search, for every
    machine.


    if ur theory can't tolerate that, THEN ITS BROKEN NUMBNUTS

    My theory can't tolerate what? That we might be able to know the answer
    to every possible instance, but that knowledge can't come from a finite machine?



    which it can't because if u could point that machine L, then according
    to u we'd know it was a non-halting machine, which contradicts it
    being machine L. so machine L, the first point were maximum
    decidability breaks down can't even be known!

    Right, we can't possible KNOW that a given machine is unknowable. As the meta-information defines the value of the question.

    Nothing wrong with that, it is just a property of unknowable things.


    you can't even tell me what form a machine looks like when it's
    unknowable, because none of the arguments for undecidable machines
    utilize machines *that actually exist*, and furthermore, if u could
    point to one of these "unknowable" machines it would cease to be
    unknowable!!

    So? You seem to be hung up on the side issue of the existance of
    unkmowable machines. We CAN say some things about their behavior, just
    not enough to know if a given machine is unknowable. This just comes
    from the incompleteness of logic in powerful enough systems.


    i'm sorry, this is like fucking believing in mathematical ghosts bro,

    LOGIC HAS LEFT THE DISCUSSION


    Only for you. it seems you just can't handle talking about things that
    are unknowable. By their nature, logic can't tell us much about them,
    only if the can/might exists. We know that there MUST be statements that
    are unprovable in truth value, and from more advance proofs, that even
    as we go down layers of meta-logic that might be able to prove some statements, there will ALWAYS be some statements that are unprovable,
    and if they are unprovable in ALL systems, they are unknowable.

    yah bro u keep going on about those unknowable limits to decidability
    that u can't even point to a *real* example of because being able to do
    so would contradict the premise that this unknowable limit even exists
    in the first place!

    god damn bro
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Tristan Wibberley@tristan.wibberley+netnews2@alumni.manchester.ac.uk to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Mon Dec 8 01:26:26 2025
    From Newsgroup: comp.theory

    On 06/12/2025 17:00, olcott wrote:
    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    Do you really mean "truthy" on the basis of meaning?
    I'd argue "true on the basis of meaning" can only every be truthy, but
    "truthy on the basis of meaning" could, perhaps, become true.
    --
    Tristan Wibberley

    The message body is Copyright (C) 2025 Tristan Wibberley except
    citations and quotations noted. All Rights Reserved except that you may,
    of course, cite it academically giving credit to me, distribute it
    verbatim as part of a usenet system or its archives, and use it to
    promote my greatness and general superiority without misrepresentation
    of my opinions other than my opinion of my greatness and general
    superiority which you _may_ misrepresent. You definitely MAY NOT train
    any production AI system with it but you may train experimental AI that
    will only be used for evaluation of the AI methods it implements.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Ben Bacarisse@ben@bsb.me.uk to comp.theory on Mon Dec 8 01:46:48 2025
    From Newsgroup: comp.theory

    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist.

    Is a "real TM" any different to a TM? If so, on what way? What is an undecidable machine (or, for that matter, a decidable machine)? I can't
    keep this in mind if I don't know what your terms mean.

    see, if we do not have a general halting decider then there must be some input machine L, which is the first machine in the full enumeration who's halting semantics cannot be decided up for some kind of semantics (like halting).

    The theory of desirability is all about sets. Sets are or are not
    decidable. The set of TMs that halt (on, say, an empty tape) is not
    decidable, for example. Unless you choose to use conventional terms or
    define some new terms precisely, you will just be writing
    technical-sounding nonsense.

    well, first off: all the proofs for undecidability use purely hypothetical machines, which then are declared to not exist, so none of those machines could be *real* machine L.

    I very much doubt you know all the proofs about undecidability. I doubt
    you know even all the proofs of the undecidability of the set of halting
    TMs. I don't.

    so what is this proposed non-hypothetical *real* machine L that then cannot be decided?

    See above. What is a real TM as opposed to a TM as usually defined?

    and could that machine L even exist?

    Does any TM exist? TMs are, after all, just mathematical objects. If
    you accept that mathematical objects (like the set of primes) exist,
    then every TM exists.

    let's say someone found that limit L and demonstrated this property that it cannot be decided upon by a halting decider ... but then next step in undecidable proofs is to declare the machine's non-existence, because an undecidable machine is also not a deterministic machine, which ultimately contradicts the fact that this limit machine L was suppose to actually *exist*, so how could it ever exist?

    You might want to read some more proofs about TMs and halting.

    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly irreconcilable nonsense. but bring it on my dudes, how do u think i'm wrong this time???

    I sympathise. But I get tired with people who don't define their terms
    and argue about a topic they don't appear to have studied.
    --
    Ben.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 21:42:06 2025
    From Newsgroup: comp.theory

    On 12/7/25 6:21 PM, dart200 wrote:
    On 12/7/25 2:41 PM, Richard Damon wrote:
    On 12/7/25 4:59 PM, dart200 wrote:
    On 12/6/25 2:21 PM, Richard Damon wrote:
    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not >>>>>>>>> exist.

    But "Undecidability" isn't about a particular "machine", but
    about a general problem, a total MAPPING of the (infinite) set >>>>>>>> of inputs to there respective output. It is the statement that >>>>>>>> there can not exist a "Program" (as defined by the theory, which >>>>>>>> are finite definite algorithms) that can recreate the mapping. >>>>>>>>
    For halting, every given program is know to either halt or not, >>>>>>>> the problem is to be able to universally give that answer
    correctly in finite time. THAT can't be done (universally, i.e. >>>>>>>> for any possible input machine).


    see, if we do not have a general halting decider then there >>>>>>>>> must be some input machine L, which is the first machine in the >>>>>>>>> full enumeration who's halting semantics cannot be decided up >>>>>>>>> for some kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there >>>>>>>> is a machine that it will give a wrong answer to (or fail to
    answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines >>>>>>> that could not be decided upon, not only do not exist, they
    actually could not exist... and therefore they *do not* and *will >>>>>>> not* come up in a full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably
    cannot be decided upon???

    That isn't the question, so just a straw man. The issues isn't an >>>>>> example, but the full question.


    if you tell me: look at these hypothetical undecidable machine
    that cannot exist, but from that we can just extrapolate *real* >>>>>>> forms of such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an
    example of one???

    i'm not buying this whole if hypotheticals can be presented, then >>>>>>> certainly *real* variations of it exist ... where else would
    hypothesizing about something just like fucking imply non-
    hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and
    want to claim to be a correct halt decider, I can make a machine
    and input to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be a >>>>>> machine that gets all input correct.


    what that input machine is, can very well differ depending on >>>>>>>> which machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely >>>>>>>>> hypothetical machines, which then are declared to not exist, so >>>>>>>>> none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE a >>>>>>>> real machine if the decider it was built on was an actual machine. >>>>>>>>

    so what is this proposed non-hypothetical *real* machine L that >>>>>>>>> then cannot be decided?

    But that isn't the claim. It isn't that there is a specific
    machine L that can't be decided, and in fact, there can't be
    such a machine, as there are two poor deciders, we can all Yes, >>>>>>>> and No, that always answer for every input their given answer, >>>>>>>> ONE of those MUST be right, so there can not be a single
    specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and
    misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this
    property that it cannot be decided upon by a halting
    decider ... but then next step in undecidable proofs is to
    declare the machine's non- existence, because an undecidable >>>>>>>>> machine is also not a deterministic machine, which ultimately >>>>>>>>> contradicts the fact that this limit machine L was suppose to >>>>>>>>> actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how >>>>>>>>> are TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly >>>>>>>>> irreconcilable nonsense. but bring it on my dudes, how do u >>>>>>>>> think i'm wrong this time???


    And your problem he is you are working on the wrong problem,
    because "someone" has spewed out so much misinformaiton that he >>>>>>>> has reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own thots >>>>>>> that i've mostly developed on my own without much external
    validation anywhere. polcott is an interesting character, but we >>>>>>> haven't yet seen eye to eye enough for much influence to happen >>>>>>> either way

    Because it seems, you don't understand what the actual problem is, >>>>>> or how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's >>>>>>> incompleteness, and i'm not making claims about it because it's >>>>>>> just outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the
    Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole >>>>>>
    But the theory of computing is based on logic that can express the >>>>>> Natural numbers, and thus that part of mathematics comes in.



    The problem isn't that some given machine can't be decided if it >>>>>>>> halts or not, but that for every machine that claims to be a
    decider, there will be an input for which it gives the wrong
    answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this
    behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what are >>>>>> you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim >>>>>> is universally correct, I can make an input that shows the claim
    to be wrong.

    Your problem is you have the question backwards. It isn't that
    there is a machine that no machine can get the right answer for,
    as that is clearly wrong, but there is no machine that can always >>>>>> get the right answer.

    I side affect of this, is that there WILL be machines that we can >>>>>> not know the answer for, but we can't know if a given machine is
    one of them, as knowing that lets you know what the answer is, as >>>>>> the only unknowable halting state machines are non-halting, as ALL >>>>>> halting machine can be shown to be halting by just running them
    till the halt.


    sure you can throw around hypothetical examples of undecidable
    machines all day long, i've spent a lot of time considering them >>>>>>> myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we
    can't know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*???

    Which is an answer we can never know the answer to (at least
    possibly, I am not sure if we can actually prove such an
    existance, only its potential to exist)



    Now, a side effect of this fact, it becomes true that there
    exists some machine/input combinations that we can not know if >>>>>>>> they halt or not, but another side effect of this is we can't >>>>>>>> tell if a given machine is one of them, as by definition any
    machine we can't know if it halts or not, must be non-halting, >>>>>>>> as any halting machine can be

    bruh ... do u not recognize the inherent contradiction in say in
    all machines which can't know the halting of ... must therefore be
    non- halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it
    enough steps, as there must be some finite number of steps to run it
    till it halts, as that is the DEFINITION of Halting, and a finite
    number of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming
    they are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status.
    All we can know is we haven't found the status YET. Not knowN can be
    either halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone
    almost entirely unnoticed besides a few "cranks" on the internet, >>>>>>>
    none of which have put it so succinctly like i've done so in the >>>>>>> last day


    No, the problem is you keep on looking for that which the theory
    says is unknowable. We can show that there are machines that we
    can not know the halting property of, but we can never know if a
    machine is in that class.

    We can know that no machine can be a correct decider, as for any
    claimed decider, we can show an input that it gets wrong. Thus no >>>>>> universally correct deciders, which IS the question possed by the >>>>>> problem.



    One way of looking at this, is we can take all machines, and we know
    that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3
    categories (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as running
    them enough (but for a still finite number of steps) will reach the
    halt state, and thus it not yet being know is just because we
    haven't run it far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there
    exists a proof, to be discovered, that proves that it will not halt.

    For the Unknowable machines, they can't be Halting, as we showed
    that all halting machines are knowable by just running them long
    enough. There is nothing that says we must be able to find a proof
    of non- halting, and the fact that Halting is non-decidable seems to
    imply that this category can't be empty, or our decider just needs
    to apply the appropriate proof of non-halting to correctly decide.
    The fact that there are an infinite number of possible proofs may
    allow this category to be empty, but I am not sure you can prove that. >>>>
    As I point out, It can't be possible to prove that a machine is in
    this unknowable category, as only non-halting machines can be
    unknowable, and thus a proof that a machine is in this category
    can't be correct, or the whole logic system is proven inconsistant.
    This is similar to the point that Godel uses in his incompleteness
    proof, as if you could prove the sentence true, that proof creates
    the counter example that makes the sentence false, thus no proof can
    exist.

    great so u've ended up in the situation of certainly believing in
    "unknowable" (yet certainly non-halting) machines,

    that you can't even prove exist,

    I don't need to prove they exist, as that isn't what the problem is
    talking about.

    Undecidabiity just means that you can't make a decider that gets all
    the answers right, and THAT is fully provable with a simple proof.

    The meta-logic to show that there exists some machines that we CAN'T
    know, is a different problem, and much more complicated.


    except for apparent demonstration with hypothetical machines that
    then can't even exist,

    i... just...

    /that is fucking crazy bro/

    It is the reasonable outcome of the fact that is reasonable to prove,
    that there can never be a machine that decides all input correctly,
    and thus the Halting Problem is undecidable.


    *there has to be some machine L at which "unknowability" can be
    pointed to*, why?? because we can partially decide this function,
    then there must be some maximally partial decidable, and with that
    there *must* be some *real* *existent* machine L which that maximally
    partial decidability "breaks down" and cannot be decided upon!

    Nope. To prove that it is undecidable, you just need to prove that no
    decider gets all answers right.

    It is theoretically conceivable that there could be a proof that can
    be discovered, but only after a potentially infinite search, for every
    machine.


    if ur theory can't tolerate that, THEN ITS BROKEN NUMBNUTS

    My theory can't tolerate what? That we might be able to know the
    answer to every possible instance, but that knowledge can't come from
    a finite machine?



    which it can't because if u could point that machine L, then
    according to u we'd know it was a non-halting machine, which
    contradicts it being machine L. so machine L, the first point were
    maximum decidability breaks down can't even be known!

    Right, we can't possible KNOW that a given machine is unknowable. As
    the meta-information defines the value of the question.

    Nothing wrong with that, it is just a property of unknowable things.


    you can't even tell me what form a machine looks like when it's
    unknowable, because none of the arguments for undecidable machines
    utilize machines *that actually exist*, and furthermore, if u could
    point to one of these "unknowable" machines it would cease to be
    unknowable!!

    So? You seem to be hung up on the side issue of the existance of
    unkmowable machines. We CAN say some things about their behavior, just
    not enough to know if a given machine is unknowable. This just comes
    from the incompleteness of logic in powerful enough systems.


    i'm sorry, this is like fucking believing in mathematical ghosts bro,

    LOGIC HAS LEFT THE DISCUSSION


    Only for you. it seems you just can't handle talking about things that
    are unknowable. By their nature, logic can't tell us much about them,
    only if the can/might exists. We know that there MUST be statements
    that are unprovable in truth value, and from more advance proofs, that
    even as we go down layers of meta-logic that might be able to prove
    some statements, there will ALWAYS be some statements that are
    unprovable, and if they are unprovable in ALL systems, they are
    unknowable.

    yah bro u keep going on about those unknowable limits to decidability
    that u can't even point to a *real* example of because being able to do
    so would contradict the premise that this unknowable limit even exists
    in the first place!

    god damn bro


    Because Turing PROVED that the Halting Problem can't be computed, thus,
    the limit exists.

    We may not be able to precisely define the line betweem computable and non-computable (or decidable vs non-decidable), but we know it exists as
    we have things know to be on both sides.

    We have a number of general propositions that have been proven to be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can fall
    into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we know
    an answer (if we do) as knowing the answer shows it is knowable.

    Showing that some things might be knowable but not currently know is
    possible, but that does NOT mean we can answer the knowability question
    for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know" that
    might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Sun Dec 7 21:17:19 2025
    From Newsgroup: comp.theory

    On 12/7/2025 7:26 PM, Tristan Wibberley wrote:
    On 06/12/2025 17:00, olcott wrote:
    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    Do you really mean "truthy" on the basis of meaning?
    I'd argue "true on the basis of meaning" can only every be truthy, but "truthy on the basis of meaning" could, perhaps, become true.


    In other words we cannot be certain
    that the integer five is a number?
    --
    Copyright 2025 Olcott<br><br>

    My 28 year goal has been to make <br>
    "true on the basis of meaning" computable.<br><br>

    This required establishing a new foundation<br>
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sun Dec 7 20:28:44 2025
    From Newsgroup: comp.theory

    On 12/7/25 6:42 PM, Richard Damon wrote:
    On 12/7/25 6:21 PM, dart200 wrote:
    On 12/7/25 2:41 PM, Richard Damon wrote:
    On 12/7/25 4:59 PM, dart200 wrote:
    On 12/6/25 2:21 PM, Richard Damon wrote:
    On 12/6/25 4:41 PM, dart200 wrote:
    On 12/6/25 10:44 AM, Richard Damon wrote:
    On 12/6/25 2:34 AM, dart200 wrote:
    On 12/5/25 5:31 PM, Richard Damon wrote:
    On 12/4/25 3:22 AM, dart200 wrote:
    keep in mind: all real TMs exist, undecidable machines do not >>>>>>>>>> exist.

    But "Undecidability" isn't about a particular "machine", but >>>>>>>>> about a general problem, a total MAPPING of the (infinite) set >>>>>>>>> of inputs to there respective output. It is the statement that >>>>>>>>> there can not exist a "Program" (as defined by the theory,
    which are finite definite algorithms) that can recreate the >>>>>>>>> mapping.

    For halting, every given program is know to either halt or not, >>>>>>>>> the problem is to be able to universally give that answer
    correctly in finite time. THAT can't be done (universally, i.e. >>>>>>>>> for any possible input machine).


    see, if we do not have a general halting decider then there >>>>>>>>>> must be some input machine L, which is the first machine in >>>>>>>>>> the full enumeration who's halting semantics cannot be decided >>>>>>>>>> up for some kind of semantics (like halting).

    No, it means that for every machine in that enumeration, there >>>>>>>>> is a machine that it will give a wrong answer to (or fail to >>>>>>>>> answer), and

    let me boil this down:

    all "proven" examples of what are actually hypothetical machines >>>>>>>> that could not be decided upon, not only do not exist, they
    actually could not exist... and therefore they *do not* and
    *will not* come up in a full enumeration of machines

    Where do you see that?


    so what is the *real* example of a machine that demonstrably
    cannot be decided upon???

    That isn't the question, so just a straw man. The issues isn't an >>>>>>> example, but the full question.


    if you tell me: look at these hypothetical undecidable machine >>>>>>>> that cannot exist, but from that we can just extrapolate *real* >>>>>>>> forms of such machines that certainly can exist ... ???

    But that isn't what the proofs do.

    All you are doing is showing a misunderstanding of the problem.


    but like ok, if ur so certain they *must* exist, what is an
    example of one???

    i'm not buying this whole if hypotheticals can be presented,
    then certainly *real* variations of it exist ... where else
    would hypothesizing about something just like fucking imply non- >>>>>>>> hypothetical forms of it actually exist as real constructs???

    And a proof can be made, that for *ANY* machine you can make and >>>>>>> want to claim to be a correct halt decider, I can make a machine >>>>>>> and input to give to it that it will get wrong.

    Since I can do that for EVERY machine you make, there can not be >>>>>>> a machine that gets all input correct.


    what that input machine is, can very well differ depending on >>>>>>>>> which machine in the enumeration you are looking at.


    well, first off: all the proofs for undecidability use purely >>>>>>>>>> hypothetical machines, which then are declared to not exist, >>>>>>>>>> so none of those machines could be *real* machine L.

    Not "ALL", but the classic one. and the input derived WOULD BE >>>>>>>>> a real machine if the decider it was built on was an actual >>>>>>>>> machine.


    so what is this proposed non-hypothetical *real* machine L >>>>>>>>>> that then cannot be decided?

    But that isn't the claim. It isn't that there is a specific >>>>>>>>> machine L that can't be decided, and in fact, there can't be >>>>>>>>> such a machine, as there are two poor deciders, we can all Yes, >>>>>>>>> and No, that always answer for every input their given answer, >>>>>>>>> ONE of those MUST be right, so there can not be a single
    specific machine that all get wrong.

    That idea is just part of Peter Olcotts stupidity and
    misunderstanding.


    and could that machine L even exist?

    let's say someone found that limit L and demonstrated this >>>>>>>>>> property that it cannot be decided upon by a halting
    decider ... but then next step in undecidable proofs is to >>>>>>>>>> declare the machine's non- existence, because an undecidable >>>>>>>>>> machine is also not a deterministic machine, which ultimately >>>>>>>>>> contradicts the fact that this limit machine L was suppose to >>>>>>>>>> actually *exist*, so how could it ever exist?

    and if the limit machine L does not actually exist, then how >>>>>>>>>> are TM semantics not generally decidable???

    good god guys, it's so tiring arguing against what is
    seemingly irreconcilable nonsense. but bring it on my dudes, >>>>>>>>>> how do u think i'm wrong this time???


    And your problem he is you are working on the wrong problem, >>>>>>>>> because "someone" has spewed out so much misinformaiton that he >>>>>>>>> has reduced the intelligence of the world.

    no bro, please read this carefully: these really are my own
    thots that i've mostly developed on my own without much external >>>>>>>> validation anywhere. polcott is an interesting character, but we >>>>>>>> haven't yet seen eye to eye enough for much influence to happen >>>>>>>> either way

    Because it seems, you don't understand what the actual problem
    is, or how the proof actually work.


    unlike polcott, i'm personally not sure what to do about godel's >>>>>>>> incompleteness, and i'm not making claims about it because it's >>>>>>>> just outside the scope i'm trying to address

    So, you don't care about logic that has the power to express the >>>>>>> Natural Numbers?


    i'm trying to address the theory of computing, not math as a whole >>>>>>>
    But the theory of computing is based on logic that can express
    the Natural numbers, and thus that part of mathematics comes in. >>>>>>>


    The problem isn't that some given machine can't be decided if >>>>>>>>> it halts or not, but that for every machine that claims to be a >>>>>>>>> decider, there will be an input for which it gives the wrong >>>>>>>>> answer, or it fails to answers.

    i know this is hard to really consider:

    what is an example of a *real machine that exists*, where this >>>>>>>> behavior demonstrably happens???

    Since it is proven that there can't be a correct decider, what
    are you asking for?

    As I said, for *ANY* "Halt Decider" that you want to try to claim >>>>>>> is universally correct, I can make an input that shows the claim >>>>>>> to be wrong.

    Your problem is you have the question backwards. It isn't that
    there is a machine that no machine can get the right answer for, >>>>>>> as that is clearly wrong, but there is no machine that can always >>>>>>> get the right answer.

    I side affect of this, is that there WILL be machines that we can >>>>>>> not know the answer for, but we can't know if a given machine is >>>>>>> one of them, as knowing that lets you know what the answer is, as >>>>>>> the only unknowable halting state machines are non-halting, as
    ALL halting machine can be shown to be halting by just running
    them till the halt.


    sure you can throw around hypothetical examples of undecidable >>>>>>>> machines all day long, i've spent a lot of time considering them >>>>>>>> myself, probably more than you actually...

    And, as I have said, that isn't the concept to consider, as we
    can't know that a machine is undecidable.


    but like what about a *real* machine, that *actually exists*??? >>>>>>>
    Which is an answer we can never know the answer to (at least
    possibly, I am not sure if we can actually prove such an
    existance, only its potential to exist)



    Now, a side effect of this fact, it becomes true that there >>>>>>>>> exists some machine/input combinations that we can not know if >>>>>>>>> they halt or not, but another side effect of this is we can't >>>>>>>>> tell if a given machine is one of them, as by definition any >>>>>>>>> machine we can't know if it halts or not, must be non-halting, >>>>>>>>> as any halting machine can be

    bruh ... do u not recognize the inherent contradiction in say in
    all machines which can't know the halting of ... must therefore be >>>>>> non- halting???

    What is the contradiction in that?

    Do you understand the difference between knowABLE, and knowN.

    Any machine that halts, can ALWAYS be proven it halts by running it >>>>> enough steps, as there must be some finite number of steps to run
    it till it halts, as that is the DEFINITION of Halting, and a
    finite number of steps makes a proof that gives knowledge.



    like u literally just decided what they all must be after claiming >>>>>> they are machiens which we cannot know the halting status of ...

    Right, but we can't KNOW that we can't know their halting status.
    All we can know is we haven't found the status YET. Not knowN can
    be either halting or non-halting, halting if we haven't run it yet.


    proven to halt, just by running it for enough steps.

    honestly richard, i think i just stumbled right into a core
    contradiction baked into the theory of computing that has gone >>>>>>>> almost entirely unnoticed besides a few "cranks" on the internet, >>>>>>>>
    none of which have put it so succinctly like i've done so in the >>>>>>>> last day


    No, the problem is you keep on looking for that which the theory >>>>>>> says is unknowable. We can show that there are machines that we >>>>>>> can not know the halting property of, but we can never know if a >>>>>>> machine is in that class.

    We can know that no machine can be a correct decider, as for any >>>>>>> claimed decider, we can show an input that it gets wrong. Thus no >>>>>>> universally correct deciders, which IS the question possed by the >>>>>>> problem.



    One way of looking at this, is we can take all machines, and we
    know that they must fall into exactly 2 categories
    Halting or
    Non-Halting,

    But ore knowledge of them divdes them into three categories:

    Known Halting,
    Known Non-Halting, or
    Unknown Halting Status.

    And this last category we know can consist of machines in 3
    categories (but we don't know which for a given machine):
    Yet-to-be-known, but Knowable, Halting
    Yet-to-be-known, but Knowable, Non-Halting
    Not Knowable Non-Halting.

    All Halting machines are Knowable, even if not-yet known, as
    running them enough (but for a still finite number of steps) will
    reach the halt state, and thus it not yet being know is just
    because we haven't run it far enough.

    For the Yet-to-be-know but Knowable Non-Halting Machines, there
    exists a proof, to be discovered, that proves that it will not halt. >>>>>
    For the Unknowable machines, they can't be Halting, as we showed
    that all halting machines are knowable by just running them long
    enough. There is nothing that says we must be able to find a proof
    of non- halting, and the fact that Halting is non-decidable seems
    to imply that this category can't be empty, or our decider just
    needs to apply the appropriate proof of non-halting to correctly
    decide. The fact that there are an infinite number of possible
    proofs may allow this category to be empty, but I am not sure you
    can prove that.

    As I point out, It can't be possible to prove that a machine is in
    this unknowable category, as only non-halting machines can be
    unknowable, and thus a proof that a machine is in this category
    can't be correct, or the whole logic system is proven inconsistant. >>>>> This is similar to the point that Godel uses in his incompleteness
    proof, as if you could prove the sentence true, that proof creates
    the counter example that makes the sentence false, thus no proof
    can exist.

    great so u've ended up in the situation of certainly believing in
    "unknowable" (yet certainly non-halting) machines,

    that you can't even prove exist,

    I don't need to prove they exist, as that isn't what the problem is
    talking about.

    Undecidabiity just means that you can't make a decider that gets all
    the answers right, and THAT is fully provable with a simple proof.

    The meta-logic to show that there exists some machines that we CAN'T
    know, is a different problem, and much more complicated.


    except for apparent demonstration with hypothetical machines that
    then can't even exist,

    i... just...

    /that is fucking crazy bro/

    It is the reasonable outcome of the fact that is reasonable to prove,
    that there can never be a machine that decides all input correctly,
    and thus the Halting Problem is undecidable.


    *there has to be some machine L at which "unknowability" can be
    pointed to*, why?? because we can partially decide this function,
    then there must be some maximally partial decidable, and with that
    there *must* be some *real* *existent* machine L which that
    maximally partial decidability "breaks down" and cannot be decided
    upon!

    Nope. To prove that it is undecidable, you just need to prove that no
    decider gets all answers right.

    It is theoretically conceivable that there could be a proof that can
    be discovered, but only after a potentially infinite search, for
    every machine.


    if ur theory can't tolerate that, THEN ITS BROKEN NUMBNUTS

    My theory can't tolerate what? That we might be able to know the
    answer to every possible instance, but that knowledge can't come from
    a finite machine?



    which it can't because if u could point that machine L, then
    according to u we'd know it was a non-halting machine, which
    contradicts it being machine L. so machine L, the first point were
    maximum decidability breaks down can't even be known!

    Right, we can't possible KNOW that a given machine is unknowable. As
    the meta-information defines the value of the question.

    Nothing wrong with that, it is just a property of unknowable things.


    you can't even tell me what form a machine looks like when it's
    unknowable, because none of the arguments for undecidable machines
    utilize machines *that actually exist*, and furthermore, if u could
    point to one of these "unknowable" machines it would cease to be
    unknowable!!

    So? You seem to be hung up on the side issue of the existance of
    unkmowable machines. We CAN say some things about their behavior,
    just not enough to know if a given machine is unknowable. This just
    comes from the incompleteness of logic in powerful enough systems.


    i'm sorry, this is like fucking believing in mathematical ghosts bro,

    LOGIC HAS LEFT THE DISCUSSION


    Only for you. it seems you just can't handle talking about things
    that are unknowable. By their nature, logic can't tell us much about
    them, only if the can/might exists. We know that there MUST be
    statements that are unprovable in truth value, and from more advance
    proofs, that even as we go down layers of meta-logic that might be
    able to prove some statements, there will ALWAYS be some statements
    that are unprovable, and if they are unprovable in ALL systems, they
    are unknowable.

    yah bro u keep going on about those unknowable limits to decidability
    that u can't even point to a *real* example of because being able to
    do so would contradict the premise that this unknowable limit even
    exists in the first place!

    god damn bro


    Because Turing PROVED that the Halting Problem can't be computed, thus,
    the limit exists.

    We may not be able to precisely define the line betweem computable and non-computable (or decidable vs non-decidable), but we know it exists as
    we have things know to be on both sides.

    We have a number of general propositions that have been proven to be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we know
    an answer (if we do) as knowing the answer shows it is knowable.

    Showing that some things might be knowable but not currently know is possible, but that does NOT mean we can answer the knowability question
    for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know" that
    might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting machines
    with "unknown" behavior actually looks like because then ur theory falls apart, despite the fact we can in fact emuerate over all machines ...

    so idk wtf u think u'r actually talking about there buddy
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Sun Dec 7 20:37:02 2025
    From Newsgroup: comp.theory

    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist.

    Is a "real TM" any different to a TM? If so, on what way? What is an undecidable machine (or, for that matter, a decidable machine)? I can't
    keep this in mind if I don't know what your terms mean.

    see, if we do not have a general halting decider then there must be some
    input machine L, which is the first machine in the full enumeration who's
    halting semantics cannot be decided up for some kind of semantics (like
    halting).

    The theory of desirability is all about sets. Sets are or are not
    decidable. The set of TMs that halt (on, say, an empty tape) is not decidable, for example. Unless you choose to use conventional terms or define some new terms precisely, you will just be writing
    technical-sounding nonsense.

    all the example of machines that cannot be decided into the set of
    halting or non-halting machines are then declared to not exist ... so
    they can't come up in the actual enumeration of machines.


    well, first off: all the proofs for undecidability use purely hypothetical >> machines, which then are declared to not exist, so none of those machines
    could be *real* machine L.

    I very much doubt you know all the proofs about undecidability. I doubt
    you know even all the proofs of the undecidability of the set of halting
    TMs. I don't.

    so what is this proposed non-hypothetical *real* machine L that then cannot >> be decided?

    See above. What is a real TM as opposed to a TM as usually defined?

    real TMs come up in the full enumerations. the hypothetical TMs
    discussed in undecidability proofs do not exist, and therefore cannot
    appear in full enumerations


    and could that machine L even exist?

    Does any TM exist? TMs are, after all, just mathematical objects. If
    you accept that mathematical objects (like the set of primes) exist,
    then every TM exists.

    TMs that exist come up in the full enumeration of machine, which is necessarily possible given that machine description are finite objects.


    let's say someone found that limit L and demonstrated this property that it >> cannot be decided upon by a halting decider ... but then next step in
    undecidable proofs is to declare the machine's non-existence, because an
    undecidable machine is also not a deterministic machine, which ultimately
    contradicts the fact that this limit machine L was suppose to actually
    *exist*, so how could it ever exist?

    You might want to read some more proofs about TMs and halting.

    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    these hypothetical machines which we present as unclassifiable are also
    not real machines.

    what are *real* machines, that we can actually iterate upon in the full enumeration of machines, that are *provably* unclassifiable???


    and if the limit machine L does not actually exist, then how are TM
    semantics not generally decidable???

    good god guys, it's so tiring arguing against what is seemingly
    irreconcilable nonsense. but bring it on my dudes, how do u think i'm wrong >> this time???

    I sympathise. But I get tired with people who don't define their terms
    and argue about a topic they don't appear to have studied.


    cut that gaslighting shit out bro
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Tristan Wibberley@tristan.wibberley+netnews2@alumni.manchester.ac.uk to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Mon Dec 8 06:36:27 2025
    From Newsgroup: comp.theory

    On 08/12/2025 03:17, olcott wrote:
    On 12/7/2025 7:26 PM, Tristan Wibberley wrote:
    On 06/12/2025 17:00, olcott wrote:
    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    Do you really mean "truthy" on the basis of meaning?
    I'd argue "true on the basis of meaning" can only every be truthy, but
    "truthy on the basis of meaning" could, perhaps, become true.


    In other words we cannot be certain
    that the integer five is a number?

    that "the integer five" refers to a number. exactly
    --
    Tristan Wibberley

    The message body is Copyright (C) 2025 Tristan Wibberley except
    citations and quotations noted. All Rights Reserved except that you may,
    of course, cite it academically giving credit to me, distribute it
    verbatim as part of a usenet system or its archives, and use it to
    promote my greatness and general superiority without misrepresentation
    of my opinions other than my opinion of my greatness and general
    superiority which you _may_ misrepresent. You definitely MAY NOT train
    any production AI system with it but you may train experimental AI that
    will only be used for evaluation of the AI methods it implements.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Tristan Wibberley@tristan.wibberley+netnews2@alumni.manchester.ac.uk to comp.theory on Mon Dec 8 09:48:26 2025
    From Newsgroup: comp.theory

    On 08/12/2025 04:37, dart200 wrote:
    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist.

    Is a "real TM" any different to a TM?  If so, on what way?  What is an
    undecidable machine (or, for that matter, a decidable machine)?  I can't
    keep this in mind if I don't know what your terms mean.


    dart200 - you cunningly avoided answering the above, making all the rest
    a pointless read, and thus a pointless write.
    --
    Tristan Wibberley

    The message body is Copyright (C) 2025 Tristan Wibberley except
    citations and quotations noted. All Rights Reserved except that you may,
    of course, cite it academically giving credit to me, distribute it
    verbatim as part of a usenet system or its archives, and use it to
    promote my greatness and general superiority without misrepresentation
    of my opinions other than my opinion of my greatness and general
    superiority which you _may_ misrepresent. You definitely MAY NOT train
    any production AI system with it but you may train experimental AI that
    will only be used for evaluation of the AI methods it implements.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 07:31:44 2025
    From Newsgroup: comp.theory

    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed,
    thus, the limit exists.

    We may not be able to precisely define the line betweem computable and
    non-computable (or decidable vs non-decidable), but we know it exists
    as we have things know to be on both sides.

    We have a number of general propositions that have been proven to be
    uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can
    fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we know
    an answer (if we do) as knowing the answer shows it is knowable.

    Showing that some things might be knowable but not currently know is
    possible, but that does NOT mean we can answer the knowability
    question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know" that
    might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting machines with "unknown" behavior actually looks like because then ur theory falls apart, despite the fact we can in fact emuerate over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as they aren't the topic of the problem.

    It seems you are stuck in a Naive Set Theory system that insists on
    having Sets based on just a description of them.

    What I am talking about is that we can prove that there can not exist of
    a finite algorithm that will always tell if any finite algorithn it is
    given the full description of will reach an answer or not.

    Since such a decider doesn't exist, we of course can't "describe" it,
    except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with more
    work we CAN determine if they will halt or not, but there will be some
    which we can't (perhaps yet) determine if we can do that.

    So, the set of machines which we can not know their behavior is not a
    valid set to talk about except in a Naive Set theory, which will itself
    be inconsistant. The fact you keep on harping about that set says you
    don't understand the problem with it.

    Your logic seems to be based on trying to solve Russel's Teapot, which
    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory on Mon Dec 8 07:35:51 2025
    From Newsgroup: comp.theory

    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully deterministic,
    but just run from an infinite number of steps, and for which no
    reduction is available for use to determine that in a finite number of
    steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to
    determine.

    Deterministic doesn't mean finite, or reducible to finite.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy,sci.logic,sci.math on Mon Dec 8 10:25:12 2025
    From Newsgroup: comp.theory

    On 12/8/2025 12:36 AM, Tristan Wibberley wrote:
    On 08/12/2025 03:17, olcott wrote:
    On 12/7/2025 7:26 PM, Tristan Wibberley wrote:
    On 06/12/2025 17:00, olcott wrote:
    As my signature line now stipulates
    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    Do you really mean "truthy" on the basis of meaning?
    I'd argue "true on the basis of meaning" can only every be truthy, but
    "truthy on the basis of meaning" could, perhaps, become true.


    In other words we cannot be certain
    that the integer five is a number?

    that "the integer five" refers to a number. exactly


    The body of general knowledge that can be expressed in
    language includes all of the details of every published
    definition in a knowledge ontology type hierarchy.
    Each atomic fact of the actual world.

    This is stored as formalized natural language such as
    Rudolf Carnap Meaning Postulates, Montague Grammar of
    natural language semantics, or the CycL language of the
    Cyc project's knowledge ontology.

    Some aspects of this knowledge might also be stored in
    some other formal language that may be more compact
    and succinct for mathematical notions.
    --
    Copyright 2025 Olcott<br><br>

    My 28 year goal has been to make <br>
    "true on the basis of meaning" computable.<br><br>

    This required establishing a new foundation<br>
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Dec 8 11:23:36 2025
    From Newsgroup: comp.theory

    On 12/8/25 1:48 AM, Tristan Wibberley wrote:
    On 08/12/2025 04:37, dart200 wrote:
    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist.

    Is a "real TM" any different to a TM?  If so, on what way?  What is an >>> undecidable machine (or, for that matter, a decidable machine)?  I can't >>> keep this in mind if I don't know what your terms mean.


    dart200 - you cunningly avoided answering the above, making all the rest
    a pointless read, and thus a pointless write.

    i'm pretty sure i answer it several times over in the rest of the post,
    so that's why u read the whole post numbnuts ...

    anyways, the hypothetical machines we talk about in undecidable proofs
    are not real deterministic machines because deterministic machines must
    remain determinable at every step of the computation, which those
    undecidable machines aren't.

    these machines which remap themselves based on the response they get
    from a decider do not have determinable behavior, so they cannot be deterministic, and cannot come up in the enumeration of machines.

    what do *actual* undecidable machines look like???

    so far ion my discussion with richard he's concluded *real* machines
    which cannot be classified into the set of programs that halt/not, are
    all non-halting machines that cannot be specifically identified or else
    we'd know they are non-halting machines, breaking the conclusion they
    are undecidable machines.

    that's where we are at in computing: undecidable spooks which can't be specifically identified lest they'd stop being the undecidable spooks
    that they are
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 11:51:27 2025
    From Newsgroup: comp.theory

    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed,
    thus, the limit exists.

    We may not be able to precisely define the line betweem computable
    and non-computable (or decidable vs non-decidable), but we know it
    exists as we have things know to be on both sides.

    We have a number of general propositions that have been proven to be
    uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can
    fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we
    know an answer (if we do) as knowing the answer shows it is knowable.

    Showing that some things might be knowable but not currently know is
    possible, but that does NOT mean we can answer the knowability
    question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know" that
    might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting
    machines with "unknown" behavior actually looks like because then ur
    theory falls apart, despite the fact we can in fact emuerate over all
    machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, how
    are they not the topic???


    It seems you are stuck in a Naive Set Theory system that insists on
    having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts


    What I am talking about is that we can prove that there can not exist of
    a finite algorithm that will always tell if any finite algorithn it is
    given the full description of will reach an answer or not.

    but u can't give me a what logical structure a finite algorithm would
    provably fail in, because all the hypothetical failures demonstrated in undecidability proofs *DO NOT EXIST*


    Since such a decider doesn't exist, we of course can't "describe" it,
    except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with more
    work we CAN determine if they will halt or not, but there will be some
    which we can't (perhaps yet) determine if we can do that.

    well apparently that set will contain machines we *cannot* *ever* know,
    that we *cannot* *know* that we *cannot* *know*, so you can't even show
    me the form of the machine that is not mappable, ur just presuming it exists


    So, the set of machines which we can not know their behavior is not a
    valid set to talk about except in a Naive Set theory, which will itself
    be inconsistant. The fact you keep on harping about that set says you
    don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a possibility
    space than set theory theory, set theory needs to encompass infinite
    sets of real numbers ... computing does not


    Your logic seems to be based on trying to solve Russel's Teapot, which

    ur claiming there's certainly a fucking teapot out there that *can't* be
    found or else it wouldn't exist!

    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Dec 8 13:02:36 2025
    From Newsgroup: comp.theory

    On 12/8/25 4:35 AM, Richard Damon wrote:
    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully deterministic,
    but just run from an infinite number of steps, and for which no
    reduction is available for use to determine that in a finite number of steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to determine.

    Deterministic doesn't mean finite, or reducible to finite.

    because undecidability proofs don't have anything to do with infinite
    work, the all involve hypothesized machines which cannot be classified,
    and therefore also cannot actually exist

    see this is the crux of the issue: proofs of "undecidable" machines
    supposedly disprove the halting algo in order to disprove the existance
    of said undecidable machines ... but in the wake of disproving the
    halting algo ur left with at least one machine that must be undecidable ...

    which defeats the purpose of the proof

    it's a self-defeating concept that has been held onto for almost a
    century for some ungodly reason that you will not specify
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Dec 8 13:03:33 2025
    From Newsgroup: comp.theory

    On 12/8/25 1:02 PM, dart200 wrote:
    On 12/8/25 4:35 AM, Richard Damon wrote:
    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully deterministic,
    but just run from an infinite number of steps, and for which no
    reduction is available for use to determine that in a finite number of
    steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to
    determine.

    Deterministic doesn't mean finite, or reducible to finite.

    because undecidability proofs don't have anything to do with infinite
    work, the all involve hypothesized machines which cannot be classified,

    and this can be shown in finite time,

    and therefore also cannot actually exist

    see this is the crux of the issue: proofs of "undecidable" machines supposedly disprove the halting algo in order to disprove the existance
    of said undecidable machines ... but in the wake of disproving the
    halting algo ur left with at least one machine that must be undecidable ...

    which defeats the purpose of the proof

    it's a self-defeating concept that has been held onto for almost a
    century for some ungodly reason that you will not specify


    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory on Mon Dec 8 18:49:04 2025
    From Newsgroup: comp.theory

    On 12/8/25 4:02 PM, dart200 wrote:
    On 12/8/25 4:35 AM, Richard Damon wrote:
    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully deterministic,
    but just run from an infinite number of steps, and for which no
    reduction is available for use to determine that in a finite number of
    steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to
    determine.

    Deterministic doesn't mean finite, or reducible to finite.

    because undecidability proofs don't have anything to do with infinite
    work, the all involve hypothesized machines which cannot be classified,
    and therefore also cannot actually exist

    Nope, show me one that does that!

    They all show that for every decider, we can make an input that it will
    get wrong, and that input is DIFFERENT for each decider.


    see this is the crux of the issue: proofs of "undecidable" machines supposedly disprove the halting algo in order to disprove the existance
    of said undecidable machines ... but in the wake of disproving the
    halting algo ur left with at least one machine that must be undecidable ...

    No, the crux is you don't understand what you are reading.


    which defeats the purpose of the proof

    Nope, just shows you are stuck on a strawman.


    it's a self-defeating concept that has been held onto for almost a
    century for some ungodly reason that you will not specify



    Again, where do the proofs actually do what you claim, create a SINGLE
    machine that no decider can handle?

    It seems you don't understand what a machine actually is.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 19:13:13 2025
    From Newsgroup: comp.theory

    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed,
    thus, the limit exists.

    We may not be able to precisely define the line betweem computable
    and non-computable (or decidable vs non-decidable), but we know it
    exists as we have things know to be on both sides.

    We have a number of general propositions that have been proven to be
    uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can
    fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we
    know an answer (if we do) as knowing the answer shows it is knowable.

    Showing that some things might be knowable but not currently know is
    possible, but that does NOT mean we can answer the knowability
    question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know" that
    might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting
    machines with "unknown" behavior actually looks like because then ur
    theory falls apart, despite the fact we can in fact emuerate over all
    machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as
    they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, how
    are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists on
    having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of the
    actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show the existance of an input (that varies based on the decider we are talking
    about) that it will get wrong.


    What I am talking about is that we can prove that there can not exist
    of a finite algorithm that will always tell if any finite algorithn it
    is given the full description of will reach an answer or not.

    but u can't give me a what logical structure a finite algorithm would provably fail in, because all the hypothetical failures demonstrated in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an algorithm
    that uses that algorithm, and then does the opposite.

    All algorithms need to fail for that form of input, which again, is a DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that every
    decider fails on at least one input, and the one they fail on can be
    different for every decider.



    Since such a decider doesn't exist, we of course can't "describe" it,
    except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with more
    work we CAN determine if they will halt or not, but there will be some
    which we can't (perhaps yet) determine if we can do that.

    well apparently that set will contain machines we *cannot* *ever* know,
    that we *cannot* *know* that we *cannot* *know*, so you can't even show
    me the form of the machine that is not mappable, ur just presuming it
    exists


    What "Set"? That is the problem, you can't construct that set by any consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end up
    with inconsistant logic.


    So, the set of machines which we can not know their behavior is not a
    valid set to talk about except in a Naive Set theory, which will
    itself be inconsistant. The fact you keep on harping about that set
    says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a possibility space than set theory theory, set theory needs to encompass infinite
    sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot, which

    ur claiming there's certainly a fucking teapot out there that *can't* be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the
    unknowable machine. I don't need the unknowable machine to prove undecidability.

    It seems you are just stuck looking at the case that I point out might
    exists, and just ignore the fact that you keep on misusing the terminology.


    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 17:30:42 2025
    From Newsgroup: comp.theory

    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed,
    thus, the limit exists.

    We may not be able to precisely define the line betweem computable
    and non-computable (or decidable vs non-decidable), but we know it
    exists as we have things know to be on both sides.

    We have a number of general propositions that have been proven to
    be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine can >>>>> fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we
    know an answer (if we do) as knowing the answer shows it is knowable. >>>>>
    Showing that some things might be knowable but not currently know
    is possible, but that does NOT mean we can answer the knowability
    question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know"
    that might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can
    always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting
    machines with "unknown" behavior actually looks like because then ur
    theory falls apart, despite the fact we can in fact emuerate over
    all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as
    they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, how
    are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists on
    having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of the
    actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show the existance of an input (that varies based on the decider we are talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat ur
    own proof's meaning,

    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that look nothing like the paradoxes you construct (because those *cant* exist),
    but if we could point to or describe specifically in any way, that would
    also self-defeat their existence!

    my god the kind of shit the theory of computing has been blowing up
    their asshole for the past century:

    wanking on about unknowable, yet non-halting ghost machines none can
    ever discover lest their theory unravel into a puff of irreconcilable smoke!

    imagine believing in limitations that can't even be known!



    What I am talking about is that we can prove that there can not exist
    of a finite algorithm that will always tell if any finite algorithn
    it is given the full description of will reach an answer or not.

    but u can't give me a what logical structure a finite algorithm would
    provably fail in, because all the hypothetical failures demonstrated
    in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an algorithm
    that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists


    All algorithms need to fail for that form of input, which again, is a DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that every decider fails on at least one input, and the one they fail on can be different for every decider.



    Since such a decider doesn't exist, we of course can't "describe" it,
    except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 classes, >>>
    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with
    more work we CAN determine if they will halt or not, but there will
    be some which we can't (perhaps yet) determine if we can do that.

    well apparently that set will contain machines we *cannot* *ever*
    know, that we *cannot* *know* that we *cannot* *know*, so you can't
    even show me the form of the machine that is not mappable, ur just
    presuming it exists


    What "Set"? That is the problem, you can't construct that set by any consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end up
    with inconsistant logic.


    So, the set of machines which we can not know their behavior is not a
    valid set to talk about except in a Naive Set theory, which will
    itself be inconsistant. The fact you keep on harping about that set
    says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot, which

    ur claiming there's certainly a fucking teapot out there that *can't*
    be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    ur not operating on speculation, u are proposing there exists a *hard*
    and *certain* but *unknowable* teapot that would cease to exist if it
    were ever found...

    and ignore the fact we can certainly enumerate over it. we can infact
    write this teapot down, we apparently just can't know the teapot is the
    teapot we're looking for

    the state of computing theory is mind numbingly ghastly

    unknowable machine. I don't need the unknowable machine to prove undecidability.

    It seems you are just stuck looking at the case that I point out might exists, and just ignore the fact that you keep on misusing the terminology.


    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.


    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Dec 8 17:52:56 2025
    From Newsgroup: comp.theory

    On 12/8/25 3:49 PM, Richard Damon wrote:
    On 12/8/25 4:02 PM, dart200 wrote:
    On 12/8/25 4:35 AM, Richard Damon wrote:
    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully deterministic,
    but just run from an infinite number of steps, and for which no
    reduction is available for use to determine that in a finite number
    of steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to
    determine.

    Deterministic doesn't mean finite, or reducible to finite.

    because undecidability proofs don't have anything to do with infinite
    work, the all involve hypothesized machines which cannot be
    classified, and therefore also cannot actually exist

    Nope, show me one that does that!

    They all show that for every decider, we can make an input that it will
    get wrong, and that input is DIFFERENT for each decider.

    BUT THEN U CLAIM THE DECIDER DOESN'T EXIST SO, SO THAT INPUT DOESN'T
    EXIST, THE PROBLEM OF IRRECONCILABLE INPUT DOESN'T EXIST IN THE REAL ENUMERATION OF MACHINES

    you then just overgeneralize this problem to the rest of computing and fallacious just assume there is some other (but apparently unknowable)
    means to produce an input that could fool any attempt to decide on only
    *real* machines

    that's the fundamental error ur making: an overgeneralization fallacy



    see this is the crux of the issue: proofs of "undecidable" machines
    supposedly disprove the halting algo in order to disprove the
    existance of said undecidable machines ... but in the wake of
    disproving the halting algo ur left with at least one machine that
    must be undecidable ...

    No, the crux is you don't understand what you are reading.


    which defeats the purpose of the proof

    Nope, just shows you are stuck on a strawman.


    it's a self-defeating concept that has been held onto for almost a
    century for some ungodly reason that you will not specify



    Again, where do the proofs actually do what you claim, create a SINGLE machine that no decider can handle?

    It seems you don't understand what a machine actually is.
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 21:24:50 2025
    From Newsgroup: comp.theory

    On 12/8/25 8:30 PM, dart200 wrote:
    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed, >>>>>> thus, the limit exists.

    We may not be able to precisely define the line betweem computable >>>>>> and non-computable (or decidable vs non-decidable), but we know it >>>>>> exists as we have things know to be on both sides.

    We have a number of general propositions that have been proven to >>>>>> be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine
    can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we >>>>>> know an answer (if we do) as knowing the answer shows it is knowable. >>>>>>
    Showing that some things might be knowable but not currently know >>>>>> is possible, but that does NOT mean we can answer the knowability >>>>>> question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the
    decidable and the undeciable there is a band of "we don't know"
    that might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you can >>>>>> always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting
    machines with "unknown" behavior actually looks like because then
    ur theory falls apart, despite the fact we can in fact emuerate
    over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as
    they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, how
    are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists on
    having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of the
    actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show
    the existance of an input (that varies based on the decider we are
    talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat ur
    own proof's meaning,

    I never said the PROBLEM doesn't exist, just that no decider can
    correctly answer the problem for all inputs.

    Maybe you don't understand the nature of problems and answers.


    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that look nothing like the paradoxes you construct (because those *cant* exist),
    but if we could point to or describe specifically in any way, that would also self-defeat their existence!

    Where did I use these ghost machines?




    my god the kind of shit the theory of computing has been blowing up
    their asshole for the past century:

    The only shit is what is in your head, not understand what is being said.


    wanking on about unknowable, yet non-halting ghost machines none can
    ever discover lest their theory unravel into a puff of irreconcilable
    smoke!

    it seems you are stuck in your ghosts


    imagine believing in limitations that can't even be known!

    Why do you say that?

    The limitation is well know, that the halting function can not be computed.

    This means that EVERY attempt to compute it will give some wrong answers.

    That doesn't mean there needs to be a specific input that we can't know
    its halting, even if that might be an implication of that fact.

    For the proposition, the existance of such a machine isn't important.

    It seems you have a problem with "abstract" concepts, like having to
    look at the answers for ALL inputs for the decider to meet the requirements.

    Note, very specifically, for a given machine, there ALWAYS is a machine
    that correctly answer for it, we just might not know which machine it is
    that gives the answer. The the problem of Halting for just a specific
    machine is not uncomputable, even if we don't know the answer, all that
    means is we can't tell which machines were right and which were wrong.




    What I am talking about is that we can prove that there can not
    exist of a finite algorithm that will always tell if any finite
    algorithn it is given the full description of will reach an answer
    or not.

    but u can't give me a what logical structure a finite algorithm would
    provably fail in, because all the hypothetical failures demonstrated
    in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an
    algorithm that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists

    Of what?

    It seems you are stuck on a strawman.

    The non-hypothetical example is that "Halting" is not decidable, as
    there can not exist a machine that gets the right answer for every
    possible machine given to it.

    What is a non-hypothetical example of something said not to exist?

    Can you give me a non-hypothetical example of an even number greater
    than 2 that is prime?



    All algorithms need to fail for that form of input, which again, is a
    DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that every
    decider fails on at least one input, and the one they fail on can be
    different for every decider.



    Since such a decider doesn't exist, we of course can't "describe"
    it, except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3
    classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with
    more work we CAN determine if they will halt or not, but there will
    be some which we can't (perhaps yet) determine if we can do that.

    well apparently that set will contain machines we *cannot* *ever*
    know, that we *cannot* *know* that we *cannot* *know*, so you can't
    even show me the form of the machine that is not mappable, ur just
    presuming it exists


    What "Set"? That is the problem, you can't construct that set by any
    consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end up
    with inconsistant logic.


    So, the set of machines which we can not know their behavior is not
    a valid set to talk about except in a Naive Set theory, which will
    itself be inconsistant. The fact you keep on harping about that set
    says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot, which >>>
    ur claiming there's certainly a fucking teapot out there that *can't*
    be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    No, where did I say that an undecidable machine must exist?

    I claim that no decider can get every input correct, and THAT is the definition that makes the problem uncomputable.

    I point out that this seems to imply that there likely is some machine
    that we can't know if it halts or not, and an implication of that unknowability is that that machine (if it exists) must not halt.


    ur not operating on speculation, u are proposing there exists a *hard*
    and *certain* but *unknowable* teapot that would cease to exist if it
    were ever found...

    Nope, I don't need the "teapot" to exist for Halting to not be computab;le.


    and ignore the fact we can certainly enumerate over it. we can infact
    write this teapot down, we apparently just can't know the teapot is the teapot we're looking for

    Ok, then what even number greater than 2 can not be written as the sum
    of two primes?


    the state of computing theory is mind numbingly ghastly

    Nope, your understanding of it is.


    unknowable machine. I don't need the unknowable machine to prove
    undecidability.

    It seems you are just stuck looking at the case that I point out might
    exists, and just ignore the fact that you keep on misusing the
    terminology.


    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.




    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory on Mon Dec 8 21:24:56 2025
    From Newsgroup: comp.theory

    On 12/8/25 8:52 PM, dart200 wrote:
    On 12/8/25 3:49 PM, Richard Damon wrote:
    On 12/8/25 4:02 PM, dart200 wrote:
    On 12/8/25 4:35 AM, Richard Damon wrote:
    On 12/7/25 11:37 PM, dart200 wrote:
    dude an "undecidable" machine cannot exist, as it's behavior is
    undeterminable which contradicts the deterministic nature of TMs

    That is an incorrect reasoning.

    The "undecidable machine" (if they do exist) are fully
    deterministic, but just run from an infinite number of steps, and
    for which no reduction is available for use to determine that in a
    finite number of steps.

    How do you intend to KNOW in a finite amount of work, which is a
    limitation of all knowledge, something that takes infinite work to
    determine.

    Deterministic doesn't mean finite, or reducible to finite.

    because undecidability proofs don't have anything to do with infinite
    work, the all involve hypothesized machines which cannot be
    classified, and therefore also cannot actually exist

    Nope, show me one that does that!

    They all show that for every decider, we can make an input that it
    will get wrong, and that input is DIFFERENT for each decider.

    BUT THEN U CLAIM THE DECIDER DOESN'T EXIST SO, SO THAT INPUT DOESN'T
    EXIST, THE PROBLEM OF IRRECONCILABLE INPUT DOESN'T EXIST IN THE REAL ENUMERATION OF MACHINES

    Then I guess you are admitting that you can't even CLAIM a decider might
    be a halt decider. We only need a decider that CLAIMS to be a halt
    decider to prove it wrong, or maybe even that there can't be anything
    that would be called a decider.

    The claim is that given any machine you want to try to call a halt
    decider, I can prove you wrong by showing you a definite input that
    makes it wrong.

    The RESULT of being able to do that is that we can show that no decider
    can exist that gets the right answer for all inputs.

    I don't need to make an input for a decider that doesn't exist.


    you then just overgeneralize this problem to the rest of computing and fallacious just assume there is some other (but apparently unknowable)
    means to produce an input that could fool any attempt to decide on only *real* machines

    Nope. But then, the Halting Problem doesn't make direct claims about any
    other computation problem. Since one properly defined problem isn't computable, we know that SOME problems are not computable.

    What have I "overgeneralize", are you thinking I am making things up
    like Olcott does?


    that's the fundamental error ur making: an overgeneralization fallacy


    Nope, it seems you are using the stupidity fallacy, or maybe just the strawbrain fallacy.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 19:06:45 2025
    From Newsgroup: comp.theory

    On 12/8/25 6:24 PM, Richard Damon wrote:
    On 12/8/25 8:30 PM, dart200 wrote:
    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be computed, >>>>>>> thus, the limit exists.

    We may not be able to precisely define the line betweem
    computable and non-computable (or decidable vs non-decidable),
    but we know it exists as we have things know to be on both sides. >>>>>>>
    We have a number of general propositions that have been proven to >>>>>>> be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine >>>>>>> can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove we >>>>>>> know an answer (if we do) as knowing the answer shows it is
    knowable.

    Showing that some things might be knowable but not currently know >>>>>>> is possible, but that does NOT mean we can answer the knowability >>>>>>> question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the >>>>>>> decidable and the undeciable there is a band of "we don't know" >>>>>>> that might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you
    can always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting
    machines with "unknown" behavior actually looks like because then >>>>>> ur theory falls apart, despite the fact we can in fact emuerate
    over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, as >>>>> they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist,
    how are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists on >>>>> having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of the
    actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show
    the existance of an input (that varies based on the decider we are
    talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat ur
    own proof's meaning,

    I never said the PROBLEM doesn't exist, just that no decider can
    correctly answer the problem for all inputs.

    Maybe you don't understand the nature of problems and answers.


    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that
    look nothing like the paradoxes you construct (because those *cant*
    exist), but if we could point to or describe specifically in any way,
    that would also self-defeat their existence!

    Where did I use these ghost machines?




    my god the kind of shit the theory of computing has been blowing up
    their asshole for the past century:

    The only shit is what is in your head, not understand what is being said.


    wanking on about unknowable, yet non-halting ghost machines none can
    ever discover lest their theory unravel into a puff of irreconcilable
    smoke!

    it seems you are stuck in your ghosts


    imagine believing in limitations that can't even be known!

    Why do you say that?

    The limitation is well know, that the halting function can not be computed.

    This means that EVERY attempt to compute it will give some wrong answers.

    That doesn't mean there needs to be a specific input that we can't know
    its halting, even if that might be an implication of that fact.

    For the proposition, the existance of such a machine isn't important.

    It seems you have a problem with "abstract" concepts, like having to
    look at the answers for ALL inputs for the decider to meet the
    requirements.

    Note, very specifically, for a given machine, there ALWAYS is a machine
    that correctly answer for it, we just might not know which machine it is that gives the answer. The the problem of Halting for just a specific machine is not uncomputable, even if we don't know the answer, all that means is we can't tell which machines were right and which were wrong.




    What I am talking about is that we can prove that there can not
    exist of a finite algorithm that will always tell if any finite
    algorithn it is given the full description of will reach an answer
    or not.

    but u can't give me a what logical structure a finite algorithm
    would provably fail in, because all the hypothetical failures
    demonstrated in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an
    algorithm that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists

    Of what?

    It seems you are stuck on a strawman.

    The non-hypothetical example is that "Halting" is not decidable, as
    there can not exist a machine that gets the right answer for every
    possible machine given to it.

    What is a non-hypothetical example of something said not to exist?

    nononono, the undecidable machine *must* exist if halting cannot be
    fully decided upon ...


    Can you give me a non-hypothetical example of an even number greater
    than 2 that is prime?



    All algorithms need to fail for that form of input, which again, is a
    DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that
    every decider fails on at least one input, and the one they fail on
    can be different for every decider.



    Since such a decider doesn't exist, we of course can't "describe"
    it, except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3
    classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with
    more work we CAN determine if they will halt or not, but there will >>>>> be some which we can't (perhaps yet) determine if we can do that.

    well apparently that set will contain machines we *cannot* *ever*
    know, that we *cannot* *know* that we *cannot* *know*, so you can't
    even show me the form of the machine that is not mappable, ur just
    presuming it exists


    What "Set"? That is the problem, you can't construct that set by any
    consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end up
    with inconsistant logic.


    So, the set of machines which we can not know their behavior is not >>>>> a valid set to talk about except in a Naive Set theory, which will
    itself be inconsistant. The fact you keep on harping about that set >>>>> says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot, which >>>>
    ur claiming there's certainly a fucking teapot out there that
    *can't* be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    No, where did I say that an undecidable machine must exist?

    I claim that no decider can get every input correct, and THAT is the definition that makes the problem uncomputable.

    THEREFORE some machines must exist that said decider cannot decide upon:

    the "undecidable" machines,

    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???


    I point out that this seems to imply that there likely is some machine
    that we can't know if it halts or not, and an implication of that unknowability is that that machine (if it exists) must not halt.


    you only speculate it must exist, but the speculation goes so far as to
    claim that speculation is the best we can do, that we cannot even
    specifically know what form of machine it is ... or ur whole freaking
    theory here falls apart


    ur not operating on speculation, u are proposing there exists a *hard*
    and *certain* but *unknowable* teapot that would cease to exist if it
    were ever found...

    Nope, I don't need the "teapot" to exist for Halting to not be computab;le.

    yeah u do: if a decider cannot handle ever input, then there must exist
    the input that the decider cannot handle

    u are asserting that the teapot *must* exist, and go so far as to claim
    that even if we can look at it (which we can, because we can enumerate
    all machines, err "teapots"), we just can't know that the teapot is the specific teapot we're looking for



    and ignore the fact we can certainly enumerate over it. we can infact
    write this teapot down, we apparently just can't know the teapot is
    the teapot we're looking for

    Ok, then what even number greater than 2 can not be written as the sum
    of two primes?


    the state of computing theory is mind numbingly ghastly

    Nope, your understanding of it is.

    i don't buy into claims of fundamentally unknowable ghosts that *must*
    exist bro



    unknowable machine. I don't need the unknowable machine to prove
    undecidability.

    It seems you are just stuck looking at the case that I point out
    might exists, and just ignore the fact that you keep on misusing the
    terminology.


    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.




    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 22:19:01 2025
    From Newsgroup: comp.theory

    On 12/8/25 10:06 PM, dart200 wrote:
    On 12/8/25 6:24 PM, Richard Damon wrote:
    On 12/8/25 8:30 PM, dart200 wrote:
    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be
    computed, thus, the limit exists.

    We may not be able to precisely define the line betweem
    computable and non-computable (or decidable vs non-decidable), >>>>>>>> but we know it exists as we have things know to be on both sides. >>>>>>>>
    We have a number of general propositions that have been proven >>>>>>>> to be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine >>>>>>>> can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not).

    The question of knowABILITY is tougher, as it is easy to prove >>>>>>>> we know an answer (if we do) as knowing the answer shows it is >>>>>>>> knowable.

    Showing that some things might be knowable but not currently
    know is possible, but that does NOT mean we can answer the
    knowability question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the >>>>>>>> decidable and the undeciable there is a band of "we don't know" >>>>>>>> that might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you >>>>>>>> can always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting >>>>>>> machines with "unknown" behavior actually looks like because then >>>>>>> ur theory falls apart, despite the fact we can in fact emuerate >>>>>>> over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results,
    as they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist,
    how are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists
    on having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of the
    actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show
    the existance of an input (that varies based on the decider we are
    talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat
    ur own proof's meaning,

    I never said the PROBLEM doesn't exist, just that no decider can
    correctly answer the problem for all inputs.

    Maybe you don't understand the nature of problems and answers.


    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that
    look nothing like the paradoxes you construct (because those *cant*
    exist), but if we could point to or describe specifically in any way,
    that would also self-defeat their existence!

    Where did I use these ghost machines?




    my god the kind of shit the theory of computing has been blowing up
    their asshole for the past century:

    The only shit is what is in your head, not understand what is being said.


    wanking on about unknowable, yet non-halting ghost machines none can
    ever discover lest their theory unravel into a puff of irreconcilable
    smoke!

    it seems you are stuck in your ghosts


    imagine believing in limitations that can't even be known!

    Why do you say that?

    The limitation is well know, that the halting function can not be
    computed.

    This means that EVERY attempt to compute it will give some wrong answers.

    That doesn't mean there needs to be a specific input that we can't
    know its halting, even if that might be an implication of that fact.

    For the proposition, the existance of such a machine isn't important.

    It seems you have a problem with "abstract" concepts, like having to
    look at the answers for ALL inputs for the decider to meet the
    requirements.

    Note, very specifically, for a given machine, there ALWAYS is a
    machine that correctly answer for it, we just might not know which
    machine it is that gives the answer. The the problem of Halting for
    just a specific machine is not uncomputable, even if we don't know the
    answer, all that means is we can't tell which machines were right and
    which were wrong.




    What I am talking about is that we can prove that there can not
    exist of a finite algorithm that will always tell if any finite
    algorithn it is given the full description of will reach an answer >>>>>> or not.

    but u can't give me a what logical structure a finite algorithm
    would provably fail in, because all the hypothetical failures
    demonstrated in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an
    algorithm that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists

    Of what?

    It seems you are stuck on a strawman.

    The non-hypothetical example is that "Halting" is not decidable, as
    there can not exist a machine that gets the right answer for every
    possible machine given to it.

    What is a non-hypothetical example of something said not to exist?

    nononono, the undecidable machine *must* exist if halting cannot be
    fully decided upon ...


    Can you give me a non-hypothetical example of an even number greater
    than 2 that is prime?



    All algorithms need to fail for that form of input, which again, is
    a DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that
    every decider fails on at least one input, and the one they fail on
    can be different for every decider.



    Since such a decider doesn't exist, we of course can't "describe" >>>>>> it, except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3
    classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with >>>>>> more work we CAN determine if they will halt or not, but there
    will be some which we can't (perhaps yet) determine if we can do
    that.

    well apparently that set will contain machines we *cannot* *ever*
    know, that we *cannot* *know* that we *cannot* *know*, so you can't >>>>> even show me the form of the machine that is not mappable, ur just
    presuming it exists


    What "Set"? That is the problem, you can't construct that set by any
    consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end up
    with inconsistant logic.


    So, the set of machines which we can not know their behavior is
    not a valid set to talk about except in a Naive Set theory, which >>>>>> will itself be inconsistant. The fact you keep on harping about
    that set says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot,
    which

    ur claiming there's certainly a fucking teapot out there that
    *can't* be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    No, where did I say that an undecidable machine must exist?

    I claim that no decider can get every input correct, and THAT is the
    definition that makes the problem uncomputable.

    THEREFORE some machines must exist that said decider cannot decide upon:

    the "undecidable" machines,


    Nope, because nothing says that machine can't be decider by other machines.

    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???

    Nope, THAT decider didn't give the correct answer, not that NO machine
    cna give the correct answer.

    You seem to have a fundamental problem with qualifiers.



    I point out that this seems to imply that there likely is some machine
    that we can't know if it halts or not, and an implication of that
    unknowability is that that machine (if it exists) must not halt.


    you only speculate it must exist, but the speculation goes so far as to claim that speculation is the best we can do, that we cannot even specifically know what form of machine it is ... or ur whole freaking
    theory here falls apart

    No, for a given machine, we have the recipe to build the input that it
    will get wrong.

    Thus, for any existing machine you want to claim to be a prospective
    halt decider, I can show an input that it gets wrong.



    ur not operating on speculation, u are proposing there exists a
    *hard* and *certain* but *unknowable* teapot that would cease to
    exist if it were ever found...

    Nope, I don't need the "teapot" to exist for Halting to not be
    computab;le.

    yeah u do: if a decider cannot handle ever input, then there must exist
    the input that the decider cannot handle

    No I don't, as I can provide a physically demonstratable input for ANY
    machine you want to put forward.

    I don't need to find that elusive unknowable machine.



    u are asserting that the teapot *must* exist, and go so far as to claim
    that even if we can look at it (which we can, because we can enumerate
    all machines, err "teapots"), we just can't know that the teapot is the specific teapot we're looking for


    That the teapot must exist is a RESULT of the fact that we can show that
    the problem is uncomputable. If we had an algorithm that allowed us to
    KNOW the behavior of every machine, then we could make the input on
    whatever that algorithm that we used to know about machines, and that algorithm would be wrong about that machine.



    and ignore the fact we can certainly enumerate over it. we can infact
    write this teapot down, we apparently just can't know the teapot is
    the teapot we're looking for

    Ok, then what even number greater than 2 can not be written as the sum
    of two primes?


    the state of computing theory is mind numbingly ghastly

    Nope, your understanding of it is.

    i don't buy into claims of fundamentally unknowable ghosts that *must*
    exist bro

    That is your problem.

    What can you PROVE about it?

    How do you handle the fact that you can't make a correct decider for ALL inputs?

    How can you KNOW the answer, if you can't make an algorithm to tell you?

    Your problem is you don't understand how knowledge comes about.
    Knowledge comes form things that are computable/provable. The fact we
    can show that some things can not be computed/proven means that some
    things can not be known.

    One of the problems is that while we can know what we know, we can't
    tell out of what we don't know can't be known, and which might
    eventually become known. You seem to want to lable this lack of
    knowledge a "ghost", when it is just reality.




    unknowable machine. I don't need the unknowable machine to prove
    undecidability.

    It seems you are just stuck looking at the case that I point out
    might exists, and just ignore the fact that you keep on misusing the
    terminology.


    is just a logic error. It just shows that there are things whose
    existance / non-existence just are not practically knowable.







    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 19:38:42 2025
    From Newsgroup: comp.theory

    On 12/8/25 7:19 PM, Richard Damon wrote:
    On 12/8/25 10:06 PM, dart200 wrote:
    On 12/8/25 6:24 PM, Richard Damon wrote:
    On 12/8/25 8:30 PM, dart200 wrote:
    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be
    computed, thus, the limit exists.

    We may not be able to precisely define the line betweem
    computable and non-computable (or decidable vs non-decidable), >>>>>>>>> but we know it exists as we have things know to be on both sides. >>>>>>>>>
    We have a number of general propositions that have been proven >>>>>>>>> to be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that machine >>>>>>>>> can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not). >>>>>>>>>
    The question of knowABILITY is tougher, as it is easy to prove >>>>>>>>> we know an answer (if we do) as knowing the answer shows it is >>>>>>>>> knowable.

    Showing that some things might be knowable but not currently >>>>>>>>> know is possible, but that does NOT mean we can answer the
    knowability question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of the >>>>>>>>> decidable and the undeciable there is a band of "we don't know" >>>>>>>>> that might contain some things that "we can't know".

    This is part of the problem of working in infinite spaces, you >>>>>>>>> can always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting >>>>>>>> machines with "unknown" behavior actually looks like because
    then ur theory falls apart, despite the fact we can in fact
    emuerate over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, >>>>>>> as they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, >>>>>> how are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists >>>>>>> on having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of
    the actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can show >>>>> the existance of an input (that varies based on the decider we are
    talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat
    ur own proof's meaning,

    I never said the PROBLEM doesn't exist, just that no decider can
    correctly answer the problem for all inputs.

    Maybe you don't understand the nature of problems and answers.


    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that
    look nothing like the paradoxes you construct (because those *cant*
    exist), but if we could point to or describe specifically in any
    way, that would also self-defeat their existence!

    Where did I use these ghost machines?




    my god the kind of shit the theory of computing has been blowing up
    their asshole for the past century:

    The only shit is what is in your head, not understand what is being
    said.


    wanking on about unknowable, yet non-halting ghost machines none can
    ever discover lest their theory unravel into a puff of
    irreconcilable smoke!

    it seems you are stuck in your ghosts


    imagine believing in limitations that can't even be known!

    Why do you say that?

    The limitation is well know, that the halting function can not be
    computed.

    This means that EVERY attempt to compute it will give some wrong
    answers.

    That doesn't mean there needs to be a specific input that we can't
    know its halting, even if that might be an implication of that fact.

    For the proposition, the existance of such a machine isn't important.

    It seems you have a problem with "abstract" concepts, like having to
    look at the answers for ALL inputs for the decider to meet the
    requirements.

    Note, very specifically, for a given machine, there ALWAYS is a
    machine that correctly answer for it, we just might not know which
    machine it is that gives the answer. The the problem of Halting for
    just a specific machine is not uncomputable, even if we don't know
    the answer, all that means is we can't tell which machines were right
    and which were wrong.




    What I am talking about is that we can prove that there can not >>>>>>> exist of a finite algorithm that will always tell if any finite >>>>>>> algorithn it is given the full description of will reach an
    answer or not.

    but u can't give me a what logical structure a finite algorithm
    would provably fail in, because all the hypothetical failures
    demonstrated in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an
    algorithm that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists

    Of what?

    It seems you are stuck on a strawman.

    The non-hypothetical example is that "Halting" is not decidable, as
    there can not exist a machine that gets the right answer for every
    possible machine given to it.

    What is a non-hypothetical example of something said not to exist?

    nononono, the undecidable machine *must* exist if halting cannot be
    fully decided upon ...


    Can you give me a non-hypothetical example of an even number greater
    than 2 that is prime?



    All algorithms need to fail for that form of input, which again, is >>>>> a DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that
    every decider fails on at least one input, and the one they fail on >>>>> can be different for every decider.



    Since such a decider doesn't exist, we of course can't "describe" >>>>>>> it, except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 >>>>>>> classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that with >>>>>>> more work we CAN determine if they will halt or not, but there
    will be some which we can't (perhaps yet) determine if we can do >>>>>>> that.

    well apparently that set will contain machines we *cannot* *ever* >>>>>> know, that we *cannot* *know* that we *cannot* *know*, so you
    can't even show me the form of the machine that is not mappable,
    ur just presuming it exists


    What "Set"? That is the problem, you can't construct that set by
    any consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end
    up with inconsistant logic.


    So, the set of machines which we can not know their behavior is >>>>>>> not a valid set to talk about except in a Naive Set theory, which >>>>>>> will itself be inconsistant. The fact you keep on harping about >>>>>>> that set says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement.



    Your logic seems to be based on trying to solve Russel's Teapot, >>>>>>> which

    ur claiming there's certainly a fucking teapot out there that
    *can't* be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    No, where did I say that an undecidable machine must exist?

    I claim that no decider can get every input correct, and THAT is the
    definition that makes the problem uncomputable.

    THEREFORE some machines must exist that said decider cannot decide upon:

    the "undecidable" machines,


    Nope, because nothing says that machine can't be decider by other machines.

    that's also just fucking speculation on ur part since you can't even
    point to this machine which cannot be decided by one partial decider,
    but can be by another


    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???

    Nope, THAT decider didn't give the correct answer, not that NO machine
    cna give the correct answer.

    when it comes to hypothesized undecidable proofs ... no machine can
    correctly decide:

    und = () -> halts(und) && loop_forever(), not just halts()

    so know ur just fucking cherry-picking behavior randomly without proof
    or a system to justify it because it suits the world view u've been
    taught for this point in the discussion

    and ur feel confident to not justify anything with specifics... because
    if u could actually point to *real* examples of machines that cannot be decided, then ur fucking theory fucking falls apart

    holy fuck, i can't believe this kinda trash is the consensus


    You seem to have a fundamental problem with qualifiers.

    cut that gaslighting shit out bro




    I point out that this seems to imply that there likely is some
    machine that we can't know if it halts or not, and an implication of
    that unknowability is that that machine (if it exists) must not halt.


    you only speculate it must exist, but the speculation goes so far as
    to claim that speculation is the best we can do, that we cannot even
    specifically know what form of machine it is ... or ur whole freaking
    theory here falls apart

    No, for a given machine, we have the recipe to build the input that it
    will get wrong.

    but none of fucking hypotheticals actually exist!!! what about deciding
    on *only* machines that actually exist???

    i'm imaging u asking next: "how do you limit the input to only machines
    that exist???"

    like, WHAT IN THE FUCK!??? only machines that exist in the full
    enumeration, actually exist!


    Thus, for any existing machine you want to claim to be a prospective
    halt decider, I can show an input that it gets wrong.



    ur not operating on speculation, u are proposing there exists a
    *hard* and *certain* but *unknowable* teapot that would cease to
    exist if it were ever found...

    Nope, I don't need the "teapot" to exist for Halting to not be
    computab;le.

    yeah u do: if a decider cannot handle ever input, then there must
    exist the input that the decider cannot handle

    No I don't, as I can provide a physically demonstratable input for ANY machine you want to put forward.

    I don't need to find that elusive unknowable machine.

    u just need to speculate endlessly about it and assert it's truth,
    because ur so convinced that ur broken ass theory of computing is coherent




    u are asserting that the teapot *must* exist, and go so far as to
    claim that even if we can look at it (which we can, because we can
    enumerate all machines, err "teapots"), we just can't know that the
    teapot is the specific teapot we're looking for


    That the teapot must exist is a RESULT of the fact that we can show that
    the problem is uncomputable. If we had an algorithm that allowed us to
    KNOW the behavior of every machine, then we could make the input on
    whatever that algorithm that we used to know about machines, and that algorithm would be wrong about that machine.

    or maybe theory is just broken instead of fixing it, u shoved it under a fucking rug for the last century in fear of machines that you do nothing
    more than speculate about




    and ignore the fact we can certainly enumerate over it. we can
    infact write this teapot down, we apparently just can't know the
    teapot is the teapot we're looking for

    Ok, then what even number greater than 2 can not be written as the
    sum of two primes?


    the state of computing theory is mind numbingly ghastly

    Nope, your understanding of it is.

    i don't buy into claims of fundamentally unknowable ghosts that *must*
    exist bro

    That is your problem.

    What can you PROVE about it?

    How do you handle the fact that you can't make a correct decider for ALL inputs?

    How can you KNOW the answer, if you can't make an algorithm to tell you?

    Your problem is you don't understand how knowledge comes about.
    Knowledge comes form things that are computable/provable. The fact we
    can show that some things can not be computed/proven means that some
    things can not be known.

    One of the problems is that while we can know what we know, we can't
    tell out of what we don't know can't be known, and which might
    eventually become known. You seem to want to lable this lack of
    knowledge a "ghost", when it is just reality.




    unknowable machine. I don't need the unknowable machine to prove
    undecidability.

    It seems you are just stuck looking at the case that I point out
    might exists, and just ignore the fact that you keep on misusing
    the terminology.


    is just a logic error. It just shows that there are things whose >>>>>>> existance / non-existence just are not practically knowable.







    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Mon Dec 8 22:00:50 2025
    From Newsgroup: comp.theory

    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 23:12:26 2025
    From Newsgroup: comp.theory

    On 12/8/25 10:38 PM, dart200 wrote:
    On 12/8/25 7:19 PM, Richard Damon wrote:
    On 12/8/25 10:06 PM, dart200 wrote:
    On 12/8/25 6:24 PM, Richard Damon wrote:
    On 12/8/25 8:30 PM, dart200 wrote:
    On 12/8/25 4:13 PM, Richard Damon wrote:
    On 12/8/25 2:51 PM, dart200 wrote:
    On 12/8/25 4:31 AM, Richard Damon wrote:
    On 12/7/25 11:28 PM, dart200 wrote:
    On 12/7/25 6:42 PM, Richard Damon wrote:

    Because Turing PROVED that the Halting Problem can't be
    computed, thus, the limit exists.

    We may not be able to precisely define the line betweem
    computable and non-computable (or decidable vs non-decidable), >>>>>>>>>> but we know it exists as we have things know to be on both sides. >>>>>>>>>>
    We have a number of general propositions that have been proven >>>>>>>>>> to be uncomputable/undecidable, like the Halting Problem.

    When we narrow the question to a specific machine, that
    machine can fall into 3 camps.

    Known to Halt.
    Known to Never Halt.
    Unknown in behavior (but we know it will either halt of not). >>>>>>>>>>
    The question of knowABILITY is tougher, as it is easy to prove >>>>>>>>>> we know an answer (if we do) as knowing the answer shows it is >>>>>>>>>> knowable.

    Showing that some things might be knowable but not currently >>>>>>>>>> know is possible, but that does NOT mean we can answer the >>>>>>>>>> knowability question for all things that are knowable.

    Why are you so stuck in the fact that between the domain of >>>>>>>>>> the decidable and the undeciable there is a band of "we don't >>>>>>>>>> know" that might contain some things that "we can't know". >>>>>>>>>>
    This is part of the problem of working in infinite spaces, you >>>>>>>>>> can always end up with a piece you don't know about.

    u put urself in a mathematical jam,

    can't actually show me what one of these apparently non-halting >>>>>>>>> machines with "unknown" behavior actually looks like because >>>>>>>>> then ur theory falls apart, despite the fact we can in fact >>>>>>>>> emuerate over all machines ...

    so idk wtf u think u'r actually talking about there buddy


    But I don't need to talk about machines with unknowable results, >>>>>>>> as they aren't the topic of the problem.

    ... what??? the halting problem is literally ur proof they exist, >>>>>>> how are they not the topic???


    Nope. It seems you don't understand the words I am using.



    It seems you are stuck in a Naive Set Theory system that insists >>>>>>>> on having Sets based on just a description of them.

    and ur stuck on believing in machine ghosts

    Nope, I believe your ghosts exist, but they are not the based of
    the actual proof.

    Which is that a "Correct Halt Decider" is the ghost, as we can
    show the existance of an input (that varies based on the decider
    we are talking about) that it will get wrong.

    after which u declare that problem to not actually exist and defeat >>>>> ur own proof's meaning,

    I never said the PROBLEM doesn't exist, just that no decider can
    correctly answer the problem for all inputs.

    Maybe you don't understand the nature of problems and answers.


    and try to make up for this by supposing (but not actually
    demonstrating) that there must be instead some ghost machines that
    look nothing like the paradoxes you construct (because those *cant* >>>>> exist), but if we could point to or describe specifically in any
    way, that would also self-defeat their existence!

    Where did I use these ghost machines?




    my god the kind of shit the theory of computing has been blowing up >>>>> their asshole for the past century:

    The only shit is what is in your head, not understand what is being
    said.


    wanking on about unknowable, yet non-halting ghost machines none
    can ever discover lest their theory unravel into a puff of
    irreconcilable smoke!

    it seems you are stuck in your ghosts


    imagine believing in limitations that can't even be known!

    Why do you say that?

    The limitation is well know, that the halting function can not be
    computed.

    This means that EVERY attempt to compute it will give some wrong
    answers.

    That doesn't mean there needs to be a specific input that we can't
    know its halting, even if that might be an implication of that fact.

    For the proposition, the existance of such a machine isn't important.

    It seems you have a problem with "abstract" concepts, like having to
    look at the answers for ALL inputs for the decider to meet the
    requirements.

    Note, very specifically, for a given machine, there ALWAYS is a
    machine that correctly answer for it, we just might not know which
    machine it is that gives the answer. The the problem of Halting for
    just a specific machine is not uncomputable, even if we don't know
    the answer, all that means is we can't tell which machines were
    right and which were wrong.




    What I am talking about is that we can prove that there can not >>>>>>>> exist of a finite algorithm that will always tell if any finite >>>>>>>> algorithn it is given the full description of will reach an
    answer or not.

    but u can't give me a what logical structure a finite algorithm >>>>>>> would provably fail in, because all the hypothetical failures
    demonstrated in undecidability proofs *DO NOT EXIST*

    Sure, for any finite halt decision algorithm, to decide on an
    algorithm that uses that algorithm, and then does the opposite.

    i asked for a non-hypothetical example that actually exists

    Of what?

    It seems you are stuck on a strawman.

    The non-hypothetical example is that "Halting" is not decidable, as
    there can not exist a machine that gets the right answer for every
    possible machine given to it.

    What is a non-hypothetical example of something said not to exist?

    nononono, the undecidable machine *must* exist if halting cannot be
    fully decided upon ...


    Can you give me a non-hypothetical example of an even number greater
    than 2 that is prime?



    All algorithms need to fail for that form of input, which again,
    is a DIFFERENT input for every claimed decider.

    We don't need to find a single input that all fail on, just that
    every decider fails on at least one input, and the one they fail
    on can be different for every decider.



    Since such a decider doesn't exist, we of course can't
    "describe" it, except by point out its absence.

    Yes, we can enumerate over all machines, and divide them into 3 >>>>>>>> classes,

    Known to Halt,
    Known to not Halt.
    We don't know (possibly just yet) what they do.

    In that last class, there may be some that we can prove that
    with more work we CAN determine if they will halt or not, but >>>>>>>> there will be some which we can't (perhaps yet) determine if we >>>>>>>> can do that.

    well apparently that set will contain machines we *cannot* *ever* >>>>>>> know, that we *cannot* *know* that we *cannot* *know*, so you
    can't even show me the form of the machine that is not mappable, >>>>>>> ur just presuming it exists


    What "Set"? That is the problem, you can't construct that set by
    any consistent set theory.

    You need to rely on "Naive" set theory to build your set, you end >>>>>> up with inconsistant logic.


    So, the set of machines which we can not know their behavior is >>>>>>>> not a valid set to talk about except in a Naive Set theory,
    which will itself be inconsistant. The fact you keep on harping >>>>>>>> about that set says you don't understand the problem with it.

    this is computing theory bro, it's a lot more constrained a
    possibility space than set theory theory, set theory needs to
    encompass infinite sets of real numbers ... computing does not

    So? If you can't build the set, you can't use it in your arguement. >>>>>>


    Your logic seems to be based on trying to solve Russel's Teapot, >>>>>>>> which

    ur claiming there's certainly a fucking teapot out there that
    *can't* be found or else it wouldn't exist!

    Nope, my comment was that there might be a teapot out there, the

    MIGHT?!?! BRO, you claim there *MUST* be one ... holy shit bro

    No, where did I say that an undecidable machine must exist?

    I claim that no decider can get every input correct, and THAT is the
    definition that makes the problem uncomputable.

    THEREFORE some machines must exist that said decider cannot decide upon: >>>
    the "undecidable" machines,


    Nope, because nothing says that machine can't be decider by other
    machines.

    that's also just fucking speculation on ur part since you can't even
    point to this machine which cannot be decided by one partial decider,
    but can be by another

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
    else halt.

    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider.

    It seems you are stuck on your strawman with confused qualification that
    NO machine can decide that input correctly, but that isn't the claim,
    only that this particular one doesn't.

    The fact that I can ALWAYS make such a machine for ANY decider you may
    want to create means that:

    For ALL deciders H, there exist an input H^ that that particual H gets
    wrong.

    THus, but the logic of qualifies, this means that there does not exist
    any H that gets the correct answer for all inputs.



    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???

    Nope, THAT decider didn't give the correct answer, not that NO machine
    cna give the correct answer.

    when it comes to hypothesized undecidable proofs ... no machine can correctly decide:

    und = () -> halts(und) && loop_forever(), not just halts()

    Note, this und isn't a machine until a particular Halts is chosen, and
    DOES show that any prospecive Halt Decider can't be an always correct
    halt decider.

    Thus, you yourself just showed the input for the GIVEN decider "halts"


    so know ur just fucking cherry-picking behavior randomly without proof
    or a system to justify it because it suits the world view u've been
    taught for this point in the discussion

    No, we know your brain is just mush, as you just demonstrated the point
    you claimed couldn't be shown.


    and ur feel confident to not justify anything with specifics... because
    if u could actually point to *real* examples of machines that cannot be decided, then ur fucking theory fucking falls apart

    And what isn't specific about your "und" template.

    Note, you err in calling it a machine, as it isn't a machine until
    paired with a particular "halts" decider.


    holy fuck, i can't believe this kinda trash is the consensus

    Yes, I can't believe how you keep on repeating your error of not knowing
    what you are talking about,



    You seem to have a fundamental problem with qualifiers.

    cut that gaslighting shit out bro

    What gaslighting?

    You just proved the point you said couldn't be shown, but you can't
    recognize it.





    I point out that this seems to imply that there likely is some
    machine that we can't know if it halts or not, and an implication of
    that unknowability is that that machine (if it exists) must not halt.


    you only speculate it must exist, but the speculation goes so far as
    to claim that speculation is the best we can do, that we cannot even
    specifically know what form of machine it is ... or ur whole freaking
    theory here falls apart

    No, for a given machine, we have the recipe to build the input that it
    will get wrong.

    but none of fucking hypotheticals actually exist!!! what about deciding
    on *only* machines that actually exist???

    but "halt" isn't just a hypothetical, it is the placeholder for ANY
    decider you want to try to claim.


    i'm imaging u asking next: "how do you limit the input to only machines
    that exist???"

    Because the all do, at least if your claimed halt exist.

    If you admit that there is not possible halt to exist, then you have
    agreed to the proposition and don't need further proof.



    like, WHAT IN THE FUCK!??? only machines that exist in the full
    enumeration, actually exist!

    Right, and non of them give the right answer to the und built from them,
    so none of them can be a correct halt decider.



    Thus, for any existing machine you want to claim to be a prospective
    halt decider, I can show an input that it gets wrong.



    ur not operating on speculation, u are proposing there exists a
    *hard* and *certain* but *unknowable* teapot that would cease to
    exist if it were ever found...

    Nope, I don't need the "teapot" to exist for Halting to not be
    computab;le.

    yeah u do: if a decider cannot handle ever input, then there must
    exist the input that the decider cannot handle

    No I don't, as I can provide a physically demonstratable input for ANY
    machine you want to put forward.

    I don't need to find that elusive unknowable machine.

    u just need to speculate endlessly about it and assert it's truth,
    because ur so convinced that ur broken ass theory of computing is coherent

    Because it IS true, and your problem is you don't understand the logic
    of universals.

    If I can show that ALL are incorrect, I have shown that NONE are correct.

    If you are looking for an example form that "none", you don't understand
    how logic works.





    u are asserting that the teapot *must* exist, and go so far as to
    claim that even if we can look at it (which we can, because we can
    enumerate all machines, err "teapots"), we just can't know that the
    teapot is the specific teapot we're looking for


    That the teapot must exist is a RESULT of the fact that we can show
    that the problem is uncomputable. If we had an algorithm that allowed
    us to KNOW the behavior of every machine, then we could make the input
    on whatever that algorithm that we used to know about machines, and
    that algorithm would be wrong about that machine.

    or maybe theory is just broken instead of fixing it, u shoved it under a fucking rug for the last century in fear of machines that you do nothing more than speculate about

    If your idea of "fixing" a system is to just declair it broken, you are showing your stupidity.

    All you are doing is showing your ignorance.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,sci.logic,sci.math on Mon Dec 8 23:20:28 2025
    From Newsgroup: comp.theory

    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification for
    the test.

    The problem is you (and Bill) just don't understand it.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete systems.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Mon Dec 8 22:33:16 2025
    From Newsgroup: comp.theory

    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification for
    the test.

    The problem is you (and Bill) just don't understand it.


    He and Eric have been PhD computer science professors
    for decades. Of course that by itself means that
    they must be woefully less than your own infallibility.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete systems.

    That has nothing to do with foundations.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Mon Dec 8 22:51:37 2025
    From Newsgroup: comp.theory

    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification for
    the test.

    The problem is you (and Bill) just don't understand it.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete systems.

    With the text of each program P we associate a
    unique number ⌈P⌉, known as the program’s encoding,
    which will stand for the program when we want to
    use that program as data, e.g. when passing one
    program to another as an argument.

    You are just terribly inaccurate in paraphrasing.
    Perhaps speaking to no one at all is better than
    talking to you.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,sci.logic,sci.math on Mon Dec 8 20:54:27 2025
    From Newsgroup: comp.theory

    On 12/8/25 8:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    stoddart didn't want to discuss anything and i've been pissing off eric
    u saw the emails
    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Mon Dec 8 23:02:20 2025
    From Newsgroup: comp.theory

    On 12/8/2025 10:54 PM, dart200 wrote:
    On 12/8/25 8:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    stoddart didn't want to discuss anything and i've been pissing off eric
    u saw the emails


    None the less you can carefully examine
    his work and see how and where he affirms
    your position. Eric is happy with me.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Mon Dec 8 21:23:35 2025
    From Newsgroup: comp.theory

    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
           else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider.

    partial decidable does not fly it loses to BB

    if BB has some limit L (which is must if u believe halting problem),
    then there must be some specifically L-state machine which *no* machine
    could decide upon, for if that machine was decidable by anything, then
    BB could find that anything and subvert the limit L


    It seems you are stuck on your strawman with confused qualification that
    NO machine can decide that input correctly, but that isn't the claim,
    only that this particular one doesn't.

    The fact that I can ALWAYS make such a machine for ANY decider you may
    want to create means that:

    For ALL deciders H, there exist an input H^ that that particual H gets wrong.

    or ur theory is just broken and u refuse to address it


    THus, but the logic of qualifies, this means that there does not exist
    any H that gets the correct answer for all inputs.



    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???

    Nope, THAT decider didn't give the correct answer, not that NO
    machine cna give the correct answer.

    when it comes to hypothesized undecidable proofs ... no machine can
    correctly decide:

    und = () -> halts(und) && loop_forever(), not just halts()

    Note, this und isn't a machine until a particular Halts is chosen, and
    DOES show that any prospecive Halt Decider can't be an always correct
    halt decider.

    Thus, you yourself just showed the input for the GIVEN decider "halts"


    so know ur just fucking cherry-picking behavior randomly without proof
    or a system to justify it because it suits the world view u've been
    taught for this point in the discussion

    No, we know your brain is just mush, as you just demonstrated the point
    you claimed couldn't be shown.

    yeah cause i know what ur arguments are u retard, i just don't agree
    because they result in a bunch of barely justified extrapolation about unknowable math ghosts preventing u from effectively computing a halting map

    i think it's bunk, we (those who don't agree with the halting problem)
    just haven't quite nailed down the contradiction involved succinctly enough
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,sci.logic,sci.math on Tue Dec 9 07:42:25 2025
    From Newsgroup: comp.theory

    On 12/8/25 11:51 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete
    systems.

    With the text of each program P we associate a
    unique number ⌈P⌉, known as the program’s encoding,
    which will stand for the program when we want to
    use that program as data, e.g. when passing one
    program to another as an argument.

    You are just terribly inaccurate in paraphrasing.
    Perhaps speaking to no one at all is better than
    talking to you.


    Except there are many texts that create the equivalent program, and thus
    many numbers for that program.

    Yes, we can convert a program into data, but there are many data values
    that all represent the same program.

    This means that Program H can't use a "unique" value of its
    representation to detect the input using it, as the pathological program
    can just use an equivalent variation not in the finite list of values
    that H tests for.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,sci.logic,sci.math on Tue Dec 9 07:42:26 2025
    From Newsgroup: comp.theory

    On 12/8/25 11:33 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.


    He and Eric have been PhD computer science professors
    for decades. Of course that by itself means that
    they must be woefully less than your own infallibility.

    So?

    Appeal to Authority is just a FALICY.

    The fact this is you full arguement just show the error in your logic.


    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete
    systems.

    That has nothing to do with foundations.


    Sure it does.

    His decider check if the input uses it. That is based on the decider
    being able to detect that usage. Since there is no unique value to test,
    the test can't be done.

    Your logic is based on assuming you can make assumptions about things
    that are not true, and thus your logic is based on falsehoods being
    true, and thus shows it is just unsound, as are you.

    Sorry, all you are doing is showing how bad your logic abilities.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 07:42:29 2025
    From Newsgroup: comp.theory

    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to not answer.


    if BB has some limit L (which is must if u believe halting problem),
    then there must be some specifically L-state machine which *no* machine could decide upon, for if that machine was decidable by anything, then
    BB could find that anything and subvert the limit L

    WHy does BB need to have a limit L?

    There may be a limit to its input that BB can create a correct answer.

    IF you allow "partial decidability", then BB just can't use a partial
    decider to correctly get its answer.

    The issue is your BB is like the Ghost you keep on trying to talk about.
    It is a machine that just doesn't exist, a you can't take the limit of a
    thing that doesn't exist.

    And you have it wrong. There are machine that can correctly decide on
    that BB, it is just we can't tell which machines those are or if any
    given machine is in that set. Because we can't tell if that machine just happened to get the right answer, we can't get the knowledge out of it.

    The problem is that just because some "random" machine gives the right
    answer, if we don't know it does, then BB couldn't has used it to make
    its decision.



    It seems you are stuck on your strawman with confused qualification
    that NO machine can decide that input correctly, but that isn't the
    claim, only that this particular one doesn't.

    The fact that I can ALWAYS make such a machine for ANY decider you may
    want to create means that:

    For ALL deciders H, there exist an input H^ that that particual H gets
    wrong.

    or ur theory is just broken and u refuse to address it

    So, what is broken. The only broken thing I have seen so far is your logic.

    You don't seem to know what you are actually talking about.



    THus, but the logic of qualifies, this means that there does not exist
    any H that gets the correct answer for all inputs.



    that can't look anything like the hypothetical machines in
    undecidability proofs that don't actually exist???

    Nope, THAT decider didn't give the correct answer, not that NO
    machine cna give the correct answer.

    when it comes to hypothesized undecidable proofs ... no machine can
    correctly decide:

    und = () -> halts(und) && loop_forever(), not just halts()

    Note, this und isn't a machine until a particular Halts is chosen, and
    DOES show that any prospecive Halt Decider can't be an always correct
    halt decider.

    Thus, you yourself just showed the input for the GIVEN decider "halts"


    so know ur just fucking cherry-picking behavior randomly without
    proof or a system to justify it because it suits the world view u've
    been taught for this point in the discussion

    No, we know your brain is just mush, as you just demonstrated the
    point you claimed couldn't be shown.

    yeah cause i know what ur arguments are u retard, i just don't agree
    because they result in a bunch of barely justified extrapolation about unknowable math ghosts preventing u from effectively computing a halting
    map

    In other words, you don't like the truth, so you mush your brain to try
    to claim it can't be.


    i think it's bunk, we (those who don't agree with the halting problem)
    just haven't quite nailed down the contradiction involved succinctly enough


    In other words, you think personal opinions are greater than
    mathematical proof.

    That is the proof that your brain is just mush.

    You "Know" you must be right, without any actual proof, so you ignore
    the truth and prove your stupidity.

    The problem is, Truth *IS* true, and you can't just assume it isn't, and
    lies are lies and you can't make them the truth.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Tue Dec 9 09:39:50 2025
    From Newsgroup: comp.theory

    On 12/9/2025 6:42 AM, Richard Damon wrote:
    On 12/8/25 11:51 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete
    systems.

    With the text of each program P we associate a
    unique number ⌈P⌉, known as the program’s encoding,
    which will stand for the program when we want to
    use that program as data, e.g. when passing one
    program to another as an argument.

    You are just terribly inaccurate in paraphrasing.
    Perhaps speaking to no one at all is better than
    talking to you.


    Except there are many texts that create the equivalent program, and thus many numbers for that program.


    He is doing this like Gödel numbers, thus a unique
    identifier is needed. And again this is merely nit-picky
    his point is that the foundations of computer science
    are incorrect and I have shown that two different ways.

    Yes, we can convert a program into data, but there are many data values
    that all represent the same program.


    No there are not you are just not being precise enough
    in your choice of words. And yet again this is an
    irrelevant nit-picky detail.

    This means that Program H can't use a "unique" value of its
    representation to detect the input using it, as the pathological program
    can just use an equivalent variation not in the finite list of values
    that H tests for.

    If the finite strings are not identical then the
    inputs are not identical.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Tue Dec 9 09:53:11 2025
    From Newsgroup: comp.theory

    On 12/9/2025 6:42 AM, Richard Damon wrote:
    On 12/8/25 11:33 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.


    He and Eric have been PhD computer science professors
    for decades. Of course that by itself means that
    they must be woefully less than your own infallibility.

    So?

    Appeal to Authority is just a FALICY.

    The fact this is you full arguement just show the error in your logic.


    He and Eric just understand these things better
    than you and you lack of understanding is not
    a rebuttal. I honestly believe that you are
    capable of understanding these very difficult
    things if you merely give up your insistence
    on remaining in rebuttal mode.

    It has take me more than 21 years to finally get
    clear and correct words that are consistent with
    standard definitions. For my first fifteen years
    I only had strongly held intuitions and had to
    overload terms of the art with different meanings
    because there were no exiting terms that conveyed
    the meanings that I needed to convey.


    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE encoding
    for every program, which is a false assumption in Turing Complete
    systems.

    That has nothing to do with foundations.


    Sure it does.

    His decider check if the input uses it. That is based on the decider
    being able to detect that usage. Since there is no unique value to test,
    the test can't be done.


    For the conventional halting problem proof there
    is a unique value. That the proof can be adapted
    is off-topic. We must make one point at a time
    with no leaping to conclusions.

    Your logic is based on assuming you can make assumptions about things
    that are not true, and thus your logic is based on falsehoods being
    true, and thus shows it is just unsound, as are you.

    Sorry, all you are doing is showing how bad your logic abilities.

    That I understand these things at deeper philosophical
    levels is not any lack of understanding on my part. I
    am merely having the same problem as Ludwig Wittgenstein
    in that mathematicians and logicians are rigid-minded
    and utterly unwilling to reexamine philosophical foundations.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 10:55:46 2025
    From Newsgroup: comp.theory

    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did
    explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders that
    try to decide on it:

    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get there
    later)



    if BB has some limit L (which is must if u believe halting problem),
    then there must be some specifically L-state machine which *no*
    machine could decide upon, for if that machine was decidable by
    anything, then BB could find that anything and subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    if you believe the halting problem, then BB must have a limit L, or else halting becomes generally solvable using the BB function. see, if you
    can compute the BB number for any N-state machines, then for any N-state machine u can just run the N-state machine until BB number of steps. any machine that halts on or before BB(N) steps halts, any that run past
    must be nonhalting

    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-state machine, until one comes back with an halting answer, for every N-state machine, which then it can the use to decide what the BB number is for
    any N ...

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    so no richard, partial decidability does not work if BB is to have a limit
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 12:22:00 2025
    From Newsgroup: comp.theory

    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in
    Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    Nope, as it has an non-determinism/non-input that affects its behavior. Computation theory is about the mapping of input to output, so any non- determinism or dependency of a "non-input" isn't allowed, as the machine
    no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing something here.


    There ARE variants of computation theory that handles such machines, but
    not about individual runs, but about the collection of all runs. They "branch" the path at each non-deterministic point, and look at the final result, using a couple of different criteria.

    My fuzzer keeps trying to hit all paths in DD and keeps per-path
    counters. So, it accounts for all runs. This is only dealing with PO's DD.

    int DD()
    {
    10: int Halt_Status = HHH(DD);
    20: if (Halt_Status)
    30: HERE: goto HERE;
    40: return Halt_Status;
    }


    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or non-
    halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered interesting for the theory.

    DD can halt, or not depending on what HHH returns. If we can hit all
    paths then we have full coverage of DD and the simulation can fin.

    [...]
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From wij@wyniijj5@gmail.com to comp.theory on Wed Dec 10 05:56:48 2025
    From Newsgroup: comp.theory

    On Tue, 2025-12-09 at 10:55 -0800, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders that
    try to decide on it:

    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get there later)



    if BB has some limit L (which is must if u believe halting problem), then there must be some specifically L-state machine which *no*
    machine could decide upon, for if that machine was decidable by anything, then BB could find that anything and subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    if you believe the halting problem, then BB must have a limit L, or else halting becomes generally solvable using the BB function. see, if you
    can compute the BB number for any N-state machines, then for any N-state machine u can just run the N-state machine until BB number of steps. any machine that halts on or before BB(N) steps halts, any that run past
    must be nonhalting

    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-state machine, until one comes back with an halting answer, for every N-state machine, which then it can the use to decide what the BB number is for
    any N ...

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    so no richard, partial decidability does not work if BB is to have a limit
    Don't be silly. Even god cannot solve the Halting Problem. https://sourceforge.net/projects/cscall/files/MisFiles/ghp.txt/download
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From wij@wyniijj5@gmail.com to comp.theory on Wed Dec 10 05:59:43 2025
    From Newsgroup: comp.theory

    On Tue, 2025-12-09 at 12:22 -0800, Chris M. Thomasson wrote:
    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    Nope, as it has an non-determinism/non-input that affects its behavior. Computation theory is about the mapping of input to output, so any non- determinism or dependency of a "non-input" isn't allowed, as the machine no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing something here.


    There ARE variants of computation theory that handles such machines, but not about individual runs, but about the collection of all runs. They "branch" the path at each non-deterministic point, and look at the final result, using a couple of different criteria.

    My fuzzer keeps trying to hit all paths in DD and keeps per-path
    counters. So, it accounts for all runs. This is only dealing with PO's DD.

    int DD()
    {
    10:    int Halt_Status = HHH(DD);
    20:    if (Halt_Status)
    30:       HERE: goto HERE;
    40:    return Halt_Status;
    }


    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or non- halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered interesting for the theory.

    DD can halt, or not depending on what HHH returns. If we can hit all
    paths then we have full coverage of DD and the simulation can fin.

    [...]
    That is correct that DD's *definition* relies on HHH, which has to be deterministic. I.e. DD is created AFTER HHH is given. Whatever you call
    HHH, e.g. (correct) simulator, termination analyser (more powerful than
    TM),... almighty god, does not change anything. The HP is undecidable. https://sourceforge.net/projects/cscall/files/MisFiles/ghp.txt/download
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Tristan Wibberley@tristan.wibberley+netnews2@alumni.manchester.ac.uk to comp.theory on Tue Dec 9 22:18:30 2025
    From Newsgroup: comp.theory

    On 08/12/2025 19:23, dart200 wrote:
    On 12/8/25 1:48 AM, Tristan Wibberley wrote:
    On 08/12/2025 04:37, dart200 wrote:
    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist.

    Is a "real TM" any different to a TM?  If so, on what way?  What is an >>>> undecidable machine (or, for that matter, a decidable machine)?  I
    can't
    keep this in mind if I don't know what your terms mean.


    dart200 - you cunningly avoided answering the above, making all the rest
    a pointless read, and thus a pointless write.

    i'm pretty sure i answer it several times over in the rest of the post,
    so that's why u read the whole post numbnuts ...

    no that's not right.
    --
    Tristan Wibberley

    The message body is Copyright (C) 2025 Tristan Wibberley except
    citations and quotations noted. All Rights Reserved except that you may,
    of course, cite it academically giving credit to me, distribute it
    verbatim as part of a usenet system or its archives, and use it to
    promote my greatness and general superiority without misrepresentation
    of my opinions other than my opinion of my greatness and general
    superiority which you _may_ misrepresent. You definitely MAY NOT train
    any production AI system with it but you may train experimental AI that
    will only be used for evaluation of the AI methods it implements.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic,sci.math on Tue Dec 9 16:24:24 2025
    From Newsgroup: comp.theory

    On 12/9/2025 2:22 PM, Chris M. Thomasson wrote:
    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in
    Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    Nope, as it has an non-determinism/non-input that affects its
    behavior. Computation theory is about the mapping of input to output,
    so any non- determinism or dependency of a "non-input" isn't allowed,
    as the machine no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing something here.


    There ARE variants of computation theory that handles such machines,
    but not about individual runs, but about the collection of all runs.
    They "branch" the path at each non-deterministic point, and look at
    the final result, using a couple of different criteria.

    My fuzzer keeps trying to hit all paths in DD and keeps per-path
    counters. So, it accounts for all runs. This is only dealing with PO's DD.

    int DD()
    {
    10:    int Halt_Status = HHH(DD);
    20:    if (Halt_Status)
    30:       HERE: goto HERE;
    40:    return Halt_Status;
    }


    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or non-
    halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered
    interesting for the theory.

    DD can halt, or not depending on what HHH returns. If we can hit all
    paths then we have full coverage of DD and the simulation can fin.

    [...]

    These are finally the long sought words that do
    resolve the halting problem to a category error.

    Turing machine deciders only compute the mapping from
    their [finite string] inputs to an accept or reject
    state on the basis that this [finite string] input
    specifies or fails to specify a particular semantic
    or syntactic property.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory on Tue Dec 9 16:25:49 2025
    From Newsgroup: comp.theory

    On 12/9/2025 3:59 PM, wij wrote:
    On Tue, 2025-12-09 at 12:22 -0800, Chris M. Thomasson wrote:
    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt. >>>>>
    If that is for the same, it isn't a "Program" (aka an algorithm) in
    Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle. >>>
    Nope, as it has an non-determinism/non-input that affects its behavior.
    Computation theory is about the mapping of input to output, so any non-
    determinism or dependency of a "non-input" isn't allowed, as the machine >>> no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing
    something here.


    There ARE variants of computation theory that handles such machines, but >>> not about individual runs, but about the collection of all runs. They
    "branch" the path at each non-deterministic point, and look at the final >>> result, using a couple of different criteria.

    My fuzzer keeps trying to hit all paths in DD and keeps per-path
    counters. So, it accounts for all runs. This is only dealing with PO's DD. >>
    int DD()
    {
    10:    int Halt_Status = HHH(DD);
    20:    if (Halt_Status)
    30:       HERE: goto HERE;
    40:    return Halt_Status;
    }


    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or non-
    halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered
    interesting for the theory.

    DD can halt, or not depending on what HHH returns. If we can hit all
    paths then we have full coverage of DD and the simulation can fin.

    [...]

    That is correct that DD's *definition* relies on HHH, which has to be deterministic. I.e. DD is created AFTER HHH is given. Whatever you call
    HHH, e.g. (correct) simulator, termination analyser (more powerful than TM),... almighty god, does not change anything. The HP is undecidable. https://sourceforge.net/projects/cscall/files/MisFiles/ghp.txt/download


    These are finally the long sought words that do
    resolve the halting problem to a category error.

    Turing machine deciders only compute the mapping from
    their [finite string] inputs to an accept or reject
    state on the basis that this [finite string] input
    specifies or fails to specify a particular semantic
    or syntactic property.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Tue Dec 9 14:48:04 2025
    From Newsgroup: comp.theory

    On 12/9/25 2:18 PM, Tristan Wibberley wrote:
    On 08/12/2025 19:23, dart200 wrote:
    On 12/8/25 1:48 AM, Tristan Wibberley wrote:
    On 08/12/2025 04:37, dart200 wrote:
    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist. >>>>>
    Is a "real TM" any different to a TM?  If so, on what way?  What is an >>>>> undecidable machine (or, for that matter, a decidable machine)?  I
    can't
    keep this in mind if I don't know what your terms mean.


    dart200 - you cunningly avoided answering the above, making all the rest >>> a pointless read, and thus a pointless write.

    i'm pretty sure i answer it several times over in the rest of the post,
    so that's why u read the whole post numbnuts ...

    no that's not right.


    bruh if ur just gunna cut out everything i post and just arbitrarily
    disagree like a worthless troll ...

    don't bother replying
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory on Tue Dec 9 16:54:02 2025
    From Newsgroup: comp.theory

    On 12/9/2025 4:48 PM, dart200 wrote:
    On 12/9/25 2:18 PM, Tristan Wibberley wrote:
    On 08/12/2025 19:23, dart200 wrote:
    On 12/8/25 1:48 AM, Tristan Wibberley wrote:
    On 08/12/2025 04:37, dart200 wrote:
    On 12/7/25 5:46 PM, Ben Bacarisse wrote:
    dart200 <user7160@newsgrouper.org.invalid> writes:

    keep in mind: all real TMs exist, undecidable machines do not exist. >>>>>>
    Is a "real TM" any different to a TM?  If so, on what way?  What >>>>>> is an
    undecidable machine (or, for that matter, a decidable machine)?  I >>>>>> can't
    keep this in mind if I don't know what your terms mean.


    dart200 - you cunningly avoided answering the above, making all the
    rest
    a pointless read, and thus a pointless write.

    i'm pretty sure i answer it several times over in the rest of the post,
    so that's why u read the whole post numbnuts ...

    no that's not right.


    bruh if ur just gunna cut out everything i post and just arbitrarily disagree like a worthless troll ...

    don't bother replying


    He might be one of the smartest ones here.
    He did understand my difficult paragraph
    well enough to improve it.

    Turing machine deciders only compute the mapping from
    their [finite string] inputs to an accept or reject
    state on the basis that this [finite string] input
    specifies or fails to specify a *particular* semantic
    or syntactic property.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning" computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 21:58:09 2025
    From Newsgroup: comp.theory

    On 12/9/25 3:22 PM, Chris M. Thomasson wrote:
    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt.

    If that is for the same, it isn't a "Program" (aka an algorithm) in
    Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can handle.

    Nope, as it has an non-determinism/non-input that affects its
    behavior. Computation theory is about the mapping of input to output,
    so any non- determinism or dependency of a "non-input" isn't allowed,
    as the machine no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing something here.


    But DD doesn't HAVE input. The return value from HHH isn't "input", it
    is part of the operation of the program that is DD.


    There ARE variants of computation theory that handles such machines,
    but not about individual runs, but about the collection of all runs.
    They "branch" the path at each non-deterministic point, and look at
    the final result, using a couple of different criteria.

    My fuzzer keeps trying to hit all paths in DD and keeps per-path
    counters. So, it accounts for all runs. This is only dealing with PO's DD.


    The problem is HHH is part of DD, and needs to be defined as a
    deterministic algorithm.

    You are just repeating Olcotts error of thinking that you can define HHH
    as somehow "outside" of DD, but that just puts you outside the field.

    int DD()
    {
    10:    int Halt_Status = HHH(DD);
    20:    if (Halt_Status)
    30:       HERE: goto HERE;
    40:    return Halt_Status;
    }


    Some ask if ANY path halts, if so the machine is considered Halting.

    Some ask if ALL paths eventually halt, and that is required to be
    halting, if it might not ever halt with a non-vanishing probability,
    then it is non-halting.

    Some determine the probability of each of the final states (or non-
    halting) and that distribution is the answer.

    Single runs of non-deterministic machines just are not considered
    interesting for the theory.

    DD can halt, or not depending on what HHH returns. If we can hit all
    paths then we have full coverage of DD and the simulation can fin.

    [...]

    But which DD are you simulating/fuzzing? DD includes the HHH that it
    calls, whichj you have made no longer meet the requirements of the system.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,sci.logic,sci.math on Tue Dec 9 23:02:48 2025
    From Newsgroup: comp.theory

    On 12/9/25 10:53 AM, polcott wrote:
    On 12/9/2025 6:42 AM, Richard Damon wrote:
    On 12/8/25 11:33 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.


    He and Eric have been PhD computer science professors
    for decades. Of course that by itself means that
    they must be woefully less than your own infallibility.

    So?

    Appeal to Authority is just a FALICY.

    The fact this is you full arguement just show the error in your logic.


    He and Eric just understand these things better
    than you and you lack of understanding is not
    a rebuttal. I honestly believe that you are
    capable of understanding these very difficult
    things if you merely give up your insistence
    on remaining in rebuttal mode.

    Nope, he just shows he has the same ignorance (that you have admitted
    to) about what Computation Theory is about.


    It has take me more than 21 years to finally get
    clear and correct words that are consistent with
    standard definitions. For my first fifteen years
    I only had strongly held intuitions and had to
    overload terms of the art with different meanings
    because there were no exiting terms that conveyed
    the meanings that I needed to convey.

    Nope, you have wasted 21 years to try to create a better sounding LIE.

    The problem is you don't actually know what anything you say actually
    means in the theory you claim to be working on, because you have
    admitted you keep yourself ignorant of the actual facts.



    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE
    encoding for every program, which is a false assumption in Turing
    Complete systems.

    That has nothing to do with foundations.


    Sure it does.

    His decider check if the input uses it. That is based on the decider
    being able to detect that usage. Since there is no unique value to
    test, the test can't be done.


    For the conventional halting problem proof there
    is a unique value. That the proof can be adapted
    is off-topic. We must make one point at a time
    with no leaping to conclusions.

    Nope. Just shows your ignorance.

    It is computationally IMPOSSIBLE for H to universally detect that the
    machine H^ that it has been give is using a copy of itself.

    Your problem is that in your ignorance, you created a bad representation system that only handles less than Turing Complete systems, and even
    admit to a condition that proves this fact.


    Your logic is based on assuming you can make assumptions about things
    that are not true, and thus your logic is based on falsehoods being
    true, and thus shows it is just unsound, as are you.

    Sorry, all you are doing is showing how bad your logic abilities.

    That I understand these things at deeper philosophical
    levels is not any lack of understanding on my part. I
    am merely having the same problem as Ludwig Wittgenstein
    in that mathematicians and logicians are rigid-minded
    and utterly unwilling to reexamine philosophical foundations.


    Nope, you just prove Dunning-Kruger because you THINK you understand
    something you are just totally ignorant of.

    You have proved this many times, as your world is based on hopeful proclamations with no factual basis behind them, because you just don't understand what Truth actually is.

    Mathematic and Logic *IS* "rigid-minded" as it has actual rules. A
    concept foreign to you, which is why you can't actually understand
    anything in them.

    As has been pointed out many times, if you want create a totally new
    system, go ahead a do it, just be clear that is what you are doing, and
    thus nothing you say has any impact on the systems you left behind.

    Your problem is, you refuse to leave the system behind, because you KNOW (maybe just subconsiously) that they usefully and validly point out
    things you don't want to admit.

    Your problem is your mind can only handle trivially small logic system,
    so all you are trying to do is define "logic" to only handle those
    trivially small sets where incompleteness doesn't occur/
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,sci.logic,sci.math on Tue Dec 9 23:02:50 2025
    From Newsgroup: comp.theory

    On 12/9/25 10:39 AM, polcott wrote:
    On 12/9/2025 6:42 AM, Richard Damon wrote:
    On 12/8/25 11:51 PM, polcott wrote:
    On 12/8/2025 10:20 PM, Richard Damon wrote:
    On 12/8/25 11:00 PM, polcott wrote:
    On 12/8/2025 9:38 PM, dart200 wrote:

    *You have support for this in high places*

    The Halting Paradox
    Bill Stoddart

    6 Conclusions
    The idea of a universal halting test seems reasonable,
    but cannot be formalised as a consistent specification.
    It has no model and does not exist as a conceptual object.
    Assuming its conceptual existence leads to a paradox.

    https://arxiv.org/pdf/1906.05340


    Which doesn't prove anything, as there IS a consistant specification
    for the test.

    The problem is you (and Bill) just don't understand it.

    Part of the problem is Bill doesn't understand the nature of Turing
    Complete systems. In particular, he assume there is a UNIQUE
    encoding for every program, which is a false assumption in Turing
    Complete systems.

    With the text of each program P we associate a
    unique number ⌈P⌉, known as the program’s encoding,
    which will stand for the program when we want to
    use that program as data, e.g. when passing one
    program to another as an argument.

    You are just terribly inaccurate in paraphrasing.
    Perhaps speaking to no one at all is better than
    talking to you.


    Except there are many texts that create the equivalent program, and
    thus many numbers for that program.


    He is doing this like Gödel numbers, thus a unique
    identifier is needed. And again this is merely nit-picky
    his point is that the foundations of computer science
    are incorrect and I have shown that two different ways.

    Nope, doesn't work that way. A Godel number is just a way of converting
    a logical sentence into a number. Since there are many ways to say the
    same thing, and each variation would have a different Godel number, it
    isn't unique.

    Even the same sentence, if it introduces new definitions, can have
    multiple Godel numbers, as every new definition creates an arbitraryness
    that gives you multiple values.

    This just highlights that you don't understand what you are talking about.


    Yes, we can convert a program into data, but there are many data
    values that all represent the same program.


    No there are not you are just not being precise enough
    in your choice of words. And yet again this is an
    irrelevant nit-picky detail.

    No, you ar just assuming the impossible. It isn't "picky", it is being accurate, a concept you don't understand.

    How many computationally equivalent version of your HHH program do you
    think we can create?


    This means that Program H can't use a "unique" value of its
    representation to detect the input using it, as the pathological
    program can just use an equivalent variation not in the finite list of
    values that H tests for.

    If the finite strings are not identical then the
    inputs are not identical.


    WHICH "finite string" of H are you lookiing at?

    There is only one "input" in the problem, the representation of H^,
    which include a copy of the computational equivalent of H.

    do you not agree that these two are identical programs:


    int foo(int x) {
    return x+1;
    }

    and

    int foo(int y) {
    int x = y + 1;
    return x;
    }


    Do they not compute the exact same value for all inputs?

    Do the strings that represent the program exactly compate as equal?

    How can you detect ALL possible variations of something like this.

    Part of your problem is you don't understand that Compuations are based
    on actual algorithms being executed, and they don't have a native
    cononical representation.

    Part of this is because you chose not to learn the details of what you
    talk about, and thus your reckless-disregard for the truth has turned
    you into a lying idiot.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 23:02:53 2025
    From Newsgroup: comp.theory

    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not decider. >>>
    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to
    not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders that
    try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes
    don't answer. This class is more useful if they always eventually answer
    for one side of the decision, and only not-answer sometimes for the
    other. Halting is partially decidable by this criteria, with a decider
    that eventually answer halting for all halting machines, and non-halting
    for a large class of non-halting machines. I looked at machines of this
    type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get there later)


    The Abstract talks about changing the meaning of basics of Conputation
    theory and the defintion of Halting (I haven't read the full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is conceeding
    that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons for
    why we should accept either of these proposals vs a more conventional perspective,

    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    It seems this is just another person not understand the reasoning behind
    how computations were defined, and why "Halting" was an important
    question, but just wants to create a somewhat similar solvable problem,
    even if such an alternative problem has no use.




    if BB has some limit L (which is must if u believe halting problem),
    then there must be some specifically L-state machine which *no*
    machine could decide upon, for if that machine was decidable by
    anything, then BB could find that anything and subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    BB(n) is the maximum length tape that a Turing Machine of n states can
    create and then halt.

    BB(n) is, by definitiion a "finite" number. Talking about the "limit" of
    a finite number is a misuse of the term.

    We can sometimes establish upper and lower bounds on the value of BB(n),
    is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or else halting becomes generally solvable using the BB function. see, if you
    can compute the BB number for any N-state machines, then for any N-state machine u can just run the N-state machine until BB number of steps. any machine that halts on or before BB(N) steps halts, any that run past
    must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't have
    an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-state machine, until one comes back with an halting answer, for every N-state machine, which then it can the use to decide what the BB number is for
    any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.


    so no richard, partial decidability does not work if BB is to have a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.theory,alt.buddha.short.fat.guy on Tue Dec 9 20:31:43 2025
    From Newsgroup: comp.theory

    On 12/9/2025 6:58 PM, Richard Damon wrote:
    On 12/9/25 3:22 PM, Chris M. Thomasson wrote:
    On 12/7/2025 2:48 PM, Richard Damon wrote:
    On 12/7/25 4:32 PM, Chris M. Thomasson wrote:
    On 12/6/2025 7:07 PM, Richard Damon wrote:
    On 12/6/25 7:57 PM, Chris M. Thomasson wrote:
    On 12/6/2025 2:21 PM, Richard Damon wrote:
    [...]

    Think of a program that can sometimes halt, other times never halt. >>>>>
    If that is for the same, it isn't a "Program" (aka an algorithm) in >>>>> Computation Theory, whicb is what "Decidability" is defined in.

    I thought my fuzzer was an algorithm that Computation Theory can
    handle.

    Nope, as it has an non-determinism/non-input that affects its
    behavior. Computation theory is about the mapping of input to output,
    so any non- determinism or dependency of a "non-input" isn't allowed,
    as the machine no longer "compute" a mapping.

    I am not sure its a "non-input" when my fuzzer tries to feed DD input
    until both paths (halting and non-halting) are hit. I must be missing
    something here.


    But DD doesn't HAVE input. The return value from HHH isn't "input", it
    is part of the operation of the program that is DD.[...]

    My fuzzer is giving DD input. DD acts on HHH's output. I simply hijacked
    it as a fuzzy oracle.

    Heck in BASIC? That little shit (HHH) should be able to be run in a sense?

    DD depends on it. When we hit full path coverage, we can say, completed.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Thu Dec 11 11:35:08 2025
    From Newsgroup: comp.theory

    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not
    decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to
    not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did
    explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders
    that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually answer
    for one side of the decision, and only not-answer sometimes for the

    no, there's always going to be some machine which they cannot answer for
    both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a decider
    that eventually answer halting for all halting machines, and non-halting
    for a large class of non-halting machines. I looked at machines of this
    type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get there
    later)


    The Abstract talks about changing the meaning of basics of Conputation theory and the defintion of Halting (I haven't read the full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is conceeding
    that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons for
    why we should accept either of these proposals vs a more conventional perspective,

    because the implications are so broad my interest was to just focus on
    the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning behind
    how computations were defined, and why "Halting" was an important
    question, but just wants to create a somewhat similar solvable problem,
    even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting problem),
    then there must be some specifically L-state machine which *no*
    machine could decide upon, for if that machine was decidable by
    anything, then BB could find that anything and subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already
    computed it up to 5, there cannot be any machines <6 states that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter whether
    it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the "limit" of
    a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which cannot
    be decided on *by any partial* decider, because the BB computation would
    find it and use it


    We can sometimes establish upper and lower bounds on the value of BB(n),
    is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or
    else halting becomes generally solvable using the BB function. see, if
    you can compute the BB number for any N-state machines, then for any
    N-state machine u can just run the N-state machine until BB number of
    steps. any machine that halts on or before BB(N) steps halts, any that
    run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't have
    an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-
    state machine, until one comes back with an halting answer, for every
    N-state machine, which then it can the use to decide what the BB
    number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this



    so no richard, partial decidability does not work if BB is to have a
    limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory on Thu Dec 11 14:45:27 2025
    From Newsgroup: comp.theory

    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not
    decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to
    not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did
    explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders
    that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes for
    the

    no, there's always going to be some machine which they cannot answer for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a decider
    that eventually answer halting for all halting machines, and non-
    halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of Conputation
    theory and the defintion of Halting (I haven't read the full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus on
    the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and subvert >>>>> the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already computed it up to 5, there cannot be any machines <6 states that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states can
    create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the "limit"
    of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so therefore L must exist

    if L does exist, then there must be some L-state machine U which cannot
    be decided on *by any partial* decider, because the BB computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or
    else halting becomes generally solvable using the BB function. see,
    if you can compute the BB number for any N-state machines, then for
    any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-
    state machine, until one comes back with an halting answer, for every
    N-state machine, which then it can the use to decide what the BB
    number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this



    so no richard, partial decidability does not work if BB is to have a
    limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up
    on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning expressed in language"
    reliably computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Thu Dec 11 13:02:44 2025
    From Newsgroup: comp.theory

    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not
    decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to >>>>> not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i
    did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and
    all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines, and
    non- halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the
    full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus on
    the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already
    computed it up to 5, there cannot be any machines <6 states that are
    not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the "limit"
    of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or
    else halting becomes generally solvable using the BB function. see,
    if you can compute the BB number for any N-state machines, then for
    any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB
    can run continually run more and more deciders in parallel, on every
    N- state machine, until one comes back with an halting answer, for
    every N-state machine, which then it can the use to decide what the
    BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this



    so no richard, partial decidability does not work if BB is to have a
    limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up
    on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software, and as
    a 35 year old burnt out SWE, i'm tired of living in a world running off
    sucky software. it really is limiting our potential, and i want my soon
    to be born son to have a far better experience with this shit than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be

    this has lead to not only an unnecessary explosion in complexity of
    software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have computed semantic proofs guaranteeing they actually do what we want them to do. "testing" is poor substitute for doing so, but that's the most we can
    agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in fundamental math more generally ... like producing more refined limits
    to it's philosophical impact. tho idk if it can be gotten rid of
    completely, anymore than we can get rid of the words "this statement is
    false"

    but i am currently focused on the theory of computing and not anything
    more generally. the fundamental objects comprising the theory of
    computing (machines) are far more constrained in their definitions than
    what set theory needs to encompass, and within those constraints i think
    i can twist the consensus into some contradiction that are just entirely ignorant of atm

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,alt.buddha.short.fat.guy on Thu Dec 11 15:20:55 2025
    From Newsgroup: comp.theory

    On 12/11/2025 3:02 PM, dart200 wrote:
    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H. >>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed
    to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i
    did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and
    all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes >>>
    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines, and
    non- halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful. >>>>
    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory" >>>>> problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the
    full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus
    on the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already
    computed it up to 5, there cannot be any machines <6 states that are
    not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or >>>>> else halting becomes generally solvable using the BB function. see, >>>>> if you can compute the BB number for any N-state machines, then for >>>>> any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then
    we could solve the hatling problem, as we have an upper limit for
    the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB
    can run continually run more and more deciders in parallel, on
    every N- state machine, until one comes back with an halting
    answer, for every N-state machine, which then it can the use to
    decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-
    state machine cannot be decidable by *any* partial decider on the
    matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this



    so no richard, partial decidability does not work if BB is to have
    a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip
    up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software, and as
    a 35 year old burnt out SWE, i'm tired of living in a world running off sucky software. it really is limiting our potential, and i want my soon
    to be born son to have a far better experience with this shit than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be


    Exactly: Tarski even "proved" that we can't even directly
    compute what is true. This lets dangerous liars get away
    with their dangerous lies.

    this has lead to not only an unnecessary explosion in complexity of
    software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have computed semantic proofs guaranteeing they actually do what we want them to do.

    Yes without computing halting total proof of
    correctness is impossible.

    "testing" is poor substitute for doing so, but that's the most we can
    agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in fundamental math more generally ... like producing more refined limits
    to it's philosophical impact. tho idk if it can be gotten rid of
    completely, anymore than we can get rid of the words "this statement is false"


    I don't think that there actually are any limits
    except for expressions requiring infinite proofs.

    but i am currently focused on the theory of computing and not anything
    more generally. the fundamental objects comprising the theory of
    computing (machines) are far more constrained in their definitions than
    what set theory needs to encompass, and within those constraints i think
    i can twist the consensus into some contradiction that are just entirely ignorant of atm


    I have explored all of the key areas. None of them
    can be made as 100% perfectly concrete and unequivocal
    as computing.

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice


    I do have my refutation of the halting problem itself
    boiled down to a rough draft of two first principles.

    When the halting problem requires a halt decider
    to report on the behavior of a Turing machine this
    is always a category error because Turing machines
    only take finite string inputs.

    The corrected halting problem requires a Turing
    machine decider to report in the behavior that its
    actual finite string input actually specifies.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning expressed in language"
    reliably computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Fri Dec 12 10:02:27 2025
    From Newsgroup: comp.theory

    On 12/11/25 2:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not
    decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to
    not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i did
    explore that paradigm in one of my papers, a believe it's possible to
    create a program that seeks out an contradicts any and all deciders
    that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes

    yeah that's what i explored in the paper i posted

    But if your modifed criteria isn't itself useful, what good is it. THe
    fact that you began with a disclaimer that you weren't going to look at
    the quality of the criteria makes the rest meaningless. After all, we
    HAVE a lot of existing answers like that, either over machines of
    reduced capability of partial results.


    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes for
    the

    no, there's always going to be some machine which they cannot answer for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an input
    that doesn't meet the requriement, but might not answer for such input.

    Thus a Halting Recognizer is possible, as any machine that as part of
    its operation simulates the machine at a non-vanishing rate will
    eventually reach the halting state, and thus give the correct answer.

    If your ideas can't reach even that standard, they are less useful than existing results.


    please do read §2 of that paper

    depends on having the time to read something that began with a
    disclaimer that indicates it likely isn't valuable.

    other. Halting is partially decidable by this criteria, with a decider
    that eventually answer halting for all halting machines, and non-
    halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of Conputation
    theory and the defintion of Halting (I haven't read the full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus on
    the idea of the technique vs why

    And if you won't do the work to see if your ideas have any value, why
    should anyone else?

    As I have said, there are MANY other results in the category you are
    talking about, and if you aren't going to compare your results to them
    and show similar usefullness, why bother.

    My guess is you didn't look at much prior art, and thus your results are likely poorer version of the existing work based on smarter people
    working on the results of other smarter people.



    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷

    Yes, the first step of such a project should have been a study of what
    others have done. After all, those who won't study history are doomed to repeat it. If you didn't look into other attempts, you likely went down
    the same dead ends that have been traveled in the past.



    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and subvert >>>>> the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already computed it up to 5, there cannot be any machines <6 states that are not decidable

    Right, but that isn't the definition of "Computable" for a function.

    Just like "Undecidable Problems" can be correctly decided for a lot of possible inputs, just not for all.



    BB(n) is the maximum length tape that a Turing Machine of n states can
    create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver


    No, the "input" is the number of states in the machine.

    There are two versions of Busy Beaver, one is the number of symbols
    output, the other is the number of steps it can run.

    The first is actually the original as I remember, because that is an
    actual semantic property of a machine as normally defined. Steps are
    not, as the operation of a Turing Machine is classically looked at as a
    black box and thus HOW it generated the results are not significant,
    just that it did.


    but for the purposes of this discussion it doesn't really matter whether it's space or steps we're talking about


    Right. The steps is better for talking about the Halting Problem, and
    likely the source of that variant.


    BB(n) is, by definitiion a "finite" number. Talking about the "limit"
    of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    But your terminolgy is just bad there.


    if L doesn't exist, that would make halting generally decidable, so therefore L must exist

    if L does exist, then there must be some L-state machine U which cannot
    be decided on *by any partial* decider, because the BB computation would find it and use it

    Wrong. If by "Partial Decider" you mean a machine that is right for some inputs, but wrong for other, ALL inputs are partially decidable. As the
    pair of machines one that says Halting for all inputs and one that says Non-Halting for all inputs would be right.

    If you mean by "Partial Decider" a machine that is always right when it answers. but might not answer, your results don't follow, as the set of partial deciders is (at least potentially) infinte, and thus BB couldn't combine the whole set to get the answer.

    This is your "ghost" problem, that since we don't know which inputs a
    given partial decider will fail to answer on, we can't just work on
    infinite enumerations of them.


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or
    else halting becomes generally solvable using the BB function. see,
    if you can compute the BB number for any N-state machines, then for
    any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB can
    run continually run more and more deciders in parallel, on every N-
    state machine, until one comes back with an halting answer, for every
    N-state machine, which then it can the use to decide what the BB
    number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this


    I was talking about a know limit to the value PRODUCED by BB.

    After all, you discussion of a limit on the input is really a category
    error, as the function BB can take any number as its input.

    What you really mean is that the domain processed by calculatable_BB(n)
    has an upper limit, and yes, it can be proven that there must be a value
    above which BB can not be calculable, and I believe some values as upper limits of that limit have been found.




    so no richard, partial decidability does not work if BB is to have a
    limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up
    on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Fri Dec 12 21:18:50 2025
    From Newsgroup: comp.theory

    On 12/12/25 7:02 AM, Richard Damon wrote:
    On 12/11/25 2:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not
    decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed to >>>>> not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i
    did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and
    all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes

    yeah that's what i explored in the paper i posted

    But if your modifed criteria isn't itself useful, what good is it. THe

    idk what's with boomers and the notion that someone needs to have
    literally everything worked out about a thing before posting an idea???

    if it doesn't interest you yet, then it's prolly not for you yet

    fact that you began with a disclaimer that you weren't going to look at
    the quality of the criteria makes the rest meaningless. After all, we
    HAVE a lot of existing answers like that, either over machines of
    reduced capability of partial results.


    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an input
    that doesn't meet the requriement, but might not answer for such input.

    Thus a Halting Recognizer is possible, as any machine that as part of
    its operation simulates the machine at a non-vanishing rate will
    eventually reach the halting state, and thus give the correct answer.

    If your ideas can't reach even that standard, they are less useful than existing results.


    please do read §2 of that paper

    depends on having the time to read something that began with a
    disclaimer that indicates it likely isn't valuable.

    i mean u have a bunch time to keep dicking me around on this, richard...


    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines, and
    non- halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful.

    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory"
    problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the
    full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus on
    the idea of the technique vs why

    And if you won't do the work to see if your ideas have any value, why
    should anyone else?

    i made another paper on a reason to use it, and it worked out
    miraculously well. turing would have been impressed, because it did the unfathomable in making a direct diagonal (across computable numbers)
    actually computable, while leaving the inverse still uncomputable...

    and idk how to unlearn that

    https://www.academia.edu/143540657


    As I have said, there are MANY other results in the category you are
    talking about, and if you aren't going to compare your results to them
    and show similar usefullness, why bother.

    My guess is you didn't look at much prior art, and thus your results are likely poorer version of the existing work based on smarter people
    working on the results of other smarter people.

    u find me anything like the paper i just linked to, and i'll delete thunderbird to leave this god-forsaking group forever

    and please don't comment on it until you read it enough to at least
    explain to me how i used a quine in the paper. and no, the quine itself doesn't solve turing's problem, but it does do something interesting
    that turing never recognized because he never knew about quines




    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷

    Yes, the first step of such a project should have been a study of what others have done. After all, those who won't study history are doomed to repeat it. If you didn't look into other attempts, you likely went down
    the same dead ends that have been traveled in the past.

    if only life proceeded like such TV reality




    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already
    computed it up to 5, there cannot be any machines <6 states that are
    not decidable

    Right, but that isn't the definition of "Computable" for a function.

    BB_up_to_5_returns_0_after(n) is a wholly computable function

    "computable up to a limit" is a meaningful phrase that can be
    represented by more constrained functions that are indeed fully
    computable, returning some recognizable non-answer after the "limit" to computability it reached.


    Just like "Undecidable Problems" can be correctly decided for a lot of possible inputs, just not for all.



    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver


    No, the "input" is the number of states in the machine.

    There are two versions of Busy Beaver, one is the number of symbols
    output, the other is the number of steps it can run.

    The first is actually the original as I remember, because that is an
    actual semantic property of a machine as normally defined. Steps are
    not, as the operation of a Turing Machine is classically looked at as a black box and thus HOW it generated the results are not significant,
    just that it did.

    could have just read the article instead of speculated bro:

    /Radó defined two functions related to the busy beaver game: the score function Σ(n) and the shifts function S(n) Both take a number of Turing machine states n and output the maximum score attainable by a Turing
    machine of that number of states by some measure. The score function
    Σ(n) gives the maximum number of 1s an n-state Turing machine can output before halting, while the shifts function S(n) gives the maximum number
    of shifts (or equivalently steps, because each step includes a shift)
    that an n-state Turing machine can undergo before halting/



    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    Right. The steps is better for talking about the Halting Problem, and
    likely the source of that variant.


    BB(n) is, by definitiion a "finite" number. Talking about the "limit"
    of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    But your terminolgy is just bad there.


    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it

    Wrong. If by "Partial Decider" you mean a machine that is right for some inputs, but wrong for other, ALL inputs are partially decidable. As the
    pair of machines one that says Halting for all inputs and one that says Non-Halting for all inputs would be right.

    If you mean by "Partial Decider" a machine that is always right when it

    yes

    answers. but might not answer, your results don't follow, as the set of partial deciders is (at least potentially) infinte, and thus BB couldn't combine the whole set to get the answer.

    it is infinite. heck for any single machine there are infinite machines
    that compute that same function.

    BB just does an unbounded search running incrementally running more of
    them simultaneously. for every iteration it starts 1 partial decider to
    it's list of in-progress deciders, runs them all one step, and tests
    each one for an answer

    if there is an answer out there, then it will be found...

    which ikd what ur gunna do about that rick, or was ur nick-name dick,
    eh? i mean u know this kinda drill already, it's similar to enumerating
    out halting machines.


    This is your "ghost" problem, that since we don't know which inputs a
    given partial decider will fail to answer on, we can't just work on
    infinite enumerations of them.


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or
    else halting becomes generally solvable using the BB function. see,
    if you can compute the BB number for any N-state machines, then for
    any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then we
    could solve the hatling problem, as we have an upper limit for the
    number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB
    can run continually run more and more deciders in parallel, on every
    N- state machine, until one comes back with an halting answer, for
    every N-state machine, which then it can the use to decide what the
    BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-state
    machine cannot be decidable by *any* partial decider on the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this


    I was talking about a know limit to the value PRODUCED by BB.

    After all, you discussion of a limit on the input is really a category error, as the function BB can take any number as its input.

    What you really mean is that the domain processed by calculatable_BB(n)
    has an upper limit, and yes, it can be proven that there must be a value above which BB can not be calculable, and I believe some values as upper limits of that limit have been found.


    the proof for the upper limit rn depends on how well someone could
    bit-pack a halting paradox into their proof i think, lol




    so no richard, partial decidability does not work if BB is to have a
    limit


    You only have the problem is BB has a KNOWN limit. Again, you trip up
    on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Fri Dec 12 21:22:53 2025
    From Newsgroup: comp.theory

    On 12/11/25 1:20 PM, polcott wrote:
    On 12/11/2025 3:02 PM, dart200 wrote:
    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H. >>>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed >>>>>>> to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i >>>>>> did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and >>>>>> all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes >>>>
    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines,
    and non- halting for a large class of non-halting machines. I
    looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is
    useful.

    It is easy to create a system where Halting can be decided, it just >>>>> needs making the system less than Turing Complete, so if you idea
    is based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox >>>>>>
    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable numbers/, >>>>>> but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the >>>>> full paper).

    All that is doing is admitting that by the definitions accepted for >>>>> defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a
    more conventional perspective,

    because the implications are so broad my interest was to just focus
    on the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine >>>>>>>> which *no* machine could decide upon, for if that machine was >>>>>>>> decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit? >>>>>
    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6 states
    that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L,
    or else halting becomes generally solvable using the BB function. >>>>>> see, if you can compute the BB number for any N-state machines,
    then for any N-state machine u can just run the N-state machine
    until BB number of steps. any machine that halts on or before
    BB(N) steps halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then
    we could solve the hatling problem, as we have an upper limit for
    the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't >>>>> have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB >>>>>> can run continually run more and more deciders in parallel, on
    every N- state machine, until one comes back with an halting
    answer, for every N-state machine, which then it can the use to
    decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try
    to mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-
    state machine cannot be decidable by *any* partial decider on the >>>>>> matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and
    proofs have been put out in regards to this



    so no richard, partial decidability does not work if BB is to have >>>>>> a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip
    up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software, and
    as a 35 year old burnt out SWE, i'm tired of living in a world running
    off sucky software. it really is limiting our potential, and i want my
    soon to be born son to have a far better experience with this shit
    than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be


    Exactly: Tarski even "proved" that we can't even directly
    compute what is true. This lets dangerous liars get away
    with their dangerous lies.

    this has lead to not only an unnecessary explosion in complexity of
    software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have computed
    semantic proofs guaranteeing they actually do what we want them to do.

    Yes without computing halting total proof of
    correctness is impossible.

    "testing" is poor substitute for doing so, but that's the most we can
    agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in
    fundamental math more generally ... like producing more refined limits
    to it's philosophical impact. tho idk if it can be gotten rid of
    completely, anymore than we can get rid of the words "this statement
    is false"


    I don't think that there actually are any limits
    except for expressions requiring infinite proofs.

    but i am currently focused on the theory of computing and not anything
    more generally. the fundamental objects comprising the theory of
    computing (machines) are far more constrained in their definitions
    than what set theory needs to encompass, and within those constraints
    i think i can twist the consensus into some contradiction that are
    just entirely ignorant of atm


    I have explored all of the key areas. None of them
    can be made as 100% perfectly concrete and unequivocal
    as computing.

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice


    I do have my refutation of the halting problem itself
    boiled down to a rough draft of two first principles.

    When the halting problem requires a halt decider
    to report on the behavior of a Turing machine this
    is always a category error because Turing machines
    only take finite string inputs.

    The corrected halting problem requires a Turing
    machine decider to report in the behavior that its
    actual finite string input actually specifies.



    polcott, i'm working on making the halting problem complete and
    consistent in regards to a subset of the improved "reflective turing
    machines" that encompasses all useful computations

    i'm sorry, but not about trying to reaffirm the halting function as
    still uncomputable by calling it a category error
    --
    a burnt out swe investigating into why our tooling doesn't involve
    basic semantic proofs like halting analysis

    please excuse my pseudo-pyscript,

    ~ nick
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From polcott@polcott333@gmail.com to comp.theory,sci.logic on Sat Dec 13 07:15:48 2025
    From Newsgroup: comp.theory

    On 12/12/2025 11:22 PM, dart200 wrote:
    On 12/11/25 1:20 PM, polcott wrote:
    On 12/11/2025 3:02 PM, dart200 wrote:
    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the >>>>>>>>>> machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong. >>>>>>>>
    YOU need to provide some machine that my arguement will label as H. >>>>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed >>>>>>>> to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i >>>>>>> did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any
    and all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but
    sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually >>>>>> answer for one side of the decision, and only not-answer sometimes >>>>>> for the

    no, there's always going to be some machine which they cannot
    answer for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines,
    and non- halting for a large class of non-halting machines. I
    looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is
    useful.

    It is easy to create a system where Halting can be decided, it
    just needs making the system less than Turing Complete, so if you >>>>>> idea is based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox >>>>>>>
    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable numbers/, >>>>>>> but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read
    the full paper).

    All that is doing is admitting that by the definitions accepted
    for defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a
    more conventional perspective,

    because the implications are so broad my interest was to just focus >>>>> on the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to >>>>>> discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning >>>>>> behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine >>>>>>>>> which *no* machine could decide upon, for if that machine was >>>>>>>>> decidable by anything, then BB could find that anything and >>>>>>>>> subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit? >>>>>>
    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6 states >>>>> that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n states >>>>>> can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, so >>>>> therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of >>>>>> BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, >>>>>>> or else halting becomes generally solvable using the BB function. >>>>>>> see, if you can compute the BB number for any N-state machines, >>>>>>> then for any N-state machine u can just run the N-state machine >>>>>>> until BB number of steps. any machine that halts on or before
    BB(N) steps halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then >>>>>> we could solve the hatling problem, as we have an upper limit for >>>>>> the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we
    don't have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB >>>>>>> can run continually run more and more deciders in parallel, on
    every N- state machine, until one comes back with an halting
    answer, for every N-state machine, which then it can the use to >>>>>>> decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try >>>>>> to mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L- >>>>>>> state machine cannot be decidable by *any* partial decider on the >>>>>>> matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and
    proofs have been put out in regards to this



    so no richard, partial decidability does not work if BB is to
    have a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip >>>>>> up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software, and
    as a 35 year old burnt out SWE, i'm tired of living in a world
    running off sucky software. it really is limiting our potential, and
    i want my soon to be born son to have a far better experience with
    this shit than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be


    Exactly: Tarski even "proved" that we can't even directly
    compute what is true. This lets dangerous liars get away
    with their dangerous lies.

    this has lead to not only an unnecessary explosion in complexity of
    software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have
    computed semantic proofs guaranteeing they actually do what we want
    them to do.

    Yes without computing halting total proof of
    correctness is impossible.

    "testing" is poor substitute for doing so, but that's the most we can
    agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in
    fundamental math more generally ... like producing more refined
    limits to it's philosophical impact. tho idk if it can be gotten rid
    of completely, anymore than we can get rid of the words "this
    statement is false"


    I don't think that there actually are any limits
    except for expressions requiring infinite proofs.

    but i am currently focused on the theory of computing and not
    anything more generally. the fundamental objects comprising the
    theory of computing (machines) are far more constrained in their
    definitions than what set theory needs to encompass, and within those
    constraints i think i can twist the consensus into some contradiction
    that are just entirely ignorant of atm


    I have explored all of the key areas. None of them
    can be made as 100% perfectly concrete and unequivocal
    as computing.

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice


    I do have my refutation of the halting problem itself
    boiled down to a rough draft of two first principles.

    When the halting problem requires a halt decider
    to report on the behavior of a Turing machine this
    is always a category error because Turing machines
    only take finite string inputs.

    The corrected halting problem requires a Turing
    machine decider to report in the behavior that its
    actual finite string input actually specifies.



    polcott, i'm working on making the halting problem complete and
    consistent in regards to a subset of the improved "reflective turing machines" that encompasses all useful computations

    i'm sorry, but not about trying to reaffirm the halting function as
    still uncomputable by calling it a category error


    I do compute the halting function correctly.
    I have been doing this for more than three years.
    We probably should not be spamming alt.buddha.short.fat.guy

    int sum(int x, int y){return x + y;}
    sum(3,2) should return 5 and it is incorrect
    to require sum(3,2) to return the sum of 5+6.
    --
    Copyright 2025 Olcott

    My 28 year goal has been to make
    "true on the basis of meaning expressed in language"
    reliably computable.

    This required establishing a new foundation
    for correct reasoning.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 13 09:26:17 2025
    From Newsgroup: comp.theory

    On 12/13/25 12:18 AM, dart200 wrote:
    On 12/12/25 7:02 AM, Richard Damon wrote:
    On 12/11/25 2:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer???

    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement?

    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H. >>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed
    to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i
    did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and
    all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes >>>
    yeah that's what i explored in the paper i posted

    But if your modifed criteria isn't itself useful, what good is it. THe

    idk what's with boomers and the notion that someone needs to have
    literally everything worked out about a thing before posting an idea???

    Not that you need to have it all worked out, but that you evaluate as
    you go if there are signs of it being useful.


    if it doesn't interest you yet, then it's prolly not for you yet

    Yet, you ask for help.

    The problem is if you don't think of usefulness at the start, you will certainly end up with a system without usefulness.

    It seems you are making the same error of Olcott, of diving into a field
    that you are ignorant of. There are REASONS for the rules you want to
    flaunt, and by doing so you condemn your work to the trash heap of
    worthless ideas.


    fact that you began with a disclaimer that you weren't going to look
    at the quality of the criteria makes the rest meaningless. After all,
    we HAVE a lot of existing answers like that, either over machines of
    reduced capability of partial results.


    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an input
    that doesn't meet the requriement, but might not answer for such input.

    Thus a Halting Recognizer is possible, as any machine that as part of
    its operation simulates the machine at a non-vanishing rate will
    eventually reach the halting state, and thus give the correct answer.

    If your ideas can't reach even that standard, they are less useful
    than existing results.


    please do read §2 of that paper

    depends on having the time to read something that began with a
    disclaimer that indicates it likely isn't valuable.

    i mean u have a bunch time to keep dicking me around on this, richard...

    No, I look at things when I have a few spare moments waiting for other
    things to happen. To properly read a 20 page paper takes more of an
    effort, and when it begins with a disclaimer that tells me the author
    isn't going to even try to make things useful, there isn't much of an incentive.


    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines, and
    non- halting for a large class of non-halting machines. I looked at
    machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is useful. >>>>
    It is easy to create a system where Halting can be decided, it just
    needs making the system less than Turing Complete, so if you idea is
    based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's "satisfactory" >>>>> problem from the og paper /on computable numbers/, but we'll get
    there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the
    full paper).

    All that is doing is admitting that by the definitions accepted for
    defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or reasons
    for why we should accept either of these proposals vs a more
    conventional perspective,

    because the implications are so broad my interest was to just focus
    on the idea of the technique vs why

    And if you won't do the work to see if your ideas have any value, why
    should anyone else?

    i made another paper on a reason to use it, and it worked out
    miraculously well. turing would have been impressed, because it did the unfathomable in making a direct diagonal (across computable numbers) actually computable, while leaving the inverse still uncomputable...

    What is a "Computable Number"?

    How can we know if a number is "Computable"?


    and idk how to unlearn that

    https://www.academia.edu/143540657

    Which begins with an error, Turing Machines do not uniquely map to
    finite strings, and thus do not uniquely map to numbers.

    The problem is the "name" of the states in the Turing Machine are
    arbitrary, but end up in some manner in the string. Since we can easily
    just assign the same machine different names for the states, we can
    create many different encodings for a given machine.

    You even quote his statement:
    To each computable sequence there corresponds at least one description
    number, while to no description number does there correspond more than
    one computable sequence. The computable sequences and numbers are
    therefore enumerable

    It seems you may need to study some of the properties of infinite sets
    better.

    Now, each string represents just a single machine, so we can still
    iterate through all machines, we just see each machine many times in
    that infinite iteration.



    As I have said, there are MANY other results in the category you are
    talking about, and if you aren't going to compare your results to them
    and show similar usefullness, why bother.

    My guess is you didn't look at much prior art, and thus your results
    are likely poorer version of the existing work based on smarter people
    working on the results of other smarter people.

    u find me anything like the paper i just linked to, and i'll delete thunderbird to leave this god-forsaking group forever

    Have you looked at ANYTHING academic on infinite sets?


    and please don't comment on it until you read it enough to at least
    explain to me how i used a quine in the paper. and no, the quine itself doesn't solve turing's problem, but it does do something interesting
    that turing never recognized because he never knew about quines


    Since you start with:
    The diagonal computation must compute the unique natural number nh that describes it,

    But, as shown above, there is no such number, as compuations are
    represented by an infinite set of numbers, your logic is just based on a
    false premise.




    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷

    Yes, the first step of such a project should have been a study of what
    others have done. After all, those who won't study history are doomed
    to repeat it. If you didn't look into other attempts, you likely went
    down the same dead ends that have been traveled in the past.

    if only life proceeded like such TV reality


    So instead you walked out into the void with no idea of where you are
    going, and hoping you will just stumble upon something useful.




    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine
    which *no* machine could decide upon, for if that machine was
    decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've already
    computed it up to 5, there cannot be any machines <6 states that are
    not decidable

    Right, but that isn't the definition of "Computable" for a function.

    BB_up_to_5_returns_0_after(n) is a wholly computable function

    Sure, but that isn't BB


    "computable up to a limit" is a meaningful phrase that can be
    represented by more constrained functions that are indeed fully
    computable, returning some recognizable non-answer after the "limit" to computability it reached.

    It may be "meaningful", but may not be useful.

    If you can prove that limit point is big enough, there might be some
    uses for it on small practical problems.

    For uses in logic theory, which was the initial goal of the field, ALL
    means ALL and not just for small numbers.



    Just like "Undecidable Problems" can be correctly decided for a lot of
    possible inputs, just not for all.



    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver


    No, the "input" is the number of states in the machine.

    There are two versions of Busy Beaver, one is the number of symbols
    output, the other is the number of steps it can run.

    The first is actually the original as I remember, because that is an
    actual semantic property of a machine as normally defined. Steps are
    not, as the operation of a Turing Machine is classically looked at as
    a black box and thus HOW it generated the results are not significant,
    just that it did.

    could have just read the article instead of speculated bro:

    /Radó defined two functions related to the busy beaver game: the score function Σ(n) and the shifts function S(n) Both take a number of Turing machine states n and output the maximum score attainable by a Turing
    machine of that number of states by some measure. The score function
    Σ(n) gives the maximum number of 1s an n-state Turing machine can output before halting, while the shifts function S(n) gives the maximum number
    of shifts (or equivalently steps, because each step includes a shift)
    that an n-state Turing machine can undergo before halting/

    And neither is computable for all values.

    Note, I was pointing out that you were inaccurate in your correction to
    my statement.

    BB, as originally stated, was about length of tape generated.




    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    Right. The steps is better for talking about the Halting Problem, and
    likely the source of that variant.


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    But your terminolgy is just bad there.


    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it

    Wrong. If by "Partial Decider" you mean a machine that is right for
    some inputs, but wrong for other, ALL inputs are partially decidable.
    As the pair of machines one that says Halting for all inputs and one
    that says Non-Halting for all inputs would be right.

    If you mean by "Partial Decider" a machine that is always right when it

    yes

    Ok, that is the more useful definition.


    answers. but might not answer, your results don't follow, as the set
    of partial deciders is (at least potentially) infinte, and thus BB
    couldn't combine the whole set to get the answer.

    it is infinite. heck for any single machine there are infinite machines
    that compute that same function.

    BB just does an unbounded search running incrementally running more of
    them simultaneously. for every iteration it starts 1 partial decider to
    it's list of in-progress deciders, runs them all one step, and tests
    each one for an answer

    But that means you need an enumerated list of all machines that ARE
    partial deciders, and which excludes machines that are just incorrect.

    That tends to mean you need a finite test that a given machine is such a machine, and that is an uncomputable problem.


    if there is an answer out there, then it will be found...
    which ikd what ur gunna do about that rick, or was ur nick-name dick,
    eh? i mean u know this kinda drill already, it's similar to enumerating
    out halting machines.

    Right, It is a task that can't be done. The problem is that there will
    be some machines that no always correct partial decider will decide, we
    just won't be able to identify those machines, they will just always be
    a member of the cloud of currently unknown machines, and while we can
    reduce that set with more and more work, it turns out it can never be empty.

    If your logic can't handle that some things are inherently unknowable,
    it can't handle this problem. This is part of Olcott's trap, He can't distringuish between Known and True, but thinks we can know all truths.

    You try to dismiss this as just "Ghosts", but the problem is that these
    ghosts do exists, they are just unknowable.



    This is your "ghost" problem, that since we don't know which inputs a
    given partial decider will fail to answer on, we can't just work on
    infinite enumerations of them.


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, or >>>>> else halting becomes generally solvable using the BB function. see, >>>>> if you can compute the BB number for any N-state machines, then for >>>>> any N-state machine u can just run the N-state machine until BB
    number of steps. any machine that halts on or before BB(N) steps
    halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then
    we could solve the hatling problem, as we have an upper limit for
    the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't
    have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB
    can run continually run more and more deciders in parallel, on
    every N- state machine, until one comes back with an halting
    answer, for every N-state machine, which then it can the use to
    decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try to
    mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-
    state machine cannot be decidable by *any* partial decider on the
    matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and proofs
    have been put out in regards to this


    I was talking about a know limit to the value PRODUCED by BB.

    After all, you discussion of a limit on the input is really a category
    error, as the function BB can take any number as its input.

    What you really mean is that the domain processed by
    calculatable_BB(n) has an upper limit, and yes, it can be proven that
    there must be a value above which BB can not be calculable, and I
    believe some values as upper limits of that limit have been found.


    the proof for the upper limit rn depends on how well someone could bit-
    pack a halting paradox into their proof i think, lol

    Not quite but close.





    so no richard, partial decidability does not work if BB is to have
    a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip
    up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.




    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Tristan Wibberley@tristan.wibberley+netnews2@alumni.manchester.ac.uk to comp.theory,alt.buddha.short.fat.guy on Sat Dec 13 14:43:26 2025
    From Newsgroup: comp.theory

    On 12/12/2025 15:02, Richard Damon wrote:

    Nothing in the context above seemed to provide the definition pondered
    below.
    ...

    no, there's always going to be some machine which they cannot answer
    for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an input
    that doesn't meet the requriement, but might not answer for such input.

    Is that by one of Olcott's definitions or a conventional one?

    In the field of AI, "Recogniser" is already taken and includes those
    that give "false", "incorrect", "untruthful", "unconventional" and "not-as-labelled" results, however you want to call it.

    "Deductive Recogniser" might be a good term, it avoids the notion of
    absolute truth and falsity but it can easily be seen to be relative to
    your formal system's correctness, which I think is what we really
    require (it's perfect as far your formal system defines perfect).

    A physical embodiment such as a real computer that ostensibly implements
    a deductive recogniser wouldn't be one, not really.


    ...
    I didn't read the rest.
    --
    Tristan Wibberley

    The message body is Copyright (C) 2025 Tristan Wibberley except
    citations and quotations noted. All Rights Reserved except that you may,
    of course, cite it academically giving credit to me, distribute it
    verbatim as part of a usenet system or its archives, and use it to
    promote my greatness and general superiority without misrepresentation
    of my opinions other than my opinion of my greatness and general
    superiority which you _may_ misrepresent. You definitely MAY NOT train
    any production AI system with it but you may train experimental AI that
    will only be used for evaluation of the AI methods it implements.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,sci.logic,alt.buddha.short.fat.guy on Sat Dec 13 08:01:08 2025
    From Newsgroup: comp.theory

    On 12/13/25 5:15 AM, polcott wrote:
    On 12/12/2025 11:22 PM, dart200 wrote:
    On 12/11/25 1:20 PM, polcott wrote:
    On 12/11/2025 3:02 PM, dart200 wrote:
    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the >>>>>>>>>>> machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong. >>>>>>>>>
    YOU need to provide some machine that my arguement will label >>>>>>>>> as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can >>>>>>>>>>> not decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is
    allowed to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? >>>>>>>> i did explore that paradigm in one of my papers, a believe it's >>>>>>>> possible to create a program that seeks out an contradicts any >>>>>>>> and all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called >>>>>>> recognizer, are machines that never give a wrong answer, but
    sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always eventually >>>>>>> answer for one side of the decision, and only not-answer
    sometimes for the

    no, there's always going to be some machine which they cannot
    answer for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines, >>>>>>> and non- halting for a large class of non-halting machines. I
    looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is >>>>>>> useful.

    It is easy to create a system where Halting can be decided, it
    just needs making the system less than Turing Complete, so if you >>>>>>> idea is based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox >>>>>>>>
    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable
    numbers/, but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read >>>>>>> the full paper).

    All that is doing is admitting that by the definitions accepted >>>>>>> for defining a computation and what halting means, the author is >>>>>>> conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a >>>>>>> more conventional perspective,

    because the implications are so broad my interest was to just
    focus on the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going to >>>>>>> discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷


    It seems this is just another person not understand the reasoning >>>>>>> behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar >>>>>>> solvable problem, even if such an alternative problem has no use. >>>>>>>


    if BB has some limit L (which is must if u believe halting >>>>>>>>>> problem), then there must be some specifically L-state machine >>>>>>>>>> which *no* machine could decide upon, for if that machine was >>>>>>>>>> decidable by anything, then BB could find that anything and >>>>>>>>>> subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit? >>>>>>>
    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6
    states that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n
    states can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver

    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes >>>>>> fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable,
    so therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value of >>>>>>> BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L, >>>>>>>> or else halting becomes generally solvable using the BB
    function. see, if you can compute the BB number for any N-state >>>>>>>> machines, then for any N-state machine u can just run the N-
    state machine until BB number of steps. any machine that halts >>>>>>>> on or before BB(N) steps halts, any that run past must be
    nonhalting

    No, if we could establish an upper limit for BB(n) for all n,
    then we could solve the hatling problem, as we have an upper
    limit for the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we
    don't have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that >>>>>>>> BB can run continually run more and more deciders in parallel, >>>>>>>> on every N- state machine, until one comes back with an halting >>>>>>>> answer, for every N-state machine, which then it can the use to >>>>>>>> decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try >>>>>>> to mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L- >>>>>>>> state machine cannot be decidable by *any* partial decider on >>>>>>>> the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and
    proofs have been put out in regards to this



    so no richard, partial decidability does not work if BB is to >>>>>>>> have a limit


    You only have the problem is BB has a KNOWN limit. Again, you
    trip up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software, and
    as a 35 year old burnt out SWE, i'm tired of living in a world
    running off sucky software. it really is limiting our potential, and
    i want my soon to be born son to have a far better experience with
    this shit than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be


    Exactly: Tarski even "proved" that we can't even directly
    compute what is true. This lets dangerous liars get away
    with their dangerous lies.

    this has lead to not only an unnecessary explosion in complexity of
    software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have
    computed semantic proofs guaranteeing they actually do what we want
    them to do.

    Yes without computing halting total proof of
    correctness is impossible.

    "testing" is poor substitute for doing so, but that's the most we
    can agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in
    fundamental math more generally ... like producing more refined
    limits to it's philosophical impact. tho idk if it can be gotten rid
    of completely, anymore than we can get rid of the words "this
    statement is false"


    I don't think that there actually are any limits
    except for expressions requiring infinite proofs.

    but i am currently focused on the theory of computing and not
    anything more generally. the fundamental objects comprising the
    theory of computing (machines) are far more constrained in their
    definitions than what set theory needs to encompass, and within
    those constraints i think i can twist the consensus into some
    contradiction that are just entirely ignorant of atm


    I have explored all of the key areas. None of them
    can be made as 100% perfectly concrete and unequivocal
    as computing.

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice


    I do have my refutation of the halting problem itself
    boiled down to a rough draft of two first principles.

    When the halting problem requires a halt decider
    to report on the behavior of a Turing machine this
    is always a category error because Turing machines
    only take finite string inputs.

    The corrected halting problem requires a Turing
    machine decider to report in the behavior that its
    actual finite string input actually specifies.



    polcott, i'm working on making the halting problem complete and
    consistent in regards to a subset of the improved "reflective turing
    machines" that encompasses all useful computations

    i'm sorry, but not about trying to reaffirm the halting function as
    still uncomputable by calling it a category error


    I do compute the halting function correctly.

    the halting *function* is an abstract mathematical object that maps a
    machine description to whether the machine described halts or not, not
    the associated machine description that attempts to compute this

    I have been doing this for more than three years.
    We probably should not be spamming alt.buddha.short.fat.guy

    i hang out there tho, i have my own reasons for posting this there


    int sum(int x, int y){return x + y;}
    sum(3,2) should return 5 and it is incorrect
    to require sum(3,2) to return the sum of 5+6.


    u can argue about what computing machines actually exist all u want, and whether anything actually computes the halting *function*, i'm not going
    to argue over what the halting *function* itself is
    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From olcott@polcott333@gmail.com to comp.theory,sci.logic,comp.ai.philosophy on Sat Dec 13 10:22:04 2025
    From Newsgroup: comp.theory

    On 12/13/2025 10:01 AM, dart200 wrote:
    On 12/13/25 5:15 AM, polcott wrote:
    On 12/12/2025 11:22 PM, dart200 wrote:
    On 12/11/25 1:20 PM, polcott wrote:
    On 12/11/2025 3:02 PM, dart200 wrote:
    On 12/11/25 12:45 PM, polcott wrote:
    On 12/11/2025 1:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the >>>>>>>>>>>> machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong. >>>>>>>>>>
    YOU need to provide some machine that my arguement will label >>>>>>>>>> as H.



    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can >>>>>>>>>>>> not decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is
    allowed to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? >>>>>>>>> i did explore that paradigm in one of my papers, a believe it's >>>>>>>>> possible to create a program that seeks out an contradicts any >>>>>>>>> and all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called >>>>>>>> recognizer, are machines that never give a wrong answer, but
    sometimes

    yeah that's what i explored in the paper i posted

    don't answer. This class is more useful if they always
    eventually answer for one side of the decision, and only not- >>>>>>>> answer sometimes for the

    no, there's always going to be some machine which they cannot
    answer for both sides

    please do read §2 of that paper

    other. Halting is partially decidable by this criteria, with a >>>>>>>> decider that eventually answer halting for all halting machines, >>>>>>>> and non- halting for a large class of non-halting machines. I >>>>>>>> looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is >>>>>>>> useful.

    It is easy to create a system where Halting can be decided, it >>>>>>>> just needs making the system less than Turing Complete, so if >>>>>>>> you idea is based on that, so what.


    https://www.academia.edu/136521323/
    how_to_resolve_a_halting_paradox

    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable
    numbers/, but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read >>>>>>>> the full paper).

    All that is doing is admitting that by the definitions accepted >>>>>>>> for defining a computation and what halting means, the author is >>>>>>>> conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a >>>>>>>> more conventional perspective,

    because the implications are so broad my interest was to just
    focus on the idea of the technique vs why


    But, what good is an alternate formulation if you aren't going >>>>>>>> to discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd >>>>>>> actually have to read it 🤷


    It seems this is just another person not understand the
    reasoning behind how computations were defined, and why
    "Halting" was an important question, but just wants to create a >>>>>>>> somewhat similar solvable problem, even if such an alternative >>>>>>>> problem has no use.



    if BB has some limit L (which is must if u believe halting >>>>>>>>>>> problem), then there must be some specifically L-state
    machine which *no* machine could decide upon, for if that >>>>>>>>>>> machine was decidable by anything, then BB could find that >>>>>>>>>>> anything and subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a >>>>>>>>> limit?

    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6
    states that are not decidable


    BB(n) is the maximum length tape that a Turing Machine of n
    states can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver >>>>>>>
    but for the purposes of this discussion it doesn't really matter >>>>>>> whether it's space or steps we're talking about


    BB(n) is, by definitiion a "finite" number. Talking about the >>>>>>>> "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes >>>>>>> fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    if L doesn't exist, that would make halting generally decidable, >>>>>>> so therefore L must exist

    if L does exist, then there must be some L-state machine U which >>>>>>> cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it


    We can sometimes establish upper and lower bounds on the value >>>>>>>> of BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit >>>>>>>>> L, or else halting becomes generally solvable using the BB
    function. see, if you can compute the BB number for any N-state >>>>>>>>> machines, then for any N-state machine u can just run the N- >>>>>>>>> state machine until BB number of steps. any machine that halts >>>>>>>>> on or before BB(N) steps halts, any that run past must be
    nonhalting

    No, if we could establish an upper limit for BB(n) for all n, >>>>>>>> then we could solve the hatling problem, as we have an upper
    limit for the number of steps we need to simulate the machine. >>>>>>>>
    BB(n) has a value, but for sufficiently large values of n, we >>>>>>>> don't have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that >>>>>>>>> BB can run continually run more and more deciders in parallel, >>>>>>>>> on every N- state machine, until one comes back with an halting >>>>>>>>> answer, for every N-state machine, which then it can the use to >>>>>>>>> decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to >>>>>>>> try to mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L- >>>>>>>>> state machine cannot be decidable by *any* partial decider on >>>>>>>>> the matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and
    proofs have been put out in regards to this



    so no richard, partial decidability does not work if BB is to >>>>>>>>> have a limit


    You only have the problem is BB has a KNOWN limit. Again, you >>>>>>>> trip up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.


    I just glanced at your paper and skipped to the conclusion.
    Why do we care about the undecidability of the halting problem?
    Because undecidability in general (if it is correct) shows
    that truth itself is broken. Truth itself cannot be broken.
    This is the only reason why I have worked on these things
    for 28 years.

    because it makes us suck as developing and maintaining software,
    and as a 35 year old burnt out SWE, i'm tired of living in a world
    running off sucky software. it really is limiting our potential,
    and i want my soon to be born son to have a far better experience
    with this shit than i did.

    a consequence of accepting the halting problem is then necessarily
    accepting proof against *all* semantic deciders, barring us from
    agreeing on what such general deciders might be


    Exactly: Tarski even "proved" that we can't even directly
    compute what is true. This lets dangerous liars get away
    with their dangerous lies.

    this has lead to not only an unnecessary explosion in complexity of >>>>> software engineering, because we can't generally compute semantic
    (turing) equivalence,

    but the general trend in deploying software that doesn't have
    computed semantic proofs guaranteeing they actually do what we want >>>>> them to do.

    Yes without computing halting total proof of
    correctness is impossible.

    "testing" is poor substitute for doing so, but that's the most we
    can agree upon due to the current theory of computing.

    i think my ideas might contribute to dealing with incompleteness in >>>>> fundamental math more generally ... like producing more refined
    limits to it's philosophical impact. tho idk if it can be gotten
    rid of completely, anymore than we can get rid of the words "this
    statement is false"


    I don't think that there actually are any limits
    except for expressions requiring infinite proofs.

    but i am currently focused on the theory of computing and not
    anything more generally. the fundamental objects comprising the
    theory of computing (machines) are far more constrained in their
    definitions than what set theory needs to encompass, and within
    those constraints i think i can twist the consensus into some
    contradiction that are just entirely ignorant of atm


    I have explored all of the key areas. None of them
    can be made as 100% perfectly concrete and unequivocal
    as computing.

    that's the slam dunk left that i need. i have a means to rectify
    whatever contradiction we find thru the use of RTMs, but i'm still
    teasing out the contradiction that will *force* others to notice


    I do have my refutation of the halting problem itself
    boiled down to a rough draft of two first principles.

    When the halting problem requires a halt decider
    to report on the behavior of a Turing machine this
    is always a category error because Turing machines
    only take finite string inputs.

    The corrected halting problem requires a Turing
    machine decider to report in the behavior that its
    actual finite string input actually specifies.



    polcott, i'm working on making the halting problem complete and
    consistent in regards to a subset of the improved "reflective turing
    machines" that encompasses all useful computations

    i'm sorry, but not about trying to reaffirm the halting function as
    still uncomputable by calling it a category error


    I do compute the halting function correctly.

    the halting *function* is an abstract mathematical object that maps a machine description to whether the machine described halts or not, not
    the associated machine description that attempts to compute this


    All Turing machines only compute the mapping
    from input finite strings to some value.
    On this basis I do compute halting correctly.

    I have been doing this for more than three years.
    We probably should not be spamming alt.buddha.short.fat.guy

    i hang out there tho, i have my own reasons for posting this there


    Theory of computation issues are disrespectful
    spam to that group that violate Buddhist compassion.

    I was a long time poster to alt.zen. I still
    have 8969 messages posted there since 2005.

    Also my great grand uncle Henry Steel Olcott
    was a very famous Buddhist.


    int sum(int x, int y){return x + y;}
    sum(3,2) should return 5 and it is incorrect
    to require sum(3,2) to return the sum of 5+6.


    u can argue about what computing machines actually exist all u want, and whether anything actually computes the halting *function*, i'm not going
    to argue over what the halting *function* itself is


    Then you get the wrong answer.

    In computability theory and computational complexity
    theory, a decision problem is a computational problem
    that can be posed as a yes–no question on a set of
    input values. https://en.wikipedia.org/wiki/Decision_problem

    Most people have no idea that there is such a thing
    as an incorrect question. Because of this they misclassify
    incorrect yes/no questions as undecidable decision problem
    instances.
    --
    Copyright 2025 Olcott<br><br>

    My 28 year goal has been to make <br>
    "true on the basis of meaning expressed in language"<br>
    reliably computable.<br><br>

    This required establishing a new foundation<br>
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 13 13:41:16 2025
    From Newsgroup: comp.theory

    On 12/13/25 9:43 AM, Tristan Wibberley wrote:
    On 12/12/2025 15:02, Richard Damon wrote:

    Nothing in the context above seemed to provide the definition pondered
    below.
    ...

    no, there's always going to be some machine which they cannot answer
    for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an input
    that doesn't meet the requriement, but might not answer for such input.

    Is that by one of Olcott's definitions or a conventional one?

    Conventional, from the Computation Theory I studied decades ago.


    In the field of AI, "Recogniser" is already taken and includes those
    that give "false", "incorrect", "untruthful", "unconventional" and "not-as-labelled" results, however you want to call it.

    But is also used in classical Computation Theory as a step down from
    Deciders.


    "Deductive Recogniser" might be a good term, it avoids the notion of
    absolute truth and falsity but it can easily be seen to be relative to
    your formal system's correctness, which I think is what we really
    require (it's perfect as far your formal system defines perfect).

    A physical embodiment such as a real computer that ostensibly implements
    a deductive recogniser wouldn't be one, not really.

    Nothing in Classical Computation Theory is concerned with "physical embodiment" or "real computer" as the field pre-dates our developmenht
    of such.

    In those days, a "Computer" was a person who was "mechanically"
    following a recipe with an input pile and scratch paper to generate a
    result.



    ...
    I didn't read the rest.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,alt.buddha.short.fat.guy on Sat Dec 13 17:17:28 2025
    From Newsgroup: comp.theory

    On 12/13/25 6:26 AM, Richard Damon wrote:
    On 12/13/25 12:18 AM, dart200 wrote:
    On 12/12/25 7:02 AM, Richard Damon wrote:
    On 12/11/25 2:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the machine: >>>>>>>>>
    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong.

    YOU need to provide some machine that my arguement will label as H. >>>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed >>>>>>> to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i >>>>>> did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any and >>>>>> all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but sometimes >>>>
    yeah that's what i explored in the paper i posted

    But if your modifed criteria isn't itself useful, what good is it. THe

    idk what's with boomers and the notion that someone needs to have
    literally everything worked out about a thing before posting an idea???

    Not that you need to have it all worked out, but that you evaluate as
    you go if there are signs of it being useful.


    if it doesn't interest you yet, then it's prolly not for you yet

    Yet, you ask for help.

    The problem is if you don't think of usefulness at the start, you will certainly end up with a system without usefulness.

    TV reality

    history is littered with entirely serendipitous innovation, and in fact
    our progression depends on serendipity. which is why creativity for the
    sake it, rather than with purpose, can be required


    It seems you are making the same error of Olcott, of diving into a field that you are ignorant of. There are REASONS for the rules you want to flaunt, and by doing so you condemn your work to the trash heap of
    worthless ideas.


    fact that you began with a disclaimer that you weren't going to look
    at the quality of the criteria makes the rest meaningless. After all,
    we HAVE a lot of existing answers like that, either over machines of
    reduced capability of partial results.


    don't answer. This class is more useful if they always eventually
    answer for one side of the decision, and only not-answer sometimes
    for the

    no, there's always going to be some machine which they cannot answer
    for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an
    input that doesn't meet the requriement, but might not answer for
    such input.

    Thus a Halting Recognizer is possible, as any machine that as part of
    its operation simulates the machine at a non-vanishing rate will
    eventually reach the halting state, and thus give the correct answer.

    If your ideas can't reach even that standard, they are less useful
    than existing results.


    please do read §2 of that paper

    depends on having the time to read something that began with a
    disclaimer that indicates it likely isn't valuable.

    i mean u have a bunch time to keep dicking me around on this, richard...

    No, I look at things when I have a few spare moments waiting for other things to happen. To properly read a 20 page paper takes more of an
    effort, and when it begins with a disclaimer that tells me the author
    isn't going to even try to make things useful, there isn't much of an incentive.

    ok keep arguing about something u haven't read then, that'll surely teach me



    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines,
    and non- halting for a large class of non-halting machines. I
    looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is
    useful.

    It is easy to create a system where Halting can be decided, it just >>>>> needs making the system less than Turing Complete, so if you idea
    is based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox >>>>>>
    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable numbers/, >>>>>> but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read the >>>>> full paper).

    All that is doing is admitting that by the definitions accepted for >>>>> defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a
    more conventional perspective,

    because the implications are so broad my interest was to just focus
    on the idea of the technique vs why

    And if you won't do the work to see if your ideas have any value, why
    should anyone else?

    i made another paper on a reason to use it, and it worked out
    miraculously well. turing would have been impressed, because it did
    the unfathomable in making a direct diagonal (across computable
    numbers) actually computable, while leaving the inverse still
    uncomputable...

    What is a "Computable Number"?

    How can we know if a number is "Computable"?

    like turing's paper, decider D on the matter is assumed



    and idk how to unlearn that

    https://www.academia.edu/143540657

    Which begins with an error, Turing Machines do not uniquely map to
    finite strings, and thus do not uniquely map to numbers.

    *can be*, u moron


    The problem is the "name" of the states in the Turing Machine are
    arbitrary, but end up in some manner in the string. Since we can easily
    just assign the same machine different names for the states, we can
    create many different encodings for a given machine.

    You even quote his statement:
    To each computable sequence there corresponds at least one description number, while to no description number does there correspond more than
    one computable sequence. The computable sequences and numbers are
    therefore enumerable

    It seems you may need to study some of the properties of infinite sets better.

    Now, each string represents just a single machine, so we can still

    yes, so the machines are *uniquely* described by each description number/string 🙄🙄🙄

    iterate through all machines, we just see each machine many times in
    that infinite iteration.



    As I have said, there are MANY other results in the category you are
    talking about, and if you aren't going to compare your results to
    them and show similar usefullness, why bother.

    My guess is you didn't look at much prior art, and thus your results
    are likely poorer version of the existing work based on smarter
    people working on the results of other smarter people.

    u find me anything like the paper i just linked to, and i'll delete
    thunderbird to leave this god-forsaking group forever

    Have you looked at ANYTHING academic on infinite sets?d
    no actually i can't even read



    and please don't comment on it until you read it enough to at least
    explain to me how i used a quine in the paper. and no, the quine
    itself doesn't solve turing's problem, but it does do something
    interesting that turing never recognized because he never knew about
    quines


    Since you start with:
    The diagonal computation must compute the unique natural number nh that describes it,

    But, as shown above, there is no such number, as compuations are
    represented by an infinite set of numbers, your logic is just based on a false premise.

    bruh, if ever u could read more than one sentence at a time:

    /The particular number that represents a machine is entirely dependent
    on the specific language that the machine description has been encoded by/





    But, what good is an alternate formulation if you aren't going to
    discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷

    Yes, the first step of such a project should have been a study of
    what others have done. After all, those who won't study history are
    doomed to repeat it. If you didn't look into other attempts, you
    likely went down the same dead ends that have been traveled in the past.

    if only life proceeded like such TV reality


    So instead you walked out into the void with no idea of where you are
    going, and hoping you will just stumble upon something useful.

    like i said, i can't even read so ...





    It seems this is just another person not understand the reasoning
    behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine >>>>>>>> which *no* machine could decide upon, for if that machine was >>>>>>>> decidable by anything, then BB could find that anything and
    subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit? >>>>>
    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6 states
    that are not decidable

    Right, but that isn't the definition of "Computable" for a function.

    BB_up_to_5_returns_0_after(n) is a wholly computable function

    Sure, but that isn't BB


    "computable up to a limit" is a meaningful phrase that can be
    represented by more constrained functions that are indeed fully
    computable, returning some recognizable non-answer after the "limit"
    to computability it reached.

    It may be "meaningful", but may not be useful.

    If you can prove that limit point is big enough, there might be some
    uses for it on small practical problems.

    For uses in logic theory, which was the initial goal of the field, ALL
    means ALL and not just for small numbers.



    Just like "Undecidable Problems" can be correctly decided for a lot
    of possible inputs, just not for all.



    BB(n) is the maximum length tape that a Turing Machine of n states
    can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver


    No, the "input" is the number of states in the machine.

    There are two versions of Busy Beaver, one is the number of symbols
    output, the other is the number of steps it can run.

    The first is actually the original as I remember, because that is an
    actual semantic property of a machine as normally defined. Steps are
    not, as the operation of a Turing Machine is classically looked at as
    a black box and thus HOW it generated the results are not
    significant, just that it did.

    could have just read the article instead of speculated bro:

    /Radó defined two functions related to the busy beaver game: the score
    function Σ(n) and the shifts function S(n) Both take a number of
    Turing machine states n and output the maximum score attainable by a
    Turing machine of that number of states by some measure. The score
    function Σ(n) gives the maximum number of 1s an n-state Turing machine
    can output before halting, while the shifts function S(n) gives the
    maximum number of shifts (or equivalently steps, because each step
    includes a shift) that an n-state Turing machine can undergo before
    halting/

    And neither is computable for all values.

    Note, I was pointing out that you were inaccurate in your correction to
    my statement.

    BB, as originally stated, was about length of tape generated.

    as the paragraph said: the original score function was: /maximum number
    of 1s an n-state Turing machine can output before halting/ which is
    analogous to but does not necessarily match "tape length"

    but he also directly talked about "shifts" which is analogous to, but
    does also not directly match, "steps"

    bruh ur gunna have to step down from being a chief engineer right about everything for once, because ur now making nuanced errors that could
    have been avoided by actually reading instead of just skimming + presuming





    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    Right. The steps is better for talking about the Halting Problem, and
    likely the source of that variant.


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    But your terminolgy is just bad there.


    if L doesn't exist, that would make halting generally decidable, so
    therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it

    Wrong. If by "Partial Decider" you mean a machine that is right for
    some inputs, but wrong for other, ALL inputs are partially decidable.
    As the pair of machines one that says Halting for all inputs and one
    that says Non-Halting for all inputs would be right.

    If you mean by "Partial Decider" a machine that is always right when it

    yes

    Ok, that is the more useful definition.


    answers. but might not answer, your results don't follow, as the set
    of partial deciders is (at least potentially) infinte, and thus BB
    couldn't combine the whole set to get the answer.

    it is infinite. heck for any single machine there are infinite
    machines that compute that same function.

    BB just does an unbounded search running incrementally running more of
    them simultaneously. for every iteration it starts 1 partial decider
    to it's list of in-progress deciders, runs them all one step, and
    tests each one for an answer

    But that means you need an enumerated list of all machines that ARE
    partial deciders, and which excludes machines that are just incorrect.

    instead of searching, i'd probably generate more and more of them just
    named differently. it's not like the difference between two partial
    deciders is really algorithmic in nature, it's just that they have
    different names


    That tends to mean you need a finite test that a given machine is such a machine, and that is an uncomputable problem.


    if there is an answer out there, then it will be found...
    which ikd what ur gunna do about that rick, or was ur nick-name dick,
    eh? i mean u know this kinda drill already, it's similar to
    enumerating out halting machines.

    Right, It is a task that can't be done. The problem is that there will
    be some machines that no always correct partial decider will decide, we
    just won't be able to identify those machines, they will just always be
    a member of the cloud of currently unknown machines, and while we can
    reduce that set with more and more work, it turns out it can never be
    empty.

    If your logic can't handle that some things are inherently unknowable,
    it can't handle this problem. This is part of Olcott's trap, He can't distringuish between Known and True, but thinks we can know all truths.

    bruh i'm only talking about computing here, not *all* truths


    You try to dismiss this as just "Ghosts", but the problem is that these ghosts do exists, they are just unknowable.

    and i still don't believe in ghosts 😂😂😂




    This is your "ghost" problem, that since we don't know which inputs a
    given partial decider will fail to answer on, we can't just work on
    infinite enumerations of them.


    We can sometimes establish upper and lower bounds on the value of
    BB(n), is that what you mean by "a limit L"?


    if you believe the halting problem, then BB must have a limit L,
    or else halting becomes generally solvable using the BB function. >>>>>> see, if you can compute the BB number for any N-state machines,
    then for any N-state machine u can just run the N-state machine
    until BB number of steps. any machine that halts on or before
    BB(N) steps halts, any that run past must be nonhalting

    No, if we could establish an upper limit for BB(n) for all n, then
    we could solve the hatling problem, as we have an upper limit for
    the number of steps we need to simulate the machine.

    BB(n) has a value, but for sufficiently large values of n, we don't >>>>> have an upper bound for BB(n).


    and the problem with allowing for partial decidability is that BB >>>>>> can run continually run more and more deciders in parallel, on
    every N- state machine, until one comes back with an halting
    answer, for every N-state machine, which then it can the use to
    decide what the BB number is for any N ...

    So, what BB are you running? Or are you misusing "running" to try
    to mean somehow trying to calculate?

    contradicting the concept it must have a limit L, where some L-
    state machine cannot be decidable by *any* partial decider on the >>>>>> matter,

    No, it can have a limit, just not a KNOWN limit.

    consensus is there can a known limit L to the BB function, and
    proofs have been put out in regards to this


    I was talking about a know limit to the value PRODUCED by BB.

    After all, you discussion of a limit on the input is really a
    category error, as the function BB can take any number as its input.

    What you really mean is that the domain processed by
    calculatable_BB(n) has an upper limit, and yes, it can be proven that
    there must be a value above which BB can not be calculable, and I
    believe some values as upper limits of that limit have been found.


    the proof for the upper limit rn depends on how well someone could
    bit- pack a halting paradox into their proof i think, lol

    Not quite but close.





    so no richard, partial decidability does not work if BB is to have >>>>>> a limit


    You only have the problem is BB has a KNOWN limit. Again, you trip
    up on assuming you can know any answer you want.

    That some things are not knowable breaks your logic.




    --
    hi, i'm nick! let's end war 🙃

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Damon@Richard@Damon-Family.org to comp.theory,alt.buddha.short.fat.guy on Sat Dec 13 20:50:49 2025
    From Newsgroup: comp.theory

    On 12/13/25 8:17 PM, dart200 wrote:
    On 12/13/25 6:26 AM, Richard Damon wrote:
    On 12/13/25 12:18 AM, dart200 wrote:
    On 12/12/25 7:02 AM, Richard Damon wrote:
    On 12/11/25 2:35 PM, dart200 wrote:
    On 12/9/25 8:02 PM, Richard Damon wrote:
    On 12/9/25 1:55 PM, dart200 wrote:
    On 12/9/25 4:42 AM, Richard Damon wrote:
    On 12/9/25 12:23 AM, dart200 wrote:
    On 12/8/25 8:12 PM, Richard Damon wrote:

    ???

    Given Machine H is chosen as one partial decider then the >>>>>>>>>> machine:

    H^(d): if H(d, d) returns halting, loop forever
            else halt.

    i'm sorry now ur claiming H(d,d) actually returns an answer??? >>>>>>>>>
    when did this happen, and what does it return buddy???

    what ever its programs says it will.

    Do you not understand the concept of a parameter to an arguement? >>>>>>>>
    My claim is if *YOU* give me a machine H, I can prove it wrong. >>>>>>>>
    YOU need to provide some machine that my arguement will label as H. >>>>>>>>


    Then H^(H^) will show that H was wrong for H(H^, H^)

    How is that not showing the machine which that machine can not >>>>>>>>>> decider.

    partial decidable does not fly it loses to BB

    Nope, because "partial deciability" means the machine is allowed >>>>>>>> to not answer.

    so what ur saying is H won't answer, so H^ will have an answer? i >>>>>>> did explore that paradigm in one of my papers, a believe it's
    possible to create a program that seeks out an contradicts any
    and all deciders that try to decide on it:

    H^ must have a behavior, so there is a correct answer.

    One semi-useful class of partial decider, which are also called
    recognizer, are machines that never give a wrong answer, but
    sometimes

    yeah that's what i explored in the paper i posted

    But if your modifed criteria isn't itself useful, what good is it. THe >>>
    idk what's with boomers and the notion that someone needs to have
    literally everything worked out about a thing before posting an idea???

    Not that you need to have it all worked out, but that you evaluate as
    you go if there are signs of it being useful.


    if it doesn't interest you yet, then it's prolly not for you yet

    Yet, you ask for help.

    The problem is if you don't think of usefulness at the start, you will
    certainly end up with a system without usefulness.

    TV reality

    Nope, you are just showing your stupidity.



    history is littered with entirely serendipitous innovation, and in fact
    our progression depends on serendipity. which is why creativity for the
    sake it, rather than with purpose, can be required

    Inovation needs to start with a knowledge of the basics, something you
    don't seem to have.



    It seems you are making the same error of Olcott, of diving into a
    field that you are ignorant of. There are REASONS for the rules you
    want to flaunt, and by doing so you condemn your work to the trash
    heap of worthless ideas.


    fact that you began with a disclaimer that you weren't going to look
    at the quality of the criteria makes the rest meaningless. After
    all, we HAVE a lot of existing answers like that, either over
    machines of reduced capability of partial results.


    don't answer. This class is more useful if they always eventually >>>>>> answer for one side of the decision, and only not-answer sometimes >>>>>> for the

    no, there's always going to be some machine which they cannot
    answer for both sides

    Then you concepts doesn't have Recognizers, as BY DEFIHITION, they
    always correct accept any input that satisfies the requirement, and
    never incorrect accept an input that doesn't. They may reject an
    input that doesn't meet the requriement, but might not answer for
    such input.

    Thus a Halting Recognizer is possible, as any machine that as part
    of its operation simulates the machine at a non-vanishing rate will
    eventually reach the halting state, and thus give the correct answer.

    If your ideas can't reach even that standard, they are less useful
    than existing results.


    please do read §2 of that paper

    depends on having the time to read something that began with a
    disclaimer that indicates it likely isn't valuable.

    i mean u have a bunch time to keep dicking me around on this, richard...

    No, I look at things when I have a few spare moments waiting for other
    things to happen. To properly read a 20 page paper takes more of an
    effort, and when it begins with a disclaimer that tells me the author
    isn't going to even try to make things useful, there isn't much of an
    incentive.

    ok keep arguing about something u haven't read then, that'll surely
    teach me

    I have taken a quick look at it. Once you assumed that every machine has
    a unique number, you were cooked, as that is a false statement.




    other. Halting is partially decidable by this criteria, with a
    decider that eventually answer halting for all halting machines,
    and non- halting for a large class of non-halting machines. I
    looked at machines of this type in the late 70's in school.

    Also, "beleive" is not proof, and doesn't mean you framework is
    useful.

    It is easy to create a system where Halting can be decided, it
    just needs making the system less than Turing Complete, so if you >>>>>> idea is based on that, so what.


    https://www.academia.edu/136521323/how_to_resolve_a_halting_paradox >>>>>>>
    (partial decidability also wouldn't work in Turing's
    "satisfactory" problem from the og paper /on computable numbers/, >>>>>>> but we'll get there later)


    The Abstract talks about changing the meaning of basics of
    Conputation theory and the defintion of Halting (I haven't read
    the full paper).

    All that is doing is admitting that by the definitions accepted
    for defining a computation and what halting means, the author is
    conceeding that Halting is uncomputable.

    The paper than says:

    This paper does not attempt to present at depth arguments or
    reasons for why we should accept either of these proposals vs a
    more conventional perspective,

    because the implications are so broad my interest was to just focus >>>>> on the idea of the technique vs why

    And if you won't do the work to see if your ideas have any value,
    why should anyone else?

    i made another paper on a reason to use it, and it worked out
    miraculously well. turing would have been impressed, because it did
    the unfathomable in making a direct diagonal (across computable
    numbers) actually computable, while leaving the inverse still
    uncomputable...

    What is a "Computable Number"?

    How can we know if a number is "Computable"?

    like turing's paper, decider D on the matter is assumed

    And proved to not be able to exist.

    If you understand logic, you will realize that you are allowed to
    temporarily assume something exists to prove that it can't, you can't
    assume something to exist to prove that it exists.

    This is the nature of proof by contradiction,




    and idk how to unlearn that

    https://www.academia.edu/143540657

    Which begins with an error, Turing Machines do not uniquely map to
    finite strings, and thus do not uniquely map to numbers.

    *can be*, u moron


    Nope.

    A given Turing Machine can be expressed in an infinite number of string/numbers unless it is a trivial machine.



    The problem is the "name" of the states in the Turing Machine are
    arbitrary, but end up in some manner in the string. Since we can
    easily just assign the same machine different names for the states, we
    can create many different encodings for a given machine.

    You even quote his statement:
    To each computable sequence there corresponds at least one description
    number, while to no description number does there correspond more than
    one computable sequence. The computable sequences and numbers are
    therefore enumerable

    It seems you may need to study some of the properties of infinite sets
    better.

    Now, each string represents just a single machine, so we can still

    yes, so the machines are *uniquely* described by each description number/string 🙄🙄🙄

    Nope. You have many strings each which represent the same machine, but
    no string represents more than one machine.

    It is sort of like the fact that the size of the Rationals is the same
    as the size of the Natural Numbers.


    iterate through all machines, we just see each machine many times in
    that infinite iteration.



    As I have said, there are MANY other results in the category you are
    talking about, and if you aren't going to compare your results to
    them and show similar usefullness, why bother.

    My guess is you didn't look at much prior art, and thus your results
    are likely poorer version of the existing work based on smarter
    people working on the results of other smarter people.

    u find me anything like the paper i just linked to, and i'll delete
    thunderbird to leave this god-forsaking group forever

    Have you looked at ANYTHING academic on infinite sets?d
    no actually i can't even read

    Then I guess you aare just admitting to being a liar.




    and please don't comment on it until you read it enough to at least
    explain to me how i used a quine in the paper. and no, the quine
    itself doesn't solve turing's problem, but it does do something
    interesting that turing never recognized because he never knew about
    quines


    Since you start with:
    The diagonal computation must compute the unique natural number nh
    that describes it,

    But, as shown above, there is no such number, as compuations are
    represented by an infinite set of numbers, your logic is just based on
    a false premise.

    bruh, if ever u could read more than one sentence at a time:

    /The particular number that represents a machine is entirely dependent
    on the specific language that the machine description has been encoded by/


    Nope. Even in the "specific language" (if you mean the rules for
    encoding) there are many encodings for a given machine, as the internal labeling of the states is arbitrary.





    But, what good is an alternate formulation if you aren't going to >>>>>> discuss why the alternative is going to be useful.

    i cannot condense meaning into the abstract and conclusions, u'd
    actually have to read it 🤷

    Yes, the first step of such a project should have been a study of
    what others have done. After all, those who won't study history are
    doomed to repeat it. If you didn't look into other attempts, you
    likely went down the same dead ends that have been traveled in the
    past.

    if only life proceeded like such TV reality


    So instead you walked out into the void with no idea of where you are
    going, and hoping you will just stumble upon something useful.

    like i said, i can't even read so ...

    So, I guess you are just a worm. (Write Only Random Memory)

    If that is your attitude, you have a great opertunity to be Olcott II






    It seems this is just another person not understand the reasoning >>>>>> behind how computations were defined, and why "Halting" was an
    important question, but just wants to create a somewhat similar
    solvable problem, even if such an alternative problem has no use.



    if BB has some limit L (which is must if u believe halting
    problem), then there must be some specifically L-state machine >>>>>>>>> which *no* machine could decide upon, for if that machine was >>>>>>>>> decidable by anything, then BB could find that anything and >>>>>>>>> subvert the limit L

    WHy does BB need to have a limit L?

    my my richard, u don't know that in ur theory BB must have a limit? >>>>>>
    You seem to be using undefined terms.

    BB is apparently the Busy Beaver problem, which since it is
    uncomputable, can't actually be a machine.

    yeah but it's certainly computable up until a limit, as we've
    already computed it up to 5, there cannot be any machines <6 states >>>>> that are not decidable

    Right, but that isn't the definition of "Computable" for a function.

    BB_up_to_5_returns_0_after(n) is a wholly computable function

    Sure, but that isn't BB


    "computable up to a limit" is a meaningful phrase that can be
    represented by more constrained functions that are indeed fully
    computable, returning some recognizable non-answer after the "limit"
    to computability it reached.

    It may be "meaningful", but may not be useful.

    If you can prove that limit point is big enough, there might be some
    uses for it on small practical problems.

    For uses in logic theory, which was the initial goal of the field, ALL
    means ALL and not just for small numbers.



    Just like "Undecidable Problems" can be correctly decided for a lot
    of possible inputs, just not for all.



    BB(n) is the maximum length tape that a Turing Machine of n states >>>>>> can create and then halt.

    technically it's steps: https://en.wikipedia.org/wiki/Busy_beaver


    No, the "input" is the number of states in the machine.

    There are two versions of Busy Beaver, one is the number of symbols
    output, the other is the number of steps it can run.

    The first is actually the original as I remember, because that is an
    actual semantic property of a machine as normally defined. Steps are
    not, as the operation of a Turing Machine is classically looked at
    as a black box and thus HOW it generated the results are not
    significant, just that it did.

    could have just read the article instead of speculated bro:

    /Radó defined two functions related to the busy beaver game: the
    score function Σ(n) and the shifts function S(n) Both take a number
    of Turing machine states n and output the maximum score attainable by
    a Turing machine of that number of states by some measure. The score
    function Σ(n) gives the maximum number of 1s an n-state Turing
    machine can output before halting, while the shifts function S(n)
    gives the maximum number of shifts (or equivalently steps, because
    each step includes a shift) that an n-state Turing machine can
    undergo before halting/

    And neither is computable for all values.

    Note, I was pointing out that you were inaccurate in your correction
    to my statement.

    BB, as originally stated, was about length of tape generated.

    as the paragraph said: the original score function was: /maximum number
    of 1s an n-state Turing machine can output before halting/ which is analogous to but does not necessarily match "tape length"

    Maybe in the paper you read (but then you said you can't read). But historicaly the initial score function was length of the output tape.


    but he also directly talked about "shifts" which is analogous to, but
    does also not directly match, "steps"

    bruh ur gunna have to step down from being a chief engineer right about everything for once, because ur now making nuanced errors that could
    have been avoided by actually reading instead of just skimming + presuming

    Part of my job is to notice problems before things get too far.

    If you want to just continue down a failing path, go ahead.






    but for the purposes of this discussion it doesn't really matter
    whether it's space or steps we're talking about


    Right. The steps is better for talking about the Halting Problem,
    and likely the source of that variant.


    BB(n) is, by definitiion a "finite" number. Talking about the
    "limit" of a finite number is a misuse of the term.

    i mean the natural number limit L >5 at which point BB(L) becomes
    fundamentally *unknowable* due to some L-state machine being
    fundamentally undecidable.

    But your terminolgy is just bad there.


    if L doesn't exist, that would make halting generally decidable, so >>>>> therefore L must exist

    if L does exist, then there must be some L-state machine U which
    cannot be decided on *by any partial* decider, because the BB
    computation would find it and use it

    Wrong. If by "Partial Decider" you mean a machine that is right for
    some inputs, but wrong for other, ALL inputs are partially
    decidable. As the pair of machines one that says Halting for all
    inputs and one that says Non-Halting for all inputs would be right.

    If you mean by "Partial Decider" a machine that is always right when it >>>
    yes

    Ok, that is the more useful definition.


    answers. but might not answer, your results don't follow, as the set
    of partial deciders is (at least potentially) infinte, and thus BB
    couldn't combine the whole set to get the answer.

    it is infinite. heck for any single machine there are infinite
    machines that compute that same function.

    BB just does an unbounded search running incrementally running more
    of them simultaneously. for every iteration it starts 1 partial
    decider to it's list of in-progress deciders, runs them all one step,
    and tests each one for an answer

    But that means you need an enumerated list of all machines that ARE
    partial deciders, and which excludes machines that are just incorrect.

    instead of searching, i'd probably generate more and more of them just
    named differently. it's not like the difference between two partial
    deciders is really algorithmic in nature, it's just that they have
    different names

    How do you "generate" them? That means you need to show you can make a
    full decider to determine if a given machine is a partial decider.

    And no, two different partial deciders isn't just their name, or they
    are really the same decider, for your method to work, you need to find a
    set of partial deciders that together decide on every possible input.
    That needs more than finding just variations on the ones you already
    have found, as those don't help your search space.




    That tends to mean you need a finite test that a given machine is such
    a machine, and that is an uncomputable problem.


    if there is an answer out there, then it will be found...
    which ikd what ur gunna do about that rick, or was ur nick-name
    dick,
    eh? i mean u know this kinda drill already, it's similar to
    enumerating out halting machines.

    Right, It is a task that can't be done. The problem is that there will
    be some machines that no always correct partial decider will decide,
    we just won't be able to identify those machines, they will just
    always be a member of the cloud of currently unknown machines, and
    while we can reduce that set with more and more work, it turns out it
    can never be empty.

    If your logic can't handle that some things are inherently unknowable,
    it can't handle this problem. This is part of Olcott's trap, He can't
    distringuish between Known and True, but thinks we can know all truths.

    bruh i'm only talking about computing here, not *all* truths


    You try to dismiss this as just "Ghosts", but the problem is that
    these ghosts do exists, they are just unknowable.

    and i still don't believe in ghosts 😂😂😂

    Maybe you should, as in this case they are real. Closing your eyes and ignoring them won't make them go away.


    --- Synchronet 3.21a-Linux NewsLink 1.2