UNC is moving toward a small, usable suite of Reticulum-native tools.

The north star is low-friction sharing. A user should be able to download the app, follow a short guide, configure a couple of things, and start sharing, downloading, and chatting.

Near term

  • improve GUI behavior
  • publish clearer install and deployment docs

Long term

  • improve operator and administrative features
  • explore v2 GUI updates (native Qt, etc..)
  • additional performance optimizations (we've only performed mixed synthetic/organic tests sub 75 users)
  • additional testing over different types of links (HaLow, LoRa, etc..)
  • explore interoperability with the extended Reticulum cinematic universe: LXMF/LXST/NomadNet

Completed:

Usability and safety (current)

  • configurable concurrent download limits
  • configurable upload limits
  • optional bandwidth caps
  • friend/bookmark/block controls
  • clearer online/offline availability
  • retry queue for unavailable peers
  • first-run setup flow

Groups and moderation (current)

  • group tags distinct from file tags
  • hub-local groups
  • browseable group member files
  • peer and file moderation states
  • block, ban, and quarantine behavior
  • external operator-maintained block feeds

Federation (current)

Configure multiple hubs, search them in parallel, merge results, and deduplicate.

Hubs replicate catalog state to each other using pull-based sync. The model is leaderless, operator-configured, and friendly to intermittent links. Convergence is good.

Chat and rooms (current)

  • public rooms
  • private rooms
  • room manifests
  • invite packages
  • room-key epochs
  • leave / revoke / rotate behavior
  • ephemeral and durable retention policies
  • CLI and GUI support

Agent and remote operations

The room-native agent layer is exploring:

  • trusted controller identities
  • allowlisted command execution
  • signed JSON results
  • task UUIDs
  • fleet awareness
  • artifact movement
  • long-running jobs
  • stronger trust policy
  • signed updates and rollout

Out of scope

UNC is not aiming to add:

  • advertising
  • paid rankings
  • centralized account systems
  • mandatory real-world identity
  • hidden analytics
  • platform-owned user activity logs