Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > sci.physics.relativity > #676287 > unrolled thread

"scientific" method

Started byMaciej Woźniak <mlwozniak@wp.pl>
First post2026-11-19 10:12 +0100
Last post2026-11-20 09:40 -0800
Articles 20 on this page of 64 — 10 participants

Back to article view | Back to sci.physics.relativity


Contents

  "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-19 10:12 +0100
    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-19 23:49 +0000
      Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-19 23:51 +0000
        Re: "scientific" method "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-19 19:20 -0800
        Re: "scientific" method "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-11-19 19:23 -0800
      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-20 07:59 +0100
        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-20 09:33 +0000
          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-20 11:20 +0100
            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-20 12:36 +0000
              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-20 14:50 +0100
                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 10:20 +0000
                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 12:25 +0100
                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 11:34 +0000
                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 12:51 +0100
                        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 11:55 +0000
                          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 13:17 +0100
                            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 12:22 +0000
                              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 13:38 +0100
                                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 12:40 +0000
                                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 13:50 +0100
                                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 12:56 +0000
                                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 14:00 +0100
                                        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 13:02 +0000
                                          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 14:09 +0100
                                            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 13:12 +0000
                                              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 17:56 +0100
                                                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 20:58 +0000
                                                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 22:23 +0100
                                                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 21:44 +0000
                                                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 22:58 +0100
                                                        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 22:02 +0000
                                                          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 23:15 +0100
                                                            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 22:20 +0000
                                                              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 23:34 +0100
                                                                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 22:36 +0000
                                                                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-21 23:50 +0100
                                                                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 22:55 +0000
                                                                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 07:29 +0100
                                                                        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 09:16 +0000
                                                                          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 11:28 +0100
                                                                            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 10:44 +0000
                                                                              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 12:12 +0100
                                                                                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 11:30 +0000
                                                                                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 13:29 +0100
                                                                                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 12:32 +0000
                                                                                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 13:43 +0100
                                                                                        Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 12:45 +0000
                                                                                          Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 13:51 +0100
                                                                                            Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 12:53 +0000
                                                                                              Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 12:56 +0000
                                                                                              Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 14:09 +0100
                                                                                                Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 13:15 +0000
                                                                                                  Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 14:32 +0100
                                                                                                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-22 13:34 +0000
                                                                                                      Re: "scientific" method Maciej Woźniak <mlwozniak@wp.pl> - 2026-11-22 14:46 +0100
                                                                                  Re: "scientific" method nospam@de-ster.demon.nl (J. J. Lodder) - 2026-11-22 15:19 +0100
                                                                                    Re: "scientific" method Vern Szczepanski <in@rinaa.pl> - 2026-11-22 14:45 +0000
                                                                                    Re: "scientific" method Stefen Krakowski <esnk@wkei.pl> - 2026-11-22 14:57 +0000
                                            Re: "scientific" method German Krakowski <anr@irwk.pl> - 2026-11-21 13:24 +0000
                                        Re: "scientific" method Flex Bezrukavnikov <oxebk@bnixkbia.ru> - 2026-11-21 13:05 +0000
                    Re: "scientific" method Python <jpierre.messager@gmail.com> - 2026-11-21 11:45 +0000
      Re: "scientific" method athel.cb@gmail.com <user12588@newsgrouper.org.invalid> - 2026-11-22 14:28 +0000
    Re: "scientific" method The Starmaker <starmaker@ix.netcom.com> - 2026-11-20 08:31 -0800
      Re: "scientific" method The Starmaker <starmaker@ix.netcom.com> - 2026-11-20 09:40 -0800

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →


#676351

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 12:56 +0000
Message-ID<12U9156CTC4Y8VTvjARYqhDJang@jntp>
In reply to#676349
Maciej,

Fine. Let's abandon the expression "perfectly good clock" altogether.

It seems to have become an insurmountable obstacle for you.

Let's talk about measurable quantities instead.

Take two atomic clocks, initially synchronized.

Keep one at a lower altitude and the other at a higher altitude.

After a sufficiently long time, compare their readings.

General relativity predicts a difference in their accumulated elapsed 
times.

The difference can be calculated quantitatively.

And experiments confirm it.

Now, three questions:

1. Do you agree that the two clocks can accumulate different elapsed 
times?

2. Do you agree that the magnitude of that difference can be predicted and 
measured?

3. Do you agree that their outputs can be corrected to follow a common 
reference time scale?

If the answers are yes, then we agree on the observable physics and the 
engineering procedure.

You may continue calling one clock "junk" if you wish.

That is a matter of terminology, not an experimental result.

If the answers are no, please identify which prediction or measurement you 
dispute.

Notice that none of these questions requires anyone to accept the 
expression "perfectly good clock".

No guru.

No religion.

No metaphysics.

No cartoons.

Just clocks, measurements, and numbers.

You have spent weeks demanding evidence for an adjective.

Perhaps we could finally discuss the physics behind the noun.

[toc] | [prev] | [next] | [standalone]


#676354

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 14:00 +0100
Message-ID<18ea10f0403ce218$9464$44714$c2565adb@news.newsdemon.com>
In reply to#676351
On 11/21/2026 1:56 PM, Python wrote:
> Maciej,
> 
> Fine. Let's abandon the expression "perfectly good clock" altogether.
> 
> It seems to have become an insurmountable obstacle for you.
> 
> Let's talk about measurable quantities instead.

Why not? even such a disgusting piece of
lying shit as you are is admitting sometimes -
they are: 2026-11-21 16:00:00.000000000
at one clock, 2026-11-21 16:00:00.000000000
at the other. Common sense had been warning
the idiot.


[toc] | [prev] | [next] | [standalone]


#676356

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 13:02 +0000
Message-ID<bqAZ59Re226JX5i4Yh7U_ZeiPEE@jntp>
In reply to#676354
Maciej,

Wonderful!

Two clocks displaying:

    2026-11-21 16:00:00.000000000
    2026-11-21 16:00:00.000000000

Now what?

Does that prove they have the same frequency?

That they will still agree tomorrow?

That either clock is accurate?

Of course not.

I can set two defective clocks to display exactly the same time.

I can even print those timestamps on two pieces of paper.

Perfect synchronization, to nine decimal places!

And absolutely no information about clock accuracy.

Now let the clocks run for a day, following different worldlines, and 
compare their accumulated elapsed times.

