Oh and of course making hashtags clickable and searchable, that will be quick to add so I should do that first #damus

Reply to this note

Please Login to reply.

Discussion

One glaring issue with relays right now is that you can't put a limit result on initial queries

you can control what you receive, so you can close the connection after reaching your limit, no?

Yeah but I like to keep connections open so I don't have to do a TLS handshake after every query.

so send a new req with a since filter

well yeah I already do that, but I don't go out of my way to kill connections after every query. I guess I could create an abstraction that does this for one-off stuff... bleh

Thinking about it some more, this wouldn't work because created_at order is not defined and it would need to be desc

what's your objective? what are you trying to achieve?

ah so you're querying #hashtags and handling those results?

Yes you can't use a since filter here effectively without a lot of probing. They main issue is that some relays return way too much data so we should just add a limit to the spec.

what's too much data for a query?

hashtags, infinite scrollback paged chatrooms. All of these are very hard to do without having some kind of limit option with implied created_at desc ordering in a query.