Dan,

URL: news.tequilamockingbirdonline.net
Join mailto:sysop@tequilamockingbirdonline.net
NETMAIL Yes, 1:266/404

This is not a valid FidoNet node, and hasn't been for more than a year.

Correct ... however "for about just slightly over a year" would be less insinuating.

Now that we're talking, are you interested in a list of dozens and dozens of dead nodes in the nodelist, some of them being *Cs up to the level of RC ?

\%/@rd

--- DB4 - 20230201
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Ward Dossche wrote to Dan Clough <=-

URL: news.tequilamockingbirdonline.net
Join mailto:sysop@tequilamockingbirdonline.net
NETMAIL Yes, 1:266/404

This is not a valid FidoNet node, and hasn't been for more than a year.

Correct ... however "for about just slightly over a year" would
be less insinuating.

Maybe. Does it change the fact that it should have been updated by the illustrious Snooze editor many months ago?

Now that we're talking, are you interested in a list of dozens
and dozens of dead nodes in the nodelist, some of them being *Cs
up to the level of RC ?

No. I'm already aware of that, and I can't do anything to fix that.
Seems like a ZC/IC could, though. Yup.



... He does the work of 3 Men...Moe, Larry & Curly
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hey Dan,

Maybe. Does it change the fact that it should have been updated by the illustrious Snooze editor many months ago?

No, it does not. It should have been updated and probably it will. I think the problem lies in the fact that whenever a person closes the door behind him/her very little attention is given to inform those that stay behid to pick-up the thread or wind a particular activity down.

Now that we're talking, are you interested in a list of dozens
and dozens of dead nodes in the nodelist, some of them being *Cs
up to the level of RC ?

No. I'm already aware of that, and I can't do anything to fix that.
Seems like a ZC/IC could, though. Yup.

Correct again ... maybe I need to post a list of all the dead nodes ... rude awakening ... also my zone BTW...

\%/@rd

--- DB4 - 20230201
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Ward Dossche wrote to Dan Clough <=-

Maybe. Does it change the fact that it should have been updated by the illustrious Snooze editor many months ago?

No, it does not. It should have been updated and probably it
will. I think the problem lies in the fact that whenever a person
closes the door behind him/her very little attention is given to
inform those that stay behid to pick-up the thread or wind a
particular activity down.

Fair enough, and agreed.

Now that we're talking, are you interested in a list of dozens
and dozens of dead nodes in the nodelist, some of them being *Cs
up to the level of RC ?

No. I'm already aware of that, and I can't do anything to fix that.
Seems like a ZC/IC could, though. Yup.

Correct again ... maybe I need to post a list of all the dead
nodes ... rude awakening ... also my zone BTW...

I think that would be a great idea.

Oh, and thank you for being civil, and not talking in circles.


... YORGAMAK HAS ARRIVED AND WILL INITIATE DESTRUCTIMATION.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Correct again ... maybe I need to post a list of all the dead nodes ... rude awakening ... also my zone BTW...

You could try pinging the list occasionally and making a notice if it doesn't respond?

-----------------------------------
user is generated from /dev/urandom

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (1:229/317)

Correct again ... maybe I need to post a list of all the dead nodes

...

rude awakening ... also my zone BTW...

You could try pinging the list occasionally and making a notice if it doesn't respond?

I will react the way my good friend Nick Andre would want me to react ... no-one's paying me a salary and what you're asking is a pretty big job, even with a reduced nodelist these days.

To give you an idea ...

R14 has 25 entries in the region-segment but only 3 can be reached. 1:14/0 is not one of them.

R15 has 71 entries in its region-segment a multitude of which are equally unreachable fro; this location.

This can have sevaral reasons:

* Nodelist errors, for example not putting a non-standard port after the
domain but as "IBN:24555". That cannot be parsed by known software
* Invalid domain name
* Expired domain name
* Bad binkd-configuration
* Blocking inbound calls
* ...

I had a check ran as you suggested and I'm getting 217 entries with connection issues but the 'nodelist police' think I'm way too severe so I will be looking into this again at a later moment.

Take care,

\%/@rd

--- DB4 - 20230201
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Maybe. Does it change the fact that it should have been updated by the illustrious Snooze editor many months ago?

