The Nostr Wallet Connect in more-speech used to work. Now it doesn't. I didn't change anything. I'm using getalby, though I also tried Mutiny with identical results.

The initial REQ for 13194 goes out to the relay (in this case wss://relay.getalby.com/v1) but nothing comes back. Dead silence until time out.

This is strange because all my other relay connections work just fine. (like the ones I'm using to send this message). And this one used to work too. So I'm thinking maybe there's some kind of header that the websocket connection needs.

Did something change in the NIP-47?

I've got a websocket tool that I use with Chrome. It lets me open web sockets and send message to them. The relay works when I use it.

I'm at a loss. Any ideas?

Reply to this note

Please Login to reply.

Discussion

you should tag nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm they have pretty good support

in this case it's about what alby has implemented, that may not be what NIP-47 specifies currently

From what I know we follow the NIP-47 spec and haven't received similar notifications from other apps.

Can we provide any information to help debugging it?

See my DM.

From: Moritz<-jb55 at 02/08 19:50

> From what I know we follow the NIP-47 spec and haven't received similar notifications from other apps.

> Can we provide any information to help debugging it?

CC: #[4]

CC: #[5]

CC: #[6]

hey, I am happy to help. can you share an event id in a DM? - maybe also the content if possible.

nothing really changed actually. no issues are know.

Did you get my DM?

From: bumi<-cameri at 02/14 08:58

> hey, I am happy to help. can you share an event id in a DM? - maybe also the content if possible.

> nothing really changed actually. no issues are know.

CC: #[4]