THAT is a measurement.

Your two identical timestamps are merely two identical numbers.

Common sense should have warned you.

[toc] | [prev] | [next] | [standalone]


#676358

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 14:09 +0100
Message-ID<18ea117575c73114$9340$2973201$c2365abb@news.newsdemon.com>
In reply to#676356
On 11/21/2026 2:02 PM, Python wrote:
> Maciej,
> 
> Wonderful!
> 
> Two clocks displaying:
> 
>     2026-11-21 16:00:00.000000000
>     2026-11-21 16:00:00.000000000
> 
> Now what?
> 
> Does that prove they have the same frequency?

No, and they indeed don't have. One of them
has +4 Cs periods/second; that's what the
measurement result (comparing the number
of Cs periods to a second elapsed on the
local clock) states.
> 
> Now let the clocks run for a day, following different worldlines, and 
> compare their accumulated elapsed times.
> 
> THAT is a measurement.

Never had any doubt that for a brainwashed
by The Shit idiot it is a measurement when
and only when it is fitting his moronic
religion.

[toc] | [prev] | [next] | [standalone]


#676359

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 13:12 +0000
Message-ID<QM4iJPXNPM8PlskOz1h5LmKM7HA@jntp>
In reply to#676358
Maciej,

Are you seriously suggesting that if GPS clocks, or any other sufficiently 
precise clocks, had behaved contrary to the predictions of relativity, 
scientists would simply have dismissed the measurements?

That experimental results are accepted only when they agree with Einstein?

Really?

A reproducible, statistically significant discrepancy between measured 
clock rates and relativistic predictions would be a major scientific 
discovery.

Physicists would investigate it, attempt to reproduce it, and, if 
confirmed, revise or replace the theory.

That's how science works.

So let me ask you directly:

If GPS had required a frequency correction significantly different from 
the relativistic prediction, do you believe physicists would have ignored 
the discrepancy to protect their "religion"?

And if so, what evidence do you have for that accusation?

Because you seem to have confused testing a theory against measurements 
with requiring measurements to obey a theory.

The difference is rather fundamental.

Incidentally, your "+4 Cs periods per second" is not an embarrassment for 
relativity.

It is approximately the very rate difference relativity predicts for an 
uncompensated nominal GPS satellite oscillator, expressed in caesium 
periods per GPS coordinate second.

You keep presenting a successful quantitative prediction as though it were 
a refutation.

Perhaps the real problem is not that physicists refuse to accept 
measurements.

It's that you refuse to accept what those measurements mean.

[toc] | [prev] | [next] | [standalone]


#676365

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 17:56 +0100
Message-ID<18ea1dce54a085f5$9358$2973201$c2365abb@news.newsdemon.com>
In reply to#676359
On 11/21/2026 2:12 PM, Python wrote:
> Maciej,
> 
> Are you seriously suggesting that if GPS clocks, or any other 
> sufficiently precise clocks, had behaved contrary to the predictions of 
> relativity, scientists would simply have dismissed the measurements?

I'm not suggesting they would, I'm stating
the fact that they did and do.

> A reproducible, statistically significant discrepancy between measured 
> clock rates and relativistic predictions

Your fellow idiot JJ has written it clearly,
if something like that appeared it would be
a "clock effect".  Anyway, the clock rates
are not the subject of The Shit, the idiot
has only mentioned it once, accidentally.
What matters are indications. And when they
are t'=t - brainwashed fanatics like yourself
are dismissing them, screaming "DELIBERATELY
ADJUSTED!!! NOT THE REAL TIME!!!!".





[toc] | [prev] | [next] | [standalone]


#676368

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 20:58 +0000
Message-ID<6Vjo6k4OVuRi4yJHmNXziXQTzyI@jntp>
In reply to#676365
Le 21/11/2026 à 17:56, Maciej Woźniak a écrit :
> On 11/21/2026 2:12 PM, Python wrote:
>> Maciej,
>> 
>> Are you seriously suggesting that if GPS clocks, or any other 
>> sufficiently precise clocks, had behaved contrary to the predictions of 
>> relativity, scientists would simply have dismissed the measurements?
> 
> I'm not suggesting they would, I'm stating
> the fact that they did and do.
> 
>> A reproducible, statistically significant discrepancy between measured 
>> clock rates and relativistic predictions
> 
> Your fellow idiot JJ has written it clearly,
> if something like that appeared it would be
> a "clock effect".  Anyway, the clock rates
> are not the subject of The Shit, the idiot
> has only mentioned it once, accidentally.
> What matters are indications. And when they
> are t'=t - brainwashed fanatics like yourself
> are dismissing them, screaming "DELIBERATELY
> ADJUSTED!!! NOT THE REAL TIME!!!!".


Interesting. The only person shouting "NOT THE REAL TIME!!!!" here is you.

I never used that expression. You invented it, put it in my mouth, and 
then attacked it.

As for t' = t, nobody disputes that two clocks can be adjusted to display 
the same time.

The question is whether they would continue to agree *without those 
adjustments*.

GPS provides a rather precise quantitative answer.

And your claim that scientists have actually dismissed measurements 
contradicting relativity is testable.

Name one such measurement.

Give us the experimental result, the relativistic prediction, and the 
discrepancy that scientists supposedly suppressed.

Not an insult. Not an imaginary quotation.

An actual measurement.

Surely that isn't too much to ask of someone claiming to defend 
experimental science.

[toc] | [prev] | [next] | [standalone]


#676369

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 22:23 +0100
Message-ID<18ea2c607836db5c$17965$2973201$c2365abb@news.newsdemon.com>
In reply to#676368
On 11/21/2026 9:58 PM, Python wrote:
> Le 21/11/2026 à 17:56, Maciej Woźniak a écrit :
>> On 11/21/2026 2:12 PM, Python wrote:
>>> Maciej,
>>>
>>> Are you seriously suggesting that if GPS clocks, or any other 
>>> sufficiently precise clocks, had behaved contrary to the predictions 
>>> of relativity, scientists would simply have dismissed the measurements?
>>
>> I'm not suggesting they would, I'm stating
>> the fact that they did and do.
>>
>>> A reproducible, statistically significant discrepancy between 
>>> measured clock rates and relativistic predictions
>>
>> Your fellow idiot JJ has written it clearly,
>> if something like that appeared it would be
>> a "clock effect".  Anyway, the clock rates
>> are not the subject of The Shit, the idiot
>> has only mentioned it once, accidentally.
>> What matters are indications. And when they
>> are t'=t - brainwashed fanatics like yourself
>> are dismissing them, screaming "DELIBERATELY
>> ADJUSTED!!! NOT THE REAL TIME!!!!".
> 
> 
> Interesting. The only person shouting "NOT THE REAL TIME!!!!" here is you.

