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 <8oeOO24dBPnEyI9KFEVYhR4Qarg@jntp>
Deutsch   English   Français   Italiano  
<8oeOO24dBPnEyI9KFEVYhR4Qarg@jntp>

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

Path: ...!3.eu.feeder.erje.net!feeder.erje.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!pasdenom.info!from-devjntp
Message-ID: <8oeOO24dBPnEyI9KFEVYhR4Qarg@jntp>
JNTP-Route: news2.nemoweb.net
JNTP-DataType: Article
Subject: Re: [SR and synchronization] Cognitive Dissonances and Mental Blockage
References: <v9q6eu$1tlm9$1@dont-email.me> <liduroFtbroU2@mid.individual.net> <v9sh1e$2apq2$3@dont-email.me>
 <lig7svF8jpgU10@mid.individual.net> <v9vfe6$2qll6$10@dont-email.me> <liiprgFlcbgU3@mid.individual.net>
Newsgroups: sci.physics.relativity
JNTP-HashClient: WyzWHYD17aa6FnxwtZU8ANfBaHk
JNTP-ThreadID: v9q6eu$1tlm9$1@dont-email.me
JNTP-Uri: http://news2.nemoweb.net/?DataID=8oeOO24dBPnEyI9KFEVYhR4Qarg@jntp
User-Agent: Nemo/0.999a
JNTP-OriginServer: news2.nemoweb.net
Date: Tue, 20 Aug 24 09:38:03 +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-20T09:38:03Z/8993569"; 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: 3197
Lines: 57

Le 20/08/2024 à 08:02, Thomas Heger a écrit :
> Am Montag000019, 19.08.2024 um 14:56 schrieb Python:

> I take as example two spaceships in 1 lightseconds distance, which are 
> called A and B.

 AB = 1 lightsecond

> Both have a HUGE clock strapped to that spaceship and use a VERY HUGE 
> telescope to read the clock of the other ship.
> 
> 
> Now clock A shows 12 o'clock and zero seconds.

 "Now" for A. 

> Ship B reads this at time 12 o'clock plus 1 second,

 Si sa montre est synchronisée en convention Eisntein.

> but turns the own 
> clock (showing 12 o'clock plus one seconds) back by one second.

 Dans ce cas, B est parfaitement synchronisé sur A, c'est à dire que B 
"vit" exactement dans la
même simultanéité que A, dans le même instant présent que B.

 C'était vrai au départ, et ça l'est encore plus sur les horloges. 

> Now the observer of ship A reads the clock from ship B and reads 12 
> o'clock plus zero seconds, while the own clock shows 12 o'clock plus one 
> seconds.

 No!

 J'ai reculé ma montre B d'une seconde.

 A me voyait déjà, lui, avec une seconde de retard. 

 Il me voit maintenant avec deux secondes de retard. 
> 
> This is regarded as an error and the own clocks as being ahead, hence it 
> was turned back to 12 o'clock plus zero seconds.
> 
> This is seen from ship B, where the own clock shows actually 12 o'clock 
> plus one second. This is corrected by adjustment of one second, by which 
> that clock is turned backwards.
> 
> This could go on forever, while both clocks would stand still.
> 
> But certainly this is not what you would call 'synchronization'.
> 
> 
> TH
> 
> ...