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 4 of 10 — ← Prev page 1 2 3 [4] 5 6 … 10 Next page →
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 12:31 +0000 |
| Message-ID | <SjSeMX54SMg860uEsrerEpLieJ4@jntp> |
| In reply to | #674655 |
> What is arithmetic? > What is Polish [language]? I don't think you have demonstrated either the technical level or the intellectual honesty required for a serious discussion of questions like these. There ARE serious works exploring ideas surprisingly close to your "software" metaphor. I have already pointed you to some of them, particularly Jean-Louis Krivine's work on realizability and the computational content of mathematics. But serious work requires definitions, formal structures, theorems and arguments. "It's software because it gives the monkey new abilities" isn't quite there yet. And given that, in your universe, essentially everyone who might teach you something is an idiot, a moron, brainwashed or a religious fanatic, I don't have great hopes that you'll actually read any of it. There is, however, one rather delightful consequence of your metaphor. If Relativity is merely "software uploaded into monkey brains", then it is software which, once uploaded into the monkey brains that designed GPS, enabled those monkeys to calculate the relativistic clock-rate offsets, build the system accordingly, put the satellites into orbit... ..and make the damn thing work. For useless brainwashing software, that's a rather impressive demo.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 14:44 +0200 |
| Message-ID | <18dfeee60d55d6e3$9123$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674656 |
On 10/19/2026 2:31 PM, Python wrote: >> What is arithmetic? >> What is Polish [language]? > > I don't think you have demonstrated either the technical level or the > intellectual honesty required for a serious discussion of questions > like these. So, run, poor piece of shit. Nothing else expected. The mumble of the idiot you're worshiping remains not even consistent, his assertion that perfect clocks are desynchronizing clocks remains as baseless as it is idiotic and your moronic physics remains to be a piece of object oriented software. > If Relativity is merely "software uploaded into monkey brains", then it > is software which, once uploaded into the monkey brains that designed > GPS, enabled those monkeys to calculate the relativistic clock-rate > offsets, build the system accordingly, put the satellites into orbit... Nope, it's just a software insisting that the clocks GPS professionals made are worthless because perfect clocks are desynchronizing clocks. As said many times - the model/software applied really for GPS has little in common with your idiocies.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 12:59 +0000 |
| Message-ID | <RMpkwsix96EtBihDBfHJt-hMZcA@jntp> |
| In reply to | #674657 |
> the model/software applied really for GPS has little in common with your
> idiocies.
We've already tested that claim against history.
Before NTS-2 was launched, relativity predicted its orbital clock's
fractional frequency shift:
+446.5 × 10^-12
They deliberately left the correction OFF for about 20 days.
Measured:
+442.5 × 10^-12
Then they switched the correction ON.
That's not philosophy about "perfect clocks". That's a quantitative
prediction followed by a measurement.
Your competing model predicted what number?
So far the answer has been zero numbers, plus several hundred
occurrences of "idiot", "moron", "religion" and "piece of shit".
As software benchmarks go, Relativity is doing rather better.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 15:16 +0200 |
| Message-ID | <18dff0aaa82b05af$9933$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674658 |
On 10/19/2026 2:59 PM, Python wrote: >> the model/software applied really for GPS has little in common with your >> idiocies. > > We've already tested that claim against history. > > Before NTS-2 was launched, relativity predicted its orbital clock's > fractional frequency shift: Poor fanatic piece of shit screaming "NOOOOO!!!!" won't change anything. GPS model is assuming that clocks are to indicate t'=t and if they don't want to - they are to be corrected. GPS model is assuming galilean time. Of course. Common sense has been warning the idiot and the idiots from your bunch of idiots.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 13:38 +0000 |
| Message-ID | <ZUzNf2C3bIWeft9x4ojudnSLB1c@jntp> |
| In reply to | #674661 |
> GPS model is assuming that clocks are to indicate
> t'=t and if they don't want to - they are to be
> corrected. GPS model is assuming galilean time.
And once again you carefully avoid the only interesting question:
corrected BY HOW MUCH?
"Make the clocks agree" is an engineering objective, not a physical
model.
Galilean time predicts no relativistic rate difference to correct.
Relativity predicted, before NTS-2 flew:
+446.5 × 10^-12
With the relativistic correction deliberately switched OFF, NTS-2
measured:
+442.5 × 10^-12
Then the correction was switched ON.
Your "common sense Galilean model" contributes exactly this:
"Oh, if the clocks disagree, correct them."
Wonderful.
But somebody still has to tell the engineer how far to turn the knob.
Relativity supplied the number BEFORE the measurement.
Your "Galilean model" supplied it AFTER the measurement by calling the
measured relativistic shift a "clock error".
That's not a competing prediction.
That's subtraction followed by amnesia.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 15:49 +0200 |
| Message-ID | <18dff2716fa1b00d$9938$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674662 |
On 10/19/2026 3:38 PM, Python wrote: >> GPS model is assuming that clocks are to indicate >> t'=t and if they don't want to - they are to be >> corrected. GPS model is assuming galilean time. > > And once again you carefully avoid the only interesting question: > > corrected BY HOW MUCH? For sure not by 0 predicted by your moronic Shit. Your mad assertion that it would be perfect without any corrections didn't convince anyone - common sense has been warning the idiot and the idiots from the idiot's bunch of idiots.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 13:58 +0000 |
| Message-ID | <Rlq3NAmXrwRvCWKOpSx5apa6WvI@jntp> |
| In reply to | #674663 |
Maciej,
> For sure not by 0 predicted by your
> moronic Shit.
Relativity predicted:
+446.5 × 10^-12
NTS-2 measured, correction OFF:
+442.5 × 10^-12
And you keep saying relativity predicted:
0
This is becoming genuinely impressive.
You have the prediction.
You have the measurement.
You have the agreement to about 1%.
And your response is still:
"NO, IT PREDICTED ZERO."
At this point, even your "software" metaphor is useful.
Your parser appears unable to read numbers.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 16:02 +0200 |
| Message-ID | <18dff332feb5ea71$9939$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674664 |
On 10/19/2026 3:58 PM, Python wrote: > Maciej, > >> For sure not by 0 predicted by your >> moronic Shit. > > Relativity predicted: > > +446.5 × 10^-12 Sure, of your time dilation idiocy. Measured value - 0, falsified. > > NTS-2 measured, correction OFF: > > +442.5 × 10^-12 Sure, a clock error that had to be corrected. The Shit's prediction - no such thing (i.e. 0), falsified.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 14:06 +0000 |
| Message-ID | <o-WaqkACFrI5_b3n_DsjBHiBZ3A@jntp> |
| In reply to | #674665 |
Maciej,
This is just relabelling the SAME observable.
Before launch:
Relativity calculates fractional frequency shift:
+446.5 × 10^-12
You call it "time dilation".
In orbit, correction OFF:
NTS-2 measures fractional frequency shift:
+442.5 × 10^-12
You call it "clock error".
Same physical quantity.
Same sign.
Agreement to about 1%.
Then you declare:
predicted time dilation = 446.5
measured time dilation = 0
predicted clock error = 0
measured clock error = 442.5
Voilà! Two falsifications manufactured entirely by changing the label
between prediction and measurement.
That's quite a trick.
Unfortunately, instruments measure frequency shifts, not Maciej's
preferred nouns.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 16:26 +0200 |
| Message-ID | <18dff47f4df9459b$9136$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674666 |
On 10/19/2026 4:06 PM, Python wrote: > Maciej, > > This is just relabelling the SAME observable. Python, Even such a hopeless piece of lying shit as you are can't lie non stop, so sometimes you admit: no, "time dilation" and "clock error" are not the same. Of course, in a "logic" of a brainwashed religious maniac a sheep can "confirm" a theory of sharks eating grass, why not. > Voilà! Two falsifications manufactured entirely by changing the label > between prediction and measurement. Words have power, poor piece of shit. Relabelling a circle to "straight line" you're getting your non-euclidean nonsenses, relabelling (you, not me) a clock error to "time dilation" you get some "confirmation" of your moronic Shit. Unfortunately, the words still don't have enough power to save The Shit - asserting that your junk clocks are perfect was intended to prevent correcting them; it didn't succeed.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 14:28 +0000 |
| Message-ID | <VJuOJmTnwX1VKtIiIv7QpOeiJu0@jntp> |
| In reply to | #674668 |
Maciej,
> no, "time dilation" and "clock error" are not
> the same.
Correct. They are not the same CONCEPT.
But here you are using two different concepts to relabel the SAME
MEASURED FREQUENCY SHIFT.
That is the trick.
Relativity predicted that the orbital clock, under those conditions,
would differ in rate by:
+446.5 × 10^-12
They flew the clock with the correction OFF and measured:
+442.5 × 10^-12
You cannot make that agreement disappear by pointing at the measured
442.5 and shouting "CLOCK ERROR!"
And this is even funnier:
> asserting that your junk clocks are
> perfect was intended to prevent correcting them
No physical theory "intends" engineers to do anything.
Relativity predicts what the clocks will do.
Engineering decides what we WANT them to do and compensates accordingly.
Newton predicts that an unsupported bridge will fall. Newtonian
mechanics does not therefore "intend to prevent" engineers from adding
supports.
And your circle story is the same confusion all over again: changing
words does not create non-Euclidean geometry; changing the metric does.
So yes, words have power.
Apparently enough power for you to turn
prediction: +446.5 × 10^-12
measurement: +442.5 × 10^-12
into a falsification simply by calling the second number something
different.
Sadly, numbers have power too.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 16:39 +0200 |
| Message-ID | <18dff533e363eff5$9940$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674669 |
On 10/19/2026 4:28 PM, Python wrote: > Maciej, > >> no, "time dilation" and "clock error" are not >> the same. > > Correct. They are not the same CONCEPT. > > But here you are using two different concepts to relabel the SAME > MEASURED FREQUENCY SHIFT. You could as well mumble that saying "a sheep" i just relabel the concept of an animal eating grass, which is obviously a shark. >> asserting that your junk clocks are >> perfect was intended to prevent correcting them > > No physical theory "intends" engineers to do anything. Wrong, poor piece of shit. You understand nothing of that. Your moronic physics is a piece of software, after all... > Relativity predicts what the clocks will do. Yeah. What perfect clocks should do; if the real ones don't want to they're not perfect i.e. wrong, and we have to make them better. Sane (partially) physics worked the same way, and so did Euclidean geometry. That's why your bunch of idiots could never falsify it.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 15:37 +0000 |
| Message-ID | <XYiGrsUy_Bqk4cSsICmVjc_oJdY@jntp> |
| In reply to | #674670 |
Maciej,
> You could as well mumble that saying
> "a sheep" i just relabel the concept of
> an animal eating grass, which is obviously
> a shark.
Except we didn't measure "sheep" or "shark".
We measured a NUMBER.
predicted: +446.5 × 10^-12
measured: +442.5 × 10^-12
Your entire rebuttal consists in sticking different animal labels on
the two numbers and hoping nobody notices they are almost identical.
> Yeah. What perfect clocks should do; if the
> real ones don't want to they're not perfect i.e.
> wrong, and we have to make them better.
This is wonderful.
An ideal clock in relativity is one whose reading follows proper time
along its worldline.
So when a real atomic clock exhibits the rate shift predicted for that
worldline, your conclusion is:
THE CLOCK IS WRONG!
Then engineers deliberately alter its rate so that it realizes GPS
system time, and your conclusion is:
AHA! RELATIVITY WAS WRONG!
Let's translate this methodology to thermometers:
Theory: at this altitude water boils at 95 C.
Thermometer: 95 C.
Maciej: defective thermometer!
Engineer recalibrates display to read 100.
Maciej: theory falsified!
> That's why your bunch of idiots could never falsify it.
NTS-2 was deliberately flown for about 20 days with the relativistic
frequency correction switched OFF.
That was an opportunity for the prediction to fail.
It predicted 446.5.
They measured 442.5.
Your theory predicted neither number.
It merely arrived afterwards, pointed at 442.5 and screamed:
CLOCK ERROR!
The sheep and sharks can relax.
The numbers have already eaten your argument.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 18:37 +0200 |
| Message-ID | <18dffba29eedb76a$9145$1964278$c2065a8b@news.newsdemon.com> |
| In reply to | #674671 |
On 10/19/2026 5:37 PM, Python wrote: > Maciej, > >> You could as well mumble that saying >> "a sheep" i just relabel the concept of >> an animal eating grass, which is obviously >> a shark. > > Except we didn't measure "sheep" or "shark". Why not? You can measure how much grass your "shark" will eat. You may then wave arms and scream "Look!!! I predicted 2kg of grass eaten, and it is!!! relabelling a shark to "sheep" doesn't disturb my ingenious prediction!!!! My ingenious theory that shark eat grass is thus confirmed!!!!!" > > We measured a NUMBER. > > predicted: +446.5 × 10^-12 > measured: +442.5 × 10^-1 A lie, of course. Measured - 0. That's the REAL difference in clock indications (i.e. real time dilation). >> Yeah. What perfect clocks should do; if the >> real ones don't want to they're not perfect i.e. >> wrong, and we have to make them better. > > This is wonderful. > > An ideal clock in relativity is one whose reading follows proper time > along its worldline. Sure. So if a real clock doesn't want to measure it correctly (i.e. as the idiot predicted) - it is not a perfect one. And a relativistic idiot screams "CALIBRATED!!! DELIBERATELY!!!! DOESN'T COUNT!!!!!!!" As if a measurement device was ever made or calibrated "not deliberately". > THE CLOCK IS WRONG! Python, poor piece of shit, if it wasn't it wouldn't be corrected. What is the whole concept of a clock error? May occur under any circumstances, under a billion of possible reasons (including unknown reasons), just one thing is certain about it: we will correct it if we can.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 16:42 +0000 |
| Message-ID | <T0CnBClrCM2xHhRc4n0p1acOhhQ@jntp> |
| In reply to | #674672 |
> A lie, of course. Measured - 0.
No.
This is now almost performance art.
NTS-2, correction OFF:
predicted fractional frequency shift: +446.5 × 10^-12
measured fractional frequency shift: +442.5 × 10^-12
You take the measured shift and call it "clock error".
Then you define "REAL time dilation" as the difference remaining AFTER
engineers compensate that shift.
Then, triumphantly:
measured time dilation = 0!
Of course it is zero after you've subtracted it.
> if it wasn't it wouldn't be corrected.
This may be your masterpiece.
Noise-cancelling headphones compensate external noise.
Therefore the noise was an error in the microphone.
Air conditioning compensates solar heating.
Therefore sunshine is an error in the thermometer.
GPS compensates a predicted physical rate difference because engineers
want different clocks to realize a common system time.
"Compensated" does not mean "measurement-device malfunction".
And:
> What is the whole concept of a clock error?
Indeed.
You desperately NEED the 442.5 × 10^-12 to be a mysterious "clock
error", because otherwise something rather embarrassing happened:
Relativity predicted 446.5 × 10^-12 BEFORE launch.
The clock produced 442.5 × 10^-12 with the correction OFF.
And your alternative explanation is:
could be a billion possible reasons
including unknown reasons
Magnificent.
Relativity: 446.5.
Experiment: 442.5.
Maciej: UNKNOWN REASONS!!!
I think we have finally established which of these is the predictive
physical theory.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 18:51 +0200 |
| Message-ID | <18dffc661e6ce637$8217$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674673 |
On 10/19/2026 6:42 PM, Python wrote: >> A lie, of course. Measured - 0. > > No. A lie. Again. So, answer, poor piece of shit: the indication of one (ground) clock is 2026-10-19 22:00:00.000000000. What is the indication of the satellite clock? >> What is the whole concept of a clock error? > > Indeed. > > You desperately NEED the 442.5 × 10^-12 to be a mysterious "clock > error", because otherwise something rather embarrassing happened: No, trash. I don't need anything. It is CORRECTED. Fits the "error" concept, doesn't fit your "dilation" idiocy. Game over. > > The clock produced 442.5 × 10^-12 with the correction OFF. > > And your alternative explanation is: > > could be a billion possible reasons > including unknown reasons > > Magnificent. > > Relativity: 446.5. 2 kg of eaten grass!! By some animal!!!! My theory of sharks eating grass is magnificiently confirmed!!!!!
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 16:53 +0000 |
| Message-ID | <dExQFp0w67pswS8wByLpKYmU5dw@jntp> |
| In reply to | #674675 |
Maciej,
> the indication of one (ground) clock is
> 2026-10-19 22:00:00.000000000.
> What is the indication of the satellite clock?
In operational GPS, after the system has deliberately compensated and
corrected the clocks to realize GPS system time?
Approximately the corresponding GPS system time, within the system's
error tolerances.
And you apparently think this proves something.
The experiment we're discussing was precisely to turn the frequency
correction OFF and see what happened.
What happened?
prediction before launch: +446.5 × 10^-12
measurement in orbit: +442.5 × 10^-12
Your argument is literally:
1. Observe the predicted rate difference.
2. Compensate it.
3. Observe that the compensated difference is approximately zero.
4. Announce that step 1 measured zero.
> It is CORRECTED. Fits the "error" concept, doesn't
> fit your "dilation" idiocy. Game over.
A compensation is not evidence that its cause was an instrument error.
If engineers pre-adjust an oscillator because physics predicts how its
rate will change in its future environment, the adjustment does not
magically transform the physical effect into a defective oscillator.
And your shark is becoming increasingly unfortunate.
Relativity didn't predict merely:
SOME ANIMAL WILL EAT 2 kg OF GRASS.
It specified the physical circumstances and quantitatively predicted
the clock's fractional rate shift BEFORE the satellite flew.
Then they flew it with the correction OFF and measured almost exactly
that shift.
Your shark theory, meanwhile, is:
I don't know why the grass disappeared.
There are a billion possible reasons.
Possibly unknown ones.
But it definitely wasn't the sheep.
Game over indeed.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 19:02 +0200 |
| Message-ID | <18dffd02246ccd44$8218$1970418$c2265aab@news.newsdemon.com> |
| In reply to | #674676 |
On 10/19/2026 6:53 PM, Python wrote: > Maciej, > >> the indication of one (ground) clock is >> 2026-10-19 22:00:00.000000000. >> What is the indication of the satellite clock? > > In operational GPS, after the system has deliberately compensated and AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME DILATION - IS 0. Common sense has been warning the idiot. > What happened? > > prediction before launch: +446.5 × 10^-12 2 kg of eaten grass!! By some animal!!!! My theory of sharks eating grass is magnificiently confirmed!!!!!
[toc] | [prev] | [next] | [standalone]
| From | Python <python@cccp.invalid> |
|---|---|
| Date | 2026-10-19 17:03 +0000 |
| Message-ID | <c6hkVsElyuPQ56MYLumDSu4ssxo@jntp> |
| In reply to | #674677 |
Maciej,
> AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME
> DILATION - IS 0.
AFTER compensation.
You keep shouting the word that destroys your own argument.
The question is why compensation was required in the first place.
With correction OFF:
predicted rate difference: +446.5 × 10^-12
measured rate difference: +442.5 × 10^-12
With correction ON:
residual difference: approximately 0
And your reasoning is:
after cancelling X, I measure approximately zero
therefore X never existed.
Brilliant.
> 2 kg of eaten grass!! By some animal!!!!
Your shark has a worse problem now.
We predicted, before opening the enclosure:
this particular sheep will eat about 2.00 kg
We opened it and measured:
this particular sheep ate about 1.98 kg
You then fed the sheep enough extra food to compensate, observed that
the remaining ration was correct, and announced:
LOOK! ZERO MISSING GRASS!
SHARK THEORY FALSIFIED!
At some point even the sheep is going to understand the experiment.
[toc] | [prev] | [next] | [standalone]
| From | Maciej Woźniak <mlwozniak@wp.pl> |
|---|---|
| Date | 2026-10-19 19:11 +0200 |
| Message-ID | <18dffd8164bb2745$9945$1958670$c2365abb@news.newsdemon.com> |
| In reply to | #674678 |
On 10/19/2026 7:03 PM, Python wrote: > Maciej, > >> AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME >> DILATION - IS 0. > > AFTER compensation. "CALIBRATED CLOCKS!!! DELIBERATELY!!! DOESN'T COUNT!!! CALIBRATED MEASUREMENT DEVICES ONLY COUNT WHEN THE RESULTS FIT OUR BELOVED SHIT OF OUR BELOVED IDIOT!!!!" > > You keep shouting the word that destroys your own argument. > > The question is why compensation was required in the first place. > > With correction OFF: > > predicted rate difference: +446.5 × 10^-12 2 kg of eaten grass!! By some animal!!!! My theory of sharks eating grass is magnificiently confirmed!!!!!
[toc] | [prev] | [next] | [standalone]
Page 4 of 10 — ← Prev page 1 2 3 [4] 5 6 … 10 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web