the lack of pagination in the mastodon context endpoint is literally so broken.

jonny (good kind)

the lack of pagination in the mastodon context endpoint is literally so broken. this is for a post with a lot, but not that many replies (~300), and masto will just freeze and send you... all of them. every time. sometimes twice.

#mastodev

https://media.neuromatch.social/media_attachments/files/113/332/526/255/327/402/original/bd7e97f9e1ea6643.png

Helge

"If the lookup is cached, fetching it twice might get you around the initial timeout. As databases are often smart, this might even help without implementing any caching." - advice from hell

jonny (good kind)

@helge i wonder what is more expensive, fetching and potentially caching 100% of every reply tree every time, or fetching and potentially caching pages of a reply tree as they are requested. hmmmmmm

Jenniferplusplus

@jonny @helge the more expensive thing is pretending that materialized views are the same thing as tables, and not adding an index to support this very common and obvious use case.