nandi/frq · README.md

nandi/frqpublic⑂ Fork 0

⑂ 719742dcbe6d54f9a46d2dd1d059f7a72286e5ba

README.md · 201 lines · 10.1 KBmarkdown    Blame HistoryRaw
A freeq client in jolt, as glimmer components on Vidya   1
3A **[freeq](https://github.com/codegod100/freeq)** client written in
4**[jolt](https://github.com/jolt-lang/jolt)**, as
5[glimmer](https://github.com/jolt-lang/glimmer) components painted by
6**[Vidya](https://tangled.org/nandi.uk/vidya)**/egui.
8It is a proof of concept port of [sleek](../sleek), which is the same client in
9Rust against egui directly. The screens are sleek's — connect, chats, chat,
10discover, settings, under a tab bar — but each is hiccup over glimmer's widget
11tags rather than immediate-mode drawing code, and state lives in ratoms instead
12of an `AppState` struct.
Sign in with Bluesky OAuth, through freeq's broker   15src/frq/atproto.jolt handle → DID → PDS → session, and the SASL payloads
16src/frq/oauth.jolt   the broker flow: login URL, loopback capture, /session
Remember an OAuth sign-in across restarts   17src/frq/store.jolt   the saved sign-in, mode 600 in the config directory
Show who is talking, with their Bluesky picture   18src/frq/avatars.jolt profile pictures, by DID or handle
Copy sleek's profiles   19src/frq/profile.jolt who someone is: the Bluesky profile behind a nick
Show the pictures people paste   20src/frq/media.jolt   image links: spot them, fetch them once, cache on disk
Send a picture by pasting it   21src/frq/upload.jolt  a pasted picture to freeq's media endpoint, as multipart
   22src/frq/av.jolt      calls: the signaling, and a handle on the media plane
Say when each thing was said   23src/frq/clock.jolt   the reader's own zone, twelve-hour times, day headings
Pick any emoji, in colour   24src/frq/emoji.jolt   the picker's catalog: every drawable emoji and its name
Sign in with a Bluesky identity   25src/frq/irc.jolt     IRC over TLS or TCP: parser, reader thread, SASL, PRIVMSG
A freeq client in jolt, as glimmer components on Vidya   26src/frq/state.jolt   the ratoms every screen reads, and `apply-msg!`
27src/frq/app.jolt     the screens
Stop mistaking a quiet connection for a closed one   30
32`FRQ_TRACE=1` prints every IRC line sent and received to stderr, which on
33Android is logcat.
A freeq client in jolt, as glimmer components on Vidya   35
Take both native libraries from one place   37Both native libraries, then the app:
A freeq client in jolt, as glimmer components on Vidya   38
Take both native libraries from one place   44`just lib` builds [jolt-native](https://gitlab.com/nandithebull/jolt-native),
Take glimmer-vidya from gitlab, so a stranger can build this   45cloning it into `.jolt-native` at the pinned commit unless you already have a
46sibling checkout, which wins. That repo is where every shared object this
47client loads comes from: `libvidya`, the retained-tree ABI glimmer paints
48through, and `libjoltmoq`, the AV media plane. They come out of one directory,
49and `just run` puts that one directory on the loader path.
   50
A freeq client in jolt, as glimmer components on Vidya   51`just run` is `jolt -M:frq` with `LD_LIBRARY_PATH` pointed at the built
52library. It connects to `irc.freeq.at:6697` over TLS and joins `#test`. Untick
53TLS on the connect screen (or point it at `127.0.0.1`) for a local server's
54plain listener:
57cargo run --release --bin freeq-server        # in the freeq checkout
Sign in with a Bluesky identity   60## Signing in
Sign in with Bluesky OAuth, through freeq's broker   62Three modes on the connect screen.
Sign in with a Bluesky identity   63
Sign in with Bluesky OAuth, through freeq's broker   64**Bluesky** (OAuth, the default way in) follows sleek's flow: frq binds a
65loopback port, puts it in `return_to`, and opens
66`auth.freeq.at/auth/login?handle=…`. The broker runs the OAuth dance with the
67PDS and redirects back to that port with the handoff in the URL *fragment*, so
68it never reaches a server as a query string. The page frq serves there has one
69job: POST the fragment back to itself. What comes back is a single-use SASL
70`web-token` and a durable `broker_token`; later connections mint a fresh token
71from the durable one at `/session` and skip the browser.
Sign in with a Bluesky identity   72
Remember an OAuth sign-in across restarts   73The durable token is saved to `$XDG_CONFIG_HOME/frq/session.edn` (mode 600) so
Connect on launch when an account is remembered   74a restart resumes without one, along with the handle and nick it belongs to —
75and it connects on its own at launch when one is there.
Remember an OAuth sign-in across restarts   76The web-token beside it is single-use and deliberately not saved. A token the
77broker no longer honours is dropped — from disk and memory — and the browser
78flow runs once more, rather than failing the same way on every Connect.
Sign in with Bluesky OAuth, through freeq's broker   80**App password** signs in without a browser, straight to the user's own PDS:
81`resolveHandle` → DID → PDS from the DID document → `createSession`. The
82password goes to that PDS and nowhere else, is never written to disk, and is
83dropped once the session exists.
Sign in with a Bluesky identity   84
Sign in with Bluesky OAuth, through freeq's broker   85Either way freeq sees only a token. The SASL mechanism is
86`ATPROTO-CHALLENGE` in both cases — `method: "web-token"`, which the server
87resolves through its own token store, or `method: "pds-session"` with the
88server's nonce echoed back so the token cannot be replayed elsewhere.
90A refused sign-in is reported and the connection carries on as a guest.
Sign in with a Bluesky identity   91
A freeq client in jolt, as glimmer components on Vidya   92
94An APK with two shared libraries and no Java: `libvidya.so` (vidya's Rust/egui
95C ABI, which owns the event loop as the NativeActivity's own library) and
96`libjoltapp.so` (frq compiled to a Chez boot image). Both native halves come
97from the vidya checkout; only the boot image is frq's.
100./android/build-apk.sh run      # build, install, launch on a connected device
101./android/build-apk.sh log      # logcat, filtered
104Needs what vidya's Android build needs — SDK, NDK r29, and a cross-built Chez
105in `~/.cache/vidya-chez-android`.
107TLS does not work there: jolt reaches OpenSSL through the dynamic loader, and
108Android has no public `libssl` to load. The connect screen falls back to the
109plain `:6667` listener on its own, which is why the plain transport is the raw
110`socket`/`connect`/`send`/`recv` calls rather than jolt's `java.net.Socket`
111surface — that surface does not work on Android either, while the syscalls do.
113## What the PoC covers
115* TLS (`:6697`, via jolt.mvn-http's OpenSSL bindings) or plain TCP (`:6667`)
116* Guest connect (`NICK`/`USER`), `001` welcome, `PING`/`PONG` keepalive
117* Auto-joins `#test` on `irc.freeq.at`
118* Join channels, channel buffers with unread counts, send and receive `PRIVMSG`
Ask for the backlog freeq restores channels without   119* Backlog on join, and `CHATHISTORY` for the channels freeq restores instead
Say when each thing was said   120* Twelve-hour timestamps from the server's own clock, with a heading wherever
121  the day changes
Answer a message, not just read that one was answered   122* A chip above a reply quoting what it answers, and a click that goes there;
123  ↩ beside a sender to answer them, with `+draft/reply` on the way out
Pick any emoji, in colour   124* Emoji reactions: colour pills under a message, ☺ beside the sender to open a
125  picker over every emoji Vidya can draw (popular first, then Unicode's own
126  groups, searchable by name), and a second click on a pill to take yours off
127  — sent as `TAGMSG`, and restored from the server's own tally when the
128  backlog comes back
Show the pictures people paste   129* Inline previews for PNG links, fetched once and cached under
Click a picture to see it full size   130  `$XDG_CACHE_HOME/frq/media`; click one to see it full size
Send a picture by pasting it   131* Ctrl+V in the draft attaches the picture on the clipboard: it is previewed
132  under the box and uploaded to freeq's media endpoint while you write the line
133  it goes with, and only on the way out does it become the link — which is the
134  whole of what sending an image over IRC means. The draft itself is never
135  written into. Text pastes as text, as it always did: the picture path is the
136  keystroke the field had no text to answer with
A freeq client in jolt, as glimmer components on Vidya   137* Join/part notices, DMs bucketed under the sender's nick
138* Discover list, search over buffers, disconnect
Remember which rooms this client has been in   139* The rooms you have opened, remembered across runs and listed in the order
140  you last used them (`$XDG_CONFIG_HOME/frq/channels.edn`)
Order the chat list by what you were last in   141* Conversations listed most recently opened first
Show who is talking, with their Bluesky picture   142* Bluesky avatars beside the sender, resolved from the DID freeq tags each
143  message with
   144* Calls: a Call button opens one in a channel, a banner offers Join where
145  somebody already has, and in one there is mute, deafen, video and leave. Mute
146  and deafen are separate — a deafened microphone still carries your voice.
147  Whoever turns a camera on appears as a tile; the self-view is labelled You
148  and sits last, where it cannot push a face you are talking to off the row
150
152Signaling is IRC and lives here: `+freeq.at/av-start`, `av-join` and `av-leave`
153go out as TAGMSGs and the server broadcasts `+freeq.at/av-state` back, which is
154what actually moves this client's state — a press is optimistic, and the server
155settles it. Losing a race to open a call (`start-collision`) is answered by
156joining the call that won rather than by reporting an error, since the person
157asked to be in a call in that room and there is one.
159Media is not IRC and is not here. Audio and video ride MoQ — Media over QUIC —
160through freeq's SFU, and that is `libjoltmoq`: Opus, H.264, capture and
161transport, lifted out of sleek rather than written a second time in jolt.
162`src/frq/av.jolt` is the whole of what frq says to it, and two of its rules
163shape this side:
165* **Nothing calls back.** Status and video are polled, drained by a timer that
166  glimmer runs on the loop thread — the only thread allowed to touch a node.
167* **A frame is borrowed.** The decoder's own buffer is handed to Vidya as a
168  pointer and painted by an `:image` with a `:feed`. The pixels never become a
169  jolt value and are never copied on this side, which is the only way thirty
170  frames a second is affordable here.
172The SFU is dialled once the server has minted a token, not when we ask to join:
173a remote SFU refuses a connection without one, and the MoQ client then retries
174in a loop that looks exactly like a hang.
A freeq client in jolt, as glimmer components on Vidya   175
176
178* **TLS and plain TCP only** — no WebSocket, no iroh. On Android, plain only.
Sign in with Bluesky OAuth, through freeq's broker   179* **No `did:key` signing, no credential gates, no E2EE.** Sign-in of either
180  kind needs TLS, so it is desktop-only — the Android build connects as a
181
Remember an OAuth sign-in across restarts   182* **Only the broker token is persisted**, and only for OAuth. An app-password
183  sign-in is not remembered.
Show the pictures people paste   184* **Previews are PNG only** — the tree backend's decoder reads no other
185  format, and a fetch needs TLS, so the phone shows links. The link is left in
186  place either way.
187* **Nothing evicts the media cache.**
   188* **Calls are desktop-only.** `libjoltmoq` is not built for Android here, and
189  the camera and microphone paths that are would still need the runtime
190  permissions the APK does not ask for.
191* **One call at a time**, which is the media plane's rule and the microphone's.
192* **No call is offered in a DM** — freeq's AV signaling is a channel's.
Send a picture by pasting it   193* **Pasting a picture needs a sign-in and a desktop.** The upload is filed
194  under the DID of a live session, so a guest cannot make one; and it is read
195  off the clipboard through the ABI's `vidya_clipboard_image_png`, which
196  arboard backs on desktop and nothing backs on Android. It also shares
197  nothing to your PDS and posts nothing to Bluesky — those fields are opt-in
198  and this client does not send them.
   199* **No scrollback trimming or threads.**
Stop mistaking a quiet connection for a closed one   200* A sent line waits up to 200ms for the reader thread to flush it.
A freeq client in jolt, as glimmer components on Vidya   201* Message lists are keyed vboxes; glimmer-vidya has no `:listbox` yet.

A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	1	# frq
	2
	3	A [freeq](https://github.com/codegod100/freeq) client written in
	4	[jolt](https://github.com/jolt-lang/jolt), as
	5	[glimmer](https://github.com/jolt-lang/glimmer) components painted by
	6	[Vidya](https://tangled.org/nandi.uk/vidya)/egui.
	7
	8	It is a proof of concept port of [sleek](../sleek), which is the same client in
	9	Rust against egui directly. The screens are sleek's — connect, chats, chat,
	10	discover, settings, under a tab bar — but each is hiccup over glimmer's widget
	11	tags rather than immediate-mode drawing code, and state lives in ratoms instead
	12	of an `AppState` struct.
	13
	14	```
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	15	src/frq/atproto.jolt handle → DID → PDS → session, and the SASL payloads
	16	src/frq/oauth.jolt the broker flow: login URL, loopback capture, /session
Remember an OAuth sign-in across restarts 4aa71e7 nandi 20d ago	17	src/frq/store.jolt the saved sign-in, mode 600 in the config directory
Show who is talking, with their Bluesky picture f5548bd nandi 20d ago	18	src/frq/avatars.jolt profile pictures, by DID or handle
Copy sleek's profiles b79ebc4 nandi 19d ago	19	src/frq/profile.jolt who someone is: the Bluesky profile behind a nick
Show the pictures people paste 56cdac3 nandi 20d ago	20	src/frq/media.jolt image links: spot them, fetch them once, cache on disk
Send a picture by pasting it 8a491ba nandi 19d ago	21	src/frq/upload.jolt a pasted picture to freeq's media endpoint, as multipart
Calls f31ad3d nandi 19d ago	22	src/frq/av.jolt calls: the signaling, and a handle on the media plane
Say when each thing was said dbf3b86 nandi 20d ago	23	src/frq/clock.jolt the reader's own zone, twelve-hour times, day headings
Pick any emoji, in colour 18c5ccd nandi 20d ago	24	src/frq/emoji.jolt the picker's catalog: every drawable emoji and its name
Sign in with a Bluesky identity 5192124 nandi 20d ago	25	src/frq/irc.jolt IRC over TLS or TCP: parser, reader thread, SASL, PRIVMSG
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	26	src/frq/state.jolt the ratoms every screen reads, and `apply-msg!`
	27	src/frq/app.jolt the screens
	28	```
	29
Stop mistaking a quiet connection for a closed one a225fb1 nandi 20d ago	30	## Tracing
	31
	32	`FRQ_TRACE=1` prints every IRC line sent and received to stderr, which on
	33	Android is logcat.
	34
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	35	## Running
	36
Take both native libraries from one place a66d1c1 nandi 19d ago	37	Both native libraries, then the app:
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	38
	39	```bash
	40	just lib
	41	just run
	42	```
	43
Take both native libraries from one place a66d1c1 nandi 19d ago	44	`just lib` builds [jolt-native](https://gitlab.com/nandithebull/jolt-native),
Take glimmer-vidya from gitlab, so a stranger can build this 5c40e75 nandi 19d ago	45	cloning it into `.jolt-native` at the pinned commit unless you already have a
	46	sibling checkout, which wins. That repo is where every shared object this
	47	client loads comes from: `libvidya`, the retained-tree ABI glimmer paints
	48	through, and `libjoltmoq`, the AV media plane. They come out of one directory,
	49	and `just run` puts that one directory on the loader path.
Calls f31ad3d nandi 19d ago	50
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	51	`just run` is `jolt -M:frq` with `LD_LIBRARY_PATH` pointed at the built
	52	library. It connects to `irc.freeq.at:6697` over TLS and joins `#test`. Untick
	53	TLS on the connect screen (or point it at `127.0.0.1`) for a local server's
	54	plain listener:
	55
	56	```bash
	57	cargo run --release --bin freeq-server # in the freeq checkout
	58	```
	59
Sign in with a Bluesky identity 5192124 nandi 20d ago	60	## Signing in
Sign in with a Bluesky identity 5192124 nandi 20d ago	61
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	62	Three modes on the connect screen.
Sign in with a Bluesky identity 5192124 nandi 20d ago	63
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	64	Bluesky (OAuth, the default way in) follows sleek's flow: frq binds a
	65	loopback port, puts it in `return_to`, and opens
	66	`auth.freeq.at/auth/login?handle=…`. The broker runs the OAuth dance with the
	67	PDS and redirects back to that port with the handoff in the URL fragment, so
	68	it never reaches a server as a query string. The page frq serves there has one
	69	job: POST the fragment back to itself. What comes back is a single-use SASL
	70	`web-token` and a durable `broker_token`; later connections mint a fresh token
	71	from the durable one at `/session` and skip the browser.
Sign in with a Bluesky identity 5192124 nandi 20d ago	72
Remember an OAuth sign-in across restarts 4aa71e7 nandi 20d ago	73	The durable token is saved to `$XDG_CONFIG_HOME/frq/session.edn` (mode 600) so
Connect on launch when an account is remembered 9237cf4 nandi 20d ago	74	a restart resumes without one, along with the handle and nick it belongs to —
	75	and it connects on its own at launch when one is there.
Remember an OAuth sign-in across restarts 4aa71e7 nandi 20d ago	76	The web-token beside it is single-use and deliberately not saved. A token the
	77	broker no longer honours is dropped — from disk and memory — and the browser
	78	flow runs once more, rather than failing the same way on every Connect.
	79
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	80	App password signs in without a browser, straight to the user's own PDS:
	81	`resolveHandle` → DID → PDS from the DID document → `createSession`. The
	82	password goes to that PDS and nowhere else, is never written to disk, and is
	83	dropped once the session exists.
Sign in with a Bluesky identity 5192124 nandi 20d ago	84
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	85	Either way freeq sees only a token. The SASL mechanism is
	86	`ATPROTO-CHALLENGE` in both cases — `method: "web-token"`, which the server
	87	resolves through its own token store, or `method: "pds-session"` with the
	88	server's nonce echoed back so the token cannot be replayed elsewhere.
	89
	90	A refused sign-in is reported and the connection carries on as a guest.
Sign in with a Bluesky identity 5192124 nandi 20d ago	91
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	92	## Android
	93
	94	An APK with two shared libraries and no Java: `libvidya.so` (vidya's Rust/egui
	95	C ABI, which owns the event loop as the NativeActivity's own library) and
	96	`libjoltapp.so` (frq compiled to a Chez boot image). Both native halves come
	97	from the vidya checkout; only the boot image is frq's.
	98
	99	```bash
	100	./android/build-apk.sh run # build, install, launch on a connected device
	101	./android/build-apk.sh log # logcat, filtered
	102	```
	103
	104	Needs what vidya's Android build needs — SDK, NDK r29, and a cross-built Chez
	105	in `~/.cache/vidya-chez-android`.
	106
	107	TLS does not work there: jolt reaches OpenSSL through the dynamic loader, and
	108	Android has no public `libssl` to load. The connect screen falls back to the
	109	plain `:6667` listener on its own, which is why the plain transport is the raw
	110	`socket`/`connect`/`send`/`recv` calls rather than jolt's `java.net.Socket`
	111	surface — that surface does not work on Android either, while the syscalls do.
	112
	113	## What the PoC covers
	114
	115	* TLS (`:6697`, via jolt.mvn-http's OpenSSL bindings) or plain TCP (`:6667`)
	116	* Guest connect (`NICK`/`USER`), `001` welcome, `PING`/`PONG` keepalive
	117	* Auto-joins `#test` on `irc.freeq.at`
	118	* Join channels, channel buffers with unread counts, send and receive `PRIVMSG`
Ask for the backlog freeq restores channels without 94e59a2 nandi 20d ago	119	* Backlog on join, and `CHATHISTORY` for the channels freeq restores instead
Say when each thing was said dbf3b86 nandi 20d ago	120	* Twelve-hour timestamps from the server's own clock, with a heading wherever
Say when each thing was said dbf3b86 nandi 20d ago	121	the day changes
Answer a message, not just read that one was answered 4876db8 nandi 20d ago	122	* A chip above a reply quoting what it answers, and a click that goes there;
	123	↩ beside a sender to answer them, with `+draft/reply` on the way out
Pick any emoji, in colour 18c5ccd nandi 20d ago	124	* Emoji reactions: colour pills under a message, ☺ beside the sender to open a
	125	picker over every emoji Vidya can draw (popular first, then Unicode's own
	126	groups, searchable by name), and a second click on a pill to take yours off
	127	— sent as `TAGMSG`, and restored from the server's own tally when the
	128	backlog comes back
Show the pictures people paste 56cdac3 nandi 20d ago	129	* Inline previews for PNG links, fetched once and cached under
Click a picture to see it full size 563ada3 nandi 20d ago	130	`$XDG_CACHE_HOME/frq/media`; click one to see it full size
Send a picture by pasting it 8a491ba nandi 19d ago	131	* Ctrl+V in the draft attaches the picture on the clipboard: it is previewed
	132	under the box and uploaded to freeq's media endpoint while you write the line
	133	it goes with, and only on the way out does it become the link — which is the
	134	whole of what sending an image over IRC means. The draft itself is never
	135	written into. Text pastes as text, as it always did: the picture path is the
	136	keystroke the field had no text to answer with
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	137	* Join/part notices, DMs bucketed under the sender's nick
	138	* Discover list, search over buffers, disconnect
Remember which rooms this client has been in 1d062fd nandi 20d ago	139	* The rooms you have opened, remembered across runs and listed in the order
	140	you last used them (`$XDG_CONFIG_HOME/frq/channels.edn`)
Order the chat list by what you were last in 75e557e nandi 20d ago	141	* Conversations listed most recently opened first
Show who is talking, with their Bluesky picture f5548bd nandi 20d ago	142	* Bluesky avatars beside the sender, resolved from the DID freeq tags each
	143	message with
Calls f31ad3d nandi 19d ago	144	* Calls: a Call button opens one in a channel, a banner offers Join where
	145	somebody already has, and in one there is mute, deafen, video and leave. Mute
	146	and deafen are separate — a deafened microphone still carries your voice.
	147	Whoever turns a camera on appears as a tile; the self-view is labelled You
	148	and sits last, where it cannot push a face you are talking to off the row
	149
	150	## Calls
	151
	152	Signaling is IRC and lives here: `+freeq.at/av-start`, `av-join` and `av-leave`
	153	go out as TAGMSGs and the server broadcasts `+freeq.at/av-state` back, which is
	154	what actually moves this client's state — a press is optimistic, and the server
	155	settles it. Losing a race to open a call (`start-collision`) is answered by
	156	joining the call that won rather than by reporting an error, since the person
	157	asked to be in a call in that room and there is one.
	158
	159	Media is not IRC and is not here. Audio and video ride MoQ — Media over QUIC —
	160	through freeq's SFU, and that is `libjoltmoq`: Opus, H.264, capture and
	161	transport, lifted out of sleek rather than written a second time in jolt.
	162	`src/frq/av.jolt` is the whole of what frq says to it, and two of its rules
	163	shape this side:
	164
	165	* Nothing calls back. Status and video are polled, drained by a timer that
	166	glimmer runs on the loop thread — the only thread allowed to touch a node.
	167	* A frame is borrowed. The decoder's own buffer is handed to Vidya as a
	168	pointer and painted by an `:image` with a `:feed`. The pixels never become a
	169	jolt value and are never copied on this side, which is the only way thirty
	170	frames a second is affordable here.
	171
	172	The SFU is dialled once the server has minted a token, not when we ask to join:
	173	a remote SFU refuses a connection without one, and the MoQ client then retries
	174	in a loop that looks exactly like a hang.
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	175
	176	## Limits
	177
	178	* TLS and plain TCP only — no WebSocket, no iroh. On Android, plain only.
Sign in with Bluesky OAuth, through freeq's broker 2d4a377 nandi 20d ago	179	* No `did:key` signing, no credential gates, no E2EE. Sign-in of either
	180	kind needs TLS, so it is desktop-only — the Android build connects as a
	181	guest.
Remember an OAuth sign-in across restarts 4aa71e7 nandi 20d ago	182	* Only the broker token is persisted, and only for OAuth. An app-password
	183	sign-in is not remembered.
Show the pictures people paste 56cdac3 nandi 20d ago	184	* Previews are PNG only — the tree backend's decoder reads no other
	185	format, and a fetch needs TLS, so the phone shows links. The link is left in
	186	place either way.
	187	* Nothing evicts the media cache.
Calls f31ad3d nandi 19d ago	188	* Calls are desktop-only. `libjoltmoq` is not built for Android here, and
	189	the camera and microphone paths that are would still need the runtime
	190	permissions the APK does not ask for.
	191	* One call at a time, which is the media plane's rule and the microphone's.
	192	* No call is offered in a DM — freeq's AV signaling is a channel's.
Send a picture by pasting it 8a491ba nandi 19d ago	193	* Pasting a picture needs a sign-in and a desktop. The upload is filed
	194	under the DID of a live session, so a guest cannot make one; and it is read
	195	off the clipboard through the ABI's `vidya_clipboard_image_png`, which
	196	arboard backs on desktop and nothing backs on Android. It also shares
	197	nothing to your PDS and posts nothing to Bluesky — those fields are opt-in
	198	and this client does not send them.
Calls f31ad3d nandi 19d ago	199	* No scrollback trimming or threads.
Stop mistaking a quiet connection for a closed one a225fb1 nandi 20d ago	200	* A sent line waits up to 200ms for the reader thread to flush it.
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	201	* Message lists are keyed vboxes; glimmer-vidya has no `:listbox` yet.