T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
On 8/13/23 10:06 PM, jillery wrote:
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Try digreig@gmail.com.
On Mon, 14 Aug 2023 06:06:57 -0700, John HarshmanBeagle is apparently down. Unless DIG forwards mail, he may be effectively unreachable.
<john.h...@gmail.com> wrote:
On 8/13/23 10:06 PM, jillery wrote:
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Try dig...@gmail.com.I have, as well as several other email addresses DIG has used. He has
never replied to any of my emails.
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
On Monday, August 14, 2023 at 1:06:50 AM UTC-4, jillery wrote:
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Thanks for setting this thread up, jillery. It gave us in the USA early advance
warning (1:06 am, EDT). As of now, the downtime is past the 27 hour mark.
I have often recommended to DIG that he use sci.bio.paleontology to
let us know that he is aware that Beagle is down and to give us
periodic updates [one a day is enough, IMO] on how soon he expects
it to be back up.
Alas, the last time I got any feedback from DIG was early in 2011.
In particular, he seems oblivious to these recommendations.
Peter Nyikos
On 8/14/23 16:05, Peter Nyikos wrote:
On Monday, August 14, 2023 at 1:06:50 AM UTC-4, jillery wrote:
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Thanks for setting this thread up, jillery. It gave us in the USA early advance
warning (1:06 am, EDT). As of now, the downtime is past the 27 hour mark.
I have often recommended to DIG that he use sci.bio.paleontology to
let us know that he is aware that Beagle is down and to give us
periodic updates [one a day is enough, IMO] on how soon he expects
it to be back up.
Alas, the last time I got any feedback from DIG was early in 2011.
In particular, he seems oblivious to these recommendations.
Peter Nyikos
what is dig?
On Monday, August 14, 2023 at 7:41:04?AM UTC-7, jillery wrote:
On Mon, 14 Aug 2023 06:06:57 -0700, John HarshmanBeagle is apparently down. Unless DIG forwards mail, he may be effectively unreachable.
<john.h...@gmail.com> wrote:
On 8/13/23 10:06 PM, jillery wrote:I have, as well as several other email addresses DIG has used. He has
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Try dig...@gmail.com.
never replied to any of my emails.
On Friday, November 4, 2022 at 2:30:16 PM UTC-7, 69jp...@gmail.com wrote:**********************************
On Thu, 3 Nov 2022 13:24:47 -0700 (PDT), erik simpson
<eastsi...@gmail.com> wrote:
DIG is aware of the problem. SBP doesn't need TOs infamous collection of nutters and trolls. For that matter,So you have a direct connect to DIG. I understand why you don't share
neither does TO need them, but there they are. Unfortunately, both groups are nearly dead in any
event.
it, but that you or someone like you does affirms my reasons for
posting my OP to SBP.
DIG posted a couple of non-English texts to T.O. However, whatever he
did to do so has not made T.O. work for mere mortals. I ask you to
inform him of that fact.
It's not for me to publish anyone else's information. I'm sure he's aware of the fact that
it's still down. As the good Lawyer has pointed out, things have changed greatly over the
years when someone could trip over the power cord and bring down a server. Mostly, the result
is more reliable systems overall, at the expense of much greater interconnectivity, with lots of
possible failure points. Security issues have also multiplied, although I can't see what implications
that has for archaic gab groups. I'll bet it's back up sooner rather than later. If DIG gets fed up, who
knows?
On Mon, 14 Aug 2023 08:53:23 -0700 (PDT), erik simpsonOf course not. I've written to him, but I've received no answer. He's not obligated to
<eastsi...@gmail.com> wrote:
On Monday, August 14, 2023 at 7:41:04?AM UTC-7, jillery wrote:Use of .gmail.com moots problems with using email addys that route
On Mon, 14 Aug 2023 06:06:57 -0700, John HarshmanBeagle is apparently down. Unless DIG forwards mail, he may be effectively unreachable.
<john.h...@gmail.com> wrote:
On 8/13/23 10:06 PM, jillery wrote:I have, as well as several other email addresses DIG has used. He has
T.O. may require DIG's attention. The last post to T.O. was over 12
hours ago.
Try dig...@gmail.com.
never replied to any of my emails.
thru Beagle.
The last time this happened, you wrote:
*********************************
Newsgroups: sci.bio.paleontology
Date: Fri, 4 Nov 2022 15:44:20 -0700 (PDT)
Message-ID: <12b0eaab-f47e-4aa1...@googlegroups.com>
Subject: Re: Beagle down again
From: erik simpson <eastsi...@gmail.com>
On Friday, November 4, 2022 at 2:30:16 PM UTC-7, 69jp...@gmail.com wrote: >> On Thu, 3 Nov 2022 13:24:47 -0700 (PDT), erik simpson
<eastsi...@gmail.com> wrote:
DIG is aware of the problem. SBP doesn't need TOs infamous collection of nutters and trolls. For that matter,So you have a direct connect to DIG. I understand why you don't share
neither does TO need them, but there they are. Unfortunately, both groups are nearly dead in any
event.
it, but that you or someone like you does affirms my reasons for
posting my OP to SBP.
DIG posted a couple of non-English texts to T.O. However, whatever he
did to do so has not made T.O. work for mere mortals. I ask you to
inform him of that fact.
It's not for me to publish anyone else's information. I'm sure he's aware of the fact that**********************************
it's still down. As the good Lawyer has pointed out, things have changed greatly over the
years when someone could trip over the power cord and bring down a server. Mostly, the result
is more reliable systems overall, at the expense of much greater interconnectivity, with lots of
possible failure points. Security issues have also multiplied, although I can't see what implications
that has for archaic gab groups. I'll bet it's back up sooner rather than later. If DIG gets fed up, who
knows?
It's been over 60 hours since the last post to T.O. History and
recent activity shows T.O. nutters and trolls migrate to SPB whenever
T.O. goes down. As someone who claims a direct connection to DIG, are
you willing to stand idle and DNR T.O.?
I've written to [DIG] but I've received no answer. He's not obligated to
me in any way, just as I'm not obligated to TO.
On Thursday, November 3, 2022 at 3:14:36 PM UTC-4, Lawyer Daggett wrote:
...
The fix to getting talk.origins up again will likely be simple once the moderator knows it needs to
be done and has time to log in and restart things. Of course weirdness can occur if some admin
blocks beagle from sending or receiving mail because of some confusion, or some automatic
software update overwrites a parameter that needs to be custom set. But the main issue is that
the moderator works for free in his spare time and he has a job and a life that takes precedent,
or at least should.
I comment on my own witty perspicacity in anticipating the sort of error that occurred. It was a block
on sending/receiving mail because of an update in a global list of spam sites, so I was, shall we
say, half right. I thus proudly accept the title of Half Wit and retire from this group.
On Wednesday, August 16, 2023 at 1:28:44 AM UTC-4, erik simpson wrote:
I've written to [DIG] but I've received no answer. He's not obligated to
me in any way, just as I'm not obligated to TO.
As jillery pointed out, it's been over 60 hours [now over 70] since Beagle's been down.
I thought the following exchange from an earlier downtime, and its aftermath, might help relieve the tension some of us might be feeling.
On Sunday, November 6, 2022 at 12:33:45 PM UTC-5, Lawyer Daggett wrote:
On Thursday, November 3, 2022 at 3:14:36 PM UTC-4, Lawyer Daggett wrote:
...
The fix to getting talk.origins up again will likely be simple once the
moderator knows it needs to
be done and has time to log in and restart things. Of course weirdness
can occur if some admin
blocks beagle from sending or receiving mail because of some confusion,
or some automatic
software update overwrites a parameter that
needs to be custom set. But the main issue is that
the moderator works for free in his spare time and he has a job and a
life that takes precedent,
or at least should.
I comment on my own witty perspicacity in anticipating the sort of error
that occurred. It was a block
on sending/receiving mail because of an update in a global list of spam
sites, so I was, shall we
say, half right. I thus proudly accept the title of Half Wit and retire from this group.
At first I thought you were imitating Hemidactylus ("Our presence does
much to improve the place")
or jillery ("...my devastating retorts"), but you wound up being more modest than them.
To give credit where credit is due, the rest of us were stumbling blindly in the dark,
while, as they say,
"In the land of the blind, the one-eyed man is king."
But don't let it go to your head. You are king of the t.o. exiles concerned about when
and how Beagle would be back. That's a subset of all the t.o. exiles, and
the others were off
in their own virtual land.
Back to the rough and tumble,
Peter Nyikos
================================ end of post
archived at https://groups.google.com/g/sci.bio.paleontology/c/piprYPdW6qg/m/4AJn2EISAgAJ Re: Beagle down again
Nov 8, 2022, 7:23:54 PM
With "rough and tumble" I was referring to t.o. being back up,
and the fact that our exchanges here in s.b.p. had been comparatively good-natured, like the post I've shared with y'all just now.
Peter Nyikos
Peter Nyikos <peter2nyikos@gmail.com> wrote:
On Wednesday, August 16, 2023 at 1:28:44 AM UTC-4, erik simpson wrote:DIG will get to it when he gets to it.
I've written to [DIG] but I've received no answer. He's not obligated to >>> me in any way, just as I'm not obligated to TO.
On Wednesday, August 16, 2023 at 1:28:44?AM UTC-4, erik simpson wrote:
I've written to [DIG] but I've received no answer. He's not obligated to
me in any way, just as I'm not obligated to TO.
As jillery pointed out, it's been over 60 hours [now over 70] since Beagle's been down.
I thought the following exchange from an earlier downtime, and its aftermath, >might help relieve the tension some of us might be feeling.
On Sunday, November 6, 2022 at 12:33:45 PM UTC-5, Lawyer Daggett wrote:
On Thursday, November 3, 2022 at 3:14:36 PM UTC-4, Lawyer Daggett wrote:
...
The fix to getting talk.origins up again will likely be simple once the moderator knows it needs to
be done and has time to log in and restart things. Of course weirdness can occur if some admin
blocks beagle from sending or receiving mail because of some confusion, or some automatic
software update overwrites a parameter that needs to be custom set. But the main issue is that
the moderator works for free in his spare time and he has a job and a life that takes precedent,
or at least should.
I comment on my own witty perspicacity in anticipating the sort of error that occurred. It was a block
on sending/receiving mail because of an update in a global list of spam sites, so I was, shall we
say, half right. I thus proudly accept the title of Half Wit and retire from this group.
At first I thought you were imitating Hemidactylus ("Our presence does much to improve the place")
or jillery ("...my devastating retorts"), but you wound up being more modest than them.
To give credit where credit is due, the rest of us were stumbling blindly in the dark,
while, as they say,
"In the land of the blind, the one-eyed man is king."
But don't let it go to your head. You are king of the t.o. exiles concerned about when
and how Beagle would be back. That's a subset of all the t.o. exiles, and the others were off
in their own virtual land.
Back to the rough and tumble,
Peter Nyikos
================================ end of post
archived at >https://groups.google.com/g/sci.bio.paleontology/c/piprYPdW6qg/m/4AJn2EISAgAJ >Re: Beagle down again
Nov 8, 2022, 7:23:54?PM
With "rough and tumble" I was referring to t.o. being back up,
and the fact that our exchanges here in s.b.p. had been comparatively >good-natured, like the post I've shared with y'all just now.
On Wed, 16 Aug 2023 05:19:00 -0700 (PDT), Peter Nyikos
<peter2...@gmail.com> posted yet another self-parody:
On Wednesday, August 16, 2023 at 1:28:44?AM UTC-4, erik simpson wrote:
And nobody even implied any such obligations.I've written to [DIG] but I've received no answer. He's not obligated to >> me in any way, just as I'm not obligated to TO.
As jillery pointed out, it's been over 60 hours [now over 70] since Beagle's been down.
I thought the following exchange from an earlier downtime, and its aftermath,
might help relieve the tension some of us might be feeling.
On Sunday, November 6, 2022 at 12:33:45 PM UTC-5, Lawyer Daggett wrote:
On Thursday, November 3, 2022 at 3:14:36 PM UTC-4, Lawyer Daggett wrote: >> ...
The fix to getting talk.origins up again will likely be simple once the moderator knows it needs to
be done and has time to log in and restart things. Of course weirdness can occur if some admin
blocks beagle from sending or receiving mail because of some confusion, or some automatic
software update overwrites a parameter that needs to be custom set. But the main issue is that
the moderator works for free in his spare time and he has a job and a life that takes precedent,
or at least should.
I comment on my own witty perspicacity in anticipating the sort of error that occurred. It was a block
on sending/receiving mail because of an update in a global list of spam sites, so I was, shall we
say, half right. I thus proudly accept the title of Half Wit and retire from this group.
At first I thought you were imitating Hemidactylus ("Our presence does much to improve the place")It's remarkable how PeeWee Peter repeats the same stupid lies about
or jillery ("...my devastating retorts"), but you wound up being more modest than them.
jillery, no matter how many times he's proved wrong.
To give credit where credit is due, the rest of us were stumbling blindly in the dark,
while, as they say,
"In the land of the blind, the one-eyed man is king."
But don't let it go to your head. You are king of the t.o. exiles concerned about when
and how Beagle would be back. That's a subset of all the t.o. exiles, and the others were off
in their own virtual land.
Back to the rough and tumble,
I've no idea how you got that impression. I simply stated what I did and what the results were.Peter Nyikos
================================ end of post
archived at >https://groups.google.com/g/sci.bio.paleontology/c/piprYPdW6qg/m/4AJn2EISAgAJ
Re: Beagle down again
Nov 8, 2022, 7:23:54?PM
With "rough and tumble" I was referring to t.o. being back up,Apparently Erik and PeeWee Peter share the same meaning of
and the fact that our exchanges here in s.b.p. had been comparatively >good-natured, like the post I've shared with y'all just now.
"good-natured" to include asinine allusions.
On Thursday, August 17, 2023 at 4:41:15?AM UTC-7, jillery wrote:
On Wed, 16 Aug 2023 05:19:00 -0700 (PDT), Peter NyikosI've no idea how you got that impression. I simply stated what I did and what the results were.
<peter2...@gmail.com> posted yet another self-parody:
On Wednesday, August 16, 2023 at 1:28:44?AM UTC-4, erik simpson wrote:And nobody even implied any such obligations.
I've written to [DIG] but I've received no answer. He's not obligated to >> >> me in any way, just as I'm not obligated to TO.
As jillery pointed out, it's been over 60 hours [now over 70] since Beagle's been down.It's remarkable how PeeWee Peter repeats the same stupid lies about
I thought the following exchange from an earlier downtime, and its aftermath,
might help relieve the tension some of us might be feeling.
On Sunday, November 6, 2022 at 12:33:45 PM UTC-5, Lawyer Daggett wrote:
On Thursday, November 3, 2022 at 3:14:36 PM UTC-4, Lawyer Daggett wrote: >> >> ...
The fix to getting talk.origins up again will likely be simple once the moderator knows it needs to
be done and has time to log in and restart things. Of course weirdness can occur if some admin
blocks beagle from sending or receiving mail because of some confusion, or some automatic
software update overwrites a parameter that needs to be custom set. But the main issue is that
the moderator works for free in his spare time and he has a job and a life that takes precedent,
or at least should.
I comment on my own witty perspicacity in anticipating the sort of error that occurred. It was a block
on sending/receiving mail because of an update in a global list of spam sites, so I was, shall we
say, half right. I thus proudly accept the title of Half Wit and retire from this group.
At first I thought you were imitating Hemidactylus ("Our presence does much to improve the place")
or jillery ("...my devastating retorts"), but you wound up being more modest than them.
jillery, no matter how many times he's proved wrong.
To give credit where credit is due, the rest of us were stumbling blindly in the dark,Apparently Erik and PeeWee Peter share the same meaning of
while, as they say,
"In the land of the blind, the one-eyed man is king."
But don't let it go to your head. You are king of the t.o. exiles concerned about when
and how Beagle would be back. That's a subset of all the t.o. exiles, and the others were off
in their own virtual land.
Back to the rough and tumble,
Peter Nyikos
================================ end of post
archived at
https://groups.google.com/g/sci.bio.paleontology/c/piprYPdW6qg/m/4AJn2EISAgAJ
Re: Beagle down again
Nov 8, 2022, 7:23:54?PM
With "rough and tumble" I was referring to t.o. being back up,
and the fact that our exchanges here in s.b.p. had been comparatively
good-natured, like the post I've shared with y'all just now.
"good-natured" to include asinine allusions.
Peter went off in a relatively calm way (yes, I'm surprised at that), but I very rarely agree with
him about anything.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 302 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 100:06:05 |
| Calls: | 6,767 |
| Calls today: | 5 |
| Files: | 12,295 |
| Messages: | 5,376,419 |
| Posted today: | 1 |