we finally learn that by "objective" you meant:
-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
Maciej Wo+|niak wrote:
we finally learn that by "objective" you meant:
-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
you cant combine that, cretin, the object there means that is class
template based, that includes both methods and data
On 10/18/2026 1:37 AM, Python wrote:
Le 17/10/2026 |a 22:19, Maciej Wo+|niak a |-crit :
On 10/17/2026 9:17 PM, Russell Bahmutoff wrote:
Maciej Wo+|niak wrote:
On 10/17/2026 8:24 PM, The Starmaker wrote:
In other words, there is no Physics.
yous made it all up!
Physics is a piece of objective software designed for a monkey's brain. >>>>> And that it's made up doesn't mean it doesn't exist.
very big truth once again, but it's only
objective because
By objective I mean that.
https://en.wikipedia.org/wiki/Object-oriented_programming
So after several days of:
-a-a "objective physics"
-a-a "objective reality"
-a-a "objective software"
we finally learn that by "objective" you meant:
-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
Le 18/10/2026 |a 07:47, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:37 AM, Python wrote:
Le 17/10/2026 |a 22:19, Maciej Wo+|niak a |-crit :
On 10/17/2026 9:17 PM, Russell Bahmutoff wrote:
Maciej Wo+|niak wrote:
On 10/17/2026 8:24 PM, The Starmaker wrote:
In other words, there is no Physics.
yous made it all up!
Physics is a piece of objective software designed for a monkey's
brain.
And that it's made up doesn't mean it doesn't exist.
very big truth once again, but it's only
objective because
By objective I mean that.
https://en.wikipedia.org/wiki/Object-oriented_programming
So after several days of:
-a-a-a "objective physics"
-a-a-a "objective reality"
-a-a-a "objective software"
we finally learn that by "objective" you meant:
-a-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
No. The adjective is:
-a-a object-oriented
not:
-a-a objective.
On 10/18/2026 1:00 PM, Python wrote:
Le 18/10/2026 |a 07:47, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:37 AM, Python wrote:
Le 17/10/2026 |a 22:19, Maciej Wo+|niak a |-crit :
On 10/17/2026 9:17 PM, Russell Bahmutoff wrote:
Maciej Wo+|niak wrote:
On 10/17/2026 8:24 PM, The Starmaker wrote:
In other words, there is no Physics.
yous made it all up!
Physics is a piece of objective software designed for a monkey's >>>>>>> brain.
And that it's made up doesn't mean it doesn't exist.
very big truth once again, but it's only
objective because
By objective I mean that.
https://en.wikipedia.org/wiki/Object-oriented_programming
So after several days of:
-a-a-a "objective physics"
-a-a-a "objective reality"
-a-a-a "objective software"
we finally learn that by "objective" you meant:
-a-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
No. The adjective is:
-a-a object-oriented
not:
-a-a objective.
So it must be "object oriented c" not "objective c", right,
poor piece of shit?
On 10/18/2026 1:00 PM, Python wrote:
Le 18/10/2026 |a 07:47, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:37 AM, Python wrote:
Le 17/10/2026 |a 22:19, Maciej Wo+|niak a |-crit :
On 10/17/2026 9:17 PM, Russell Bahmutoff wrote:
Maciej Wo+|niak wrote:
On 10/17/2026 8:24 PM, The Starmaker wrote:
In other words, there is no Physics.
yous made it all up!
Physics is a piece of objective software designed for a monkey's >>>>>>> brain.
And that it's made up doesn't mean it doesn't exist.
very big truth once again, but it's only
objective because
By objective I mean that.
https://en.wikipedia.org/wiki/Object-oriented_programming
So after several days of:
"objective physics"
"objective reality"
"objective software"
we finally learn that by "objective" you meant:
object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
No. The adjective is:
object-oriented
not:
objective.
So it must be "object oriented c" not "objective c", right,
poor piece of shit?
Le 18/10/2026 |a 13:54, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:00 PM, Python wrote:
Le 18/10/2026 |a 07:47, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:37 AM, Python wrote:
Le 17/10/2026 |a 22:19, Maciej Wo+|niak a |-crit :
On 10/17/2026 9:17 PM, Russell Bahmutoff wrote:
Maciej Wo+|niak wrote:
On 10/17/2026 8:24 PM, The Starmaker wrote:
In other words, there is no Physics.
yous made it all up!
Physics is a piece of objective software designed for a monkey's >>>>>>>> brain.
And that it's made up doesn't mean it doesn't exist.
very big truth once again, but it's only
objective because
By objective I mean that.
https://en.wikipedia.org/wiki/Object-oriented_programming
So after several days of:
-a-a-a "objective physics"
-a-a-a "objective reality"
-a-a-a "objective software"
we finally learn that by "objective" you meant:
-a-a-a object-oriented.
Nope. Usually "objective" means something else.
But when combined with "software" it's this meaning.
No. The adjective is:
-a-a-a object-oriented
not:
-a-a-a objective.
So it must be "object oriented c" not "objective c", right,
poor piece of shit?
:-)))))
"Objective-C" is the proper name of a programming language.
On 10/18/2026 1:57 PM, Python wrote:..
"Objective-C" is the proper name of a programming language.
[argument snipped]
And it is obviously wrong name, right, poor piece
of shit? Should be "object oriented c" instead?
Le 18/10/2026 |a 14:10, Maciej Wo+|niak a |-crit :
On 10/18/2026 1:57 PM, Python wrote:..
"Objective-C" is the proper name of a programming language.
[argument snipped]
And it is obviously wrong name, right, poor piece
of shit? Should be "object oriented c" instead?
:-)
I see why you snipped everything below the first two lines.
If you prefer your moronic physics
to be a piece of object-oriented software
- let it be.
Maciej,
If you prefer your moronic physics
to be a piece of object-oriented software
- let it be.
:-)))
MY physics?
Let's review who introduced this magnificent thesis:
-a-a "Physics is a piece of objective software
-a-a-a designed for a monkey's brain."
That was YOU.
Then YOU explained that "objective" meant "object-oriented".
And now, three posts later, it has somehow become MY claim that physics
is object-oriented software.
This is getting into small-child-with-jam-all-over-his-face territory:
-a-a "I didn't eat the jam."
Maciej, YOU wrote:
-a-a "Physics is a piece of objective software"
YOU explained that "objective" meant "object-oriented".
And now "physics is object-oriented software" is somehow "your physics", meaning everyone else's.
I don't identify with brainwashing religions,
it's yours.
I don't identify with brainwashing religions,
it's yours.
Nobody asked what you identify with.
YOU wrote:
-a-a "Physics is a piece of objective software"
YOU explained:
-a-a "objective" = "object-oriented"
And now the resulting proposition belongs to us because you don't
"identify" with physics.
than what he considered the important idea: MESSAGING.
His description of OOP was essentially:
messaging hidden/local state extreme late binding
He even famously remarked that when he invented "object-oriented", he certainly did not have C++ in mind.
Your moronic physics IS a piece of object-oriented
software
Maciej,
Your moronic physics IS a piece of object-oriented
software
There we are.
So it IS your thesis after all.
On 10/19/2026 12:43 PM, Python wrote:
Maciej,
Your moronic physics IS a piece of object-oriented
software
There we are.
So it IS your thesis after all.
Of course it's not yours, you're far, far,
far too dumb for it, but your dumbness
doesn't change the facts, poor piece of
shit.
Le 19/10/2026 |a 13:05, Maciej Wo+|niak a |-crit :
On 10/19/2026 12:43 PM, Python wrote:
Maciej,
Your moronic physics IS a piece of object-oriented
software
There we are.
So it IS your thesis after all.
Of course it's not yours, you're far, far,
far too dumb for it, but your dumbness
doesn't change the facts, poor piece of
shit.
Fine. Let's examine your grand thesis itself:
-a-a "Physics is a piece of object-oriented software
-a-a-a designed for a monkey's brain."
What exactly makes physics "object-oriented software"?
Mostly - that uploaded to a brain of an idiot
like yourself it is giving that brain new
abilities.
Mostly - that uploaded to a brain of an idiot
like yourself it is giving that brain new
abilities.
That doesn't make it object-oriented software.
It doesn't even make it software.
Learning arithmetic gives a child new abilities.
Learning Polish gives a child new abilities.
Learning chess gives a child new abilities.
Are arithmetic, Polish and chess all object-oriented software?
Exactly
And "object oriented" - is because of its structure.
Can't AI deal with all of them? If it can, you should know:
it's software.
Maciej,
Exactly
Excellent. So now arithmetic, Polish and chess are literally software.
Your definition is apparently:
-a-a anything learned that gives a brain new abilities = software
That isn't a result from computer science. It's a metaphor you've
promoted to a definition.
And then:
And "object oriented" - is because of its structure.
Ah, the long-awaited technical explanation:
-a-a because of its structure.
WHAT structure?
Object-oriented programming has identifiable structural concepts:
objects, encapsulated state/behaviour, message passing or method
dispatch, classes/prototypes depending on the model, polymorphism, etc.
You have identified precisely none of these.
Can't AI deal with all of them? If it can, you should know:
it's software.
A weather program can deal with hurricanes.
Therefore hurricanes are software?
A chess program can deal with chess, a translator with Polish, and a
CAS with arithmetic. That tells us something about what software can REPRESENT and PROCESS, not what those things ARE.
What is arithmetic?
What is Polish [language]?
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.
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...
the model/software applied really for GPS has little in common with your idiocies.
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:
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.
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:
-a-a corrected BY HOW MUCH?
For sure not by 0 predicted by your
moronic Shit.
Maciej,
For sure not by 0 predicted by your
moronic Shit.
Relativity predicted:
-a-a +446.5 |u 10^-12
NTS-2 measured, correction OFF:
-a-a +442.5 |u 10^-12
Maciej,
This is just relabelling the SAME observable.
Voil|a! Two falsifications manufactured entirely by changing the label between prediction and measurement.
no, "time dilation" and "clock error" are not
the same.
asserting that your junk clocks are
perfect was intended to prevent correcting them
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.
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.
You could as well mumble that saying
"a sheep" i just relabel the concept of
an animal eating grass, which is obviously
a shark.
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.
That's why your bunch of idiots could never falsify it.
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.
-a-a predicted: +446.5 |u 10^-12
-a-a measured:-a +442.5 |u 10^-1
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.
-a-a THE CLOCK IS WRONG!
A lie, of course. Measured - 0.
if it wasn't it wouldn't be corrected.
What is the whole concept of a clock error?
A lie. Again.A lie, of course. Measured - 0.
No.
What is the whole concept of a clock error?
Indeed.
You desperately NEED the 442.5 |u 10^-12 to be a mysterious "clock
error", because otherwise something rather embarrassing happened:
The clock produced 442.5 |u 10^-12 with the correction OFF.
And your alternative explanation is:
-a-a could be a billion possible reasons
-a-a including unknown reasons
Magnificent.
Relativity: 446.5.
the indication of one (ground) clock is
2026-10-19 22:00:00.000000000.
What is the indication of the satellite clock?
It is CORRECTED. Fits the "error" concept, doesn't
fit your "dilation" idiocy. Game over.
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
What happened?
-a-a prediction before launch:-a +446.5 |u 10^-12
AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME
DILATION - IS 0.
2 kg of eaten grass!! By some animal!!!!
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:
-a-a predicted rate difference: +446.5 |u 10^-12
"CALIBRATED CLOCKS!!! DELIBERATELY!!!
DOESN'T COUNT!!!"
Maciej,
"CALIBRATED CLOCKS!!! DELIBERATELY!!!
DOESN'T COUNT!!!"
You're still confusing CALIBRATION with COMPENSATION.
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.
deliberate modifying measurement devices is only allowed
when the result will fit One And Only True Shit of Einstein.
Maciej,
deliberate modifying measurement devices is only allowed
when the result will fit One And Only True Shit of Einstein.
You have managed to reverse the chronology again.
The correction was OFF.
OFF, Maciej.
That's precisely why NTS-2 was a test.
Relativity predicts: +446.5 |u 10^-12
Correction: OFF
Clock measures: +442.5 |u 10^-12
Only AFTER that measurement was the correction switched ON.
So your accusation is now:
"They modified the device to obtain the predicted result!"
when the predicted result was obtained while the modification you're complaining about was explicitly disabled.
This is becoming difficult to parody.
You are doing it faster than I can.
On 10/19/2026 02:55 PM, Python wrote:
Maciej,
deliberate modifying measurement devices is only allowed
when the result will fit One And Only True Shit of Einstein.
You have managed to reverse the chronology again.
The correction was OFF.
OFF, Maciej.
That's precisely why NTS-2 was a test.
Relativity predicts: +446.5 |u 10^-12
Correction: OFF
Clock measures: +442.5 |u 10^-12
Only AFTER that measurement was the correction switched ON.
So your accusation is now:
"They modified the device to obtain the predicted result!"
when the predicted result was obtained while the modification you're
complaining about was explicitly disabled.
This is becoming difficult to parody.
You are doing it faster than I can.
This is physics: not parody.
(It is a bit parrot-y, ..., yet there aren't really bits for par-ity.)
It's a gauge theory and a continuum mechanics.
Maciej,
deliberate modifying measurement devices is only allowed
when the result will fit One And Only True Shit of Einstein.
You have managed to reverse the chronology again.
The correction was OFF.
OFF, Maciej.
That's precisely why NTS-2 was a test.
-a-a Relativity predicts:-a-a-a-a +446.5 |u 10^-12
-a-a "They modified the device to obtain the predicted result!"
when the predicted result was obtained while the modification you're complaining about was explicitly disabled.
They modified (calibrated)
the device to obtain THE CORRECT result.
Maciej,
They modified (calibrated)
the device to obtain THE CORRECT result.
You keep running away from the chronology:
Calling the first number "time dilation" and the second "clock error"
doesn't make two observables.
It's the same measured frequency shift.
The engineer still needs to know BY HOW MUCH to compensate.
Relativity gave the number before launch.
Your "common sense" renamed it after measurement.
That's not physics.
the chronology:
it's just completely insignificant.
"clock error" and "time dilation"
ARE two different observables.
your mad religion is asserting that
it should be 0
Maciej,
the chronology:
it's just completely insignificant.
Of course. Prediction BEFORE measurement is "completely insignificant"
when your entire alternative consists of explaining the result AFTER measurement.
"clock error" and "time dilation"
ARE two different observables.
No.
all day long.
The numbers won't care.
your mad religion is asserting that
it should be 0
This is simply false.
It asserted +446.5 |u 10^-12.
Before launch.
Correction OFF.
You say: "a shark will eat 2kg of grass."
A sheep eats 2kg of grass.
it would be perfect, correct, proper if they stayed off.
Maciej,
You say: "a shark will eat 2kg of grass."
A sheep eats 2kg of grass.
No. Your analogy fails exactly where you need it.
Relativity predicted a specific observable: the orbital clock's
fractional frequency shift.
it would be perfect, correct, proper if they stayed off.
YES.
A lie. It predicts your time dilation nonsense.
Not just a "frequency shift"
sane people have a different opinion. In their opinion when
clocks desynchronize it's NOT proper, NOT correct, NOT perfect
A lie. It predicts your time dilation nonsense.
Not just a "frequency shift"
Enough bullshit.
"Time dilation" here HAS an observable quantitative consequence:
sane people have a different opinion. In their opinion when
clocks desynchronize it's NOT proper, NOT correct, NOT perfect
This is your other lie.
Engineers correcting a physical effect to satisfy an engineering
requirement does NOT imply they believe the physical prediction was
wrong.
the difference in clock INDICATIONS. Really - 0. Falsified.
Yeah, right, the clocks have been calibrated,
I know.
engineers correcting junk clocks
Maciej,
the difference in clock INDICATIONS. Really - 0. Falsified.
Yeah, right, the clocks have been calibrated,
I know.
You have finally compressed your entire argument into four lines:
-a-a The predicted difference is zero.
-a-a Because the predicted difference was compensated.
engineers correcting junk clocks
They are not correcting "junk clocks". They are deliberately
That's the difference between a sheep (error)
and a shark (dilation). We compensate the first,
we don't compensate the other.
That's the difference between a sheep (error)
and a shark (dilation). We compensate the first,
we don't compensate the other.
And there it is: your entire argument is a definition YOU invented.
-a-a If compensated -> error.
-a-a If dilation-a-a-a -> must not be compensated.
Why?
Relativity predicts the rate shift.
That's not an experiment.
That's wordplay.
Your sheep and shark are the same fucking +442.5 |u 10^-12 wearing
different labels.
Because if it is compensated [...] there is no
"difference in clock indications"
Maciej,
Because if it is compensated [...] there is no
"difference in clock indications"
This is spectacularly circular:
-a-a If we compensate X, X disappears.
the "rate difference" we correct is an error,
the "rate difference" we accept would be
your time dilation.
the "rate difference" we correct is an error,
the "rate difference" we accept would be
your time dilation.
Thank you. You have finally stated the trick explicitly.
For you, the distinction is NOT physical.
It is:
-a-a same measured rate difference
-a-a-a-a-a-a |
-a-a-a-a-a-a +-- engineers accept it-a -> "time dilation"
-a-a-a-a-a-a |
-a-a-a-a-a-a +-- engineers compensate -> "clock error"
So whether a physical effect is "time dilation" depends on an
ENGINEERING DECISION made afterwards.
That's priceless.
If tomorrow GPS engineers decided not to compensate it, your
+442.5 |u 10^-12 would magically stop being a "clock error" and become
"time dilation".
That's a fact.
Go convince them [...] they have to stop compensating
Maciej,
That's a fact.
Excellent. You have now explicitly admitted that, in YOUR terminology,
the very same physical rate difference changes nature according to what engineers decide to do with it.
And then this masterpiece:
Go convince them [...] they have to stop compensating
Why would I?
Relativity predicts the effect.
If engineers compensate thermal expansion in a bridge, thermal
expansion doesn't cease to be physics.
Maciej,
They modified (calibrated)
the device to obtain THE CORRECT result.
You keep running away from the chronology:
Relativity predicted: +446.5 |u 10^-12
Correction: OFF
NTS-2 measured: +442.5 |u 10^-12
Correction: THEN switched ON
Calling the first number "time dilation" and the second "clock error"
doesn't make two observables. It's the same measured frequency shift.
And "the clocks should agree" predicts precisely nothing.
The engineer still needs to know BY HOW MUCH to compensate.
Relativity gave the number before launch.
Your "common sense" renamed it after measurement.
That's not physics.
That's bookkeeping with insults.
the REAL difference in clock indications is 0.
"perfect bridges should collapse"
Maciej,
the REAL difference in clock indications is 0.
Yes. AFTER compensating the predicted rate difference.
You have now reduced your argument to:
-a-a effect predicted
-a-a effect measured
-a-a effect compensated
-a-a compensated result ree 0
-a-a therefore effect never existed
And this:
"perfect bridges should collapse"
is precisely the same category error again.
Relativity does NOT say:
-a-a "perfect GPS clocks should desynchronize"
not any measured effect, just a clock
error.
Never existed. Exactly. Just a clock error.
Maciej,
not any measured effect, just a clock
error.
You keep saying "just a clock error" as though naming the measurement explained it.
It doesn't.
The inconvenient facts remain:
-a-a predicted before launch: +446.5 |u 10^-12
-a-a correction OFF
-a-a measured in orbit:-a-a-a-a-a-a +442.5 |u 10^-12
Why that magnitude?
Why that sign?
The measured effect never existed because you renamed the measured
effect "error".
Relativity provides a quantitative prediction.
Why that magnitude?
Why that sign?
Who cares?
Can't erroneous equipment "measure" effects
that don't exist?
the really measured value is 0
Maciej,
Why that magnitude?
Why that sign?
Who cares?
And there, finally, is your entire scientific method.
Relativity, BEFORE launch:
-a-a +446.5 |u 10^-12
Can't erroneous equipment "measure" effects
that don't exist?
Of course it can.
But when an alleged "error" has the magnitude and sign quantitatively predicted BEFORE the equipment is even put into orbit, a physicist asks
why.
the really measured value is 0
AFTER correcting by approximately the amount predicted.
So your "really measured value" is:
-a-a measured effect - compensation for measured effect ree 0
Fuck your so called "scientific method" crap.
My really measured value is the REAL
value of the difference in clock indications.
[...] 0.
Your mad shit has predicted 0 of clock error
to compensate.
Maciej,
Fuck your so called "scientific method" crap.
Yes, that was already becoming clear.
My really measured value is the REAL
value of the difference in clock indications.
[...] 0.
You keep measuring the result AFTER compensation and pretending it is
the measurement BEFORE compensation.
The chronology you declared "insignificant" is precisely what exposes
the trick:
-a-a correction OFF:-a +442.5 |u 10^-12 measured
-a-a correction ON:-a-a approximately 0 residual
You call only the second one "REAL" because the first one is
catastrophically inconvenient.
Your mad shit has predicted 0 of clock error
to compensate.
Relativity doesn't predict a malfunction called "clock error".
I call the second one real because
1)the first was for 20 days (about), the
other for 50 years
we corrected the clocks giving 1, so they were erroneous.
your mad Shit is predicting nothing to compensate.
Maciej,
I call the second one real because
1)the first was for 20 days (about), the
other for 50 years
This is priceless.
An experiment becomes less real because it lasted 20 days
we corrected the clocks giving 1, so they were erroneous.
No. You keep using your conclusion as your premise:
And the historical sequence remains brutally immune to your vocabulary:
-a-a BEFORE launch:
-a-a-a-a-a-a relativity calculates +446.5 |u 10^-12
-a-a IN orbit, correction OFF:
-a-a-a-a-a-a clock measures +442.5 |u 10^-12
-a-a AFTER measurement:
-a-a-a-a-a-a correction switched ON
You can call 442.5 a "clock error", a sheep, a shark, or the Archbishop
of Canterbury.
You still haven't explained why your "erroneous" clock made almost
exactly the error relativity calculated BEFORE IT FLEW.
your mad Shit is predicting nothing to compensate.
It predicted the physical rate shift that engineers compensate.
Your insistence that a theory must additionally call that shift an
"ERROR" before engineers are permitted to cancel it is entirely your invention.
Physics predicts what happens.
20 days compared to 50 years makes
an exception of no significance.
engineers are NOT permitted to cancel it.
Your theory is forbidding that
And then it doesn't happen
Maciej,
20 days compared to 50 years makes
an exception of no significance.
This may be your best one yet.
The 20 days are precisely when the predicted correction was OFF.
The following 50 years are precisely when GPS has been designed to
COMPENSATE relativistic effects.
So your argument is now:
-a-a The uncontaminated test doesn't count because it lasted only 20 days.
-a-a The following 50 years of cancelling the effect prove that the
-a-a effect being cancelled doesn't exist.
Magnificent.
engineers are NOT permitted to cancel it.
Your theory is forbidding that
This is simply something you invented.
Please provide the equation of relativity containing the operator
-a-a ENGINEERS_ARE_FORBIDDEN_TO_COMPENSATE()
There isn't one.
Relativity says what ideal clocks do along specified worldlines.
It does not dictate what frequency engineers must make an oscillator
output for a navigation system.
Engineers are perfectly free to compensate the predicted effect.
And then it doesn't happen
It DID happen.
That's the part you cannot make disappear:
-a-a predicted: +446.5 |u 10^-12
-a-a measured:-a +442.5 |u 10^-12
Then they compensated it.
Your entire argument is now that once humans deliberately prevent a
predicted effect from appearing in the final system output, the
prediction has failed.
By that standard, brakes falsify Newton.
-a-a Why did the uncorrected NTS-2 clock produce +442.5 |u 10^-12
-a-a when relativity had predicted +446.5 |u 10^-12 before launch?
Your answer remains:
-a-a "Who cares?"
Everyone who understands what a quantitative prediction is, Maciej.
That's rather the point.
Measured - 0.
And started the real measurements.
Maciej,
Measured - 0.
No.
You have now spent dozens of posts arguing that the first measurement
doesn't count because engineers subsequently cancelled what it measured.
And started the real measurements.
Wonderful.
So measurements become "real" only after engineers modify the clocks
And still, after all the shouting:
-a-a predicted before launch: +446.5
-a-a measured correction OFF: +442.5
Relativity supplied the number.
SOME clocks may fit any nonsense.
clocks which later (almost immediately) showed they're
unusable for measurements.
the measured REALLY value is 0.
Maciej,
the REAL difference in clock indications is 0.
Yes. AFTER compensating the predicted rate difference.
You have now reduced your argument to:
effect predicted
effect measured
effect compensated
compensated result ree 0
therefore effect never existed
And this:
"perfect bridges should collapse"
is precisely the same category error again.
Relativity does NOT say:
"perfect GPS clocks should desynchronize"
It says what ideal clocks following specified worldlines accumulate.
What engineers WANT their displayed/system times to do is a completely different question.
A physical theory predicts behaviour.
It does not issue engineering commandments.
And your position has now become genuinely hilarious:
Relativity predicts the amount GPS must compensate.
GPS compensates it.
You then claim GPS refutes relativity because the compensation worked.
You aren't arguing against relativity anymore.
You're using its successful cancellation as evidence that there was
nothing to cancel.
On 10/20/2026 08:29 AM, Python wrote:
Maciej,
the REAL difference in clock indications is 0.
Yes. AFTER compensating the predicted rate difference.
You have now reduced your argument to:
effect predicted
effect measured
effect compensated
compensated result ree 0
therefore effect never existed
And this:
"perfect bridges should collapse"
is precisely the same category error again.
Relativity does NOT say:
"perfect GPS clocks should desynchronize"
It says what ideal clocks following specified worldlines accumulate.
What engineers WANT their displayed/system times to do is a completely
different question.
A physical theory predicts behaviour.
It does not issue engineering commandments.
And your position has now become genuinely hilarious:
Relativity predicts the amount GPS must compensate.
GPS compensates it.
You then claim GPS refutes relativity because the compensation worked.
You aren't arguing against relativity anymore.
You're using its successful cancellation as evidence that there was
nothing to cancel.
Dark Matter / Dark Energy falsified the usual cosmology with the
usual theory.
What are you, chicken?
Lense-Thirring gives frame-dragging,
and there's more than one way to interpret Eotvos.
There are lots of ways to "give the Lorentzians".
Also there are many ways.
Maciej,
SOME clocks may fit any nonsense.
"SOME" clocks. Excellent.
Cesium clocks in NTS-2.
Cesium and rubidium clocks throughout GPS.
Atomic clocks in gravitational redshift experiments.
Hafele-Keating.
Gravity Probe A.
Modern optical-clock height comparisons.
20 days of 50 years.
Definitely - some clocks.
any not-fitting the madness [...] clock simply
doesn't exist for you.
20 days of 50 years.
Definitely - some clocks.
You appear to have missed the rest of the list.
any not-fitting the madness [...] clock simply
doesn't exist for you.
Excellent. Name one.
Give us the clock, its trajectory/gravitational conditions, the
GPS real/calibrated clocks.
your precious unadjusted Cs clocks have no more importance
than unadjusted pendulums.
Maciej,
GPS real/calibrated clocks.
Ah. So THAT is your counterexample.
Let's admire it:
-a-a 1. Relativity predicts a rate difference.
-a-a 2. The unadjusted clock exhibits that rate difference.
-a-a 3. Engineers calibrate the clock to compensate it.
-a-a 4. The calibrated clock no longer exhibits it.
your precious unadjusted Cs clocks have no more importance
than unadjusted pendulums.
Indeed, an unadjusted pendulum would also be scientifically interesting
if relativity predicted before launch that its rate would change by
-a-a +446.5 |u 10^-12
and it subsequently measured
-a-a +442.5 |u 10^-12.
Unfortunately for your analogy, that's the part you keep forgetting.
Calibration can make a clock useful for GPS.
It cannot travel backwards in time and erase what the clock measured
before calibration.
That's the usual fate of measurements made
with erroneous equipment. They are erased.
Maciej,
That's the usual fate of measurements made
with erroneous equipment. They are erased.
Ah, excellent. Science according to Maciej:
-a-a BEFORE launch:
-a-a-a-a-a-a theory predicts +446.5 |u 10^-12
the key, decisive factor determining the clock indications are
user adjustments.
no surprise that his primitive babbling failed.
the key, decisive factor determining the clock indications are
user adjustments.
For fuck's sake, Maciej, YES.
That's precisely why NTS-2 was operated for about 20 days with the relativistic correction SWITCHED OFF.
How many times does this have to be spelled out?
-a-a prediction BEFORE launch:-a-a-a-a-a-a +446.5 |u 10^-12
On 10/22/2026 1:20 AM, Python wrote:
the key, decisive factor determining the clock indications are
user adjustments.
For fuck's sake, Maciej, YES.
And - since the factor
is not present in your moronic
gedankenwelt and with the reality the
idiot had no contact (samely as his
worshipers, BTW) - no surprise that
his primitive babbling failed.
That's precisely why NTS-2 was operated for about 20 days with the
relativistic correction SWITCHED OFF.
How many times does this have to be spelled out?
-a-a-a prediction BEFORE launch:-a-a-a-a-a-a +446.5 |u 10^-12
Sure, of your moronic time dilation. I. e.
of the difference in clock indications.
Really measured value, with correctly calibrated
clocks - 0. Good bye, The Shit.
if your mad religion succeeded in forcing the users to adjust the clocks
its [...] prophecies would be fulfilled.
Common sense has been warning the idiot.
Maciej,
This is becoming surreal.
if your mad religion succeeded in forcing the users to adjust the clocks
its [...] prophecies would be fulfilled.
No.
The prophecy was tested BEFORE the adjustment.
Adjustment is THE KEY, DECISIVE factor here.
Adjustment is THE KEY, DECISIVE factor here.
For the operation of GPS: yes.
For any clock indications in the real world
AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!
Maciej,
For any clock indications in the real world
No. And this is now embarrassingly simple.
In the reality they must be CRAFTED and ADJUSTED.
AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!
Maciej,
In the reality they must be CRAFTED and ADJUSTED.
Congratulations. You have discovered that clocks are manufactured.
Now explain the number.
Two clocks can both be beautifully CRAFTED and ADJUSTED on Earth.
Put one into the NTS-2 orbit and, with the relativistic correction OFF:
-a-a relativity predicts: +446.5 |u 10^-12
-a-a clock measures:-a-a-a-a-a +442.5 |u 10^-12
Your explanation:
If the clocks didn't fit your "perfection differently" - they
wouldn't be sent.
clocks of different construction, that wouldn't fit your prophecies
Maciej,
If the clocks didn't fit your "perfection differently" - they
wouldn't be sent.
Ah, excellent. A new escape hatch: selection bias.
Unfortunately it still doesn't produce the number.
the REAL value of the difference
of the clock indications [...] is 0.
the REAL value of the difference
of the clock indications [...] is 0.
Yes.
AFTER COMPENSATION.
You keep presenting this as a revelation when it is literally the
Adjustment is THE KEY, DECISIVE factor here.
Maciej,
You're looping.
Adjustment is THE KEY, DECISIVE factor here.
For the FINAL clock indication.
And for time, i.e. "what clocks indicate"
if your mad religion succeeded in forcing the users to adjust the clocks
Maciej,
And for time, i.e. "what clocks indicate"
No.
if your mad religion succeeded in forcing the users to adjust the clocks
This is becoming hilarious.
Relativity did not "force" the clock to be adjusted so that its
prediction would come true.
Relativity did not "force" the clock to be adjusted so that its
prediction would come true.
Of course it didn't - the clocks keep measuring
t'=t just like they always did. It was just
trying. Wasted efforts, common sense has been
warning the idiot.
the clocks keep measuring t'=t just like they always did.
Maciej,
the clocks keep measuring t'=t just like they always did.
No.
The NTS-2 clock, with the relativistic correction OFF, measured:
-a-a t' != t
You are now simply taking the result AFTER engineers deliberately
weren't the clocks of Newtonian physicists
deliberately calibrated?
Your shitty revolution has changed NOTHING.
The clocks keep doing what they always did
Maciej,
weren't the clocks of Newtonian physicists
deliberately calibrated?
Of course.
And once again: calibration does not explain the number.
Calibrate two cesium clocks together on Earth.
Put one into the NTS-2 orbit.
Leave the relativistic correction OFF.
What happens?
Relativity, BEFORE launch:
-a-a +446.5 |u 10^-12
Experiment:
-a-a +442.5 |u 10^-12
Even such a nonsensical crap as The Shit of Einstein can
have some correct predictions
But [...] it had to start babbling about
the indications of perfect clocks.
Maciej,
Ah.
So after several days of:
-a-a "t'=t!"
-a-a "just clock error!"
-a-a "adjustment is THE KEY!"
-a-a "your prophecy failed!"
we finally arrive at:
Even such a nonsensical crap as The Shit of Einstein can
have some correct predictions
Thank you.
That was the point.
Relativity predicted the orbital clock-rate shift quantitatively:
It has also predicted, also quantitatively -
difference in clock indication in GPS.
Bullshit, the measured value is 0
including your "clock rates"
Maciej,
It has also predicted, also quantitatively -
difference in clock indication in GPS.
Bullshit, the measured value is 0
No.
the indication of a clock from GPS ground base is -
2026-10-23 15:00:00.00000000.
What is the [measured] indication of a clock in
a GPS satellite?
Maciej,Yes. The real, measured value of the difference
the indication of a clock from GPS ground base is -
2026-10-23 15:00:00.00000000.
What is the [measured] indication of a clock in
a GPS satellite?
After the GPS clock has been deliberately frequency-offset and its
remaining clock offset/drift corrections have been applied?
Approximately:
-a-a 2026-10-23 15:00:00.00000000
The real, measured value of the difference
in clock indications is - 0.
Maciej,Adjustment is THE KEY, DECISIVE
The real, measured value of the difference
in clock indications is - 0.
AFTER COMPENSATION.
Maciej,
You're literally pasting the same paragraph again.
So let's make this painfully short.
YES:
-a-a adjustment is decisive for the FINAL indication.
NO:
-a-a adjustment cannot explain a measurement made
-a-a while that adjustment is SWITCHED OFF.
How is it in galilean physics? Is "time"
the indication of an unadjusted pendulum there?
It can, and very easily. A clock error.
Discarded.
Maciej,
How is it in galilean physics? Is "time"
the indication of an unadjusted pendulum there?
No.
And nobody claims that "time" is whatever an arbitrary unadjusted
physical device happens to indicate.
You're confusing the definition/realization of a time scale with the
physical behaviour of a clock used to realize it.
But your next sentence is much more interesting:
It can, and very easily. A clock error.
Discarded.
Excellent.
So your explanation of NTS-2 is now:
-a-a relativity predicted before launch:
-a-a-a-a-a-a +446.5 |u 10^-12
-a-a clock placed in orbit, correction OFF:
-a-a-a-a-a-a +442.5 |u 10^-12
-a-a Maciej:
-a-a-a-a-a-a "clock error"
What extraordinary luck.
The "clock error" had:
-a-a the predicted sign,
-a-a the predicted magnitude,
-a-a the predicted dependence on orbital conditions,
and differed from the relativistic prediction by about 1%.
Then, when engineers applied the correction calculated for that
supposed "error", GPS worked as intended.
This is becoming a wonderful scientific methodology:
-a-a prediction agrees with measurement -> discard measurement as error
-a-a correction based on prediction works -> discard that too
-a-a corrected residual is zero -> THIS is the only real measurement
With that method, no physical effect could ever be observed.
And "clock error" still isn't a quantitative theory.
Relativity said:
-a-a +446.5 |u 10^-12
The real, measured value is - 0.
Maciej,
The real, measured value is - 0.
Yes.
After compensation.
Maciej,
You have now pasted essentially the same paragraph yet again, after
every point in it has already been answered repeatedly.
I did.
Maciej,
I did.
Indeed.
You explicitly acknowledge that you are repeating the same paragraph
after the answer has already been given repeatedly.
Maciej,
Yes.
That is now the fourth or fifth time you've pasted essentially the same paragraph.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:41:45 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,687 |