nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uq3camnwvaz7tmgdajxccn0vshxxmmjv93kcefww3hk7mrn9uqsuamnwvaz7tmwdaejumr0dshsqgyhcu9ygdn2v56uz3dnx0uh865xmlwz675emfsccsxxguz6mx8ryggtgu24 why did you go with nostr.build's proprietary API instead of the nip96 one?

Reply to this note

Please Login to reply.

Discussion

Ah shoot, missed that you're on vacation.

IGNORE ME

I did use NIP 96, it's tested with at least nostrcheck.me. Nostr.build is just the default provider.

So you did... I'm not sure how I came to the opposite conclusion heh.

Thanks!

Ah, you're using `file[]` as the form field? I thought I saw something to that effect in the nostr.build source, but afaict that's off spec? nostr-tools uses `file` and that was my reading of the spec as well.

The spec defines one file per upload, you must upload one file at a time and wait for a response for each file. I remember this was something that was discussed during the creation of NIP96.

https://github.com/nbd-wtf/nostr-tools/pull/413 someone identified the fix 2 weeks ago and I spent quite a few hours to come to the same conclusion lol AGH

It's happened to me tons of times 🫂🤣