Text 25929, 94 rader
Skriven 2012-02-26 09:47:50 av Roy Witt (1:387/22)
  Kommentar till text 25810 av Björn Felten (2:203/2)
Ärende: Fidonews Vol 29 No 08 February 20, 2012
===============================================
26 Feb 12 07:05, Björn Felten wrote to Roy Witt:


 RW>> After a few weeks of seeing the results of what happened, I even
 RW>> wrote an article for Fidonews stating that Fidonet can repair the
 RW>> disorder if we all work together.

 BF>    Amen to that! Cooperation is the true key to a properly working
 BF> network, that's for sure.

That is the key that will continue Fidonet as a whole, rather than as two
seperate entities.

 BF>    I think that our readers would very much appreciate that article,
 BF> even it it now may be a matter of retrospect.

I'll look it over and see if there's anything that needs changing, then
ponder what good it would do in retrospect.

 BF>    I know that I personally would appreciate it. :)

I'm sure you would...but I'd have to submit it to both version editor's at
the same time to be fair.

 BF>    And, a few of us has continued the work that you started. We now
 BF> no longer disconnect old links when connecting to new ones.

I've never disconnected from any link that would work with me in that
regard. I have been disconnected by unsatisfied links who didn't like my
brand of politics. No problem, as there was always a fall-back plan to
follow.

 BF>    The problem there is of course when we get interzonal connections
 BF> (the S-B-lines will not help preventing dupe loops), but from what we
 BF> can see, the normal dupe check will do the job just fine.

The ancient practice of deleting seen-by lines was to detect such dupe
prevention and worked because there weren't any nets on the other side of
any Zone that had the same net. Today that no longer applies and seen-bys
can remain intact. I have a dual feed to one remaining echo that
periodically receives the same messages in each echo. The one configured
in Area C gets the messages in the intended echo, the one that is
configured in Area A gets tossed into my BAD messages folder. Since the
output of the tosser's Areas.BBS file is used in GoldEd to read what is
tossed, I see both versions of those messages. BADs are deleted by this
user, while the others remain in the echo in which they are designated.

 BF>    The few dupes that get away will be a tell tale of what nodes are
 BF> not following FTN standards properly anyway... 8-)

I don't think I've sent out any dupes with three different links to
echomail. The above that are tossed to BAD are never tossed out, although
they could be, very easily. If I were to include a fourth, it's easy
enough to add an additional Area and toss those as well. Not to mention
that I also have 2 or 3 echomail areas set up in net 387 for net level
local distribution...

 BF>    Our embryo of a proper web organization is now covering three
 BF> zones, and we are seeking connections to the other two. If anyone
 BF> from Z4 and Z5 feels up to it, please give me a call.

There exists the Gulf Coast backbone, which one member's job is to inquire
of both of those zones about that. That's an attempt to get Fidonet
echomail back on track with something similar to the World Wide Backbone
of yesteryear.

 RW>> PS - I don't see any of Ross' messages here, so there must be
 RW>> something broken in the NAB that causes that to happen. If he's not
 RW>> sending his messages to Janis, there's a big chance that they won't
 RW>> appear here at all. OTH, if she does receive them and they aren't
 RW>> sent to our mutual source in Z3, then they may go the same route as
 RW>> the missing Fnews messages that Neut didn't see.

 BF>    That's interesting. And I mean that in a technical sense, not a
 BF> political, mind you. :)

I suppose, if push comes to shove, I could areafix this echo from Ross and
see those messages in my BAD area. Of course, that would require some
trickery in reading and writing privileges here. Meaning I would have to
change Ross's security level so that they don't go back out to his system.

 BF>    Please keep us posted on future developments here!

OK.

                R\%/itt


  ... Only those who will risk going too far can possibly
  ... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
 * Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)