@hodlbod did you fix something with caching websocket connections or something? Over the past month or so I stopped using coracle (and nostr) because I was being assaulted with 22242 signing requests, and now I'm not (or at least it's tolerable now).
Ademan
npub19jes...pt7r
Neanderthal hacking on Bitcoin stuff. LNHANCE please!
I really wish nos2x had some kind of support for understanding what it's signing. Like a template that says "you can always sign an event that looks like this, with this varying part" or something. Specifically thinking of how I get prompted to sign like 30 22242 events, but as long as it's to a relay I've pre-approved I'm ok auto-approving. (nos2x kind of does this already, but it only keeps track of the kind, but I don't want to blanket allow 22242s)
@npub1dlxa...5230 ayyyyyyyyyyyyyyyy
Is there a legal defense fund for good samaritans willing to disobey inhuman federal edicts in order to help people affected by helene? Seems like a good cause. @Guy Swann @Marty Bent
If it gets well funded, either there's enough money for everyone, or if there isn't enough money, that implies a pretty large amount of civil disobedience.
@Jack Spirko have you ever tried to grow gooseberries in zone 8? I've been considering blueberries but I get the impression they're pretty water hungry and I don't have a good irrigation plan for where I want to put them. Plus, I have one report that they "haven't had success" with blueberries, even with irrigation, out here.
I've obviously got blackberries but I want something that can also function as a border on its own.
I'm specifically considering
but also more common gooseberry varieties.
Ribes curvatum - Wikipedia
@hodlbod I'm getting an error "Error: nos2x: undefined commands.ts:635" when trying to click the follow button on a user (I use a plugin, obviously). If you see this message, then the issue is limited to following (or else at least doesn't affect posting).
We had some sprite left over from independence day and I watered it down with a lemon sparkling water. If it wasn't for the sugar I'd drink this every day.
WOW, I didn't realize we were so strongly inverted, for so long... I just kind of assumed since the yield curve inversion had exited the news cycle that it had crossed back into positive territory...
Source: 
Source: 
X (formerly Twitter)
Robert P. Murphy (@BobMurphyEcon) on X
Inverted yield curve can't cause recession if the Fed never cuts short rates. *taps forehead*
I can tell this issue on the nips repo is going to stagnate forever ๐ฉ
So is Swan pining for the fjords or is this really (as they claim) cutting their activities they had expanded into, presumably leaving their "profitable" core intact?
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