Skip to content

Vision/3 Bundle v0.4.0

Choose a tag to compare

View all tags
@robbiew robbiew released this 22 Jul 00:28
· 49 commits to main since this release
v0.4.0
d55234b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Vision/3 Full Distribution v0.4.0

Each bundle is a full distribution: extract and run. No need to build from source or clone the vision3 repo.

TUI-only echomail configuration: every FTN task — creating networks, changing
hubs, resetting binkd.conf — can now be done entirely from the config editor,
with no JSON or binkd.conf hand-editing.

Event scheduler

  • The scheduler now always runs; individual events are the enable/disable control. The top-level enabled flag in events.json is deprecated and ignored (existing configs with enabled: false self-heal on upgrade — a deprecation notice is logged). Seeded events remain individually disabled, so fresh installs stay quiet until events are enabled.

Echomail / FTN configuration

  • Echomail Links is now the source of truth for your hub: link records gain Hostname and Port fields (wizard-filled for new networks; port defaults to 24554). Saving from the config editor updates or creates the matching binkd.conf node line, so a hub change is a single TUI edit.
  • Per-network poll events follow a changed hub address on save, and are created automatically for any network whose link has a hostname — manually created networks poll their hub with no Events-editor setup.
  • Deleting binkd.conf is now a supported reset: on the next config-editor save it is regenerated completely from your configuration (identity, domains with zones derived from your addresses, address lines, and hub node lines).
  • Manually created networks are first-class: the Network Name field normalizes to the lowercase binkd domain (hubs expect fsxnet, not FSXNET), matching the wizard's behavior.
  • Hardening: binkd.conf parsing no longer uses a line-length-limited scanner anywhere (an oversized line could previously truncate a rewritten file), appended node lines are stably sorted, and sysop-added flags on poll events survive hub retargeting.

Quick start

  1. Download the archive for your platform (see Assets below).
  2. Extract to a directory (e.g. /opt/vision3 or C:\vision3).
  3. From that directory, optionally run once: ./setup.sh (Unix) or .\setup.ps1 (Windows) to generate the SSH host key.
  4. 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.json for 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
Assets 10
Loading