• on the nature of undecidability within computing: and refuting the church turing thesis

    From dart200@user7160@newsgrouper.org.invalid to comp.theory,sci.logic,alt.buddha.short.fat.guy on Wed Aug 26 22:40:41 2026
    From Newsgroup: comp.theory

    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how
    an idealized human agent can compute that which is not turing computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling a
    bit hesitant to go further into the arguments... idk u could tempt me
    prolly Efn+

    i'm willing to post the section headers as of now:

    1 the halting problem
    2 the circle-free problem
    2.1 turing's diagonal
    2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    3.1 clarification on self-reference
    4 how undecidability is it?
    4.1 reducing circle-free to halting
    4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    5.1 bugfix: adding an identify check
    5.2 bugfix: injecting a partial recognizer
    5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    6.1 a proposed limit to undecidability within computing
    6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    7.1 the terminal machine
    7.2 a record on the side
    7.3 inject value and reduce
    7.4 objective mechanics vs addressable simulation
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 15:29:19 2026
    From Newsgroup: comp.theory

    On 27/08/2026 1:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how
    an idealized human agent can compute that which is not turing computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling a
    bit hesitant to go further into the arguments... idk u could tempt me
    prolly Efn+

    i'm willing to post the section headers as of now:


    I'm also a little hesitant I'll understand your paper, but the following section headers are indeed enticing. Will you put the paper up some-
    where plebs like me can read them, once you publish?


    1 the halting problem
    2 the circle-free problem
    -a2.1 turing's diagonal
    -a2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    -a3.1 clarification on self-reference
    4 how undecidability is it?
    -a4.1 reducing circle-free to halting
    -a4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    -a5.1 bugfix: adding an identify check
    -a5.2 bugfix: injecting a partial recognizer
    -a5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    -a6.1 a proposed limit to undecidability within computing
    -a6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    -a7.1 the terminal machine
    -a7.2 a record on the side
    -a7.3 inject value and reduce
    -a7.4 objective mechanics vs addressable simulation
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 10:49:58 2026
    From Newsgroup: comp.theory

    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how
    an idealized human agent can compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing computable? Much can be computed with a Turing computable partial
    method.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory on Thu Aug 27 19:46:11 2026
    From Newsgroup: comp.theory

    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing computable? Much can be computed with a Turing computable partial
    method.


    I previously gave this practical counter example, and you're welcome
    to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something, anything. Now, after that feat, how do you do this with a Turing mach-
    ine? You can obviously simulate the Antikythera mechanism with a Turing machine, but you cannot /compute/ as one. At best, you can use
    armatures controlled by the Turing machine to turn the dials of the
    Antikythera mechanism.

    Now, can you positively prove, that a computation done with an Antiky-
    thera mechanism can be done with a Turing machine, and that it's not a simulation thereof?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 07:34:27 2026
    From Newsgroup: comp.theory

    On 08/26/2026 10:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how
    an idealized human agent can compute that which is not turing computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling a
    bit hesitant to go further into the arguments... idk u could tempt me
    prolly Efn+

    i'm willing to post the section headers as of now:

    1 the halting problem
    2 the circle-free problem
    2.1 turing's diagonal
    2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    3.1 clarification on self-reference
    4 how undecidability is it?
    4.1 reducing circle-free to halting
    4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    5.1 bugfix: adding an identify check
    5.2 bugfix: injecting a partial recognizer
    5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    6.1 a proposed limit to undecidability within computing
    6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    7.1 the terminal machine
    7.2 a record on the side
    7.3 inject value and reduce
    7.4 objective mechanics vs addressable simulation

    What you might find is yourself establishing the _independence_
    of various ordinary theorems vis-a-vis their conjecture, from
    usual ordinary theories that you'll be finding have implicits
    and stipulations that while so seemingly innocuous or plain,
    were always inside a box that declared itself open and closed.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 12:48:17 2026
    From Newsgroup: comp.theory

    On 8/27/26 7:34 AM, Ross Finlayson wrote:
    On 08/26/2026 10:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how
    an idealized human agent can compute that which is not turing computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling a
    bit hesitant to go further into the arguments... idk u could tempt me
    prolly Efn+

    i'm willing to post the section headers as of now:

    1 the halting problem
    2 the circle-free problem
    -a 2.1 turing's diagonal
    -a 2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    -a 3.1 clarification on self-reference
    4 how undecidability is it?
    -a 4.1 reducing circle-free to halting
    -a 4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    -a 5.1 bugfix: adding an identify check
    -a 5.2 bugfix: injecting a partial recognizer
    -a 5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    -a 6.1 a proposed limit to undecidability within computing
    -a 6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    -a 7.1 the terminal machine
    -a 7.2 a record on the side
    -a 7.3 inject value and reduce
    -a 7.4 objective mechanics vs addressable simulation

    What you might find is yourself establishing the _independence_

    while a particular number can be computed by an idealize human agent
    (the anti-diagonal across turing computable sequences),

    it is necessary that said number is not turing computable lest a
    contradiction would be generated as per turing's original paper /on
    computable numbers/

    of various ordinary theorems vis-a-vis their conjecture, from
    usual ordinary theories that you'll be finding have implicits
    and stipulations that while so seemingly innocuous or plain,
    were always inside a box that declared itself open and closed.

    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 12:48:55 2026
    From Newsgroup: comp.theory

    On 8/27/26 12:29 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 1:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling
    a bit hesitant to go further into the arguments... idk u could tempt
    me prolly Efn+

    i'm willing to post the section headers as of now:


    I'm also a little hesitant I'll understand your paper, but the following section headers are indeed enticing.-a Will you put the paper up some-
    where plebs like me can read them, once you publish?

    of course, i'm but a pleb writing for other interested plebs, eh?

    i have other related material posted here:

    https://independent.academia.edu/NickSwenson26

    none of them are peer reviewed atm, nor as well technically developed,
    but are by and large related to the what i'm writing about now, which is
    the first i expect to be able to publish


    1 the halting problem
    2 the circle-free problem
    -a-a2.1 turing's diagonal
    -a-a2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    -a-a3.1 clarification on self-reference
    4 how undecidability is it?
    -a-a4.1 reducing circle-free to halting
    -a-a4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    -a-a5.1 bugfix: adding an identify check
    -a-a5.2 bugfix: injecting a partial recognizer
    -a-a5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    -a-a6.1 a proposed limit to undecidability within computing
    -a-a6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    -a-a7.1 the terminal machine
    -a-a7.2 a record on the side
    -a-a7.3 inject value and reduce
    -a-a7.4 objective mechanics vs addressable simulation


    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Thu Aug 27 12:50:29 2026
    From Newsgroup: comp.theory

    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function
    that is strictly outside the bounds of turing computability

    computable? Much can be computed with a Turing computable partial
    method.


    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing machine)
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dude@punditster@gmail.com to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 18:00:32 2026
    From Newsgroup: comp.theory

    On 8/27/2026 12:29 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 1:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling
    a bit hesitant to go further into the arguments... idk u could tempt
    me prolly Efn+

    i'm willing to post the section headers as of now:


    I'm also a little hesitant I'll understand your paper, but the following section headers are indeed enticing.-a Will you put the paper up some-
    where plebs like me can read them, once you publish?

    Most of the code is posted already. I would copy and paste it here, but
    I know this is a family-oriented board.

    See:

    Nick's Greatest Hits

    alt.messianic



    1 the halting problem
    2 the circle-free problem
    -a-a2.1 turing's diagonal
    -a-a2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    -a-a3.1 clarification on self-reference
    4 how undecidability is it?
    -a-a4.1 reducing circle-free to halting
    -a-a4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    -a-a5.1 bugfix: adding an identify check
    -a-a5.2 bugfix: injecting a partial recognizer
    -a-a5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    -a-a6.1 a proposed limit to undecidability within computing
    -a-a6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    -a-a7.1 the terminal machine
    -a-a7.2 a record on the side
    -a-a7.3 inject value and reduce
    -a-a7.4 objective mechanics vs addressable simulation



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dude@punditster@gmail.com to comp.theory,sci.logic,alt.buddha.short.fat.guy on Thu Aug 27 18:07:54 2026
    From Newsgroup: comp.theory

    On 8/27/2026 12:48 PM, dart200 wrote:
    On 8/27/26 7:34 AM, Ross Finlayson wrote:
    On 08/26/2026 10:40 PM, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate how >>> an idealized human agent can compute that which is not turing
    computable.

    until someone is willing to grant me an cs.LO endorsement i'm feeling a
    bit hesitant to go further into the arguments... idk u could tempt me
    prolly Efn+

    i'm willing to post the section headers as of now:

    1 the halting problem
    2 the circle-free problem
    -a 2.1 turing's diagonal
    -a 2.2 a simpler form
    3 the self-referential set-classification paradox generalized
    -a 3.1 clarification on self-reference
    4 how undecidability is it?
    -a 4.1 reducing circle-free to halting
    -a 4.2 on the "existence" of recursive undecidability
    5 rectifying EYou
    -a 5.1 bugfix: adding an identify check
    -a 5.2 bugfix: injecting a partial recognizer
    -a 5.3 a fallacy in turing's proof
    6 the anti-diagonal problem
    -a 6.1 a proposed limit to undecidability within computing
    -a 6.2 a second fallacy in turing's paper
    7 refuting the church turing thesis
    -a 7.1 the terminal machine
    -a 7.2 a record on the side
    -a 7.3 inject value and reduce
    -a 7.4 objective mechanics vs addressable simulation

    What you might find is yourself establishing the _independence_

    while a particular number can be computed by an idealize human agent
    (the anti-diagonal across turing computable sequences),

    it is necessary that said number is not turing computable lest a contradiction would be generated as per turing's original paper /on computable numbers/

    It looks like your paper is a thesis, not a theorem

    A theorem requires a formal mathematical proof.


    of various ordinary theorems vis-a-vis their conjecture, from
    usual ordinary theories that you'll be finding have implicits
    and stipulations that while so seemingly innocuous or plain,
    were always inside a box that declared itself open and closed.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Fri Aug 28 10:21:42 2026
    From Newsgroup: comp.theory

    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing
    computable? Much can be computed with a Turing computable partial
    method.

    I previously gave this practical counter example, and you're welcome
    to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something, anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged example
    is known and there is no evicence that more was ever constructed.

    Now, after that feat, how do you do this with a Turing machine?
    -aYou can obviously simulate the Antikythera mechanism with a Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Fri Aug 28 00:40:34 2026
    From Newsgroup: comp.theory

    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes
    i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is
    not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof, which
    can't be simulated by a turing machine because any value computed by a
    turing machine is necessarily addressable


    computable? Much can be computed with a Turing computable partial
    method.

    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing
    machine)

    You can suspect anything but without a proof that is nothing.

    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Fri Aug 28 10:27:27 2026
    From Newsgroup: comp.theory

    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    computable? Much can be computed with a Turing computable partial
    method.

    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing machine)

    You can suspect anything but without a proof that is nothing.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Sat Aug 29 11:05:35 2026
    From Newsgroup: comp.theory

    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes
    i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is
    not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof, which can't be simulated by a turing machine because any value computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory on Sat Aug 29 15:17:45 2026
    From Newsgroup: comp.theory

    On 08/29/2026 01:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes
    i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is >>>>>> not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably infinite address space and any finite or countably infinite is
    accessible.

    If Turing computes a limit, is it perfect?


    I imagine by "countably infinite" you don't include "nonstandard
    countable", yet, anybody who talks about point-at-infinity,
    compactification, fixed-point theorems, or even divergence
    to infinity, gets one to deal with. "Super-tasks" and for
    the "super-martingale" and the like is what it's often called,
    and nature does it all the time every day and so does anybody
    who ever passed calculus class.

    "Zeno machines", then, compute.

    ("Bzzzt, does compute.")








    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Sat Aug 29 23:47:53 2026
    From Newsgroup: comp.theory

    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is >>>>>> not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You

    my paper is specifically details how that method can exist, and how the algorithm differs from all the partial classifiers found in the turing computable space, and who no turing machine can truly implement the
    algorithm

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherent more limited by their concrete formally addressable nature.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. and i'm trying to increase their use by resolving
    their limitations more accurately so we stop tripping over the halting
    problem as excuse to not be proving correctness for every single program
    we deploy...

    not testing isn't good enough bro, nor is the braindead way we go about producing and maintain computing infrastructure. the dumb fucking corp
    ratrace to nowhere instead of producing the system we not only need but deserve is just so ungodly

    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountably the prevents the addressing, it's a mechanical discontinuity, and i can only explain by properly describing the thought experiment
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Sat Aug 29 23:51:57 2026
    From Newsgroup: comp.theory

    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is >>>>>> not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    my paper specifically details how that method can exist, and how the
    algorithm differs from all the partial classifiers found in the turing computable space, and why no turing machine can truly implement the
    objective total algorithm even if it is mechanically computable.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by their formally addressable nature.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over the halting problem as excuse to not be proving correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go about producing and maintaining computing infrastructure. the dumb fucking
    corpo ratrace to nowhere instead of producing the systems we not only
    need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a mechanical discontinuity, and i can only explain by properly describing the
    justifying thought experiment
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Sun Aug 30 11:17:02 2026
    From Newsgroup: comp.theory

    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which >>>>>>> is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>
    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    my paper specifically details how that method can exist, and how the algorithm differs from all the partial classifiers found in the turing computable space, and why no turing machine can truly implement the objective total algorithm even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over the halting problem as excuse to not be proving correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go about producing and maintaining computing infrastructure. the dumb fucking
    corpo ratrace to nowhere instead of producing the systems we not only
    need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a mechanical discontinuity, and i can only explain by properly describing the
    justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility. Restrictions
    in accessibility can also be simulated.
    --
    Mikko

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory on Sun Aug 30 10:05:52 2026
    From Newsgroup: comp.theory

    On 08/30/2026 01:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it.
    yes i'm quite serious about refuting the church turing thesis. i >>>>>>>> demonstrate how an idealized human agent can compute that which >>>>>>>> is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>>
    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability >>>>>
    If you can't simulate that agent with a Turing-complete computer you >>>>> cant use it for any computation. If you can you can compute the same >>>>> with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    my paper specifically details how that method can exist, and how the
    algorithm differs from all the partial classifiers found in the turing
    computable space, and why no turing machine can truly implement the
    objective total algorithm even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by
    their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over
    the halting problem as excuse to not be proving correctness for every
    single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go
    about producing and maintaining computing infrastructure. the dumb
    fucking corpo ratrace to nowhere instead of producing the systems we
    not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility. Restrictions
    in accessibility can also be simulated.


    How about "restrictions in non-accessibility".

    A usual account of "transfinite induction schema" makes usually
    that there are uncountably many ordinals, then for accounts of
    induction then transfinite induction after limit ordinals greater
    than zero, has that somehow matematics does that for free, then
    if you've heard of Skolem/Louwenheim/Levy they have countable models
    of uncountable models, which of course would seem paradoxical since
    one of the aspects of such structure in ordinals is the existence of
    ordinals and all their relations.

    The "close-enough" is also the "not-quite".


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Sun Aug 30 18:17:42 2026
    From Newsgroup: comp.theory

    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. >>>>>>>> yes i'm quite serious about refuting the church turing thesis. i >>>>>>>> demonstrate how an idealized human agent can compute that which >>>>>>>> is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>>
    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability >>>>>
    If you can't simulate that agent with a Turing-complete computer you >>>>> cant use it for any computation. If you can you can compute the same >>>>> with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    my paper specifically details how that method can exist, and how the
    algorithm differs from all the partial classifiers found in the turing
    computable space, and why no turing machine can truly implement the
    objective total algorithm even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as "evidence"?


    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by
    their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model directly
    to express algorithms, we use it as a fundamental basis for mechanical computation, but the way we discuss algorithms is far more high level

    the only difference between the agent's algorithm and the partial
    classifiers that exist in turing machines, is that a partial classifier
    must deal with self-references, whereas the agent does not have to
    logically reckon about that because it's not possible to create a direct reference to computational process, again my paper will go into more
    detail here specifically


    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over
    the halting problem as excuse to not be proving correctness for every
    single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go
    about producing and maintaining computing infrastructure. the dumb
    fucking corpo ratrace to nowhere instead of producing the systems we
    not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility. Restrictions
    in accessibility can also be simulated.


    it's not a numerical discontinuity, it's a mechanical one

    it's like trying to program a random turing machine to directly access
    it's own source code ... the information exists in abstract, but the
    turing machine model does not have a mechanical means of accessing it
    (barring a program implemented with a genuine quine, but those are
    exceptions stemming from programmatic solutions, not the fundamental
    mechanics of the machine)

    or it's like asking a turing machine being simulated by another to
    arbitrarily access values from the machine that is simulating it...
    that's just not mechanically possible. a simulator mechanically has
    random and total access to the simulation, but the simulation does not
    have that same access in reverse

    those are forms of mechanical discontinuities where the information just cannot flow because of a lack of specified mechanics for it do so.
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory on Mon Aug 31 09:22:48 2026
    From Newsgroup: comp.theory

    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes
    i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is
    not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing
    computable? Much can be computed with a Turing computable partial
    method.

    I previously gave this practical counter example, and you're welcome
    to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something,
    anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged example
    is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion. Please stop breathing
    those sauna fumes in Finland, and do your original research. Here is
    mine.

    https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been reconstruct-
    ions since. Now, if you want to /define/ a reconstruction as an invalid
    method of arguing on Usenet, I'll just have to tip my top hat to you,
    and insist you invent a time machine instead.


    Now, after that feat, how do you do this with a Turing machine?
    -aYou can obviously simulate the Antikythera mechanism with a Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.


    Let there be epsilon less than delta. Once you have constructed a simu- lation, I'll construct a level, and a fine bolt to adjust it. I believe
    I'll try for twenty thousand threads per inch. So the question is, can
    I nudge an arbitrary long lever, with a bolt -- hopefully starting at
    twenty thousand threads per inch -- finely enough, that each nudge fits
    within the smallest floating point precision you have -- I'm going to
    assume you were going to use double precision in C, REAL*8 in Fortran 77
    or f64 in Rust -- and you won't /see it/ because your simulation lacks
    real world precision?

    Now, since I currently lack a machine shop, I should warn you that I ex-
    pect you to pay me USD 100,000.00 -- that's one hundred thousand United
    States dollars -- to acquire one, and build said lever and bolt. The Antikythera mechanism replica I can probably afford after a few months
    of saving up, so you don't have to add that to your cost analysis.

    Then, the question is, are you a sore enough loser in Usenet arguments,
    that you're willing to pay me to refute you? Or can you accept a grace-
    ful loss and just tip your sword in my direction? I am assuming you are
    a fully anointed philosopher of a doctorate, and got a sword from the
    king of Finland already.


    Best wishes, and happy simulation construction!


    P.S.

    And for people who think this was written by an L.L.M., please try to
    ask ChatGPT what the finest bolt with the largest number of threads per
    inch is, and realize it has no idea, and cannot conceive of someone
    making custom bolt with a large thread count, because it's geared only
    towards selling you bolts that are readily available on the open market,
    and can't conceive of the notion that people can make their own bolts.

    So if you think ChatGPT knows everything, than you're best off by print-
    ing out this followup, and eat it; then never post on Usenet again!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory on Mon Aug 31 09:28:29 2026
    From Newsgroup: comp.theory

    On 30/08/2026 6:17 AM, Ross Finlayson wrote:
    On 08/29/2026 01:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is >>>>>>> not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>
    yes, i use the concept of an idealized human agent to compute a
    function that is strictly outside the bounds of turing computability

    If you can't simulate that agent with a Turing-complete computer you
    cant use it for any computation. If you can you can compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two different
    ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You
    may be able to compute some values of an uncomputable function but you
    can't know that you can compute for arguments that will be given later
    unless you have a method.

    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.

    If Turing computes a limit, is it perfect?

    Dear Ross,

    I believe it is not. As I just followed up with Mikko in a different
    tangent of this conversation, I have positively proven, using the tra-
    ditional /let there be epsilon less than delta/ method, that a there
    is indeed a real world mechanism that trumps all Turing computations
    of a classical limit -- in what we now tend to call -- calculus.



    I imagine by "countably infinite" you don't include "nonstandard
    countable", yet, anybody who talks about point-at-infinity,
    compactification, fixed-point theorems, or even divergence
    to infinity, gets one to deal with. "Super-tasks" and for
    the "super-martingale" and the like is what it's often called,
    and nature does it all the time every day and so does anybody
    who ever passed calculus class.

    "Zeno machines", then, compute.

    ("Bzzzt, does compute.")

    I did not have to resort to any of this word soup to win the argument,
    but you have at it!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Mon Aug 31 12:36:35 2026
    From Newsgroup: comp.theory

    On 31/08/2026 04:22, Johann 'Myrkraverk' Oskarsson wrote:
    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes
    i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is
    not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing
    computable? Much can be computed with a Turing computable partial
    method.

    I previously gave this practical counter example, and you're welcome
    to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something,
    anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged example
    is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion.-a Please stop breathing those sauna fumes in Finland, and do your original research.-a Here is
    mine.

    -a https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been reconstruct-
    ions since.-a Now, if you want to /define/ a reconstruction as an invalid method of arguing on Usenet, I'll just have to tip my top hat to you,
    and insist you invent a time machine instead.

    The reconstruction is reasonble but it is impossible to verify every
    detail. But the mechanism is understood sufficiently well that the
    the purpose and idea can be understood. That a part of the writing on
    the machine has been read also helps.

    The remaining uncertainties are small and irrelevant to our discussion.

    Now, after that feat, how do you do this with a Turing machine?
    -aYou can obviously simulate the Antikythera mechanism with a Turing>
    machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.

    Let there be epsilon less than delta.-a Once you have constructed a simu- lation, I'll construct a level, and a fine bolt to adjust it.-a I believe I'll try for twenty thousand threads per inch.-a So the question is, can
    I nudge an arbitrary long lever, with a bolt -- hopefully starting at
    twenty thousand threads per inch -- finely enough, that each nudge fits within the smallest floating point precision you have -- I'm going to
    assume you were going to use double precision in C, REAL*8 in Fortran 77
    or f64 in Rust -- and you won't /see it/ because your simulation lacks
    real world precision?

    The topic was Turing computability. Particuar floating point limitations
    are irrelevant. Computability of real numbers means computability to any desired precision.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Mon Aug 31 12:55:40 2026
    From Newsgroup: comp.theory

    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. >>>>>>>>> yes i'm quite serious about refuting the church turing thesis. >>>>>>>>> i demonstrate how an idealized human agent can compute that >>>>>>>>> which is not turing computable.

    Is there any way to prove that humans can compute anyhing not >>>>>>>> Turing

    yes, i use the concept of an idealized human agent to compute a >>>>>>> function that is strictly outside the bounds of turing computability >>>>>>
    If you can't simulate that agent with a Turing-complete computer you >>>>>> cant use it for any computation. If you can you can compute the same >>>>>> with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You >>>> may be able to compute some values of an uncomputable function but you >>>> can't know that you can compute for arguments that will be given later >>>> unless you have a method.

    my paper specifically details how that method can exist, and how the
    algorithm differs from all the partial classifiers found in the
    turing computable space, and why no turing machine can truly
    implement the objective total algorithm even if it is mechanically
    computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by
    their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model directly
    to express algorithms, we use it as a fundamental basis for mechanical computation, but the way we discuss algorithms is far more high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not
    mean that the computation can be performed quickly enough. The theory
    of complexity of computation nees a different model.

    the only difference between the agent's algorithm and the partial classifiers that exist in turing machines, is that a partial classifier
    must deal with self-references, whereas the agent does not have to
    logically reckon about that because it's not possible to create a direct reference to computational process, again my paper will go into more
    detail here specifically

    Whether something is a self-reference is a matter of interpretation.
    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over
    the halting problem as excuse to not be proving correctness for every
    single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go
    about producing and maintaining computing infrastructure. the dumb
    fucking corpo ratrace to nowhere instead of producing the systems we
    not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof,
    which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably
    infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical
    relevant to algorithms?

    it's like trying to program a random turing machine to directly access
    it's own source code ... the information exists in abstract, but the
    turing machine model does not have a mechanical means of accessing it (barring a program implemented with a genuine quine, but those are exceptions stemming from programmatic solutions, not the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to arbitrarily access values from the machine that is simulating it...
    that's just not mechanically possible.

    The simulating machine can use any value it can access. But the process
    is not a simulation if those values are not present in the real thing
    the simulation itendes to simulate.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory,comp.lang.misc on Mon Aug 31 19:23:43 2026
    From Newsgroup: comp.theory

    On 31/08/2026 5:36 PM, Mikko wrote:
    On 31/08/2026 04:22, Johann 'Myrkraverk' Oskarsson wrote:
    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which is >>>>>> not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>> computable? Much can be computed with a Turing computable partial
    method.

    I previously gave this practical counter example, and you're welcome
    to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something, >>>> anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged example
    is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion.-a Please stop breathing
    those sauna fumes in Finland, and do your original research.-a Here is
    mine.

    -a-a https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been reconstruct-
    ions since.-a Now, if you want to /define/ a reconstruction as an invalid
    method of arguing on Usenet, I'll just have to tip my top hat to you,
    and insist you invent a time machine instead.

    The reconstruction is reasonble but it is impossible to verify every
    detail. But the mechanism is understood sufficiently well that the
    the purpose and idea can be understood. That a part of the writing on
    the machine has been read also helps.

    The remaining uncertainties are small and irrelevant to our discussion.

    Now, after that feat, how do you do this with a Turing machine?
    -aYou can obviously simulate the Antikythera mechanism with a
    Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.

    Let there be epsilon less than delta.-a Once you have constructed a simu-
    lation, I'll construct a level, and a fine bolt to adjust it.-a I believe
    I'll try for twenty thousand threads per inch.-a So the question is, can
    I nudge an arbitrary long lever, with a bolt -- hopefully starting at
    twenty thousand threads per inch -- finely enough, that each nudge fits
    within the smallest floating point precision you have -- I'm going to
    assume you were going to use double precision in C, REAL*8 in Fortran 77
    or f64 in Rust -- and you won't /see it/ because your simulation lacks
    real world precision?

    The topic was Turing computability. Particuar floating point limitations
    are irrelevant. Computability of real numbers means computability to any desired precision.


    Right, so you want to stick to that argument? Can you construct arbi-
    trary precision floating point library, and can I still create an arbi-
    trary long lever, with an arbitrary fine threaded bolt to push it, so
    that when you try to allocate more R.A.M. for the results, you panic
    because your tower of computation runs out of memory and forgets every-
    thing?

    I'm assuming you're going to write your simulator in Rust, being a duly anointed philosopher of a doctorate, I have no idea which, so I've added comp.lang.misc to this discussion, as comp.lang.rust is still being de-
    bated in news.groups.proposals.

    I will now await for you to finish said simulator, before I begin con- structing my very own mechanical shop of machinery, and /define/ myself
    as having won said argument until you show an actual working simulator
    I can then crash with a panic!


    Enjoy making the simulator in Rust!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory,comp.lang.misc on Mon Aug 31 07:33:34 2026
    From Newsgroup: comp.theory

    On 08/31/2026 04:23 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 31/08/2026 5:36 PM, Mikko wrote:
    On 31/08/2026 04:22, Johann 'Myrkraverk' Oskarsson wrote:
    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which
    is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>> computable? Much can be computed with a Turing computable partial
    method.

    I previously gave this practical counter example, and you're welcome >>>>> to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute something, >>>>> anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged example >>>> is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion. Please stop breathing
    those sauna fumes in Finland, and do your original research. Here is
    mine.

    https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been reconstruct- >>> ions since. Now, if you want to /define/ a reconstruction as an invalid >>> method of arguing on Usenet, I'll just have to tip my top hat to you,
    and insist you invent a time machine instead.

    The reconstruction is reasonble but it is impossible to verify every
    detail. But the mechanism is understood sufficiently well that the
    the purpose and idea can be understood. That a part of the writing on
    the machine has been read also helps.

    The remaining uncertainties are small and irrelevant to our discussion.

    Now, after that feat, how do you do this with a Turing machine?
    You can obviously simulate the Antikythera mechanism with a
    Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.

    Let there be epsilon less than delta. Once you have constructed a simu- >>> lation, I'll construct a level, and a fine bolt to adjust it. I believe >>> I'll try for twenty thousand threads per inch. So the question is, can
    I nudge an arbitrary long lever, with a bolt -- hopefully starting at
    twenty thousand threads per inch -- finely enough, that each nudge fits
    within the smallest floating point precision you have -- I'm going to
    assume you were going to use double precision in C, REAL*8 in Fortran 77 >>> or f64 in Rust -- and you won't /see it/ because your simulation lacks
    real world precision?

    The topic was Turing computability. Particuar floating point limitations
    are irrelevant. Computability of real numbers means computability to any
    desired precision.


    Right, so you want to stick to that argument? Can you construct arbi-
    trary precision floating point library, and can I still create an arbi-
    trary long lever, with an arbitrary fine threaded bolt to push it, so
    that when you try to allocate more R.A.M. for the results, you panic
    because your tower of computation runs out of memory and forgets every- thing?

    I'm assuming you're going to write your simulator in Rust, being a duly anointed philosopher of a doctorate, I have no idea which, so I've added comp.lang.misc to this discussion, as comp.lang.rust is still being de-
    bated in news.groups.proposals.

    I will now await for you to finish said simulator, before I begin con- structing my very own mechanical shop of machinery, and /define/ myself
    as having won said argument until you show an actual working simulator
    I can then crash with a panic!


    Enjoy making the simulator in Rust!

    "Interval arithmetic" is a usual sort of principled account
    with regards to "extended-precision arithmetic" that though
    mostly the "computer algebra systems" keep things formulaic
    throughout and only approximate numbers at the end.

    It's like when computing rotations in computer graphics,
    and there's a great account that matrix-manipulation the
    matrix-manipulation starts to have that 90-degree rotations
    start looking slightly off, i.e., it's relevant to getting
    things straight left-to-right and up-to-down, or according
    to the various coordinate and sign conventions or representations
    on a grid of picture-elements, that for simple accounts like
    vertical and horizontal lines on paper that making floating-point
    is graphically unsettling.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory,comp.lang.misc on Tue Sep 1 03:58:50 2026
    From Newsgroup: comp.theory

    On 31/08/2026 10:33 PM, Ross Finlayson wrote:
    On 08/31/2026 04:23 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 31/08/2026 5:36 PM, Mikko wrote:
    On 31/08/2026 04:22, Johann 'Myrkraverk' Oskarsson wrote:
    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>>>> i'm quite serious about refuting the church turing thesis. i
    demonstrate how an idealized human agent can compute that which >>>>>>>> is not turing computable.

    Is there any way to prove that humans can compute anyhing not Turing >>>>>>> computable? Much can be computed with a Turing computable partial >>>>>>> method.

    I previously gave this practical counter example, and you're welcome >>>>>> to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute
    something,
    anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged
    example
    is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion.-a Please stop breathing >>>> those sauna fumes in Finland, and do your original research.-a Here is >>>> mine.

    -a-a https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been
    reconstruct-
    ions since.-a Now, if you want to /define/ a reconstruction as an
    invalid
    method of arguing on Usenet, I'll just have to tip my top hat to you,
    and insist you invent a time machine instead.

    The reconstruction is reasonble but it is impossible to verify every
    detail. But the mechanism is understood sufficiently well that the
    the purpose and idea can be understood. That a part of the writing on
    the machine has been read also helps.

    The remaining uncertainties are small and irrelevant to our discussion.

    Now, after that feat, how do you do this with a Turing machine?
    You can obviously simulate the Antikythera mechanism with a
    Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute
    what the simulated machine can compute.

    Let there be epsilon less than delta.-a Once you have constructed a
    simu-
    lation, I'll construct a level, and a fine bolt to adjust it.-a I
    believe
    I'll try for twenty thousand threads per inch.-a So the question is, can >>>> I nudge an arbitrary long lever, with a bolt -- hopefully starting at
    twenty thousand threads per inch -- finely enough, that each nudge fits >>>> within the smallest floating point precision you have -- I'm going to
    assume you were going to use double precision in C, REAL*8 in
    Fortran 77
    or f64 in Rust -- and you won't /see it/ because your simulation lacks >>>> real world precision?

    The topic was Turing computability. Particuar floating point limitations >>> are irrelevant. Computability of real numbers means computability to any >>> desired precision.


    Right, so you want to stick to that argument?-a Can you construct arbi-
    trary precision floating point library, and can I still create an arbi-
    trary long lever, with an arbitrary fine threaded bolt to push it, so
    that when you try to allocate more R.A.M. for the results, you panic
    because your tower of computation runs out of memory and forgets every-
    thing?

    I'm assuming you're going to write your simulator in Rust, being a duly
    anointed philosopher of a doctorate, I have no idea which, so I've added
    comp.lang.misc to this discussion, as comp.lang.rust is still being de-
    bated in news.groups.proposals.

    I will now await for you to finish said simulator, before I begin con-
    structing my very own mechanical shop of machinery, and /define/ myself
    as having won said argument until you show an actual working simulator
    I can then crash with a panic!


    Enjoy making the simulator in Rust!

    "Interval arithmetic" is a usual sort of principled account
    with regards to "extended-precision arithmetic" that though
    mostly the "computer algebra systems" keep things formulaic
    throughout and only approximate numbers at the end.

    Do you mean to say that an /Antikythera mechanical simulator/
    can be done purely in algebraic terms, and does not need float-
    ing point at all?

    Wouldn't that simulator just run out of R.A.M. faster than arbi-
    trary precision floating point library?


    It's like when computing rotations in computer graphics,
    and there's a great account that matrix-manipulation the
    matrix-manipulation starts to have that 90-degree rotations
    start looking slightly off, i.e., it's relevant to getting
    things straight left-to-right and up-to-down, or according
    to the various coordinate and sign conventions or representations
    on a grid of picture-elements, that for simple accounts like
    vertical and horizontal lines on paper that making floating-point
    is graphically unsettling.



    I thought this was already solved in the 90s -- or earlier? -- by
    using quaternions instead of matrices for the rotations, and that
    it would remove the weird wobbling that comes from repeated calcu-
    lations of the rotation matrix?


    Please enlighten us on this subject!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Aug 31 14:35:08 2026
    From Newsgroup: comp.theory

    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. >>>>>>>>>> yes i'm quite serious about refuting the church turing thesis. >>>>>>>>>> i demonstrate how an idealized human agent can compute that >>>>>>>>>> which is not turing computable.

    Is there any way to prove that humans can compute anyhing not >>>>>>>>> Turing

    yes, i use the concept of an idealized human agent to compute a >>>>>>>> function that is strictly outside the bounds of turing
    computability

    If you can't simulate that agent with a Turing-complete computer you >>>>>>> cant use it for any computation. If you can you can compute the same >>>>>>> with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. You >>>>> may be able to compute some values of an uncomputable function but you >>>>> can't know that you can compute for arguments that will be given later >>>>> unless you have a method.

    my paper specifically details how that method can exist, and how the
    algorithm differs from all the partial classifiers found in the
    turing computable space, and why no turing machine can truly
    implement the objective total algorithm even if it is mechanically
    computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in
    turing machine constructions, which are inherently more limited by
    their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model
    directly to express algorithms, we use it as a fundamental basis for
    mechanical computation, but the way we discuss algorithms is far more
    high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not
    mean that the computation can be performed quickly enough. The theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm
    address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial
    classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does not
    have to logically reckon about that because it's not possible to
    create a direct reference to computational process, again my paper
    will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation.

    an true self-reference is not a matter of interpretation. for a running machine this is an exact copy of the source code for the running machine

    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping over
    the halting problem as excuse to not be proving correctness for
    every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go
    about producing and maintaining computing infrastructure. the dumb
    fucking corpo ratrace to nowhere instead of producing the systems we
    not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof, >>>>>> which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably >>>>> infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine access
    to it's own source code in order to function optimally

    while this can be implemented programmatically using a quine, it's not
    by default a mechanism of turing machines, so any random program does
    not have access to their own source code, only ones implemented with
    quines have definitive access to that. the rest struggle from a
    mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they have
    a programmatic solution they struggle from a what is a mechanical discontinuity


    it's like trying to program a random turing machine to directly access
    it's own source code ... the information exists in abstract, but the
    turing machine model does not have a mechanical means of accessing it
    (barring a program implemented with a genuine quine, but those are
    exceptions stemming from programmatic solutions, not the fundamental
    mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to
    arbitrarily access values from the machine that is simulating it...
    that's just not mechanically possible.

    The simulating machine can use any value it can access. But the process
    is not a simulation if those values are not present in the real thing
    the simulation itendes to simulate.


    the point is dude that this is an example of mechanical limitation. the information of the simulator exists during the simulation, but the
    simulation is mechanically incapable of having guaranteed access to it
    unless a programmatic solution of provided by the simulator
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory,comp.lang.misc on Mon Aug 31 20:22:59 2026
    From Newsgroup: comp.theory

    On 08/31/2026 12:58 PM, Johann 'Myrkraverk' Oskarsson wrote:
    On 31/08/2026 10:33 PM, Ross Finlayson wrote:
    On 08/31/2026 04:23 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 31/08/2026 5:36 PM, Mikko wrote:
    On 31/08/2026 04:22, Johann 'Myrkraverk' Oskarsson wrote:
    On 28/08/2026 3:21 PM, Mikko wrote:
    On 27/08/2026 14:46, Johann 'Myrkraverk' Oskarsson wrote:
    On 27/08/2026 3:49 PM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes >>>>>>>>> i'm quite serious about refuting the church turing thesis. i >>>>>>>>> demonstrate how an idealized human agent can compute that which >>>>>>>>> is not turing computable.

    Is there any way to prove that humans can compute anyhing not
    Turing
    computable? Much can be computed with a Turing computable partial >>>>>>>> method.

    I previously gave this practical counter example, and you're welcome >>>>>>> to prove me wrong.

    You pick up an Antikythera mechanism, and use it to compute
    something,
    anything.

    Unlikely, as the mechanism is not fylly known. Only one damaged
    example
    is known and there is no evicence that more was ever constructed.

    Dear Mikko,

    I'm afraid you're wading in error and confusion. Please stop
    breathing
    those sauna fumes in Finland, and do your original research. Here is >>>>> mine.

    https://www.antikytheramechanism.co.uk/category/all-products

    So, 1) the mechanism is fully known, 2) and there have been
    reconstruct-
    ions since. Now, if you want to /define/ a reconstruction as an
    invalid
    method of arguing on Usenet, I'll just have to tip my top hat to you, >>>>> and insist you invent a time machine instead.

    The reconstruction is reasonble but it is impossible to verify every
    detail. But the mechanism is understood sufficiently well that the
    the purpose and idea can be understood. That a part of the writing on
    the machine has been read also helps.

    The remaining uncertainties are small and irrelevant to our discussion. >>>>
    Now, after that feat, how do you do this with a Turing machine? >>>>>> > You can obviously simulate the Antikythera mechanism with a
    Turing> machine, but you cannot /compute/ as one.

    Simulation is enough. If one can simulate a machine one can compute >>>>>> what the simulated machine can compute.

    Let there be epsilon less than delta. Once you have constructed a
    simu-
    lation, I'll construct a level, and a fine bolt to adjust it. I
    believe
    I'll try for twenty thousand threads per inch. So the question is,
    can
    I nudge an arbitrary long lever, with a bolt -- hopefully starting at >>>>> twenty thousand threads per inch -- finely enough, that each nudge
    fits
    within the smallest floating point precision you have -- I'm going to >>>>> assume you were going to use double precision in C, REAL*8 in
    Fortran 77
    or f64 in Rust -- and you won't /see it/ because your simulation lacks >>>>> real world precision?

    The topic was Turing computability. Particuar floating point
    limitations
    are irrelevant. Computability of real numbers means computability to
    any
    desired precision.


    Right, so you want to stick to that argument? Can you construct arbi-
    trary precision floating point library, and can I still create an arbi-
    trary long lever, with an arbitrary fine threaded bolt to push it, so
    that when you try to allocate more R.A.M. for the results, you panic
    because your tower of computation runs out of memory and forgets every-
    thing?

    I'm assuming you're going to write your simulator in Rust, being a duly
    anointed philosopher of a doctorate, I have no idea which, so I've added >>> comp.lang.misc to this discussion, as comp.lang.rust is still being de-
    bated in news.groups.proposals.

    I will now await for you to finish said simulator, before I begin con-
    structing my very own mechanical shop of machinery, and /define/ myself
    as having won said argument until you show an actual working simulator
    I can then crash with a panic!


    Enjoy making the simulator in Rust!

    "Interval arithmetic" is a usual sort of principled account
    with regards to "extended-precision arithmetic" that though
    mostly the "computer algebra systems" keep things formulaic
    throughout and only approximate numbers at the end.

    Do you mean to say that an /Antikythera mechanical simulator/
    can be done purely in algebraic terms, and does not need float-
    ing point at all?

    Wouldn't that simulator just run out of R.A.M. faster than arbi-
    trary precision floating point library?


    It's like when computing rotations in computer graphics,
    and there's a great account that matrix-manipulation the
    matrix-manipulation starts to have that 90-degree rotations
    start looking slightly off, i.e., it's relevant to getting
    things straight left-to-right and up-to-down, or according
    to the various coordinate and sign conventions or representations
    on a grid of picture-elements, that for simple accounts like
    vertical and horizontal lines on paper that making floating-point
    is graphically unsettling.



    I thought this was already solved in the 90s -- or earlier? -- by
    using quaternions instead of matrices for the rotations, and that
    it would remove the weird wobbling that comes from repeated calcu-
    lations of the rotation matrix?


    Please enlighten us on this subject!


    I don't know that off-hand, it's an outstanding problem and well-known limitation of finite-element-analysis, and about the imprecision of
    floating points, and the incompleteness of rational arithmetic,
    about rational-algebras and radical-magmas.

    The gimbal-lock is an error mode in systems of gyroscopes, where
    for example "that did gyre and gimble in the wabe", whereas the
    quaternions don't suffer that themselves, and help avoid "lerps"
    and the like, then in the setting of where rotation-matrices are
    used to indicate usually in a wider setting the translation, rotation,
    and skew of the affine, or transformation-matrices in computer graphics,
    then usually providing rational rotations of multiples
    of pi/2 radians just involves constant cases since as arithmetic
    would accumulate its imprecision it would be off.

    Then, for seconds, days, and years, and clock-arithmetic, then
    a usual idea is that there are separate sorts time-keeping methods
    for each, then its similar for systems as would be like an analog
    computer that involves things like the _yenri_, which is a form
    of calculus from Japan that's about circles-within-circles as
    for epicycles and the like instead of the quadratic and the usual
    account of trapezoid rule and integration the the integral calculus,
    then usually the idea is to compute the time-of-day then draw the
    watch-hands, which in reality, actually tick on through a continuous
    sweep of motion.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Tue Sep 1 09:44:03 2026
    From Newsgroup: comp.theory

    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. >>>>>>>>>>> yes i'm quite serious about refuting the church turing
    thesis. i demonstrate how an idealized human agent can
    compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing not >>>>>>>>>> Turing

    yes, i use the concept of an idealized human agent to compute a >>>>>>>>> function that is strictly outside the bounds of turing
    computability

    If you can't simulate that agent with a Turing-complete computer >>>>>>>> you
    cant use it for any computation. If you can you can compute the >>>>>>>> same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing computable. >>>>>> You
    may be able to compute some values of an uncomputable function but >>>>>> you
    can't know that you can compute for arguments that will be given
    later
    unless you have a method.

    my paper specifically details how that method can exist, and how
    the algorithm differs from all the partial classifiers found in the >>>>> turing computable space, and why no turing machine can truly
    implement the objective total algorithm even if it is mechanically
    computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently in
    abstract from the more concrete mechanical implementations found in >>>>> turing machine constructions, which are inherently more limited by
    their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described.
    But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model
    directly to express algorithms, we use it as a fundamental basis for
    mechanical computation, but the way we discuss algorithms is far more
    high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not
    mean that the computation can be performed quickly enough. The theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm
    address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial
    classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does not
    have to logically reckon about that because it's not possible to
    create a direct reference to computational process, again my paper
    will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation.

    an true self-reference is not a matter of interpretation. for a running machine this is an exact copy of the source code for the running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great and
    incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping
    over the halting problem as excuse to not be proving correctness
    for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go
    about producing and maintaining computing infrastructure. the dumb
    fucking corpo ratrace to nowhere instead of producing the systems
    we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack thereof, >>>>>>> which can't be simulated by a turing machine because any value
    computed by a turing machine is necessarily addressable

    That has not been proven. There is no way to implement an uncountably >>>>>> infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine access
    to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing
    machines. They are never optimal.

    Ordinary computers perform quite well without any ability to access
    their own "source code".
    while this can be implemented programmatically using a quine, it's not
    by default a mechanism of turing machines, so any random program does
    not have access to their own source code, only ones implemented with
    quines have definitive access to that. the rest struggle from a
    mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they have
    a programmatic solution they struggle from a what is a mechanical discontinuity


    it's like trying to program a random turing machine to directly
    access it's own source code ... the information exists in abstract,
    but the turing machine model does not have a mechanical means of
    accessing it (barring a program implemented with a genuine quine, but
    those are exceptions stemming from programmatic solutions, not the
    fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to
    arbitrarily access values from the machine that is simulating it...
    that's just not mechanically possible.

    The simulating machine can use any value it can access. But the process
    is not a simulation if those values are not present in the real thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Tue Sep 1 12:50:33 2026
    From Newsgroup: comp.theory

    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>> it. yes i'm quite serious about refuting the church turing >>>>>>>>>>>> thesis. i demonstrate how an idealized human agent can >>>>>>>>>>>> compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing not >>>>>>>>>>> Turing

    yes, i use the concept of an idealized human agent to compute >>>>>>>>>> a function that is strictly outside the bounds of turing
    computability

    If you can't simulate that agent with a Turing-complete
    computer you
    cant use it for any computation. If you can you can compute the >>>>>>>>> same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two
    different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function
    but you
    can't know that you can compute for arguments that will be given >>>>>>> later
    unless you have a method.

    my paper specifically details how that method can exist, and how
    the algorithm differs from all the partial classifiers found in
    the turing computable space, and why no turing machine can truly
    implement the objective total algorithm even if it is mechanically >>>>>> computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently in >>>>>> abstract from the more concrete mechanical implementations found
    in turing machine constructions, which are inherently more limited >>>>>> by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described. >>>>> But there is no known way to describe an anlgorithm that cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model
    directly to express algorithms, we use it as a fundamental basis for
    mechanical computation, but the way we discuss algorithms is far
    more high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not
    mean that the computation can be performed quickly enough. The theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm
    address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial
    classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does
    not have to logically reckon about that because it's not possible to
    create a direct reference to computational process, again my paper
    will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation.

    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the exact transition table for the running machine

    sure the encoding is up to "interpretation", but given a specified (and correct) method of encoding machines, the self-reference is exact and
    not up to interpretation.

    i think we agree on this


    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great and >>>>>> incredibly useful. i'm trying to increase their productivity by
    resolving their limitations more accurately so we stop tripping
    over the halting problem as excuse to not be proving correctness
    for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go >>>>>> about producing and maintaining computing infrastructure. the dumb >>>>>> fucking corpo ratrace to nowhere instead of producing the systems >>>>>> we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing
    computability due to an issue of addressability, or lack
    thereof, which can't be simulated by a turing machine because >>>>>>>> any value computed by a turing machine is necessarily addressable >>>>>>>
    That has not been proven. There is no way to implement an
    uncountably
    infinite address space and any finite or countably infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway
    butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of circle-free machine)

    this maximal subset may be turing-complete, but i wouldn't expect you to accept that without reading the proof i have to yet to post.

    actually, even correctly deciding a less-than-maximal subset of turing machines requires a true self-reference


    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference

    while this can be implemented programmatically using a quine, it's not
    by default a mechanism of turing machines, so any random program does
    not have access to their own source code, only ones implemented with
    quines have definitive access to that. the rest struggle from a
    mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they
    have a programmatic solution they struggle from a what is a mechanical
    discontinuity


    it's like trying to program a random turing machine to directly
    access it's own source code ... the information exists in abstract,
    but the turing machine model does not have a mechanical means of
    accessing it (barring a program implemented with a genuine quine,
    but those are exceptions stemming from programmatic solutions, not
    the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to
    arbitrarily access values from the machine that is simulating it...
    that's just not mechanically possible.

    The simulating machine can use any value it can access. But the process
    is not a simulation if those values are not present in the real thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    but what i'm trying to convey is that a mechanical discontinuity happens
    when a computation run on a turing machine lacks a mechanism to directly access some specific information.

    i gave you two examples of where a lack of mechanism creates a
    mechanical discontinuity, and if u don't want to consider them then i
    cannot help you further here
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Wed Sep 2 11:04:21 2026
    From Newsgroup: comp.theory

    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>>> it. yes i'm quite serious about refuting the church turing >>>>>>>>>>>>> thesis. i demonstrate how an idealized human agent can >>>>>>>>>>>>> compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to compute >>>>>>>>>>> a function that is strictly outside the bounds of turing >>>>>>>>>>> computability

    If you can't simulate that agent with a Turing-complete
    computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function >>>>>>>> but you
    can't know that you can compute for arguments that will be given >>>>>>>> later
    unless you have a method.

    my paper specifically details how that method can exist, and how >>>>>>> the algorithm differs from all the partial classifiers found in >>>>>>> the turing computable space, and why no turing machine can truly >>>>>>> implement the objective total algorithm even if it is
    mechanically computable.

    You havn't posted a pointer to your article so we can't comment.
    But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently >>>>>>> in abstract from the more concrete mechanical implementations
    found in turing machine constructions, which are inherently more >>>>>>> limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be described. >>>>>> But there is no known way to describe an anlgorithm that cannot be >>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model
    directly to express algorithms, we use it as a fundamental basis
    for mechanical computation, but the way we discuss algorithms is
    far more high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not
    mean that the computation can be performed quickly enough. The theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm
    address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial
    classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does
    not have to logically reckon about that because it's not possible
    to create a direct reference to computational process, again my
    paper will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation.

    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running
    machine does not care and hardly knows whether the description is a self-descriptipn.

    sure the encoding is up to "interpretation", but given a specified (and correct) method of encoding machines, the self-reference is exact and
    not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    i think we agree on this


    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great and >>>>>>> incredibly useful. i'm trying to increase their productivity by >>>>>>> resolving their limitations more accurately so we stop tripping >>>>>>> over the halting problem as excuse to not be proving correctness >>>>>>> for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we go >>>>>>> about producing and maintaining computing infrastructure. the
    dumb fucking corpo ratrace to nowhere instead of producing the
    systems we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing >>>>>>>>> computability due to an issue of addressability, or lack
    thereof, which can't be simulated by a turing machine because >>>>>>>>> any value computed by a turing machine is necessarily addressable >>>>>>>>
    That has not been proven. There is no way to implement an
    uncountably
    infinite address space and any finite or countably infinite is >>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway >>>>>> butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of circle-free machine)

    Then you should use some other word. Words derived from "optimum" are understood to refer performance and resource consumption aspectes of computation.

    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect you to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference

    Not proven.

    while this can be implemented programmatically using a quine, it's
    not by default a mechanism of turing machines, so any random program
    does not have access to their own source code, only ones implemented
    with quines have definitive access to that. the rest struggle from a
    mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they
    have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly
    access it's own source code ... the information exists in abstract, >>>>> but the turing machine model does not have a mechanical means of
    accessing it (barring a program implemented with a genuine quine,
    but those are exceptions stemming from programmatic solutions, not
    the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to
    arbitrarily access values from the machine that is simulating it... >>>>> that's just not mechanically possible.

    The simulating machine can use any value it can access. But the process >>>> is not a simulation if those values are not present in the real thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    but what i'm trying to convey is that a mechanical discontinuity happens when a computation run on a turing machine lacks a mechanism to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    i gave you two examples of where a lack of mechanism creates a
    mechanical discontinuity, and if u don't want to consider them then i
    cannot help you further here
    Your examples were not clear. And examples are not very good for the
    purpose. Or at least, for a rough idea, you need counter-examples, too.
    But complete definitions are clearer.
    --
    Mikko

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Wed Sep 2 07:56:01 2026
    From Newsgroup: comp.theory

    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>>>> it. yes i'm quite serious about refuting the church turing >>>>>>>>>>>>>> thesis. i demonstrate how an idealized human agent can >>>>>>>>>>>>>> compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>> computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function >>>>>>>>> but you
    can't know that you can compute for arguments that will be
    given later
    unless you have a method.

    my paper specifically details how that method can exist, and how >>>>>>>> the algorithm differs from all the partial classifiers found in >>>>>>>> the turing computable space, and why no turing machine can truly >>>>>>>> implement the objective total algorithm even if it is
    mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>> But in this discussion you have posted no evidence that you can
    compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently >>>>>>>> in abstract from the more concrete mechanical implementations >>>>>>>> found in turing machine constructions, which are inherently more >>>>>>>> limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be
    described.
    But there is no known way to describe an anlgorithm that cannot be >>>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model
    directly to express algorithms, we use it as a fundamental basis
    for mechanical computation, but the way we discuss algorithms is
    far more high level

    Yes, a Turing machine is not a practical way of doing things. It is
    a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not >>>>> mean that the computation can be performed quickly enough. The theory >>>>> of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm
    address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial >>>>>> classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does >>>>>> not have to logically reckon about that because it's not possible >>>>>> to create a direct reference to computational process, again my
    paper will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation.

    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    machine does not care and hardly knows whether the description is a self-descriptipn.

    it matters for certain algos like partial semantic deciders that must be
    aware of when they are deciding on a self-reference


    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is exact
    and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not


    i think we agree on this


    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>> and incredibly useful. i'm trying to increase their productivity >>>>>>>> by resolving their limitations more accurately so we stop
    tripping over the halting problem as excuse to not be proving >>>>>>>> correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we >>>>>>>> go about producing and maintaining computing infrastructure. the >>>>>>>> dumb fucking corpo ratrace to nowhere instead of producing the >>>>>>>> systems we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing >>>>>>>>>> computability due to an issue of addressability, or lack
    thereof, which can't be simulated by a turing machine because >>>>>>>>>> any value computed by a turing machine is necessarily addressable >>>>>>>>>
    That has not been proven. There is no way to implement an
    uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a
    mechanical discontinuity, and i can only explain by properly
    describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway >>>>>>> butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical >>>>> relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of
    circle-free machine)

    Then you should use some other word. Words derived from "optimum" are understood to refer performance and resource consumption aspectes of computation.

    i explained my usage


    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect you
    to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of turing
    machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference

    Not proven.

    while this can be implemented programmatically using a quine, it's
    not by default a mechanism of turing machines, so any random program
    does not have access to their own source code, only ones implemented
    with quines have definitive access to that. the rest struggle from a
    mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they
    have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly
    access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a mechanical >>>>>> means of accessing it (barring a program implemented with a
    genuine quine, but those are exceptions stemming from programmatic >>>>>> solutions, not the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows
    the argument and that fully determines the value of the function.
    or it's like asking a turing machine being simulated by another to >>>>>> arbitrarily access values from the machine that is simulating
    it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the
    process
    is not a simulation if those values are not present in the real thing >>>>> the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine


    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a mechanism
    to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it. communication is a two
    way street dud, and if u don't accept ur half the responsibility i won't
    care to explain myself further to someone who doesn't care


    i gave you two examples of where a lack of mechanism creates a
    mechanical discontinuity, and if u don't want to consider them then i
    cannot help you further here
    Your examples were not clear. And examples are not very good for the
    purpose. Or at least, for a rough idea, you need counter-examples, too.
    But complete definitions are clearer.
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Thu Sep 3 11:06:41 2026
    From Newsgroup: comp.theory

    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>>>>> it. yes i'm quite serious about refuting the church >>>>>>>>>>>>>>> turing thesis. i demonstrate how an idealized human agent >>>>>>>>>>>>>>> can compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function >>>>>>>>>> but you
    can't know that you can compute for arguments that will be >>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and >>>>>>>>> how the algorithm differs from all the partial classifiers
    found in the turing computable space, and why no turing machine >>>>>>>>> can truly implement the objective total algorithm even if it is >>>>>>>>> mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently >>>>>>>>> in abstract from the more concrete mechanical implementations >>>>>>>>> found in turing machine constructions, which are inherently >>>>>>>>> more limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be
    described.
    But there is no known way to describe an anlgorithm that cannot be >>>>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model >>>>>>> directly to express algorithms, we use it as a fundamental basis >>>>>>> for mechanical computation, but the way we discuss algorithms is >>>>>>> far more high level

    Yes, a Turing machine is not a practical way of doing things. It is >>>>>> a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not >>>>>> mean that the computation can be performed quickly enough. The theory >>>>>> of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity.
    i'm address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial >>>>>>> classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does >>>>>>> not have to logically reckon about that because it's not possible >>>>>>> to create a direct reference to computational process, again my >>>>>>> paper will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation. >>>>>
    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a
    Turing machine, which is as unaccessible as self.

    A description does not refer to a partuclar machine. A description that describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that must be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is
    exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An
    uninterpreted string does not refer.

    i think we agree on this


    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>>> and incredibly useful. i'm trying to increase their
    productivity by resolving their limitations more accurately so >>>>>>>>> we stop tripping over the halting problem as excuse to not be >>>>>>>>> proving correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we >>>>>>>>> go about producing and maintaining computing infrastructure. >>>>>>>>> the dumb fucking corpo ratrace to nowhere instead of producing >>>>>>>>> the systems we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing >>>>>>>>>>> computability due to an issue of addressability, or lack >>>>>>>>>>> thereof, which can't be simulated by a turing machine because >>>>>>>>>>> any value computed by a turing machine is necessarily
    addressable

    That has not been proven. There is no way to implement an >>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous
    anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical >>>>>> relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of
    circle-free machine)

    Then you should use some other word. Words derived from "optimum" are
    understood to refer performance and resource consumption aspectes of
    computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could
    be better.

    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect you
    to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of
    turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference

    Not proven.

    while this can be implemented programmatically using a quine, it's
    not by default a mechanism of turing machines, so any random
    program does not have access to their own source code, only ones
    implemented with quines have definitive access to that. the rest
    struggle from a mechanical limitation, and that's the point of the
    example

    sure, many/most algos may not need it, but some do, and unless they >>>>> have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly >>>>>>> access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a mechanical >>>>>>> means of accessing it (barring a program implemented with a
    genuine quine, but those are exceptions stemming from
    programmatic solutions, not the fundamental mechanics of the
    machine)

    An algorithm cannot and need not access its "source code". It knows >>>>>> the argument and that fully determines the value of the function. >>>>>>> or it's like asking a turing machine being simulated by another >>>>>>> to arbitrarily access values from the machine that is simulating >>>>>>> it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the
    process
    is not a simulation if those values are not present in the real thing >>>>>> the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization
    omits unimprtant implementation details. It may avoid some constraints
    of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional restrictins that real computers have not. But neither restrictins are "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a mechanism
    to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    communication is a two way street

    Not always. A can read what for example Turing has written but I can't
    ask Turing about the exact meanings of his words. Unless you can write
    a preentation that can be understood by readers who can't or don't ask questions it doesn't matter whether you have discovered something. But
    if it is useful or otherwise interesting someone with better skills of presentation will discover it and publish.
    --
    Mikko

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Thu Sep 3 09:39:18 2026
    From Newsgroup: comp.theory

    On 9/3/26 1:06 AM, Mikko wrote:
    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda >>>>>>>>>>>>>>>> liking it. yes i'm quite serious about refuting the >>>>>>>>>>>>>>>> church turing thesis. i demonstrate how an idealized >>>>>>>>>>>>>>>> human agent can compute that which is not turing >>>>>>>>>>>>>>>> computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable
    function but you
    can't know that you can compute for arguments that will be >>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and >>>>>>>>>> how the algorithm differs from all the partial classifiers >>>>>>>>>> found in the turing computable space, and why no turing
    machine can truly implement the objective total algorithm even >>>>>>>>>> if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist
    independently in abstract from the more concrete mechanical >>>>>>>>>> implementations found in turing machine constructions, which >>>>>>>>>> are inherently more limited by their formally addressable nature. >>>>>>>>>
    THe concept of algorithm comtains that an algorithm can be
    described.
    But there is no known way to describe an anlgorithm that cannot be >>>>>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model >>>>>>>> directly to express algorithms, we use it as a fundamental basis >>>>>>>> for mechanical computation, but the way we discuss algorithms is >>>>>>>> far more high level

    Yes, a Turing machine is not a practical way of doing things. It is >>>>>>> a mathematicial model that is useful when one wants to probe that >>>>>>> some function is or is not computable. But being computable does not >>>>>>> mean that the computation can be performed quickly enough. The
    theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity.
    i'm address the theoretical domain of computability, not complexity >>>>>>

    the only difference between the agent's algorithm and the
    partial classifiers that exist in turing machines, is that a
    partial classifier must deal with self-references, whereas the >>>>>>>> agent does not have to logically reckon about that because it's >>>>>>>> not possible to create a direct reference to computational
    process, again my paper will go into more detail here specifically >>>>>>>
    Whether something is a self-reference is a matter of interpretation. >>>>>>
    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a
    Turing machine, which is as unaccessible as self.

    it's a copy (in some encoding) of the transition table the we use to
    define and then refer to a particular machine, and what it specifically computes. it's how machines reference to each other. it's how a machine
    can reference itself, including referencing any particular value it can computes


    A description does not refer to a partuclar machine. A description that describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that must
    be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    i never said it was trivial, just that it matters.


    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is
    exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An uninterpreted string does not refer.

    we can stick to handling one particular encoding of machines when it
    comes how to reckon about undecidability within computing.


    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>> actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>>>> and incredibly useful. i'm trying to increase their
    productivity by resolving their limitations more accurately so >>>>>>>>>> we stop tripping over the halting problem as excuse to not be >>>>>>>>>> proving correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we >>>>>>>>>> go about producing and maintaining computing infrastructure. >>>>>>>>>> the dumb fucking corpo ratrace to nowhere instead of producing >>>>>>>>>> the systems we not only need but deserve is just so ungodly >>>>>>>>>>

    the agent can compute something outside the bounds of turing >>>>>>>>>>>> computability due to an issue of addressability, or lack >>>>>>>>>>>> thereof, which can't be simulated by a turing machine >>>>>>>>>>>> because any value computed by a turing machine is
    necessarily addressable

    That has not been proven. There is no way to implement an >>>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous
    anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything
    mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine >>>>>> access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing >>>>> machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of
    circle-free machine)

    Then you should use some other word. Words derived from "optimum" are
    understood to refer performance and resource consumption aspectes of
    computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could
    be better.

    thank you for ur input


    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect
    you to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of
    turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference >>>
    Not proven.

    while this can be implemented programmatically using a quine, it's >>>>>> not by default a mechanism of turing machines, so any random
    program does not have access to their own source code, only ones
    implemented with quines have definitive access to that. the rest
    struggle from a mechanical limitation, and that's the point of the >>>>>> example

    sure, many/most algos may not need it, but some do, and unless
    they have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly >>>>>>>> access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a
    mechanical means of accessing it (barring a program implemented >>>>>>>> with a genuine quine, but those are exceptions stemming from
    programmatic solutions, not the fundamental mechanics of the
    machine)

    An algorithm cannot and need not access its "source code". It knows >>>>>>> the argument and that fully determines the value of the function. >>>>>>>> or it's like asking a turing machine being simulated by another >>>>>>>> to arbitrarily access values from the machine that is simulating >>>>>>>> it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the >>>>>>> process
    is not a simulation if those values are not present in the real >>>>>>> thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation. >>>>>
    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization

    yes it does. it has a head. and a tape. and various commands it can
    process in accordance with a transition table that then has mechanical
    effects on that head and tape. those are the mechanics of the idealized computing machine, and that's how i'm using the word

    i explained my usage

    omits unimprtant implementation details. It may avoid some constraints
    of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional restrictins that real computers have not. But neither restrictins are "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a mechanism
    to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    it can also be the consequence of bad listening, which is really quite
    endemic in online discussion


    communication is a two way street

    Not always. A can read what for example Turing has written but I can't
    ask Turing about the exact meanings of his words. Unless you can write
    a preentation that can be understood by readers who can't or don't ask questions it doesn't matter whether you have discovered something. But
    if it is useful or otherwise interesting someone with better skills of presentation will discover it and publish.


    jeez sentiments like that make me wonder if this god-forsaking species
    is even worthy of further progress tbh ...

    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a world floundering around in a rather asinine implementation of general
    computing that even remotely do what we need it do, to be frank
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Fri Sep 4 11:37:46 2026
    From Newsgroup: comp.theory

    On 03/09/2026 19:39, dart200 wrote:
    On 9/3/26 1:06 AM, Mikko wrote:
    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda >>>>>>>>>>>>>>>>> liking it. yes i'm quite serious about refuting the >>>>>>>>>>>>>>>>> church turing thesis. i demonstrate how an idealized >>>>>>>>>>>>>>>>> human agent can compute that which is not turing >>>>>>>>>>>>>>>>> computable.

    Is there any way to prove that humans can compute >>>>>>>>>>>>>>>> anyhing not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can >>>>>>>>>>>>>> compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>>>>> different ways, which in of itself has not be proven. >>>>>>>>>>>>
    There is no known method to compute what is not Turing >>>>>>>>>>>> computable. You
    may be able to compute some values of an uncomputable >>>>>>>>>>>> function but you
    can't know that you can compute for arguments that will be >>>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and >>>>>>>>>>> how the algorithm differs from all the partial classifiers >>>>>>>>>>> found in the turing computable space, and why no turing >>>>>>>>>>> machine can truly implement the objective total algorithm >>>>>>>>>>> even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as >>>>>>>>> "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist
    independently in abstract from the more concrete mechanical >>>>>>>>>>> implementations found in turing machine constructions, which >>>>>>>>>>> are inherently more limited by their formally addressable >>>>>>>>>>> nature.

    THe concept of algorithm comtains that an algorithm can be >>>>>>>>>> described.
    But there is no known way to describe an anlgorithm that
    cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine model >>>>>>>>> directly to express algorithms, we use it as a fundamental
    basis for mechanical computation, but the way we discuss
    algorithms is far more high level

    Yes, a Turing machine is not a practical way of doing things. It is >>>>>>>> a mathematicial model that is useful when one wants to probe that >>>>>>>> some function is or is not computable. But being computable does >>>>>>>> not
    mean that the computation can be performed quickly enough. The >>>>>>>> theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. >>>>>>> i'm address the theoretical domain of computability, not complexity >>>>>>>

    the only difference between the agent's algorithm and the
    partial classifiers that exist in turing machines, is that a >>>>>>>>> partial classifier must deal with self-references, whereas the >>>>>>>>> agent does not have to logically reckon about that because it's >>>>>>>>> not possible to create a direct reference to computational
    process, again my paper will go into more detail here specifically >>>>>>>>
    Whether something is a self-reference is a matter of
    interpretation.

    an true self-reference is not a matter of interpretation. for a >>>>>>> running machine this is an exact copy of the source code for the >>>>>>> running machine

    Whithout any interpretation there are no references, only synbols. >>>>>> Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a
    Turing machine, which is as unaccessible as self.

    it's a copy (in some encoding) of the transition table the we use to
    define and then refer to a particular machine, and what it specifically computes.

    The same behaviour can be presented with different transition tables in
    the same language. Trivial changes include the order of the rules and
    the naming of the states. In addition tape symbols that are not used for
    input nor output can be replaced. THerefore it is not tirivial to
    determine whether the table describes self. And in any case, it does not
    refer to self instead of a similar one as both are described by the same
    table.

    it's how machines reference to each other. it's how a machine
    can reference itself, including referencing any particular value it can computes

    Machines can describe themselves or other machines but a description
    is not a reference: another machine similar to self is not self but
    is described by the same description.

    A description does not refer to a partuclar machine. A description that
    describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that must
    be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    i never said it was trivial, just that it matters.

    You never proved that it is possible.

    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is
    exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An
    uninterpreted string does not refer.

    we can stick to handling one particular encoding of machines when it
    comes how to reckon about undecidability within computing.

    Does it matter that a problem can be solvable if presented one way
    but unsolvable if preneted in another way?

    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>>> actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>>>>> and incredibly useful. i'm trying to increase their
    productivity by resolving their limitations more accurately >>>>>>>>>>> so we stop tripping over the halting problem as excuse to not >>>>>>>>>>> be proving correctness for every single program we deploy... >>>>>>>>>>>
    no, testing isn't good enough bro, nor is the braindead way >>>>>>>>>>> we go about producing and maintaining computing
    infrastructure. the dumb fucking corpo ratrace to nowhere >>>>>>>>>>> instead of producing the systems we not only need but deserve >>>>>>>>>>> is just so ungodly


    the agent can compute something outside the bounds of >>>>>>>>>>>>> turing computability due to an issue of addressability, or >>>>>>>>>>>>> lack thereof, which can't be simulated by a turing machine >>>>>>>>>>>>> because any value computed by a turing machine is
    necessarily addressable

    That has not been proven. There is no way to implement an >>>>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous >>>>>>>>>> anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything
    mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine >>>>>>> access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing >>>>>> machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of >>>>> circle-free machine)

    Then you should use some other word. Words derived from "optimum" are
    understood to refer performance and resource consumption aspectes of
    computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could
    be better.

    thank you for ur input

    You are welcome.

    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect
    you to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of
    turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access >>>>>> their own "source code".

    sure, the point is there exist some algos that require a self-
    reference

    Not proven.

    while this can be implemented programmatically using a quine,
    it's not by default a mechanism of turing machines, so any random >>>>>>> program does not have access to their own source code, only ones >>>>>>> implemented with quines have definitive access to that. the rest >>>>>>> struggle from a mechanical limitation, and that's the point of
    the example

    sure, many/most algos may not need it, but some do, and unless
    they have a programmatic solution they struggle from a what is a >>>>>>> mechanical discontinuity


    it's like trying to program a random turing machine to directly >>>>>>>>> access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a
    mechanical means of accessing it (barring a program implemented >>>>>>>>> with a genuine quine, but those are exceptions stemming from >>>>>>>>> programmatic solutions, not the fundamental mechanics of the >>>>>>>>> machine)

    An algorithm cannot and need not access its "source code". It knows >>>>>>>> the argument and that fully determines the value of the function. >>>>>>>>> or it's like asking a turing machine being simulated by another >>>>>>>>> to arbitrarily access values from the machine that is
    simulating it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the >>>>>>>> process
    is not a simulation if those values are not present in the real >>>>>>>> thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation. >>>>>>
    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization

    yes it does. it has a head. and a tape. and various commands it can
    process in accordance with a transition table that then has mechanical effects on that head and tape. those are the mechanics of the idealized computing machine, and that's how i'm using the word

    Those are mathematical descriptions. Perhaps you mean systematic?
    i explained my usage

    omits unimprtant implementation details. It may avoid some constraints
    of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional
    restrictins that real computers have not. But neither restrictins are
    "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a
    mechanism to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    it can also be the consequence of bad listening, which is really quite endemic in online discussion

    In case of bad listening the cause and consequences are on the same side
    so the other side needn't care.

    communication is a two way street

    Not always. A can read what for example Turing has written but I can't
    ask Turing about the exact meanings of his words. Unless you can write
    a preentation that can be understood by readers who can't or don't ask
    questions it doesn't matter whether you have discovered something. But
    if it is useful or otherwise interesting someone with better skills of
    presentation will discover it and publish.

    jeez sentiments like that make me wonder if this god-forsaking species
    is even worthy of further progress tbh ...

    Worthy or not, it is able.

    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a world floundering around in a rather asinine implementation of general
    computing that even remotely do what we need it do, to be frank
    --
    Mikko

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.theory on Fri Sep 4 16:57:48 2026
    From Newsgroup: comp.theory

    On 04/09/2026 12:39 AM, dart200 wrote:


    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a world floundering around in a rather asinine implementation of general
    computing that even remotely do what we need it do, to be frank

    And I wish you great success with it. Turing machine supremacy needs to
    end. After all, Alan Turing screwed up greatly when he coined the
    Turing Test. Not with the test itself, nor the machines, but with folk,
    and how they tend to anthropomorphize the machines when they behave even remotely like a person.

    The Turing Machine, while useful, has some serious drawbacks, and that's unrelated to the Antikythera mechanism I keep bringing up. After all,
    it's just a method of analogue computing using gears instead of elec-
    tricity.

    And don't stop there, please continue with your endeavours [sic], and
    implement a non-turing machine for the rest of use to marvel at.


    Now go forth and conquer the world!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Fri Sep 4 12:39:11 2026
    From Newsgroup: comp.theory

    On 9/4/26 1:37 AM, Mikko wrote:
    On 03/09/2026 19:39, dart200 wrote:
    On 9/3/26 1:06 AM, Mikko wrote:
    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda >>>>>>>>>>>>>>>>>> liking it. yes i'm quite serious about refuting the >>>>>>>>>>>>>>>>>> church turing thesis. i demonstrate how an idealized >>>>>>>>>>>>>>>>>> human agent can compute that which is not turing >>>>>>>>>>>>>>>>>> computable.

    Is there any way to prove that humans can compute >>>>>>>>>>>>>>>>> anyhing not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>>>> compute a function that is strictly outside the bounds >>>>>>>>>>>>>>>> of turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can >>>>>>>>>>>>>>> compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in >>>>>>>>>>>>>> two different ways, which in of itself has not be proven. >>>>>>>>>>>>>
    There is no known method to compute what is not Turing >>>>>>>>>>>>> computable. You
    may be able to compute some values of an uncomputable >>>>>>>>>>>>> function but you
    can't know that you can compute for arguments that will be >>>>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and >>>>>>>>>>>> how the algorithm differs from all the partial classifiers >>>>>>>>>>>> found in the turing computable space, and why no turing >>>>>>>>>>>> machine can truly implement the objective total algorithm >>>>>>>>>>>> even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as >>>>>>>>>> "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist
    independently in abstract from the more concrete mechanical >>>>>>>>>>>> implementations found in turing machine constructions, which >>>>>>>>>>>> are inherently more limited by their formally addressable >>>>>>>>>>>> nature.

    THe concept of algorithm comtains that an algorithm can be >>>>>>>>>>> described.
    But there is no known way to describe an anlgorithm that >>>>>>>>>>> cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine >>>>>>>>>> model directly to express algorithms, we use it as a
    fundamental basis for mechanical computation, but the way we >>>>>>>>>> discuss algorithms is far more high level

    Yes, a Turing machine is not a practical way of doing things. >>>>>>>>> It is
    a mathematicial model that is useful when one wants to probe that >>>>>>>>> some function is or is not computable. But being computable >>>>>>>>> does not
    mean that the computation can be performed quickly enough. The >>>>>>>>> theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. >>>>>>>> i'm address the theoretical domain of computability, not complexity >>>>>>>>

    the only difference between the agent's algorithm and the >>>>>>>>>> partial classifiers that exist in turing machines, is that a >>>>>>>>>> partial classifier must deal with self-references, whereas the >>>>>>>>>> agent does not have to logically reckon about that because >>>>>>>>>> it's not possible to create a direct reference to
    computational process, again my paper will go into more detail >>>>>>>>>> here specifically

    Whether something is a self-reference is a matter of
    interpretation.

    an true self-reference is not a matter of interpretation. for a >>>>>>>> running machine this is an exact copy of the source code for the >>>>>>>> running machine

    Whithout any interpretation there are no references, only synbols. >>>>>>> Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the >>>>>> exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a
    Turing machine, which is as unaccessible as self.

    it's a copy (in some encoding) of the transition table the we use to
    define and then refer to a particular machine, and what it
    specifically computes.

    The same behaviour can be presented with different transition tables in

    those are different machines even if they have the same behavior.
    machine identity is defined by the /exact/ same transition table.

    i get that machine equivalence can be tricky, but let me define some
    language to specify the various relations:

    identical/self-equivalence: this is when two descriptions are the
    /exact/ same transition table and therefore the same string

    isomorphic equivalence: this is when two machines may not have the same transition table, but produce the /exact/ same series of steps in the computations they produce. to be more precise because for example state
    names can still differ between isomorphic machines, i define this more precisely as the same output bits being written at the same steps in the computation.

    functional/turing equivalence: this is when two machines produce the
    same output even if not thru the exact same series of steps.

    to clarify how "output" is defined here for turing machines (which can
    just write to a tape), i'm reusing turing's convention from his paper:
    the tape is programmatically divided into cells of F-cells and E-cells. F-cells are write only, done so in order, and consist of the defined
    "output" for what the machine is computing. E-cells are for all the
    temporary tape state that is not the direct output of the machine.
    turing wrote the very first turing machine description with this
    convention in mind.

    the same language. Trivial changes include the order of the rules and
    the naming of the states. In addition tape symbols that are not used for input nor output can be replaced. THerefore it is not tirivial to
    determine whether the table describes self. And in any case, it does not refer to self instead of a similar one as both are described by the same table.

    it's how machines reference to each other. it's how a machine can
    reference itself, including referencing any particular value it can
    computes

    Machines can describe themselves or other machines but a description
    is not a reference: another machine similar to self is not self but
    is described by the same description.

    u seem to be arguing that self-references don't actually exist... uhhh
    ok, i don't care for things that don't actually exist, so i'm not going
    to use a label for them

    i'm using the term self-reference to label when a machines are referring
    to their own exact description, as that description is semantically
    equivalent when simulated within another machine as it is when run on
    it's own. idk why ur arguing about this, it seems kinda pointless.

    classic usenet, eh???


    A description does not refer to a partuclar machine. A description that
    describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that
    must be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    i never said it was trivial, just that it matters.

    You never proved that it is possible.

    sure the encoding is up to "interpretation", but given a specified >>>>>> (and correct) method of encoding machines, the self-reference is
    exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An
    uninterpreted string does not refer.

    we can stick to handling one particular encoding of machines when it
    comes how to reckon about undecidability within computing.

    Does it matter that a problem can be solvable if presented one way
    but unsolvable if preneted in another way?

    because all turing-computable sequences can be found computed by some
    machine within the total enumeration of all machines in a single turing-complete language, and therefore covers everything that is
    possibly computable by a turing machine

    are there infinite ways of expressing that same thing becuase there are infinite ways of encoding turing machines? sure, but the point is
    addressing undecidability within a complete expression of everything
    that is computable, not trying to address the complexity involved with translating the infinite ways of expressing the same thing

    those are different issues and i'm addressing the undecidability part,
    not the translation part. and yes you'll prolly keep insisting it
    matters but when enumerating over all machines, it is only necessary to
    do so in one turing-complete language. we do this so it's possible to
    grasp at what exactly are the limits of computability. throwing a bunch
    of arbitrarily complexity in there muddles the more fundamental issue
    and makes it unreasonable to reckon about ... and therefore is counter productive


    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>>>> actions.

    this isn't like a bad thing either, turing machines are >>>>>>>>>>>> great and incredibly useful. i'm trying to increase their >>>>>>>>>>>> productivity by resolving their limitations more accurately >>>>>>>>>>>> so we stop tripping over the halting problem as excuse to >>>>>>>>>>>> not be proving correctness for every single program we >>>>>>>>>>>> deploy...

    no, testing isn't good enough bro, nor is the braindead way >>>>>>>>>>>> we go about producing and maintaining computing
    infrastructure. the dumb fucking corpo ratrace to nowhere >>>>>>>>>>>> instead of producing the systems we not only need but >>>>>>>>>>>> deserve is just so ungodly


    the agent can compute something outside the bounds of >>>>>>>>>>>>>> turing computability due to an issue of addressability, or >>>>>>>>>>>>>> lack thereof, which can't be simulated by a turing machine >>>>>>>>>>>>>> because any value computed by a turing machine is >>>>>>>>>>>>>> necessarily addressable

    That has not been proven. There is no way to implement an >>>>>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous >>>>>>>>>>> anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything
    mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs
    genuine access to it's own source code in order to function
    optimally

    If you want to talk about optimization you must not talk about
    Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to >>>>>> optimal functionality, ei deciding some maximal subset of machines >>>>>> within a given semantic set (like set of halting machine, or set
    of circle-free machine)

    Then you should use some other word. Words derived from "optimum" are >>>>> understood to refer performance and resource consumption aspectes of >>>>> computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could
    be better.

    thank you for ur input

    You are welcome.

    There are problems where every partial algorithm fails to compute for >>>>> some argument that another partial agorithm computes. One example is >>>>> the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect >>>>>> you to accept that without reading the proof i have to yet to post. >>>>>
    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of
    turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access >>>>>>> their own "source code".

    sure, the point is there exist some algos that require a self-
    reference

    Not proven.

    while this can be implemented programmatically using a quine, >>>>>>>> it's not by default a mechanism of turing machines, so any
    random program does not have access to their own source code, >>>>>>>> only ones implemented with quines have definitive access to
    that. the rest struggle from a mechanical limitation, and that's >>>>>>>> the point of the example

    sure, many/most algos may not need it, but some do, and unless >>>>>>>> they have a programmatic solution they struggle from a what is a >>>>>>>> mechanical discontinuity


    it's like trying to program a random turing machine to
    directly access it's own source code ... the information
    exists in abstract, but the turing machine model does not have >>>>>>>>>> a mechanical means of accessing it (barring a program
    implemented with a genuine quine, but those are exceptions >>>>>>>>>> stemming from programmatic solutions, not the fundamental >>>>>>>>>> mechanics of the machine)

    An algorithm cannot and need not access its "source code". It >>>>>>>>> knows
    the argument and that fully determines the value of the function. >>>>>>>>>> or it's like asking a turing machine being simulated by
    another to arbitrarily access values from the machine that is >>>>>>>>>> simulating it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the >>>>>>>>> process
    is not a simulation if those values are not present in the real >>>>>>>>> thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation. >>>>>>>
    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world >>>>> whereas "algorithm" refers to a mathematical concept. The real world >>>>> does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization

    yes it does. it has a head. and a tape. and various commands it can
    process in accordance with a transition table that then has mechanical
    effects on that head and tape. those are the mechanics of the
    idealized computing machine, and that's how i'm using the word

    Those are mathematical descriptions. Perhaps you mean systematic?

    i call it a mechanical discontinuity because of a lack of specified
    mechanism within the mathematical model

    i explained my usage

    omits unimprtant implementation details. It may avoid some constraints
    of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional
    restrictins that real computers have not. But neither restrictins are
    "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a
    mechanism to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    it can also be the consequence of bad listening, which is really quite
    endemic in online discussion

    In case of bad listening the cause and consequences are on the same side
    so the other side needn't care.

    i'm definitely affects, however indirectly, by all the ignorance
    sustained thru poor listening skills


    communication is a two way street

    Not always. A can read what for example Turing has written but I can't
    ask Turing about the exact meanings of his words. Unless you can write
    a preentation that can be understood by readers who can't or don't ask
    questions it doesn't matter whether you have discovered something. But
    if it is useful or otherwise interesting someone with better skills of
    presentation will discover it and publish.

    jeez sentiments like that make me wonder if this god-forsaking species
    is even worthy of further progress tbh ...

    Worthy or not, it is able.

    growth isn't the same thing as progress


    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a
    world floundering around in a rather asinine implementation of general
    computing that even remotely do what we need it do, to be frank

    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Fri Sep 4 22:44:32 2026
    From Newsgroup: comp.theory

    On 9/4/26 12:39 PM, dart200 wrote:
    On 9/4/26 1:37 AM, Mikko wrote:
    On 03/09/2026 19:39, dart200 wrote:
    On 9/3/26 1:06 AM, Mikko wrote:
    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda >>>>>>>>>>>>>>>>>>> liking it. yes i'm quite serious about refuting the >>>>>>>>>>>>>>>>>>> church turing thesis. i demonstrate how an idealized >>>>>>>>>>>>>>>>>>> human agent can compute that which is not turing >>>>>>>>>>>>>>>>>>> computable.

    Is there any way to prove that humans can compute >>>>>>>>>>>>>>>>>> anyhing not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>>>>> compute a function that is strictly outside the bounds >>>>>>>>>>>>>>>>> of turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can >>>>>>>>>>>>>>>> compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in >>>>>>>>>>>>>>> two different ways, which in of itself has not be proven. >>>>>>>>>>>>>>
    There is no known method to compute what is not Turing >>>>>>>>>>>>>> computable. You
    may be able to compute some values of an uncomputable >>>>>>>>>>>>>> function but you
    can't know that you can compute for arguments that will be >>>>>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, >>>>>>>>>>>>> and how the algorithm differs from all the partial
    classifiers found in the turing computable space, and why >>>>>>>>>>>>> no turing machine can truly implement the objective total >>>>>>>>>>>>> algorithm even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't >>>>>>>>>>>> comment.
    But in this discussion you have posted no evidence that you can >>>>>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as >>>>>>>>>>> "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist
    independently in abstract from the more concrete mechanical >>>>>>>>>>>>> implementations found in turing machine constructions, >>>>>>>>>>>>> which are inherently more limited by their formally >>>>>>>>>>>>> addressable nature.

    THe concept of algorithm comtains that an algorithm can be >>>>>>>>>>>> described.
    But there is no known way to describe an anlgorithm that >>>>>>>>>>>> cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine >>>>>>>>>>> model directly to express algorithms, we use it as a
    fundamental basis for mechanical computation, but the way we >>>>>>>>>>> discuss algorithms is far more high level

    Yes, a Turing machine is not a practical way of doing things. >>>>>>>>>> It is
    a mathematicial model that is useful when one wants to probe that >>>>>>>>>> some function is or is not computable. But being computable >>>>>>>>>> does not
    mean that the computation can be performed quickly enough. The >>>>>>>>>> theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs
    complexity. i'm address the theoretical domain of
    computability, not complexity


    the only difference between the agent's algorithm and the >>>>>>>>>>> partial classifiers that exist in turing machines, is that a >>>>>>>>>>> partial classifier must deal with self-references, whereas >>>>>>>>>>> the agent does not have to logically reckon about that
    because it's not possible to create a direct reference to >>>>>>>>>>> computational process, again my paper will go into more >>>>>>>>>>> detail here specifically

    Whether something is a self-reference is a matter of
    interpretation.

    an true self-reference is not a matter of interpretation. for a >>>>>>>>> running machine this is an exact copy of the source code for >>>>>>>>> the running machine

    Whithout any interpretation there are no references, only synbols. >>>>>>>> Without references there are no self-references.

    a self-reference is a finite length value of data that encodes
    the exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running >>>>>
    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a >>>> Turing machine, which is as unaccessible as self.

    it's a copy (in some encoding) of the transition table the we use to
    define and then refer to a particular machine, and what it
    specifically computes.

    The same behaviour can be presented with different transition tables in

    those are different machines even if they have the same behavior.
    machine identity is defined by the /exact/ same transition table.

    i get that machine equivalence can be tricky, but let me define some language to specify the various relations:

    identical/self-equivalence: this is when two descriptions are the /
    exact/ same transition table and therefore the same string

    isomorphic equivalence: this is when two machines may not have the same transition table, but produce the /exact/ same series of steps in the computations they produce. to be more precise because for example state names can still differ between isomorphic machines, i define this more precisely as the same output bits being written at the same steps in the computation.

    functional/turing equivalence: this is when two machines produce the
    same output even if not thru the exact same series of steps.

    to clarify how "output" is defined here for turing machines (which can
    just write to a tape), i'm reusing turing's convention from his paper:
    the tape is programmatically divided into cells of F-cells and E-cells. F-cells are write only, done so in order, and consist of the defined "output" for what the machine is computing. E-cells are for all the temporary tape state that is not the direct output of the machine.
    turing wrote the very first turing machine description with this
    convention in mind.

    the same language. Trivial changes include the order of the rules and
    the naming of the states. In addition tape symbols that are not used for
    input nor output can be replaced. THerefore it is not tirivial to
    determine whether the table describes self. And in any case, it does not
    refer to self instead of a similar one as both are described by the same
    table.

    it's how machines reference to each other. it's how a machine can
    reference itself, including referencing any particular value it can
    computes

    Machines can describe themselves or other machines but a description
    is not a reference: another machine similar to self is not self but
    is described by the same description.

    u seem to be arguing that self-references don't actually exist... uhhh
    ok, i don't care for things that don't actually exist, so i'm not going
    to use a label for them

    i'm using the term self-reference to label when a machines are referring
    to their own exact description, as that description is semantically equivalent when simulated within another machine as it is when run on
    it's own. idk why ur arguing about this, it seems kinda pointless.

    for more information on the possibility of self-referential machines,
    please do read the wikipedia section on kleene's 2nd recursion theorem:

    https://en.wikipedia.org/wiki/Kleene%27s_recursion_theorem#Kleene's_second_recursion_theorem


    classic usenet, eh???


    A description does not refer to a partuclar machine. A description that >>>> describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a >>>>>> self-descriptipn.

    it matters for certain algos like partial semantic deciders that
    must be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    i never said it was trivial, just that it matters.

    You never proved that it is possible.

    sure the encoding is up to "interpretation", but given a
    specified (and correct) method of encoding machines, the self-
    reference is exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An
    uninterpreted string does not refer.

    we can stick to handling one particular encoding of machines when it
    comes how to reckon about undecidability within computing.

    Does it matter that a problem can be solvable if presented one way
    but unsolvable if preneted in another way?

    because all turing-computable sequences can be found computed by some machine within the total enumeration of all machines in a single turing- complete language, and therefore covers everything that is possibly computable by a turing machine

    are there infinite ways of expressing that same thing becuase there are infinite ways of encoding turing machines? sure, but the point is
    addressing undecidability within a complete expression of everything
    that is computable, not trying to address the complexity involved with translating the infinite ways of expressing the same thing

    those are different issues and i'm addressing the undecidability part,
    not the translation part. and yes you'll prolly keep insisting it
    matters but when enumerating over all machines, it is only necessary to
    do so in one turing-complete language. we do this so it's possible to
    grasp at what exactly are the limits of computability. throwing a bunch
    of arbitrarily complexity in there muddles the more fundamental issue
    and makes it unreasonable to reckon about ... and therefore is counter productive


    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>>>>> actions.

    this isn't like a bad thing either, turing machines are >>>>>>>>>>>>> great and incredibly useful. i'm trying to increase their >>>>>>>>>>>>> productivity by resolving their limitations more accurately >>>>>>>>>>>>> so we stop tripping over the halting problem as excuse to >>>>>>>>>>>>> not be proving correctness for every single program we >>>>>>>>>>>>> deploy...

    no, testing isn't good enough bro, nor is the braindead way >>>>>>>>>>>>> we go about producing and maintaining computing
    infrastructure. the dumb fucking corpo ratrace to nowhere >>>>>>>>>>>>> instead of producing the systems we not only need but >>>>>>>>>>>>> deserve is just so ungodly


    the agent can compute something outside the bounds of >>>>>>>>>>>>>>> turing computability due to an issue of addressability, >>>>>>>>>>>>>>> or lack thereof, which can't be simulated by a turing >>>>>>>>>>>>>>> machine because any value computed by a turing machine is >>>>>>>>>>>>>>> necessarily addressable

    That has not been proven. There is no way to implement an >>>>>>>>>>>>>> uncountably
    infinite address space and any finite or countably >>>>>>>>>>>>>> infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's >>>>>>>>>>>>> a mechanical discontinuity, and i can only explain by >>>>>>>>>>>>> properly describing the justifying thought experiment >>>>>>>>>>>>
    A finite or countable address space is fully discontinuous >>>>>>>>>>>> anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one >>>>>>>>>>
    What does "mechanical discontinuity" mean? How is anything >>>>>>>>>> mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs
    genuine access to it's own source code in order to function >>>>>>>>> optimally

    If you want to talk about optimization you must not talk about >>>>>>>> Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to >>>>>>> optimal functionality, ei deciding some maximal subset of
    machines within a given semantic set (like set of halting
    machine, or set of circle-free machine)

    Then you should use some other word. Words derived from "optimum" are >>>>>> understood to refer performance and resource consumption aspectes of >>>>>> computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could >>>> be better.

    thank you for ur input

    You are welcome.

    There are problems where every partial algorithm fails to compute for >>>>>> some argument that another partial agorithm computes. One example is >>>>>> the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect >>>>>>> you to accept that without reading the proof i have to yet to post. >>>>>>
    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of >>>>>>> turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access >>>>>>>> their own "source code".

    sure, the point is there exist some algos that require a self-
    reference

    Not proven.

    while this can be implemented programmatically using a quine, >>>>>>>>> it's not by default a mechanism of turing machines, so any
    random program does not have access to their own source code, >>>>>>>>> only ones implemented with quines have definitive access to >>>>>>>>> that. the rest struggle from a mechanical limitation, and
    that's the point of the example

    sure, many/most algos may not need it, but some do, and unless >>>>>>>>> they have a programmatic solution they struggle from a what is >>>>>>>>> a mechanical discontinuity


    it's like trying to program a random turing machine to
    directly access it's own source code ... the information >>>>>>>>>>> exists in abstract, but the turing machine model does not >>>>>>>>>>> have a mechanical means of accessing it (barring a program >>>>>>>>>>> implemented with a genuine quine, but those are exceptions >>>>>>>>>>> stemming from programmatic solutions, not the fundamental >>>>>>>>>>> mechanics of the machine)

    An algorithm cannot and need not access its "source code". It >>>>>>>>>> knows
    the argument and that fully determines the value of the function. >>>>>>>>>>> or it's like asking a turing machine being simulated by >>>>>>>>>>> another to arbitrarily access values from the machine that is >>>>>>>>>>> simulating it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But >>>>>>>>>> the process
    is not a simulation if those values are not present in the >>>>>>>>>> real thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical
    limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world >>>>>> whereas "algorithm" refers to a mathematical concept. The real world >>>>>> does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization >>>
    yes it does. it has a head. and a tape. and various commands it can
    process in accordance with a transition table that then has
    mechanical effects on that head and tape. those are the mechanics of
    the idealized computing machine, and that's how i'm using the word

    Those are mathematical descriptions. Perhaps you mean systematic?

    i call it a mechanical discontinuity because of a lack of specified mechanism within the mathematical model

    i explained my usage

    omits unimprtant implementation details. It may avoid some constraints >>>> of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional
    restrictins that real computers have not. But neither restrictins are
    "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity >>>>>>> happens when a computation run on a turing machine lacks a
    mechanism to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    it can also be the consequence of bad listening, which is really
    quite endemic in online discussion

    In case of bad listening the cause and consequences are on the same side
    so the other side needn't care.

    i'm definitely affects, however indirectly, by all the ignorance
    sustained thru poor listening skills


    communication is a two way street

    Not always. A can read what for example Turing has written but I can't >>>> ask Turing about the exact meanings of his words. Unless you can write >>>> a preentation that can be understood by readers who can't or don't ask >>>> questions it doesn't matter whether you have discovered something. But >>>> if it is useful or otherwise interesting someone with better skills of >>>> presentation will discover it and publish.

    jeez sentiments like that make me wonder if this god-forsaking
    species is even worthy of further progress tbh ...

    Worthy or not, it is able.

    growth isn't the same thing as progress


    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a
    world floundering around in a rather asinine implementation of
    general computing that even remotely do what we need it do, to be frank


    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Sat Sep 5 11:08:42 2026
    From Newsgroup: comp.theory

    On 04/09/2026 22:39, dart200 wrote:
    On 9/4/26 1:37 AM, Mikko wrote:
    On 03/09/2026 19:39, dart200 wrote:
    On 9/3/26 1:06 AM, Mikko wrote:
    On 02/09/2026 17:56, dart200 wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda >>>>>>>>>>>>>>>>>>> liking it. yes i'm quite serious about refuting the >>>>>>>>>>>>>>>>>>> church turing thesis. i demonstrate how an idealized >>>>>>>>>>>>>>>>>>> human agent can compute that which is not turing >>>>>>>>>>>>>>>>>>> computable.

    Is there any way to prove that humans can compute >>>>>>>>>>>>>>>>>> anyhing not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>>>>> compute a function that is strictly outside the bounds >>>>>>>>>>>>>>>>> of turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can >>>>>>>>>>>>>>>> compute the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in >>>>>>>>>>>>>>> two different ways, which in of itself has not be proven. >>>>>>>>>>>>>>
    There is no known method to compute what is not Turing >>>>>>>>>>>>>> computable. You
    may be able to compute some values of an uncomputable >>>>>>>>>>>>>> function but you
    can't know that you can compute for arguments that will be >>>>>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, >>>>>>>>>>>>> and how the algorithm differs from all the partial
    classifiers found in the turing computable space, and why >>>>>>>>>>>>> no turing machine can truly implement the objective total >>>>>>>>>>>>> algorithm even if it is mechanically computable.

    You havn't posted a pointer to your article so we can't >>>>>>>>>>>> comment.
    But in this discussion you have posted no evidence that you can >>>>>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as >>>>>>>>>>> "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist
    independently in abstract from the more concrete mechanical >>>>>>>>>>>>> implementations found in turing machine constructions, >>>>>>>>>>>>> which are inherently more limited by their formally >>>>>>>>>>>>> addressable nature.

    THe concept of algorithm comtains that an algorithm can be >>>>>>>>>>>> described.
    But there is no known way to describe an anlgorithm that >>>>>>>>>>>> cannot be
    described as a Turing machine.

    on the flip side we never actually use the turing machine >>>>>>>>>>> model directly to express algorithms, we use it as a
    fundamental basis for mechanical computation, but the way we >>>>>>>>>>> discuss algorithms is far more high level

    Yes, a Turing machine is not a practical way of doing things. >>>>>>>>>> It is
    a mathematicial model that is useful when one wants to probe that >>>>>>>>>> some function is or is not computable. But being computable >>>>>>>>>> does not
    mean that the computation can be performed quickly enough. The >>>>>>>>>> theory
    of complexity of computation nees a different model.

    i'm aware of the difference between computability vs
    complexity. i'm address the theoretical domain of
    computability, not complexity


    the only difference between the agent's algorithm and the >>>>>>>>>>> partial classifiers that exist in turing machines, is that a >>>>>>>>>>> partial classifier must deal with self-references, whereas >>>>>>>>>>> the agent does not have to logically reckon about that
    because it's not possible to create a direct reference to >>>>>>>>>>> computational process, again my paper will go into more >>>>>>>>>>> detail here specifically

    Whether something is a self-reference is a matter of
    interpretation.

    an true self-reference is not a matter of interpretation. for a >>>>>>>>> running machine this is an exact copy of the source code for >>>>>>>>> the running machine

    Whithout any interpretation there are no references, only synbols. >>>>>>>> Without references there are no self-references.

    a self-reference is a finite length value of data that encodes
    the exact transition table for the running machine

    That's not a reference, it is a self-description. Though the running >>>>>
    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    It is not a copy, it is a description. A copy of a Turing machine is a >>>> Turing machine, which is as unaccessible as self.

    it's a copy (in some encoding) of the transition table the we use to
    define and then refer to a particular machine, and what it
    specifically computes.

    The same behaviour can be presented with different transition tables in

    those are different machines even if they have the same behavior.
    machine identity is defined by the /exact/ same transition table.

    So you consideer a machine that
    - if the symbol under the head is A it is repaced with B and then
    the head is noved to right and then the machine halts
    - otherwise the machine halts immediateyl
    different from a machine that
    - if the symbol under the head is not A the machine halts immediately
    - otherwise the symbol under the head is replaced with B and then
    the head is moved to right and then the machine halts.

    i get that machine equivalence can be tricky, but let me define some language to specify the various relations:

    identical/self-equivalence: this is when two descriptions are the /
    exact/ same transition table and therefore the same string

    isomorphic equivalence: this is when two machines may not have the same transition table, but produce the /exact/ same series of steps in the computations they produce. to be more precise because for example state names can still differ between isomorphic machines, i define this more precisely as the same output bits being written at the same steps in the computation.

    functional/turing equivalence: this is when two machines produce the
    same output even if not thru the exact same series of steps.

    to clarify how "output" is defined here for turing machines (which can
    just write to a tape), i'm reusing turing's convention from his paper:
    the tape is programmatically divided into cells of F-cells and E-cells. F-cells are write only, done so in order, and consist of the defined "output" for what the machine is computing. E-cells are for all the temporary tape state that is not the direct output of the machine.
    turing wrote the very first turing machine description with this
    convention in mind.

    Another possibility is to define that only those symbols are output
    symbols that no rule replaces with another symbol.
    the same language. Trivial changes include the order of the rules and
    the naming of the states. In addition tape symbols that are not used for
    input nor output can be replaced. THerefore it is not tirivial to
    determine whether the table describes self. And in any case, it does not
    refer to self instead of a similar one as both are described by the same
    table.

    it's how machines reference to each other. it's how a machine can
    reference itself, including referencing any particular value it can
    computes

    Machines can describe themselves or other machines but a description
    is not a reference: another machine similar to self is not self but
    is described by the same description.

    u seem to be arguing that self-references don't actually exist... uhhh
    ok, i don't care for things that don't actually exist, so i'm not going
    to use a label for them

    Self-reference does exist in an interpretation that interpretes some
    expression as a self-reference.

    i'm using the term self-reference to label when a machines are referring
    to their own exact description, as that description is semantically equivalent when simulated within another machine as it is when run on
    it's own. idk why ur arguing about this, it seems kinda pointless.

    classic usenet, eh???

    So your "self-reference" does not refer to self but to an equivelence
    class that includes self.

    A description does not refer to a partuclar machine. A description that >>>> describes a machine also describes copies of that machine.

    machine does not care and hardly knows whether the description is a >>>>>> self-descriptipn.

    it matters for certain algos like partial semantic deciders that
    must be aware of when they are deciding on a self-reference

    For that they need to be able to identify a self-description. That is
    not a trivial problem.

    i never said it was trivial, just that it matters.

    You never proved that it is possible.

    sure the encoding is up to "interpretation", but given a
    specified (and correct) method of encoding machines, the self-
    reference is exact and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not

    A string that is an exact self-reference in some interprete|ition may
    refer to something else or hothing in another interpretation. An
    uninterpreted string does not refer.

    we can stick to handling one particular encoding of machines when it
    comes how to reckon about undecidability within computing.

    Does it matter that a problem can be solvable if presented one way
    but unsolvable if preneted in another way?

    because all turing-computable sequences can be found computed by some machine within the total enumeration of all machines in a single turing- complete language, and therefore covers everything that is possibly computable by a turing machine

    are there infinite ways of expressing that same thing becuase there are infinite ways of encoding turing machines? sure, but the point is
    addressing undecidability within a complete expression of everything
    that is computable, not trying to address the complexity involved with translating the infinite ways of expressing the same thing

    those are different issues and i'm addressing the undecidability part,
    not the translation part. and yes you'll prolly keep insisting it
    matters but when enumerating over all machines, it is only necessary to
    do so in one turing-complete language. we do this so it's possible to
    grasp at what exactly are the limits of computability. throwing a bunch
    of arbitrarily complexity in there muddles the more fundamental issue
    and makes it unreasonable to reckon about ... and therefore is counter productive

    Just be careful with the definitions when you specify what you are
    going to describe.

    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>>>>> actions.

    this isn't like a bad thing either, turing machines are >>>>>>>>>>>>> great and incredibly useful. i'm trying to increase their >>>>>>>>>>>>> productivity by resolving their limitations more accurately >>>>>>>>>>>>> so we stop tripping over the halting problem as excuse to >>>>>>>>>>>>> not be proving correctness for every single program we >>>>>>>>>>>>> deploy...

    no, testing isn't good enough bro, nor is the braindead way >>>>>>>>>>>>> we go about producing and maintaining computing
    infrastructure. the dumb fucking corpo ratrace to nowhere >>>>>>>>>>>>> instead of producing the systems we not only need but >>>>>>>>>>>>> deserve is just so ungodly


    the agent can compute something outside the bounds of >>>>>>>>>>>>>>> turing computability due to an issue of addressability, >>>>>>>>>>>>>>> or lack thereof, which can't be simulated by a turing >>>>>>>>>>>>>>> machine because any value computed by a turing machine is >>>>>>>>>>>>>>> necessarily addressable

    That has not been proven. There is no way to implement an >>>>>>>>>>>>>> uncountably
    infinite address space and any finite or countably >>>>>>>>>>>>>> infinite is
    accessible.


    it's not uncountability that prevents the addressing, it's >>>>>>>>>>>>> a mechanical discontinuity, and i can only explain by >>>>>>>>>>>>> properly describing the justifying thought experiment >>>>>>>>>>>>
    A finite or countable address space is fully discontinuous >>>>>>>>>>>> anyway butthat does not prevent a simulation of full
    accessibility. Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one >>>>>>>>>>
    What does "mechanical discontinuity" mean? How is anything >>>>>>>>>> mechanical
    relevant to algorithms?

    a halting classifier/decider, even if only partial, needs
    genuine access to it's own source code in order to function >>>>>>>>> optimally

    If you want to talk about optimization you must not talk about >>>>>>>> Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to >>>>>>> optimal functionality, ei deciding some maximal subset of
    machines within a given semantic set (like set of halting
    machine, or set of circle-free machine)

    Then you should use some other word. Words derived from "optimum" are >>>>>> understood to refer performance and resource consumption aspectes of >>>>>> computation.

    i explained my usage

    Even with an explanation it is confusing. Another word or phrase could >>>> be better.

    thank you for ur input

    You are welcome.

    There are problems where every partial algorithm fails to compute for >>>>>> some argument that another partial agorithm computes. One example is >>>>>> the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect >>>>>>> you to accept that without reading the proof i have to yet to post. >>>>>>
    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of >>>>>>> turing machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access >>>>>>>> their own "source code".

    sure, the point is there exist some algos that require a self-
    reference

    Not proven.

    while this can be implemented programmatically using a quine, >>>>>>>>> it's not by default a mechanism of turing machines, so any
    random program does not have access to their own source code, >>>>>>>>> only ones implemented with quines have definitive access to >>>>>>>>> that. the rest struggle from a mechanical limitation, and
    that's the point of the example

    sure, many/most algos may not need it, but some do, and unless >>>>>>>>> they have a programmatic solution they struggle from a what is >>>>>>>>> a mechanical discontinuity


    it's like trying to program a random turing machine to
    directly access it's own source code ... the information >>>>>>>>>>> exists in abstract, but the turing machine model does not >>>>>>>>>>> have a mechanical means of accessing it (barring a program >>>>>>>>>>> implemented with a genuine quine, but those are exceptions >>>>>>>>>>> stemming from programmatic solutions, not the fundamental >>>>>>>>>>> mechanics of the machine)

    An algorithm cannot and need not access its "source code". It >>>>>>>>>> knows
    the argument and that fully determines the value of the function. >>>>>>>>>>> or it's like asking a turing machine being simulated by >>>>>>>>>>> another to arbitrarily access values from the machine that is >>>>>>>>>>> simulating it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But >>>>>>>>>> the process
    is not a simulation if those values are not present in the >>>>>>>>>> real thing
    the simulation itendes to simulate.

    the point is dude that this is an example of mechanical
    limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world >>>>>> whereas "algorithm" refers to a mathematical concept. The real world >>>>>> does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    An idealized machine does not have specific mechanics. The idealization >>>
    yes it does. it has a head. and a tape. and various commands it can
    process in accordance with a transition table that then has
    mechanical effects on that head and tape. those are the mechanics of
    the idealized computing machine, and that's how i'm using the word

    Those are mathematical descriptions. Perhaps you mean systematic?

    i call it a mechanical discontinuity because of a lack of specified mechanism within the mathematical model

    Abouve you said you are not going to use any word for things that
    don't exist.

    i explained my usage

    omits unimprtant implementation details. It may avoid some constraints >>>> of real computers like the requiremt that every machine instruction
    must perform a Turing-computable function. Or it may have additional
    restrictins that real computers have not. But neither restrictins are
    "mechanical", only functional.

    but what i'm trying to convey is that a mechanical discontinuity >>>>>>> happens when a computation run on a turing machine lacks a
    mechanism to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it.

    That is an unavoidable consequence of bad presentation.

    it can also be the consequence of bad listening, which is really
    quite endemic in online discussion

    In case of bad listening the cause and consequences are on the same side
    so the other side needn't care.

    i'm definitely affects, however indirectly, by all the ignorance
    sustained thru poor listening skills

    Anyway, the listening or reading skills of your audience are mpostly undontrollable and even unobservable.

    communication is a two way street

    Not always. A can read what for example Turing has written but I can't >>>> ask Turing about the exact meanings of his words. Unless you can write >>>> a preentation that can be understood by readers who can't or don't ask >>>> questions it doesn't matter whether you have discovered something. But >>>> if it is useful or otherwise interesting someone with better skills of >>>> presentation will discover it and publish.

    jeez sentiments like that make me wonder if this god-forsaking
    species is even worthy of further progress tbh ...

    Worthy or not, it is able.

    growth isn't the same thing as progress

    But growth is easire to achieve and easier to identify and measure.

    but i'm not doing it for the rest of ya'll. i'm doing it to build a
    better world for my kid, so that he doesn't need to suffer thru a
    world floundering around in a rather asinine implementation of
    general computing that even remotely do what we need it do, to be frank
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Damon@richard@damon-family.org to comp.theory on Mon Sep 7 20:17:44 2026
    From Newsgroup: comp.theory

    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function that is strictly outside the bounds of turing computability

    But your rCLidealized human agentrCY doesnrCOt exist, and that number not on the
    diagonal canrCOt be computed by an actual existing idealized human agent,
    they can only create a symbol for something that is actually unknown.


    computable? Much can be computed with a Turing computable partial
    method.


    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing machine)


    Your problem is you donrCOt understand that the rCLrulesrCY require you to be looking at things that can actually exist under the basic rules.

    Your idealization is just a smoke screen to hide that you are trying to
    imagine things that are outside the allowable domain of machines.

    It is well known in the field of Hyper Computability that there exist an infinite number of rCLLevel 0rCY problems that canrCOt be solved by machines limited to the normal rules of computability (being limited to finite rule
    sets and finite time) that can actually be solved by Level 1 Hyper
    Computation machines that relax those limits. Of course, the reason we
    number the levels is because with level 1 computation machines, we can
    create problem that these level 1 machines canrCOt compute, needing a level 2 machine, and so on and so forth. A Level N machine can solve problems using
    no more that level N-1 computation as their input.

    Of course, one problem with Hyper Computation machines is they can not
    actually be made in a physical rCLlevel 0rCY universe like we live in, so are only theoretical/mathematical constructs.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Richard Damon@richard@damon-family.org to comp.theory on Mon Sep 7 20:17:46 2026
    From Newsgroup: comp.theory

    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>>>>> it. yes i'm quite serious about refuting the church turing >>>>>>>>>>>>>>> thesis. i demonstrate how an idealized human agent can >>>>>>>>>>>>>>> compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function >>>>>>>>>> but you
    can't know that you can compute for arguments that will be >>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and how >>>>>>>>> the algorithm differs from all the partial classifiers found in >>>>>>>>> the turing computable space, and why no turing machine can truly >>>>>>>>> implement the objective total algorithm even if it is
    mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to
    understand what it is evidence about.

    i might be the first to realize: algorithms exist independently >>>>>>>>> in abstract from the more concrete mechanical implementations >>>>>>>>> found in turing machine constructions, which are inherently more >>>>>>>>> limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be
    described.
    But there is no known way to describe an anlgorithm that cannot be >>>>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model >>>>>>> directly to express algorithms, we use it as a fundamental basis >>>>>>> for mechanical computation, but the way we discuss algorithms is >>>>>>> far more high level

    Yes, a Turing machine is not a practical way of doing things. It is >>>>>> a mathematicial model that is useful when one wants to probe that
    some function is or is not computable. But being computable does not >>>>>> mean that the computation can be performed quickly enough. The theory >>>>>> of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm >>>>> address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial >>>>>>> classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does >>>>>>> not have to logically reckon about that because it's not possible >>>>>>> to create a direct reference to computational process, again my >>>>>>> paper will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation. >>>>>
    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine
    th
    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    Nope, the problem is rCLTuring MachinesrCY are incapable of handling rCLreferencesrCY of any form, let alone rCLself-referencesrCY.


    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that must be aware of when they are deciding on a self-reference


    Nope, the problem is you rCLgrammarrCY is just invalid. Note that part of your problem is that you want to express questions that use self-references when that is NOT in the allowed problem space. Part of the issue is that the
    class of problems under concern are required to be rCLObjectiverCY, and thus have the same answer to any machine you pose it to, and thus it canrCOt refer to the machine the problem is being given to.

    As to machines being able to detect that an input contains a machine based
    on itself, that has been proven to be uncomputable. A fact you assume to
    not be correct.


    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is exact
    and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not


    i think we agree on this


    An algrithm does not interprete, it just specifies computational
    actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>>> and incredibly useful. i'm trying to increase their productivity >>>>>>>>> by resolving their limitations more accurately so we stop
    tripping over the halting problem as excuse to not be proving >>>>>>>>> correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we >>>>>>>>> go about producing and maintaining computing infrastructure. the >>>>>>>>> dumb fucking corpo ratrace to nowhere instead of producing the >>>>>>>>> systems we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing >>>>>>>>>>> computability due to an issue of addressability, or lack >>>>>>>>>>> thereof, which can't be simulated by a turing machine because >>>>>>>>>>> any value computed by a turing machine is necessarily addressable >>>>>>>>>>
    That has not been proven. There is no way to implement an >>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway >>>>>>>> butthat does not prevent a simulation of full accessibility.
    Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical >>>>>> relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing
    machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of
    circle-free machine)

    Then you should use some other word. Words derived from "optimum" are
    understood to refer performance and resource consumption aspectes of
    computation.

    i explained my usage

    Typical technique of scammers send liars.



    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect you
    to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of turing
    machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference

    Not proven.

    while this can be implemented programmatically using a quine, it's
    not by default a mechanism of turing machines, so any random program >>>>> does not have access to their own source code, only ones implemented >>>>> with quines have definitive access to that. the rest struggle from a >>>>> mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they >>>>> have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly >>>>>>> access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a mechanical >>>>>>> means of accessing it (barring a program implemented with a
    genuine quine, but those are exceptions stemming from programmatic >>>>>>> solutions, not the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows >>>>>> the argument and that fully determines the value of the function. >>>>>>> or it's like asking a turing machine being simulated by another to >>>>>>> arbitrarily access values from the machine that is simulating
    it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the
    process
    is not a simulation if those values are not present in the real thing >>>>>> the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation.

    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    Something you need to actually DEFINE, and if not compatible with the rules
    of the field you claim to be working in just admits you donrCOt know what you are talking about.

    This has been part of you problem, that you donrCOt actually understand the field you are talking about, or its rules, and you just prove that you
    donrCOt seem actually capable of understanding it.



    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a mechanism
    to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it. communication is a two
    way street dud, and if u don't accept ur half the responsibility i won't care to explain myself further to someone who doesn't care


    i gave you two examples of where a lack of mechanism creates a
    mechanical discontinuity, and if u don't want to consider them then i
    cannot help you further here
    Your examples were not clear. And examples are not very good for the
    purpose. Or at least, for a rough idea, you need counter-examples, too.
    But complete definitions are clearer.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Sep 7 14:26:45 2026
    From Newsgroup: comp.theory

    On 9/7/26 1:17 PM, Richard Damon wrote:
    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 9/2/26 1:04 AM, Mikko wrote:
    On 01/09/2026 22:50, dart200 wrote:
    On 8/31/26 11:44 PM, Mikko wrote:
    On 01/09/2026 00:35, dart200 wrote:
    On 8/31/26 2:55 AM, Mikko wrote:
    On 31/08/2026 04:17, dart200 wrote:
    On 8/30/26 1:17 AM, Mikko wrote:
    On 30/08/2026 09:51, dart200 wrote:
    On 8/29/26 1:05 AM, Mikko wrote:
    On 28/08/2026 10:40, dart200 wrote:
    On 8/28/26 12:27 AM, Mikko wrote:
    On 27/08/2026 22:50, dart200 wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking >>>>>>>>>>>>>>>> it. yes i'm quite serious about refuting the church turing >>>>>>>>>>>>>>>> thesis. i demonstrate how an idealized human agent can >>>>>>>>>>>>>>>> compute that which is not turing computable.

    Is there any way to prove that humans can compute anyhing >>>>>>>>>>>>>>> not Turing

    yes, i use the concept of an idealized human agent to >>>>>>>>>>>>>> compute a function that is strictly outside the bounds of >>>>>>>>>>>>>> turing computability

    If you can't simulate that agent with a Turing-complete >>>>>>>>>>>>> computer you
    cant use it for any computation. If you can you can compute >>>>>>>>>>>>> the same
    with a Turing machine.

    that's just asserting the church-turing thesis at me in two >>>>>>>>>>>> different ways, which in of itself has not be proven.

    There is no known method to compute what is not Turing
    computable. You
    may be able to compute some values of an uncomputable function >>>>>>>>>>> but you
    can't know that you can compute for arguments that will be >>>>>>>>>>> given later
    unless you have a method.

    my paper specifically details how that method can exist, and how >>>>>>>>>> the algorithm differs from all the partial classifiers found in >>>>>>>>>> the turing computable space, and why no turing machine can truly >>>>>>>>>> implement the objective total algorithm even if it is
    mechanically computable.

    You havn't posted a pointer to your article so we can't comment. >>>>>>>>> But in this discussion you have posted no evidence that you can >>>>>>>>> compute somthing that a Turing machine cannot.

    i'm just serious: would you consider a thought experiment as
    "evidence"?

    Usually I wouldn't but it is possible to do so. One just need to >>>>>>> understand what it is evidence about.

    i might be the first to realize: algorithms exist independently >>>>>>>>>> in abstract from the more concrete mechanical implementations >>>>>>>>>> found in turing machine constructions, which are inherently more >>>>>>>>>> limited by their formally addressable nature.

    THe concept of algorithm comtains that an algorithm can be
    described.
    But there is no known way to describe an anlgorithm that cannot be >>>>>>>>> described as a Turing machine.

    on the flip side we never actually use the turing machine model >>>>>>>> directly to express algorithms, we use it as a fundamental basis >>>>>>>> for mechanical computation, but the way we discuss algorithms is >>>>>>>> far more high level

    Yes, a Turing machine is not a practical way of doing things. It is >>>>>>> a mathematicial model that is useful when one wants to probe that >>>>>>> some function is or is not computable. But being computable does not >>>>>>> mean that the computation can be performed quickly enough. The theory >>>>>>> of complexity of computation nees a different model.

    i'm aware of the difference between computability vs complexity. i'm >>>>>> address the theoretical domain of computability, not complexity


    the only difference between the agent's algorithm and the partial >>>>>>>> classifiers that exist in turing machines, is that a partial
    classifier must deal with self-references, whereas the agent does >>>>>>>> not have to logically reckon about that because it's not possible >>>>>>>> to create a direct reference to computational process, again my >>>>>>>> paper will go into more detail here specifically

    Whether something is a self-reference is a matter of interpretation. >>>>>>
    an true self-reference is not a matter of interpretation. for a
    running machine this is an exact copy of the source code for the
    running machine

    Whithout any interpretation there are no references, only synbols.
    Without references there are no self-references.

    a self-reference is a finite length value of data that encodes the
    exact transition table for the running machine
    th
    That's not a reference, it is a self-description. Though the running

    that's what a self-reference is for turing machines, it can only
    reference itself by an exact copy

    Nope, the problem is rCLTuring MachinesrCY are incapable of handling rCLreferencesrCY of any form, let alone rCLself-referencesrCY.

    yes rick i'm aware it's not a pointer-reference like modern programing paradigms

    i'm using "self-reference" to describe a situation where a turing
    machine has an exact copy of it's description on the tape somewhere,
    allowing to do something like run semantic analysis on itself, or
    simulate itself, or etc

    more modern programming paradigms would use pointer to do this, but like
    you: turing machines don't have those.



    machine does not care and hardly knows whether the description is a
    self-descriptipn.

    it matters for certain algos like partial semantic deciders that must be
    aware of when they are deciding on a self-reference


    Nope, the problem is you rCLgrammarrCY is just invalid. Note that part of your
    problem is that you want to express questions that use self-references when that is NOT in the allowed problem space. Part of the issue is that the
    class of problems under concern are required to be rCLObjectiverCY, and thus have the same answer to any machine you pose it to, and thus it canrCOt refer to the machine the problem is being given to.

    As to machines being able to detect that an input contains a machine based
    on itself, that has been proven to be uncomputable. A fact you assume to
    not be correct.


    sure the encoding is up to "interpretation", but given a specified
    (and correct) method of encoding machines, the self-reference is exact >>>> and not up to interpretation.

    The meaning of "exact" also depends on interpretation.

    it does not


    i think we agree on this


    An algrithm does not interprete, it just specifies computational >>>>>>> actions.

    this isn't like a bad thing either, turing machines are great >>>>>>>>>> and incredibly useful. i'm trying to increase their productivity >>>>>>>>>> by resolving their limitations more accurately so we stop
    tripping over the halting problem as excuse to not be proving >>>>>>>>>> correctness for every single program we deploy...

    no, testing isn't good enough bro, nor is the braindead way we >>>>>>>>>> go about producing and maintaining computing infrastructure. the >>>>>>>>>> dumb fucking corpo ratrace to nowhere instead of producing the >>>>>>>>>> systems we not only need but deserve is just so ungodly


    the agent can compute something outside the bounds of turing >>>>>>>>>>>> computability due to an issue of addressability, or lack >>>>>>>>>>>> thereof, which can't be simulated by a turing machine because >>>>>>>>>>>> any value computed by a turing machine is necessarily addressable >>>>>>>>>>>
    That has not been proven. There is no way to implement an >>>>>>>>>>> uncountably
    infinite address space and any finite or countably infinite is >>>>>>>>>>> accessible.


    it's not uncountability that prevents the addressing, it's a >>>>>>>>>> mechanical discontinuity, and i can only explain by properly >>>>>>>>>> describing the justifying thought experiment

    A finite or countable address space is fully discontinuous anyway >>>>>>>>> butthat does not prevent a simulation of full accessibility. >>>>>>>>> Restrictions
    in accessibility can also be simulated.

    it's not a numerical discontinuity, it's a mechanical one

    What does "mechanical discontinuity" mean? How is anything mechanical >>>>>>> relevant to algorithms?

    a halting classifier/decider, even if only partial, needs genuine
    access to it's own source code in order to function optimally

    If you want to talk about optimization you must not talk about Turing >>>>> machines. They are never optimal.

    by optimally i don't mean speed/time complexity, i'm referring to
    optimal functionality, ei deciding some maximal subset of machines
    within a given semantic set (like set of halting machine, or set of
    circle-free machine)

    Then you should use some other word. Words derived from "optimum" are
    understood to refer performance and resource consumption aspectes of
    computation.

    i explained my usage

    Typical technique of scammers send liars.



    There are problems where every partial algorithm fails to compute for
    some argument that another partial agorithm computes. One example is
    the halting problem.

    this maximal subset may be turing-complete, but i wouldn't expect you
    to accept that without reading the proof i have to yet to post.

    THat's right. Without a proof there is nothing.

    actually, even correctly deciding a less-than-maximal subset of turing >>>> machines requires a true self-reference

    In particular, that cannot be accepted without a proof.

    Ordinary computers perform quite well without any ability to access
    their own "source code".

    sure, the point is there exist some algos that require a self-reference >>>
    Not proven.

    while this can be implemented programmatically using a quine, it's >>>>>> not by default a mechanism of turing machines, so any random program >>>>>> does not have access to their own source code, only ones implemented >>>>>> with quines have definitive access to that. the rest struggle from a >>>>>> mechanical limitation, and that's the point of the example

    sure, many/most algos may not need it, but some do, and unless they >>>>>> have a programmatic solution they struggle from a what is a
    mechanical discontinuity


    it's like trying to program a random turing machine to directly >>>>>>>> access it's own source code ... the information exists in
    abstract, but the turing machine model does not have a mechanical >>>>>>>> means of accessing it (barring a program implemented with a
    genuine quine, but those are exceptions stemming from programmatic >>>>>>>> solutions, not the fundamental mechanics of the machine)

    An algorithm cannot and need not access its "source code". It knows >>>>>>> the argument and that fully determines the value of the function. >>>>>>>> or it's like asking a turing machine being simulated by another to >>>>>>>> arbitrarily access values from the machine that is simulating
    it... that's just not mechanically possible.

    The simulating machine can use any value it can access. But the
    process
    is not a simulation if those values are not present in the real thing >>>>>>> the simulation itendes to simulate.

    the point is dude that this is an example of mechanical limitation. >>>>>
    No, it is an essential aspect of the meanings of the words.


    idk what ur arguing,

    Meanings of the words. The word "mechanical" refers to the real world
    whereas "algorithm" refers to a mathematical concept. The real world
    does not limit mathematics in any way.

    we're discussing the mechanics of an idealized computing machine

    Something you need to actually DEFINE, and if not compatible with the rules of the field you claim to be working in just admits you donrCOt know what you are talking about.

    i'm well aware of the limits to turing machine computability rick


    This has been part of you problem, that you donrCOt actually understand the field you are talking about, or its rules, and you just prove that you donrCOt seem actually capable of understanding it.

    need i remind you: no one has proven that turing machine computation
    actually encompasses all that is intuitive computable




    but what i'm trying to convey is that a mechanical discontinuity
    happens when a computation run on a turing machine lacks a mechanism
    to directly access some specific information.

    Whatever you were trying to comvay you failed. No other result is
    possible without without a respect of the meanings of the words.

    well you then similarly failed to understand it. communication is a two
    way street dud, and if u don't accept ur half the responsibility i won't
    care to explain myself further to someone who doesn't care


    i gave you two examples of where a lack of mechanism creates a
    mechanical discontinuity, and if u don't want to consider them then i
    cannot help you further here
    Your examples were not clear. And examples are not very good for the
    purpose. Or at least, for a rough idea, you need counter-examples, too.
    But complete definitions are clearer.

    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From dart200@user7160@newsgrouper.org.invalid to comp.theory on Mon Sep 7 14:29:53 2026
    From Newsgroup: comp.theory

    On 9/7/26 1:17 PM, Richard Damon wrote:
    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function
    that is strictly outside the bounds of turing computability

    But your rCLidealized human agentrCY doesnrCOt exist, and that number not on the

    they exist as much as a turing machine does, which to say in theory they
    can ...

    diagonal canrCOt be computed by an actual existing idealized human agent, they can only create a symbol for something that is actually unknown.

    i do agree is that problems like halting shows that no turing machine is
    a total decider for all input machines ...

    but i disagree with the church-turing thesis that the turing machine
    model captures the full scope of what is intuitive computable (by said idealized human agent)

    because there is no machine that is objectively 'undecidable',

    even proving that machine is undecidable in respect to a particular
    decider requires us to compute the fact (thru a finite series of steps)
    that said decider failed to classify it correctly ... which means we
    still correctly decided what the machine actually does, in order to show
    how it wasn't classifier by the decider in the way it ought to be.

    what my paper shows is that undecidability within the turing machine
    model is due to the inherent quality of turing machine model being addressable/referencable in total, it's not due to more a fundamental
    limit to computability. i construct a model that demonstrates that if
    the idealized agent is required to write his answers to a "terminal
    machine", which would make them addressable, those answers are then
    subject to the same turing machine limits



    computable? Much can be computed with a Turing computable partial
    method.


    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing machine) >>

    Your problem is you donrCOt understand that the rCLrulesrCY require you to be looking at things that can actually exist under the basic rules.

    Your idealization is just a smoke screen to hide that you are trying to imagine things that are outside the allowable domain of machines.

    i'm not trying to extend the domain of machines with this paper, i'm
    proving that the domain of turing machines is not a limit to what is intuitively computable

    it's worth reminding you there is _still_ no proof for the church-turing thesis, i don't actually have to show a fault in any proof along with my
    proof against it, because there is _none_ for it

    there are just people continually engaging in repetitive propaganda over
    it. which btw is appropriate according to turing:

    | The [ct-thesis] is rCa one which one does not attempt to prove.
    | Propaganda is more appropriate to it than proof, for its status
    | is something between a theorem and a definition [Tur1954]



    It is well known in the field of Hyper Computability that there exist an infinite number of rCLLevel 0rCY problems that canrCOt be solved by machines limited to the normal rules of computability (being limited to finite rule sets and finite time) that can actually be solved by Level 1 Hyper Computation machines that relax those limits. Of course, the reason we
    number the levels is because with level 1 computation machines, we can
    create problem that these level 1 machines canrCOt compute, needing a level 2 machine, and so on and so forth. A Level N machine can solve problems using no more that level N-1 computation as their input.

    Of course, one problem with Hyper Computation machines is they can not actually be made in a physical rCLlevel 0rCY universe like we live in, so are only theoretical/mathematical constructs.

    nice to see ur not dead yet rick, i mean that genuinely
    --
    arising us out of the computing dark ages,
    please excuse my pseudo-pyscript,
    ~ the lil crank that could
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to comp.theory on Mon Sep 7 18:27:52 2026
    From Newsgroup: comp.theory

    On 09/07/2026 01:17 PM, Richard Damon wrote:
    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm
    quite serious about refuting the church turing thesis. i demonstrate
    how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function
    that is strictly outside the bounds of turing computability

    But your rCLidealized human agentrCY doesnrCOt exist, and that number not on the
    diagonal canrCOt be computed by an actual existing idealized human agent, they can only create a symbol for something that is actually unknown.


    computable? Much can be computed with a Turing computable partial
    method.


    at this point i suspect there to be machines which may not be
    "computable" by any partial decider, but even that is just not quite
    equal to what an idealized agent can mechanically prove in a finite
    amount of steps (which is necessarily not computable by any turing machine) >>

    Your problem is you donrCOt understand that the rCLrulesrCY require you to be looking at things that can actually exist under the basic rules.

    Your idealization is just a smoke screen to hide that you are trying to imagine things that are outside the allowable domain of machines.

    It is well known in the field of Hyper Computability that there exist an infinite number of rCLLevel 0rCY problems that canrCOt be solved by machines limited to the normal rules of computability (being limited to finite rule sets and finite time) that can actually be solved by Level 1 Hyper Computation machines that relax those limits. Of course, the reason we
    number the levels is because with level 1 computation machines, we can
    create problem that these level 1 machines canrCOt compute, needing a level 2 machine, and so on and so forth. A Level N machine can solve problems using no more that level N-1 computation as their input.

    Of course, one problem with Hyper Computation machines is they can not actually be made in a physical rCLlevel 0rCY universe like we live in, so are only theoretical/mathematical constructs.



    Well-ordering and well-foundedness and well-dispersion are three
    different rules, that to be made to agree, involve super-classical
    and infinitary reasoning, and, analytical bridges, about continuous
    domains.

    So, there are rules about when rules disagree, also.

    "Zeno machines" in nature are constantly computing all the time,
    those are simply evidenced as "analog computers" for examples.

    I.e., some of what are written as "hyper" problems are easily
    re-written as "hypo" problems. There's not a strict ordering
    as there is in the sense of usual account of polynomial and
    non-polynomial problems, which have quite available means of
    computing their bounds and of their approximations their error bounds.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mikko@mikko.levanto@iki.fi to comp.theory on Wed Sep 9 11:01:22 2026
    From Newsgroup: comp.theory

    On 08/09/2026 00:29, dart200 wrote:
    On 9/7/26 1:17 PM, Richard Damon wrote:
    dart200 <user7160@newsgrouper.org.invalid> wrote:
    On 8/27/26 12:49 AM, Mikko wrote:
    On 27/08/2026 08:40, dart200 wrote:
    title of my next paper is tentative, but i'm kinda liking it. yes i'm >>>>> quite serious about refuting the church turing thesis. i demonstrate >>>>> how an idealized human agent can compute that which is not turing
    computable.

    Is there any way to prove that humans can compute anyhing not Turing

    yes, i use the concept of an idealized human agent to compute a function >>> that is strictly outside the bounds of turing computability

    But your rCLidealized human agentrCY doesnrCOt exist, and that number not on
    the

    they exist as much as a turing machine does, which to say in theory they
    can ...

    No, they don-?t. Turing machines exist as a well-defined mathematical
    construct presented in textbooks. Your "idealized human agent" does not.
    --
    Mikko
    --- Synchronet 3.22a-Linux NewsLink 1.2