Path: ...!3.eu.feeder.erje.net!feeder.erje.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!pasdenom.info!from-devjntp
Message-ID: <NCMZlHRuo1p_S6DXG_aN0gMczys@jntp>
JNTP-Route: news2.nemoweb.net
JNTP-DataType: Article
Subject: Re: Space-time interval (2)
References: <YqTjbAPdSf8P-veYFHQCI8eskLU@jntp> <327c4ebc77dc16239ac38f00b508451b@www.novabbs.com> <ZmtVAt4HhKe0jdT-a3px1duKdmw@jntp>
 <v9i8c5$bvnu$9@dont-email.me> <VOohu46_lYfs6YEQG8qZQKYepNw@jntp> <v9ia7k$bvnu$11@dont-email.me>
 <FxxcAtB-BaU4TzfE-6Txlbo_gEA@jntp> <v9kiq7$tput$1@dont-email.me> <EtDoDs0BPVkZJTF9Hcr7blKk9p0@jntp>
 <v9nfir$1e6i8$1@dont-email.me>
Newsgroups: sci.physics.relativity
JNTP-HashClient: FE9Hdp_qIw2qYnrBndbY5xoBimU
JNTP-ThreadID: L0IgA2CWtv7gPeDAAk57TJ-BbeQ
JNTP-Uri: http://news2.nemoweb.net/?DataID=NCMZlHRuo1p_S6DXG_aN0gMczys@jntp
User-Agent: Nemo/0.999a
JNTP-OriginServer: news2.nemoweb.net
Date: Fri, 16 Aug 24 12:38:05 +0000
Organization: Nemoweb
JNTP-Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36
Injection-Info: news2.nemoweb.net; posting-host="e8cbf2474b472b9bb79db3dccb6a856bc1d05409"; logging-data="2024-08-16T12:38:05Z/8988871"; posting-account="4@news2.nemoweb.net"; mail-complaints-to="julien.arlandis@gmail.com"
JNTP-ProtocolVersion: 0.21.1
JNTP-Server: PhpNemoServer/0.94.5
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-JNTP-JsonNewsGateway: 0.96
From:  Richard Hachel   <r.hachel@jesauspu.fr>
Bytes: 1956
Lines: 11

Le 16/08/2024 à 14:10, Mikko a écrit :
>>> 
>>> No, it does not. A watch may be set to show that time or another time and
>>> it shows as it was set.
>> 
>> That's not what I'm talking about.
> 
> Yes, you were. You said "each watch will lag behind the other".

If we do a type M synchronization as I explained in the previous post.

R.H.