Feature Request
After a successful NIP-46 Amber sign-in, the home screen shows only the raw 16-char pubkey prefix. There's no code anywhere that fetches the user's kind-0 (NIP-01 profile metadata) event, and no UI element to render name / about / picture / nip05 from one.
The user-visible symptom: after scanning the QR code and approving in Amber, the user lands on a home screen that says "🦉 Hoot - 0a1b2c3d4e5f6789..." — meaningless hex chars. Users recognise themselves by name, not by 16 hex characters.
This is fixed by the branch feat/nip46-profile-on-login. Summary:
nip46.Session.FetchProfile(ctx, userPubKey) queries live relay connections for a kind-0 event.- The TUI's
qrSuccessMsg carries the profile alongside the pubkey.
- Home screen renders name + about + NIP-05 (✓ prefix) when available.
- Profile is cached in
cache.profiles with 24h TTL.
- Fetches fall back gracefully to the npub display when no kind-0 event exists.
PR: #78
Feature Request
After a successful NIP-46 Amber sign-in, the home screen shows only the raw 16-char pubkey prefix. There's no code anywhere that fetches the user's kind-0 (NIP-01 profile metadata) event, and no UI element to render
name/about/picture/nip05from one.The user-visible symptom: after scanning the QR code and approving in Amber, the user lands on a home screen that says "🦉 Hoot - 0a1b2c3d4e5f6789..." — meaningless hex chars. Users recognise themselves by name, not by 16 hex characters.
This is fixed by the branch
feat/nip46-profile-on-login. Summary:nip46.Session.FetchProfile(ctx, userPubKey)queries live relay connections for a kind-0 event.qrSuccessMsgcarries the profile alongside the pubkey.cache.profileswith 24h TTL.PR: #78