pull down to refresh

153 sats \ 3 replies \ @ek 7h \ on: NWC ecosystem map nostr
I am implementing CLINK and I definitely like the distinction between noffer and ndebit. It tells me immediately if what I have is for receiving (not very sensitive) or sending (extremely sensitive).
Unfortunately, a NWC url does not. This leads to bad UX because we need to tell them that this NWC url that looks like any other NWC url is too permissive if they give us one for sending when we expect one for receiving.
In general, NWC urls are opaque where we want transparency (permissions), and transparent where being opaque might be better (exposing "implementation details" like pubkey, relay, secret etc. to the user).
This could be fixed if NWC urls also were encoded with a prefix like noffer or ndebit.
But since they can support both in one ... not sure if this actually makes sense
write
preview
55 sats \ 2 replies \ @Scoresby OP 7h
I hadn't heard of CLINK yet. Looks like I have some reading to do. (Also: great name)
reply
110 sats \ 0 replies \ @justin_shocknet 6h
great name
Had to thread the needle with the "Pub" theme but also it's an onomatopoeia for metallic coins changing hands.
ek:
Yea afaik NWC doesn't offer a way to arbitrarily issue invoices since it's all predicated on pre-shared secrets. For the debits, SN can use a persistent key that has a proper display name and avatar etc that the wallet can show the user, the idea is that user's construct their rules around identities rather than what amount to random API keys.
Also dropped a tip in the other thread towards nmanage that may be useful for manipulating users offers.
reply
17 sats \ 0 replies \ @ek 7h
it's from @justin_shocknet
reply