nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 I have the same issue but this issue is closed. Is the fix commit deployed?

https://github.com/quentintaranpino/nostrcheck-server/issues/34

https://cdn.nostrcheck.me/83d52b4363d2d1bc5a098de7be67c120bfb7c0cee8efefd8eb6e42372af24689/8a93a5d72b6caafbb3cf15b0b8c2f696959dc594ed60a55a9b55adc3fd08f3e2.webp

Reply to this note

Please Login to reply.

Discussion

(error at NIP-96 API)

It shouldn’t be closed, I’ll check. The bug is still active, and using the workaround they suggest works.

I’m going to activate the bypass for the tag u in nip98. Give me a few minutes; I didn’t think it would affect you on Nostter.

It should be fixed now. Can you check?

Thank you, wait a minutes.

It works fine without the workaround, thank you!

Sorry for the inconvenience 🙏