Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <a610865812a2359182345fca40704d24@www.novabbs.com>
Deutsch   English   Français   Italiano  
<a610865812a2359182345fca40704d24@www.novabbs.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: hitlong@yahoo.com (gharnagel)
Newsgroups: sci.physics.relativity
Subject: Re: Space-time interval (2)
Date: Wed, 14 Aug 2024 14:39:55 +0000
Organization: novaBBS
Message-ID: <a610865812a2359182345fca40704d24@www.novabbs.com>
References: <YqTjbAPdSf8P-veYFHQCI8eskLU@jntp> <jBxUcP6BzIhx3lL1WyQctHmm7jo@jntp> <v9g6ij$3vsfg$1@dont-email.me> <AVa827R_LOez7mc5Ad3CT6GyhiA@jntp> <327c4ebc77dc16239ac38f00b508451b@www.novabbs.com> <17eb7db913381cc9$330199$505029$c2365abb@news.newsdemon.com> <ZmtVAt4HhKe0jdT-a3px1duKdmw@jntp> <v9i8c5$bvnu$9@dont-email.me> <VOohu46_lYfs6YEQG8qZQKYepNw@jntp> <v9ia7k$bvnu$11@dont-email.me> <FxxcAtB-BaU4TzfE-6Txlbo_gEA@jntp>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="2558956"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="p+/k+WRPC4XqxRx3JUZcWF5fRnK/u/hzv6aL21GRPZM";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: 47dad9ee83da8658a9a980eb24d2d25075d9b155
X-Rslight-Site: $2y$10$7uitKS39IEP0Py9tY3QjS.tFCH0bSf3elFDHiHCX3Enp3sB1P01eS
Bytes: 4521
Lines: 70

On Wed, 14 Aug 2024 13:24:17 +0000, Richard Hachel wrote:
>
> Le 14/08/2024 à 15:08, Python a écrit :
> >
> > Clocks are physical devices (except in Wozniak's mind). They are not
> > synchronized by imaginary devices on imaginary spatial dimensions.
> >
> > They are built in order to have the same rate (inside an acceptable
> > narrow interval) to begin with, then drifted according to what
> > General Relativity predict in order to stay in synch in ECI
> > frame (despite what demented Wozniak pretends).
> >
> > These are engineering tasks, not the stupid mythomaniac fantasies of
> > a histrionic senile country doctor.
>
> But you're mixing everything up.
>
> That's not what I'm talking about, I'm talking about the initial
> synchronization. At some point you have to synchronize all the watches
> in all the capitals with each other.
> However, this is by nature impossible.

“There is no point in using the word 'impossible' to describe something
that has clearly happened.” – Douglas Adams

> The notion of universal anisochrony means that each watch will lag
> behind the other with an anisochrony Et=x/c, a reciprocal phenomenon
> that will affect all the watches in the universe.

There is no such thing as "universal anisochrony": it is a false notion.
You're conflating time dilation (a real phenomenon) with something else.

> So, to start the watches at t=0, you'll need a point in the universe
> placed at an equal distance from all the others, and only an abstract
> point placed in an imaginary, perpendicular dimension, at an equal
> distance from all the points in the local universe will be able to do
> this.

Not necessary, but you're going overboard in complexity.  NO ONE wants
to synchronize watches over the whole universe!  Pick a reasonable goal.

Watches remotely located but at rest wrt each other can certainly be
synchronized by Einstein synchronization.  No need to have a source
halfway between the two clocks (although that works, too (if you know
that the distance between the source and each clock is exactly the same,
but you have to use the elements of ES to determine that).

> It's not hard to understand.
> Now you are talking about something else, that is to say the second
> particularity which is no longer anisochrony, but the relativity of the
> internal chronotropy of watches, in the sense that time passes less
> quickly at the level of the satellite than at the level of a terrestrial
> clock, and that the chronotropic shift must be regularly reestablished.
>
> R.H.

Actually, time passes MORE quickly at the satellite.  "Chronotropy" is
a canard.  The rate of the satellite clock is set to run slow so that
it is observed to run at the proper rate on the earth.  The reason why
the satellite must be updated is because (1) the satellite is not in an
exactly circular orbit and (2) the earth does not have a uniform
density.

Someone (I'm not naming any names) needs to do some studying.

“Education isn’t something you can finish.” – Isaac Asimov

“A person who won’t read has no advantage over one who can’t read.”
– Mark Twain

https://en.wikipedia.org/wiki/Einstein_synchronisation