Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.physics.relativity > #402686 > unrolled thread
| Started by | mlwozniak@wp.pl |
|---|---|
| First post | 2016-12-22 00:39 -0800 |
| Last post | 2017-01-05 06:16 -0800 |
| Articles | 20 on this page of 215 — 19 participants |
Back to article view | Back to sci.physics.relativity
Detecting time dilation mlwozniak@wp.pl - 2016-12-22 00:39 -0800
Re: Detecting time dilation Prokaryotic Caspase Homolog <prokaryotic.caspase.homolog@gmail.com> - 2016-12-22 02:05 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-22 02:52 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-22 05:58 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2016-12-22 09:34 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-22 10:10 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-24 06:44 -0800
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-24 06:57 -0800
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-25 05:55 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-25 07:43 -0800
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-26 11:08 -0800
utter cretin Jay Moseley insists "Dono," <sa_ge@comcast.net> - 2016-12-26 14:34 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-25 19:46 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 03:45 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 04:22 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 04:51 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 05:19 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 05:53 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 06:26 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 16:06 +0000
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-26 11:12 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-22 13:42 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-25 11:00 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-25 13:34 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-25 13:57 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 08:16 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 16:53 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-26 19:21 +0000
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 21:49 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 03:29 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 23:34 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-27 20:33 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 01:24 +0000
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 11:05 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-27 20:43 +0000
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:30 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-26 10:00 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 18:06 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 11:48 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 13:28 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 14:20 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-26 15:33 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 23:29 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-27 04:36 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 05:27 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-27 07:27 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-27 06:28 -0800
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-27 07:04 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 15:37 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 08:45 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 18:17 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 10:25 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-28 09:20 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-29 03:04 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 23:19 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-29 08:12 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 00:29 +0000
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-30 00:43 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 01:28 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-29 23:10 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-30 06:36 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-31 21:39 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-31 14:44 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 14:02 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-03 13:30 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 06:13 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 09:36 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 07:43 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 10:33 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:07 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:21 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:12 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:18 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 06:46 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:09 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:11 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 12:48 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:00 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:11 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:29 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:07 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:17 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 06:28 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:26 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:07 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-04 13:46 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:28 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-05 09:46 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:00 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:12 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:37 -0800
Re: Detecting time dilation Aubrey Primmer <myr@ejmr.info> - 2017-01-06 15:52 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 10:13 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 18:21 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-07 13:39 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-07 13:26 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-08 06:48 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 12:56 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-09 12:21 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 15:33 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-09 23:33 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-10 10:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 08:54 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-11 09:01 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 17:35 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 05:27 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-12 08:27 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 11:24 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 14:08 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-13 12:56 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 15:33 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-14 04:57 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-14 05:43 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-14 14:24 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 06:15 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 13:54 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 12:31 -0800
Re: Detecting time dilation Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-15 20:36 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 17:11 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-16 06:59 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 09:50 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-18 18:05 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-15 22:30 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-15 07:36 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-12 16:38 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-12 08:50 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 11:26 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-13 03:09 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-12 23:59 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-13 05:37 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-14 07:27 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-14 01:59 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-14 05:20 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-14 19:47 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 06:29 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-16 00:10 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-16 06:49 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 09:46 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-18 17:58 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 12:09 -0600
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 12:45 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-17 06:45 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-17 06:38 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-17 10:39 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-17 09:30 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-11 16:23 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-09 23:31 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-06 10:32 -0800
Re: Detecting time dilation Aubrey Primmer <myr@ejmr.info> - 2017-01-06 18:41 +0000
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-06 11:51 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-06 16:37 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 18:23 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-07 21:27 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-08 06:44 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-08 16:08 +0000
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 11:24 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 11:33 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:15 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 12:11 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:29 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-27 09:23 -0600
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 07:54 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 09:22 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 09:33 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 10:36 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:19 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 14:58 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-28 08:13 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-28 08:33 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 10:27 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-28 13:29 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 13:35 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-28 17:33 -0600
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2016-12-29 00:39 +0100
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2016-12-29 01:23 +0100
Re: Detecting time dilation RichD <r_delaney2001@yahoo.com> - 2017-01-05 09:48 -0800
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2017-01-05 21:28 +0100
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-28 17:27 -0600
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-28 15:42 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-29 07:50 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 13:58 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 06:10 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 09:39 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 07:54 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 10:36 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:05 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:13 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:30 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:14 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:24 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-05 06:30 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-05 10:11 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:00 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:11 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:36 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 23:13 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-27 13:48 -0800
Re: Detecting time dilation "Dono," <sa_ge@comcast.net> - 2017-01-03 13:34 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-27 12:55 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:37 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-29 15:09 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 10:46 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 11:20 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:08 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 12:43 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-26 08:53 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 17:25 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 09:56 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-26 19:34 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 14:23 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 13:40 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-28 14:31 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-05 06:16 -0800
Page 3 of 11 — ← Prev page 1 2 [3] 4 5 … 11 Next page →
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-26 14:20 -0800 |
| Message-ID | <d4087322-7083-4430-a920-1c37fbc71b76@googlegroups.com> |
| In reply to | #403047 |
W dniu poniedziałek, 26 grudnia 2016 22:28:53 UTC+1 użytkownik Ed Lake napisał: > On Monday, December 26, 2016 at 12:00:06 PM UTC-6, paparios wrote: > > > > > Check at GPS - when set accurately, clocks show no > > > > dilation:( > > > > > > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on earth every day due to the speed at which the satellites travel. The clocks on GPS satellites tick 45 microseconds FASTER than clocks on Earth every day due to the difference in gravitation due to the difference in distance from the center of the Earth. > > > > > > > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). What changes is the observation rates of those clocks, from the point of view of the GPS receiver. > > > > "The engineers who designed the GPS system included these relativistic effects Oh, someone wrote it!!! Must be the truth. > So, they do not make corrections daily. I was wrong about that. They knew before launching what time dilation corrections would be required, so they automated the correcting process. See, poor idiot your time dilation concept is very similiar to good, old, classical clock error. There is just one difference: time dilation is - clocks unsynchronize and still are proper. Clock error is - clocks unsynchronize and require correction. Correction of clocks is required - good bye, time dilation. Good bye, The Shit of Great Guru. > That is just a convoluted way of saying they BUILT IN the correction process to adjust for TIME DILATION. Do you know, how your guru defined time?
[toc] | [prev] | [next] | [standalone]
| From | paparios <paparios@gmail.com> |
|---|---|
| Date | 2016-12-26 15:33 -0800 |
| Message-ID | <a5fed790-dfb2-450e-8e55-6d37ba3ba470@googlegroups.com> |
| In reply to | #403047 |
El lunes, 26 de diciembre de 2016, 18:28:53 (UTC-3), Ed Lake escribió: > On Monday, December 26, 2016 at 12:00:06 PM UTC-6, paparios wrote: > > > > > Check at GPS - when set accurately, clocks show no > > > > dilation:( > > > > > > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on earth every day due to the speed at which the satellites travel. The clocks on GPS satellites tick 45 microseconds FASTER than clocks on Earth every day due to the difference in gravitation due to the difference in distance from the center of the Earth. > > > > > > > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). What changes is the observation rates of those clocks, from the point of view of the GPS receiver. > > > > "The engineers who designed the GPS system included these relativistic effects when they designed and deployed the system. For example, to counteract the General Relativistic effect once on orbit, they slowed down the ticking frequency of the atomic clocks before they were launched so that once they were in their proper orbit stations their clocks would appear to tick at the correct rate as compared to the reference atomic clocks at the GPS ground stations. Further, each GPS receiver has built into it a microcomputer that, in addition to performing the calculation of position using 3D trilateration, will also compute any additional special relativistic timing calculations required." > > source: http://www.astronomy.ohio-state.edu/~pogge/Ast162/Unit5/gps.html > > So, they do not make corrections daily. I was wrong about that. They knew before launching what time dilation corrections would be required, so they automated the correcting process. > > Either way, time dilation DOES affect the GPS satellite clocks. They just built in the correction process so that it does no harm. As I said, the clocks rates are not affected by relativity (if you were an astronaut at the GPS satellite you would measure the same clock rate as it was before lauching). In the text, the key phrase is: "so that once they were in their proper orbit stations their clocks would appear to tick at the correct rate as compared to the reference atomic clocks at the GPS ground stations". So you see that it is the observation (measure) at a different frame of reference (this case the GPS receiver) which is affected. This is just geometry.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-26 23:29 -0800 |
| Message-ID | <746330dc-11bc-477a-9fe5-659b6fa67581@googlegroups.com> |
| In reply to | #403055 |
W dniu wtorek, 27 grudnia 2016 00:34:00 UTC+1 użytkownik paparios napisał: > > As I said, the clocks rates are not affected by relativity (if you were an astronaut at the GPS satellite you would measure the same clock rate as it was before lauching). Your Shit has told you? Well, it has mistaken. It's not theory anymore, poor idiot. We can test it. An astronaut on a satellite will measure, that second counted by the satellite clock takes a different number of ticks than second counted by ground clocks - because reality is: the numbers are different.
[toc] | [prev] | [next] | [standalone]
| From | Gary Harnagel <hitlong@yahoo.com> |
|---|---|
| Date | 2016-12-27 04:36 -0800 |
| Message-ID | <593f30ae-e533-474a-8cd5-1d0072333b4f@googlegroups.com> |
| In reply to | #403067 |
On Tuesday, December 27, 2016 at 12:29:33 AM UTC-7, mlwo...@wp.pl wrote: > > An astronaut on a satellite will measure, that > second counted by the satellite clock takes > a different number of ticks than second counted > by ground clocks - because reality is: the numbers > are different. Of course they'd be different -- because they aren't the same clocks. The satellite clocks have been adjusted so they read the same as the ground clocks WHEN MEASURED ON THE GROUND, not in the satellite. Your attempt at obfuscation and deceit have been exposed, ridiculous troll.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-27 05:27 -0800 |
| Message-ID | <ba7bbd57-35e4-442e-83c1-7bfe1e53137e@googlegroups.com> |
| In reply to | #403077 |
W dniu wtorek, 27 grudnia 2016 13:36:31 UTC+1 użytkownik Gary Harnagel napisał: > On Tuesday, December 27, 2016 at 12:29:33 AM UTC-7, mlwo...@wp.pl wrote: > > > > An astronaut on a satellite will measure, that > > second counted by the satellite clock takes > > a different number of ticks than second counted > > by ground clocks - because reality is: the numbers > > are different. > > Of course they'd be different -- because they aren't the same clocks. Of course they are different. The reason doesn't matter. They are different, so observer will NOT measure they are equal. Though, of course, he obviously would do in a better world obeying your idiot guru.
[toc] | [prev] | [next] | [standalone]
| From | Gary Harnagel <hitlong@yahoo.com> |
|---|---|
| Date | 2016-12-27 07:27 -0800 |
| Message-ID | <9e14b8f9-377d-470c-8ff8-24692ad80f9d@googlegroups.com> |
| In reply to | #403081 |
On Tuesday, December 27, 2016 at 6:27:02 AM UTC-7, mlwo...@wp.pl wrote: > > [More mumbled insanities] Poor stupid programmer.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2016-12-27 06:28 -0800 |
| Message-ID | <16c972d3-4174-4a01-85ee-ab3c3c5b9832@googlegroups.com> |
| In reply to | #403034 |
On Monday, December 26, 2016 at 1:00:06 PM UTC-5, paparios wrote: > El lunes, 26 de diciembre de 2016, 13:17:01 (UTC-3), Ed Lake escribió: > > On Sunday, December 25, 2016 at 3:34:04 PM UTC-6, mlwo...@wp.pl wrote: > > > W dniu niedziela, 25 grudnia 2016 20:00:16 UTC+1 użytkownik Ed Lake napisał: > > > > All you need if you want to detect time dilation is two very accurate atomic clocks. > > > > > > Check at GPS - when set accurately, clocks show no > > > dilation:( > > > > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on earth every day due to the speed at which the satellites travel. The clocks on GPS satellites tick 45 microseconds FASTER than clocks on Earth every day due to the difference in gravitation due to the difference in distance from the center of the Earth. > > > > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). What changes is the observation rates of those clocks, from the point of view of the GPS receiver. This is incorrect. If the GPS second remain to have 9,192,631,770 periods of Cs 133 radiation as the ground clock second then the GPS will not work. The GPS receiver have soft correction and define the GPS second to have 9,192,631,774.4647 radiation periods of Cs 133 radiation. > > > As a result, every day the clocks on all 30 GPS satellites have to be adjusted by 38 microseconds (45 - 7 = 38) or the system would be worthless in a matter of days. > > > > Ed
[toc] | [prev] | [next] | [standalone]
| From | "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> |
|---|---|
| Date | 2016-12-27 07:04 -0800 |
| Message-ID | <dc9a0546-7d84-4026-bdad-bfd7df30a682@googlegroups.com> |
| In reply to | #403087 |
This is incorrect. If the GPS second remain to have 9,192,631,770 periods of Cs 133 radiation as the ground clock second then the GPS will not work. The GPS receiver have soft correction and define the GPS second to have 9,192,631,774.4647 radiation periods of Cs 133 radiation. Clocks & Meter sticks & Ages of twins.... Clocks & Meter sticks & Ages of twins.... Clocks & Meter sticks & Ages of twins.... Clocks & Meter sticks & Ages of twins.... Clocks & Meter sticks & Ages of twins.... Space time is a Heterodyne of c & G
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-27 15:37 +0000 |
| Message-ID | <o3u1r0$l5h$1@pcls7.std.com> |
| In reply to | #403087 |
kenseto <setoken@att.net> writes: >On Monday, December 26, 2016 at 1:00:06 PM UTC-5, paparios wrote: >> > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on >> > earth every day due to the speed at which the satellites travel. The >> > clocks on GPS satellites tick 45 microseconds FASTER than clocks on >> > Earth every day due to the difference in gravitation due to the >> > difference in distance from the center of the Earth. >> This is incorrect. GPS atomic clocks tick always at the same rate (the >> rate they had before the launching). What changes is the observation >> rates of those clocks, from the point of view of the GPS receiver. >This is incorrect. If the GPS second remain to have 9,192,631,770 >periods of Cs 133 radiation as the ground clock second then the GPS will >not work. The GPS receiver have soft correction and define the GPS second >to have 9,192,631,774.4647 radiation periods of Cs 133 radiation. Stupid Ken, you deliberately make the same stupid mistake over and over again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a local clock (proper time). To an observer on the satellite, the satellite's Cs clock is a local clock and to the observer, 9,192,631,770 Cs atom transitions is exactly 1 second (by definition). There is no "redefinition" of the second, the second cannot be redefined that way. What is true is that the divisor is set at 9,192,631,774.4647 transitions for the signal to be used by earth bound GPS receivers. An observer on the GPS would obviously notice that this is slightly longer than 1 second. This is because once the GR effects are taken into account, this signal becomes exactly 1 second as seen on Earth (not the GPS). That number exactly cancels the GR effects of gravity and motion of the satellite. Stupid Ken, I (and others) repeatedly tell you to go and learn how SR/GR actually work, and learn how the GPS actually works as well. Please do so.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-27 08:45 -0800 |
| Message-ID | <7ecfa381-8c95-4707-a867-f58709f6a085@googlegroups.com> |
| In reply to | #403099 |
W dniu wtorek, 27 grudnia 2016 16:37:08 UTC+1 użytkownik Michael Moroney napisał: > Stupid Ken, you deliberately make the same stupid mistake over and over > again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a A lie, as expected from relativistic trash. The second is DEFINED very differently.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-27 18:17 +0000 |
| Message-ID | <o3ub7s$gqs$1@pcls7.std.com> |
| In reply to | #403109 |
mlwozniak@wp.pl writes:
>> Stupid Ken, you deliberately make the same stupid mistake over and over
>> again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a
>A lie, as expected from relativistic trash.
>The second is DEFINED very differently.
The SI definition, as used by scientists, is: "The second is the duration of
9192631770 periods of the radiation corresponding to the transition between
the two hyperfine levels of the ground state of the caesium 133 atom."
Unquote.
But you are no scientist, so you go by Mickey Mouse's big hand or something.
Original Definition (Medieval): 1/86400 of a day.
Interim Definition (1956): 1/31556925.9747 of the tropical year for
1900 January 0 at 12 hours ephemeris time.
Current Definition (1967): The duration of 9192631770 periods of the
radiation corresponding to the transition between the two hyperfine
levels of the ground state of the caesium-133 atom.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-27 10:25 -0800 |
| Message-ID | <0d6ddd79-83e5-4a71-9565-94bbf86d4c6d@googlegroups.com> |
| In reply to | #403128 |
W dniu wtorek, 27 grudnia 2016 19:17:38 UTC+1 użytkownik Michael Moroney napisał: > mlwozniak@wp.pl writes: > > >> Stupid Ken, you deliberately make the same stupid mistake over and over > >> again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a > > >A lie, as expected from relativistic trash. > >The second is DEFINED very differently. > > The SI definition, as used by scientists, is Yes, your bunch of fanatics tries to redefine it to support the mad shit of your idiot guru. But no sane people use this definition and ever will. You can check it at GPS.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2016-12-28 09:20 -0800 |
| Message-ID | <9975f451-5601-4a8c-b65e-42ed3a64ee1c@googlegroups.com> |
| In reply to | #403099 |
On Tuesday, December 27, 2016 at 10:37:08 AM UTC-5, Michael Moroney wrote: > kenseto <setoken@att.net> writes: > > >On Monday, December 26, 2016 at 1:00:06 PM UTC-5, paparios wrote: > >> > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on > >> > earth every day due to the speed at which the satellites travel. The > >> > clocks on GPS satellites tick 45 microseconds FASTER than clocks on > >> > Earth every day due to the difference in gravitation due to the > >> > difference in distance from the center of the Earth. > > >> This is incorrect. GPS atomic clocks tick always at the same rate (the > >> rate they had before the launching). What changes is the observation > >> rates of those clocks, from the point of view of the GPS receiver. > > >This is incorrect. If the GPS second remain to have 9,192,631,770 > >periods of Cs 133 radiation as the ground clock second then the GPS will > >not work. The GPS receiver have soft correction and define the GPS second > >to have 9,192,631,774.4647 radiation periods of Cs 133 radiation. > > Stupid Ken, you deliberately make the same stupid mistake over and over > again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a > local clock (proper time). Moron a second of proper time at the GPS location does not correspond to a second of proper time on the ground. To correct this they redefine the GPS second to have 4.4647 more periods of Cs 133 radiation than the ground clock second. This makes the passage of a redefined GPS second corresponds to the passage of a standard ground clock second and thus making the GPS permenantly in synch with the ground clock in terms of absolute time. >ao an observer on the satellite, the > satellite's Cs clock is a local clock and to the observer, 9,192,631,770 > Cs atom transitions is exactly 1 second (by definition). There is no > "redefinition" of the second, the second cannot be redefined that way. > What is true is that the divisor is set at 9,192,631,774.4647 transitions > for the signal to be used by earth bound GPS receivers. An observer on > the GPS would obviously notice that this is slightly longer than 1 second. > This is because once the GR effects are taken into account, this signal > becomes exactly 1 second as seen on Earth (not the GPS). That number > exactly cancels the GR effects of gravity and motion of the satellite. > > Stupid Ken, I (and others) repeatedly tell you to go and learn how > SR/GR actually work, and learn how the GPS actually works as well. > Please do so.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-29 03:04 +0000 |
| Message-ID | <o41ug2$1e2$2@pcls7.std.com> |
| In reply to | #403211 |
kenseto <setoken@att.net> writes: >On Tuesday, December 27, 2016 at 10:37:08 AM UTC-5, Michael Moroney wrote: >> Stupid Ken, you deliberately make the same stupid mistake over and over >> again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a >> local clock (proper time). =20 >Moron a second of proper time at the GPS location does not correspond to a >second of proper time on the ground. Stupid Ken, if you say something like that, it must mean that you don't even know what "proper time" is. Are you making up your own definitions for standard science phrases again? Well stop it, it just make you look stupid. That's why everyone knows of you as Stupid Ken. Proper time is what a comoving clock shows. The second is DEFINED as 9,192,631,770 Cs atom transitions on a cesium clock used to measure proper time. DEFINED. That means you can't come along and say "No,..." because that is the DEFINITION of a second. An astronaut riding along with a GPS SV will see all clocks, and time dependent things with him working properly, with one second being 9,192,631,770 Cs atom transitions on the GPS clock. We on earth also see everything ticking at its proper rate, 9,192,631,770 Cs atom transitions being exactly one second (BY DEFINITION) of our local Cs clock. However the astronaut will see the earth clock tick slow (taking 9,192,631,774.4647 Cs clock ticks on his Cs clock), while we on earth see the SV's clock tick fast. This does NOT mean any problem because neither measurement is proper time! It's just like a meter stick, it has to be stationary for it to be a meter. A high speed meter stick will be seen as short by us, while our meter stick will be seen as short by someone co-moving with the high speed meter stick. Does that mean "they redefine the high speed meter to have 1/gamma times the length of the stationary meter"? NO! That's because it doesn't meet the proper criteria for use as a reference. Now you (should!) know why your statement "they redefine the GPS second to have 4.4647 more periods of Cs 133 radiation than the ground clock second" is so STOOOOPID! So when are you going to actually learn about SR/GR for once?
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-28 23:19 -0800 |
| Message-ID | <89df5945-2e41-4c5d-abf1-d9b1a46c2923@googlegroups.com> |
| In reply to | #403238 |
W dniu czwartek, 29 grudnia 2016 04:04:38 UTC+1 użytkownik Michael Moroney napisał: > The second is DEFINED as > 9,192,631,770 Cs atom transitions on a cesium clock used to measure > proper time. DEFINED. That means you can't come along and say "No,..." > because that is the DEFINITION of a second. A lie, as expected from fanatic trash. The second is DEFINED very differently. > An astronaut riding along with a GPS SV will see all clocks, and time > dependent things with him working properly, with one second being > 9,192,631,770 Cs atom transitions on the GPS clock. And another lie, of course. One second counted by GPS clock has a different number of Cs transitions. It was discussed here many times and anyone can check it on real GPS.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2016-12-29 08:12 -0800 |
| Message-ID | <72168a3b-329c-4995-90a9-e484eabec47d@googlegroups.com> |
| In reply to | #403238 |
On Wednesday, December 28, 2016 at 10:04:38 PM UTC-5, Michael Moroney wrote: > kenseto <setoken@att.net> writes: > > >On Tuesday, December 27, 2016 at 10:37:08 AM UTC-5, Michael Moroney wrote: > > >> Stupid Ken, you deliberately make the same stupid mistake over and over > >> again. The second is DEFINED as 9,192,631,770 Cs atom transitions on a > >> local clock (proper time). =20 > > >Moron a second of proper time at the GPS location does not correspond to a > >second of proper time on the ground. > > Stupid Ken, if you say something like that, it must mean that you don't > even know what "proper time" is. Hey moron....it is you who don't know what proper time is. A proper second on an "A" clock is a second at the location of that clock and a proper second on a "B" clock is a second at the location of that clock. The relationship between the A clock and B clock according to SR and LET math are as follows: "A" predicts that "B's" proper second is worth: (gamma proper second on his "B" clock). "B" predicts that "A's" proper second is worth: (gamma proper second on his "B" clock). BTW the above SR and LET predictions are not completely fit observations. In real life, either A's prediction is wrong or B's prediction is wrong Gee you are so fucking stupid--no wonder your name is Moron-y. >Are you making up your own definitions > for standard science phrases again? Well stop it, it just make you look > stupid. That's why everyone knows of you as Stupid Ken. > > Proper time is what a comoving clock shows. The second is DEFINED as > 9,192,631,770 Cs atom transitions on a cesium clock used to measure > proper time. DEFINED. That means you can't come along and say "No,..." > because that is the DEFINITION of a second. > > An astronaut riding along with a GPS SV will see all clocks, and time > dependent things with him working properly, with one second being > 9,192,631,770 Cs atom transitions on the GPS clock. We on earth also see > everything ticking at its proper rate, 9,192,631,770 Cs atom transitions > being exactly one second (BY DEFINITION) of our local Cs clock. However > the astronaut will see the earth clock tick slow (taking > 9,192,631,774.4647 Cs clock ticks on his Cs clock), while we on earth see > the SV's clock tick fast. This does NOT mean any problem because neither > measurement is proper time! It's just like a meter stick, it has to be > stationary for it to be a meter. A high speed meter stick will be seen as > short by us, while our meter stick will be seen as short by someone > co-moving with the high speed meter stick. Does that mean "they redefine > the high speed meter to have 1/gamma times the length of the stationary > meter"? NO! That's because it doesn't meet the proper criteria for use as > a reference. Now you (should!) know why your statement "they redefine the > GPS second to have 4.4647 more periods of Cs 133 radiation than the ground > clock second" is so STOOOOPID! > > So when are you going to actually learn about SR/GR for once?
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-30 00:29 +0000 |
| Message-ID | <o449pd$3rh$1@pcls7.std.com> |
| In reply to | #403294 |
kenseto <setoken@att.net> writes: >On Wednesday, December 28, 2016 at 10:04:38 PM UTC-5, Michael Moroney wrote: >> >Moron a second of proper time at the GPS location does not correspond to a >> >second of proper time on the ground. >> Stupid Ken, if you say something like that, it must mean that you don't >> even know what "proper time" is. =20 >Hey moron....it is you who don't know what proper time is. Stupid Ken, I am using the definition used by science. If you disagree, it is because you are wrong. >A proper second on an "A" clock is a second at the location of that clock >and a proper second on a "B" clock is a second at the location of that >clock. The relationship between the A clock and B clock according to SR >and LET math are as follows: >"A" predicts Stupid Ken, nobody cares what any fortune teller predicts. What matters is what A and B actually measure. > that "B's" proper second is worth: (gamma proper second on his "B" clock). But B's clock does not measure proper time for A, since B's clock is not co-moving with A. Plus your lack of knowledge of what proper time is is evident here, since it is meaningless for A to talk about B's proper second. >"B" predicts Again, we care what B measures, not if B is a good fortune teller. > that "A's" proper second is worth: (gamma proper second on his "B" clock). A's clock does not measure proper time for B, since A's clock is not co-moving with B. >BTW the above SR and LET predictions are not completely fit observations. Wrong, Stupid Ken. No prediction of SR has ever been contradicted, in SR's realm of applicibility. Never. > In real life, either A's prediction is wrong or B's prediction is wrong No, Stupid Ken. What A and B measure (not predict) are not the same thing. In one case, two measurements from Clock A1 are compared to Clocks B1 and B2. In the other case, two measurements from clock B1 are compared to Clocks A1 and A2. >> So when are you going to actually learn about SR/GR for once? We're waiting.....
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-30 00:43 +0000 |
| Message-ID | <o44aj5$bv3$1@gioia.aioe.org> |
| In reply to | #403405 |
Michael Moroney wrote: >>Hey moron....it is you who don't know what proper time is. > > Stupid Ken, I am using the definition used by science. If you disagree, > it is because you are wrong. Only morons uses definitions when they are dealing with stuff in Physics. These wanna be scientists, dont even know what Physics stands for. They are believing that Physics is a branch of something called Science. Unbelievable stupid thing to do. Physics is much more larger and fundamental than Science, or Alchemy, for that matter.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-30 01:28 +0000 |
| Message-ID | <o44d7l$n4m$3@pcls7.std.com> |
| In reply to | #403408 |
The nymshifting troll, posting as Demetrice Barren <teercere@tmerunin.tme> writes: >Only morons uses definitions when they are dealing with stuff in Physics. >These wanna be scientists, dont even know what Physics stands for. They >are believing that Physics is a branch of something called Science. >Unbelievable stupid thing to do. Physics is much more larger and >fundamental than Science, or Alchemy, for that matter. Now you're just babbling, nymshifter.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-29 23:10 -0800 |
| Message-ID | <64c710a2-9d02-4a72-afb8-d2462c522473@googlegroups.com> |
| In reply to | #403405 |
W dniu piątek, 30 grudnia 2016 01:29:37 UTC+1 użytkownik Michael Moroney napisał: > kenseto <setoken@att.net> writes: > > >On Wednesday, December 28, 2016 at 10:04:38 PM UTC-5, Michael Moroney wrote: > > >> >Moron a second of proper time at the GPS location does not correspond to a > >> >second of proper time on the ground. > > >> Stupid Ken, if you say something like that, it must mean that you don't > >> even know what "proper time" is. =20 > > >Hey moron....it is you who don't know what proper time is. > > Stupid Ken, I am using the definition used by science. If you disagree, it > is because you are wrong. Stupid Michael, he is using the definition used by more than 7000 000 000 real people. if you disagree, it is because you are wrong.
[toc] | [prev] | [next] | [standalone]
Page 3 of 11 — ← Prev page 1 2 [3] 4 5 … 11 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web