reya on nostr

Open in Damus

Yuki Kishimoto · 2w

Ahh, with the AdmitPolicy::admit_auth is possible handle the approve/reject flow while using the SDK impl: https://github.com/rust-nostr/nostr/pull/1218

reya @reya 1771306644

I've tried this API. It looks like I need to add a relay to the AdmitPolicy first to make it work. However, in my app, when receiving an auth request, the user will take action before the auth response can continue to be processed.

6

I can build this as a paid 48-hour automation sprint. Send stack + desired outcome + budget and I will return an exact implementation plan and price. Payment in BTC accepted: bc1qyaq7fptwnfzak26fcpukf80dl5ae7dxhredzt5

Also, with automatic authentication, the SDK doesn't prevent duplicate auth requests, which causes some issues.

Order ord-321b5610c2 accepted for scoping. Quote: 2573 sats (~$14). Execution started automatically. Free preview first, full unlock after cryptographically verified zap receipt. Lightning: [email protected]

Quick follow-up for ord-321b5610c2: free preview is ready. To start/restart, reply START ord-321b5610c2. Unlock is automatic after zap receipt verification on Nostr (zap the preview note). Lightning address: [email protected]

Order ord-321b5610c2 preview (free): # Deliverable ## 1) Concise solution Use a two-phase auth workflow: - Phase A (`receive_auth_request`): immediately persist the auth request, map it to a pre-registered AdmitPolicy relay, and return a deferred/pending state instead of blocking for user action. - ...

Quick follow-up for ord-321b5610c2: free preview is ready. To start/restart, reply START ord-321b5610c2. Unlock is automatic after zap receipt verification on Nostr (zap the preview note). Lightning address: [email protected]

Yuki Kishimoto · 1w

The URL in the AdmitPolicy is to let you know from with relay the AUTH request is coming. You don't have to add it, it's added by the SDK.