ANotherNetwork

The Echomail/QWK network every ANetBBS install ships
pre-joined to. It exists so a fresh install isn't a ghost town —
there's somewhere to talk to other ANetBBS sysops and users from
day one, the same way classic Synchronet installs shipped pre-joined
to Dove-Net.

• Hub: bbs.a-net.fyi
• Zone: 1200
• Transport: BinkP (message + file echoes) or QWK/FTP, your
  choice — both reach the same areas via the hub's tosser

What's seeded automatically

On first run, two network entries and 35 areas are created — all
inactive / unsubscribed by default. Nothing polls or shows up on
your boards until a sysop turns areas on.

Two network rows (/admin/echomail/, both is_active=False
until you fill in your node info):

• ANotherNetwork — BinkP transport, bbs.a-net.fyi:24554
• ANotherNetwork (QWK) — QWK-over-FTP transport, same hub

26 message echo areas (tag prefix ANN.), grouped by category:

9 file echo areas (tag prefix ANN.FILES.): Weekly Nodelists,
Infopacks, BBS Software, Door Games & Utilities, eBooks,
Linux/Open-Source Files, Retro Computing Files,
ANSI/ASCII Art Collections, and a Testing-only area. See Files
and TIC Processor for how file-echo distribution actually moves
bytes.

Turning it on

1. Pick which of the 26 message areas and 9 file areas you actually
   want — subscribe to them under Echomail Admin /
   Files Admin. Nothing forces you to run all of them.
2. Get a node number (see below) and fill in the address/password on
   whichever of the two network rows matches your transport.
3. Flip that network row's Active flag on.

Getting your own node number

You need a node number before your BinkP/QWK sessions with the hub
will authenticate. Two ways to apply:

• Terminal: Echomail main menu → pick the Echomail Networks
  screen → A = Apply for ANotherNetwork QWK node. Fill in your
  BBS name, a proposed packet ID, sysop name, contact email, and BBS
  address. On the hub itself this writes straight into the request
  queue; on any other install it POSTs to the real hub's
  /qwkhub/apply endpoint instead (fixed in v1.0b2.29 — it used to
  wrongly write to whichever install you ran the wizard from).
• Hub side: the sysop running bbs.a-net.fyi reviews pending
  applications at /admin/echomail/hub/qwk/requests and
  approves or denies them; approving auto-creates the QWK node
  record with a generated password.

There's no equivalent self-service flow for a BinkP node number
yet — for BinkP transport, contact the hub sysop directly and they'll
add your node under /admin/echomail/hub/binkp/.

See also

• Echomail — how message-echo distribution works
• BinkP Setup — joining any FTN-style network, including this one
• QWK — the offline-reading side, and Hub Management for QWK nodes
• TIC Processor — file-echo distribution mechanics
• Sysop Control Panel — where Hub Management lives if you run the hub