Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33806
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23541
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12847
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4193
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13586
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16053
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22012
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   900
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4785
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2802
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13066
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4277
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   28550
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2020
DOS_INTERNET   0/196
duplikat   6000
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
Möte FIDONEWS_OLD4, 37224 texter
 lista första sista föregående nästa
Text 10098, 195 rader
Skriven 2013-08-29 15:21:16 av Ulrich Schroeter (2:244/1120)
  Kommentar till text 10094 av Michiel van der Vlist (2:280/5555)
Ärende: Internet access - Fidonet Policy thoughts ....
======================================================
Hi Michiel,

Thursday August 29 2013 13:17, you wrote to me:

 MV> Hello Ulrich,
 MV> On Thursday August 29 2013 05:42, you wrote to me:
 MV>>> Apart from the impossibility of changing P4,

 US>> p407, 8.1 isn't a blocker as all ZC's accepts the proposal to
 US>> move forward with the voting mechanism

 MV> The last time it was tried it already failed at the first step:
 MV> getting a majority of the RC's to say "yes".

at the first step ?

you're building your house from the roof tops ?-)

and then you probably didn't had a masterplan to move this project
to success ... ?!?  ?-)

 MV>  Six month work for some
 MV> two dozen people - me included - to come to consensus about some very
 MV> simple changes and it failed right at the first hurdle.

 MV> And now that there is no IC, it will be even more difficult. You
 MV> assume that a unanimous decision by the ZC's take the place of a
 MV> decision by the IC, but I am sure not everyone will agree on that.

preparation, that starts before starting with main work
the planning period is still to use seriosly, to identify blockers,
eg missing IC ... you have to put in extra steps, but this also is a chance to
get the required people involved, before the main project part starts
eg. start with interviews with the ZC's to get their viewpoints, what is
possible, what is a NO GO ... at this step you also can request their
anticipates, how difficult it is nowadays to get response from the RC's and
NC's of the included regions and nets. Furthermore, how deep an antipathy exist
to update an essential document

Another essential topic in project planning of Policy Update is PR - public
relations ... communicate the changes, how Fidonet will win if a specific
update will be incorporated. How each member receives an advantage if a
specific paragraph will be updated and what it does mean for the future of
Fidonet ...


 MV> Sorry Uli, I know when I have lost. I know the theory of changing P4,
 MV> and I also know that in practise it is impossible.

you didn't yet show up the real show stoppers or blocking factors
The missing IC can be a show stopper, but this needs some investigation
before it can be concluded, that it is a blocker

there were rumours all around over the years to update P407 as it is outdated
since about 15 (?) years ... there is enough potencial support, the question
is, does it count for a majority ...
The best way to get an overview is to ask around first, then start with the
work ...

 MV>  It has been tried
 MV> many times and it has always failed. If you want to try again, go
 MV> ahead, but count me out. I have better things to do than to waste my
 MV> precious time on a mission impossible.

 US>> 51% of all votes will bring the proposal POLICY to effect

 MV> You conveniently skip a number of steps....

