Hilariously wrong on all three points. It’s a Python script I wrote in under a minute making identical requests to the same thread fewer than 10 times a second; Lemmy’s complete lack of caching isn’t a “bug”. That this extremely simple vector instantly brought down even the high-spec Lemmy.World instance with a low volume of requests is sad, and it’s tiring to see Lemmy zealots spam my communities advertising this tankie spaghetti code jank as an alleged reddit “alternative” when it topples from this. The multiple attack vectors I’ve tested make it abundantly clear that Lemmy’s team has been incapable of performing even the most basic possible load testing.
Won’t be responding to or reading any replies, don’t care.
BTW, ltree is a horrifically bad solution for comment trees, and any of the self-proclaimed “Postgres professionals” in these threads should be able to explain why if they have even the slightest bit of RDBMS knowledge.
Hilariously wrong on all three points. It’s a Python script I wrote in under a minute making identical requests to the same thread fewer than 10 times a second; Lemmy’s complete lack of caching isn’t a “bug”. That this extremely simple vector instantly brought down even the high-spec Lemmy.World instance with a low volume of requests is sad, and it’s tiring to see Lemmy zealots spam my communities advertising this tankie spaghetti code jank as an alleged reddit “alternative” when it topples from this. The multiple attack vectors I’ve tested make it abundantly clear that Lemmy’s team has been incapable of performing even the most basic possible load testing.
Won’t be responding to or reading any replies, don’t care.
BTW, ltree is a horrifically bad solution for comment trees, and any of the self-proclaimed “Postgres professionals” in these threads should be able to explain why if they have even the slightest bit of RDBMS knowledge.