Files
The BBS file library — uploads, downloads, descriptions, areas.
Layout
| Concept | What it is |
|---|---|
| File | A single uploaded file with description + uploader |
| File area | A bucket of files — e.g. "Software", "Music" |
| TIC | A FidoNet-distributed file echo (network-replicated) |
Browsing
- Web:
/files/shows a tree of areas. Click into one to see
the file list with descriptions and download links. - Terminal: main menu F. Terminal downloads happen via Zmodem
if the client supports it; otherwise base64-into-a-pager
fallback. - FTP: if the sysop has turned it on (
FTP_ENABLED, off by
default), any plain FTP client can browse and download from the
same file areas — anonymous access is read-only and limited to
active, non-sysop-only areas; logged-in users can also upload
where an area's upload permission allows it. Default port21.
Uploading
Logged-in users can upload to the Uploads area by default.
Sysops can change which areas accept user uploads.
Per-file metadata:
- Description (required)
- Tags (optional, comma-separated)
- Replaces (older file? link them so the system marks one as
superseded) - License (optional)
Virus scanning
The sysop can wire ClamAV via /admin/files/virus-scan/. Uploads
are scanned on arrival; infected files are quarantined to a
sysop-only area.
Descriptions
ANetBBS reads FILE_ID.DIZ from inside .zip / .rar / .7z
uploads and uses it as the description if you didn't provide one.
Common BBS-scene practice.
TIC distribution
For files received via TIC Processor, the file lands in the
configured TIC area, its .tic companion is parsed, and the
description is read from the Desc: line.
Every install ships with 9 such areas already configured (though
unsubscribed by default) under ANotherNetwork — tags
ANN.FILES.NODELIST, ANN.FILES.INFOPACK, ANN.FILES.BBSSOFT,
ANN.FILES.DOORS, ANN.FILES.EBOOKS, ANN.FILES.LINUX,
ANN.FILES.RETRO, ANN.FILES.ANSIART, and ANN.FILES.TEST.
This works in both directions: uploading a file into any
network-attached file area (not just ANotherNetwork's) automatically
queues it for outbound distribution to every subscribed peer — no
separate "publish" step. See the Outbound section of
TIC Processor for exactly which upload paths trigger this.
Quotas
Sysop sets per-user upload quotas under /admin/users/<id>/. Default
is no quota.