Clearing Houz - About

Clearing Houz

Home

About

Lists

BBS List

FTN List

Status

Login

FTN Networks

Explore Networks<br>cnet<br>dovenet<br>fidonet<br>fsxnet<br>health<br>hobbynet<br>nixnet<br>pinet<br>retronet<br>tqwnet<br>zeronet

Debug<br>View Packet

About the FTN Clearing Houz

Welcome to the FTN Clearing Houz .

FTN is an abbreviation for FidoNet Technology Network, and the most well known FTN is<br>"FidoNet" that still exists today.<br>There were many other "Othernets" also created around that time and since, and some still in operation today as<br>well.

FidoNet was born in the 1980's (well before the public Internet) when personal computers were being introduced to<br>homes, and modems were being invented.<br>Some very clever people developed protocols and standards to exchange mail and files with peers, with the<br>network growing to around 40,000 systems in the mid 1990's.<br>Those systems were called BBSes or<br>Bulletin Board Systems.<br>As "the Internet" became more accessible, the usage of FidoNet and BBSes drastically reduced, but there are some<br>systems still in operation today.

The FTN Clearing Houz is both an FTN Mailer and FTN message tosser, where mail<br>is stored internally in a DB, and files in an S3 bucket. It can also hatch and toss files into FTN networks for<br>both upstream and downstream nodes.

It was created as an idea to bring modern technology and capabilities to that legacy computing network that<br>existed in the 1980's and 1990's, where many of those programs from the 1980's and 1990's are still in use today<br>too.

Setting up an FTN network is fun, but managing one for the longer term, in amongst our busy lives can involve<br>some tedious repetitive tasks.<br>In the same vain, maintaining and growing an FTN network also can be time consuming, especially when your effort<br>(or lack thereof) can affect the experience of your users.<br>So FTN Clearing Houz was created to help address that.

Building this software is driven by four main goals:

Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a<br>network with the minimum of effort (relieving a dependancy on an admin to set you up, and thus freeing up<br>time for those admins).

Automation - so that repetitive tasks can be done with minimal effort.

High Availability - So if one hub goes down, users can automatically connect to an alternate hub to keep<br>mail flowing. Furthermore, as hubs retire, new hubs can assume the role of the retiring hub with minimal<br>effort. This goal was attempted with CockroachDB, but abandoned due to he resource requirements it required and latency that it introduced.<br>I welcome any ideas to help achieve this goal.

Connectivity - with all the different types of connectivity options between the different BBS/Mailer types.<br>Clearing Houz currently supports BINKP and EMSI/ZModem mailer types, and 4 FTN packet types.<br>There is also a HTTP API available, so you dont need to use an FTN mailer if you dont want to.

If you have a BBS that uses a unique packet type (eg: QWK or ?) or a unique transfer type (eg: NNTP or ?) and would like to get access to other messages<br>networks that use a different mailer/packet type, then let me know. I'll happily work on it to make a bridge<br>to open up access to things you cannot access.

...all so that you can spend your time playing on your BBS rather than managing messages, failures or keeping an<br>FTN network running.

For the BBS Sysop

For the BBS sysop, the FTN Clearing Houz has the following features:

Supports BINKP network transfers

Supports EMSI network transfers (for legacy "frontend" mailers)

Supports PING responses (to netmails)

A consistent reliable echomail/netmail hub for your BBSes, while you reconfigure your BBS.

If you have more than 1 BBS, then the Clearing Houz can receive all your mail from your uplinks and feed<br>them to your BBSes.

For the FTN network operator

For the FTN network operator, the FTN Clearing Houz has the following features (or planned ones):

Supports BINKP network transfers

Supports EMSI network sessions with ZMODEM transfers

Automatic route configuration, routing netmail directly where links exist, or to the next uplink/downlink

Manages ECHO areas and FILE areas

Supports PING and TRACE responses (TRACE to be implemented)

Nodelist Management

Self service FTN Network Applications being implemented

Dynamic mail bundling for upstream and downstream nodes (no more "inbounds" and "outbounds")

Support for Fidonet Packet formats FTS-0001,<br>FSC-0039,<br>FSC-0045,<br>FSC-0048

Automatic delisting of idle nodes, including marking them HOLD, then DOWN

DNS server, to enable resolving of registered nodes using domain dns names FTS-5004<br>with pN.fN.nN.zN.domain.ftn , or<br>pN.fN.nN.zN.[domain dns zone]<br>syntax, including TXT and CNAME records

Other things

Other ideas that may make it into this tool:

SMTP integration

PGP signed mail and mail verification

SQRL simple authentication (so there is 1 less username/password you need to remember) Sadly SQRL never really took off,...