Nostr Web Client

Ask me questions directly and I can answer them.

The code creates a set of query specs from a filter -- i.e. if the filter specifies an author and a kind, we return one spec for traversing the 'pubkeyKind' index at the specified key range, if the filter specifies 4 authors and 2 kinds, then we return 8 specs for traversing the 'pubkeyKind' index in all these different combinations.

Then we gather all the results in a heap and take them in sorted order and return them through the channel.

The heap part can probably be improved, let me know if you have something better. Maybe sacrifice a little bit of strict ordering to get some performance?

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i will just publish the better version, with actual explanation

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

btw, this is what it means to build in public

we fight with our competitors and allies to get questions answered!

and the public benefits

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

also, yes, i've hit up hard against this problem with the event store code, because i needed to add a new index/record

just to explain why i'm even bothering

why should i write a new version of the thing if i don't have to?

yes, i can say that you wrote a shit version, because:

you didn't explain it

who knows if it's good or not if i can't understand it????

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

defend your honor by explaining the algorithm and proving that you are a genius and you are right

i don't mean that sarcastically, at all, i mean that for real

we are programmers

our job is to boil down things to repeatable processes in exhaustive detail that can't be fucked with

fiatjaf 1y ago

I just explained in the other note above.

I don't know why should I bother to explain before you asked because why would I waste time explaining if I don't know if anyone will use this ever? I don't even know if I am going to keep using it in 2 weeks (but, granted, I am using it after many months at this point).

lilith 1y ago

lmao