Thread - Nostr Hypermedia

You're welcome, I've been working on NIP-55 integration for a while so I'm always interested in these edge cases. I think the issue lies in the bogus hex key that Amber generates from the empty npub string. It needs more testing with various pubkeys combinations, but changing the null check in Amber fixes the problem for me. I'm happy to raise an issue, the bug is easily reproducible with the right test keys, the only question is which repo - Pokey, Amber or both?

↑ Parent

Replies (4)

greenart7c3 1 year ago

The issue is in the get public key method pr when hes trying to auth to a relay? Can you send a pull request to fix the null check?

1 replies ↓

SLCW slcw@rocky.nostr1.com 1 year ago

@greenart7c3 is tagged in this thread, so let's see what he has to say about it. Awesome debugging work! Nothing gives me the tingles like collaboration! When you say "dud relay" does that mean that the issue ultimately stems from a bad relay defined in Amber?

1 replies ↓

SLCW slcw@rocky.nostr1.com 1 year ago

Let me know if you'd like me confirm that this fix resolves the original problem of auth failing and that "Amber not installed" toast being generated before you publish an updated Amber release.

Biz chebizarro@coinos.io 1 year ago

By "dud relay" I meant a relay specified in the key's relay list which isn't accepting notes, either because the key isn't authorized or there's something wrong with the relay and it's rejecting all messages. Looking at it more deeply, it's possible it's just any relay that requires authorization, so if you have one or more of them on your relay list than that might be what's causing the Amber not found message.

2 replies ↓