Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.physics.relativity > #674529 > unrolled thread
| Started by | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| First post | 2026-10-17 09:11 +0200 |
| Last post | 2026-10-17 18:57 -0700 |
| Articles | 20 on this page of 192 — 12 participants |
Back to article view | Back to sci.physics.relativity
Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 09:11 +0200
Re: Words have power Truman Babichev <avbb@bi.ru> - 2026-10-17 09:58 +0000
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 13:08 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 18:25 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 16:32 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 18:46 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 16:49 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 18:55 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:04 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:14 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:18 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:21 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:23 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:29 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:31 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:36 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:38 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:44 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:46 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 19:55 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 17:57 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 20:09 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 23:39 +0000
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-17 19:03 -0700
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 07:50 +0200
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 11:24 -0700
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 20:44 +0200
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 12:02 -0700
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 21:54 +0200
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 13:31 -0700
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 22:45 +0200
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 15:56 -0700
Re: Words have power Russell Bahmutoff <sm@temar.ru> - 2026-10-17 19:17 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 22:19 +0200
Re: Words have power Fermin Ribakov <ifrbn@iobf.ru> - 2026-10-17 21:03 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 07:46 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-17 23:37 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 07:47 +0200
Re: Words have power Kevvy Ruzaev <vvavv@vrzrz.ru> - 2026-10-18 07:51 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 10:16 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 11:00 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 13:54 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 11:57 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 14:10 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 12:13 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 14:20 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 12:23 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 14:28 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 12:36 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 14:39 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-18 12:42 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 14:44 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 10:43 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 13:05 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 11:15 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 13:21 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 11:42 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 13:53 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 12:07 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 14:19 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 12:31 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 14:44 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 12:59 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 15:16 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 13:38 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 15:49 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 13:58 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 16:02 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 14:06 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 16:26 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 14:28 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 16:39 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 15:37 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 18:37 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 16:42 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 18:51 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 16:53 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 19:02 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 17:03 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 19:11 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 17:23 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-19 19:37 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-19 21:55 +0000
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-19 15:10 -0700
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-19 15:27 -0700
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 07:23 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 08:00 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 10:26 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 08:34 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 10:54 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 09:25 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 12:10 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 10:18 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 12:32 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 10:39 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 12:44 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 10:55 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 13:09 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 11:11 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 13:22 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 11:37 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 13:44 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 11:48 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 13:55 +0200
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 14:03 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 15:29 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 17:57 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 16:03 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 18:13 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 16:15 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 18:27 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 16:51 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 19:12 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 17:17 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 19:33 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 20:25 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 23:07 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 21:15 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-20 23:34 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 21:39 +0000
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 21:52 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-21 06:40 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-21 14:51 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-21 17:03 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-21 15:04 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-21 17:16 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-21 17:45 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-21 20:07 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-21 23:20 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 07:05 +0200
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 07:21 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 11:27 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 14:28 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 12:31 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 14:38 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 13:46 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 15:53 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 14:02 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 16:29 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 15:23 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 18:35 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 16:46 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 18:55 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 17:11 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 19:18 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 17:21 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 19:31 +0200
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-22 21:08 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-22 22:04 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 06:53 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 09:01 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 12:22 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 10:27 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 12:32 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 10:33 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 12:40 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 10:41 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 12:45 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 10:49 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 12:51 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 10:56 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:06 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 11:11 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:19 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 11:33 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:36 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 11:43 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:50 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 11:51 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:53 +0200
Re: Words have power Python <python@cccp.invalid> - 2026-10-23 11:55 +0000
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-23 13:56 +0200
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-20 15:28 -0700
Re: Words have power Python <python@cccp.invalid> - 2026-10-20 22:32 +0000
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-20 07:11 -0700
Re: Words have power Salvado Bazarov <avvazv@vzbb.ru> - 2026-10-19 19:07 +0000
Re: Words have power "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-19 14:39 -0700
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-18 04:58 -0700
Re: Words have power Dawn Rujenkov <jrdj@een.ru> - 2026-10-18 16:55 +0000
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 13:34 -0700
Re: Words have power The Starmaker <starmaker@ix.netcom.com> - 2026-10-17 22:19 -0700
Re: Words have power nospam@de-ster.demon.nl (J. J. Lodder) - 2026-10-17 22:37 +0200
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-17 22:47 +0200
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-17 19:00 -0700
Re: Words have power nospam@de-ster.demon.nl (J. J. Lodder) - 2026-10-18 12:30 +0200
Re: Words have power Maciej Woźniak <mlwozniak@wp.pl> - 2026-10-18 12:42 +0200
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-18 04:56 -0700
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-18 07:07 -0700
Re: Words have power nospam@de-ster.demon.nl (J. J. Lodder) - 2026-10-18 21:39 +0200
Re: Words have power Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-19 00:56 -0700
Re: Words have power (perspective geomtry) Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-17 09:15 -0700
Re: Words have power (perspective geometry) Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-10-17 18:57 -0700
Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-22 18:35 +0200 |
| Message-ID | <18e0e746668e0e12$41747$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674832 |
On 10/22/2026 5:23 PM, Python wrote: > Maciej, > >> If the clocks didn't fit your "perfection differently" - they >> wouldn't be sent. > > Ah, excellent. A new escape hatch: selection bias. > > Unfortunately it still doesn't produce the number. And even more unfortunately - the REAL value of the difference of the clock indications (i.e. your time dilation), measured by correctly calibrated clocks, as close to perfection as our best engineers can get - is 0. Common sense has been warning your idiot guru.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-22 16:46 +0000 |
| Message-ID | <zAh7OTvlk_wXXgdt34ad6e8JBdE@jntp> |
| In reply to | #674834 |
> the REAL value of the difference
> of the clock indications [...] is 0.
Yes.
AFTER COMPENSATION.
You keep presenting this as a revelation when it is literally the
purpose of the compensation.
NTS-2:
correction OFF:
predicted rate difference: +446.5 × 10^-12
measured rate difference: +442.5 × 10^-12
correction ON:
resulting difference: approximately 0
And your argument is:
"LOOK! AFTER SUBTRACTING THE PREDICTED DIFFERENCE,
THE DIFFERENCE IS GONE!"
Yes, Maciej.
That's what subtraction does.
The interesting experimental question was whether the difference
existed BEFORE it was subtracted.
It did.
Its value was measured.
And relativity had predicted its value before launch.
You still haven't explained +442.5 × 10^-12.
You just keep pointing triumphantly at the zero obtained after
engineers cancelled it.
Subtraction followed by amnesia.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-22 18:55 +0200 |
| Message-ID | <18e0e854ed9ed611$44063$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674835 |
On 10/22/2026 6:46 PM, Python wrote: >> the REAL value of the difference >> of the clock indications [...] is 0. > > Yes. > > AFTER COMPENSATION. > > You keep presenting this as a revelation when it is literally the Adjustment is THE KEY, DECISIVE factor here. Even such an idiot as you are has admitted. Now - your moronic prophet was too dumb to even notice that the factor exists and you're waving your arms and screaming "LOOK!!!! A GREAT SUCCESS!!! THE PROPHECY WORKS PERFECTLY!!! AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!" It's not, of course, that one could expect any better logic from a brainwashed fanatic idiot.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-22 17:11 +0000 |
| Message-ID | <9rODQPozBHZgaQxw2QLVMWBxdHc@jntp> |
| In reply to | #674837 |
Maciej,
You're looping.
> Adjustment is THE KEY, DECISIVE factor here.
For the FINAL clock indication.
Not for measuring what the clock does when that adjustment is OFF.
This really should not require another fifty posts.
NTS-2 deliberately did:
adjustment OFF
prediction: +446.5 × 10^-12
measurement: +442.5 × 10^-12
Your response is still:
"BUT ADJUSTMENT IS DECISIVE!"
Yes. That's why they switched it OFF.
The experiment was specifically designed to remove your "KEY, DECISIVE
factor" and measure the physical rate shift independently of it.
Then, after measuring the predicted shift, they switched the adjustment
ON and cancelled it for operational use.
You keep screaming that Einstein failed to predict the adjustment.
Nobody claims relativity predicts what knob an engineer will turn.
It predicts how far the knob needs to be turned.
And that is the number you have spent several days desperately avoiding:
predicted: +446.5 × 10^-12
measured: +442.5 × 10^-12
Your "common sense" still predicts no number at all.
Apparently it is excellent at shouting "ADJUST THE CLOCK!" but becomes
remarkably shy when asked:
BY HOW MUCH?
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-22 19:18 +0200 |
| Message-ID | <18e0e999fbe9eca3$42699$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674839 |
On 10/22/2026 7:11 PM, Python wrote: > Maciej, > > You're looping. > >> Adjustment is THE KEY, DECISIVE factor here. > > For the FINAL clock indication. And for time, i.e. "what clocks indicate", poor piece of shit. It's not any magical power of your moronic formulas, it's designing, crafting and adjusting. And, of course - if your mad religion succeeded in forcing the users to adjust the clocks its "PROPER!!! CORRECT!!! PERFECT!!! MATCHING THE SI STANDARD!!!" way its mad prophecies would be fulfilled. But there was really never any hope for that. Common sense has been warning the idiot.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-22 17:21 +0000 |
| Message-ID | <h4jJ-2jEvMLz7AFlqZ3ZTT3CWwE@jntp> |
| In reply to | #674840 |
Maciej,
> And for time, i.e. "what clocks indicate"
No. You are once again confusing three different things:
1. how a physical clock naturally runs under given conditions;
2. how engineers deliberately adjust it;
3. what it indicates after that adjustment.
NTS-2 separated 1 and 2 experimentally.
With the relativistic correction DISABLED, the clock did not magically
choose its indication because an engineer "crafted" it that way.
Its orbital rate shifted.
predicted before launch: +446.5 × 10^-12
measured in orbit: +442.5 × 10^-12
Then engineers deliberately changed its rate.
> if your mad religion succeeded in forcing the users to adjust the clocks
This is becoming hilarious.
Relativity did not "force" the clock to be adjusted so that its
prediction would come true.
THE PREDICTION CAME TRUE WITH THE ADJUSTMENT OFF.
The adjustment was applied afterwards to CANCEL the predicted effect.
You have now managed to reverse the chronology completely:
relativity predicts X
experiment with correction OFF measures X
engineers later compensate X
Maciej: "AHA! THE COMPENSATION CAUSED THE PROPHECY TO COME TRUE!"
No.
The prophecy had already come true.
The compensation made its operational consequence disappear.
And after all these posts, you still cannot answer the embarrassingly
simple question:
Why did an uncorrected clock produce +442.5 × 10^-12
when relativity had predicted +446.5 × 10^-12?
"DESIGNING! CRAFTING! ADJUSTING!"
is not a calculation.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-22 19:31 +0200 |
| Message-ID | <18e0ea567f288456$41753$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674841 |
On 10/22/2026 7:21 PM, Python wrote: > Maciej, > >> And for time, i.e. "what clocks indicate" > > No. Yes, poor piece of shit, yes. And, of course - if your mad religion succeeded in forcing the users to adjust the clocks its "PROPER!!! CORRECT!!! PERFECT!!! MATCHING THE SI STANDARD!!!" way its mad prophecies would be fulfilled. But there was really never any hope for that. Common sense has been warning the idiot. >> if your mad religion succeeded in forcing the users to adjust the clocks > > This is becoming hilarious. > > Relativity did not "force" the clock to be adjusted so that its > prediction would come true. Of course it didn't - the clocks keep measuring t'=t just like they always did. It was just trying. Wasted efforts, common sense has been warning the idiot.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-22 21:08 +0200 |
| Message-ID | <18e0ef9b7b3513f5$42706$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674842 |
On 10/22/2026 7:31 PM, Maciej Woźniak wrote: >> >> Relativity did not "force" the clock to be adjusted so that its >> prediction would come true. > > Of course it didn't - the clocks keep measuring > t'=t just like they always did. It was just > trying. Wasted efforts, common sense has been > warning the idiot. You did your best, poor piece of shit. You were chanting "PROPER!!! CORRECT!!! PERFECT!!!" as loudly as you could. You casted "bottles of vodka", "nurses" and tons of other shit at every opposition you meet... Wasted efforts. The clocks keep and will keep measuring t'=t, just like they always did.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-22 22:04 +0000 |
| Message-ID | <8HypgGlNNjP43aNBxuNEBrNqEIo@jntp> |
| In reply to | #674842 |
Maciej,
> the clocks keep measuring t'=t just like they always did.
No.
The NTS-2 clock, with the relativistic correction OFF, measured:
t' != t
More precisely, its rate differed by:
measured: +442.5 × 10^-12
where relativity had predicted:
predicted: +446.5 × 10^-12
Only AFTER compensation was the operational result brought back toward:
t' = t
You are now simply taking the result AFTER engineers deliberately
cancelled the rate difference and pretending it was also the result
BEFORE they cancelled it.
It wasn't.
That's exactly why the first 20 days of NTS-2 matter.
Correction OFF: 442.5 × 10^-12.
Correction ON: approximately zero.
Your entire argument requires those two experiments to have had the
same result.
They didn't.
And shouting "t'=t" cannot retroactively change what the uncorrected
clock measured.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 06:53 +0200 |
| Message-ID | <18e10f878fc81781$123$2210059$c2265aab@news.newsdemon.com> |
| In reply to | #674849 |
On 10/23/2026 12:04 AM, Python wrote: > Maciej, > >> the clocks keep measuring t'=t just like they always did. > > No. > > The NTS-2 clock, with the relativistic correction OFF, measured: > > t' != t As long as the key, decisive factor wasn't involved. > > You are now simply taking the result AFTER engineers deliberately Excuse me, poor piece of shit, weren't the clocks of Newtonian physicists deliberately calibrated? Your shitty revolution has changed NOTHING. The clocks keep doing what they always did, it's just that your bunch of fanatics is grumbling that it's incorrect, improper and dirty, and it shouldn't be taken into account.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-23 09:01 +0000 |
| Message-ID | <l1nziLJKYKkag2XA2p_hyS1A9Xk@jntp> |
| In reply to | #674858 |
Maciej,
> weren't the clocks of Newtonian physicists
> deliberately calibrated?
Of course.
And once again: calibration does not explain the number.
Calibrate two cesium clocks together on Earth.
Put one into the NTS-2 orbit.
Leave the relativistic correction OFF.
What happens?
Relativity, BEFORE launch:
+446.5 × 10^-12
Experiment:
+442.5 × 10^-12
"Newtonian physicists calibrated clocks too" predicts neither number.
> Your shitty revolution has changed NOTHING.
Except, inconveniently, the quantitative prediction of what happens
when that calibrated clock is moved into a different gravitational
potential and velocity.
That is precisely what was tested.
Your argument has now reached:
"Clocks were calibrated before Einstein,
therefore relativity predicts nothing about clocks."
Thermometers were calibrated before statistical mechanics too.
So what?
> The clocks keep doing what they always did
YES.
And relativity predicts what they do.
That is the part you keep desperately walking around.
Nobody needed Einstein to invent calibration.
They needed physics to calculate how much the clock rate would change.
NTS-2 supplied a wonderfully simple comparison:
Einstein: +446.5 × 10^-12
experiment: +442.5 × 10^-12
Maciej: "CLOCKS WERE CALIBRATED BEFORE EINSTEIN!"
Still waiting for your number.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 12:22 +0200 |
| Message-ID | <18e121843ff9f4d0$338$2205363$c2065a8b@news.newsdemon.com> |
| In reply to | #674863 |
On 10/23/2026 11:01 AM, Python wrote: > Maciej, > >> weren't the clocks of Newtonian physicists >> deliberately calibrated? > > Of course. > > And once again: calibration does not explain the number. > > Calibrate two cesium clocks together on Earth. > > Put one into the NTS-2 orbit. > > Leave the relativistic correction OFF. > > What happens? > > Relativity, BEFORE launch: > > +446.5 × 10^-12 > > Experiment: > > +442.5 × 10^-12 See, poor piece of shit - science has been working with scientists for centuries. Its idiotproofness is amazing. Even such a nonsensical crap as The Shit of Einstein can have some correct predictions and be squeezed for some usable information. And if your mad religion limited itself to things it's familiar with, including your "clock rates" I wouldn't be here fighting it. But no - it had to start babbling about the indications of perfect clocks. Too bad for it.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-23 10:27 +0000 |
| Message-ID | <noJLZC6LG6XNM3B9EvFddtrxO2s@jntp> |
| In reply to | #674865 |
Maciej,
Ah.
So after several days of:
"t'=t!"
"just clock error!"
"adjustment is THE KEY!"
"your prophecy failed!"
we finally arrive at:
> Even such a nonsensical crap as The Shit of Einstein can
> have some correct predictions
Thank you.
That was the point.
Relativity predicted the orbital clock-rate shift quantitatively:
predicted: +446.5 × 10^-12
measured: +442.5 × 10^-12
So the effect was not created by adjustment, calibration, religion,
terminology, or engineers being bullied by Einstein.
It was predicted and then measured with the correction OFF.
Now you retreat to:
> But [...] it had to start babbling about
> the indications of perfect clocks.
There is no retreat available there either.
An ideal clock in relativity is simply a theoretical clock whose
reading follows proper time along its worldline.
"Perfect" does NOT mean:
"a clock magically adjusted so that its indication must remain
equal to every other clock everywhere."
That is your definition, not relativity's.
And this distinction is exactly what the experiment demonstrates:
two clocks can be perfectly good clocks and nevertheless accumulate
different elapsed times along different worldlines.
You may dislike calling that "proper time".
You may dislike "ideal clock".
You may dislike Einstein.
But after finally conceding that the quantitative prediction is
correct, changing the vocabulary won't make
442.5 × 10^-12
turn back into zero.
You've spent days fighting the physics.
Now that you've conceded the physics, you're fighting the dictionary.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 12:32 +0200 |
| Message-ID | <18e122061900cb2f$347$2205363$c2065a8b@news.newsdemon.com> |
| In reply to | #674867 |
On 10/23/2026 12:27 PM, Python wrote: > Maciej, > > Ah. > > So after several days of: > > "t'=t!" > "just clock error!" > "adjustment is THE KEY!" > "your prophecy failed!" > > we finally arrive at: > >> Even such a nonsensical crap as The Shit of Einstein can >> have some correct predictions > > Thank you. > > That was the point. > > Relativity predicted the orbital clock-rate shift quantitatively: It has also predicted, also quantitatively - difference in clock indication in GPS. Bullshit, the measured value is 0, even such a disgusting piece of lying shit as you are is admitting that sometimes. And if your mad religion limited itself to things it's familiar with, including your "clock rates" I wouldn't be here fighting it. But no - it had to start babbling about the indications of perfect clocks. Too bad for it.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-23 10:33 +0000 |
| Message-ID | <SjOop2Dgub9y2pT6hNNqoDaa3mc@jntp> |
| In reply to | #674869 |
Maciej,
> It has also predicted, also quantitatively -
> difference in clock indication in GPS.
> Bullshit, the measured value is 0
No.
You are STILL confusing the physical prediction with the engineered
output after compensation.
Relativity predicts that, if you take suitable clocks along the two
different worldlines WITHOUT compensating their relative rates, their
elapsed-time readings diverge.
NTS-2 tested precisely that situation:
relativistic correction OFF
predicted fractional rate difference:
+446.5 × 10^-12
measured fractional rate difference:
+442.5 × 10^-12
A nonzero rate difference accumulated over time IS a growing difference
in clock indications.
Then engineers compensated the rate difference so that GPS clocks would
remain aligned with GPS system time.
And, astonishingly:
compensated difference ≈ 0
You keep calling that zero the "measured value" of the relativistic
effect.
It is the measured RESIDUAL AFTER CANCELLING the relativistic effect.
If
natural drift = +38 µs/day
and engineers apply
correction = -38 µs/day,
then obtaining
residual ≈ 0
does not demonstrate that the natural drift was zero.
It demonstrates that the correction worked.
And this makes your new concession particularly fatal:
> including your "clock rates"
You now concede that relativity correctly predicts the clock-rate
difference.
Maciej, integrate a nonzero rate difference over time.
What do you get?
A difference in clock indications.
There is no magical firewall between "clock rates" and "clock
indications".
The latter is the integral of the former.
Your entire remaining argument is therefore:
"I concede the derivative, but deny that integrating it
changes the function."
Good luck with that.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 12:40 +0200 |
| Message-ID | <18e122782cf001f2$346$2210059$c2265aab@news.newsdemon.com> |
| In reply to | #674871 |
On 10/23/2026 12:33 PM, Python wrote: > Maciej, > >> It has also predicted, also quantitatively - >> difference in clock indication in GPS. >> Bullshit, the measured value is 0 > > No. Yes. And even such a pathetic piece of shit as you are is admitting it sometimes. Let's try again: the indication of a clock from GPS ground base is - 2026-10-23 15:00:00.00000000. What is the [measured] indication of a clock in a GPS satellite?
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-23 10:41 +0000 |
| Message-ID | <VDED9M-BW5Et9POWANnx8Filv4c@jntp> |
| In reply to | #674874 |
Maciej,
> the indication of a clock from GPS ground base is -
> 2026-10-23 15:00:00.00000000.
> What is the [measured] indication of a clock in
> a GPS satellite?
After the GPS clock has been deliberately frequency-offset and its
remaining clock offset/drift corrections have been applied?
Approximately:
2026-10-23 15:00:00.00000000
within the accuracy of the system.
Nobody disputes that.
Now remove the relativistic frequency compensation.
After one day, approximately:
ground: 2026-10-24 15:00:00.000000
satellite: 2026-10-24 15:00:00.000038
That's precisely the point.
You are asking me for the output AFTER engineers have deliberately
cancelled the predicted rate difference, obtaining approximately zero,
and pretending this measures the rate difference BEFORE cancellation.
It doesn't.
And you've just conceded that relativity correctly predicts the
"clock rates".
So your argument has become mathematically spectacular:
d(satellite time - ground time)/dt != 0
but somehow, according to Maciej,
satellite time - ground time = 0
forever.
Calculus would like a word.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 12:45 +0200 |
| Message-ID | <18e122c456a30f4a$361$2205363$c2065a8b@news.newsdemon.com> |
| In reply to | #674875 |
On 10/23/2026 12:41 PM, Python wrote: > Maciej, > >> the indication of a clock from GPS ground base is - >> 2026-10-23 15:00:00.00000000. >> What is the [measured] indication of a clock in >> a GPS satellite? > > After the GPS clock has been deliberately frequency-offset and its > remaining clock offset/drift corrections have been applied? > > Approximately: > > 2026-10-23 15:00:00.00000000 Yes. The real, measured value of the difference in clock indications is - 0. Even such a disgusting piece of lying shit is admitting it, again.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-23 10:49 +0000 |
| Message-ID | <nr-gYKL7WU1sDhoKjlMOFOi2rRE@jntp> |
| In reply to | #674877 |
Maciej,
> The real, measured value of the difference
> in clock indications is - 0.
AFTER COMPENSATION.
Yes.
Nobody has denied this. Ever.
Now let's try your reasoning on something simpler:
natural drift: +38 µs/day
applied correction: -38 µs/day
measured residual: 0 µs/day
Maciej concludes:
"THE REAL MEASURED DRIFT IS ZERO!"
No.
The real measured RESIDUAL is zero.
The natural drift was measured separately, with the correction OFF.
And this is not hypothetical:
NTS-2 correction OFF:
measured rate shift = +442.5 × 10^-12
You are deliberately choosing the compensated observable and calling it
the uncompensated observable.
That's like applying a 10 kg counterweight, observing that a scale is
balanced, and triumphantly announcing:
"THE REAL MEASURED WEIGHT IS ZERO!"
No.
The zero is the result AFTER compensation.
And the funniest part is that you have now conceded that relativity
correctly predicts the clock-rate difference.
So we have reached:
nonzero rate difference: admitted
compensation of that rate difference: admitted
zero residual after compensation: admitted
and somehow your conclusion is:
therefore the uncompensated rate difference never existed.
Subtraction followed by amnesia, again.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-23 12:51 +0200 |
| Message-ID | <18e123199ad30c59$367$2205363$c2065a8b@news.newsdemon.com> |
| In reply to | #674880 |
On 10/23/2026 12:49 PM, Python wrote: > Maciej, > >> The real, measured value of the difference >> in clock indications is - 0. > > AFTER COMPENSATION. Adjustment is THE KEY, DECISIVE factor here. Even such an idiot as you are has admitted. Now - your moronic prophet was too dumb to even notice that the factor exists and you're waving your arms and screaming "LOOK!!!! A GREAT SUCCESS!!! THE PROPHECY WORKS PERFECTLY!!! AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!" It's not, of course, that one could expect any better logic from a brainwashed fanatic idiot.
[toc] | [prev] | [next] | [standalone]
Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web