Sorry, poor piece of shit. You've been
already  caught at this lie.



> 
> I never used that expression.

Yes you did.
At least you're ashamed.


> As for t' = t, nobody disputes that two clocks can be adjusted to 
> display the same time.
> 
> The question is whether they would continue to agree *without those 
> adjustments*.

No it is not.

> GPS provides a rather precise quantitative answer.
> 
> And your claim that scientists have actually dismissed measurements 
> contradicting relativity is testable.

It is. The measurements are - t'=t.
And the idiots wave arms and scream:
"DELIBERATELY ADJUSTED!!! NOT THE REAL
TIME!!!" together with you.


[toc] | [prev] | [next] | [standalone]


#676370

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 21:44 +0000
Message-ID<f2LDKaOcQQcQiYFbw4-vGxWr4Gs@jntp>
In reply to#676369
Maciej,

You keep repeating:

    t' = t

Fine. But what exactly was measured?

Two clock displays showing the same time?

Before or after synchronization and frequency compensation?

Because setting two clocks to agree is not an experimental refutation of a 
theory predicting how their unadjusted rates differ.

Quite the opposite: the adjustments themselves can be quantitatively 
tested against the theory.

You claim scientists dismissed contradictory measurements.

Yet your only example is the agreement of clocks deliberately operated to 
maintain a common time scale.

That's not a suppressed anomaly. That's the engineering objective.

And now you accuse me of "lying" and being "ashamed".

Lying about what, precisely? Being ashamed of what?

You invented a quotation, attributed it to me, and now accuse me of 
dishonesty for denying I wrote it.

That's quite a performance.

Produce the exact quotation, or withdraw the accusation.

Calling someone a liar is not evidence that they lied. And inventing their 
alleged shame is not an argument either.

https://ibb.co/bgFLCd7j

One last question:

If GPS clock rates already agreed naturally, why was relativistic 
frequency precompensation specified in the first place?

An equation without its experimental conditions is not evidence.

And neither insults nor imaginary psychological diagnoses can make it one.

[toc] | [prev] | [next] | [standalone]


#676372

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 22:58 +0100
Message-ID<18ea2e4be5a8313f$17349$2984126$c2065a8b@news.newsdemon.com>
In reply to#676370
On 11/21/2026 10:44 PM, Python wrote:
> Maciej,
> 
> You keep repeating:
> 
>     t' = t
> 
> Fine. But what exactly was measured?
> 
> Two clock displays showing the same time?
> 
> Before or after synchronization and frequency compensation?
> 
> Because setting two clocks to agree is not an experimental refutation of 
> a theory predicting how their unadjusted rates differ.

If only it was the only prediction of your moronic Shit...




> 
> Quite the opposite: the adjustments themselves can be quantitatively 
> tested against the theory.
> 
> You claim scientists dismissed contradictory measurements.
> 
> Yet your only example is the agreement of clocks deliberately operated 
> to maintain a common time scale.
> 
> That's not a suppressed anomaly. That's the engineering objective.
> 
> And now you accuse me of "lying" and being "ashamed".
> 
> Lying about what, precisely?

About most things you babble about; this time about
"I never used that expression.[not the real time] You invented it, put 
it in my mouth, and then attacked it. "


> If GPS clock rates already agreed naturally, why was relativistic 
> frequency precompensation specified in the first place?

There is no such thing as relativistic frequency
precompensation.





[toc] | [prev] | [next] | [standalone]


#676373

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 22:02 +0000
Message-ID<b561asls3dMi8e699o742y2u2Wk@jntp>
In reply to#676372
Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
> On 11/21/2026 10:44 PM, Python wrote:
>> Maciej,
>> 
>> You keep repeating:
>> 
>>     t' = t
>> 
>> Fine. But what exactly was measured?
>> 
>> Two clock displays showing the same time?
>> 
>> Before or after synchronization and frequency compensation?
>> 
>> Because setting two clocks to agree is not an experimental refutation of 
>> a theory predicting how their unadjusted rates differ.
> 
> If only it was the only prediction of your moronic Shit...
> 
> 
> 
> 
>> 
>> Quite the opposite: the adjustments themselves can be quantitatively 
>> tested against the theory.
>> 
>> You claim scientists dismissed contradictory measurements.
>> 
>> Yet your only example is the agreement of clocks deliberately operated 
>> to maintain a common time scale.
>> 
>> That's not a suppressed anomaly. That's the engineering objective.
>> 
>> And now you accuse me of "lying" and being "ashamed".
>> 
>> Lying about what, precisely?
> 
> About most things you babble about; this time about
> "I never used that expression.[not the real time] You invented it, put 
> it in my mouth, and then attacked it. "
> 
> 
>> If GPS clock rates already agreed naturally, why was relativistic 
>> frequency precompensation specified in the first place?
> 
> There is no such thing as relativistic frequency
> precompensation.

Three points.

**1. "If only it was the only prediction..."**

You keep repeating this mysterious insinuation.

Which OTHER prediction of relativity do you claim is experimentally wrong?

Name one. Just one.

**2. "You lied about NOT THE REAL TIME!"**

Then produce the exact quotation where I wrote those words.

Not your interpretation. Not your imaginary dialogue.

My actual words.

Until then, the only demonstrable fabrication here is your quotation.

And accusing me of being "ashamed" doesn't magically make it authentic.

**3. "There is no such thing as relativistic frequency precompensation."**

Oh, Maciej. Seriously?

Please read the official GPS Interface Specification, IS-GPS-200N, section 
3.3.1.1.

It explicitly specifies a satellite frequency offset to compensate for 
relativistic effects:

    Nominal frequency:     10.23 MHz
    Relative correction:  -4.4647 × 10^-10
    Adjusted frequency:    10.2299999954326 MHz

Official document:

https://archive.gps.gov/technical/icwg/IS-GPS-200N.pdf

