🬐 🬠 🬞🬂🬏 🬟 🬑 🬟 🬑 ff2596c2.. ╭ff2596c2..╮ see-em: 🬋🬋🬋 🬋🬋🬋 🬋 🬋 files │diff │ refs discuss issues new login 🬐 🬠 🬐 🬠 🬑 🬟 🬰 ╰──────────╯ user

╭ changed ╮ │README.md│ ╰─────────╯ ╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │33 Haxy will provide a text user interface (TUI) over SSH, so you can browse the Haxy instance entirely from your terminal. These are sometimes called SSH apps. One big advantage they have is that you are automatically authenticated with your SSH key, so creating an account on a Haxy instance and associating it with your SSH public key can be done instantly. │ │34 │ │35 Additionally, Haxy will provide a web UI for a more typical experience in a web browser. To avoid having separate UI codebases, the web UI will simply render the TUI in your browser. This sounds frightening but it can be done in an accessible way that is usable for screen readers and mobile devices. See [an early look](https://www.youtube.com/watch?v=08AnxqnhTcs) at how the web UI will work. │ │36 + │ │37 +Here's what it looks like so far in the terminal and on the web: │ │38 │ │39 +<p align="center"> │ │40 +<a href="https://raw.githubusercontent.com/xit-vcs/haxy/refs/heads/master/screenshots/terminal.avif"><img src="screenshots/terminal.avif" width="49%" /></a> │ │41 +<a href="https://raw.githubusercontent.com/xit-vcs/haxy/refs/heads/master/screenshots/web.avif"><img src="screenshots/web.avif" width="49%" /></a> │ │42 +</p> │ │43 + │ │44 ## Why not Radicle? │ │45 │ │46 The main difference between Haxy's design and [Radicle](https://radicle.dev/) is that Haxy is not peer-to-peer. While a p2p architecture can be useful in free speech contexts, it can lead to a significant amount of complexity and make it more difficult to have a consistently good experience. Haxy is *federated* in the sense that anyone can run a Haxy instance, and your projects can be easily moved between them. I believe that is pragmatically the kind of decentralization that people want, and it significantly simplifies the implementation.│ ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭ added ──────────────────╮ │screenshots/terminal.avif│ ╰─────────────────────────╯ ╭ added ─────────────╮ │screenshots/web.avif│ ╰────────────────────╯