Nostr Web Client

Oh…I misunderstood. You see that on blossom.band?

Yes, the link is from blossom band: nostr:npub1dryseu6yv7evgz2f7pfzk6wht8flapcfv5l6r4y65pg5px293awqlwwfpc.blossom. band/ad15b6cad2dda9c74727138df1d95545ed2dcad2f9eb183d5d9a78757aebd9d8.jpg

Reply to this note

Please Login to reply.

Discussion

Galaxie 5000 8mo ago

Ok I’ll just have to see what they say

The Fishcake (nostr.build) 8mo ago

You could also try and see if Amethyst, Primal or any other client does and if it works. I am not sure if nip94 tags are causing the issue

The Fishcake (nostr.build) 8mo ago

nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe I think I found the issue. It seems that Nostur expects full nip96 like response in blossom nip94 tags, while BUD08 just states tags array of arrays under nip94 field, nothing else. Initially I got it wrong too, and returned it as your check does. Now it is fixed and complies with BUD08 specs.

https://github.com/nostur-com/nostr-essentials/blob/d6f550579d15c850635c7c1ae73a7f4f6b80d1f6/Sources/NostrEssentials/NIP-96/UploadResponse.swift#L28

https://github.com/nostur-com/nostr-essentials/blob/d6f550579d15c850635c7c1ae73a7f4f6b80d1f6/Sources/NostrEssentials/Blossom/BlossomUploadResponse.swift#L17

https://github.com/nostur-com/nostr-essentials/blob/d6f550579d15c850635c7c1ae73a7f4f6b80d1f6/Sources/NostrEssentials/Blossom/BlossomUploader.swift#L75

The Fishcake (nostr.build) 8mo ago

https://github.com/hzrd149/blossom/blob/master/buds/08.md - for reference

Fabian 7mo ago

I see, fixing this now thanks!

The Fishcake (nostr.build) 7mo ago

I made identical mistake in the beginning, and nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 spotted it before I realized the fault 😂🤣

Kieran 7mo ago

When I was implementing it I was expecting it to be like nip96 too lol

Galaxie 5000 7mo ago

🙏