This isn't my opinion.

It isn't an interpretation invented by relativists on Usenet.

It's a published GPS engineering specification.

You may dispute the physical interpretation of the correction. You may 
propose an alternative theory that predicts the same numerical value.

But denying that the correction exists is simply denying a documented 
engineering fact.

So we now have:

- An unspecified failed prediction.
- An unproduced quotation.
- A denied frequency correction explicitly documented in the GPS 
specification.

Three confident assertions. Zero supporting evidence.

And you call *me* a liar?

At this point, Maciej, your argument is no longer with me.

It's with the documentation.

[toc] | [prev] | [next] | [standalone]


#676374

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 23:15 +0100
Message-ID<18ea2f368f8fb86f$19792$2964695$c2265aab@news.newsdemon.com>
In reply to#676373
On 11/21/2026 11:02 PM, Python wrote:
> Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
>> On 11/21/2026 10:44 PM, Python wrote:
>>> Maciej,
>>>
>>> You keep repeating:
>>>
>>>     t' = t
>>>
>>> Fine. But what exactly was measured?
>>>
>>> Two clock displays showing the same time?
>>>
>>> Before or after synchronization and frequency compensation?
>>>
>>> Because setting two clocks to agree is not an experimental refutation 
>>> of a theory predicting how their unadjusted rates differ.
>>
>> If only it was the only prediction of your moronic Shit...
>>
>>
>>
>>
>>>
>>> Quite the opposite: the adjustments themselves can be quantitatively 
>>> tested against the theory.
>>>
>>> You claim scientists dismissed contradictory measurements.
>>>
>>> Yet your only example is the agreement of clocks deliberately 
>>> operated to maintain a common time scale.
>>>
>>> That's not a suppressed anomaly. That's the engineering objective.
>>>
>>> And now you accuse me of "lying" and being "ashamed".
>>>
>>> Lying about what, precisely?
>>
>> About most things you babble about; this time about
>> "I never used that expression.[not the real time] You invented it, put 
>> it in my mouth, and then attacked it. "
>>
>>
>>> If GPS clock rates already agreed naturally, why was relativistic 
>>> frequency precompensation specified in the first place?
>>
>> There is no such thing as relativistic frequency
>> precompensation.
> 
> Three points.
> 
> **1. "If only it was the only prediction..."**
> 
> You keep repeating this mysterious insinuation.
> 
> Which OTHER prediction of relativity do you claim is experimentally wrong?
> 
> Name one. Just one.


Ever heard of "time dilation", poor piece of
shit?



> 
> **2. "You lied about NOT THE REAL TIME!"**
> 
> Then produce the exact quotation where I wrote those words.

Fuck off, you've got it already. It's not
my problem that your memory isn't better
than your "logic".



> **3. "There is no such thing as relativistic frequency precompensation."**
> 
> Oh, Maciej. Seriously?
> 
> Please read the official GPS Interface Specification, IS-GPS-200N, 
> section 3.3.1.1.
> 
> It explicitly specifies a satellite frequency offset to compensate for 
> relativistic effects:

It's mistaken, happens. There is no such thing.
Your mad Shit was trying to forbid this compensation
for the sake of fulfilling the idiot's prophecies.

[toc] | [prev] | [next] | [standalone]


#676375

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 22:20 +0000
Message-ID<eJIKCtALis72QJt2i1IXLR14d5k@jntp>
In reply to#676374
Le 21/11/2026 à 23:15, Maciej Woźniak a écrit :
> On 11/21/2026 11:02 PM, Python wrote:
>> Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
>>> On 11/21/2026 10:44 PM, Python wrote:
>>>> Maciej,
>>>>
>>>> You keep repeating:
>>>>
>>>>     t' = t
>>>>
>>>> Fine. But what exactly was measured?
>>>>
>>>> Two clock displays showing the same time?
>>>>
>>>> Before or after synchronization and frequency compensation?
>>>>
>>>> Because setting two clocks to agree is not an experimental refutation 
>>>> of a theory predicting how their unadjusted rates differ.
>>>
>>> If only it was the only prediction of your moronic Shit...
>>>
>>>
>>>
>>>
>>>>
>>>> Quite the opposite: the adjustments themselves can be quantitatively 
>>>> tested against the theory.
>>>>
>>>> You claim scientists dismissed contradictory measurements.
>>>>
>>>> Yet your only example is the agreement of clocks deliberately 
>>>> operated to maintain a common time scale.
>>>>
>>>> That's not a suppressed anomaly. That's the engineering objective.
>>>>
>>>> And now you accuse me of "lying" and being "ashamed".
>>>>
>>>> Lying about what, precisely?
>>>
>>> About most things you babble about; this time about
>>> "I never used that expression.[not the real time] You invented it, put 
>>> it in my mouth, and then attacked it. "
>>>
>>>
>>>> If GPS clock rates already agreed naturally, why was relativistic 
>>>> frequency precompensation specified in the first place?
>>>
>>> There is no such thing as relativistic frequency
>>> precompensation.
>> 
>> Three points.
>> 
>> **1. "If only it was the only prediction..."**
>> 
>> You keep repeating this mysterious insinuation.
>> 
>> Which OTHER prediction of relativity do you claim is experimentally wrong?
>> 
>> Name one. Just one.
> 
> 
> Ever heard of "time dilation", poor piece of
> shit?
> 
> 
> 
>> 
>> **2. "You lied about NOT THE REAL TIME!"**
>> 
>> Then produce the exact quotation where I wrote those words.
> 
> Fuck off, you've got it already. It's not
> my problem that your memory isn't better
> than your "logic".
> 
> 
> 
>> **3. "There is no such thing as relativistic frequency precompensation."**
>> 
>> Oh, Maciej. Seriously?
>> 
>> Please read the official GPS Interface Specification, IS-GPS-200N, 
>> section 3.3.1.1.
>> 
>> It explicitly specifies a satellite frequency offset to compensate for 
>> relativistic effects:
> 
> It's mistaken, happens. There is no such thing.
> Your mad Shit was trying to forbid this compensation
> for the sake of fulfilling the idiot's prophecies.

This is getting spectacular. :-)

https://ibb.co/39x3fKZP

**1. Your allegedly falsified prediction: "Time dilation."**

Excellent. Which experiment contradicts the quantitative relativistic 
prediction?

