Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Sunday, 28-Jan-2024 13:29:02 JST Alex Gleason

   in reply to

   • unsafe { Sir Alecks Gates }
   @agates It's an alternative to WebLN that works remotely. I don't see what there isn't to get... that a person might want to use Nostr events instead of a REST API? It solves the authentication problem up-front because Nostr events are signed. Plus when you build in a Nosteric way, this type of thing can simplify your code a lot. It's good if you're already building on Nostr.
   • Embed this notice
     unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Sunday, 28-Jan-2024 13:29:03 JST unsafe { Sir Alecks Gates }
     Just looked at NIP-47.
     
     If the user has to interact with a central service to get connection information *on a specific relay* in the first place, why is Nostr being put in the middle?
     
     This solves nothing...
     
     https://github.com/nostr-protocol/nips/blob/master/47.md