Nostr Web Client

nip-01 protocol is a mess that literally mashes 3 query APIs into one, incoherently

fetch events by id

search events by filter

search events by content keyword search

it's three API methods that are not clearly separated and this confusion is very obvious at least between the "ids" field and the rest except the "search" field

can we combine SEARCH and FILTER together? maybe yes, but that's a separate logic, and it is actually doable with a small enough result set out of the filter before you do a full text contains search

the nip-01 protocol was not designed as a proper API, and we aren't going to progress this protocol's capabilities without adopting age old "API" semantics

Pip the WoT guy 9mo ago

> nip-01 protocol is a mess that literally mashes 3 query APIs into one, incoherently

fetch events by id

search events by filter

search events by content keyword search

Yes, If I were to re-make nip-01, I would use these 3 APIs + a general request/response API (DVM like).

However, as much as I don't like messy things, I don't think this is a big deal.

Reply to this note

Please Login to reply.

Discussion

🇵🇸 whoever loves Digit 9mo ago

the protocol spec sucking is a big deal

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 9mo ago

i see, and you have specialised in reason and logic to actually solve problems instead of attack people now?

🇵🇸 whoever loves Digit 9mo ago

kinda?

my profile bio still mentions my difficulty not lashing out at people

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 9mo ago

yeah, you only say that because you don't care as much as i do about auth and the private/paid relay use case, which i see as the main avenue of funding for development