| Revision as of 02:07, 8 December 2003 editPaul A (talk | contribs)Extended confirmed users63,852 editsmNo edit summary← Previous edit | Revision as of 05:31, 26 February 2004 edit undoSerak (talk | contribs)217 edits Added some tech and organization info...Next edit → | ||
| Line 6: | Line 6: | ||
| Later other BBS software that supported the same protocol was added to the net. | Later other BBS software that supported the same protocol was added to the net. | ||
| ⚫ | The Fidonet is (usually) a ] based system, where the nodes connect to each other and exchange files according to a set ]. Since the connections are using the same telephone lines that are used for the normal users of the BBS, the fidonet transfers only happen at special times of the day (" |
||
| ==Overview== | |||
| ⚫ | The Fidonet is (usually) a ] based system, where the nodes connect to each other and exchange files according to a set ]. Since the connections are using the same telephone lines that are used for the normal users of the BBS, the fidonet transfers only happen at special times of the day ("Zone Mail Hour", typically 4:00 in the morning). | ||
| Today Fidonet supports its own standards for netmail (similar to Internet e-mail), echomail (]-like news) and file transfers. | Today Fidonet supports its own standards for netmail (similar to Internet e-mail), echomail (]-like news) and file transfers. | ||
| Line 14: | Line 17: | ||
| Fidonet is operated by computer amateurs (many of them also ]s and ]) and is free. | Fidonet is operated by computer amateurs (many of them also ]s and ]) and is free. | ||
| ⚫ | Fidonet is organized in a tree structure, with fully automated software suites as branches and additional end users' software as leaves. | ||
| A typical software suite includes a '''mailer''' (a program that handles the physical transfer of files and messages between systems), a '''tosser''' (which packages messages to be transferred, performs basic routing sometimes acting as a compatibility layer for end user's software) and various other utilities (eg. file-compressor, mail-editor). | A typical software suite includes a '''mailer''' (a program that handles the physical transfer of files and messages between systems), a '''tosser''' (which packages messages to be transferred, performs basic routing sometimes acting as a compatibility layer for end user's software) and various other utilities (eg. file-compressor, mail-editor). | ||
| Line 22: | Line 23: | ||
| Fidonet usage has dropped a lot, but it is still particularly popular in ]. | Fidonet usage has dropped a lot, but it is still particularly popular in ]. | ||
| ==Organization== | |||
| ⚫ | Fidonet is organized in a tree structure, with fully automated software suites as branches and additional end users' software as leaves. | ||
| The Fidonet hierarchy consists of Zones,Regions,Networks,Nodes and Points broken down more-or-less geographically. The highest level is the Zone which is largely continent based: Zone 1 is North America, Zone 2 is Europe, Zone 3 is Australia, et cetera. Each zone is broken down into regions, which are broken down into nets, which consist of individual nodes. A node may also support ''points'', i.e. users who operate their own mail software but do not operate | |||
| ]s, and thus fall somewhere between a BBS ''user'' and a ''Sysop''. | |||
| Unlike the internet, each system maintains a ''nodelist'' of '''all''' member systems. Information on each node includes: name of the BBS, name of the Sysop, geographic location, telephone number, and software capabilities. | |||
| As an example, consider a node located in ], ] whose assigned node number is 918: This is located in Zone 1 (North America), Region 19, Network 170. The full Fidonet address would be be 1:170/918. Note, the ''region'' is for administrative purposes, not part of the address. Such a system may also support ''points'': for a point assigned number 42 (by the Sysop of this node) the address would be 1:170/918.42. | |||
| Netmail and Echomail flow along the same structure. A user (or point) enters a message, which the node sends to a ''hub''. A hub acts as a distribution/reception point for mail. The hub then typically send the message to the Net Coordinator. From there it may be sent through a Regional Coordinator, or to some other system specifically set up for the function. Mail to other zones is sent through a Zone Gate. Using the example above, a message might follow the path: | |||
| *1:170/918.42 ''(point)'' to 1:170/918 ''(node)'' to 1:170/900 ''(hub)'' to 1:170/0 ''(net coordinator)'' to 1:19/0 ''(region coordinator)'' to 1:1/0 ''(zone coordinator)''. From there, it gets distributed 'down stream' to the destination node(s). | |||
| ==Technical Specifications== | |||
| Fidonet contains a number of technical specifications for compatibility across systems. The most basic of all is ''FTS-0001'' which defines: | |||
| *Handshaking | |||
| *Transfer protocol ''(X-Modem)'' | |||
| *Message format | |||
| Other specifications provide for ''echomail'', different transfer protocols and handshake methods (''ex: Yoohoo/Yoohoo2u2, EMSI''), file compression, nodelist format and other aspects. Traditionally, '''every''' system must comply with FTS-0001 in order to become a Fidonet member. | |||
| ==External links== | ==External links== | ||
Revision as of 05:31, 26 February 2004
Fidonet is an inter-connecting file and message transport system used by BBSs before the explosion of the Internet. It was originally founded in 1984 by Tom Jennings as a means to network the "Fido" BBS software he developed.
Later other BBS software that supported the same protocol was added to the net.
Overview
The Fidonet is (usually) a dialup based system, where the nodes connect to each other and exchange files according to a set protocol. Since the connections are using the same telephone lines that are used for the normal users of the BBS, the fidonet transfers only happen at special times of the day ("Zone Mail Hour", typically 4:00 in the morning).
Today Fidonet supports its own standards for netmail (similar to Internet e-mail), echomail (Usenet-like news) and file transfers. Recent standards describe ways of transferring Fidonet messages and files by TCP/IP so it's possible to run Fidonet over Internet.
Some of Fidonet's echomail conferences are available in the Usenet news hierarchy and there are mail gates for exchanging messages between Internet and Fidonet.
Fidonet is operated by computer amateurs (many of them also hackers and radio amateurs) and is free.
A typical software suite includes a mailer (a program that handles the physical transfer of files and messages between systems), a tosser (which packages messages to be transferred, performs basic routing sometimes acting as a compatibility layer for end user's software) and various other utilities (eg. file-compressor, mail-editor).
An end user's software includes a (message) reader in addition to the list above.
Fidonet usage has dropped a lot, but it is still particularly popular in Russia.
Organization
Fidonet is organized in a tree structure, with fully automated software suites as branches and additional end users' software as leaves.
The Fidonet hierarchy consists of Zones,Regions,Networks,Nodes and Points broken down more-or-less geographically. The highest level is the Zone which is largely continent based: Zone 1 is North America, Zone 2 is Europe, Zone 3 is Australia, et cetera. Each zone is broken down into regions, which are broken down into nets, which consist of individual nodes. A node may also support points, i.e. users who operate their own mail software but do not operate BBSs, and thus fall somewhere between a BBS user and a Sysop.
Unlike the internet, each system maintains a nodelist of all member systems. Information on each node includes: name of the BBS, name of the Sysop, geographic location, telephone number, and software capabilities.
As an example, consider a node located in Tulsa, Oklahoma, USA whose assigned node number is 918: This is located in Zone 1 (North America), Region 19, Network 170. The full Fidonet address would be be 1:170/918. Note, the region is for administrative purposes, not part of the address. Such a system may also support points: for a point assigned number 42 (by the Sysop of this node) the address would be 1:170/918.42.
Netmail and Echomail flow along the same structure. A user (or point) enters a message, which the node sends to a hub. A hub acts as a distribution/reception point for mail. The hub then typically send the message to the Net Coordinator. From there it may be sent through a Regional Coordinator, or to some other system specifically set up for the function. Mail to other zones is sent through a Zone Gate. Using the example above, a message might follow the path:
- 1:170/918.42 (point) to 1:170/918 (node) to 1:170/900 (hub) to 1:170/0 (net coordinator) to 1:19/0 (region coordinator) to 1:1/0 (zone coordinator). From there, it gets distributed 'down stream' to the destination node(s).
Technical Specifications
Fidonet contains a number of technical specifications for compatibility across systems. The most basic of all is FTS-0001 which defines:
- Handshaking
- Transfer protocol (X-Modem)
- Message format
Other specifications provide for echomail, different transfer protocols and handshake methods (ex: Yoohoo/Yoohoo2u2, EMSI), file compression, nodelist format and other aspects. Traditionally, every system must comply with FTS-0001 in order to become a Fidonet member.