F I D O N E W S Volume 16, Number 09 01 March 1999 +----------------------------+---------------------------------------+ | The newsletter of the | ISSN 1198-4589 Published by: | | FidoNet community | "FidoNews" | | _ | +27-41-581-5913 [5:5/23] | | / \ | | | /|oo \ | | | (_| /_) | | | _`@/_ \ _ | | | | | \ \\ | Editor: | | | (*) | \ )) | Henk Wolsink 5:7104/2 | | |__U__| / \// | | | _//|| _\ / | | | (_/(_|(____/ | | | (jm) | Newspapers should have no friends. | | | -- JOSEPH PULITZER | +----------------------------+---------------------------------------+ | Submission address: FidoNews Editor 5:5/23 | +--------------------------------------------------------------------+ | MORE addresses: | | | | submissions=> editor@fidonews.org | | hwolsink@catpe.alt.za | +--------------------------------------------------------------------+ | For information, copyrights, article submissions, | | obtaining copies of FidoNews or the internet gateway FAQ | | please refer to the end of this file. | +--------------------------------------------------------------------+ Table of Contents 1. EDITORIAL ................................................ 1 2. GUEST EDITORIAL .......................................... 2 Announcing Candidacy for Z1C... maybe .................... 2 What's Not Happening - Elections ......................... 2 3. LETTERS TO THE EDITOR .................................... 5 SPAM-lite in FidoNews? Ptooie! .......................... 5 4. ARTICLES ................................................. 6 Grunged Echomail Deleted (a Response) .................... 6 Letter from a concerned reader? .......................... 6 The Shrinking Nodelist - What can be done? ............... 7 Zone 1 Backbone Service Level Agreement .................. 8 5. COLUMNS .................................................. 20 ECHO TALK - Monkey Business .............................. 20 6. NOTICES .................................................. 21 7. FIDONET BY INTERNET ...................................... 22 8. FIDONEWS INFORMATION ..................................... 26 FIDONEWS 16-09 Page 1 1 Mar 1999 ================================================================= EDITORIAL ================================================================= Greetings, On my question in the 16-07 issue about Z2 and in particular R29, I received a very interesting e-mail from a SysOp there. It seems, that the Z2C just wants to show how big or is it small, he can be. What a great pity. As the saying goes: it takes all kinds to make the world go round. ;-) Since I do have the full message and the authors name here on file, he has given permission to use it. Some interesting articles this week. From a message I saw, Bob Satti has decided not stand for another term as Z1C. Thats the spirit Bob, one should not have two *C positions as far as I'm concerned. ;-) Happy reading, ----------------------------------------------------------------- FIDONEWS 16-09 Page 2 1 Mar 1999 ================================================================= GUEST EDITORIAL ================================================================= I'm not sure why I'm doing this... you'd think I'd learn. Last year I announced a candidacy for the Z1EC election, only to find that the election I'd expected never happened. Things are different this year, though. In announcing for the Z1C sysop-level election, I'm not expecting it to be held. In fact, there's been no hint from the Zone 1 RC's, who are empowered by policy to elect a Zone Coordinator, that there are any plans afoot, let alone a sysop-level election. I'm interpreting the silence from the RC's as an indication that Bob Satti will receive a vote of confidence, as happened last year, and this will serve as an election for an additional two-year term. So why run for an office when I don't expect an open election? Mostly because I believe that there should be one. There are at least two good reasons for this: 1. Fidonet sysops have expressed a consistent desire that representative positions be determined by sysop-level election rather than by the appointments specified in Policy 4. It's become fairly common practice at the NC level and a growing number of RC's are elected... but not the ZC. 2. Bob Satti currently holds the simultaneous positions of Zone Coordinator for Zone 1 and International Coordinator for all of Fidonet. One of these positions is more than enough for one man - it's time to let go. Whether there is an open election or not, I intend to start acting like a candidate. Currently I plan to discuss two issues which I consider core to the ZC position - the shrinking nodelist and the subject of elections. Following those discussions, I'll try to follow up on whatever feedback comes from echomail and netmail. One outcome I'd like to see from this announcement is the encouragement of other candidates to announce so we can get a real forum going. Perhaps Bob Satti will even join us. I'd especially like to see the sysops of Fidonet actually conduct an open election themselves rather than waiting for the RC's to make a decision. Such an election would not be binding on the RC's of course, but would effectively communicate to them the expectations of the sysops. Hopefully the RC's would realize that this is a healthy process, and seriously consider it. ----------------------------------------------------------------- What's Not Happening - Elections .-- -- -- -- -- -- WHAT'S NOT HAPPENING -- -- -- -- -- --. | There isn't always something happening on Fidonet, but | | there's always something which isn't happening. This | FIDONEWS 16-09 Page 3 1 Mar 1999 | column is dedicated to the lost causes which make Fido | | what it isn't today. Published semi-occasionally... | `-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --' Douglas Myers 1:279/720 doug@mdtnbbs.com Perennial sport in the Fido echoes is the roasting of non-elected coordinators. Currently, Martin Belcke (Regional Coordinator of Region 11) is the recipient of the honors, but he shares the limelight on a rotating basis with Dallas Hinton (RC17) and Bob Satti (Zone 1 Coordinator and International Coordinator), with occasional guest appearances by other notables. In all fairness, the criticism doesn't center on Martin's performance as RC. Indications are that he does a good job in that capacity, and probably enjoys widespread support in his own region. The criticism centers on a deep-seated conviction on the part of many that representative positions in Fido should be determined by regularly-scheduled, public elections. Unfortunately, Fido policy doesn't actually require elections - all coordinator positions are appointments by policy. However, it's become customary for a substantial number of these positions to hold public, sysop-level elections with the elected candidate then appointed per policy, and proponents of elections want that practice uniformly applied. Election advocates make several claims to support their wishes: 1. Elections, if uniformly applied, would revitalize Fidonet. This seems highly doubtful to me, as the main reason for Fido's shrinking nodelist seems to be the simple fact that computer enthusiasts have found the Internet more attractive than local BBSes. 2. Elections yield better leaders. This is unsupported, and I doubt that it can be demonstrated. However, I believe regularly-scheduled elections encourage some minimum of responsiveness from representatives, or - at least - provide a means for their removal at the next election if unsatisfactory. 3. Elections "validate" a coordinator. This seems to be the strongest argument for elections to me. No matter how controversial the election, most folks recognize a voting process as valid. Martin and his supporters offer several reasons to decline holding an election: 1. Sysops in the region have indicated that they don't want an election - to hold one would act against the wishes of the majority. FIDONEWS 16-09 Page 4 1 Mar 1999 There does seem to be some validity to the claim that sysops in the region are generally satisfied with their present representation, or - at least - aren't in open revolt. Unfortunately, the basis for that claim isn't solid. Surveys have been conducted by both proponents and opponents of elections with, supposedly, conflicting results. I suspect that sysops in the region have no desire to elect another candidate, but are not necessarily opposed to holding elections. It's hard for me to see how an actual election would be any more of an imposition than all the surveys. 2. Elections are a messy procedure, leading to vocal conflict and general disharmony. If they're done right, this is true. However, what's the alternative? Morphine injections? 3. Elections don't necessarily lead to agreement; those who supported a candidate before still support him, those who didn't still don't, and those who didn't care still don't. It's certain that the arguments still go on after an election, often with charges of election irregularities. Still, most folks eventually concede that the fellow who got the most votes should represent. My prediction is that sysop-level elections for Regions 11 and 17 and for the Z1C position won't happen in the near future... but they should. Not because Fido will somehow be revitalized with elections, not because the unelected coordinators have done a poor job, but simply because Fido should be in the hands of the sysops who are members. ----------------------------------------------------------------- FIDONEWS 16-09 Page 5 1 Mar 1999 ================================================================= LETTERS TO THE EDITOR ================================================================= SPAM-lite in FidoNews? Dear Editor: It was with growing dismay that I read the two-page press release from Fast Engines, Inc. embedded in FIDO1606.NWS, touting their new web server utility. What made it worse was that it was the longest "article" in the Snooze -- although that is not the point. I'm really very disappointed. I didn't like the idea when you announced in FIDO1547.NWS that you would allow ads that related to "BBSs and/or Fidonet", but I assumed that you meant it would be limited to commerical products applicable to the majority of FidoNet. I assumed wrongly, it seems. Since the simple majority of us still run POTS dial-up BBSi and don't run web servers, Fast Engine's product has no utility for us. In fact, it amounts to SPAM-lite, if you will --a little less salty but it still gets piped directly to an audience that didn't solicit the ad, can't use the product, don't want it and still must pay to haul and store it. I note that several to the Snooze Editor on this subject were published in 1998 (Gary Petersen, Dave Garland in FIDO1523, Doc Logger in FIDO1547) and that all of them were objections. When Zorch raised the question FIDO1522, he appeared to have qualms about the appropriateness of commerical ads. Since the readership has commented that it doesn't want commerical ads, I ask that you revise your stand and cease publishing them. If I'm hungry for highly processed stuff in a brightly colored package, I'll seek it out on my own. Lee Ayrton 1:320/455 dayrton@mail.welseyan.edu ED: The editor has the right to publish what he/she thinks is appropriate for the newsletter. I have made it quite clear in the FIDONEWS echo, that I will allow advertising, provided it relates to computers and/or communication(s). No one editor, regardless for which or what publication it might be, has the same oppinion about what should or not be placed in the their newsletter, magazine or newspaper. Your objection has been noted and I appriciate feedback. Thanks. ----------------------------------------------------------------- FIDONEWS 16-09 Page 6 1 Mar 1999 ================================================================= ARTICLES ================================================================= Grunged Echomail Deleted (a Response) by Jerry Schwartz 1:142/928 A couple of weeks ago, Roy Tellason asked about the appropriateness of suppressing long (30kb) messages from the echomail distribution system. While I'm no expert in this matter, I can address his question about whether or not people are running software which needs to be protected from messages of this size. Not long ago, I posted a series of messages which were in the 16k range (approximately). I checked to make sure they weren't much bigger than that, but I didn't check their size exactly. I should have been more careful, I guess: one or another of those messages prevented my uplink from tossing the entire bundle! Again, I can't say what the limit is but I was certainly surprised that an OS/2 system running Squish would have problems with anything I, running the DOS version of Squish, could generate. So the answer is "Yes." Anyone posting messages in the 16kb+ range is creating a technical problem. As a technical solution, I'd certainly prefer to see messages split, rather than bounced or deleted, but I'm not in charge around here.