Vision/3 Bundle v0.6.0
Vision/3 Full Distribution v0.6.0
Each bundle is a full distribution: extract and run. No need to build from source or clone the vision3 repo.
V3Net node management: hubs that don't auto-approve subscribers can now
approve, ban, and remove nodes entirely from the config editor — no database
surgery or hub restart required.
V3Net
- Node Management for hub-hosted networks: press N on a hosted network in the config editor to open a node list showing each subscriber's ID, BBS details, status, and join date — with approve, ban, unban, and delete (with confirmation) actions. Requests are keystore-signed and take effect on the live hub immediately, so a pending node can start polling without a BBS restart. (Previously a hub with
autoApprove: falseleft registrations stuck in pending with no approval path.) - New hub endpoints back the screen (operator-only, signed): list nodes plus approve/ban/unban/remove, with guards against self-lockout and invalid status transitions. Banned nodes are refused at authentication.
- New "Managing Subscriber Nodes" section in the sysop V3Net configuration guide.
Quick start
- Download the archive for your platform (see Assets below).
- Extract to a directory (e.g.
/opt/vision3orC:\vision3). - From that directory, optionally run once:
./setup.sh(Unix) or.\setup.ps1(Windows) to generate the SSH host key. - Start the BBS:
./vision3(Unix) or.\vision3.exe(Windows).
Default login: felonius / password — change after first login!
Bundle contents
- Root — vision3, ue, strings, helper, v3mail, config, menuedit (main executables)
- bin/ — binkd, sexyz, sexyz.ini (and zip/unzip on Windows)
- configs/ — template configs (edit
configs/config.jsonfor your BBS) - menus/v3/ — menu set
- data/ — skeleton (users, files, logs, msgbases, ftn, infoforms, oneliners)
- ziplab/ — ZIP processing templates (BBS ad, file comment)
- scripts/examples/ — example JS scripts for the scripting engine
- setup.sh (Unix) / setup.ps1 + setup.bat (Windows) — one-time setup (SSH key, dirs)
Paths on Windows
Path strings in the JSON configs use forward slashes; they work on Windows too. For paths you edit (e.g. doors), you can use forward or backslashes.
Platforms
- linux-amd64, linux-arm64, linux-armv7
- macOS: one universal bundle (Intel + Apple Silicon), built for amd64 and arm64 then combined
- windows-amd64, windows-386