LIMIT and OFFSET, paging, inside IN filter https://dncrews.com/limit-and-offset-can-work-with-join-f03327fa2ad3
Surprised to see local on SJW have zero posts in 1 hour, it’s mid-day USA/Canada.
And another thing: https://sh.itjust.works/?dataType=Post&listingType=Local&page=1&sort=TopSixHour
Why not just do what I did with lemmy-helper? Create a time parameter directly… and it gets us as server programmers out of the equation. Any of the sorts should take a time parameter of old cutoff (even OLD sort order would benefit from “oldest in 6 months” ordering).
Either a unix epoch integer in UTC, or a minutes=x backin time. With a cap of say 10 days.
The routine SELECT queries for listing posts… pulls the private and public keys for both person and community. A lot of text bloat between PostgreSQL and Lemmy’s RUST code. I don’t think that gets sent down to JSON API client, does it? How does that get filtered out when handed off to JSON?