the two potential show stoppers known from current Policy revision
is the proposal before IC (solution: bring all ZC's to accept proposal)
and the 2nd one, to receive 51% of all votes
from the casted votes out of the group of *C structure at and above NC
This is less a problem, if its well communicated down to all nodes.
If there is concensus over a topic before the project starts, its
unlikely, that later the referendum will vote against.
The challenge is, to bring all controverse topics upto a point, where a
majority can accept it.

When last try to update Policy did happen? Was it in the 90's ?
Today many sysops try to find workarounds around the P407 restrictions
discovered. All attempts in updating software with new features, that
is based on bending the Policy as possible, is a strong signal, that something
needs to be changed and brought in sync to todays knowledge about
communications.
About 15 years after the last referendum there is a good chance to move forward
with a new referendum, with all the experience we've collected over the
past 24 years P407 has been voted to effect.


 MV>>>  a complete (physical) restructure of Fidonet is suicide.

 MV>>>  In Dutch we have a saying: "je moet
 MV>>> oude bomen niet verplanten". I think that applies to Fidonet.

 US>> old fidonet still works together with the last big change -> FoIP

 MV> It barely survived that change.

What are the topics that leads you to this conclusion ?
I come to the opposite conclusion ... why approx 90% of
all Fidonet traffic is handled today via FoIP ?!?

 MV>  And we are down to less than 5% of what we ever were.

yes, we all do know this very well ... that by end of 90's
the majority of online users moved to internet services

 MV>  We are hovering near critical mass. Fidonet will
 MV> not survive another radical change.

So why did Fidonet survive so a long time ?
with introducing FoIP, we're nearby internet services, but this
is only half of the truth.

Facebook, Twitter, Google and many other internet "services"
are centralized systems ...
Fidonet still continues to work decentralized.
The physical layer that is used doesn't matter .. as long there are
enough systems (nodes), who can exchange partly the overall traffic.
If one system dies, another system recovers operation.

There is a similar idea with filesharing in the internet -> torrents
that builds up a decentralized filebase. Thats why fidonet today has a minor
role on frequests, but still continues to distribute mails

Why Fidonet'ers don't using forums and mailing lists? 'cause forums and mailing
lists are centralized systems. If the central server goes down, the mailing
lists and forum stops working. Fidonet still continues.

Look to the lavabit example ... email service provider has been shut down (for
whatever reason) .. the service died.

Fidonet's content is a balanced restriction and openess. If one node dies, the
rest of fidonet still continues to operate.

Probably you've also have heard about messages that in Egypt's spring fidonet
tooks a role ? ... one can belief it or not ... but looking deeper it makes
sense, to have a decentralized "organisation" running so that in case half of
the network has been shut down, the 2nd half still is operational alive ...

This is todays message, that realy makes Fidonet
in Tom Jennings ideas to have a universial, decentralized communications
network, where each one may connect another without having a dictatorship that
allows one to cut down the whole net.
Why do we block down possible alternate transport media with restrictions
written into policy, why we aren't able, to correct these clauses, so Fidonet
becomes future minded and open to systems that makes the heart of Fidonet -
decentralized operations over well defined FTN standards that doesn't limit
communication down to one transport media only

My vision:

          to give up the exclusivity of one transport layer only

from      -o-o--o---o-o-----o---o-o-o---o-o---oo-o--o--o--o-----o--o-

          by break down the barriers that prevents us today to move
          forward with an elevator concept
          to support multiple transport layers

to        -o-o--o---o-o-----o---o-o-o---o-o---oo-o--o--o--o-----o--o-
           |        | |     |     |     | |    |          |        |
          -o--o-o---o-o---o-o-----o---o-o-o--o-o--o--o----o-o-o----o-
           |    |     |     |     |     | |    |     |    |        |
          -o-o--o--o--o-----o-o-o-o-o---o-o---oo-o---o-o--o-----o--o-
             |     |          |   |     |            |          |
          ---o---o-o-----o----o--oo---o-o---oo----o--o--o-----o-o-o--

One potential candidate has been named in the meanwhile:
 "HAM" packet radio maybe such an addtl. transport layer
Others may follow ...

A subliminal anxiety of publishing content in the internet is not
that is intended by this concept. Its an open looking forward by the
question, what may happen tommorow, if one switches off the
centralized internet routers, than probably from one day to another
all internet and mostly all phone traffic (in the western world)
will be shut down.

Today we're using POTS and by bending Policy also IP ...
to add more physical layers we have to bend Policy again.
Is this what we want? or do we want the Policy updated
to make it possible to extend the Fidonet capabilities
to switch easily the media to continue with communication ?


 MV> Cheers, Michiel

 MV> -$- GoldED+/W32-MINGW 1.1.5-b20110320
 MV>  $ Origin: http://www.vlist.org (2:280/5555)

regards, uli   ;-)

---
 * Origin: AMBROSIA - Frankfurt/Main - Germany (2:244/1120)