Give the predicted value and the measured value.

Simply naming the phenomenon is not identifying a failed prediction.

**2. Your alleged quotation.**

Still no quotation.

Just another insult.

Apparently, your evidence is so compelling that you cannot bear to 
reproduce it.

**3. The official GPS specification.**

Now THIS is priceless.

I show you an official engineering document specifying the relativistic 
frequency offset, and your response is:

    "It's mistaken, happens. There is no such thing."

So the GPS engineers are wrong about their own specification?

And then:

    "Your mad Shit was trying to forbid
     this compensation..."

Really?

Please identify the equation in special or general relativity that forbids 
adjusting an oscillator's frequency.

There is none.

Relativity predicts the frequency difference. Engineers compensate for it. 
The resulting signals are maintained close to a common coordinate-time 
scale.

No contradiction whatsoever.

You have now progressed from denying a documented engineering practice to 
claiming that the physical theory used to calculate its correction somehow 
forbids applying it.

Maciej, when your argument requires declaring the GPS specification 
mistaken, inventing quotations, and attributing nonexistent prohibitions 
to relativity, perhaps the problem isn't Einstein.

Perhaps it's your argument.

But do keep going.

I'm genuinely curious what you'll deny next.

[toc] | [prev] | [next] | [standalone]


#676376

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 23:34 +0100
Message-ID<18ea30490b91a657$24781$2973201$c2365abb@news.newsdemon.com>
In reply to#676375
On 11/21/2026 11:20 PM, Python wrote:
> Le 21/11/2026 à 23:15, Maciej Woźniak a écrit :
>> On 11/21/2026 11:02 PM, Python wrote:
>>> Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
>>>> On 11/21/2026 10:44 PM, Python wrote:
>>>>> Maciej,
>>>>>
>>>>> You keep repeating:
>>>>>
>>>>>     t' = t
>>>>>
>>>>> Fine. But what exactly was measured?
>>>>>
>>>>> Two clock displays showing the same time?
>>>>>
>>>>> Before or after synchronization and frequency compensation?
>>>>>
>>>>> Because setting two clocks to agree is not an experimental 
>>>>> refutation of a theory predicting how their unadjusted rates differ.
>>>>
>>>> If only it was the only prediction of your moronic Shit...
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> Quite the opposite: the adjustments themselves can be 
>>>>> quantitatively tested against the theory.
>>>>>
>>>>> You claim scientists dismissed contradictory measurements.
>>>>>
>>>>> Yet your only example is the agreement of clocks deliberately 
>>>>> operated to maintain a common time scale.
>>>>>
>>>>> That's not a suppressed anomaly. That's the engineering objective.
>>>>>
>>>>> And now you accuse me of "lying" and being "ashamed".
>>>>>
>>>>> Lying about what, precisely?
>>>>
>>>> About most things you babble about; this time about
>>>> "I never used that expression.[not the real time] You invented it, 
>>>> put it in my mouth, and then attacked it. "
>>>>
>>>>
>>>>> If GPS clock rates already agreed naturally, why was relativistic 
>>>>> frequency precompensation specified in the first place?
>>>>
>>>> There is no such thing as relativistic frequency
>>>> precompensation.
>>>
>>> Three points.
>>>
>>> **1. "If only it was the only prediction..."**
>>>
>>> You keep repeating this mysterious insinuation.
>>>
>>> Which OTHER prediction of relativity do you claim is experimentally 
>>> wrong?
>>>
>>> Name one. Just one.
>>
>>
>> Ever heard of "time dilation", poor piece of
>> shit?
>>
>>
>>
>>>
>>> **2. "You lied about NOT THE REAL TIME!"**
>>>
>>> Then produce the exact quotation where I wrote those words.
>>
>> Fuck off, you've got it already. It's not
>> my problem that your memory isn't better
>> than your "logic".
>>
>>
>>
>>> **3. "There is no such thing as relativistic frequency 
>>> precompensation."**
>>>
>>> Oh, Maciej. Seriously?
>>>
>>> Please read the official GPS Interface Specification, IS-GPS-200N, 
>>> section 3.3.1.1.
>>>
>>> It explicitly specifies a satellite frequency offset to compensate 
>>> for relativistic effects:
>>
>> It's mistaken, happens. There is no such thing.
>> Your mad Shit was trying to forbid this compensation
>> for the sake of fulfilling the idiot's prophecies.
> 
> This is getting spectacular. :-)
> 
> https://ibb.co/39x3fKZP
> 
> **1. Your allegedly falsified prediction: "Time dilation."**
> 
> Excellent. Which experiment contradicts the quantitative relativistic 
> prediction?

One clock indication: 2026-11-23:00:00.00000000->
the other clock indication:2026-11-23:00:00.00000000.
Common sense had been warning the idiot.
And, yes, the clocks are calibrated, so don't
lie I'm avoiding admitting that, poor piece of
shit.

> **2. Your alleged quotation.**
> 
> Still no quotation.
> 
> Just another insult.

You've got it already and, of course,
learned nothing. Waste of my time.

> 


> **3. The official GPS specification.**
> 
> Now THIS is priceless.
> 
> I show you an official engineering document specifying the relativistic 
> frequency offset, and your response is:
> 
>     "It's mistaken, happens. There is no such thing."
> 
> So the GPS engineers are wrong about their own specification?

They don't know The Shit well. And I can't
blame them they don't understand someone
could be stupid enough to forbid the
synchronization of clocks for the sake
of some moronic symmetry.

>     "Your mad Shit was trying to forbid
>      this compensation..."
> 
> Really?

Really.


> 
> Please identify the equation in special or general relativity that 
> forbids adjusting an oscillator's frequency.

Your  Holiest Postulate isn't an equation,
poor piece of shit.
And it's not about adjusting an oscillator
frequency but about counting a second with
+4 Cs periods on the satellite.



> There is none.
> 
> Relativity predicts the frequency difference.

If only it was the only prediction of your
mad Shit. Isn't it predicting "time dilation"
as well?




[toc] | [prev] | [next] | [standalone]


