UNC

UNC is a suite of Reticulum-native tools for resilient file sharing, catalog federation, chat rooms, and room-driven automation.

It is built for networks that are local, slow, intermittent, experimental, private, rural, improvised.

UNC is not a cloud platform.
UNC is not a social network.
UNC is not an account system.

It is a set of tools for finding, sharing, syncing, and communicating without assuming one central service owns the whole experience.

unc (client)

Peer-to-peer file search, cataloging, and direct transfer over Reticulum.

Projects

unc_chat

Room-based chat with public/private rooms, key epochs, invites, and retention policies.

Chat

unc_hub

Catalog hubs that index files, track presence, answer search queries, and eventually federate.

Architecture

unc_agent

Room-native remote operations experiments using signed command and result events.

Agent

Why UNC exists

File sharing and online communities used to feel like shared places: searchable, weird, user-operated, and not entirely owned by companies. Over time, much of that became platform infrastructure: accounts, ads, policies, surveillance, recommendations, and monetized attention.

UNC is a small protest against that.

The goal is low-friction sharing and communication that can work across normal networks, local networks, radio links, mesh links, and other constrained paths.

Core ideas

  • local-first where possible
  • direct peer transfer
  • Reticulum-native networking
  • content-addressed file identity
  • hubs as catalogs, not file relays
  • federation instead of platform ownership
  • anonymous-by-default identities
  • human-operable tools
  • weird networks welcome

Current status

The file-sharing works: index files, register with a hub, search, and fetch. The GUI and packaging are still early. The chat and agent layers are active prototypes, not hardened production systems, but they work.