RocketDerp
RocketDerp
We were discussing this scalability problem in Lemmy 0.17.4/0.18.0 just 4 hours before the sever was crashing in **/c/lemmyperformance** https://lemmy.ml/comment/902380
> paired with an order by somewhere in the generated statement. [As I commented on Lemmy 4 days ago](https://lemmy.ml/comment/793612), the comment loading has to slice a string to determine the...
> for example if a user deletes a comment, or his account, what happens? Is the parent comment preserved as a placeholder? I know 'removed by creator' does get tombstoned...
I'm all for emergency code changes to fix performance. That said, is there a test case on how this impacts comment replies? If I'm grasping what this code is doing.......
Can these limits be lifted now that SQL TRIGGER statements have been addressed, issue #2910 ?
> by attacking a vulnerability having to do with high-comment threads. Can someone please give a link to an actual post that this happened in production? So we can add...
What's the situation with 0.18.3 - is it current now?
See also Issue #3296
> (the first error is usually just silently ignored, i added code to make it visible) Please share!