#676377

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 22:36 +0000
Message-ID<XJwKlbju-cTsOCpZELs4OQBbrwk@jntp>
In reply to#676376
Le 21/11/2026 à 23:34, Maciej Woźniak a écrit :
> On 11/21/2026 11:20 PM, Python wrote:
>> Le 21/11/2026 à 23:15, Maciej Woźniak a écrit :
>>> On 11/21/2026 11:02 PM, Python wrote:
>>>> Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
>>>>> On 11/21/2026 10:44 PM, Python wrote:
>>>>>> Maciej,
>>>>>>
>>>>>> You keep repeating:
>>>>>>
>>>>>>     t' = t
>>>>>>
>>>>>> Fine. But what exactly was measured?
>>>>>>
>>>>>> Two clock displays showing the same time?
>>>>>>
>>>>>> Before or after synchronization and frequency compensation?
>>>>>>
>>>>>> Because setting two clocks to agree is not an experimental 
>>>>>> refutation of a theory predicting how their unadjusted rates differ.
>>>>>
>>>>> If only it was the only prediction of your moronic Shit...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Quite the opposite: the adjustments themselves can be 
>>>>>> quantitatively tested against the theory.
>>>>>>
>>>>>> You claim scientists dismissed contradictory measurements.
>>>>>>
>>>>>> Yet your only example is the agreement of clocks deliberately 
>>>>>> operated to maintain a common time scale.
>>>>>>
>>>>>> That's not a suppressed anomaly. That's the engineering objective.
>>>>>>
>>>>>> And now you accuse me of "lying" and being "ashamed".
>>>>>>
>>>>>> Lying about what, precisely?
>>>>>
>>>>> About most things you babble about; this time about
>>>>> "I never used that expression.[not the real time] You invented it, 
>>>>> put it in my mouth, and then attacked it. "
>>>>>
>>>>>
>>>>>> If GPS clock rates already agreed naturally, why was relativistic 
>>>>>> frequency precompensation specified in the first place?
>>>>>
>>>>> There is no such thing as relativistic frequency
>>>>> precompensation.
>>>>
>>>> Three points.
>>>>
>>>> **1. "If only it was the only prediction..."**
>>>>
>>>> You keep repeating this mysterious insinuation.
>>>>
>>>> Which OTHER prediction of relativity do you claim is experimentally 
>>>> wrong?
>>>>
>>>> Name one. Just one.
>>>
>>>
>>> Ever heard of "time dilation", poor piece of
>>> shit?
>>>
>>>
>>>
>>>>
>>>> **2. "You lied about NOT THE REAL TIME!"**
>>>>
>>>> Then produce the exact quotation where I wrote those words.
>>>
>>> Fuck off, you've got it already. It's not
>>> my problem that your memory isn't better
>>> than your "logic".
>>>
>>>
>>>
>>>> **3. "There is no such thing as relativistic frequency 
>>>> precompensation."**
>>>>
>>>> Oh, Maciej. Seriously?
>>>>
>>>> Please read the official GPS Interface Specification, IS-GPS-200N, 
>>>> section 3.3.1.1.
>>>>
>>>> It explicitly specifies a satellite frequency offset to compensate 
>>>> for relativistic effects:
>>>
>>> It's mistaken, happens. There is no such thing.
>>> Your mad Shit was trying to forbid this compensation
>>> for the sake of fulfilling the idiot's prophecies.
>> 
>> This is getting spectacular. :-)
>> 
>> https://ibb.co/39x3fKZP
>> 
>> **1. Your allegedly falsified prediction: "Time dilation."**
>> 
>> Excellent. Which experiment contradicts the quantitative relativistic 
>> prediction?
> 
> One clock indication: 2026-11-23:00:00.00000000->
> the other clock indication:2026-11-23:00:00.00000000.
> Common sense had been warning the idiot.
> And, yes, the clocks are calibrated, so don't
> lie I'm avoiding admitting that, poor piece of
> shit.
> 
>> **2. Your alleged quotation.**
>> 
>> Still no quotation.
>> 
>> Just another insult.
> 
> You've got it already and, of course,
> learned nothing. Waste of my time.
> 
>> 
> 
> 
>> **3. The official GPS specification.**
>> 
>> Now THIS is priceless.
>> 
>> I show you an official engineering document specifying the relativistic 
>> frequency offset, and your response is:
>> 
>>     "It's mistaken, happens. There is no such thing."
>> 
>> So the GPS engineers are wrong about their own specification?
> 
> They don't know The Shit well. And I can't
> blame them they don't understand someone
> could be stupid enough to forbid the
> synchronization of clocks for the sake
> of some moronic symmetry.
> 
>>     "Your mad Shit was trying to forbid
>>      this compensation..."
>> 
>> Really?
> 
> Really.
> 
> 
>> 
>> Please identify the equation in special or general relativity that 
>> forbids adjusting an oscillator's frequency.
> 
> Your  Holiest Postulate isn't an equation,
> poor piece of shit.
> And it's not about adjusting an oscillator
> frequency but about counting a second with
> +4 Cs periods on the satellite.
> 
> 
> 
>> There is none.
>> 
>> Relativity predicts the frequency difference.
> 
> If only it was the only prediction of your
> mad Shit. Isn't it predicting "time dilation"
> as well?

You have now admitted that the clocks are calibrated.

And you acknowledge a frequency difference of approximately four caesium 
cycles per second.

Yet you insist that equal clock indications refute time dilation.

Let's make this very simple.

**Time dilation is precisely about differences in elapsed proper time 
along different worldlines.**

For atomic clocks, those differences manifest as differences in 
accumulated cycles and, consequently, in clock readings.

The GPS frequency offset compensates for a predicted rate difference so 
that the satellite clock signals can represent a common coordinate-time 
scale.

You cannot simultaneously acknowledge the rate difference, acknowledge the 
calibration, and then present the resulting agreement as evidence that the 
rate difference does not exist.

That's like adjusting two watches to run together and declaring that their 
original rate difference has been disproved.

As for your claim that Einstein's postulates *forbid* compensation: which 
postulate, and how?

Please show the logical implication.

And one final observation:

You have now rejected an official GPS specification because, according to 
you, its engineers don't understand relativity.

Apparently, when measurements disagree with your interpretation, it's the 
engineers who are wrong.

Remind me again who was accusing whom of treating physics as a religion.

[toc] | [prev] | [next] | [standalone]


