Nostur is not providing content-type as expected? Specs are clear about doing that. nostr:nprofile1qqsfhc97pejd8z3f488vnfwgaawcw0ptlffk9f94trd9la5mc09ms8spzamhxue69uhkvctzd9skutnwdaehgu339e3k7mgpp4mhxue69uhkummn9ekx7mqzaefjw any ideas?
Discussion
I left a comment on one of their posts but haven’t heard anything yet.
Hmm, I am not sure what this error actually means. It is something that is produced by Nostur. I see that your picture was uploaded:
I just used Nostr.build to post this so you could see the error.
Oh…I misunderstood. You see that on blossom.band?
Yes, the link is from blossom band: nostr:npub1dryseu6yv7evgz2f7pfzk6wht8flapcfv5l6r4y65pg5px293awqlwwfpc.blossom. band/ad15b6cad2dda9c74727138df1d95545ed2dcad2f9eb183d5d9a78757aebd9d8.jpg
Ok I’ll just have to see what they say
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
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/hzrd149/blossom/blob/master/buds/08.md - for reference
I see, fixing this now thanks!
I made identical mistake in the beginning, and nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 spotted it before I realized the fault 😂🤣
When I was implementing it I was expecting it to be like nip96 too lol
🙏
Its throwing errors but uploading successfully
I found a bug in Nostur, see my other response
Lol looks like you posted that at almost the same time. Thanks!
Yeah, it took me some time to dig through the endless dependency tree to track it 😂🤣