Nostr onboarding: publish profile, relay list and media server list #269

Merged
raucao merged 13 commits from feature/nostr-onboarding-ruby into master 2026-11-19 07:15:09 +00:00
13 Commits
Author SHA1 Message Date
raucao 355d0a2fb0 Add a "Just a moment..." title to the metadata loading state
CI / Test (pull_request) Successful in 47s
Release Drafter / Update release notes draft (pull_request) Successful in 3s
The title sits above the rotating status messages and disappears with
the loading state; the status messages no longer carry their own
ellipses.
2026-11-19 10:58:35 +04:00
raucao 7f0d10aa9c Show the relay list before the profile in Nostr settings
CI / Test (pull_request) Successful in 48s
The profile and the media server list are published to the user's write
relays, so they should be set up after the relay list. This also makes
the page order match the discovery order (relays -> profile -> media
servers) shown while loading.
2026-11-19 10:39:56 +04:00
raucao ae13890cea Even out the spacing between the Nostr settings sections
CI / Test (pull_request) Successful in 44s
Drop the bottom margin on the Relays section so the gap before Media
servers matches the gap before Relays.
2026-11-18 23:51:50 +04:00
raucao cd325f39ea Address review nits on the discovery timeout fix
CI / Test (pull_request) Successful in 45s
- Track EOSE with a done flag so a healthy relay with no matching
  events returns immediately instead of waiting out the timeout
- Restore the ensure around the client thread cleanup
- Raise the metadata fetch client timeout to 60s to cover the
  worst-case sequential discovery on the server
2026-11-18 23:41:45 +04:00
raucao f15d04d1a9 Fix discovery timeouts leaking Timeout::ExitException
FetchEvent wrapped its wait in Timeout.timeout and FetchLatestEvent
wrapped the relay loop in another one. The nesting leaked
Timeout::ExitException, which is neither a Timeout::Error nor a
StandardError, so it escaped the rescue and surfaced as a 500 on the
metadata endpoint.

- FetchEvent waits on the condition variable with a 5s timeout instead
  of Timeout.timeout, and wakes immediately when the relay errors
- FetchLatestEvent uses a monotonic deadline instead of Timeout.timeout,
  and skips a relay that raises, so one bad relay cannot abort discovery
- PublishEvent uses thread.join(TIMEOUT) instead of Timeout.timeout
2026-11-18 23:39:38 +04:00
raucao 0dda543b03 Document Nostr user onboarding and its known limitations
CI / Test (pull_request) Successful in 46s
2026-11-18 22:19:46 +04:00
raucao 2af8efde18 Unify the URL list editors and harden the metadata fetch 2026-11-18 22:19:46 +04:00
raucao 5edbd3aed1 Add the Blossom media server list (kind 10063) 2026-11-18 22:19:46 +04:00
raucao 23898ae0a0 Publish the profile (kind 0) from settings 2026-11-18 22:19:46 +04:00
raucao 92a36cf3f7 Publish the relay list (NIP-65) from settings 2026-11-18 22:19:46 +04:00
raucao 29ed14a556 Add server-side publishing for user-signed Nostr events 2026-11-18 22:19:45 +04:00
raucao 24dde0fae0 Verify Nostr event IDs before trusting signed events 2026-11-18 22:19:45 +04:00
raucao 2b30c6b750 Add Nostr onboarding: discovery services, settings UI and metadata chain 2026-11-18 22:19:35 +04:00