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 5 of 10 — ← Prev page 1 … 3 4 [5] 6 7 … 10 Next page →
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 17:23 +0000 |
| Message-ID | <On1xkI1G-pP4OL_LBmqBJIwbjyI@jntp> |
| In reply to | #674679 |
Maciej,
> "CALIBRATED CLOCKS!!! DELIBERATELY!!!
> DOESN'T COUNT!!!"
You're still confusing CALIBRATION with COMPENSATION.
The NTS-2 clock was not "calibrated" to accidentally produce
+442.5 × 10^-12.
Quite the opposite: the relativistic frequency correction was
deliberately left OFF for about 20 days so they could measure the
uncompensated orbital rate.
Relativity had already predicted:
+446.5 × 10^-12
They measured:
+442.5 × 10^-12
THEN the synthesizer correction was switched on.
Your version of experimental method is extraordinary:
prediction made before experiment
|
v
correction OFF
|
v
predicted effect observed
|
v
correction switched ON
|
v
effect compensated
|
v
Maciej: "SEE? ZERO!"
And your shark keeps screaming "2 kg of grass!" while carefully avoiding
the awkward detail that the theory specified the animal, the amount and
the circumstances BEFORE anybody weighed the grass.
Your competing theory remains:
something ate it.
Possibly for one of a billion reasons.
Science is usually a little more demanding.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 19:37 +0200 |
| Message-ID | <18dffee6a88b9967$8219$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674680 |
On 10/19/2026 7:23 PM, Python wrote: > Maciej, > >> "CALIBRATED CLOCKS!!! DELIBERATELY!!! >> DOESN'T COUNT!!!" > > You're still confusing CALIBRATION with COMPENSATION. Sure. Calibration is - when a piece of relativistic shit feels comfortable with calibration. Compensation, on the other hand is - when a piece of relativistic shit feels comfortable with compensation. Easy, isn't it? Anyway, of course, deliberate modifying measurement devices is only allowed when the result will fit One And Only True Shit of Einstein.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 21:55 +0000 |
| Message-ID | <-DWy3_VYBJ0ceRFOoSnRhkOvtxs@jntp> |
| In reply to | #674682 |
Maciej,
> deliberate modifying measurement devices is only allowed
> when the result will fit One And Only True Shit of Einstein.
You have managed to reverse the chronology again.
The correction was OFF.
OFF, Maciej.
That's precisely why NTS-2 was a test.
Relativity predicts: +446.5 × 10^-12
Correction: OFF
Clock measures: +442.5 × 10^-12
Only AFTER that measurement was the correction switched ON.
So your accusation is now:
"They modified the device to obtain the predicted result!"
when the predicted result was obtained while the modification you're
complaining about was explicitly disabled.
This is becoming difficult to parody.
You are doing it faster than I can.
[toc] | [prev] | [next] | [standalone]
| From | Ross Finlayson <ross.a.finlayson@gmail.com> |
|---|---|
| Date | 2026-10-19 15:10 -0700 |
| Message-ID | <hjOdnU-Y87_aCEv3nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #674689 |
On 10/19/2026 02:55 PM, Python wrote: > Maciej, > >> deliberate modifying measurement devices is only allowed >> when the result will fit One And Only True Shit of Einstein. > > You have managed to reverse the chronology again. > > The correction was OFF. > > OFF, Maciej. > > That's precisely why NTS-2 was a test. > > Relativity predicts: +446.5 × 10^-12 > Correction: OFF > Clock measures: +442.5 × 10^-12 > > Only AFTER that measurement was the correction switched ON. > > So your accusation is now: > > "They modified the device to obtain the predicted result!" > > when the predicted result was obtained while the modification you're > complaining about was explicitly disabled. > > This is becoming difficult to parody. > > You are doing it faster than I can. This is physics: not parody. (It is a bit parrot-y, ..., yet there aren't really bits for par-ity.) It's a gauge theory and a continuum mechanics.
[toc] | [prev] | [next] | [standalone]
| From | Ross Finlayson <ross.a.finlayson@gmail.com> |
|---|---|
| Date | 2026-10-19 15:27 -0700 |
| Message-ID | <yC2dnTv6J6jyBEv3nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #674692 |
On 10/19/2026 03:10 PM, Ross Finlayson wrote: > On 10/19/2026 02:55 PM, Python wrote: >> Maciej, >> >>> deliberate modifying measurement devices is only allowed >>> when the result will fit One And Only True Shit of Einstein. >> >> You have managed to reverse the chronology again. >> >> The correction was OFF. >> >> OFF, Maciej. >> >> That's precisely why NTS-2 was a test. >> >> Relativity predicts: +446.5 × 10^-12 >> Correction: OFF >> Clock measures: +442.5 × 10^-12 >> >> Only AFTER that measurement was the correction switched ON. >> >> So your accusation is now: >> >> "They modified the device to obtain the predicted result!" >> >> when the predicted result was obtained while the modification you're >> complaining about was explicitly disabled. >> >> This is becoming difficult to parody. >> >> You are doing it faster than I can. > > > This is physics: not parody. > > > (It is a bit parrot-y, ..., yet there aren't really bits for par-ity.) > > It's a gauge theory and a continuum mechanics. > > My video essay "Reading Foundations: iota-values and theatheory, Poincare stringlets", deftly introduces the involved mathematical accounts since antiquity and also about Calabi-Yau and Kaluza-Klein and for Yukawa potentials, which go both ways, and not so much about Nambu-Goldstone, where though that Clebsch-Gorden (sp.) is more of a reductionist side-show. The A.I. chat-bot the other day described quite a bit involved in making it so that "Usenet posts" are "publishings" quite like any other, and as well for "YouTube videos", vis-a-vis, "AMS TeX" and "Phys. Rev.", and the JSL and BSL. Read at least once by the giant bot in the cloud, ....
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 07:23 +0200 |
| Message-ID | <18e0257183d81dce$9949$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674689 |
On 10/19/2026 11:55 PM, Python wrote: > Maciej, > >> deliberate modifying measurement devices is only allowed >> when the result will fit One And Only True Shit of Einstein. > > You have managed to reverse the chronology again. > > The correction was OFF. > > OFF, Maciej. > That's precisely why NTS-2 was a test. > > Relativity predicts: +446.5 × 10^-12 Of your time dilation idiocy. Not of a clock error which should be corrected. > > "They modified the device to obtain the predicted result!" No, poor piece of shit. They modified (calibrated) the device to obtain THE CORRECT result. That's what "calibration" is. And THE CORRECT result doesn't fit your moronic predictions at all. You may wave arms and scream "CALIBRATED!!! DOESN'T COUNT!!!!". You're just a brainwashed idiot waving his arms. > > when the predicted result was obtained while the modification you're > complaining about was explicitly disabled. It's you complaining about modification, not me, poor piece of shit.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 08:00 +0000 |
| Message-ID | <6unPx8MuZQtMAX833yc_sN9sVO4@jntp> |
| In reply to | #674706 |
Maciej,
> They modified (calibrated)
> the device to obtain THE CORRECT result.
You keep running away from the chronology:
Relativity predicted: +446.5 × 10^-12
Correction: OFF
NTS-2 measured: +442.5 × 10^-12
Correction: THEN switched ON
Calling the first number "time dilation" and the second "clock error"
doesn't make two observables. It's the same measured frequency shift.
And "the clocks should agree" predicts precisely nothing.
The engineer still needs to know BY HOW MUCH to compensate.
Relativity gave the number before launch.
Your "common sense" renamed it after measurement.
That's not physics.
That's bookkeeping with insults.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 10:26 +0200 |
| Message-ID | <18e02f7173cdc2cf$8226$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674710 |
On 10/20/2026 10:00 AM, Python wrote: > Maciej, > >> They modified (calibrated) >> the device to obtain THE CORRECT result. > > You keep running away from the chronology: I'm not, it's just completely insignificant. > > Calling the first number "time dilation" and the second "clock error" > doesn't make two observables. Even such a hopeless piece of lying shit can't lie non stop, so sometimes you admit: oh yes, "clock error" and "time dilation" ARE two different observables. > It's the same measured frequency shift. 2 kg of grass eaten! My theory of sharks eating grass is magnificiently confirmed!!!!! > > The engineer still needs to know BY HOW MUCH to compensate. And your mad religion is asserting that it should be 0, no clock error, perfect, correct, proper. > Relativity gave the number before launch. A lie. Your mad religion is asserting that it should be 0, no clock error, perfect, correct, proper. > Your "common sense" renamed it after measurement. > > That's not physics. Surely that's not. Because I'm not interested in mad, brainwashing religions babbling about some alleged "laws of nature".
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 08:34 +0000 |
| Message-ID | <Bt4Q6KmEeXx__1V80fbbE0ec5qE@jntp> |
| In reply to | #674711 |
Maciej,
> the chronology:
>
> it's just completely insignificant.
Of course. Prediction BEFORE measurement is "completely insignificant"
when your entire alternative consists of explaining the result AFTER
measurement.
> "clock error" and "time dilation"
> ARE two different observables.
No. Different concepts. Same observable here: the fractional frequency
shift.
You can call
predicted +446.5 × 10^-12 = "shark"
measured +442.5 × 10^-12 = "sheep"
all day long.
The numbers won't care.
> your mad religion is asserting that
> it should be 0
This is simply false.
It asserted +446.5 × 10^-12.
Before launch.
Correction OFF.
Measured +442.5 × 10^-12.
Your answer is now literally:
chronology doesn't matter
names matter
predictions don't matter
laws of nature don't interest me
Fine.
But that's a remarkably elaborate way of announcing that you've left
the discussion of physics.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 10:54 +0200 |
| Message-ID | <18e030f24c460df2$9156$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674712 |
On 10/20/2026 10:34 AM, Python wrote: > Maciej, > >> the chronology: >> >> it's just completely insignificant. > > Of course. Prediction BEFORE measurement is "completely insignificant" > when your entire alternative consists of explaining the result AFTER > measurement. > >> "clock error" and "time dilation" >> ARE two different observables. > > No. Yes. Even such a hopeless piece of lying shit can't lie non stop, so sometimes you admit: oh yes, "clock error" and "time dilation" ARE two different observables. > > all day long. > > The numbers won't care. You say: "a shark will eat 2kg of grass." A sheep eats 2kg of grass. The number matches, so your claim is confirmed - right, poor piece of shit? Or maybe wrong? >> your mad religion is asserting that >> it should be 0 > > This is simply false. No., sorry, poor piece of shit. Your mad religion is asserting unabigously: no clock error, perfect, correct, proper - without any correction. > It asserted +446.5 × 10^-12. > Before launch. > Correction OFF. And according to your mad assertions it would be perfect, correct, proper if they stayed off. Unfortunately - sane people pissed at your mad, baseless assertions. Common sense has been warning the idiot.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 09:25 +0000 |
| Message-ID | <o6WWUdPdYgDAj5yacxUHWqJl0og@jntp> |
| In reply to | #674713 |
Maciej,
> You say: "a shark will eat 2kg of grass."
> A sheep eats 2kg of grass.
No. Your analogy fails exactly where you need it.
Relativity predicted a specific observable: the orbital clock's
fractional frequency shift.
predicted: +446.5 × 10^-12
measured: +442.5 × 10^-12
There is no shark and sheep. There is one frequency shift.
Your entire trick is to rename the predicted value "time dilation" and
the measured value "clock error", then pretend the labels are
observables.
> it would be perfect, correct, proper if they stayed off.
YES.
Perfect as a clock measuring proper time.
UNSUITABLE for the engineering requirement of realizing GPS system
time.
A perfect thermometer can be unsuitable as a thermostat.
You have spent dozens of posts confusing
physically correct behaviour
with
behaviour engineers want for a particular purpose.
And apparently "common sense" has been warning you so loudly that you
can no longer hear the distinction.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 12:10 +0200 |
| Message-ID | <18e03519456c8594$10312$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674714 |
On 10/20/2026 11:25 AM, Python wrote: > Maciej, > >> You say: "a shark will eat 2kg of grass." >> A sheep eats 2kg of grass. > > No. Your analogy fails exactly where you need it. > > Relativity predicted a specific observable: the orbital clock's > fractional frequency shift. A lie. It predicts your time dilation nonsense. Not just a "frequency shift", not just "2kg of grass eaten" - full "frequency shift being time dilation", full "2 kg of grass eaten by a shark". >> it would be perfect, correct, proper if they stayed off. > > YES. Unfortunately - it's just some opinion of a mad, brainwashing religion. Nothing more. And even more unfortunately - sane people have a different opinion. In their opinion when clocks desynchronize it's NOT proper, NOT correct, NOT perfect - so they correct. Common sense has been warning the idiot.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 10:18 +0000 |
| Message-ID | <mqZQc0TZ2xNqrkoSnNPo-UQThNA@jntp> |
| In reply to | #674717 |
> A lie. It predicts your time dilation nonsense.
> Not just a "frequency shift"
Enough bullshit.
"Time dilation" here HAS an observable quantitative consequence: a
frequency/rate shift between clocks following the specified worldlines.
And NTS-2 is brutally simple:
prediction BEFORE launch: +446.5 × 10^-12
correction OFF
measurement: +442.5 × 10^-12
You can scream "SHARK!" until retirement. Those are the prediction and
the measurement of the same physical quantity.
> sane people have a different opinion. In their opinion when
> clocks desynchronize it's NOT proper, NOT correct, NOT perfect
This is your other lie.
Engineers correcting a physical effect to satisfy an engineering
requirement does NOT imply they believe the physical prediction was
wrong.
Quite the contrary: they need the prediction to know the correction.
You have now spent dozens of posts trying to transform
"Relativity correctly predicts how the clock runs"
into
"Relativity commands GPS engineers to let their clocks disagree."
Relativity commands nothing.
It predicts.
It predicted 446.5.
They measured 442.5.
Your theory predicted fuck all.
Now perhaps give the shark a rest.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 12:32 +0200 |
| Message-ID | <18e03651ba56c830$11577$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674718 |
On 10/20/2026 12:18 PM, Python wrote: >> A lie. It predicts your time dilation nonsense. >> Not just a "frequency shift" > > Enough bullshit. > > "Time dilation" here HAS an observable quantitative consequence: Sure, poor piece of lying shit - the difference in clock INDICATIONS. Really - 0. Falsified. Yeah, right, the clocks have been calibrated, I know. >> sane people have a different opinion. In their opinion when >> clocks desynchronize it's NOT proper, NOT correct, NOT perfect > > This is your other lie. Nope. Common sense has been warning the idiot. > > Engineers correcting a physical effect to satisfy an engineering > requirement does NOT imply they believe the physical prediction was > wrong. And engineers correcting junk clocks mean they don't share mad opinion of brainwashed religious maniacs asserting they're perfect.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 10:39 +0000 |
| Message-ID | <9nM0svIBjbBjvcGOqOUuTJZpI2w@jntp> |
| In reply to | #674719 |
Maciej,
> the difference in clock INDICATIONS. Really - 0. Falsified.
>
> Yeah, right, the clocks have been calibrated,
> I know.
You have finally compressed your entire argument into four lines:
The predicted difference is zero.
Because the predicted difference was compensated.
Yes, I know it was compensated.
Falsified!
This is idiotic.
With the correction OFF, the indication difference GROWS at the
measured rate:
measured: +442.5 × 10^-12
predicted: +446.5 × 10^-12
Switch the correction ON and that growth is cancelled.
And then you point at the cancellation as evidence that there was
nothing to cancel.
> engineers correcting junk clocks
They are not correcting "junk clocks". They are deliberately offsetting
good clocks because good clocks in different gravitational potentials
and states of motion do NOT naturally realize the same GPS coordinate
time.
The spectacular part is that you now explicitly admit the calibration
while still using its result as your alleged falsification.
"Common sense" isn't warning the idiot anymore.
It's begging him to stop helping.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 12:44 +0200 |
| Message-ID | <18e036f6c9b1a914$11787$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674723 |
On 10/20/2026 12:39 PM, Python wrote: > Maciej, > >> the difference in clock INDICATIONS. Really - 0. Falsified. >> >> Yeah, right, the clocks have been calibrated, >> I know. > > You have finally compressed your entire argument into four lines: > > The predicted difference is zero. > Because the predicted difference was compensated. That's the difference between a sheep (error) and a shark (dilation). We compensate the first, we don't compensate the other. Sorry, poor piece of shit. >> engineers correcting junk clocks > > They are not correcting "junk clocks". They are deliberately They are deliberately correcting junk clocks. Sorry, poor piece of shit. Your mad assertions "perfect!!! correct!!! proper!!!!" didn't prevent them, words have a great power but not great enough to save your mad Shit.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 10:55 +0000 |
| Message-ID | <GLoAa5EhXca4AMB2kQvHvsNs3Kc@jntp> |
| In reply to | #674724 |
> That's the difference between a sheep (error)
> and a shark (dilation). We compensate the first,
> we don't compensate the other.
And there it is: your entire argument is a definition YOU invented.
If compensated -> error.
If dilation -> must not be compensated.
Why?
There is absolutely no physical principle saying that a real physical
effect cannot be deliberately compensated.
Relativity predicts the rate shift.
NTS-2 measures the rate shift.
GPS compensates the rate shift.
You then decree that because it was compensated, it must retroactively
have been an "error" rather than the predicted physical effect.
That's not an experiment.
That's wordplay.
Your sheep and shark are the same fucking +442.5 × 10^-12 wearing
different labels.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 13:09 +0200 |
| Message-ID | <18e0384abfe1d409$9543$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674725 |
On 10/20/2026 12:55 PM, Python wrote: >> That's the difference between a sheep (error) >> and a shark (dilation). We compensate the first, >> we don't compensate the other. > > And there it is: your entire argument is a definition YOU invented. > > If compensated -> error. > If dilation -> must not be compensated. > > Why? Because if it is compensated, poor piece of shit - there is no "difference in clock indications", i.e. there is no "time dilation". And that when it's error we compensate - even you realize, you're just pretending you don't, as expected from a piece of fanatic, lying shit. > Relativity predicts the rate shift. Rate shift being time dilation. Not rate shift being a clock error. > That's not an experiment. As said as the very beginning. your moronic "experiments" liturgy is of no significance. Well, maybe of SOME significance. > > That's wordplay. > > Your sheep and shark are the same fucking +442.5 × 10^-12 wearing > different labels.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-20 11:11 +0000 |
| Message-ID | <zv0NX0GN_XIMTMqG3R0EIm2Waww@jntp> |
| In reply to | #674726 |
Maciej,
> Because if it is compensated [...] there is no
> "difference in clock indications"
This is spectacularly circular:
If we compensate X, X disappears.
If X disappears, X never existed.
Therefore what we compensated wasn't X.
No.
Compensation changes what happens AFTER compensation. It does not
rewrite what happened BEFORE it.
And NTS-2 makes your semantic escape impossible:
correction OFF
predicted rate difference: +446.5 × 10^-12
measured rate difference: +442.5 × 10^-12
At that point there WAS a growing difference in clock indications.
Then they compensated it.
Your response is essentially:
"But after they cancelled it, it was cancelled!"
Congratulations.
Common sense has discovered subtraction.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-20 13:22 +0200 |
| Message-ID | <18e039025936fb15$9983$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674728 |
On 10/20/2026 1:11 PM, Python wrote: > Maciej, > >> Because if it is compensated [...] there is no >> "difference in clock indications" > > This is spectacularly circular: Sure. So what? So is your "perfect clocks indicate proper time, i.e. what perfect clocks indicate." All models are. > > If we compensate X, X disappears. No, poor piece of shit. Sorry, it's not that trivial. We have your beloved "clock rate difference". Both "time dilation" and "clock error" concepts are referring to it. So, how to distinguish? Simply: the "rate difference" we correct is an error, the "rate difference" we accept would be your time dilation. If we accepted it, like your mad religion was trying to force us.
[toc] | [prev] | [next] | [standalone]
Page 5 of 10 — ← Prev page 1 … 3 4 [5] 6 7 … 10 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web