I just wasted nostr-tools' PR #420 on a duplicate Icing on the cake of wasting hours debugging nostr-tools' nip96 support

#nostrdev #asknostr #nostr-tools I'm unable to complete nip96 uploads across nostrcheck, nostr.build, and files.v0l.io I suspect it's my fault somehow, but I'm burning more time than I'd like troubleshooting. I'm using nostr-tools and afaict based on reading nip-96, examining the nostr-tools code, and looking at the requests, I'm not certain what's wrong here. Afaict the Authorization form field is non-standard but harmless (hacking it out did not change the responses I'm getting, and reading the void-cat-rs source it looks like it should be ignored anyway). ``` POST /n96 HTTP/2 Host: files.v0l.io User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0 Accept: */* Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br, zstd Referer: http://localhost:5000/ Authorization: Nostr REDACTED Content-Type: multipart/form-data Content-Length: 24052 Origin: http://localhost:5000 Connection: keep-alive Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: cross-site Priority: u=4 TE: trailers -----------------------------11234029581503681683701650224 Content-Disposition: form-data; name="Authorization" Nostr REDACTED -----------------------------11234029581503681683701650224 Content-Disposition: form-data; name="size" 22933 -----------------------------11234029581503681683701650224 Content-Disposition: form-data; name="file"; filename="2024-07-06-152337_1000x175_scrot.png" Content-Type: image/png ... snip ... -----------------------------11234029581503681683701650224-- ``` You can see from the size field that the file is quite small. I get a 400 response from all three services. (Not a 401 or 403 or anything) I'm pretty sure I'm generating the authorization token correctly (also using nostr-tools) and I glanced at the nostr.build source code and I'm reasonably confident the response I'm getting back is generated before the auth header is checked. Both nostr.build and nostrcheck have some kind of message indicating a problem with the file upload portion. (files.v0l.io gives me a generic 400 html response) nostr.build example ``` '{"status":"error","message":"Either no file or more than one file posted. Only one file is expected."}' ``` I'm not a web guy so nothing is jumping out at me, but does anyone notice something obviously wrong with the request?

What is the currently recommended RAM for a bitcoind node, both for initial block download and steady state? I'll be using -txindex and making infrequent RPC calls, if that affects it significantly. I'm provisioning a VM on a home server for a new node, so I can always adjust later if need be. #bitcoin #asknostr

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

#asknostr #nostrdev does anyone successfully use the nostr.build nip96 endpoint?

@nostr.build I'm working on a for-funsies nostr client that I'll probably abandon fairly quickly and I'd like to integrate nostr.build If I actually release it, it'll be FOSS and free to use, but the nostr.build github made it sound like I should contact y'all before integrating it. Happy to provide more details and/or a preview release if you want. (Give me some time to do some cleanup first in the latter case heh) Like I said in all likelihood I'm going to abandon this pretty quick anyway, but I want to be a good steward.

Hey @Jack Spirko do you have any experience with

Tithonia diversifolia - Wikipedia

? I'm trying to find a perennial to build a privacy barrier, and also to generate compost. (The flowers are a bonus as pollinator attraction) The problem is, I'm in Zone 8a like you, where Tithonia supposedly will die off completely in hard freezes. I was also interested in pigeon pea, since that can even be for human consumption, but the hard freeze is a problem with them too.

@hodlbod any thoughts on what a client should do with a kind 1 with NIP-92 metadata but which has no URLs in the body? I'm inclined to treat them as "attachments" regardless. It makes the most sense for *my* purposes, but it also makes sense that many clients may just ignore them altogether (and therefore I should probably avoid creating such notes).

Test #test

I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? #asknostr If not I call dibs on "Nosbooratu"

I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? If not I call dibs on "Nosbooratu"

IndexedDB actually isn't that bad once you get used to it...

#primal doesn't create events with nip-92 metadata? #asknostr

Is anyone else slightly annoyed that we have this rich structured format and NIP-92 uses space separation in strings? I don't really have a better solution but this is fugly.