Senin, 24 Oktober 2011
06.21 | Diposting oleh
Expresi Of Love |
Edit Entri
Most early BBSes operated as stand-alone islands. Information contained on that BBS never left the system, and users would only interact with the information and user community on that BBS alone. However, as BBSes became more widespread, there evolved a desire to connect systems together to share messages and files with distant systems and users. The largest such network was FidoNet.
As is it was prohibitively expensive for the hobbyist SysOp to have a dedicated connection to another system, FidoNet was developed as a store and forward network. Private electronic mail (Netmail), public message boards (Echomail) and eventually even file attachments on a FidoNet-capable BBS would be bundled into one or more archive files over a set time interval. These archive files were then compressed with ARC or ZIP and forwarded to (or polled by) another nearby node or hub via a dialup Xmodem session. Messages would be relayed around various FidoNet hubs until they were eventually delivered to their destination. The hierarchy of FidoNet BBS nodes, hubs, and zones was maintained in a routing table called a Nodelist. Some larger BBSes or regional FidoNet hubs would make several transfers per day, some even to multiple nodes or hubs, and as such, transfers usually occurred at night or early morning when toll rates were lowest. In Fido's heyday, sending a Netmail message to a user on a distant FidoNet node, or participating in an Echomail discussion could take days, especially if any FidoNet nodes or hubs in the message's route only made one transfer call per day.
FidoNet was platform-independent and would work with any BBS that was written to use it. BBSes that did not have integrated FidoNet capability could usually add it using an external FidoNet front-end mailer such as FrontDoor, BinkleyTerm, InterMail or D'Bridge, and a mail processor such as FastEcho or Squish. The front-end mailer would conduct the periodic FidoNet transfers, while the mail processor would usually run just before and just after the mailer ran. This program would scan for and pack up new outgoing messages, and then unpack, sort and "toss" the incoming messages into a BBS user's local electronic mailbox or into the BBS's local message bases reserved for Echomail. As such, these mail processors were commonly called "scanner/tosser/packers."
Many other BBS networks followed the example of FidoNet, using the same standards and the same software. These were called FidoNet Technology Networks (FTNs). They were usually smaller and targeted at selected audiences. Some networks used QWK doors, and others such as RelayNet (RIME) and WWIVnet used non-Fido software and standards.
Before commercial Internet access became common, these networks of BBSes provided regional and international e-mail and message bases. Some even provided gateways, such as UFGATE, by which members could send/receive e-mail to/from the Internet via UUCP, and many FidoNet discussion groups were shared via Usenet. Elaborate schemes allowed users to download binary files, search gopherspace, and interact with distant programs, all using plain text e-mail.
As the volume of FidoNet Mail increased and newsgroups from the early days of the Internet became available, satellite data downstream services became viable for larger systems. The satellite service provided access to FidoNet and Usenet newsgroups in large volumes at a reasonable fee. By connecting a small dish & receiver, a constant downstream of thousands of FidoNet and Usenet newsgroups could be received. The local BBS only needed to upload new outgoing messages via the modem network back to the satellite service. This method drastically reduced phone data transfers while dramatically increasing the number of message forums.
FidoNet is still in use today, though in a much smaller form, and many Echomail groups are still shared with Usenet via FidoNet to Usenet gateways. Widespread abuse of Usenet with spam and pornography has led to many of these FidoNet gateways to cease operation completely.
As is it was prohibitively expensive for the hobbyist SysOp to have a dedicated connection to another system, FidoNet was developed as a store and forward network. Private electronic mail (Netmail), public message boards (Echomail) and eventually even file attachments on a FidoNet-capable BBS would be bundled into one or more archive files over a set time interval. These archive files were then compressed with ARC or ZIP and forwarded to (or polled by) another nearby node or hub via a dialup Xmodem session. Messages would be relayed around various FidoNet hubs until they were eventually delivered to their destination. The hierarchy of FidoNet BBS nodes, hubs, and zones was maintained in a routing table called a Nodelist. Some larger BBSes or regional FidoNet hubs would make several transfers per day, some even to multiple nodes or hubs, and as such, transfers usually occurred at night or early morning when toll rates were lowest. In Fido's heyday, sending a Netmail message to a user on a distant FidoNet node, or participating in an Echomail discussion could take days, especially if any FidoNet nodes or hubs in the message's route only made one transfer call per day.
FidoNet was platform-independent and would work with any BBS that was written to use it. BBSes that did not have integrated FidoNet capability could usually add it using an external FidoNet front-end mailer such as FrontDoor, BinkleyTerm, InterMail or D'Bridge, and a mail processor such as FastEcho or Squish. The front-end mailer would conduct the periodic FidoNet transfers, while the mail processor would usually run just before and just after the mailer ran. This program would scan for and pack up new outgoing messages, and then unpack, sort and "toss" the incoming messages into a BBS user's local electronic mailbox or into the BBS's local message bases reserved for Echomail. As such, these mail processors were commonly called "scanner/tosser/packers."
Many other BBS networks followed the example of FidoNet, using the same standards and the same software. These were called FidoNet Technology Networks (FTNs). They were usually smaller and targeted at selected audiences. Some networks used QWK doors, and others such as RelayNet (RIME) and WWIVnet used non-Fido software and standards.
Before commercial Internet access became common, these networks of BBSes provided regional and international e-mail and message bases. Some even provided gateways, such as UFGATE, by which members could send/receive e-mail to/from the Internet via UUCP, and many FidoNet discussion groups were shared via Usenet. Elaborate schemes allowed users to download binary files, search gopherspace, and interact with distant programs, all using plain text e-mail.
As the volume of FidoNet Mail increased and newsgroups from the early days of the Internet became available, satellite data downstream services became viable for larger systems. The satellite service provided access to FidoNet and Usenet newsgroups in large volumes at a reasonable fee. By connecting a small dish & receiver, a constant downstream of thousands of FidoNet and Usenet newsgroups could be received. The local BBS only needed to upload new outgoing messages via the modem network back to the satellite service. This method drastically reduced phone data transfers while dramatically increasing the number of message forums.
FidoNet is still in use today, though in a much smaller form, and many Echomail groups are still shared with Usenet via FidoNet to Usenet gateways. Widespread abuse of Usenet with spam and pornography has led to many of these FidoNet gateways to cease operation completely.
Label:
Networks
Langganan:
Posting Komentar (Atom)
Blog Archive
-
▼
2011
(1035)
-
▼
Oktober
(812)
- Wayang Topeng or Wayang Gedog
- The Dalang
- gerah
- About Wayang Kulit
- Museum Wayang Kekayon
- Wayang Sadat
- Etymology of the word
- form•Z on the small and big screen
- Rendering
- Animation
- Modeling
- Overview
- Modeler
- Transporter
- History
- Product family
- Surfacing
- Animation tools
- Drafting Assistant
- Cobalt (CAD program)
- Current State of Design Methods
- Significance of Proliferation of Information Techn...
- Proliferation of Information Technologies
- Significance of Design Management
- Alternative View
- Design Management
- Significance of Role of Professional Design Practice
- Professional Design Practice
- Significance of Emergence of Design Research and D...
- Emergence of Design Research and Design Studies
- Where Process Meets Method
- Background of Design Methods
- Design methods
- Globalization and governance controversy
- Governors
- Formation and growth of the network
- Internet governance
- Elements
- Roles
- Additional principles exist where projects are mul...
- Additional and complementary principles of governa...
- Principle 4: Ensure separation of project governan...
- Principle 3: Ensure separation of stakeholder mana...
- Principle 2: Service delivery ownership determines...
- Principle 1: Ensure a single point of accountabili...
- Three pillars of project governance
- Project governance
- Professional certification
- Frameworks
- Problems with IT governance
- Background
- Definitions
- Corporate governance of information technology
- Domination by large organizations
- Membership
- Administration
- Recommendations and Certifications
- History
- World Wide Web Consortium
- Governance models
- Website management team
- Areas of responsibility
- Website governance
- Webmaster
- Reusability
- Flexible presentation
- Effective separation
- Template uses
- Web template
- Web syndication and e-commerce
- Web syndication as a commercial model
- History
- Motivation
- Web syndication
- Criticisms
- Automated design methodologies
- Representational state transfer (REST)
- Service-oriented architecture
- Remote procedure calls
- Web API
- Big Web services
- Web service
- Web document
- Security Considerations
- Advanced
- Basic
- Client Side + Server Side
- Server Side Coding
- Client Side Coding
- Web development as an industry
- Web development
- Changes and updates
- Best practices
- Web design
- Disadvantages
- Advantages
- Online processing (called "frying" systems)
- Capabilities
- Web content management system
- Role of information management
- Governance rather than workflow
- Five stages
- Four stages
- Web content lifecycle
- Career
- Current work
- Career
- Early life
- Tim Berners-Lee
- Social networking in a work environment
- Exponential generation of resource consuming negat...
- Timeline
- History
- Theory
- Debates or design choices
- Virtual presence
- Comparison of communication and interactive tools
- Social network search engines
- Social network services
- Blogs
- Internet forums
- Groupware
- Text chat
- Instant messaging
- Social software
- Possibility and degrees of separation
- Machine readability
- Intended meaning
-
▼
Oktober
(812)
Pengikut
About Me
- Expresi Of Love
0 komentar:
Posting Komentar