#676378

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-21 23:50 +0100
Message-ID<18ea3120216f4b64$28065$44714$c2565adb@news.newsdemon.com>
In reply to#676377
On 11/21/2026 11:36 PM, Python wrote:
> Le 21/11/2026 à 23:34, Maciej Woźniak a écrit :
>> On 11/21/2026 11:20 PM, Python wrote:
>>> Le 21/11/2026 à 23:15, Maciej Woźniak a écrit :
>>>> On 11/21/2026 11:02 PM, Python wrote:
>>>>> Le 21/11/2026 à 22:58, Maciej Woźniak a écrit :
>>>>>> On 11/21/2026 10:44 PM, Python wrote:
>>>>>>> Maciej,
>>>>>>>
>>>>>>> You keep repeating:
>>>>>>>
>>>>>>>     t' = t
>>>>>>>
>>>>>>> Fine. But what exactly was measured?
>>>>>>>
>>>>>>> Two clock displays showing the same time?
>>>>>>>
>>>>>>> Before or after synchronization and frequency compensation?
>>>>>>>
>>>>>>> Because setting two clocks to agree is not an experimental 
>>>>>>> refutation of a theory predicting how their unadjusted rates differ.
>>>>>>
>>>>>> If only it was the only prediction of your moronic Shit...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Quite the opposite: the adjustments themselves can be 
>>>>>>> quantitatively tested against the theory.
>>>>>>>
>>>>>>> You claim scientists dismissed contradictory measurements.
>>>>>>>
>>>>>>> Yet your only example is the agreement of clocks deliberately 
>>>>>>> operated to maintain a common time scale.
>>>>>>>
>>>>>>> That's not a suppressed anomaly. That's the engineering objective.
>>>>>>>
>>>>>>> And now you accuse me of "lying" and being "ashamed".
>>>>>>>
>>>>>>> Lying about what, precisely?
>>>>>>
>>>>>> About most things you babble about; this time about
>>>>>> "I never used that expression.[not the real time] You invented it, 
>>>>>> put it in my mouth, and then attacked it. "
>>>>>>
>>>>>>
>>>>>>> If GPS clock rates already agreed naturally, why was relativistic 
>>>>>>> frequency precompensation specified in the first place?
>>>>>>
>>>>>> There is no such thing as relativistic frequency
>>>>>> precompensation.
>>>>>
>>>>> Three points.
>>>>>
>>>>> **1. "If only it was the only prediction..."**
>>>>>
>>>>> You keep repeating this mysterious insinuation.
>>>>>
>>>>> Which OTHER prediction of relativity do you claim is experimentally 
>>>>> wrong?
>>>>>
>>>>> Name one. Just one.
>>>>
>>>>
>>>> Ever heard of "time dilation", poor piece of
>>>> shit?
>>>>
>>>>
>>>>
>>>>>
>>>>> **2. "You lied about NOT THE REAL TIME!"**
>>>>>
>>>>> Then produce the exact quotation where I wrote those words.
>>>>
>>>> Fuck off, you've got it already. It's not
>>>> my problem that your memory isn't better
>>>> than your "logic".
>>>>
>>>>
>>>>
>>>>> **3. "There is no such thing as relativistic frequency 
>>>>> precompensation."**
>>>>>
>>>>> Oh, Maciej. Seriously?
>>>>>
>>>>> Please read the official GPS Interface Specification, IS-GPS-200N, 
>>>>> section 3.3.1.1.
>>>>>
>>>>> It explicitly specifies a satellite frequency offset to compensate 
>>>>> for relativistic effects:
>>>>
>>>> It's mistaken, happens. There is no such thing.
>>>> Your mad Shit was trying to forbid this compensation
>>>> for the sake of fulfilling the idiot's prophecies.
>>>
>>> This is getting spectacular. :-)
>>>
>>> https://ibb.co/39x3fKZP
>>>
>>> **1. Your allegedly falsified prediction: "Time dilation."**
>>>
>>> Excellent. Which experiment contradicts the quantitative relativistic 
>>> prediction?
>>
>> One clock indication: 2026-11-23:00:00.00000000->
>> the other clock indication:2026-11-23:00:00.00000000.
>> Common sense had been warning the idiot.
>> And, yes, the clocks are calibrated, so don't
>> lie I'm avoiding admitting that, poor piece of
>> shit.
>>
>>> **2. Your alleged quotation.**
>>>
>>> Still no quotation.
>>>
>>> Just another insult.
>>
>> You've got it already and, of course,
>> learned nothing. Waste of my time.
>>
>>>
>>
>>
>>> **3. The official GPS specification.**
>>>
>>> Now THIS is priceless.
>>>
>>> I show you an official engineering document specifying the 
>>> relativistic frequency offset, and your response is:
>>>
>>>     "It's mistaken, happens. There is no such thing."
>>>
>>> So the GPS engineers are wrong about their own specification?
>>
>> They don't know The Shit well. And I can't
>> blame them they don't understand someone
>> could be stupid enough to forbid the
>> synchronization of clocks for the sake
>> of some moronic symmetry.
>>
>>>     "Your mad Shit was trying to forbid
>>>      this compensation..."
>>>
>>> Really?
>>
>> Really.
>>
>>
>>>
>>> Please identify the equation in special or general relativity that 
>>> forbids adjusting an oscillator's frequency.
>>
>> Your  Holiest Postulate isn't an equation,
>> poor piece of shit.
>> And it's not about adjusting an oscillator
>> frequency but about counting a second with
>> +4 Cs periods on the satellite.
>>
>>
>>
>>> There is none.
>>>
>>> Relativity predicts the frequency difference.
>>
>> If only it was the only prediction of your
>> mad Shit. Isn't it predicting "time dilation"
>> as well?
> 
> You have now admitted that the clocks are calibrated.
> 
> And you acknowledge a frequency difference of approximately four caesium 
> cycles per second.
> 
> Yet you insist that equal clock indications refute time dilation.
> 
> Let's make this very simple.
> 
> **Time dilation is precisely about differences in elapsed proper time 
> along different worldlines.**
> 
> For atomic clocks, those differences manifest as differences in 
> accumulated cycles and, consequently, in clock readings.

In your sick gedanken delusions - sure. In
the reality clock readings are:
One clock indication: 2026-11-23:00:00.00000000->
the other clock indication:2026-11-23:00:00.00000000.
Common sense had been warning the idiot.

And, yes, the clocks are calibrated, so don't
lie I'm avoiding admitting that, poor piece of
shit.


