Jimbo

@sancoder Yes, thanks, I believe that's eventually what I did, to my recollection. > If we're gonna live with this compact_history stuff it'd be great to have such a pause...

Update: It appears that BlueWallet does sometimes show a dialog explaining that the Electrum serer cannot be connected to. I think in the case where it doesn't, it's because the...

The root cause of this issue (and many like it) is https://github.com/npm/write-file-atomic/issues/11. There is an outstanding patch which will fix this for everyone. We're all waiting for someone from npm...

Another +1 on this. Please merge as this blocks using single-threaded in a Worker context.

What's the status of this? Can we get a version of ffmpeg wasm that works single-threaded in a Worker? I'm also experiencing the `document` is not defined problem.

I'm open to alternatives. Adding `supported_nips_at` was the simplest change I could think of. Ideally, each NIP would have a version number to which relays could pledge support. > Trusting...

> StrFry's config just needs to be updated in this case. Every relay continuously needs to be updated in every case is the problem.

> We are not designing NIPs in a way that it is easy to declare compliance with. This has been my experience, yes. > Right now declaring compliance with NIPs...

> If the StrFry example you gave had versions, would it be any better? I only posted `nos.lol`, but every relay that I've ping'd has incorrectly listed at least one...

> Maybe someone should just design a test suite to run against all relays and output their compliance to varying levels of NIPs. :) This has been on my mind...