this post was submitted on 06 Aug 2023
1463 points (99.0% liked)

Announcements

23360 readers
6 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
 

This is an opportunity for any users, server admins, or interested third parties to ask anything they'd like to @[email protected] and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.

Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.

Original Announcement thread

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 41 points 1 year ago (2 children)

Maybe I'm completely misremembering things, but at some point wasn't there a hotfix to Lemmy that hard-limited how many comments a thread could have? Does anyone know if there's a maximum and if so how many?

Just wondering, cause uh, I could see this one having a lot of comments.

[–] [email protected] 34 points 1 year ago

The fix you are referring to only limits how many comments can be retrieved in a single API call (300). This limit is only used when specific parameters are passed, not in all cases.

[–] [email protected] 31 points 1 year ago

Tree-paging is a pretty complicated issue, and we really do need some DB / SQL experts to help us with figuring out how to page them correctly. The limit is 300, but only for the top-level comment fetch, which could also have different slices whether you sort by top, or new, and doesn't apply to the nested comments, which could have thousands.

The limit is a kludge, because ppl were creating thousands of comments, and without proper paging, it was affecting performance.