Logos Research retweetledi
Recently published a piece on Logos Basecamp — the launcher and unified surface of the Logos stack.
The only way to escape the censorship and monitoring of the modern world is to build local-first systems that protect privacy by default.
Here are a few things I wanted to draw out for anyone building on, or thinking about building on, Logos:
1/ Basecamp doesn't do the work — it surfaces it. Wallet logic lives in the blockchain module, messaging in comms, file-sharing in storage. Basecamp is what makes a collection of modules feel like one coherent experience to the user.
2/ It's module-agnostic by design. Whatever modules you have installed, Basecamp discovers them and loads their UIs. The stack composition is defined by the modules you choose — not by the launcher. That's what makes specialised Logos distributions possible.
3/ There are three ways into the stack for users: Basecamp (the default launcher), a standalone app (single binary, bundled UI), or a headless node (CLI only, for validators and infra). Same stack underneath; different surfaces on top.
4/ For developers: QML is the path of least resistance. Scaffold a module with the lm CLI, ship it, and Basecamp auto-loads its UI on next launch. The Package Manager handles discovery. You compose against the rest of the stack rather than rebuilding it.
5/ Basecamp is in active development on Testnet v0.1.2. Testnet v0.2 is when it starts becoming the first-class user experience for operating on the frontier.
Read the full piece: press.logos.co/article/logos-…
English
