Oddbean

▲ ▼

 Which nip46 servers support connecting with nostrconnect: schema? nak doesn't seem to, what about others?

I see next.nostrudel.ninja client has it, any other clients? 

@fiatjaf @PABLOF7z @Mike Dilger @greenart7c3

▲ ▼

 Started nip-46 #nostrability positive interop tracker here: https://github.com/nostrability/nostrability/issues/73

▲ ▼

 There is Nostr Connect nip (nip46) but then there is a small part of it which is nostrconnect://pubkey... urls. Ideally we'd have a more detailed table with more columns, "server", "client", "bunker:", "nostrconnect:", "create_account" at least come to mind.

▲ ▼

 Noted. Will add when I get computer access. Will also add you to nostrability repo, if I havent already

▲ ▼

 I'm already added

▲ ▼

 You’ll need to upgrade your GitHub account; it won’t have enough storage

▲ ▼

 Soon™️

▲ ▼

 Oh, I guess I have to support that. It's hard to learn how these protocols work.

▲ ▼

 Same here, adding it to nsec.app and nostr-login. Honestly it looks like a much better way to connect than bunker urls.

▲ ▼

 I think only amber and rust-nostr

▲ ▼

 That's my feeling too, will be adding to nsec.app and some clients.

▲ ▼

 I'm pretty sure Snort has it.

▲ ▼

 Doesn't seem so, can't find a way to generate nostrconnect: url in snort. @Kieran ?

▲ ▼

 Not gossip. It only supports the signer-initiated bunker://