this looks amazing

ahn, got it.

*10,000 highlights later* If says he's gonna do something, you better believe him.

There is actually a generous free tier: - first, you just have to tell me the pubkey you'll be using for signing the requests and I'll get you 10k credits on the house - secondly, you can use the pubkey of the user to sign requests, and if they are minimally reputable they'll get automatically 100 credits every day. To give contex, that amounts to +100k users, and with 100 credits they'll be able to search for many hours most likely.

This seems a very interesting conversation

Using has never been easier 👀

complexity is easyz simplicity is hard. GN

just wow

> I do want to fork go-nostr into something more sensible though, and I will open source that when I do make a fork and try to keep it stable I think you, me and could collaborate into makind a simple nostr lib just for the JSON encoding/decoding, filter Match logic, data structure and few more. A minimal foundational library, so we can all avoid using the go-nostr with its 180k dependencies. wdyt?

take a look at my rely framework similar to khatru, but better imo. Expetislly after the. v1 that I'm going to release next week or so

I take it as a compliment. take a look at https://github.com/pippellia-btc/rely, I built it as a heavy user of khatru that was fed up with its bugs. There you can find solid core features + much more expressivity, for example the ability to call client.Pubkey (for auth), client.IP (for rate-limiting), client.Disconnect, which are hard to do in khatru or impossible. I am now focusing on the v1 for rely, which will give you the ability to close individual subscriptions, hooks for when the relay is overloaded (monitoring, back-pressure strategies), ability to know when a client is requesting too much and so many other goodies.

cc

brooo, I promise bro, it's gonna be great bro, just you and the llm bro, you're gonna tell him, bro please write the OnEvent hook so that it stores the event if with ecash bro. It's gonna be great bro

Nope I don't use them. But the graph I have is only kind:3 based

We all know you're going to vibe it. So take a look at rely, my framework for building custom relays. https://github.com/pippellia-btc/rely

At the fact that you started the reply with "Some idiots..."

lol

mmm I don't know. More direct speech is better

I think it would encourage people not talking directly at each other and instead making spicy posts that don't quote directly, like the ones "Some idiots that think...." Quite common on twitter with the latest core knots drama.

This is interesting, thanks for sharing. Anyway I find it really nice to use Redis, it's very easy to build a custom graph on it. Btw, the bloom filter conversation is about how clients can use the results of these graphs that run on service providers, without re-doing the work. No matter the graph you use, you still have to download many thousands events per day, parse the JSON, check the signatures... Just not something you want to do on a phone, unless you are into watching your battery level go down in real time

Multiple bloom filters is an interesting idea, but still you have the problem of keeping each up to date, and I would argue that you don't need all the data all the time. You just need a bit of data, at the right moment.