Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.physics.relativity > #408960
| From | Odd Bodkin <bodkinodd@gmail.com> |
|---|---|
| Newsgroups | sci.physics.relativity |
| Subject | Re: Python's two frames, two points, and two clocks. |
| Date | 2017-02-12 15:15 -0600 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <o7qj9d$1ace$2@gioia.aioe.org> (permalink) |
| References | (13 earlier) <a34da5f7-f133-4923-bcb1-65d43f296654@googlegroups.com> <2535d370-44e1-488a-83c3-96aeabbc78c7@googlegroups.com> <fe28a799-881f-47fb-8310-3d40fac973b1@googlegroups.com> <o7hulo$1942$1@gioia.aioe.org> <8e3988ec-905c-42cb-9de3-e65d04d34bd6@googlegroups.com> |
On 2/9/2017 11:02 AM, Robert Winn wrote: > On Thursday, February 9, 2017 at 7:34:36 AM UTC-7, Odd Bodkin wrote: >> On 2/9/2017 7:09 AM, Robert Winn wrote: >>> You either show the proof of what you are saying, or I am going to say you have no proof. >> >> Robert, this is called being passive-aggressive. I'm sure you've heard >> the term before, probably in conversations about you and your personality. >> >> What you are saying is that you are going to believe what you want to >> believe, until someone comes to you and takes the trouble to convince >> you otherwise. This assumes, of course, that people care what you >> believe, which is unlikely. >> >> It is a baiting method that has the underlying motive of getting people >> to pay attention to you, rather than just leaving you alone which >> occasionally you do not like. If people invest time and effort in you, >> no matter how futile, then this is gratifying to you and great sport. It >> is even greater sport to you the more futile you make it. >> >> I think you can understand why this kind of interpersonal gamesmanship >> for your own gratification is only done in small doses by normal people. >> >> -- >> Odd Bodkin -- maker of fine toys, tools, tables > > Well, I have said this before, Odd Bodkin, and I will say it again. You are > not talking about relativity, you are talking about psychology, which does not > interest me at all. If you want to talk about relativity, you have to talk about > equations the way Gary Harnagel does. > On the contrary, Robert. To talk about relativity, you have to talk about experimental results, not equations. You don't know about the experimental results, and so all the talk about equations is a waste of time. The reason you don't look at experimental results is because of psychology. I think I'm pointing out that in general talking with you about relativity is a waste of time. -- Odd Bodkin -- maker of fine toys, tools, tables
Back to sci.physics.relativity | Previous | Next | Find similar | Unroll thread
Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-26 06:43 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 07:06 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-26 07:38 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 09:47 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2016-12-26 20:31 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-26 14:06 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2016-12-27 01:00 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-26 19:32 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2016-12-29 12:13 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-29 14:26 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2016-12-30 09:34 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2016-12-26 12:55 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-26 15:56 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2016-12-27 10:47 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-27 15:32 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-27 19:08 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-28 05:37 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-28 20:58 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-29 07:49 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-29 18:41 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-29 22:08 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-30 06:55 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-30 07:17 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-30 08:51 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-30 09:40 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-30 12:09 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2016-12-30 12:44 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-30 15:12 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-30 17:03 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-30 19:30 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-31 09:26 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-31 11:53 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-31 14:34 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-31 17:29 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-31 18:09 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2016-12-31 18:56 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-31 22:06 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-01 05:56 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-01 09:23 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-01 11:50 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-01 22:27 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-02 05:05 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-02 08:51 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-02 09:25 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-02 09:36 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-02 12:24 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-02 19:48 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-02 21:33 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-03 06:22 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-03 06:43 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-03 09:11 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-01 23:44 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-01 23:42 -0800
Natural imbecile Rober Winn hard at "work" "Dono," <sa_ge@comcast.net> - 2017-01-01 09:03 -0800
Re: Natural imbecile Rober Winn hard at "work" Robert Winn <rbwinn3@gmail.com> - 2017-01-01 09:27 -0800
Re: Natural imbecile Rober Winn hard at "work" "Dono," <sa_ge@comcast.net> - 2017-01-02 06:01 -0800
Re: Natural imbecile Rober Winn hard at "work" Robert Winn <rbwinn3@gmail.com> - 2017-01-02 08:51 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-29 08:03 -0800
Re: Python's two frames, two points, and two clocks. Demetrice Barren <teercere@tmerunin.tme> - 2016-12-30 03:28 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2016-12-29 22:11 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 14:01 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-03 12:15 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 15:45 -0600
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-03 14:11 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-03 14:30 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-03 14:47 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-03 19:09 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-03 19:31 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-04 14:33 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-04 16:19 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-04 18:24 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-05 09:58 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-05 13:56 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-05 15:43 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-06 04:21 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-06 04:35 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-06 04:59 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 07:13 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-06 22:42 -0800
Robert Winn continues to bask in his imbecility "Dono," <sa_ge@comcast.net> - 2017-01-07 12:11 -0800
Re: Robert Winn continues to bask in his imbecility Robert Winn <rbwinn3@gmail.com> - 2017-01-07 21:35 -0800
Re: Robert Winn continues to bask in his imbecility "Dono," <sa_ge@comcast.net> - 2017-01-08 08:41 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-07 13:33 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-08 07:34 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-08 11:48 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-08 20:29 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-08 21:11 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-08 21:46 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-08 21:59 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-08 22:20 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-08 22:46 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-09 06:27 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-09 15:42 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-09 08:33 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-09 19:20 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 06:29 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-10 07:05 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 07:58 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-10 12:02 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-10 10:52 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-10 11:01 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-10 12:10 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 12:12 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-10 13:24 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-10 13:40 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-10 15:37 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 23:26 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-11 04:01 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-11 04:13 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 06:22 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-11 06:38 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-11 06:40 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 07:47 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-11 08:00 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 09:49 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-11 10:15 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 10:58 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-11 18:01 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-11 11:47 -0800
Re: Python's two frames, two points, and two clocks. Ward Nusbaum <uqowm@msdmmsuus.org> - 2017-01-11 21:47 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 14:59 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 17:34 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 09:09 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-12 10:03 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 11:02 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-12 11:43 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 13:13 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-12 14:18 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 15:06 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-12 15:49 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 16:30 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-12 16:33 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 18:57 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-12 19:14 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 19:55 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-13 05:16 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 09:17 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-13 13:10 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 13:19 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-13 13:43 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 14:15 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 14:26 -0800
Re: Python's two frames, two points, and two clocks. Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-13 22:35 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 17:45 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 19:24 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 14:43 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 14:54 -0800
Re: Python's two frames, two points, and two clocks. Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-13 23:10 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 19:27 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-14 14:14 -0600
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 17:08 -0600
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-13 15:51 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 18:11 -0600
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-12 20:44 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-12 21:00 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 21:17 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 04:53 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 08:53 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 11:50 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 12:44 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-13 13:07 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 14:19 -0800
Re: Python's two frames, two points, and two clocks. Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-13 22:31 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 17:43 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-13 20:30 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 07:42 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-14 09:43 -0800
Re: Python's two frames, two points, and two clocks. Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-14 18:59 +0000
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-14 14:20 -0600
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-18 08:58 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2017-01-12 15:52 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-14 11:39 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2017-01-14 12:27 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 12:59 -0800
Re: Python's two frames, two points, and two clocks. Tom Roberts <tjroberts137@sbcglobal.net> - 2017-01-14 16:50 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 21:53 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 14:00 -0600
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2017-01-15 09:57 -0800
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2017-01-15 10:35 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 13:08 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-14 15:00 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 22:34 -0800
Imbecile Robert Winn fails basic algebra. "Dono," <sa_ge@comcast.net> - 2017-01-12 10:19 -0800
Re: Imbecile Robert Winn fails basic algebra. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 11:03 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 14:07 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 13:13 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 15:35 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 14:08 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 17:11 -0600
Re: Python's two frames, two points, and two clocks. alsor@interia.pl - 2017-01-14 10:12 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-11 16:47 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 10:24 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-11 21:00 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-12 10:31 -0800
imbecile rober winn perseveres "Dono," <sa_ge@comcast.net> - 2017-01-11 18:00 -0800
Re: imbecile rober winn perseveres Robert Winn <rbwinn3@gmail.com> - 2017-01-12 10:26 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-10 15:16 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-08 23:19 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-09 03:41 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-09 03:55 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-08 22:04 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-03 23:38 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-04 07:27 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-04 13:41 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-03 14:48 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 10:11 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-04 15:49 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-05 09:39 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-05 10:00 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 07:08 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-06 22:41 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-07 13:50 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-07 21:35 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-08 08:42 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-08 09:48 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 13:02 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-09 11:23 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 15:29 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-09 13:37 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-09 14:28 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 17:16 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 06:06 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-10 08:37 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 06:57 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-10 06:35 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 06:36 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-10 11:14 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-10 09:16 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 08:54 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 07:49 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 10:08 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-11 09:48 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 15:38 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-13 14:11 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 17:04 -0600
Cretin Rober Winn. "Dono," <sa_ge@comcast.net> - 2017-01-18 08:52 -0800
Re: Cretin Rober Winn. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 09:16 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 07:29 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-14 08:32 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 08:41 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-14 08:53 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-14 09:02 -0800
Re: Python's two frames, two points, and two clocks. paparios <paparios@gmail.com> - 2017-01-14 13:15 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-14 14:12 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-14 13:09 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 14:02 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-15 12:23 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-15 20:58 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-16 04:05 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-16 04:17 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-16 06:10 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-16 06:34 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 09:27 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-16 09:00 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 11:33 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-16 14:15 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-16 15:06 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-16 20:51 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-17 06:45 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-17 06:57 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-17 07:04 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-17 07:34 -0800
Re: Python's two frames, two points, and two clocks. "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-17 07:45 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-17 07:21 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-17 07:05 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-17 10:46 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-17 14:33 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-17 16:49 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-17 16:04 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-18 11:29 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 09:38 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-18 12:25 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-18 11:12 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 13:17 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-18 15:31 -0600
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-18 23:34 +0100
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-18 16:40 -0600
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-18 23:54 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 15:52 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-18 19:09 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 19:47 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-18 20:07 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 20:16 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-18 20:19 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 20:36 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-18 21:08 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 07:37 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-19 04:49 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 07:41 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-19 09:50 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 16:10 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-19 20:01 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 20:34 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 08:48 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 07:33 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 10:36 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 15:55 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-19 19:52 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 20:26 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-20 05:39 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-20 05:45 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 06:28 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-20 07:53 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 15:29 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-20 17:56 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-21 04:07 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 19:59 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 19:55 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-20 20:24 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 21:29 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-21 04:32 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-21 04:51 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-21 07:40 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-21 08:00 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-21 09:26 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-21 07:32 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-21 18:46 -0800
Re: Python's two frames, two points, and two clocks. Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-22 03:20 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-21 21:13 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-22 04:27 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-22 05:35 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-22 07:33 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-22 14:37 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-22 16:35 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-22 17:39 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-22 19:45 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-22 20:05 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-22 23:35 -0800
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-23 01:14 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 07:20 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-23 08:01 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 08:09 -0800
Re: Python's two frames, two points, and two clocks. Larisa Kull <looaiuoais@kesfgais.org> - 2017-01-23 04:11 +0000
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-22 23:37 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-23 03:36 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 07:21 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-23 08:22 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 09:39 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 11:44 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 10:07 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 12:26 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 11:18 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 13:51 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 13:47 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 16:56 -0600
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-23 21:44 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 13:49 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 12:46 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-23 11:44 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 13:14 -0600
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-23 18:38 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 19:41 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-24 04:22 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-24 07:44 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-24 08:27 -0800
Re: Python's two frames, two points, and two clocks. dancouriann@gmail.com - 2017-01-18 20:51 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 07:36 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 14:40 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-18 14:38 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-19 08:28 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 07:43 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-19 09:57 -0600
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-19 08:06 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-19 08:04 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 16:02 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-19 21:10 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-19 16:00 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-19 21:12 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-20 05:40 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 08:47 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 07:31 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-23 08:26 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 09:41 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 10:35 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 09:59 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 12:24 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 11:17 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 13:49 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-23 12:04 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 13:37 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-23 16:51 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-23 17:08 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-24 07:25 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-24 06:04 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-24 07:50 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-24 10:41 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-24 09:05 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 05:50 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 07:07 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 10:24 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 09:55 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-25 19:02 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 10:25 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-01-25 19:40 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 11:18 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 12:48 -0600
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 12:30 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 11:17 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 14:59 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-25 14:21 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 15:08 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 15:07 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 20:21 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-25 20:02 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-25 22:26 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-26 07:41 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-26 07:42 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-26 07:45 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-27 07:50 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-27 14:14 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-27 16:39 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-27 23:29 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-28 12:44 -0600
Re: Python's two frames, two points, and two clocks. mlwozniak@wp.pl - 2017-01-28 11:49 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-27 16:53 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-27 23:57 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-28 12:46 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-28 16:26 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-29 14:06 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-29 16:21 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-01-29 16:44 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-29 19:48 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-29 18:31 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 07:55 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 07:27 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 09:37 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-30 07:53 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 10:03 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 08:15 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 10:25 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 07:40 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 10:02 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 08:30 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 11:21 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 11:32 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-30 13:39 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-30 14:59 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-31 07:12 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-31 05:39 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-31 08:40 -0600
Re: Python's two frames, two points, and two clocks. kenseto <setoken@att.net> - 2017-01-31 11:42 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-31 07:39 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-31 10:47 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-31 09:41 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-31 11:48 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-31 11:02 -0800
Re: Python's two frames, two points, and two clocks. "Dono," <sa_ge@comcast.net> - 2017-01-31 11:15 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-01-31 11:31 -0800
The cretin Robert Winn perseveres "Dono," <sa_ge@comcast.net> - 2017-01-31 18:07 -0800
The cretin Robert Winn perseveres "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-31 18:15 -0800
Re: The cretin Robert Winn perseveres Robert Winn <rbwinn3@gmail.com> - 2017-02-01 22:26 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-02-01 03:20 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-01 22:45 -0800
Imbecile Robert Winn at work "Dono," <sa_ge@comcast.net> - 2017-02-06 11:05 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-01-31 14:27 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-01 22:16 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-02-02 08:59 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-03 20:07 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-04 04:42 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-04 10:43 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-02-04 19:49 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-04 11:40 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-02-04 20:52 +0100
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-04 12:26 -0800
Re: Python's two frames, two points, and two clocks. Python <python@python.invalid> - 2017-02-04 21:30 +0100
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-04 12:55 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-04 21:41 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-05 05:03 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 07:40 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-02-05 09:48 -0600
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 08:51 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-02-05 10:52 -0600
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-02-05 11:19 -0600
Re: Python's two frames, two points, and two clocks. benj <benj@nobody.net> - 2017-02-06 20:41 -0500
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 10:50 -0800
Re: Python's two frames, two points, and two clocks. Odd Bodkin <bodkinodd@gmail.com> - 2017-02-06 13:34 -0600
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-05 08:43 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 09:03 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 10:47 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-05 11:54 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-05 19:40 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-06 08:06 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-06 09:06 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-06 12:46 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-06 14:01 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-06 14:24 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-06 14:45 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-06 18:54 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-06 19:37 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-06 20:36 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-07 05:10 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-07 06:58 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-07 07:45 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-07 11:54 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-07 13:02 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-07 15:37 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-07 16:45 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-07 17:06 -0800
Re: Python's two frames, two points, and two clocks. Gary Harnagel <hitlong@yahoo.com> - 2017-02-07 17:41 -0800
Re: Python's two frames, two points, and two clocks. Robert Winn <rbwinn3@gmail.com> - 2017-02-07 22:29 -0800
(Thread has 578 articles, showing 500 — browse group in flat view)
csiph-web