Avatar
kuiperbelt
1d7792404ebfae1ce89cedf939ea2a2954ae58997bf084f96ed312f965359001
I'm a bitcoin maximalist and software developer.

wait, i slept on 59k #bitcoin

yeah when ive tried to use it the videos never loaded

Do you yall think ASIC prices will be affected by the halving? #asknostr #halving #mining

unleashed.chat needs a way to login besides nsec and NIP-07

I fixed the "bad event" problems. It seems relay.nostr.band does support relaying NIP 52 events but thats just not listed in its "supported_nips".

NIP-52 events have t and g tags. But when I do a REQ like this:

[REQ, "subid", {"#t":["hashtagtest"]}]

Then the relay accepts my request but shows no responses.

However, if I put this in my filter:

[REQ, "subid", {"ids":["idofcalendarevent"],"#t":["hashtagtest"]}]

then it finds my event. I believe these two filters should be && because they're in the same JSON object. BUT what I think is happening is that the "#t" bit is being ignored by the relay.

Is this a bug in the relay I'm using?

#asknostr #dev

Is it possible that relays won't report NIP-52 in their .supported_nips NIP-11 response, but yet they still will actually support NIP-52 events?

I ask because flockstr seems to be using these relays and none of them say they support NIP-52:

https://github.com/zmeyer44/flockstr/blob/fe66367c1bfc01d4046f084a80ef6e85c7e6973b/constants/relays.ts#L4

I'm getting back "bad event" from my NIP-52 events when I send it to these relays, and I can't tell if it's due to them not supporting NIP-52 or my event is badly formed.

#asknostr