unseenet 0.1.0__tar.gz

unseenet-0.1.0/LICENSE

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

unseenet-0.1.0/NOTICE

@@ -0,0 +1,11 @@
+Unseenet
+Copyright 2026 Andreas Lorensen and Unseenet contributors
+
+The source code is licensed under the Apache License, Version 2.0 (LICENSE).
+
+The protocol specification in rfc/ and the logo in assets/ are licensed
+under the Creative Commons Attribution 4.0 International License
+(CC BY 4.0), see rfc/LICENSE.md and assets/LICENSE.md.
+
+The logo wordmark is DejaVu Sans Mono Bold converted to outlines
+(Bitstream Vera / DejaVu font license).

unseenet-0.1.0/PKG-INFO

@@ -0,0 +1,247 @@
+Metadata-Version: 2.4
+Name: unseenet
+Version: 0.1.0
+Summary: A Usenet-style, decentralized and encrypted discussion network over Tor onion services
+Author: Andreas Lorensen
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/andlo/unseenet
+Project-URL: Documentation, https://andlo.github.io/unseenet/
+Project-URL: Changelog, https://github.com/andlo/unseenet/blob/main/CHANGELOG.md
+Project-URL: Specification, https://github.com/andlo/unseenet/tree/main/rfc
+Keywords: usenet,nntp,tor,onion,decentralized,encryption,bbs,privacy
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications :: Usenet News
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: pynacl>=1.5
+Requires-Dist: python-socks[asyncio]>=2.4
+Provides-Extra: tui
+Requires-Dist: textual>=0.80; extra == "tui"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: textual>=0.80; extra == "dev"
+Dynamic: license-file
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="assets/logo-dark.svg">
+    <img src="assets/logo-light.svg" alt="Unseenet" width="440">
+  </picture>
+</p>
+
+**📖 Documentation: [andlo.github.io/unseenet](https://andlo.github.io/unseenet/)**
+
+**Usenet, unseen.** A decentralized, encrypted discussion network in the
+spirit of old Usenet and BBSes — groups and chats you can reach by
+running one program from a USB stick, carried between independently run
+nodes over Tor onion services.
+
+> Status: **pre-alpha / design phase.** The protocol is being written
+> down in the [UN-RFC series](rfc/). The Python code here is a first
+> working skeleton of it. Nothing is stable yet, and it has not had a
+> security review. Do not rely on it to protect anyone yet.
+
+---
+
+## The idea
+
+In the old days, you connected to *your* news server. Your server
+exchanged articles with other servers, and before long your post had
+travelled around the world. Nobody owned Usenet. Anyone could run a
+server. You could read it with any newsreader.
+
+Unseenet brings that model back, with what we have learned since:
+
+- **Easy access.** One program, no installation, no account, no public
+  IP, no port forwarding. Put it on a USB stick and go.
+- **Decentralized.** Anyone can run a node — on a Raspberry Pi, a
+  homelab container, a VPS. Nodes replicate groups to each other the
+  way Usenet servers did. There is no central server and no company.
+- **Encrypted where it matters.** Closed groups are end-to-end
+  encrypted. The nodes that carry them see only ciphertext.
+- **Hard to seize.** The client keeps everything in one encrypted
+  vault. Nodes never hold group keys. A stolen stick or a seized server
+  reveals as little as possible.
+- **Hidden.** Every node is a Tor onion service. Nobody needs to know
+  where a node is, or who is reading.
+- **Open protocol.** Specified in numbered RFC-style documents, so
+  others can write their own nodes and clients — exactly like in the
+  old days.
+
+## How it works
+
+```
+  you (USB stick)                 the network
+  +-----------+     Tor     +--------+  Tor  +--------+
+  | unseenet  | <---------> | node A | <---> | node B | <--->  ...
+  |  client   |   ONNTP     +--------+       +--------+
+  +-----------+                 ^                 ^
+   encrypted vault              +---- node C -----+
+```
+
+- **Articles** are signed with the author's key. Their Message-ID is a
+  hash of their content, so they cannot be forged or altered in transit.
+- **Groups** are owned. A group's name includes a fingerprint of its
+  owner's key (`dk.snak@ab3k5x7qwe2rtz4m`), so nobody can hijack it, and
+  its settings live in a signed *manifest*.
+- **Group types** are chosen by the owner:
+
+  | Type        | Read         | Post                              | Encrypted |
+  |-------------|--------------|-----------------------------------|-----------|
+  | `open`      | anyone       | anyone                            | no        |
+  | `moderated` | anyone       | moderators, or with approval      | no        |
+  | `channel`   | anyone       | owner and chosen posters          | no        |
+  | `closed`    | members only | members only                      | yes       |
+
+- **Spam** is priced, not policed: every post carries a small
+  proof-of-work ("postage"), a fraction of a second for a person, costly
+  in bulk.
+- **Three authorities, no rulers.** Group owners decide who may post in
+  their group. Node operators decide which groups and peers they carry.
+  Readers decide what they see.
+- **Text only.** No binaries. Articles are at most 64 KiB. That keeps
+  nodes small and their operators out of trouble.
+- **Standard tools.** The wire protocol, ONNTP, is a strict profile of
+  NNTP. Classic newsreaders can talk to a node.
+
+## The specification
+
+The protocol is defined in the **UN-RFC** series. The documents are the
+authority; this code is just one implementation.
+
+| No. | Title |
+|-----|-------|
+| [0000](rfc/un-rfc-0000.md) | The Unseenet Request for Comments Process |
+| [0001](rfc/un-rfc-0001.md) | Architecture and Terminology |
+| [0002](rfc/un-rfc-0002.md) | Article Format |
+| [0003](rfc/un-rfc-0003.md) | Identities, Keys and Cryptographic Primitives |
+| [0004](rfc/un-rfc-0004.md) | Groups, Manifests and Access Control |
+| [0005](rfc/un-rfc-0005.md) | ONNTP: Transport and Peering over Onion Services |
+| [0006](rfc/un-rfc-0006.md) | Proof-of-Work Postage |
+| [0007](rfc/un-rfc-0007.md) | Protecting Data at Rest |
+
+Want to change the protocol or build something compatible? Read
+[UN-RFC 0000](rfc/un-rfc-0000.md) for how.
+
+## Trying it
+
+Requires Python 3.11+ and the `tor` binary (`dnf install tor` / `apt install tor`).
+
+### The client
+
+```bash
+pipx install "unseenet[tui]"
+unseenet-tui
+```
+
+(or from a clone: `pip install -e ".[tui]"`)
+
+On first start you choose a passphrase for your vault, a display name, and
+the node to connect to (its `.onion` address). Then:
+
+| Key | |
+|-----|---|
+| `g` | browse the node's groups and subscribe |
+| `n` / `r` | new post / reply (Ctrl+S sends) |
+| `c` | create a group (open, moderated, channel or closed) |
+| `k` | show your key, so a group owner can invite you |
+| `i` | invite someone to a closed group you own |
+| `j` | join a group by ID or `unseenet:join` link |
+| `F5` | refresh (also happens every 30 seconds) |
+
+Everything is kept in `unseenet.vault`, encrypted, next to where you run it,
+and the posts you have fetched stay readable offline.
+There is also a plain command line client, `unseenet --help`.
+
+### A node
+
+On Debian or Ubuntu (a Proxmox LXC or a Raspberry Pi is plenty):
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/andlo/unseenet/main/deploy/install-node.sh | sudo bash
+```
+
+It installs Tor and the node as a systemd service and prints the node's
+`.onion` address. The full guide - configuration, peering, backup,
+security and troubleshooting - is in the
+[documentation](https://andlo.github.io/unseenet/node/install/). To peer with a friend's node, add a `[[peer]]` section
+to `/home/unseenet/node.toml` on both nodes (same `password`, each using
+the other's `name` and address) and restart with
+`systemctl restart unseenet-node`.
+
+For development, a node can run without Tor:
+`unseenet-node --no-tor --data /tmp/node --listen 127.0.0.1:1119`.
+
+## Talk about Unseenet - on Unseenet
+
+Two open groups are carried by the project's test nodes:
+
+| Group | For |
+|-------|-----|
+| `unseenet@ph5fc5hop5232qsz` | The project: protocol, software, ideas, questions |
+| `unseenet.test@ph5fc5hop5232qsz` | Test posts - say hello, try replies |
+
+Both are owned by the project key
+`ed25519:det5dxevwbk36eds2indrzlazyri3fq3bgdzw6kx4ems3o267sya`.
+Connect to the test node
+`f6vnchi5p7ll4yn6yot6cz4ohzuxy3uhc3kztafuwn3zlyoup6tn64qd.onion`,
+press `j` in the TUI and paste a group ID (or `g` to browse).
+The test nodes may be reset at any time while Unseenet is pre-alpha.
+
+## Roadmap
+
+- [x] Protocol drafts UN-RFC 0000–0007
+- [x] Article signing, content-derived Message-IDs, postage
+- [x] Manifests, four group types, moderation approvals, cancels
+- [x] Closed groups: epochs, member keys, sealed envelopes, E2E encryption
+- [x] Node: ONNTP server, validation, streaming feeds to peers
+- [x] Tor: own process, onion service via control port, SOCKS
+- [x] Client: encrypted vault, command line
+- [x] First real test: two nodes peering over Tor
+- [x] TUI client (first version): groups, threads, posting, closed groups, invites
+- [x] Node install script and systemd service
+- [x] Encrypted offline cache; documentation site; releases on PyPI
+- [ ] Pull catch-up between nodes (NEWNEWS)
+- [ ] Chat view in the TUI
+- [ ] Portable builds with bundled Tor for USB (Linux, Windows, macOS)
+- [ ] Low-latency chat delivery (UN-RFC 0008)
+- [ ] Moderation submission queue (UN-RFC 0009)
+- [ ] Node discovery (UN-RFC 0010)
+- [ ] Independent security review
+- [ ] A second, independent implementation
+
+## Contributing
+
+Ideas, criticism and code are welcome. Protocol changes go through the
+UN-RFC process; code changes through ordinary pull requests. See
+[docs/development.md](docs/development.md) for architecture and design
+decisions.
+
+## På dansk
+
+Unseenet er et decentralt og krypteret diskussionsnet i stil med det
+gamle Usenet og BBS'erne. Du kører én klient, gerne fra en USB-pind,
+kobler dig på en node over Tor, og noderne udveksler grupper med
+hinanden. Åbne grupper er som det gamle Usenet; lukkede grupper er
+end-to-end-krypterede, så noderne kun ser støj. Protokollen beskrives i
+RFC-lignende dokumenter, så alle kan lave kompatible noder og klienter.
+
+## License
+
+- Code: [Apache License 2.0](LICENSE)
+- Protocol specification (`rfc/`) and logo (`assets/`):
+  [CC BY 4.0](rfc/LICENSE.md) — copy, quote and implement freely, with credit
+
+Anyone may implement the protocol; no license is needed for that.

unseenet-0.1.0/README.md

@@ -0,0 +1,211 @@
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="assets/logo-dark.svg">
+    <img src="assets/logo-light.svg" alt="Unseenet" width="440">
+  </picture>
+</p>
+
+**📖 Documentation: [andlo.github.io/unseenet](https://andlo.github.io/unseenet/)**
+
+**Usenet, unseen.** A decentralized, encrypted discussion network in the
+spirit of old Usenet and BBSes — groups and chats you can reach by
+running one program from a USB stick, carried between independently run
+nodes over Tor onion services.
+
+> Status: **pre-alpha / design phase.** The protocol is being written
+> down in the [UN-RFC series](rfc/). The Python code here is a first
+> working skeleton of it. Nothing is stable yet, and it has not had a
+> security review. Do not rely on it to protect anyone yet.
+
+---
+
+## The idea
+
+In the old days, you connected to *your* news server. Your server
+exchanged articles with other servers, and before long your post had
+travelled around the world. Nobody owned Usenet. Anyone could run a
+server. You could read it with any newsreader.
+
+Unseenet brings that model back, with what we have learned since:
+
+- **Easy access.** One program, no installation, no account, no public
+  IP, no port forwarding. Put it on a USB stick and go.
+- **Decentralized.** Anyone can run a node — on a Raspberry Pi, a
+  homelab container, a VPS. Nodes replicate groups to each other the
+  way Usenet servers did. There is no central server and no company.
+- **Encrypted where it matters.** Closed groups are end-to-end
+  encrypted. The nodes that carry them see only ciphertext.
+- **Hard to seize.** The client keeps everything in one encrypted
+  vault. Nodes never hold group keys. A stolen stick or a seized server
+  reveals as little as possible.
+- **Hidden.** Every node is a Tor onion service. Nobody needs to know
+  where a node is, or who is reading.
+- **Open protocol.** Specified in numbered RFC-style documents, so
+  others can write their own nodes and clients — exactly like in the
+  old days.
+
+## How it works
+
+```
+  you (USB stick)                 the network
+  +-----------+     Tor     +--------+  Tor  +--------+
+  | unseenet  | <---------> | node A | <---> | node B | <--->  ...
+  |  client   |   ONNTP     +--------+       +--------+
+  +-----------+                 ^                 ^
+   encrypted vault              +---- node C -----+
+```
+
+- **Articles** are signed with the author's key. Their Message-ID is a
+  hash of their content, so they cannot be forged or altered in transit.
+- **Groups** are owned. A group's name includes a fingerprint of its
+  owner's key (`dk.snak@ab3k5x7qwe2rtz4m`), so nobody can hijack it, and
+  its settings live in a signed *manifest*.
+- **Group types** are chosen by the owner:
+
+  | Type        | Read         | Post                              | Encrypted |
+  |-------------|--------------|-----------------------------------|-----------|
+  | `open`      | anyone       | anyone                            | no        |
+  | `moderated` | anyone       | moderators, or with approval      | no        |
+  | `channel`   | anyone       | owner and chosen posters          | no        |
+  | `closed`    | members only | members only                      | yes       |
+
+- **Spam** is priced, not policed: every post carries a small
+  proof-of-work ("postage"), a fraction of a second for a person, costly
+  in bulk.
+- **Three authorities, no rulers.** Group owners decide who may post in
+  their group. Node operators decide which groups and peers they carry.
+  Readers decide what they see.
+- **Text only.** No binaries. Articles are at most 64 KiB. That keeps
+  nodes small and their operators out of trouble.
+- **Standard tools.** The wire protocol, ONNTP, is a strict profile of
+  NNTP. Classic newsreaders can talk to a node.
+
+## The specification
+
+The protocol is defined in the **UN-RFC** series. The documents are the
+authority; this code is just one implementation.
+
+| No. | Title |
+|-----|-------|
+| [0000](rfc/un-rfc-0000.md) | The Unseenet Request for Comments Process |
+| [0001](rfc/un-rfc-0001.md) | Architecture and Terminology |
+| [0002](rfc/un-rfc-0002.md) | Article Format |
+| [0003](rfc/un-rfc-0003.md) | Identities, Keys and Cryptographic Primitives |
+| [0004](rfc/un-rfc-0004.md) | Groups, Manifests and Access Control |
+| [0005](rfc/un-rfc-0005.md) | ONNTP: Transport and Peering over Onion Services |
+| [0006](rfc/un-rfc-0006.md) | Proof-of-Work Postage |
+| [0007](rfc/un-rfc-0007.md) | Protecting Data at Rest |
+
+Want to change the protocol or build something compatible? Read
+[UN-RFC 0000](rfc/un-rfc-0000.md) for how.
+
+## Trying it
+
+Requires Python 3.11+ and the `tor` binary (`dnf install tor` / `apt install tor`).
+
+### The client
+
+```bash
+pipx install "unseenet[tui]"
+unseenet-tui
+```
+
+(or from a clone: `pip install -e ".[tui]"`)
+
+On first start you choose a passphrase for your vault, a display name, and
+the node to connect to (its `.onion` address). Then:
+
+| Key | |
+|-----|---|
+| `g` | browse the node's groups and subscribe |
+| `n` / `r` | new post / reply (Ctrl+S sends) |
+| `c` | create a group (open, moderated, channel or closed) |
+| `k` | show your key, so a group owner can invite you |
+| `i` | invite someone to a closed group you own |
+| `j` | join a group by ID or `unseenet:join` link |
+| `F5` | refresh (also happens every 30 seconds) |
+
+Everything is kept in `unseenet.vault`, encrypted, next to where you run it,
+and the posts you have fetched stay readable offline.
+There is also a plain command line client, `unseenet --help`.
+
+### A node
+
+On Debian or Ubuntu (a Proxmox LXC or a Raspberry Pi is plenty):
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/andlo/unseenet/main/deploy/install-node.sh | sudo bash
+```
+
+It installs Tor and the node as a systemd service and prints the node's
+`.onion` address. The full guide - configuration, peering, backup,
+security and troubleshooting - is in the
+[documentation](https://andlo.github.io/unseenet/node/install/). To peer with a friend's node, add a `[[peer]]` section
+to `/home/unseenet/node.toml` on both nodes (same `password`, each using
+the other's `name` and address) and restart with
+`systemctl restart unseenet-node`.
+
+For development, a node can run without Tor:
+`unseenet-node --no-tor --data /tmp/node --listen 127.0.0.1:1119`.
+
+## Talk about Unseenet - on Unseenet
+
+Two open groups are carried by the project's test nodes:
+
+| Group | For |
+|-------|-----|
+| `unseenet@ph5fc5hop5232qsz` | The project: protocol, software, ideas, questions |
+| `unseenet.test@ph5fc5hop5232qsz` | Test posts - say hello, try replies |
+
+Both are owned by the project key
+`ed25519:det5dxevwbk36eds2indrzlazyri3fq3bgdzw6kx4ems3o267sya`.
+Connect to the test node
+`f6vnchi5p7ll4yn6yot6cz4ohzuxy3uhc3kztafuwn3zlyoup6tn64qd.onion`,
+press `j` in the TUI and paste a group ID (or `g` to browse).
+The test nodes may be reset at any time while Unseenet is pre-alpha.
+
+## Roadmap
+
+- [x] Protocol drafts UN-RFC 0000–0007
+- [x] Article signing, content-derived Message-IDs, postage
+- [x] Manifests, four group types, moderation approvals, cancels
+- [x] Closed groups: epochs, member keys, sealed envelopes, E2E encryption
+- [x] Node: ONNTP server, validation, streaming feeds to peers
+- [x] Tor: own process, onion service via control port, SOCKS
+- [x] Client: encrypted vault, command line
+- [x] First real test: two nodes peering over Tor
+- [x] TUI client (first version): groups, threads, posting, closed groups, invites
+- [x] Node install script and systemd service
+- [x] Encrypted offline cache; documentation site; releases on PyPI
+- [ ] Pull catch-up between nodes (NEWNEWS)
+- [ ] Chat view in the TUI
+- [ ] Portable builds with bundled Tor for USB (Linux, Windows, macOS)
+- [ ] Low-latency chat delivery (UN-RFC 0008)
+- [ ] Moderation submission queue (UN-RFC 0009)
+- [ ] Node discovery (UN-RFC 0010)
+- [ ] Independent security review
+- [ ] A second, independent implementation
+
+## Contributing
+
+Ideas, criticism and code are welcome. Protocol changes go through the
+UN-RFC process; code changes through ordinary pull requests. See
+[docs/development.md](docs/development.md) for architecture and design
+decisions.
+
+## På dansk
+
+Unseenet er et decentralt og krypteret diskussionsnet i stil med det
+gamle Usenet og BBS'erne. Du kører én klient, gerne fra en USB-pind,
+kobler dig på en node over Tor, og noderne udveksler grupper med
+hinanden. Åbne grupper er som det gamle Usenet; lukkede grupper er
+end-to-end-krypterede, så noderne kun ser støj. Protokollen beskrives i
+RFC-lignende dokumenter, så alle kan lave kompatible noder og klienter.
+
+## License
+
+- Code: [Apache License 2.0](LICENSE)
+- Protocol specification (`rfc/`) and logo (`assets/`):
+  [CC BY 4.0](rfc/LICENSE.md) — copy, quote and implement freely, with credit
+
+Anyone may implement the protocol; no license is needed for that.