Oddbean new post about | logout
▲ ▼
jiftechnify | 18 days ago (raw) | export | reply | flag +4 
 ちなみに nsec.app もamber も現在masterにマージ済みの仕様通りには動いてなかったりする
▲ ▼
brugeman | 18 days ago (raw) | root | parent | reply | flag 
 Actually both nsec.app and amber work according to master nip46, they just use the same remote-signer-pubkey and user-pubkey - nothing in the spec says this is forbidden, it's a valid behavior.
▲ ▼
jiftechnify | 18 days ago (raw) | root | parent | reply | flag 
 My point was the behavior of remote signers in "initiated by the client" flow (uses nostrconnect: token) after a user approved connection. My understanding of the 
current spec on master was "remote signers should send connect *request* to the client app", but the actual behavior of real-world signers is opposite (they send *response* to connect), so I was a little confused. 

btw, https://github.com/nostr-protocol/nips/pull/1553 should make the point clearer. I really appreciate your works that improves Nostr sign-in experiences!
▲ ▼
brugeman | 18 days ago (raw) | root | parent | reply | flag 
 Yes that part was left completely unspecified and I think the first to implement it "somehow" were Amber and Nostrudel, and then I followed with nsec.app and nostr-login. The PR you mentioned should indeed clarify this part.