> As for your claim that Einstein's postulates *forbid* compensation: 
> which postulate, and how?

Postulate of relativity, of course.
According to it Cs clocks should
work exactly the same way in
every frame. Will you have the
impudence to deny, poor piece of
shit?


> 
> Please show the logical implication.
> 
> And one final observation:
> 
> You have now rejected an official GPS specification because, according 
> to you, its engineers don't understand relativity.
I can't blame them they don't understand someone
could be stupid enough to forbid the
synchronization of clocks for the sake
of some moronic symmetry.

Can you, poor piece of shit?

[toc] | [prev] | [next] | [standalone]


#676379

FromPython <jpierre.messager@gmail.com>
Date2026-11-21 22:55 +0000
Message-ID<la-YNT9GewYUoKV7RTZdDbr7tOY@jntp>
In reply to#676378
OH! An actual argument.

You write:

    "According to [the principle of relativity]
     Cs clocks should work exactly the same way
     in every frame."

**Correct!**

An ideal caesium clock at rest in any local inertial frame obeys the same 
physical laws and has the same proper frequency.

Nobody disputes that.

But you have silently replaced:

    "The laws of physics are the same"

with:

    "All clocks must accumulate identical
     elapsed times along different worldlines."

These are NOT equivalent statements.

In fact, time dilation follows from the Lorentz transformations, which 
themselves embody the principle of relativity.

Your alleged contradiction is a prediction of the theory.

And GPS engineers don't change the laws governing caesium atoms. They 
adjust oscillator frequencies so that satellite signals can represent GPS 
coordinate time.

The atoms still obey the same physics.

The clocks simply follow different worldlines.

As for your two identical timestamps: yes, calibrated clocks can display 
identical readings.

Congratulations. You've discovered synchronization.

Now explain why the calibration was necessary.

And please stop claiming that relativity forbids synchronization.

It doesn't.

You've confused a symmetry of physical laws with an equality of clock 
readings.

That's not a subtle distinction.

It's the very distinction on which your entire argument collapses.

[toc] | [prev] | [next] | [standalone]


#676380

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-22 07:29 +0100
Message-ID<18ea4a308c191371$30600$2984126$c2065a8b@news.newsdemon.com>
In reply to#676379
On 11/21/2026 11:55 PM, Python wrote:
> OH! An actual argument.
> 
> You write:
> 
>     "According to [the principle of relativity]
>      Cs clocks should work exactly the same way
>      in every frame."
> 
> **Correct!**

Of course it's correct that your mad Shit has
been trying to forbid GPS compensations. And
if it was successful - the "time dilation"
would really happen, as prophesied. But there
was never any chance of success, common sense
had been warning the idiot.


> And GPS engineers don't change the laws governing caesium atoms. 

Of course they don't. Your mad Shit is not
a set of laws governing Cs atoms and the whole
Universe, it's a piece of software, the only
thing it can  govern are the brains of its
unfortunate  victims. What is quite much, of
course.





They
> adjust oscillator frequencies so that satellite signals can represent 
> GPS coordinate time.
> 
> The atoms still obey the same physics.
> 
> The clocks simply follow different worldlines.
> 
> As for your two identical timestamps: yes, calibrated clocks can display 
> identical readings.
> 
> Congratulations. You've discovered synchronization.
> 
> Now explain why the calibration was necessary.

Simple. Because your assertion that the clocks would
be perfectly good without it is as baseless as it is
idiotic.



> 
> And please stop claiming that relativity forbids synchronization.
> 
> It doesn't.

Yes it does.
  "According to [the principle of relativity]
       Cs clocks should work exactly the same way
       in every frame."

[toc] | [prev] | [next] | [standalone]


#676383

FromPython <jpierre.messager@gmail.com>
Date2026-11-22 09:16 +0000
Message-ID<o38lCD602kxNi_2YAh4YbjO1DyE@jntp>
In reply to#676380
Maciej,

You keep repeating:

    "Cs clocks should work exactly the same way
     in every frame."

Yes. **The same laws. The same proper frequency.**

Not necessarily the same accumulated elapsed time along different 
worldlines.

You have been told this distinction repeatedly, yet you simply ignore it.

Now you claim that GPS compensation *prevents* time dilation.

Really?

Suppose an uncompensated clock gains 38 microseconds per day relative to a 
reference time scale.

Engineers adjust its frequency so that its output stays aligned with that 
reference.

Does the adjustment prove the original rate difference never existed?

Of course not.

**Compensating for an effect does not abolish the effect.**

A thermostat doesn't abolish heat loss.

Noise cancellation doesn't abolish sound waves.

And GPS frequency compensation doesn't abolish relativistic clock-rate 
differences.

As for your assertion that relativity "forbids" synchronization:

Please derive that prohibition from the principle of relativity.

Not by repeating the principle.

By showing the logical steps.

Because the statement "physical laws are identical in inertial frames" 
does not imply "all clocks must display identical readings regardless of 
their trajectories and adjustments."

That implication exists only in your imagination.

You are not refuting relativity, Maciej.

You are repeatedly refuting something relativity never claimed.

[toc] | [prev] | [next] | [standalone]


#676384

FromMaciej Woźniak <mlwozniak@wp.pl>
Date2026-11-22 11:28 +0100
Message-ID<18ea573991079816$41110$2964695$c2265aab@news.newsdemon.com>
In reply to#676383
On 11/22/2026 10:16 AM, Python wrote:
> Maciej,
> 
> You keep repeating:
> 
>     "Cs clocks should work exactly the same way
>      in every frame."
> 
> Yes. **The same laws. The same proper frequency.**
> 
> Not necessarily the same accumulated elapsed time along different 
> worldlines.

Right. The idiot imagined that the clocks should
be identical and should desynchronize and should have
some moronic symmetry. And announced his what-should-be
delusion to be The Eternal Law of Nature. That's the
whole story.




> 
> You have been told this distinction repeatedly, yet you simply ignore it.
> 
> Now you claim that GPS compensation *prevents* time dilation.
> 
> Really?

R-E-A-L-L-Y.
It's now 2026-11-22 12:00:00.00000000 on one clock
and 2026-11-22 12:00:00.00000000 on others.
With the precision of an acceptable error.

[toc] | [prev] | [next] | [standalone]


Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | sci.physics.relativity


csiph-web