Checking the entries in what basically means an ad for peoples BBSs isn't in the Editors job description.

But thanks for pointing the error out, albeit you could have made it in netmail, now that the sysop himself didn't care about it.


--
People who think that democratic elections are all about picking the right winner, are in dire need of re-education.

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se:4119 (2:203/2)

Bj”rn Felten wrote to Dan Clough <=-

Maybe. Does it change the fact that it should have been updated by the illustrious Snooze editor many months ago?

Checking the entries in what basically means an ad for peoples
BBSs isn't in the Editors job description.

Curious. Seems like the Editor-in-Chief would/should be responsible for
all content of the publication. That's generally true for most any other periodical I can think of. Who else would/could do it?

But thanks for pointing the error out, albeit you could have
made it in netmail, now that the sysop himself didn't care about
it.

I have a vague memory, not completely sure of though; that the sysop in question has passed away...


... The Fourth Law of Computing: on a slow day, you can wait forever.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Curious. Seems like the Editor-in-Chief would/should be responsible for all content of the publication. That's generally true for most any other periodical I can think of. Who else would/could do it?

Well, what salary do those Editors that you think of have?

Who else? For a non-profit community driven publication, it's usually the community that's responsible for it's content.


--
People who think that democratic elections are all about picking the right winner, are in dire need of re-education.

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se:4119 (2:203/2)

Bj”rn Felten wrote to Dan Clough <=-

Curious. Seems like the Editor-in-Chief would/should be responsible for all content of the publication. That's generally true for most any other periodical I can think of. Who else would/could do it?

Well, what salary do those Editors that you think of have?

Significant salary, I'm sure. Not really relevant, though, as your
position is voluntary and you knew there was no salary when you took on
the job. Are you now saying you don't want to do the Editor's job
unless you are paid?

Who else? For a non-profit community driven publication, it's
usually the community that's responsible for it's content.

Sure, the content when it comes to "news" articles and so on is. But
the material under discussion here is "static" stuff that simply gets copy/pasted into each edition. It rarely changes, but sometimes does.
So in this case, the community, namely *ME*, noticed an error and
brought it to the attention of the designated Editor. I cannot
delete/alter any content myself, so wouldn't it make sense that the
Editor would do it after being informed of a change? It would seem that
all has worked as expected, at least to this point. Correct?


... Would you like to wake up from this dream?
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hello Bj”rn,

Curious. Seems like the Editor-in-Chief would/should be responsible

for

all content of the publication. That's generally true for most any

other

periodical I can think of. Who else would/could do it?

Well, what salary do those Editors that you think of have?

Who else? For a non-profit community driven publication, it's usually the community that's responsible for it's content.

Dan is absolutely correct. And I mean absolutely. In fact, Dan has
come up with the perfect solution, as noted in his own words -

I cannot delete/alter any content myself, so wouldn't it make sense
that the Editor would do it after being informed of a change? It
would seem that all has worked as expected, at least to this point.
Correct?

Dan has spotted the problem, and offered a solution to fix it.
After all, this is a non-profit community driven publication.
And Dan is a full-fledged member of that non-profit community
driven publication. And he really did make you an offer. An
offer you really cannot refuse.

So. It is all up to you now. Are you going to let him do it?
I mean, he did offer to fix it. All by himself. At no cost to
anybody else. So whataya say? He just made you an offer you
cannot refuse and you gonna tell him no? Let him do it! Let
him do it! You'll never forget it. Trust me, you'll never
forget it. Or believe another word I ever say.

For Life,
Lee

--
Be Stupid

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se:4119 (2:203/2)

Dan has spotted the problem, and offered a solution to fix it.
After all, this is a non-profit community driven publication.
And Dan is a full-fledged member of that non-profit community
driven publication. And he really did make you an offer. An
offer you really cannot refuse.

There's no need to patronize the guy.

Yes, it's nice that he finally understood what most of us have known for decades, and maybe even a few more now understand the concept.

Of course the Editor will listen to what the community has to say. DUH!


--
People who think that democratic elections are all about picking the right winner, are in dire need of re-education.

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se:4119 (2:203/2)