Tools: Difference between revisions

From Local Area Network
Parallel Wiki build: page from sourced research, source-checked 9 October 2026
 
See also: the Start a Circle chapter on this subject
Line 59: Line 59:
* [[Still to build]]
* [[Still to build]]
* [[Logos]]
* [[Logos]]
* [[Start a Circle/Resources for Activists|Resources for Activists]], in [[Start a Circle]]
* [[Start a Circle/Staying connected: Recommended Tools|Staying connected: Recommended Tools]], in [[Start a Circle]]


{{Page status|Outline}}
{{Page status|Outline}}

Revision as of 13:40, 21 October 2026

Software you install and run.

The core Logos software, Basecamp and the node, has its own pages under Logos. See Basecamp and Run a node.

Tools

  • Booth: broadcast a live stream from Basecamp over Logos Messaging, with no server or account. Prototype.
  • Medusa: a self-custody privacy wallet for the Logos Execution Zone, run as a Basecamp module. Prototype.

Each tool page has a stage: Design, Planning, Prototype, Almost done or Full Release. The page says which line from the project's own sources set the stage.

Criteria for listing a tool

The format of these criteria comes from Privacy Guides and its VPN criteria, which split each test into a minimum and a best case. A tool must meet every minimum to be listed here. The best case is what we hope to see.

Open source licence

Minimum to qualify:

  • Released under a licence approved by the Open Source Initiative or the Free Software Foundation.
  • The licence is named in the repository.

Best case:

  • A copyleft or permissive licence that matches the rest of the Logos stack.
  • Every dependency it ships is also open source.

Published code

Minimum to qualify:

  • All source code is public in a repository anyone can read.
  • A reader can build it from that source.

Best case:

  • Versioned releases with notes on what changed.
  • Signed releases, and builds that can be reproduced.
  • Dependencies pinned to exact versions.

Documentation

Minimum to qualify:

  • Install and use instructions a newcomer can follow.
  • Build instructions.

Best case:

  • A step-by-step guide from zero to working.
  • A plain statement of known limits and the threat model: what it protects against and what it does not.

Privacy

Minimum to qualify:

  • No analytics, telemetry or tracking.
  • No account or personal information needed to use it.

Best case:

  • Works over Tor or another anonymity network.
  • Keeps no logs or records of its users.
  • Keys and secrets stay on the user's own device.

Who maintains it

Minimum to qualify:

  • A named maintainer or team, or a public handle with a history of commits.
  • Some way to report bugs, such as an issue tracker.

Best case:

  • More than one active maintainer.
  • A security policy, a way to disclose bugs in private and an independent audit.
  • Says clearly whether it is an official Logos product or a community project.

See also

Page status: Outline. Stub · Outline · Usable · Guide · Star. Anyone can improve this page and change its status.