nandi/frq · 9237cf4

nandi/frqpublic⑂ Fork 0

⑂ 9237cf4

Connect on launch when an account is remembered

A saved sign-in has already said what it wants; asking for the same click at
every launch carries no information. So a remembered account connects on its
own, and the connect screen shows it happening.

It goes through a timer rather than a straight call so the window is up first:
the status line and any error should land somewhere the user is already
looking. A stale token behaves as it does anywhere else — one attempt, then
the browser. Guests are untouched, and start where they always did.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

nandi committed 2026-08-30T11:10:56-07:00 Browse files

9237cf4 parent: e84d24d

modified README.md +2 -1 Viewed

@@ -58,7 +58,8 @@ job: POST the fragment back to itself. What comes back is a single-use SASL
58	58	from the durable one at `/session` and skip the browser.
59	59
60	60	The durable token is saved to `$XDG_CONFIG_HOME/frq/session.edn` (mode 600) so
61		-a restart resumes without one, along with the handle and nick it belongs to.
	61	+a restart resumes without one, along with the handle and nick it belongs to —
	62	+and it connects on its own at launch when one is there.
62	63	The web-token beside it is single-use and deliberately not saved. A token the
63	64	broker no longer honours is dropped — from disk and memory — and the browser
64	65	flow runs once more, rather than failing the same way on every Connect.

  from the durable one at `/session` and skip the browser.
  The durable token is saved to `$XDG_CONFIG_HOME/frq/session.edn` (mode 600) so
--a restart resumes without one, along with the handle and nick it belongs to.
++a restart resumes without one, along with the handle and nick it belongs to —
++and it connects on its own at launch when one is there.
  The web-token beside it is single-use and deliberately not saved. A token the
  broker no longer honours is dropped — from disk and memory — and the browser
  flow runs once more, rather than failing the same way on every Connect.

modified src/frq/app.jolt +8 -1 Viewed

@@ -367,5 +367,12 @@
367	367	(defn -main [& _]
368	368	;; Before the window: a saved sign-in decides which mode the connect screen
369	369	;; opens in, and what it says.
370		- (s/restore-session!)
	370	+ (when (s/restore-session!)
	371	+ ;; And then it connects on its own. A remembered account has already said
	372	+ ;; what it wants; making it say so again at every launch is a click that
	373	+ ;; carries no information. It is a timer rather than a call here so the
	374	+ ;; window is up first — the connect screen with its status is what the
	375	+ ;; user should be looking at while this happens, and if it fails, the
	376	+ ;; error lands somewhere visible.
	377	+ (vidya/after! 150 s/connect!))
371	378	(ui/run app :title "frq" :width 520 :height 860))

  (defn -main [& _]
    ;; Before the window: a saved sign-in decides which mode the connect screen
    ;; opens in, and what it says.
--  (s/restore-session!)
++  (when (s/restore-session!)
++    ;; And then it connects on its own. A remembered account has already said
++    ;; what it wants; making it say so again at every launch is a click that
++    ;; carries no information. It is a timer rather than a call here so the
++    ;; window is up first — the connect screen with its status is what the
++    ;; user should be looking at while this happens, and if it fails, the
++    ;; error lands somewhere visible.
++    (vidya/after! 150 s/connect!))
    (ui/run app :title "frq" :width 520 :height 860))