Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

well, we could make a new variant of the REQ maybe? if you want to make a proposal i will give it a good going over and make sure it's solid, perhaps we can get others to help with this

part of the issue is to do pagination you need to cache queries and their results, so it must be spam-protected, and it's dependent on implementing a state cache for the queries
Avatar
semisol 1y ago

yes, 99% of extensions will act like tag queries, but based off of other things (such as links in content field)

I am considering an advanced search extension, which can be easier to implement in an external search DB

Reply to this note

Please Login to reply.

Discussion

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

adding full text searching is independent of the pagination issue, there is a NIP for the search field, i forget what it is, but it's a separate matter from providing a query state cache and pagination that depends on that cache to make possible

you can make a full text search (including, potentially, searching tag fields, i guess) separately from implementing pagination

don't muddle the two things together, the relay can already signal search field support in nip-11, and the results from using this with a REQ as in NIP-01 you get an even bigger problem with pagination

so, solve pagination first, then add the full text search

Avatar
semisol 1y ago

NIP-50 has the problem that it is extremely limited