• Re: Words have power

    From Kevvy Ruzaev@vvavv@vrzrz.ru to sci.physics.relativity,sci.math on Sun Oct 18 07:51:20 2026
    From Newsgroup: sci.math

    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
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 10:16:32 2026
    From Newsgroup: sci.math

    On 10/18/2026 9:51 AM, Kevvy Ruzaev wrote:
    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

    Sounds like your physics... and any other science...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 11:00:11 2026
    From Newsgroup: sci.math

    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 "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.

    No. The adjective is:

    object-oriented

    not:

    objective.

    And the irony gets better.

    Alan Kay, who actually coined "object-oriented", later said it was a
    bad choice of term because it made people focus on the OBJECTS rather
    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.

    So:

    "objective software" != object-oriented software

    and:

    "science contains objects"
    !=
    "science is object-oriented software".

    By your reasoning, physics is OOP because it contains objects.

    Presumably zoology is OOP because it contains animals, and a kitchen is
    OOP because it contains forks.

    You've managed to misunderstand "object-oriented" in almost exactly the
    way the man who coined the term spent years warning people not to.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 13:54:50 2026
    From Newsgroup: sci.math

    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?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 11:57:30 2026
    From Newsgroup: sci.math

    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 object-oriented

    not:

    -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.

    It does not make "objective software" a synonym for "object-oriented
    software", any more than:

    Java programmer = coffee programmer
    Python code = snake code
    C shell = seashell

    Objective-C was specifically named as an object-oriented extension to C.

    And names chosen for products, languages, trademarks or marketing are
    not definitions in computer science.

    Microsoft Windows does not establish that "windows software" means
    "Microsoft software".

    So your argument has now reached:

    a programming language was named "Objective-C"
    therefore "objective software" means "object-oriented software".

    That's not CS terminology.

    That's reverse-engineering a definition from a brand name.

    At this rate, Burger King will soon become a constitutional monarchy.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to sci.physics.relativity,sci.math on Sun Oct 18 04:58:23 2026
    From Newsgroup: sci.math

    On 10/18/2026 04:54 AM, Maciej Wo+|niak wrote:
    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?


    The "structured" usually enough makes for
    overall an account equi-interpretable with "model theory",
    and the large model theory with a universe,
    and infinity & continuity in diversity & variety.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 14:10:44 2026
    From Newsgroup: sci.math

    On 10/18/2026 1:57 PM, Python wrote:
    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.

    And it is obviously wrong name, right, poor piece
    of shit? Should be "object oriented c" instead?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 12:13:43 2026
    From Newsgroup: sci.math

    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.

    The rest contained the answer.

    Excellent debating technique, though: remove the explanation, then
    triumphantly ask for the explanation.

    Object-oriented discussion, presumably, or objective discussion :-)


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 14:20:25 2026
    From Newsgroup: sci.math

    On 10/18/2026 2:13 PM, Python wrote:
    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.

    Well, why to care about more mad
    mumble of a brainwashed idiot
    worshiping desynchronizing clocks.

    And, while "objective" is commonly used
    as asubstitute of object-oriented (vide
    our objective c) I won't insist on that.
    If you prefer your moronic physics
    to be a piece of object-oriented software
    - let it be.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 12:23:22 2026
    From Newsgroup: sci.math

    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:

    "Physics is a piece of objective software
    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 truly impressive.

    You don't merely move the goalposts.

    You leave them on my lawn and accuse me of having built them.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 14:28:35 2026
    From Newsgroup: sci.math

    On 10/18/2026 2:23 PM, Python wrote:
    Maciej,

    If you prefer your moronic physics
    to be a piece of object-oriented software
    - let it be.

    :-)))

    MY physics?

    Plural your.


    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.

    Being an idiot you can't read, no surprise.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 12:36:02 2026
    From Newsgroup: sci.math

    This is getting into small-child-with-jam-all-over-his-face territory:

    "I didn't eat the jam."

    Maciej, YOU wrote:

    "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.

    The empty jam jar is on the table.

    The spoon is in your hand.

    And there's jam all over your face.

    But apparently we simply can't read.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 14:39:36 2026
    From Newsgroup: sci.math

    On 10/18/2026 2:36 PM, Python wrote:
    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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Sun Oct 18 12:42:19 2026
    From Newsgroup: sci.math

    I don't identify with brainwashing religions,
    it's yours.

    Nobody asked what you identify with.

    YOU wrote:

    "Physics is a piece of objective software"

    YOU explained:

    "objective" = "object-oriented"

    And now the resulting proposition belongs to us because you don't
    "identify" with physics.

    The jam metaphor was perhaps too generous.

    The child at least remembers eating it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Sun Oct 18 14:44:45 2026
    From Newsgroup: sci.math

    On 10/18/2026 2:42 PM, Python wrote:
    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.

    Your moronic physics IS a piece of object-oriented
    software - whether you like it or not, poor
    piece of shit.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dawn Rujenkov@jrdj@een.ru to sci.physics.relativity,sci.math on Sun Oct 18 16:55:33 2026
    From Newsgroup: sci.math

    Python wrote:

    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.

    yet anothere imbecile former it-supporter, the OOP is not about messages,
    but messages are about clustering supercomputers. The OOP is about
    creating objects that embeds both methods and private data; you access the data through the methods, not directly, unless they are public
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 10:43:51 2026
    From Newsgroup: sci.math

    Maciej,

    Your moronic physics IS a piece of object-oriented
    software

    There we are.

    So it IS your thesis after all.

    The jam has made it back onto the bread.

    That was quite a journey.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 13:05:29 2026
    From Newsgroup: sci.math

    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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 11:15:30 2026
    From Newsgroup: sci.math

    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:

    "Physics is a piece of object-oriented software
    designed for a monkey's brain."

    What exactly makes physics "object-oriented software"?

    Classes?
    Objects?
    Encapsulation?
    Inheritance?
    Polymorphism?
    Message passing?
    Late binding?

    You have identified none of them.

    Apparently your entire argument is:

    physics talks about objects
    object-oriented programming talks about objects
    therefore physics is object-oriented software.

    By the same reasoning, a furniture catalogue is object-oriented
    software.

    Calling this a "fact" doesn't supply the missing argument.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 13:21:33 2026
    From Newsgroup: sci.math

    On 10/19/2026 1:15 PM, Python wrote:
    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.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 11:42:12 2026
    From Newsgroup: sci.math

    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?

    You started with an extravagant metaphor and, when asked what makes it "object-oriented", supplied a property that has absolutely nothing to
    do with object-oriented programming.

    At this point "object-oriented software" just means:

    something Maciej has decided to call object-oriented software.

    A remarkably flexible branch of computer science.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 13:53:31 2026
    From Newsgroup: sci.math

    On 10/19/2026 1:42 PM, Python wrote:
    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.

    Sorry, poor piece of shit, that's exactly what is
    making it software. And "object oriented" - is
    because of its structure.


    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, poor piece of shit. There are
    many and deep differences between a
    human and a monkey, and analyzing
    the hardware is not explaining them
    at all.
    Why doubts? Can't AI deal with all
    of them? If it can, you should know:
    it's software.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 12:07:13 2026
    From Newsgroup: sci.math

    Maciej,

    Exactly

    Excellent. So now arithmetic, Polish and chess are literally software.

    Your definition is apparently:

    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:

    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.

    You have quietly replaced:

    software can process X

    with:

    X is software.

    That's not computer science either.

    It's the same category error, now automated.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 14:19:14 2026
    From Newsgroup: sci.math

    On 10/19/2026 2:07 PM, Python wrote:
    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

    Python, you shouldn't conclude, you're too
    stupid for that, and "software" has no
    definition.



    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.

    And what they ARE according to poor
    piece of shit Python? What is arithmetic?
    What is Polish [language]?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 12:31:27 2026
    From Newsgroup: sci.math

    What is arithmetic?
    What is Polish [language]?

    I don't think you have demonstrated either the technical level or the intellectual honesty required for a serious discussion of questions
    like these.

    There ARE serious works exploring ideas surprisingly close to your
    "software" metaphor. I have already pointed you to some of them,
    particularly Jean-Louis Krivine's work on realizability and the
    computational content of mathematics.

    But serious work requires definitions, formal structures, theorems and arguments. "It's software because it gives the monkey new abilities"
    isn't quite there yet.

    And given that, in your universe, essentially everyone who might teach
    you something is an idiot, a moron, brainwashed or a religious fanatic,
    I don't have great hopes that you'll actually read any of it.

    There is, however, one rather delightful consequence of your metaphor.

    If Relativity is merely "software uploaded into monkey brains", then it
    is software which, once uploaded into the monkey brains that designed
    GPS, enabled those monkeys to calculate the relativistic clock-rate
    offsets, build the system accordingly, put the satellites into orbit...

    ..and make the damn thing work.

    For useless brainwashing software, that's a rather impressive demo.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 14:44:06 2026
    From Newsgroup: sci.math

    On 10/19/2026 2:31 PM, Python wrote:
    What is arithmetic?
    What is Polish [language]?

    I don't think you have demonstrated either the technical level or the intellectual honesty required for a serious discussion of questions
    like these.

    So, run, poor piece of shit.
    Nothing else expected.

    The mumble of the idiot you're worshiping
    remains not even consistent, his assertion
    that perfect clocks are desynchronizing
    clocks remains as baseless as it is idiotic
    and your moronic physics remains to be a
    piece of object oriented software.


    If Relativity is merely "software uploaded into monkey brains", then it
    is software which, once uploaded into the monkey brains that designed
    GPS, enabled those monkeys to calculate the relativistic clock-rate
    offsets, build the system accordingly, put the satellites into orbit...

    Nope, it's just a software insisting that the clocks
    GPS professionals made are worthless because
    perfect clocks are desynchronizing clocks.
    As said many times - the model/software applied
    really for GPS has little in common with your
    idiocies.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 12:59:24 2026
    From Newsgroup: sci.math

    the model/software applied really for GPS has little in common with your idiocies.

    We've already tested that claim against history.

    Before NTS-2 was launched, relativity predicted its orbital clock's
    fractional frequency shift:

    +446.5 |u 10^-12

    They deliberately left the correction OFF for about 20 days.

    Measured:

    +442.5 |u 10^-12

    Then they switched the correction ON.

    That's not philosophy about "perfect clocks". That's a quantitative
    prediction followed by a measurement.

    Your competing model predicted what number?

    So far the answer has been zero numbers, plus several hundred
    occurrences of "idiot", "moron", "religion" and "piece of shit".

    As software benchmarks go, Relativity is doing rather better.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 15:16:32 2026
    From Newsgroup: sci.math

    On 10/19/2026 2:59 PM, Python wrote:
    the model/software applied really for GPS has little in common with your
    idiocies.

    We've already tested that claim against history.

    Before NTS-2 was launched, relativity predicted its orbital clock's fractional frequency shift:


    Poor fanatic piece of shit screaming "NOOOOO!!!!"
    won't change anything.

    GPS model is assuming that clocks are to indicate
    t'=t and if they don't want to - they are to be
    corrected. GPS model is assuming galilean time.

    Of course. Common sense has been warning the
    idiot and the idiots from your bunch of idiots.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 13:38:54 2026
    From Newsgroup: sci.math

    GPS model is assuming that clocks are to indicate
    t'=t and if they don't want to - they are to be
    corrected. GPS model is assuming galilean time.

    And once again you carefully avoid the only interesting question:

    corrected BY HOW MUCH?

    "Make the clocks agree" is an engineering objective, not a physical
    model.

    Galilean time predicts no relativistic rate difference to correct.

    Relativity predicted, before NTS-2 flew:

    +446.5 |u 10^-12

    With the relativistic correction deliberately switched OFF, NTS-2
    measured:

    +442.5 |u 10^-12

    Then the correction was switched ON.

    Your "common sense Galilean model" contributes exactly this:

    "Oh, if the clocks disagree, correct them."

    Wonderful.

    But somebody still has to tell the engineer how far to turn the knob.

    Relativity supplied the number BEFORE the measurement.

    Your "Galilean model" supplied it AFTER the measurement by calling the
    measured relativistic shift a "clock error".

    That's not a competing prediction.

    That's subtraction followed by amnesia.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 15:49:05 2026
    From Newsgroup: sci.math

    On 10/19/2026 3:38 PM, Python wrote:
    GPS model is assuming that clocks are to indicate
    t'=t and if they don't want to - they are to be
    corrected. GPS model is assuming galilean time.

    And once again you carefully avoid the only interesting question:

    -a-a corrected BY HOW MUCH?

    For sure not by 0 predicted by your
    moronic Shit. Your mad assertion
    that it would be perfect without
    any corrections didn't convince
    anyone - common sense has been
    warning the idiot and the idiots
    from the idiot's bunch of idiots.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 13:58:39 2026
    From Newsgroup: sci.math

    Maciej,

    For sure not by 0 predicted by your
    moronic Shit.

    Relativity predicted:

    +446.5 |u 10^-12

    NTS-2 measured, correction OFF:

    +442.5 |u 10^-12

    And you keep saying relativity predicted:

    0

    This is becoming genuinely impressive.

    You have the prediction.
    You have the measurement.
    You have the agreement to about 1%.

    And your response is still:

    "NO, IT PREDICTED ZERO."

    At this point, even your "software" metaphor is useful.

    Your parser appears unable to read numbers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 16:02:56 2026
    From Newsgroup: sci.math

    On 10/19/2026 3:58 PM, Python wrote:
    Maciej,

    For sure not by 0 predicted by your
    moronic Shit.

    Relativity predicted:

    -a-a +446.5 |u 10^-12

    Sure, of your time dilation idiocy.
    Measured value - 0, falsified.




    NTS-2 measured, correction OFF:

    -a-a +442.5 |u 10^-12

    Sure, a clock error that had to be corrected.
    The Shit's prediction - no such thing (i.e. 0),
    falsified.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 14:06:23 2026
    From Newsgroup: sci.math

    Maciej,

    This is just relabelling the SAME observable.

    Before launch:

    Relativity calculates fractional frequency shift:
    +446.5 |u 10^-12
    You call it "time dilation".

    In orbit, correction OFF:

    NTS-2 measures fractional frequency shift:
    +442.5 |u 10^-12
    You call it "clock error".

    Same physical quantity.
    Same sign.
    Agreement to about 1%.

    Then you declare:

    predicted time dilation = 446.5
    measured time dilation = 0

    predicted clock error = 0
    measured clock error = 442.5

    Voil|a! Two falsifications manufactured entirely by changing the label
    between prediction and measurement.

    That's quite a trick.

    Unfortunately, instruments measure frequency shifts, not Maciej's
    preferred nouns.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 16:26:43 2026
    From Newsgroup: sci.math

    On 10/19/2026 4:06 PM, Python wrote:
    Maciej,

    This is just relabelling the SAME observable.

    Python,

    Even such a hopeless piece of lying
    shit as you are can't lie non stop,
    so sometimes you admit: no, "time
    dilation" and "clock error" are not
    the same.

    Of course, in a "logic" of a brainwashed
    religious maniac a sheep can "confirm" a
    theory of sharks eating grass, why not.


    Voil|a! Two falsifications manufactured entirely by changing the label between prediction and measurement.

    Words have power, poor piece of shit.
    Relabelling a circle to "straight line"
    you're getting your non-euclidean
    nonsenses, relabelling (you, not me)
    a clock error to "time dilation" you
    get some "confirmation" of your moronic
    Shit.
    Unfortunately, the words still don't
    have enough power to save The Shit -
    asserting that your junk clocks are
    perfect was intended to prevent
    correcting them; it didn't succeed.









    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 14:28:03 2026
    From Newsgroup: sci.math

    Maciej,

    no, "time dilation" and "clock error" are not
    the same.

    Correct. They are not the same CONCEPT.

    But here you are using two different concepts to relabel the SAME
    MEASURED FREQUENCY SHIFT.

    That is the trick.

    Relativity predicted that the orbital clock, under those conditions,
    would differ in rate by:

    +446.5 |u 10^-12

    They flew the clock with the correction OFF and measured:

    +442.5 |u 10^-12

    You cannot make that agreement disappear by pointing at the measured
    442.5 and shouting "CLOCK ERROR!"

    And this is even funnier:

    asserting that your junk clocks are
    perfect was intended to prevent correcting them

    No physical theory "intends" engineers to do anything.

    Relativity predicts what the clocks will do.

    Engineering decides what we WANT them to do and compensates accordingly.

    Newton predicts that an unsupported bridge will fall. Newtonian
    mechanics does not therefore "intend to prevent" engineers from adding supports.

    And your circle story is the same confusion all over again: changing
    words does not create non-Euclidean geometry; changing the metric does.

    So yes, words have power.

    Apparently enough power for you to turn

    prediction: +446.5 |u 10^-12
    measurement: +442.5 |u 10^-12

    into a falsification simply by calling the second number something
    different.

    Sadly, numbers have power too.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 16:39:39 2026
    From Newsgroup: sci.math

    On 10/19/2026 4:28 PM, Python wrote:
    Maciej,

    no, "time dilation" and "clock error" are not
    the same.

    Correct. They are not the same CONCEPT.

    But here you are using two different concepts to relabel the SAME
    MEASURED FREQUENCY SHIFT.

    You could as well mumble that saying
    "a sheep" i just relabel the concept of
    an animal eating grass, which is obviously
    a shark.

    asserting that your junk clocks are
    perfect was intended to prevent correcting them

    No physical theory "intends" engineers to do anything.

    Wrong, poor piece of shit. You understand nothing
    of that. Your moronic physics is a piece of
    software, after all...


    Relativity predicts what the clocks will do.

    Yeah. What perfect clocks should do; if the
    real ones don't want to they're not perfect i.e.
    wrong, and we have to make them better.
    Sane (partially) physics worked the same way, and
    so did Euclidean geometry. That's why your bunch
    of idiots could never falsify it.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 15:37:00 2026
    From Newsgroup: sci.math

    Maciej,

    You could as well mumble that saying
    "a sheep" i just relabel the concept of
    an animal eating grass, which is obviously
    a shark.

    Except we didn't measure "sheep" or "shark".

    We measured a NUMBER.

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    Your entire rebuttal consists in sticking different animal labels on
    the two numbers and hoping nobody notices they are almost identical.

    Yeah. What perfect clocks should do; if the
    real ones don't want to they're not perfect i.e.
    wrong, and we have to make them better.

    This is wonderful.

    An ideal clock in relativity is one whose reading follows proper time
    along its worldline.

    So when a real atomic clock exhibits the rate shift predicted for that worldline, your conclusion is:

    THE CLOCK IS WRONG!

    Then engineers deliberately alter its rate so that it realizes GPS
    system time, and your conclusion is:

    AHA! RELATIVITY WAS WRONG!

    Let's translate this methodology to thermometers:

    Theory: at this altitude water boils at 95 C.
    Thermometer: 95 C.
    Maciej: defective thermometer!
    Engineer recalibrates display to read 100.
    Maciej: theory falsified!

    That's why your bunch of idiots could never falsify it.

    NTS-2 was deliberately flown for about 20 days with the relativistic
    frequency correction switched OFF.

    That was an opportunity for the prediction to fail.

    It predicted 446.5.
    They measured 442.5.

    Your theory predicted neither number.

    It merely arrived afterwards, pointed at 442.5 and screamed:

    CLOCK ERROR!

    The sheep and sharks can relax.

    The numbers have already eaten your argument.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 18:37:31 2026
    From Newsgroup: sci.math

    On 10/19/2026 5:37 PM, Python wrote:
    Maciej,

    You could as well mumble that saying
    "a sheep" i just relabel the concept of
    an animal eating grass, which is obviously
    a shark.

    Except we didn't measure "sheep" or "shark".

    Why not? You can measure how much grass
    your "shark" will eat. You may then
    wave arms and scream "Look!!! I
    predicted 2kg of grass eaten, and it is!!!
    relabelling a shark to "sheep" doesn't
    disturb my ingenious prediction!!!! My
    ingenious theory that shark eat grass is
    thus confirmed!!!!!"




    We measured a NUMBER.

    -a-a predicted: +446.5 |u 10^-12
    -a-a measured:-a +442.5 |u 10^-1

    A lie, of course. Measured - 0. That's the REAL
    difference in clock indications (i.e. real time
    dilation).


    Yeah. What perfect clocks should do; if the
    real ones don't want to they're not perfect i.e.
    wrong, and we have to make them better.

    This is wonderful.

    An ideal clock in relativity is one whose reading follows proper time
    along its worldline.

    Sure. So if a real clock doesn't want to
    measure it correctly (i.e. as the idiot
    predicted) - it is not a perfect one.
    And a relativistic idiot screams
    "CALIBRATED!!! DELIBERATELY!!!!
    DOESN'T COUNT!!!!!!!" As if a measurement
    device was ever made or calibrated
    "not deliberately".



    -a-a THE CLOCK IS WRONG!

    Python, poor piece of shit, if it
    wasn't it wouldn't be corrected.

    What is the whole concept of a clock error?
    May occur under any circumstances, under
    a billion of possible reasons (including
    unknown reasons), just one thing is certain
    about it: we will correct it if we can.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 16:42:18 2026
    From Newsgroup: sci.math

    A lie, of course. Measured - 0.

    No.

    This is now almost performance art.

    NTS-2, correction OFF:

    predicted fractional frequency shift: +446.5 |u 10^-12
    measured fractional frequency shift: +442.5 |u 10^-12

    You take the measured shift and call it "clock error".

    Then you define "REAL time dilation" as the difference remaining AFTER engineers compensate that shift.

    Then, triumphantly:

    measured time dilation = 0!

    Of course it is zero after you've subtracted it.

    if it wasn't it wouldn't be corrected.

    This may be your masterpiece.

    Noise-cancelling headphones compensate external noise.
    Therefore the noise was an error in the microphone.

    Air conditioning compensates solar heating.
    Therefore sunshine is an error in the thermometer.

    GPS compensates a predicted physical rate difference because engineers
    want different clocks to realize a common system time.

    "Compensated" does not mean "measurement-device malfunction".

    And:

    What is the whole concept of a clock error?

    Indeed.

    You desperately NEED the 442.5 |u 10^-12 to be a mysterious "clock
    error", because otherwise something rather embarrassing happened:

    Relativity predicted 446.5 |u 10^-12 BEFORE launch.

    The clock produced 442.5 |u 10^-12 with the correction OFF.

    And your alternative explanation is:

    could be a billion possible reasons
    including unknown reasons

    Magnificent.

    Relativity: 446.5.

    Experiment: 442.5.

    Maciej: UNKNOWN REASONS!!!

    I think we have finally established which of these is the predictive
    physical theory.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 18:51:31 2026
    From Newsgroup: sci.math

    On 10/19/2026 6:42 PM, Python wrote:
    A lie, of course. Measured - 0.

    No.
    A lie. Again.
    So, answer, poor piece of shit: the indication
    of one (ground) clock is 2026-10-19 22:00:00.000000000.
    What is the indication of the satellite clock?



    What is the whole concept of a clock error?

    Indeed.

    You desperately NEED the 442.5 |u 10^-12 to be a mysterious "clock
    error", because otherwise something rather embarrassing happened:

    No, trash. I don't need anything. It is
    CORRECTED. Fits the "error" concept, doesn't
    fit your "dilation" idiocy. Game over.




    The clock produced 442.5 |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.

    2 kg of eaten grass!! By some animal!!!! My theory of
    sharks eating grass is magnificiently confirmed!!!!!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 16:53:03 2026
    From Newsgroup: sci.math

    Maciej,

    the indication of one (ground) clock is
    2026-10-19 22:00:00.000000000.
    What is the indication of the satellite clock?

    In operational GPS, after the system has deliberately compensated and
    corrected the clocks to realize GPS system time?

    Approximately the corresponding GPS system time, within the system's
    error tolerances.

    And you apparently think this proves something.

    The experiment we're discussing was precisely to turn the frequency
    correction OFF and see what happened.

    What happened?

    prediction before launch: +446.5 |u 10^-12
    measurement in orbit: +442.5 |u 10^-12

    Your argument is literally:

    1. Observe the predicted rate difference.
    2. Compensate it.
    3. Observe that the compensated difference is approximately zero.
    4. Announce that step 1 measured zero.

    It is CORRECTED. Fits the "error" concept, doesn't
    fit your "dilation" idiocy. Game over.

    A compensation is not evidence that its cause was an instrument error.

    If engineers pre-adjust an oscillator because physics predicts how its
    rate will change in its future environment, the adjustment does not
    magically transform the physical effect into a defective oscillator.

    And your shark is becoming increasingly unfortunate.

    Relativity didn't predict merely:

    SOME ANIMAL WILL EAT 2 kg OF GRASS.

    It specified the physical circumstances and quantitatively predicted
    the clock's fractional rate shift BEFORE the satellite flew.

    Then they flew it with the correction OFF and measured almost exactly
    that shift.

    Your shark theory, meanwhile, is:

    I don't know why the grass disappeared.
    There are a billion possible reasons.
    Possibly unknown ones.
    But it definitely wasn't the sheep.

    Game over indeed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 19:02:42 2026
    From Newsgroup: sci.math

    On 10/19/2026 6:53 PM, Python wrote:
    Maciej,

    the indication of one (ground) clock is
    2026-10-19 22:00:00.000000000.
    What is the indication of the satellite clock?

    In operational GPS, after the system has deliberately compensated and

    AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME
    DILATION - IS 0.
    Common sense has been warning the idiot.



    What happened?

    -a-a prediction before launch:-a +446.5 |u 10^-12


    2 kg of eaten grass!! By some animal!!!! My theory of
    sharks eating grass is magnificiently confirmed!!!!!


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 17:03:51 2026
    From Newsgroup: sci.math

    Maciej,

    AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME
    DILATION - IS 0.

    AFTER compensation.

    You keep shouting the word that destroys your own argument.

    The question is why compensation was required in the first place.

    With correction OFF:

    predicted rate difference: +446.5 |u 10^-12
    measured rate difference: +442.5 |u 10^-12

    With correction ON:

    residual difference: approximately 0

    And your reasoning is:

    after cancelling X, I measure approximately zero
    therefore X never existed.

    Brilliant.

    2 kg of eaten grass!! By some animal!!!!

    Your shark has a worse problem now.

    We predicted, before opening the enclosure:

    this particular sheep will eat about 2.00 kg

    We opened it and measured:

    this particular sheep ate about 1.98 kg

    You then fed the sheep enough extra food to compensate, observed that
    the remaining ration was correct, and announced:

    LOOK! ZERO MISSING GRASS!
    SHARK THEORY FALSIFIED!

    At some point even the sheep is going to understand the experiment.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 19:11:48 2026
    From Newsgroup: sci.math

    On 10/19/2026 7:03 PM, Python wrote:
    Maciej,

    AND MEASURED DIFFERENCE IN INDICATIONS, I.E. TIME
    DILATION - IS 0.

    AFTER compensation.

    "CALIBRATED CLOCKS!!! DELIBERATELY!!!
    DOESN'T COUNT!!! CALIBRATED MEASUREMENT
    DEVICES ONLY COUNT WHEN THE RESULTS FIT
    OUR BELOVED SHIT OF OUR BELOVED IDIOT!!!!"





    You keep shouting the word that destroys your own argument.

    The question is why compensation was required in the first place.

    With correction OFF:

    -a-a predicted rate difference: +446.5 |u 10^-12


    2 kg of eaten grass!! By some animal!!!! My theory of
    sharks eating grass is magnificiently confirmed!!!!!


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 17:23:10 2026
    From Newsgroup: sci.math

    Maciej,

    "CALIBRATED CLOCKS!!! DELIBERATELY!!!
    DOESN'T COUNT!!!"

    You're still confusing CALIBRATION with COMPENSATION.

    The NTS-2 clock was not "calibrated" to accidentally produce
    +442.5 |u 10^-12.

    Quite the opposite: the relativistic frequency correction was
    deliberately left OFF for about 20 days so they could measure the
    uncompensated orbital rate.

    Relativity had already predicted:

    +446.5 |u 10^-12

    They measured:

    +442.5 |u 10^-12

    THEN the synthesizer correction was switched on.

    Your version of experimental method is extraordinary:

    prediction made before experiment
    |
    v
    correction OFF
    |
    v
    predicted effect observed
    |
    v
    correction switched ON
    |
    v
    effect compensated
    |
    v
    Maciej: "SEE? ZERO!"

    And your shark keeps screaming "2 kg of grass!" while carefully avoiding
    the awkward detail that the theory specified the animal, the amount and
    the circumstances BEFORE anybody weighed the grass.

    Your competing theory remains:

    something ate it.

    Possibly for one of a billion reasons.

    Science is usually a little more demanding.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Mon Oct 19 19:37:22 2026
    From Newsgroup: sci.math

    On 10/19/2026 7:23 PM, Python wrote:
    Maciej,

    "CALIBRATED CLOCKS!!! DELIBERATELY!!!
    DOESN'T COUNT!!!"

    You're still confusing CALIBRATION with COMPENSATION.


    Sure. Calibration is - when a piece of
    relativistic shit feels comfortable with
    calibration.
    Compensation, on the other hand is - when
    a piece of relativistic shit feels comfortable
    with compensation.
    Easy, isn't it?

    Anyway, of course, deliberate modifying
    measurement devices is only allowed
    when the result will fit One And Only
    True Shit of Einstein.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Salvado Bazarov@avvazv@vzbb.ru to sci.physics.relativity,sci.math on Mon Oct 19 19:07:42 2026
    From Newsgroup: sci.math

    Maciej Wo+|niak wrote:

    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.

    you still are proving you are an idiot, in curved spacetime the curved
    lines are 100% what you call straight line, which is, the shortest path
    from A to B, that's your straight line, idiot

    if you diverge from that curved spacetime line, the distance becomes
    longer
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.physics.relativity,sci.math on Mon Oct 19 14:39:24 2026
    From Newsgroup: sci.math

    On 10/19/2026 5:07 AM, Python wrote:
    [...]

    subject does not know English, english.dll and all of its data missing.

    Loading... Ahhh, subject is being trained on english... Computing... Weighing...

    Not all that bad result. It does not sound like a total moron...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Mon Oct 19 21:55:05 2026
    From Newsgroup: sci.math

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to sci.physics.relativity,sci.math on Mon Oct 19 15:10:03 2026
    From Newsgroup: sci.math

    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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to sci.physics.relativity,sci.math on Mon Oct 19 15:27:36 2026
    From Newsgroup: sci.math

    On 10/19/2026 03:10 PM, Ross Finlayson wrote:
    On 10/19/2026 02:55 PM, Python wrote:
    Maciej,

    deliberate modifying measurement devices is only allowed
    when the result will fit One And Only True Shit of Einstein.

    You have managed to reverse the chronology again.

    The correction was OFF.

    OFF, Maciej.

    That's precisely why NTS-2 was a test.

    Relativity predicts: +446.5 |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.



    My video essay "Reading Foundations: iota-values and theatheory,
    Poincare stringlets", deftly introduces the involved mathematical
    accounts since antiquity and also about Calabi-Yau and Kaluza-Klein
    and for Yukawa potentials, which go both ways, and not so much about Nambu-Goldstone, where though that Clebsch-Gorden (sp.) is more of
    a reductionist side-show.

    The A.I. chat-bot the other day described quite a bit involved in
    making it so that "Usenet posts" are "publishings" quite like any
    other, and as well for "YouTube videos", vis-a-vis, "AMS TeX"
    and "Phys. Rev.", and the JSL and BSL.


    Read at least once by the giant bot in the cloud, ....


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 07:23:41 2026
    From Newsgroup: sci.math

    On 10/19/2026 11:55 PM, Python wrote:
    Maciej,

    deliberate modifying measurement devices is only allowed
    when the result will fit One And Only True Shit of Einstein.

    You have managed to reverse the chronology again.

    The correction was OFF.

    OFF, Maciej.
    That's precisely why NTS-2 was a test.

    -a-a Relativity predicts:-a-a-a-a +446.5 |u 10^-12

    Of your time dilation idiocy. Not of a clock error
    which should be corrected.




    -a-a "They modified the device to obtain the predicted result!"

    No, poor piece of shit. They modified (calibrated)
    the device to obtain THE CORRECT result. That's
    what "calibration" is. And THE CORRECT result
    doesn't fit your moronic predictions at
    all.
    You may wave arms and scream "CALIBRATED!!!
    DOESN'T COUNT!!!!". You're just a brainwashed
    idiot waving his arms.



    when the predicted result was obtained while the modification you're complaining about was explicitly disabled.

    It's you complaining about modification, not
    me, poor piece of shit.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 08:00:43 2026
    From Newsgroup: sci.math

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 10:26:55 2026
    From Newsgroup: sci.math

    On 10/20/2026 10:00 AM, Python wrote:
    Maciej,

    They modified (calibrated)
    the device to obtain THE CORRECT result.

    You keep running away from the chronology:

    I'm not, it's just completely insignificant.



    Calling the first number "time dilation" and the second "clock error"
    doesn't make two observables.

    Even such a hopeless piece of lying shit
    can't lie non stop, so sometimes you admit:
    oh yes, "clock error" and "time dilation"
    ARE two different observables.




    It's the same measured frequency shift.

    2 kg of grass eaten! My theory of
    sharks eating grass is magnificiently
    confirmed!!!!!

    The engineer still needs to know BY HOW MUCH to compensate.

    And your mad religion is asserting that
    it should be 0, no clock error, perfect,
    correct, proper.

    Relativity gave the number before launch.

    A lie. Your mad religion is asserting that
    it should be 0, no clock error, perfect,
    correct, proper.



    Your "common sense" renamed it after measurement.

    That's not physics.

    Surely that's not. Because I'm not interested
    in mad, brainwashing religions babbling about
    some alleged "laws of nature".





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 08:34:13 2026
    From Newsgroup: sci.math

    Maciej,

    the chronology:

    it's just completely insignificant.

    Of course. Prediction BEFORE measurement is "completely insignificant"
    when your entire alternative consists of explaining the result AFTER measurement.

    "clock error" and "time dilation"
    ARE two different observables.

    No. Different concepts. Same observable here: the fractional frequency
    shift.

    You can call

    predicted +446.5 |u 10^-12 = "shark"
    measured +442.5 |u 10^-12 = "sheep"

    all day long.

    The numbers won't care.

    your mad religion is asserting that
    it should be 0

    This is simply false.

    It asserted +446.5 |u 10^-12.
    Before launch.
    Correction OFF.
    Measured +442.5 |u 10^-12.

    Your answer is now literally:

    chronology doesn't matter
    names matter
    predictions don't matter
    laws of nature don't interest me

    Fine.

    But that's a remarkably elaborate way of announcing that you've left
    the discussion of physics.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 10:54:28 2026
    From Newsgroup: sci.math

    On 10/20/2026 10:34 AM, Python wrote:
    Maciej,

    the chronology:

    it's just completely insignificant.

    Of course. Prediction BEFORE measurement is "completely insignificant"
    when your entire alternative consists of explaining the result AFTER measurement.

    "clock error" and "time dilation"
    ARE two different observables.

    No.

    Yes.
    Even such a hopeless piece of lying shit
    can't lie non stop, so sometimes you admit:
    oh yes, "clock error" and "time dilation"
    ARE two different observables.


    all day long.

    The numbers won't care.

    You say: "a shark will eat 2kg of grass."
    A sheep eats 2kg of grass. The number matches,
    so your claim is confirmed - right, poor piece
    of shit? Or maybe wrong?


    your mad religion is asserting that
    it should be 0

    This is simply false.

    No., sorry, poor piece of shit. Your mad
    religion is asserting unabigously: no clock
    error, perfect, correct, proper - without
    any correction.


    It asserted +446.5 |u 10^-12.
    Before launch.
    Correction OFF.

    And according to your mad assertions it
    would be perfect, correct, proper if they
    stayed off. Unfortunately - sane people pissed
    at your mad, baseless assertions. Common sense
    has been warning the idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 09:25:51 2026
    From Newsgroup: sci.math

    Maciej,

    You say: "a shark will eat 2kg of grass."
    A sheep eats 2kg of grass.

    No. Your analogy fails exactly where you need it.

    Relativity predicted a specific observable: the orbital clock's
    fractional frequency shift.

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    There is no shark and sheep. There is one frequency shift.

    Your entire trick is to rename the predicted value "time dilation" and
    the measured value "clock error", then pretend the labels are
    observables.

    it would be perfect, correct, proper if they stayed off.

    YES.

    Perfect as a clock measuring proper time.

    UNSUITABLE for the engineering requirement of realizing GPS system
    time.

    A perfect thermometer can be unsuitable as a thermostat.

    You have spent dozens of posts confusing

    physically correct behaviour

    with

    behaviour engineers want for a particular purpose.

    And apparently "common sense" has been warning you so loudly that you
    can no longer hear the distinction.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 12:10:33 2026
    From Newsgroup: sci.math

    On 10/20/2026 11:25 AM, Python wrote:
    Maciej,

    You say: "a shark will eat 2kg of grass."
    A sheep eats 2kg of grass.

    No. Your analogy fails exactly where you need it.

    Relativity predicted a specific observable: the orbital clock's
    fractional frequency shift.

    A lie. It predicts your time dilation nonsense.
    Not just a "frequency shift", not just
    "2kg of grass eaten" - full "frequency shift being
    time dilation", full "2 kg of grass eaten by a
    shark".


    it would be perfect, correct, proper if they stayed off.

    YES.

    Unfortunately - it's just some opinion of a
    mad, brainwashing religion. Nothing more.
    And even more unfortunately - sane people have
    a different opinion. In their opinion when
    clocks desynchronize it's NOT proper, NOT
    correct, NOT perfect - so they correct.
    Common sense has been warning the idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 10:18:50 2026
    From Newsgroup: sci.math

    A lie. It predicts your time dilation nonsense.
    Not just a "frequency shift"

    Enough bullshit.

    "Time dilation" here HAS an observable quantitative consequence: a frequency/rate shift between clocks following the specified worldlines.

    And NTS-2 is brutally simple:

    prediction BEFORE launch: +446.5 |u 10^-12
    correction OFF
    measurement: +442.5 |u 10^-12

    You can scream "SHARK!" until retirement. Those are the prediction and
    the measurement of the same physical quantity.

    sane people have a different opinion. In their opinion when
    clocks desynchronize it's NOT proper, NOT correct, NOT perfect

    This is your other lie.

    Engineers correcting a physical effect to satisfy an engineering
    requirement does NOT imply they believe the physical prediction was
    wrong.

    Quite the contrary: they need the prediction to know the correction.

    You have now spent dozens of posts trying to transform

    "Relativity correctly predicts how the clock runs"

    into

    "Relativity commands GPS engineers to let their clocks disagree."

    Relativity commands nothing.

    It predicts.

    It predicted 446.5.
    They measured 442.5.

    Your theory predicted fuck all.

    Now perhaps give the shark a rest.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 12:32:55 2026
    From Newsgroup: sci.math

    On 10/20/2026 12:18 PM, Python wrote:
    A lie. It predicts your time dilation nonsense.
    Not just a "frequency shift"

    Enough bullshit.

    "Time dilation" here HAS an observable quantitative consequence:

    Sure, poor piece of lying shit - the difference
    in clock INDICATIONS. Really - 0. Falsified.

    Yeah, right, the clocks have been calibrated,
    I know.



    sane people have a different opinion. In their opinion when
    clocks desynchronize it's NOT proper, NOT correct, NOT perfect

    This is your other lie.

    Nope. Common sense has been warning the idiot.



    Engineers correcting a physical effect to satisfy an engineering
    requirement does NOT imply they believe the physical prediction was
    wrong.

    And engineers correcting junk clocks mean
    they don't share mad opinion of brainwashed
    religious maniacs asserting they're perfect.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 10:39:06 2026
    From Newsgroup: sci.math

    Maciej,

    the difference in clock INDICATIONS. Really - 0. Falsified.

    Yeah, right, the clocks have been calibrated,
    I know.

    You have finally compressed your entire argument into four lines:

    The predicted difference is zero.
    Because the predicted difference was compensated.
    Yes, I know it was compensated.
    Falsified!

    This is idiotic.

    With the correction OFF, the indication difference GROWS at the
    measured rate:

    measured: +442.5 |u 10^-12
    predicted: +446.5 |u 10^-12

    Switch the correction ON and that growth is cancelled.

    And then you point at the cancellation as evidence that there was
    nothing to cancel.

    engineers correcting junk clocks

    They are not correcting "junk clocks". They are deliberately offsetting
    good clocks because good clocks in different gravitational potentials
    and states of motion do NOT naturally realize the same GPS coordinate
    time.

    The spectacular part is that you now explicitly admit the calibration
    while still using its result as your alleged falsification.

    "Common sense" isn't warning the idiot anymore.

    It's begging him to stop helping.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 12:44:44 2026
    From Newsgroup: sci.math

    On 10/20/2026 12:39 PM, Python wrote:
    Maciej,

    the difference in clock INDICATIONS. Really - 0. Falsified.

    Yeah, right, the clocks have been calibrated,
    I know.

    You have finally compressed your entire argument into four lines:

    -a-a The predicted difference is zero.
    -a-a Because the predicted difference was compensated.

    That's the difference between a sheep (error)
    and a shark (dilation). We compensate the first,
    we don't compensate the other. Sorry, poor piece
    of shit.


    engineers correcting junk clocks

    They are not correcting "junk clocks". They are deliberately

    They are deliberately correcting junk clocks.
    Sorry, poor piece of shit. Your mad assertions
    "perfect!!! correct!!! proper!!!!" didn't
    prevent them, words have a great power but
    not great enough to save your mad Shit.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 10:55:22 2026
    From Newsgroup: sci.math

    That's the difference between a sheep (error)
    and a shark (dilation). We compensate the first,
    we don't compensate the other.

    And there it is: your entire argument is a definition YOU invented.

    If compensated -> error.
    If dilation -> must not be compensated.

    Why?

    There is absolutely no physical principle saying that a real physical
    effect cannot be deliberately compensated.

    Relativity predicts the rate shift.
    NTS-2 measures the rate shift.
    GPS compensates the rate shift.

    You then decree that because it was compensated, it must retroactively
    have been an "error" rather than the predicted physical effect.

    That's not an experiment.

    That's wordplay.

    Your sheep and shark are the same fucking +442.5 |u 10^-12 wearing
    different labels.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 13:09:04 2026
    From Newsgroup: sci.math

    On 10/20/2026 12:55 PM, Python wrote:
    That's the difference between a sheep (error)
    and a shark (dilation). We compensate the first,
    we don't compensate the other.

    And there it is: your entire argument is a definition YOU invented.

    -a-a If compensated -> error.
    -a-a If dilation-a-a-a -> must not be compensated.

    Why?


    Because if it is compensated, poor piece of shit -
    there is no "difference in clock indications",
    i.e. there is no "time dilation".

    And that when it's error we compensate - even
    you realize, you're just pretending you don't,
    as expected from a piece of fanatic, lying shit.


    Relativity predicts the rate shift.

    Rate shift being time dilation. Not rate
    shift being a clock error.

    That's not an experiment.

    As said as the very beginning. your
    moronic "experiments" liturgy is of
    no significance.
    Well, maybe of SOME significance.




    That's wordplay.

    Your sheep and shark are the same fucking +442.5 |u 10^-12 wearing
    different labels.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 11:11:37 2026
    From Newsgroup: sci.math

    Maciej,

    Because if it is compensated [...] there is no
    "difference in clock indications"

    This is spectacularly circular:

    If we compensate X, X disappears.
    If X disappears, X never existed.
    Therefore what we compensated wasn't X.

    No.

    Compensation changes what happens AFTER compensation. It does not
    rewrite what happened BEFORE it.

    And NTS-2 makes your semantic escape impossible:

    correction OFF
    predicted rate difference: +446.5 |u 10^-12
    measured rate difference: +442.5 |u 10^-12

    At that point there WAS a growing difference in clock indications.

    Then they compensated it.

    Your response is essentially:

    "But after they cancelled it, it was cancelled!"

    Congratulations.

    Common sense has discovered subtraction.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 13:22:13 2026
    From Newsgroup: sci.math

    On 10/20/2026 1:11 PM, Python wrote:
    Maciej,

    Because if it is compensated [...] there is no
    "difference in clock indications"

    This is spectacularly circular:

    Sure. So what? So is your "perfect clocks
    indicate proper time, i.e. what perfect
    clocks indicate." All models are.




    -a-a If we compensate X, X disappears.

    No, poor piece of shit. Sorry, it's not
    that trivial.
    We have your beloved "clock rate difference".
    Both "time dilation" and "clock error" concepts
    are referring to it.

    So, how to distinguish? Simply:
    the "rate difference" we correct is an error,
    the "rate difference" we accept would be
    your time dilation. If we accepted it, like
    your mad religion was trying to force us.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 11:37:16 2026
    From Newsgroup: sci.math

    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:

    same measured rate difference
    |
    +-- engineers accept it -> "time dilation"
    |
    +-- 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".

    Same clock.
    Same orbit.
    Same measured rate.
    Different engineering policy.

    And you call THAT physics.

    Relativity has the considerably less mystical criterion of predicting
    the rate from the physical trajectory and gravitational field.

    Which, inconveniently for you, it did BEFORE anyone decided what to do
    with it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 13:44:32 2026
    From Newsgroup: sci.math

    On 10/20/2026 1:37 PM, Python wrote:
    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.

    That's a fact. Your idiot guru has been
    babbling about clock indications, they
    definitely depend on how engineers
    make and adjust the clocks, sorry, poor
    piece of shit.


    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".

    Would be. Go convince them their clocks
    are not perfect enough and they have to
    stop compensating at once.
    If you succeed - I will admit: your
    mad Shit is ruling GPS. Go, poor piece
    of shit, be fearless, your cause is true
    and just.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 11:48:01 2026
    From Newsgroup: sci.math

    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.
    Engineering compensates the effect.
    GPS works.

    There is no conflict whatsoever.

    The conflict exists entirely in your head because you invented the rule:

    real physical effect + compensation = clock error
    real physical effect + no compensation = time dilation

    Physics doesn't work that way.

    If engineers compensate thermal expansion in a bridge, thermal
    expansion doesn't cease to be physics.

    The funniest part is that your proposed test for whether relativity
    "rules GPS" is now whether engineers REFUSE to use relativity to make
    GPS work properly.

    That's quite possibly the most backwards argument you've produced yet.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 13:55:48 2026
    From Newsgroup: sci.math

    On 10/20/2026 1:48 PM, Python wrote:
    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?

    Because otherwise those mad prophecies of the
    idiot you're worshiping fail sadly and miserably.



    Relativity predicts the effect.

    Sure, the effect of - difference in clock
    indications. As long as sane people fuck
    your idiocies the effect doesn't exist, and
    even such a hopeless piece of lying shit
    has to admit: the REAL difference in clock
    indications is 0.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 14:03:23 2026
    From Newsgroup: sci.math

    On 10/20/2026 1:48 PM, Python wrote:

    If engineers compensate thermal expansion in a bridge, thermal
    expansion doesn't cease to be physics.

    The inventor of "thermal expansion" was a mostly
    sane person, he didn't define his effect as
    "perfect bridges should collapse". The idiot was a
    different case, sorry.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to sci.physics.relativity,sci.math on Tue Oct 20 07:11:51 2026
    From Newsgroup: sci.math

    On 10/20/2026 01:00 AM, Python wrote:
    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.

    "Time dilation" by itself is absent the other column, "length
    contraction", which together make "space contraction".


    Audit fail.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 15:29:47 2026
    From Newsgroup: sci.math

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 17:57:45 2026
    From Newsgroup: sci.math

    On 10/20/2026 5:29 PM, 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:

    -a-a effect predicted
    -a-a effect measured

    I've told you, poor piece of shit:
    not any measured effect, just a clock
    error.

    -a-a effect compensated
    -a-a compensated result ree 0

    -a-a therefore effect never existed

    Never existed. Exactly. Just a clock
    error.



    And this:

    "perfect bridges should collapse"

    is precisely the same category error again.

    Relativity does NOT say:

    -a-a "perfect GPS clocks should desynchronize"

    You've admitted many, many times already -
    that's exactly what your mad shit is asserting.
    Even such a disgusting piece of lying shit
    can't lie non stop, but it can lie a lot,
    like above.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 16:03:39 2026
    From Newsgroup: sci.math

    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:

    predicted before launch: +446.5 |u 10^-12
    correction OFF
    measured in orbit: +442.5 |u 10^-12

    Your explanation:

    "clock error"

    Why that magnitude?
    Why that sign?
    Why was essentially that number predicted before launch?

    Nothing.

    Never existed. Exactly. Just a clock error.

    Wonderful.

    The measured effect never existed because you renamed the measured
    effect "error".

    This is your entire argument now.

    Relativity provides a quantitative prediction.

    You provide a noun.

    And a remarkable quantity of "piece of shit".
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 18:13:50 2026
    From Newsgroup: sci.math

    On 10/20/2026 6:03 PM, Python wrote:
    Maciej,

    not any measured effect, just a clock
    error.

    You keep saying "just a clock error" as though naming the measurement explained it.

    It did. Can't erroneous equipment "measure"
    effects that don't exist? What more to
    explain?



    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?

    Who cares? We corrected, and the correct corrected
    clocks measure the effect no more. If someone
    treated seriously your mad screams "PROPER!!!!
    CORRECT!!!! PERFECT!!!!" things would be different.
    But The Shit really never had any chance. Common
    sense has been warning the idiot.

    The measured effect never existed because you renamed the measured
    effect "error".

    What's so surprising? Can't erroneous equipment
    "measure" effects that don't exist?



    Relativity provides a quantitative prediction.

    And it's worthless, the really measured value is
    0 with good accuracy.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 16:15:08 2026
    From Newsgroup: sci.math

    Maciej,

    Why that magnitude?
    Why that sign?

    Who cares?

    And there, finally, is your entire scientific method.

    Relativity, BEFORE launch:

    +446.5 |u 10^-12

    NTS-2, correction OFF:

    +442.5 |u 10^-12

    Maciej:

    "Who cares?"

    Then:

    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.

    Your answer is literally that you don't care.

    the really measured value is 0

    AFTER correcting by approximately the amount predicted.

    So your "really measured value" is:

    measured effect - compensation for measured effect ree 0

    and you conclude:

    measured effect = 0.

    This isn't common sense.

    It's subtraction followed by amnesia.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 18:27:24 2026
    From Newsgroup: sci.math

    On 10/20/2026 6:15 PM, Python wrote:
    Maciej,

    Why that magnitude?
    Why that sign?

    Who cares?

    And there, finally, is your entire scientific method.

    Fuck your so called "scietific method" crap.
    Relativity, BEFORE launch:

    -a-a +446.5 |u 10^-12

    Really measured value - 0. Even such a disgusting
    piece of lying shit as you are sometimes is admitting
    that.

    Relativistic idiot:
    "THE CLOCKS WERE CALIBRATED!!!! DOESN'T COUNT!!!"
    But yes, poor piece of shit, it does.



    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.


    He can, but fuck the idiot.


    the really measured value is 0

    AFTER correcting by approximately the amount predicted.

    Lie. Your mad shit has predicted 0 of clock error
    to compensate.



    So your "really measured value" is:

    -a-a measured effect - compensation for measured effect ree 0


    Nope. My really measured value is the REAL
    value of the difference in clock indications.
    And even such a disgusting piece of lying
    shit as you are sometimes is admitting that
    this is the REAL value of the difference in clock
    indications. 0.

    And that clocks were calibrated? Sure. In
    the real world, unlike in your moronic
    gedankenwelt - it's ordinary.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 16:51:44 2026
    From Newsgroup: sci.math

    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:

    correction OFF: +442.5 |u 10^-12 measured
    correction ON: 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".

    It predicts how the clock rate changes with its physical conditions.

    GPS engineers then decide that this perfectly predicted behaviour is inconvenient for maintaining GPS system time, so they compensate it.

    And the required compensation has essentially the magnitude relativity predicted.

    Your alternative theory has now reached admirable simplicity:

    Why 442.5? Who cares?
    Why that sign? Who cares?
    Why predicted beforehand? Fuck the physicist who asks.

    After cancelling it, I get zero.

    QED.

    At least you've finally made clear why your "common sense" has no need
    for a scientific method.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 19:12:41 2026
    From Newsgroup: sci.math

    On 10/20/2026 6:51 PM, Python wrote:
    Maciej,

    Fuck your so called "scientific method" crap.

    Yes, that was already becoming clear.

    You're too dumb to comprehend, but
    poor idiot Popper has invented it especially
    to excuse the madness of your idiot guru.
    Thinkers more advanced - Poincare, Kuhn -
    knew better.


    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.

    Right. I keep measuring with calibrated clocks.
    And you keep pretending there is something
    strange and exceptional in that. Nope.

    That's the reality. The result of a measurement
    is depending on how we make and adjust the
    equipment. Your mad, brainwashing religion is
    not going to ever admit that, it will keep
    pretending that the measurement is God
    Himself speaking (of course, only the measurement
    fitting it), but it's just a mad, brainwashing
    religion.


    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.

    Lie, of course. I call the second one real because
    1)the first was for 20 days (about), the
    other for 50 years
    2)More important - we corrected the clocks giving
    1, so they were erroneous.
    You, on the other hand - keep pretending 1 to be
    the only real result because the 2 is catastrophically
    inconvenient.

    Your mad shit has predicted 0 of clock error
    to compensate.

    Relativity doesn't predict a malfunction called "clock error".

    Sometimes even such a disgusting piece of
    shit is telling the truth. Yes, your mad
    Shit is predicting nothing to compensate.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 17:17:28 2026
    From Newsgroup: sci.math

    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, while the
    50 years spent COMPENSATING the effect supposedly prove the effect
    wasn't there.

    By that logic, taking an umbrella for 50 years disproves the rain you
    measured before opening it.

    we corrected the clocks giving 1, so they were erroneous.

    No. You keep using your conclusion as your premise:

    it was corrected
    therefore it was an error
    therefore it wasn't time dilation
    therefore relativity was wrong

    That isn't reasoning. It's a carousel.

    And the historical sequence remains brutally immune to your vocabulary:

    BEFORE launch:
    relativity calculates +446.5 |u 10^-12

    IN orbit, correction OFF:
    clock measures +442.5 |u 10^-12

    AFTER measurement:
    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 answer was:

    "Who cares?"
    "Fuck the physicist."

    Which is admirably concise.

    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.
    Engineers decide what they want instead.

    After hundreds of lines of abuse, your rebuttal to +446.5 predicted
    versus +442.5 measured is still just:

    WRONG WORD!

    That's not shutting physics down, Maciej.

    That's losing an argument to a dictionary.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 19:33:08 2026
    From Newsgroup: sci.math

    On 10/20/2026 7:17 PM, Python wrote:
    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

    Rather - 20 days compared to 50 years makes
    an exception of no significance.



    we corrected the clocks giving 1, so they were erroneous.

    No. You keep using your conclusion as your premise:

    Yes. You keep denying the reality.


    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

    And the correct corrected clocks measure your delusion
    no more. It was just a clock error.


    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.

    A lie, you were admitting many times - your mad
    Shit has predicted no error.


    your mad Shit is predicting nothing to compensate.

    It predicted the physical rate shift that engineers compensate.

    Unfortunately - it's also predicted
    some difference in clock indications,
    which doesn't exist.
    And it has asserted that perfect clocks
    are desynchronizing clocks. But as the
    assertion is as baseless as it is idiotic,
    nobody is treating it seriously.

    Your insistence that a theory must additionally call that shift an
    "ERROR" before engineers are permitted to cancel it is entirely your invention.


    I'm not insisting on anything like that.
    Your theory definitely can be stupid, and
    it is. And engineers are NOT permitted to
    cancel it. Your theory is forbidding
    that in the name of prophecies of a mumbling
    madman, it's just that nobody cares.




    Physics predicts what happens.

    And then it doesn't happen, even such a hopeless
    piece of lying shit is sometimes admitting
    that.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 20:25:16 2026
    From Newsgroup: sci.math

    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:

    The uncontaminated test doesn't count because it lasted only 20 days.

    The following 50 years of cancelling the effect prove that the
    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

    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.

    They did.

    And then it doesn't happen

    It DID happen.

    That's the part you cannot make disappear:

    predicted: +446.5 |u 10^-12
    measured: +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.

    And after all the sharks, sheep, "perfect clocks", "clock errors",
    "common sense", Popper, Poincar|-, Kuhn and several metric tons of
    "piece of shit", you still have no answer to the only question that
    matters:

    Why did the uncorrected NTS-2 clock produce +442.5 |u 10^-12
    when relativity had predicted +446.5 |u 10^-12 before launch?

    Your answer remains:

    "Who cares?"

    Everyone who understands what a quantitative prediction is, Maciej.

    That's rather the point.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 23:07:32 2026
    From Newsgroup: sci.math

    On 10/20/2026 10:25 PM, Python wrote:
    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.

    Lie, there are no relativistic effects
    to compensate.




    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.

    Correct corrected clocks measure no
    delusion of yours, it was just a clock
    error, sorry, poor piece of shit.




    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.

    Right, your mad religion is persuading
    people that if the clocks don't fit mad
    delusions of your mumbling guru they're
    wrong. Fortunately, since your mad assertion
    is as baseless as it is idiotic - nobody
    sane cares, and the clocks keep measuring
    t'=t, just like they always were.



    It does not dictate what frequency engineers must make an oscillator
    output for a navigation system.

    Yes, poor piece of shit, it does. And
    brainwashed SI idiots announcing their
    wannabe standard are trying to help. Waste
    of efforts. No chance. The clocks are not
    indicating and are not going to indicate
    what the idiot imagined and announced
    perfect.




    Engineers are perfectly free to compensate the predicted effect.

    Even such a pathetic piece of
    lying shit as you are can't lie non
    stop, however, so sometimes you're
    admitting there is no predicted to
    compensate effect. But, basically,
    you're right, engineers are perfectly
    free to piss at your mad screams
    "PERFECT!!! CORRECT!!! PROPER!!!",
    piss at your wannabe standard, piss
    at your Holiest Postulate and the
    whole rest of your idiocies and
    keep the clocks measuring t'=t, just
    like they always were.




    And then it doesn't happen

    It DID happen.

    THE KNIGHT WAS ON A3!!!! AND IF IT
    WAS PERFECT IT WOULD STILL BE THERE!!!
    CHECK!!!!





    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

    Nope. Measured - 0.
    Even such a pathetic piece of lying shit
    can't lie non stop, so sometimes you admit.

    Then they compensated it.

    And started the real measurements.



    Your entire argument is now that once humans deliberately prevent a
    predicted effect from appearing in the final system output, the
    prediction has failed.

    And your entire argument is now (and always)
    that since humans calibrated clocks they're
    corrupted and polluted and dirty and the
    result doesn't count. You're such an idiot.

    By that standard, brakes falsify Newton.

    In your sick, fanatic half-brain everything
    falsify Newton. You're such an idiot.


    -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?

    I've told you, but of course you couldn't
    comprehend. If the atomic clocks didn't
    fit your madness you wouldn't announce
    them perfect and they wouldn't care about
    them.
    I can (and I did) point you many types of
    clocks not fitting your prophecies corrected or
    uncorrected. You simply ignore them. As
    expected from a brainwashed religious maniac.




    Your answer remains:

    -a-a "Who cares?"

    Everyone who understands what a quantitative prediction is, Maciej.

    Sure, "2kg of grass eaten!!! Exactly as
    our ingenious theory of sharks eating
    grass predicted!!! CONFIRMED!!! CONFIRMED!!!!"




    That's rather the point.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 21:15:35 2026
    From Newsgroup: sci.math

    Maciej,

    Measured - 0.

    No.

    correction OFF: +442.5 |u 10^-12
    correction ON: approximately 0

    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
    to cancel the inconvenient measured effect.

    And still, after all the shouting:

    predicted before launch: +446.5
    measured correction OFF: +442.5

    Your explanation for this agreement remains:

    "clock error"
    "who cares?"
    "piece of shit"
    sharks eating grass

    Relativity supplied the number.

    You supplied the zoology.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Tue Oct 20 23:34:17 2026
    From Newsgroup: sci.math

    On 10/20/2026 11:15 PM, Python wrote:
    Maciej,

    Measured - 0.

    No.

    Yes.


    You have now spent dozens of posts arguing that the first measurement
    doesn't count because engineers subsequently cancelled what it measured.

    Lie. Like always.
    You have now spent dozens of posts arguing that
    The Shit is confirmed because there existed some
    clocks fitting it. SOME clocks may fit any
    nonsense.






    And started the real measurements.

    Wonderful.

    So measurements become "real" only after engineers modify the clocks

    To start what GPS was designed for. And it
    happens that GPS is designed for - MEASUREMENTS.
    Your "perfect" junk is - very simply - unusable
    for that, face it, trash.


    And still, after all the shouting:

    -a-a predicted before launch: +446.5
    -a-a measured correction OFF: +442.5

    Yeah. "Measured" with clocks which
    later (almost immediately) showed they're
    unusable for measurements. Great.



    Relativity supplied the number.

    And it was worthless, the measured REALLY
    value is 0.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 21:39:42 2026
    From Newsgroup: sci.math

    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.

    Quite an epidemic of clocks accidentally "fitting the nonsense".

    And NTS-2 was particularly unlucky: its "error" accidentally had the
    right sign and matched a prediction made BEFORE launch to about 1%.

    clocks which later (almost immediately) showed they're
    unusable for measurements.

    This is magnificent too.

    How did they discover the clocks needed adjustment?

    BY MEASURING THEIR RATE.

    Apparently a clock is "unusable for measurements" immediately after
    being used to make the measurement you desperately need to disappear.

    the measured REALLY value is 0.

    Yes, Maciej:

    observe offset
    compensate offset
    observe residual ree 0
    conclude original offset never existed

    At this point you're not refuting relativity.

    You're refuting the concept of subtraction.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 21:52:53 2026
    From Newsgroup: sci.math

    <http://nemoweb.net/jntp?q7Yv_5S-465j3IXSCJ42yDY7XBU@jntp/Data.Media:1>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ross Finlayson@ross.a.finlayson@gmail.com to sci.physics.relativity,sci.math on Tue Oct 20 15:28:24 2026
    From Newsgroup: sci.math

    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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Tue Oct 20 22:32:44 2026
    From Newsgroup: sci.math

    Le 21/10/2026 |a 00:28, Ross Finlayson a |-crit :
    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.

    <http://nemoweb.net/jntp?G1qCd_HDwyzT982G1wUYvQ5ZXjU@jntp/Data.Media:1>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Wed Oct 21 06:40:02 2026
    From Newsgroup: sci.math

    On 10/20/2026 11:39 PM, Python wrote:
    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.
    Your mad religion has persuaded you
    they're perfect, and - while this assertion
    is as baseless as it is idiotic, you believe
    it deeply, and any other (any not-fitting
    the madness of your idiot guru) clock simply
    doesn't exist for you. Typical for brainwashed
    religious maniac.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Wed Oct 21 14:51:57 2026
    From Newsgroup: sci.math

    20 days of 50 years.
    Definitely - some clocks.

    You appear to have missed the rest of the list.

    NTS-2 was 20 days with the correction deliberately OFF.

    Hafele-Keating wasn't NTS-2.
    Gravity Probe A wasn't NTS-2.
    Modern optical-clock experiments aren't NTS-2.
    Decades of GPS atomic clocks aren't NTS-2 either.

    So "20 days of 50 years" is not an answer to any of them.

    any not-fitting the madness [...] clock simply
    doesn't exist for you.

    Excellent. Name one.

    Give us the clock, its trajectory/gravitational conditions, the
    relativistic quantitative prediction, and the measured disagreement.

    That's how you demonstrate a counterexample.

    So far your case against all those quantitative experiments consists
    of repeatedly shouting:

    SOME CLOCKS!
    20 DAYS!
    RELIGION!
    IDIOT GURU!

    The clocks, inconsiderately, continue providing numbers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Wed Oct 21 17:03:08 2026
    From Newsgroup: sci.math

    On 10/21/2026 4:51 PM, Python wrote:
    20 days of 50 years.
    Definitely - some clocks.

    You appear to have missed the rest of the list.

    Still just some clocks of no real importance.
    Your mad religion has persuaded you your
    junk is perfect and incredibly important -
    bullshit, your precious unadjusted Cs
    clocks have no more importance than unadjjusted
    pendulums. And your mad ravings and shitty lies
    won't change that.

    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. Used for the
    real measurements of the real importance,
    unlike your toys, poor piece of shit.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Wed Oct 21 15:04:28 2026
    From Newsgroup: sci.math

    Maciej,

    GPS real/calibrated clocks.

    Ah. So THAT is your counterexample.

    Let's admire it:

    1. Relativity predicts a rate difference.
    2. The unadjusted clock exhibits that rate difference.
    3. Engineers calibrate the clock to compensate it.
    4. The calibrated clock no longer exhibits it.
    5. Maciej presents the calibrated clock as evidence that the
    uncompensated rate difference doesn't exist.

    This is getting almost too easy.

    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

    +446.5 |u 10^-12

    and it subsequently measured

    +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.

    Your "counterexample" is literally the same clock, after applying the correction whose necessity you're trying to deny.

    At this point you're using the cure as proof that the symptom never
    existed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Wed Oct 21 17:16:03 2026
    From Newsgroup: sci.math

    On 10/21/2026 5:04 PM, Python wrote:
    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.

    And even such a disgusting piece of lying
    shit as you are must admit: the REAL, MEASURED
    difference of indications is - 0, against
    mad idiot's prophecies. Of course. Common
    sense has been warning the idiot.


    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.

    Of course it can, poor piece of shit, sorry.
    That's the usual fate of measurements made
    with erroneous equipment. They are erased.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Wed Oct 21 17:45:47 2026
    From Newsgroup: sci.math

    Maciej,

    That's the usual fate of measurements made
    with erroneous equipment. They are erased.

    Ah, excellent. Science according to Maciej:

    BEFORE launch:
    theory predicts +446.5 |u 10^-12

    correction OFF:
    instrument measures +442.5 |u 10^-12

    engineers:
    "Excellent, that's essentially the predicted effect.
    Now switch on the correction."

    Maciej, 49 years later:
    "ERASED! ERRONEOUS EQUIPMENT!"

    This is magnificent.

    Apparently an instrument becomes retrospectively "erroneous" when its measurement agrees embarrassingly well with a prediction you dislike.

    And after correction:

    predicted effect + deliberate compensation ree 0

    Maciej:

    "AHA! THE REAL MEASURED VALUE IS ZERO!
    THE PROPHECY FAILED!"

    This is no longer even subtraction followed by amnesia.

    You've upgraded to subtraction followed by destruction of the
    historical record.

    Your method could revolutionize experimental science:

    Prediction agrees with measurement?

    Calibrate the effect away.

    Declare the original measurement "erased".

    Victory.

    With sufficient calibration, Maciej, you could falsify a thermometer
    by turning on the air conditioning.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Wed Oct 21 20:07:58 2026
    From Newsgroup: sci.math

    On 10/21/2026 7:45 PM, Python wrote:
    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

    Sure, of your time dilation nonsense.
    I. e. of the difference in clock
    indications.
    Of course, the key, decisive factor
    determining the clock indications are
    user adjustments. 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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Wed Oct 21 23:20:31 2026
    From Newsgroup: sci.math

    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?

    prediction BEFORE launch: +446.5 |u 10^-12
    correction during the test: OFF
    measured rate shift: +442.5 |u 10^-12

    Your beloved "user adjustments" were deliberately removed from the
    experiment.

    THAT WAS THE FUCKING POINT OF THE EXPERIMENT.

    And your answer is still:

    "But later they adjusted it!"

    Yes. LATER.

    After measuring almost exactly what relativity had predicted.

    no surprise that his primitive babbling failed.

    Failed?

    Prediction: 446.5.
    Measurement: 442.5.

    You would sell your grandmother for that agreement if it supported
    your own theory.

    Instead you've spent dozens of posts desperately dragging the later
    calibration backwards through time to erase the measurement made
    before it.

    The experiment was designed specifically to separate the physical
    rate shift from the engineering correction.

    It did.

    The number matched.

    And after all the "idiot", "moronic", "religion", "gedankenwelt" and
    "primitive babbling", your answer to that remains essentially:

    YES BUT THEY ADJUSTED IT AFTERWARDS!

    Jesus Christ.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 07:05:18 2026
    From Newsgroup: sci.math

    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 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.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 07:21:58 2026
    From Newsgroup: sci.math

    On 10/22/2026 7:05 AM, Maciej Wo+|niak wrote:
    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.

    Of course - if your mad religion succeeded
    in forcing the users to adjust the clocks
    its "PROPER!!! CORRECT!!! PERFECT!!! MATCHING
    THE SI STANDARD!!!" way its mad prophecies
    would be fulfilled. But there was really
    never any hope for that. Common sense has
    been warning the idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 11:27:44 2026
    From Newsgroup: sci.math

    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.

    Again:

    predicted: +446.5 |u 10^-12
    adjustment: OFF
    measured: +442.5 |u 10^-12

    Nobody had to "force the users" to make that happen.

    IT HAPPENED WITH THE CORRECTION OFF.

    Then engineers deliberately adjusted the clocks so that their output
    would remain aligned with GPS system time.

    And you announce:

    "Really measured value: 0. Good bye, The Shit."

    This is spectacular.

    If I predict that an unheated room will cool by 10 degrees, you measure
    a 9.9-degree drop, then switch on a heater that restores the original temperature, your conclusion is apparently:

    REAL temperature difference: 0.
    Good bye, thermodynamics.

    Common sense has been warning the idiot.

    Common sense apparently has one extraordinary rule:

    Once you compensate an effect, retroactively pretend the
    uncompensated measurement never happened.

    Unfortunately, NTS-2 had the terrible lack of common sense to leave us
    the numbers.

    And those numbers still don't give a shit how loudly you type
    "PROPER!!! PERFECT!!! RELIGION!!!".
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 14:28:46 2026
    From Newsgroup: sci.math

    On 10/22/2026 1:27 PM, Python wrote:
    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. Even such an idiot as
    you are has admitted.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 12:31:26 2026
    From Newsgroup: sci.math

    Adjustment is THE KEY, DECISIVE factor here.

    For the operation of GPS: yes.

    For testing the UNADJUSTED relativistic prediction: obviously not.

    That's why they switched the fucking adjustment OFF.

    Your objection has now become:

    "Your prediction only worked when the factor deliberately excluded
    from the experiment was not involved!"

    YES, MACIEJ.

    That's called controlling a variable.

    They wanted to test the predicted natural rate shift, so they measured
    the clock BEFORE compensating that rate shift.

    And they got:

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    Then they switched the compensation ON for operational GPS.

    You somehow regard this beautifully clean experimental sequence as a devastating objection:

    "BUT WHEN THEY DELIBERATELY CHANGED THE CLOCK RATE,
    THE CLOCK RATE CHANGED!!!"

    Outstanding.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 14:38:32 2026
    From Newsgroup: sci.math

    On 10/22/2026 2:31 PM, Python wrote:
    Adjustment is THE KEY, DECISIVE factor here.

    For the operation of GPS: yes.

    For any clock indications in the real world,
    poor piece of shit. Of course, it doesn't
    include your gedanken delusions.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 13:46:50 2026
    From Newsgroup: sci.math

    Maciej,

    For any clock indications in the real world

    No. And this is now embarrassingly simple.

    Suppose a clock naturally gains 38 microseconds per day.

    You can adjust it by -38 microseconds per day.

    Then:

    natural rate difference: +38 -|s/day
    engineered correction: -38 -|s/day
    resulting indication difference: ~0

    The fact that the last number depends on adjustment does not make the
    first one imaginary.

    NTS-2 separated them experimentally:

    correction OFF:
    predicted +446.5 |u 10^-12
    measured +442.5 |u 10^-12

    correction ON:
    residual approximately zero

    And somehow you think the second line refutes the first.

    AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!

    Yes.

    When testing what a clock does WITHOUT an adjustment, you don't apply
    the adjustment.

    This apparently revolutionary experimental technique is also used for
    heaters, brakes, noise cancellation, feedback controllers and light
    switches.

    If I want to measure how quickly a room cools without heating, I turn
    the heater off.

    You:

    "FRAUD! THE HEATER IS THE KEY DECISIVE FACTOR
    IN THE TEMPERATURE OF REAL ROOMS!"

    Maciej, you're no longer exposing a flaw in relativity.

    You're having a furious argument with the OFF switch.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 15:53:13 2026
    From Newsgroup: sci.math

    On 10/22/2026 3:46 PM, Python wrote:
    Maciej,

    For any clock indications in the real world

    No. And this is now embarrassingly simple.

    Yes, poor piece of shit. In your
    gedankenwelt - gedanken clocks may
    work on your own, driven by mystical
    magic of your pretty little formulas.
    In the reality they must be CRAFTED and
    ADJUSTED.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 14:02:01 2026
    From Newsgroup: sci.math

    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:

    relativity predicts: +446.5 |u 10^-12
    clock measures: +442.5 |u 10^-12

    Your explanation:

    CLOCKS ARE CRAFTED!!!

    Yes. So are thermometers.

    That doesn't explain why a thermometer reads the temperature predicted
    by thermodynamics.

    AS LONG AS THE KEY, DECISIVE FACTOR IS NOT INVOLVED!!!

    The "key, decisive factor" was deliberately switched off precisely to
    measure what happens without it.

    And what happened matched the prior prediction.

    You can write CRAFTED, ADJUSTED and GEDANKEN in capitals another fifty
    times.

    Eventually you still owe us a number.

    Why +442.5 |u 10^-12?

    Relativity had one before launch.

    You still don't have one after fifty years.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 16:29:15 2026
    From Newsgroup: sci.math

    On 10/22/2026 4:02 PM, Python wrote:
    Maciej,

    In the reality they must be CRAFTED and ADJUSTED.

    Congratulations. You have discovered that clocks are manufactured.

    A discovery too hard for the idiot
    you're worshiping.



    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:


    Was here 2 or 3 times. If the clocks didn't
    fit your "perfection differently" - they
    wouldn't be sent. I can, and I did - provide
    you examples of clocks of different construction,
    that wouldn't fit your prophecies any way. You
    are simply ignoring the examples. Your mad
    religion has persuaded you that those fitting
    it are The Ones, and, being a mindless idiot
    mystician - you bought it.








    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 15:23:08 2026
    From Newsgroup: sci.math

    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.

    Suppose NASA maliciously selected a cesium clock because they knew it
    would "fit relativity".

    Fine.

    Now tell us how this selection process made it acquire, IN ORBIT:

    +442.5 |u 10^-12

    when relativity had calculated BEFORE LAUNCH:

    +446.5 |u 10^-12.

    Selecting a cesium clock doesn't manufacture that orbital frequency
    shift.

    clocks of different construction, that wouldn't fit your prophecies

    Of course different clocks can have different sensitivities,
    systematics and operating principles.

    Relativity does not predict:

    EVERY DEVICE CALLED "CLOCK" MUST CHANGE BY +446.5 |u 10^-12.

    It predicts the relation between proper times along specified
    worldlines. A physical clock can test that prediction only insofar as
    its own construction-dependent errors are understood.

    This is elementary experimental physics, not mysticism.

    And your argument has now completed quite a tour:

    It wasn't measured.
    It was measured, but the clock was wrong.
    It was corrected, therefore it never existed.
    The 20-day measurement doesn't count.
    Adjustment is the decisive factor.
    Adjustment was OFF, but that doesn't count either.
    Now the clock itself was selected because it would agree.

    Anything, absolutely anything, except answering:

    Why 442.5 when 446.5 had been predicted?

    At this rate, Maciej, the only component of NTS-2 you haven't blamed
    yet is the launch pad.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 18:35:40 2026
    From Newsgroup: sci.math

    On 10/22/2026 5:23 PM, Python wrote:
    Maciej,

    If the clocks didn't fit your "perfection differently" - they
    wouldn't be sent.

    Ah, excellent. A new escape hatch: selection bias.

    Unfortunately it still doesn't produce the number.

    And even more unfortunately -
    the REAL value of the difference
    of the clock indications (i.e. your
    time dilation), measured by correctly
    calibrated clocks, as close to
    perfection as our best engineers
    can get - is 0. Common sense has
    been warning your idiot guru.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 16:46:18 2026
    From Newsgroup: sci.math

    the REAL value of the difference
    of the clock indications [...] is 0.

    Yes.

    AFTER COMPENSATION.

    You keep presenting this as a revelation when it is literally the
    purpose of the compensation.

    NTS-2:

    correction OFF:
    predicted rate difference: +446.5 |u 10^-12
    measured rate difference: +442.5 |u 10^-12

    correction ON:
    resulting difference: approximately 0

    And your argument is:

    "LOOK! AFTER SUBTRACTING THE PREDICTED DIFFERENCE,
    THE DIFFERENCE IS GONE!"

    Yes, Maciej.

    That's what subtraction does.

    The interesting experimental question was whether the difference
    existed BEFORE it was subtracted.

    It did.

    Its value was measured.

    And relativity had predicted its value before launch.

    You still haven't explained +442.5 |u 10^-12.

    You just keep pointing triumphantly at the zero obtained after
    engineers cancelled it.

    Subtraction followed by amnesia.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 18:55:02 2026
    From Newsgroup: sci.math

    On 10/22/2026 6:46 PM, Python wrote:
    the REAL value of the difference
    of the clock indications [...] is 0.

    Yes.

    AFTER COMPENSATION.

    You keep presenting this as a revelation when it is literally the

    Adjustment is THE KEY, DECISIVE
    factor here. Even such an idiot as
    you are has admitted.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 17:11:16 2026
    From Newsgroup: sci.math

    Maciej,

    You're looping.

    Adjustment is THE KEY, DECISIVE factor here.

    For the FINAL clock indication.

    Not for measuring what the clock does when that adjustment is OFF.

    This really should not require another fifty posts.

    NTS-2 deliberately did:

    adjustment OFF
    prediction: +446.5 |u 10^-12
    measurement: +442.5 |u 10^-12

    Your response is still:

    "BUT ADJUSTMENT IS DECISIVE!"

    Yes. That's why they switched it OFF.

    The experiment was specifically designed to remove your "KEY, DECISIVE
    factor" and measure the physical rate shift independently of it.

    Then, after measuring the predicted shift, they switched the adjustment
    ON and cancelled it for operational use.

    You keep screaming that Einstein failed to predict the adjustment.

    Nobody claims relativity predicts what knob an engineer will turn.

    It predicts how far the knob needs to be turned.

    And that is the number you have spent several days desperately avoiding:

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    Your "common sense" still predicts no number at all.

    Apparently it is excellent at shouting "ADJUST THE CLOCK!" but becomes remarkably shy when asked:

    BY HOW MUCH?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 19:18:18 2026
    From Newsgroup: sci.math

    On 10/22/2026 7:11 PM, Python wrote:
    Maciej,

    You're looping.

    Adjustment is THE KEY, DECISIVE factor here.

    For the FINAL clock indication.

    And for time, i.e. "what clocks indicate",
    poor piece of shit. It's not any magical
    power of your moronic formulas, it's designing,
    crafting and adjusting.

    And, of course - if your mad religion succeeded
    in forcing the users to adjust the clocks
    its "PROPER!!! CORRECT!!! PERFECT!!! MATCHING
    THE SI STANDARD!!!" way its mad prophecies
    would be fulfilled. But there was really
    never any hope for that. Common sense has
    been warning the idiot.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 17:21:43 2026
    From Newsgroup: sci.math

    Maciej,

    And for time, i.e. "what clocks indicate"

    No. You are once again confusing three different things:

    1. how a physical clock naturally runs under given conditions;
    2. how engineers deliberately adjust it;
    3. what it indicates after that adjustment.

    NTS-2 separated 1 and 2 experimentally.

    With the relativistic correction DISABLED, the clock did not magically
    choose its indication because an engineer "crafted" it that way.

    Its orbital rate shifted.

    predicted before launch: +446.5 |u 10^-12
    measured in orbit: +442.5 |u 10^-12

    Then engineers deliberately changed its rate.

    if your mad religion succeeded in forcing the users to adjust the clocks

    This is becoming hilarious.

    Relativity did not "force" the clock to be adjusted so that its
    prediction would come true.

    THE PREDICTION CAME TRUE WITH THE ADJUSTMENT OFF.

    The adjustment was applied afterwards to CANCEL the predicted effect.

    You have now managed to reverse the chronology completely:

    relativity predicts X
    experiment with correction OFF measures X
    engineers later compensate X
    Maciej: "AHA! THE COMPENSATION CAUSED THE PROPHECY TO COME TRUE!"

    No.

    The prophecy had already come true.

    The compensation made its operational consequence disappear.

    And after all these posts, you still cannot answer the embarrassingly
    simple question:

    Why did an uncorrected clock produce +442.5 |u 10^-12
    when relativity had predicted +446.5 |u 10^-12?

    "DESIGNING! CRAFTING! ADJUSTING!"

    is not a calculation.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 19:31:48 2026
    From Newsgroup: sci.math

    On 10/22/2026 7:21 PM, Python wrote:
    Maciej,

    And for time, i.e. "what clocks indicate"

    No.

    Yes, poor piece of shit, yes.


    And, of course - if your mad religion succeeded
    in forcing the users to adjust the clocks
    its "PROPER!!! CORRECT!!! PERFECT!!! MATCHING
    THE SI STANDARD!!!" way its mad prophecies
    would be fulfilled. But there was really
    never any hope for that. Common sense has
    been warning the idiot.




    if your mad religion succeeded in forcing the users to adjust the clocks

    This is becoming hilarious.

    Relativity did not "force" the clock to be adjusted so that its
    prediction would come true.

    Of course it didn't - the clocks keep measuring
    t'=t just like they always did. It was just
    trying. Wasted efforts, common sense has been
    warning the idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Thu Oct 22 21:08:21 2026
    From Newsgroup: sci.math

    On 10/22/2026 7:31 PM, Maciej Wo+|niak wrote:


    Relativity did not "force" the clock to be adjusted so that its
    prediction would come true.

    Of course it didn't - the clocks keep measuring
    t'=t just like they always did. It was just
    trying. Wasted efforts, common sense has been
    warning the idiot.

    You did your best, poor piece of shit.
    You were chanting "PROPER!!! CORRECT!!!
    PERFECT!!!" as loudly as you could. You
    casted "bottles of vodka", "nurses" and
    tons of other shit at every opposition
    you meet... Wasted efforts. The clocks
    keep and will keep measuring t'=t, just
    like they always did.




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Thu Oct 22 22:04:15 2026
    From Newsgroup: sci.math

    Maciej,

    the clocks keep measuring t'=t just like they always did.

    No.

    The NTS-2 clock, with the relativistic correction OFF, measured:

    t' != t

    More precisely, its rate differed by:

    measured: +442.5 |u 10^-12

    where relativity had predicted:

    predicted: +446.5 |u 10^-12

    Only AFTER compensation was the operational result brought back toward:

    t' = t

    You are now simply taking the result AFTER engineers deliberately
    cancelled the rate difference and pretending it was also the result
    BEFORE they cancelled it.

    It wasn't.

    That's exactly why the first 20 days of NTS-2 matter.

    Correction OFF: 442.5 |u 10^-12.

    Correction ON: approximately zero.

    Your entire argument requires those two experiments to have had the
    same result.

    They didn't.

    And shouting "t'=t" cannot retroactively change what the uncorrected
    clock measured.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 06:53:20 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:04 AM, Python wrote:
    Maciej,

    the clocks keep measuring t'=t just like they always did.

    No.

    The NTS-2 clock, with the relativistic correction OFF, measured:

    -a-a t' != t

    As long as the key, decisive factor
    wasn't involved.



    You are now simply taking the result AFTER engineers deliberately

    Excuse me, poor piece of shit, weren't
    the clocks of Newtonian physicists
    deliberately calibrated?

    Your shitty revolution has changed NOTHING.
    The clocks keep doing what they always
    did, it's just that your bunch of fanatics
    is grumbling that it's incorrect, improper
    and dirty, and it shouldn't be taken into
    account.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 09:01:58 2026
    From Newsgroup: sci.math

    Maciej,

    weren't the clocks of Newtonian physicists
    deliberately calibrated?

    Of course.

    And once again: calibration does not explain the number.

    Calibrate two cesium clocks together on Earth.

    Put one into the NTS-2 orbit.

    Leave the relativistic correction OFF.

    What happens?

    Relativity, BEFORE launch:

    +446.5 |u 10^-12

    Experiment:

    +442.5 |u 10^-12

    "Newtonian physicists calibrated clocks too" predicts neither number.

    Your shitty revolution has changed NOTHING.

    Except, inconveniently, the quantitative prediction of what happens
    when that calibrated clock is moved into a different gravitational
    potential and velocity.

    That is precisely what was tested.

    Your argument has now reached:

    "Clocks were calibrated before Einstein,
    therefore relativity predicts nothing about clocks."

    Thermometers were calibrated before statistical mechanics too.

    So what?

    The clocks keep doing what they always did

    YES.

    And relativity predicts what they do.

    That is the part you keep desperately walking around.

    Nobody needed Einstein to invent calibration.

    They needed physics to calculate how much the clock rate would change.

    NTS-2 supplied a wonderfully simple comparison:

    Einstein: +446.5 |u 10^-12
    experiment: +442.5 |u 10^-12
    Maciej: "CLOCKS WERE CALIBRATED BEFORE EINSTEIN!"

    Still waiting for your number.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 12:22:58 2026
    From Newsgroup: sci.math

    On 10/23/2026 11:01 AM, Python wrote:
    Maciej,

    weren't the clocks of Newtonian physicists
    deliberately calibrated?

    Of course.

    And once again: calibration does not explain the number.

    Calibrate two cesium clocks together on Earth.

    Put one into the NTS-2 orbit.

    Leave the relativistic correction OFF.

    What happens?

    Relativity, BEFORE launch:

    -a-a +446.5 |u 10^-12

    Experiment:

    -a-a +442.5 |u 10^-12

    See, poor piece of shit - science
    has been working with scientists for
    centuries. Its idiotproofness is
    amazing. Even such a nonsensical
    crap as The Shit of Einstein can
    have some correct predictions and
    be squeezed for some usable information.

    And if your mad religion limited
    itself to things it's familiar with,
    including your "clock rates" I
    wouldn't be here fighting it. But
    no - it had to start babbling about
    the indications of perfect clocks.
    Too bad for it.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 10:27:01 2026
    From Newsgroup: sci.math

    Maciej,

    Ah.

    So after several days of:

    "t'=t!"
    "just clock error!"
    "adjustment is THE KEY!"
    "your prophecy failed!"

    we finally arrive at:

    Even such a nonsensical crap as The Shit of Einstein can
    have some correct predictions

    Thank you.

    That was the point.

    Relativity predicted the orbital clock-rate shift quantitatively:

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    So the effect was not created by adjustment, calibration, religion, terminology, or engineers being bullied by Einstein.

    It was predicted and then measured with the correction OFF.

    Now you retreat to:

    But [...] it had to start babbling about
    the indications of perfect clocks.

    There is no retreat available there either.

    An ideal clock in relativity is simply a theoretical clock whose
    reading follows proper time along its worldline.

    "Perfect" does NOT mean:

    "a clock magically adjusted so that its indication must remain
    equal to every other clock everywhere."

    That is your definition, not relativity's.

    And this distinction is exactly what the experiment demonstrates:
    two clocks can be perfectly good clocks and nevertheless accumulate
    different elapsed times along different worldlines.

    You may dislike calling that "proper time".
    You may dislike "ideal clock".
    You may dislike Einstein.

    But after finally conceding that the quantitative prediction is
    correct, changing the vocabulary won't make

    442.5 |u 10^-12

    turn back into zero.

    You've spent days fighting the physics.

    Now that you've conceded the physics, you're fighting the dictionary.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 12:32:16 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:27 PM, Python wrote:
    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, even such
    a disgusting piece of lying shit as
    you are is admitting that sometimes.

    And if your mad religion limited
    itself to things it's familiar with,
    including your "clock rates" I
    wouldn't be here fighting it. But
    no - it had to start babbling about
    the indications of perfect clocks.
    Too bad for it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 10:33:46 2026
    From Newsgroup: sci.math

    Maciej,

    It has also predicted, also quantitatively -
    difference in clock indication in GPS.
    Bullshit, the measured value is 0

    No.

    You are STILL confusing the physical prediction with the engineered
    output after compensation.

    Relativity predicts that, if you take suitable clocks along the two
    different worldlines WITHOUT compensating their relative rates, their elapsed-time readings diverge.

    NTS-2 tested precisely that situation:

    relativistic correction OFF

    predicted fractional rate difference:
    +446.5 |u 10^-12

    measured fractional rate difference:
    +442.5 |u 10^-12

    A nonzero rate difference accumulated over time IS a growing difference
    in clock indications.

    Then engineers compensated the rate difference so that GPS clocks would
    remain aligned with GPS system time.

    And, astonishingly:

    compensated difference ree 0

    You keep calling that zero the "measured value" of the relativistic
    effect.

    It is the measured RESIDUAL AFTER CANCELLING the relativistic effect.

    If

    natural drift = +38 -|s/day

    and engineers apply

    correction = -38 -|s/day,

    then obtaining

    residual ree 0

    does not demonstrate that the natural drift was zero.

    It demonstrates that the correction worked.

    And this makes your new concession particularly fatal:

    including your "clock rates"

    You now concede that relativity correctly predicts the clock-rate
    difference.

    Maciej, integrate a nonzero rate difference over time.

    What do you get?

    A difference in clock indications.

    There is no magical firewall between "clock rates" and "clock
    indications".

    The latter is the integral of the former.

    Your entire remaining argument is therefore:

    "I concede the derivative, but deny that integrating it
    changes the function."

    Good luck with that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 12:40:26 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:33 PM, Python wrote:
    Maciej,

    It has also predicted, also quantitatively -
    difference in clock indication in GPS.
    Bullshit, the measured value is 0

    No.

    Yes. And even such a pathetic piece of
    shit as you are is admitting it sometimes.

    Let's try again: the indication of a clock
    from GPS ground base is - 2026-10-23 15:00:00.00000000.
    What is the [measured] indication of a clock in
    a GPS satellite?


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 10:41:40 2026
    From Newsgroup: sci.math

    Maciej,

    the indication of a clock from GPS ground base is -
    2026-10-23 15:00:00.00000000.
    What is the [measured] indication of a clock in
    a GPS satellite?

    After the GPS clock has been deliberately frequency-offset and its
    remaining clock offset/drift corrections have been applied?

    Approximately:

    2026-10-23 15:00:00.00000000

    within the accuracy of the system.

    Nobody disputes that.

    Now remove the relativistic frequency compensation.

    After one day, approximately:

    ground: 2026-10-24 15:00:00.000000
    satellite: 2026-10-24 15:00:00.000038

    That's precisely the point.

    You are asking me for the output AFTER engineers have deliberately
    cancelled the predicted rate difference, obtaining approximately zero,
    and pretending this measures the rate difference BEFORE cancellation.

    It doesn't.

    And you've just conceded that relativity correctly predicts the
    "clock rates".

    So your argument has become mathematically spectacular:

    d(satellite time - ground time)/dt != 0

    but somehow, according to Maciej,

    satellite time - ground time = 0

    forever.

    Calculus would like a word.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 12:45:53 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:41 PM, Python wrote:
    Maciej,

    the indication of a clock from GPS ground base is -
    2026-10-23 15:00:00.00000000.
    What is the [measured] indication of a clock in
    a GPS satellite?

    After the GPS clock has been deliberately frequency-offset and its
    remaining clock offset/drift corrections have been applied?

    Approximately:

    -a-a 2026-10-23 15:00:00.00000000
    Yes. The real, measured value of the difference
    in clock indications is - 0. Even such
    a disgusting piece of lying shit is
    admitting it, again.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 10:49:45 2026
    From Newsgroup: sci.math

    Maciej,

    The real, measured value of the difference
    in clock indications is - 0.

    AFTER COMPENSATION.

    Yes.

    Nobody has denied this. Ever.

    Now let's try your reasoning on something simpler:

    natural drift: +38 -|s/day
    applied correction: -38 -|s/day
    measured residual: 0 -|s/day

    Maciej concludes:

    "THE REAL MEASURED DRIFT IS ZERO!"

    No.

    The real measured RESIDUAL is zero.

    The natural drift was measured separately, with the correction OFF.

    And this is not hypothetical:

    NTS-2 correction OFF:
    measured rate shift = +442.5 |u 10^-12

    You are deliberately choosing the compensated observable and calling it
    the uncompensated observable.

    That's like applying a 10 kg counterweight, observing that a scale is
    balanced, and triumphantly announcing:

    "THE REAL MEASURED WEIGHT IS ZERO!"

    No.

    The zero is the result AFTER compensation.

    And the funniest part is that you have now conceded that relativity
    correctly predicts the clock-rate difference.

    So we have reached:

    nonzero rate difference: admitted
    compensation of that rate difference: admitted
    zero residual after compensation: admitted

    and somehow your conclusion is:

    therefore the uncompensated rate difference never existed.

    Subtraction followed by amnesia, again.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 12:51:59 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:49 PM, Python wrote:
    Maciej,

    The real, measured value of the difference
    in clock indications is - 0.

    AFTER COMPENSATION.
    Adjustment is THE KEY, DECISIVE
    factor here. Even such an idiot as
    you are has admitted.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 10:56:09 2026
    From Newsgroup: sci.math

    Maciej,

    You're literally pasting the same paragraph again.

    So let's make this painfully short.

    YES:

    adjustment is decisive for the FINAL indication.

    NO:

    adjustment cannot explain a measurement made
    while that adjustment is SWITCHED OFF.

    NTS-2:

    correction OFF
    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    You have now even admitted that this was a correct prediction.

    So screaming

    "THE KEY, DECISIVE FACTOR WAS NOT INVOLVED!"

    is hilarious.

    OF COURSE IT WASN'T INVOLVED.

    THAT WAS THE FUCKING POINT OF SWITCHING IT OFF.

    They were measuring what happened WITHOUT the compensation.

    Then they switched it on and cancelled the measured effect.

    This isn't relativity you are failing to understand anymore.

    It's the meaning of an ON/OFF switch.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:06:41 2026
    From Newsgroup: sci.math

    On 10/23/2026 12:56 PM, Python wrote:
    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.

    Are you trying to babble that the idiot
    defining time meant "indication, but not
    the final one"?
    How is it in galilean physics? Is "time"
    the indication of an unadjusted pendulum
    there?



    NO:

    -a-a adjustment cannot explain a measurement made
    -a-a while that adjustment is SWITCHED OFF.

    It can, and very easily. A clock error.
    Discarded.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 11:11:46 2026
    From Newsgroup: sci.math

    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:

    relativity predicted before launch:
    +446.5 |u 10^-12

    clock placed in orbit, correction OFF:
    +442.5 |u 10^-12

    Maciej:
    "clock error"

    What extraordinary luck.

    The "clock error" had:

    the predicted sign,
    the predicted magnitude,
    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:

    prediction agrees with measurement -> discard measurement as error
    correction based on prediction works -> discard that too
    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:

    +446.5 |u 10^-12

    Your theory says:

    ERROR! DISCARDED!

    One of those predicted a number.

    The other is a wastebasket.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:19:15 2026
    From Newsgroup: sci.math

    On 10/23/2026 1:11 PM, Python wrote:
    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.

    Sure. Time can be only what an
    unadjusted clock marked by a
    Shit worshiper happen to indicate.
    Or an adjusted one - doesn't matter.
    Only matters whether worshipers like
    it or not.

    Anyway, the REAL, MEASURED value
    of the difference in clock indications
    is 0. Even such a disgusting piece of
    lying shit is admitting that sometimes.






    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

    Yeah. Of the time dilation, of the
    difference in clock indications.
    The real, measured value is - 0.
    Even such a disgusting piece of
    lying shit as you are is sometimes
    admitting that. Good bye, The Shit.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 11:33:38 2026
    From Newsgroup: sci.math

    Maciej,

    The real, measured value is - 0.

    Yes.

    After compensation.

    And with the compensation OFF, the real measured value was:

    +442.5 |u 10^-12

    after relativity had predicted:

    +446.5 |u 10^-12.

    You now call that measurement a "clock error" because otherwise you
    would have to acknowledge the obvious:

    relativity predicted a nonzero clock-rate difference;
    the uncorrected clock exhibited that difference;
    engineers compensated that difference;
    the compensated residual became approximately zero.

    And your argument is that the final zero proves the difference never
    existed.

    We've gone around this circle enough times.

    You have even conceded that relativity made the correct quantitative
    clock-rate prediction. Your remaining escape is simply to decree that
    the corresponding measured rate difference was an "error" and that
    only the result after cancelling it counts.

    There is nothing left to calculate, explain, or debate.

    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12
    Maciej: "DISCARDED!"

    So be it.

    Goodbye Maciej.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:36:48 2026
    From Newsgroup: sci.math

    On 10/23/2026 1:33 PM, Python wrote:
    Maciej,

    The real, measured value is - 0.

    Yes.

    After compensation.

    Adjustment is THE KEY, DECISIVE
    factor here. Even such an idiot as
    you are has admitted.

    Now - your moronic prophet was too
    dumb to even notice that the factor
    exists and you're waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR IS
    NOT INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 11:43:49 2026
    From Newsgroup: sci.math

    Maciej,

    You have now pasted essentially the same paragraph yet again, after
    every point in it has already been answered repeatedly.

    There is nothing new here to reply to.

    As I said:

    Goodbye Maciej.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:50:27 2026
    From Newsgroup: sci.math

    On 10/23/2026 1:43 PM, Python wrote:
    Maciej,

    You have now pasted essentially the same paragraph yet again, after
    every point in it has already been answered repeatedly.

    I did.
    And you're still waving your arms and
    screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR THE
    IDIOT DIDN'T EVEN NOTICE IS NOT
    INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 11:51:25 2026
    From Newsgroup: sci.math

    Maciej,

    I did.

    Indeed.

    You explicitly acknowledge that you are repeating the same paragraph
    after the answer has already been given repeatedly.

    So there is nothing left to discuss.

    For the record, one last time:

    correction OFF:
    predicted: +446.5 |u 10^-12
    measured: +442.5 |u 10^-12

    correction ON:
    residual: approximately 0

    Your response to the first measurement is "clock error".

    Your response to the second is "REAL measurement".

    And your response to every explanation of the difference is to paste
    the same paragraph again.

    Fine.

    Readers have the numbers, the chronology, and your answer to them.

    Goodbye Maciej.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:53:02 2026
    From Newsgroup: sci.math

    On 10/23/2026 1:51 PM, Python wrote:
    Maciej,

    I did.

    Indeed.

    You explicitly acknowledge that you are repeating the same paragraph
    after the answer has already been given repeatedly.

    And you're still, repeatedly, waving your
    arms and screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR THE
    IDIOT DIDN'T EVEN NOTICE IS NOT
    INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Python@python@cccp.invalid to sci.physics.relativity,sci.math on Fri Oct 23 11:55:00 2026
    From Newsgroup: sci.math

    Maciej,

    Yes.

    That is now the fourth or fifth time you've pasted essentially the same paragraph.

    The numbers and chronology remain unchanged.

    You have nothing new to say, and neither do I.

    Goodbye Maciej.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Maciej_Wo=C5=BAniak?=@mlwozniak@wp.pl to sci.physics.relativity,sci.math on Fri Oct 23 13:56:57 2026
    From Newsgroup: sci.math

    On 10/23/2026 1:55 PM, Python wrote:
    Maciej,

    Yes.

    That is now the fourth or fifth time you've pasted essentially the same paragraph.

    Python,
    Yes.
    And you're still, repeatedly, waving your
    arms and screaming "LOOK!!!! A GREAT SUCCESS!!!
    THE PROPHECY WORKS PERFECTLY!!! AS
    LONG AS THE KEY, DECISIVE FACTOR THE
    IDIOT DIDN'T EVEN NOTICE IS NOT
    INVOLVED!!!"

    It's not, of course, that one could
    expect any better logic from a brainwashed
    fanatic idiot.

    --- Synchronet 3.22a-Linux NewsLink 1.2