• About the difference between "time dilation" and "clock error"

    From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to All on Tue Jul 22 12:33:37 2025
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it, because some idiot has asserted it's
    correct and proper and demanded by
    some Laws of Nature he invented.

    Of course, there is no "time dilation"
    in GPS. It exist only in gedankenland,
    only gedanken people from gedankenland
    can be stupid enough to treat the idiot
    seriously. In the real world - stupidity
    is never infinite, the idiot has been
    mistaken about that too.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Tue Jul 22 15:08:54 2025
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about it", using
    the same tools and procedure to compute "what to do about it", disagree
    about the correction to apply for the same two clocks?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Tue Jul 22 18:17:46 2025
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about it",
    using the same tools and procedure to compute "what to do about it",
    disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hachel@21:1/5 to All on Tue Jul 22 16:41:21 2025
    Le 22/07/2025 à 17:08, Python a écrit :
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about it", using the
    same tools and procedure to compute "what to do about it", disagree about the correction to apply for the same two clocks?

    S'il n'y avait pas tant d'abrutis (qui traitent les autres d'abrutis), il aurait été possible de mieux comprendre la théorie de la relativité,
    car on voit que où on se tourne, tout le monde raconte n'importe quoi
    sans comprendre réellement les choses.

    Par exemple, si l'on demande à quelqu'un ce qui va se passer si un corps tourne autour d'un autre, par exemple une fusée qui tournerait très
    loin, à 0.8c autour de la terre, il va répondre qu'ici le mouvement est absolu, et que la chronotropie est plus faible pour la fusée.

    Les plus grands pontes de la physique diraient la même chose.

    L'incompréhension est totale. La chronotropie relative dépend de la
    vitesse, MAIS elle est toujours réciproque. Pour la terre, c'est la
    fusée qui tourne autour de la terre qui a une chronotropie plus faible.

    Mais pour la fusée, c'est l'inverse!

    Cela nous renvoie au paradoxe de Langevin, jamais réellement résolu,
    pare qu'on ne sait pas de quoi on cause, ce qui autorise à faire le
    malin.

    La fusée rentrant sur terre, le temps écoulé dans la fusée est moindre
    que le temps terrestre.

    Et là tout le monde devient fou.

    Personne, absolument personne n'est capable de comprendre pourquoi.

    Je l'explique depuis 40 ans, mais on me crache à la gueule. J'explique
    une propriété spéciale de l'univers : l'anisochronie cosmique, qui
    donne à l'espace-temps une géométrie particulière.

    Quelle belle bande de tarés, les hommes.

    Incapables qu'ils sont de comprendre que la fusée perçoit sans cesse une chronotropie terrestre battant moins vite qu'elle. Et pourtant, au retour,
    sa montre marque un temps inférieur.

    Depuis 120 ans, ça les rend tous fous, incapable qu'ils sont d'expliquer pourquoi.

    Et avec des tarés comme qui vous savez sur usenet, on en est encore à
    l'âge de pierre relativiste.

    C'est désolant.

    R.H.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Tue Jul 22 17:56:24 2025
    Le 22/07/2025 à 18:17, Maciej Woźniak a écrit :
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about it",
    using the same tools and procedure to compute "what to do about it",
    disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    I payed you to have these clocks synchronized. You refund me then ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Tue Jul 22 21:11:06 2025
    On 7/22/2025 7:56 PM, Python wrote:
    Le 22/07/2025 à 18:17, Maciej Woźniak a écrit :
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about
    it", using the same tools and procedure to compute "what to do about
    it", disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    I payed you to have these clocks synchronized.

    Did you? I don't remember.

    You refund me then ?

    And what if I don't?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Tue Jul 22 19:53:39 2025
    Le 22/07/2025 à 21:11, Maciej Woźniak a écrit :
    On 7/22/2025 7:56 PM, Python wrote:
    Le 22/07/2025 à 18:17, Maciej Woźniak a écrit :
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something about
    it", using the same tools and procedure to compute "what to do about
    it", disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    I payed you to have these clocks synchronized.

    Did you? I don't remember.

    You refund me then ?

    And what if I don't?

    I will hire someone else and ask her/him the same question.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Wed Jul 23 09:01:30 2025
    On 7/22/2025 9:53 PM, Python wrote:
    Le 22/07/2025 à 21:11, Maciej Woźniak a écrit :
    On 7/22/2025 7:56 PM, Python wrote:
    Le 22/07/2025 à 18:17, Maciej Woźniak a écrit :
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something
    about it", using the same tools and procedure to compute "what to do
    about it", disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    I payed you to have these clocks synchronized.

    Did you? I don't remember.

    You refund me then ?

    And what if I don't?

    I will hire someone else and ask her/him the same question.

    If you pay me handsomely I will
    give you any answer you desire.

    But, well, considering my attitude
    to The Shit of your idiot guru
    and to yourself - it won't be cheap.
    Better, indeed, hire someone else.
    Many of your fellow idiots would do
    it for free.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Wed Jul 23 11:28:13 2025
    Le 23/07/2025 à 09:01, Maciej Woźniak a écrit :
    On 7/22/2025 9:53 PM, Python wrote:
    Le 22/07/2025 à 21:11, Maciej Woźniak a écrit :
    On 7/22/2025 7:56 PM, Python wrote:
    Le 22/07/2025 à 18:17, Maciej Woźniak a écrit :
    On 7/22/2025 5:08 PM, Python wrote:
    Le 22/07/2025 à 12:33, Maciej Woźniak a écrit :
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it

    What if two of the technicians you hired to "do something
    about it", using the same tools and procedure to compute "what to do
    about it", disagree about the correction to apply for the same two clocks?

    That's a simple one, poor stinker: I'm
    not paying them.

    I payed you to have these clocks synchronized.

    Did you? I don't remember.

    You refund me then ?

    And what if I don't?

    I will hire someone else and ask her/him the same question.

    If you pay me handsomely I will
    give you any answer you desire.

    Oh, so you're open to bribery now?

    But, well, considering my attitude

    .. this is not quite a surprise.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Heger@21:1/5 to All on Tue Jul 29 09:48:24 2025
    Am Dienstag000022, 22.07.2025 um 12:33 schrieb Maciej Woźniak:
    When our clocks desynchronize and
    we have to correct it - it's not
    any "time dilation". It's a "clock
    error" - a very classical phenomenon,
    well known by Galileo and Newton
    and most of primary school students.

    "Time dilation" - is when our clocks
    desynchronize and we do nothing about
    it, because some idiot has asserted it's
    correct and proper and demanded by
    some Laws of Nature he invented.

    Of course, there is no "time dilation"
    in GPS. It exist only in gedankenland,
    only gedanken people from gedankenland
    can be stupid enough to treat the idiot
    seriously. In the real world - stupidity
    is never infinite, the idiot has been
    mistaken about that too.


    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to transfer a signal.


    E.g. if there is a large clock on the Moon, which we could read out by a
    large telescope, the clock there would show a time ~1s too early.

    This one second is caused by the delay of the signal from Moon to Earth
    and not because the remote clock is desynchronized.

    If the remote clock would move, say, away at 0.5 c, than things get more complicated, because the so called Doppler effect gets relevant.

    This would alter the wavelength of the received signal and also the
    apparent time at the remote station (and also the apparent form of the
    remote object)

    Now, Einstein didn't consider Wavelength at all in his paper 'On the electrodynamics of moving bodies' and called the apparent affect upon
    the remote clock 'time dilation' and the apparent deformation 'length contraction'.

    It would have been better to simply measure the delay and add that value
    to the apparent remote time.

    But that wasn't done by Einstein. Actually this delay wasn't even mentioned.

    So, in a way, Einstein used an extremely convoluted way to calculate the Doppler effect and ascribed the effects to the remote object, instead of
    to the delay caused by the finite speed of light.


    TH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul.B.Andersen@21:1/5 to All on Tue Jul 29 22:02:52 2025
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to transfer a signal.


    E.g. if there is a large clock on the Moon, which we could read out by a large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
    "The two clocks synchronise if tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Wed Jul 30 10:54:15 2025
    Le 29/07/2025 à 22:01, "Paul.B.Andersen" a écrit :
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to transfer a
    signal.


    E.g. if there is a large clock on the Moon, which we could read out by a
    large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
    "The two clocks synchronise if tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?

    Thomas could even see the delay applied according to the exact equations
    from Einstein's article as used in my Web app there: https://noedge.net/e/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Paul.B.Andersen on Wed Jul 30 07:08:50 2025
    On 7/29/2025 10:02 PM, Paul.B.Andersen wrote:
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to transfer
    a signal.


    E.g. if there is a large clock on the Moon, which we could read out by
    a large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on  the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    G edanken/fabricated delusions of a
    brainwashed idiot. anyone can check
    GPS, clocks stay in sync.>
    ---------------------

    We have an observer at point A on the Earth and another observer
    at point B on the Moon.


    Gedanken/fabricated delusions
    of a brainwashed idiot. No we
    don't have.


    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    Gedanken/fabricated delusions
    of a brainwashed idiot. SI
    idiocy is unusable and not used.

    And so on.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Heger@21:1/5 to All on Wed Jul 30 19:25:01 2025
    Am Dienstag000029, 29.07.2025 um 22:02 schrieb Paul.B.Andersen:
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to transfer
    a signal.


    E.g. if there is a large clock on the Moon, which we could read out by
    a large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on  the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
     "The two clocks synchronise if  tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?


    No, but in Einstein's paper.

    Actually I can almost sing 'On the Electrodynamics of moving bodies' and
    can assure you, that 'transit delay' or anything similar was neither calculated, measured or even mentioned.

    Einstein seemingly assumed, that the actual reading of the remote clock
    would be the remote time.

    To eleminate this error, you would need to 'ping' the remote station,
    measure the delay for a round trip, cut that in half (supposed the
    remote station is in relative rest) and add this value to your own time.

    Then you need to encode the own time plus delay into a signal and send
    that to the remote station.

    The remote station would need to decode the signal, extract the time
    value and adjust the own clockks according to that value.

    But Einstein didn't say anything like that.

    This problem was simply missing entirely in his paper.

    The main point is this:

    a 'clock' can also be a device, which has no hands and shows time values
    by electronic means. To this value you need to add the delay.

    These values need to be encoded somehow into a carrier signal. The
    encoded signal needs to be sent to the remote station, where someone
    decodes it.

    The sending station needs to know the delay in advance, hence had to
    measure it by measuring some sort of reflected message.

    This is equvalent to a 'ping' on the internet, but can be any kind of mechanism.

    If you don't do that, your process of synchronization is wrong.



    TH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul.B.Andersen@21:1/5 to All on Thu Jul 31 21:59:14 2025
    Den 30.07.2025 19:25, skrev Thomas Heger:
    Am Dienstag000029, 29.07.2025 um 22:02 schrieb Paul.B.Andersen:
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to
    transfer a signal.


    E.g. if there is a large clock on the Moon, which we could read out
    by a large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on  the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    Read this again when you have read my response below:


    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
      "The two clocks synchronise if  tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?


    No, but in Einstein's paper.

    Actually I can almost sing 'On the Electrodynamics of moving bodies' and
    can assure you, that 'transit delay' or anything similar was neither calculated, measured or even mentioned.

    Quote from § 1. Definition of Simultaneity:
    "we establish by definition that the “time” required by light
    to travel from A to B equals the “time” it requires to travel
    from B to A."

    "the time required by light to travel from A to B" _is_
    the 'transit delay' you say is never mentioned.

    Another quote from § 1. Definition of Simultaneity:
    "In accordance with definition the two clocks synchronize if
    tB − tA = t′A − tB."

    If the clocks synchronise, then the transit delay for
    the pulse is tB − tA = t′A − tB.

    The transit delay is _measured_!

    So the transit delay is calculated, measured and mentioned.

    How did you manage to miss that?
    You must have a serious reading comprehension problem!


    Einstein seemingly assumed, that the actual reading of the remote clock
    would be the remote time.

    ??? Is the clock at B the "remote clock"?

    Do you mean that the actual reading of the clock at B
    is _not_ the time showed by clock B?

    Or what do you mean?


    To eleminate this error, you would need to 'ping' the remote station,
    measure the delay for a round trip, cut that in half (supposed the
    remote station is in relative rest) and add this value to your own time.

    There is no error to correct.


    Then you need to encode the own time plus delay into a signal and send
    that to the remote station.

    Good Grief! :-D


    1. The observer at A reads the time tA when the light pulse
    is sent. He reads the clock at A!

    2. The observer at B reads the time tB when the light pulse
    is reflected. He reads the clock at B!

    3. The observer at A reads the time t'A when he receives
    the reflected light pulse. He reads the clock at A!

    These are all the measurements that are done.
    Only local clocks are read.
    There is no "reading of the remote clock"!

    The observer at A has _measured_ the transit delay.
    It is (t'A-tA)/2 ! How did you manage to miss that?

    To check if the clock at B is synchronous the observers have
    to communicate. They can do it by shouting, send it by snail mail,
    E-post, a mobile phone or whatever.
    And there is not necessary to encrypt anything!

    If they find that their clocks are not synchronous, the clock
    at B can be corrected as I explained above,




    The remote station would need to decode the signal, extract the time
    value and adjust the own clockks according to that value.

    But Einstein didn't say anything like that.

    Quite. Einstein wasn't stupid!

    Now you can read my previous post quoted above again.

    But with your serious reading comprehension problem,
    you will probably not understand it.


    This problem was simply missing entirely in his paper.

    Right. All your problems are missing.

    There is no problem in his paper.



    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Fri Aug 1 16:50:11 2025
    Le 31/07/2025 à 21:59, "Paul.B.Andersen" a écrit :
    Den 30.07.2025 19:25, skrev Thomas Heger:
    Am Dienstag000029, 29.07.2025 um 22:02 schrieb Paul.B.Andersen:
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take
    the delay into account, which is caused by the time needed to
    transfer a signal.


    E.g. if there is a large clock on the Moon, which we could read out
    by a large telescope, the clock there would show a time ~1s too early.

    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on  the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    Read this again when you have read my response below:


    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
      "The two clocks synchronise if  tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?


    No, but in Einstein's paper.

    Actually I can almost sing 'On the Electrodynamics of moving bodies' and
    can assure you, that 'transit delay' or anything similar was neither
    calculated, measured or even mentioned.

    Quote from § 1. Definition of Simultaneity:
    "we establish by definition that the “time” required by light
    to travel from A to B equals the “time” it requires to travel
    from B to A."

    "the time required by light to travel from A to B" _is_
    the 'transit delay' you say is never mentioned.

    Another quote from § 1. Definition of Simultaneity:
    "In accordance with definition the two clocks synchronize if
    tB − tA = t′A − tB."

    If the clocks synchronise, then the transit delay for
    the pulse is tB − tA = t′A − tB.

    The transit delay is _measured_!

    So the transit delay is calculated, measured and mentioned.

    How did you manage to miss that?
    You must have a serious reading comprehension problem!


    Einstein seemingly assumed, that the actual reading of the remote clock
    would be the remote time.

    ? ? ? Is the clock at B the "remote clock"?

    Do you mean that the actual reading of the clock at B
    is _not_ the time showed by clock B?

    Or what do you mean?


    To eleminate this error, you would need to 'ping' the remote station,
    measure the delay for a round trip, cut that in half (supposed the
    remote station is in relative rest) and add this value to your own time.

    There is no error to correct.


    Then you need to encode the own time plus delay into a signal and send
    that to the remote station.

    Good Grief! :-D


    1. The observer at A reads the time tA when the light pulse
    is sent. He reads the clock at A!

    2. The observer at B reads the time tB when the light pulse
    is reflected. He reads the clock at B!

    3. The observer at A reads the time t'A when he receives
    the reflected light pulse. He reads the clock at A!

    These are all the measurements that are done.
    Only local clocks are read.
    There is no "reading of the remote clock"!

    The observer at A has _measured_ the transit delay.
    It is (t'A-tA)/2 ! How did you manage to miss that?

    To check if the clock at B is synchronous the observers have
    to communicate. They can do it by shouting, send it by snail mail,
    E-post, a mobile phone or whatever.
    And there is not necessary to encrypt anything!

    If they find that their clocks are not synchronous, the clock
    at B can be corrected as I explained above,




    The remote station would need to decode the signal, extract the time
    value and adjust the own clockks according to that value.

    But Einstein didn't say anything like that.

    Quite. Einstein wasn't stupid!

    Now you can read my previous post quoted above again.

    But with your serious reading comprehension problem,
    you will probably not understand it.


    This problem was simply missing entirely in his paper.

    Right. All your problems are missing.

    There is no problem in his paper.

    Moreover Thomas could see this procedure in action at https://noedge.ne/e/


    He could even check the source code and see Einstein's very equation are
    used to compute the delay to be applied to any of both clocks or both.

    Replaying the synchronisation checking procedure allow te see how it is reflexive and symmetric.

    I may add more clocks to illustrate that the procedure is transitive.

    Which all that is needed to dismiss idiotic Hachel's claims btw...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Fri Aug 1 16:51:29 2025
    Le 01/08/2025 à 18:50, Python a écrit :
    Le 31/07/2025 à 21:59, "Paul.B.Andersen" a écrit :
    Den 30.07.2025 19:25, skrev Thomas Heger:
    Am Dienstag000029, 29.07.2025 um 22:02 schrieb Paul.B.Andersen:
    Den 29.07.2025 09:48, skrev Thomas Heger:

    Einstein wrote about a process for synchronization, which didn't take >>>>> the delay into account, which is caused by the time needed to
    transfer a signal.


    E.g. if there is a large clock on the Moon, which we could read out
    by a large telescope, the clock there would show a time ~1s too early. >>>>
    You can in principle sync a clock on the Moon with a clock on
    the Earth if we do it when the distance Moon-Earth is fairly
    constant for a few seconds, that is at the apogee or perigee,
    and the observer at Earth and the observer on  the Moon are
    where they will see the other body at zenith.

    The clocks wouldn't stay synchronous for long because
    the clocks are at different gravitational potential.
    But let's ignore this problem for now.

    ---------------------

    Read this again when you have read my response below:


    We have an observer at point A on the Earth and another observer
    at point B on the Moon. The observers have transceivers so they
    can communicate with each other.

    We have to equal clocks C_A and C_B. They are not synced in any
    way, but they are using the same time unit second.
    The clocks run at the same rate as defined by SI.

    At point A the observer has the following instruments:
    Clock C_A, a light-detector, and a powerful laser.
    The computer can register the time shown by C_A when
    the laser is fired, and when the light-detector registers
    a laser pulse from the Moon.

    At point B the observer has the following instruments:
    Clock C_B, a light-detector, a mirror and a computer.
    The computer can register the time shown by C_B when
    the light-detector registers a laser pulse from the Earth.

    Now the observer at A fires the laser.
    At this instant, C_A is showing tA seconds.

    When the laser pulse hits the mirror and the light-detector at B,
    Clock C_B shows tx seconds.

    Some time later the light detector at A registers
    the laser pulse reflected by the mirror at B.
    At this instant Clock C_A shows t'A seconds.

    Now the observer at Earth can communicate with the Moon observer
    and tell him that clock C_A showed tA when the laser pulse was
    sent, and t'A when the reflected laser pulse was received.

    The Moon observer knows that according to Einstein:
      "The two clocks synchronise if  tB − tA = t'A − tB."

    So he knows that to be in sync, clock C_B should have shown
    tB = (tA + t'A)/2

    But since it showed tx, he must add the correction:
    δ = tB - tx = (tA + t'A)/2 - tx

    So when he corrects the clock C_B with δ seconds,
    it will be in synch with clock C_A.

    Do you miss a delay in the above?


    No, but in Einstein's paper.

    Actually I can almost sing 'On the Electrodynamics of moving bodies' and >>> can assure you, that 'transit delay' or anything similar was neither
    calculated, measured or even mentioned.

    Quote from § 1. Definition of Simultaneity:
    "we establish by definition that the “time” required by light
    to travel from A to B equals the “time” it requires to travel
    from B to A."

    "the time required by light to travel from A to B" _is_
    the 'transit delay' you say is never mentioned.

    Another quote from § 1. Definition of Simultaneity:
    "In accordance with definition the two clocks synchronize if
    tB − tA = t′A − tB."

    If the clocks synchronise, then the transit delay for
    the pulse is tB − tA = t′A − tB.

    The transit delay is _measured_!

    So the transit delay is calculated, measured and mentioned.

    How did you manage to miss that?
    You must have a serious reading comprehension problem!


    Einstein seemingly assumed, that the actual reading of the remote clock
    would be the remote time.

    ? ? ? Is the clock at B the "remote clock"?

    Do you mean that the actual reading of the clock at B
    is _not_ the time showed by clock B?

    Or what do you mean?


    To eleminate this error, you would need to 'ping' the remote station,
    measure the delay for a round trip, cut that in half (supposed the
    remote station is in relative rest) and add this value to your own time.

    There is no error to correct.


    Then you need to encode the own time plus delay into a signal and send
    that to the remote station.

    Good Grief! :-D


    1. The observer at A reads the time tA when the light pulse
    is sent. He reads the clock at A!

    2. The observer at B reads the time tB when the light pulse
    is reflected. He reads the clock at B!

    3. The observer at A reads the time t'A when he receives
    the reflected light pulse. He reads the clock at A!

    These are all the measurements that are done.
    Only local clocks are read.
    There is no "reading of the remote clock"!

    The observer at A has _measured_ the transit delay.
    It is (t'A-tA)/2 ! How did you manage to miss that?

    To check if the clock at B is synchronous the observers have
    to communicate. They can do it by shouting, send it by snail mail,
    E-post, a mobile phone or whatever.
    And there is not necessary to encrypt anything!

    If they find that their clocks are not synchronous, the clock
    at B can be corrected as I explained above,




    The remote station would need to decode the signal, extract the time
    value and adjust the own clockks according to that value.

    But Einstein didn't say anything like that.

    Quite. Einstein wasn't stupid!

    Now you can read my previous post quoted above again.

    But with your serious reading comprehension problem,
    you will probably not understand it.


    This problem was simply missing entirely in his paper.

    Right. All your problems are missing.

    There is no problem in his paper.

    Moreover Thomas could see this procedure in action at https://noedge.ne/e/

    https://noedge.net/e/

    He could even check the source code and see Einstein's very equation are used to
    compute the delay to be applied to any of both clocks or both.

    Replaying the synchronisation checking procedure allow te see how it is reflexive and symmetric.

    I may add more clocks to illustrate that the procedure is transitive.

    Which all that is needed to dismiss idiotic Hachel's claims btw...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Fri Aug 1 19:39:49 2025
    Le 01/08/2025 à 21:25, Richard Hachel a écrit :
    Le 01/08/2025 à 18:50, Python a écrit :
    Le 31/07/2025 à 21:59, "Paul.B.Andersen" a écrit :

    Which all that is needed to dismiss idiotic Hachel's claims btw..

    :))

    R.H.

    Either you like it or it is the case.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hachel@21:1/5 to All on Fri Aug 1 19:25:53 2025
    Le 01/08/2025 à 18:50, Python a écrit :
    Le 31/07/2025 à 21:59, "Paul.B.Andersen" a écrit :

    Which all that is needed to dismiss idiotic Hachel's claims btw..

    :))

    R.H.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Fri Aug 1 19:52:04 2025
    Le 01/08/2025 à 21:25, Richard Hachel a écrit :
    Le 01/08/2025 à 18:50, Python a écrit :
    Le 31/07/2025 à 21:59, "Paul.B.Andersen" a écrit :

    Which all that is needed to dismiss idiotic Hachel's claims btw..

    :))

    R.H.

    Youu like it or not it is the case.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Sat Aug 2 12:35:40 2025
    Den 30.07.2025 12:54, skrev Python:

    Thomas could even see the delay applied according to the exact equations
    from Einstein's article as used in my Web app there: https://noedge.net/e/



    Nice!

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Sat Aug 2 12:31:57 2025
    Den 30.07.2025 07:08, skrev Maciej Woźniak:

    SI idiocy is unusable and not used.

    Another wise statement by Maciej Woźniak! :-D

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Paul B. Andersen on Sat Aug 2 13:52:45 2025
    On 8/2/2025 12:31 PM, Paul B. Andersen wrote:
    Den 30.07.2025 07:08, skrev Maciej Woźniak:

    SI idiocy is unusable and not used.

    Another wise statement by Maciej Woźniak! :-D

    Raving and spitting wont help, poor fanatic,
    no serious timekeeping system keeps its clocks
    matching that nonsense and you've admitted
    it many times. Eben such a disgusting piece
    of lying shit can't lie non stop.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Sat Aug 2 12:01:21 2025
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Sat Aug 2 12:36:03 2025
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    and you can do nothing
    about it apart of spitting, insulting and slandering.

    Except that I, and other, has shown how ridiculous your alleged "proof"
    is.

    And you're just doing what you can for your beloved
    Shit and your beloved church.

    No I do that because I'm disgusted by deluded liar of your kind.

    And for fun too.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Sat Aug 2 14:17:18 2025
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent, and you can do nothing
    about it apart of spitting, insulting and slandering.
    And you're just doing what you can for your beloved
    Shit and your beloved church.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Sat Aug 2 17:26:17 2025
    On 8/2/2025 2:36 PM, Python wrote:
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    Surely I did, I've poined directly
    2 denying themsellf claims derivable
    in the idiot's physics. A piece of
    fanatic shit screaming "NO!!!!!"
    spitting and slandering is changing
    nothing, sorry.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Sat Aug 2 17:14:05 2025
    Le 02/08/2025 à 17:26, Maciej Woźniak a écrit :
    On 8/2/2025 2:36 PM, Python wrote:
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    Surely I did

    No you didn't.

    I, and others, have shown how ridiculous your alleged "proof" is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Sat Aug 2 19:29:57 2025
    On 8/2/2025 7:14 PM, Python wrote:
    Le 02/08/2025 à 17:26, Maciej Woźniak a écrit :
    On 8/2/2025 2:36 PM, Python wrote:
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    Surely I did

    No you didn't.


    Surely I did, I've poined directly
    2 denying themsellf claims derivable
    in the idiot's physics. A piece of
    fanatic shit screaming "NO!!!!!"
    spitting and slandering is changing
    nothing, sorry.


    I, and others, have shown how ridiculous your alleged "proof" is.

    You waved arms, spitted and slandered.
    And others.
    Relativistic idiots rarely (if ever)
    are able to do more.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Python@21:1/5 to All on Sat Aug 2 18:28:41 2025
    Le 02/08/2025 à 19:29, Maciej Woźniak a écrit :
    On 8/2/2025 7:14 PM, Python wrote:
    Le 02/08/2025 à 17:26, Maciej Woźniak a écrit :
    On 8/2/2025 2:36 PM, Python wrote:
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    Surely I did

    No you didn't.


    Surely I did

    No, you didn't.

    I, and others, have shown how ridiculous your alleged "proof" is.

    You waved arms, spitted and slandered.
    And others.

    No, this not what we did. This what you do anyway.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@21:1/5 to Python on Sat Aug 2 21:22:06 2025
    On 8/2/2025 8:28 PM, Python wrote:
    Le 02/08/2025 à 19:29, Maciej Woźniak a écrit :
    On 8/2/2025 7:14 PM, Python wrote:
    Le 02/08/2025 à 17:26, Maciej Woźniak a écrit :
    On 8/2/2025 2:36 PM, Python wrote:
    Le 02/08/2025 à 14:17, Maciej Woźniak a écrit :
    On 8/2/2025 2:01 PM, Python wrote:
    Le 02/08/2025 à 13:52, Maciej Woźniak a écrit :
    ... a disgusting piece of lying shit can't lie non stop.

    You are a proof that it may, Maciej.

    See, poor stinker - I've proven the mumble of your idiot
    guru to be not even consistent

    You did nothing of this kind.

    Surely I did

    No you didn't.


    Surely I did

    No, you didn't.

    Surely I did, I've poined directly
    2 denying themsellf claims derivable
    in the idiot's physics. A piece of
    fanatic shit screaming "NO!!!!!"
    spitting and slandering is changing
    nothing, sorry.


    I, and others, have shown how ridiculous your alleged "proof" is.

    You waved arms, spitted and slandered.
    And others.

    No, this not what we did.

    Yes, that's exactly what you did.

    This what you do anyway.

    I've proven the mumble of your idiot guru
    to be not even consistent, and some
    brainwashed doggies screaming "NOOOOO!!!"
    and barking are not changing that,
    sorry, poor stinker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Heger@21:1/5 to All on Sun Aug 3 08:13:14 2025
    Am Samstag000002, 02.08.2025 um 12:35 schrieb Paul B. Andersen:
    Den 30.07.2025 12:54, skrev Python:

    Thomas could even see the delay applied according to the exact
    equations from Einstein's article as used in my Web app there:
    https://noedge.net/e/



    Nice!


    Not nice!

    if you criticize me, than you would need to present a quote from
    Einstein's 'On the electrodynamics of moving bodies', where Einstein
    calculated the delay or eventually mentioned the word 'delay'.

    Also possible would be any statement, where Einstein wrote, that he had
    the intention to correct the actually reading of the remote clocks time
    by the delay for the signal transit.

    But none of the above was actually present in Einstein's paper.

    The only thing, which can actually be found is an equation, which would
    allow you to calculate the delay yourself.

    But that is, of course, not enough, since Einstein had to do that
    himself and had to write, how he wanted to deal with the delay.

    And THAT cannot be found in Einstein's paper.

    TH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)