Text 25784, 126 rader
Skriven 2006-02-20 23:48:00 av Dale Shipp (1:261/1466.0)
  Kommentar till text 25746 av Michiel Van Der Vlist (2:280/5555)
Ärende: Elist mergers
=====================
 -=> On 02-20-06  12:36,  Michiel Van Der Vlist <=-
 -=> spoke to Dale Shipp about This echo... <=-

 >   Needed or not, it is a useful tool.

 MVDV> Your opinion and YOUR choice to use it.

  My choice and the choice of more than 400 other moderators who choose
  to enter information about their echos there -- including an echo of
  which you are a moderator.

 >   They would need to coordinate once per month, prior to
 > issuing the updated monthly list.

 MVDV> Once a month is unaceptable. If I wanted to know who the
 MVDV> moderator of an echo is, I would want to know who it is

   If you are that much in need of instant gratification then you can do
   a direct query of the Elist data base -- but only to find out in most
   cases that it has not changed since the last monthly publication of
   the Elist.

   Personally, I think that such a desire is overkill.

 MVDV> NOW, not a month ago. An out of date list is totally
 MVDV> useless. 48 hour is the maximum I would consider acceptable.

  You are posturing for effect, and your stated expectation is
  unreasonable.    Do you insist that the telephone company send you an
  updated phone book every week?   That is equally absurd.

 > Same as the ZCs who need to coordinate once per
 >   week prior to issuing the weekly nodelist update.

 MVDV> A compromise which is on the brink of being acceptable. It
 MVDV> does not work all that well IMNSHO. Most NC's btw, offer
 MVDV> actual up to date nodelist segments by file request.

  And your point is?  That nodelist segment does not change more than
  once per week with respect to the nodes not in their net.   The fact
  that it is available to you via request is no different from the fact
  that the Elist information is available to you via request.

 MVDV> I don't think so. Actually the longer I think about it, the more I
 MVDV> tend to  the POV that this system with a merged list and a keeper
 MVDV> for each zone would not have worked well anyway. A ship
 MVDV> needs one and no more that one captain.

  The merged list would have required cooperation, not one captain.  But
  Peter abandoned the list being kept in Z2 instead of being a part of
  that cooperation.

 >   And just how would anyone do that?  Tell me exactly how a
 > routed netmail from you to me would get here?

 MVDV> We have reply request and PING to find that out.

  So use it to answer the question.   Reply request doesn't work well
  for email -- most people ignore it.   Can you do a PING to me (or to
  my NC where I pick up my netmail)?  What does it tell you?  And how
  does it tell you what the route will be next week or next month.


 > Or the reverse. All either of us can really say for sure is who
 > we deliver the netmail to.  After that, it is out of our control.

 MVDV> No, one can make arrangements with whoever one routes the
 MVDV> message to, to use only certain routes. Alternatively a

   How absurd an expectation.  I should tell my uplink's uplink how they
   should route mail.  NOT!

 MVDV> trusted person in Z1 could take the position of routing
 MVDV> moderator updates. This person would set up a direct link
 MVDV> with the e-list keeper in Z2 and forward messages for the
 MVDV> Z1 moderators.

   DUH!  That trusted person in Z1 would have been the person who
   maintains the portion of the Elist in Z1.   Since the Elist keeper in
   Z2 abandoned his portion of the Elist, that means that Thom is the
   only one left.

 MVDV> The cost and security with this setup would be EXACTLy the
 MVDV> same as with separate Z1 and Z2 e-list keepers and a merged
 MVDV> list.

  The cost is the same because it is the same method.

 MVDV> I did. There is no gebral ban on encryption.

  You are not making sense, and what ever you meant to type you are
  wrong.   Encryption is prohibited unless restricted to special
  networks.   I have not heard of such networks existing in fidonet for
  a number of years now.  Educate me by showing how you would encrypt a
  netmail and send it to me, to my NC, RC  or even my ZC via routed
  netmail.

 > At the moment, I do not know of any node who would accept an
 > encrypted routed netmail.

 MVDV> I know plenty.

  Prove it -- send me an encrypted netmail.  I want to see the evidence.

 >  Never mind, telling me how you would encrypt it in a manner that
 > would allow me to decrypt it.

 MVDV> There are programmes for that. Not more difficuolt to set
 MVDV> up than the stuff needed to maintain an e-list.

   So tell us all how you would set it up.  Don't duck the question.

 MVDV> Well, it is not illegal where Peter Witschi was. Void pint.

  "Void pint" is what you do with beer when the rental period is up:-}}

                               Dale Shipp
                  fido_261_1466 (at) comcast (dot) net
                              (1:261/1466)


... Shipwrecked on Hesperus in Columbia, Maryland. 23:10:38, 20 Feb 2006
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01
 * Origin: Owl's Anchor (1:261/1466)