Skip to content
This repository was archived by the owner on Mar 21, 2025. It is now read-only.

Milestones

List view

  • The app will allow setting and display of local nicknames as a (required) replacement for ZeroTier network IDs and an (optional) replacement for ZeroTier addresses of the local node and peers.

    No due date
    0/1 issues closed
  • The app will be easy to install and will run correctly on aarch64/arm64 architectures (e.g. NVIDIA Jetson Nano) and armv7 architectures (e.g. Raspberry Pi 4).

    No due date
    2/2 issues closed
  • The client will able to provide network registration information through the client, for the network administrator to process.

    No due date
    0/2 issues closed
  • Since ZeroTier One comes with the network controller for all installations, each device can host its own network. There should be an interface to enable provisioning a new (private, temporary) network, quickly and easily inviting other nodes by hostname or node ID or other mechanisms, assigning them local domain names, and locking down port/protocol access with rules.

    No due date
  • The app will display known user-friendly names associated with network IDs, sourced in this milestone from the assigned hostnames in the default public registry; the app will also display the self-assigned network name reported by the ZeroTier One service. Network IDs will be reduced to identicons and, along with self-assigned names, deemphasized when user-friendly from trusted registries are known. Network names should correspond to resolvable DNS hostnames; if the network ID is looked up from the DNS hostname and the DNS hostname does not return a corroborating record, there will be a warning to the user.

    No due date
  • The app will display known user-friendly names associated with node IDs, sourced in this milestone from the assigned hostnames in the mutual ZeroTier networks. Node IDs will be reduced to identicons and deemphasized when user-friendly names are known.

    No due date
  • The user will be able to browse a registry of networks and attempt to join any network in the registry. There will be no in-app means of verifying the identity of the user or the legitimacy of the join request in this milestone - that will need to be performed out-of-band.

    No due date
  • There should be a minimum amount of work needed to get the user set up for connecting to their first network.

    No due date
    0/2 issues closed
  • The user will be able to join a ZeroTier network by entering a hostname (e.g. prakashlab.dedyn.io) which publishes its network ID in some well-known way, as a more friendly on-ramp to join a network than having to type or copy-paste a raw network ID. There will be no in-app means of verifying the identity of the user or the legitimacy of the join request in this milestone - that will need to be performed out-of-band.

    No due date
    2/4 issues closed
  • This will just be a thin graphical frontend for ZeroTier One, as a proof-of-concept for talking to the ZeroTier One service from a cross-platform Tauri application. It will not include any functionality related to registries of human-readable names as a discovery layer over the raw ZeroTier IDs.

    No due date
    12/12 issues closed