Binary & Bus, Sys. emblemFISP — File Interchange System Protocol


Publisher: Binary & Bus, Sys. (bbsys.net, B2/)
Document: FISP-0.1
Status: Experimental Draft
Publication date: 2026-11-20
Canonical URL: https://bbsys.net/doc/fisp/
Transport: TCP (default port 7070)

Abstract

FISP (File Interchange System Protocol) is a read-only, self-hosted file interchange protocol. A FISP server exposes a directory of files over a simple UTF-8 text protocol on TCP. A FISP client connects to a server by address, retrieves a flat manifest of available files, and downloads them.

FISP is deliberately small: it has no accounts, no database, no encryption, no discovery, and no server-declared identity. It is an open protocol, and the protocol name belongs to no one. The wire version identifier is FISP.

Protocol overview

Connections run over TCP (default port 7070) with line-oriented UTF-8 commands and raw byte file bodies terminated by the five-byte trailer \nEND\n:

Home directory & access control

A server is pointed at a home directory (default ./fisp via --home) containing the required files/ content root and optional control files (whitelist.txt, blacklist.txt, and key.txt, which are never served or listed):

Specification & planned implementations

The FISP-0.1 specification is published for review and implementation work:

Security & scope notes

FISP provides no transport encryption and no server authentication; access keys and files travel in plaintext, and peer identity is based on the TCP source IP address (meaning NAT, proxies, tunnels, or shared networks affect IP-based controls and per-peer limits). Uploads, deletes, hierarchical directory listings, encryption, accounts, and version negotiation are explicitly out of scope.

Feedback and technical correspondence may be directed to [email protected].