-
@ mleku
2025-02-06 10:25:33
i'm not gonna say i told you so but i will probably say i told you so when you discover the additional complexity of adding a query state cache to enable pagination
the better option is to return references to the results so the client can hold this state because it's their business, after all
i've been hinting at the idea of adding a new way of doing filter/text search queries where they return the whole set of event IDs instead of the whole events, because bandwidth is a client problem and for the majority of filter queries, a second match isn't required, meaning the event doesn't need to be decoded from teh database, only its ID found
anyway, i also think that admin API for nostr relays needs to be made more generalised and not baked into the same silly pattern as the nip-01 mashup of event by id and filter match, and teh confusing context-dependent envelope sentinels that you have to interpret based on role