So as yall can tell, with this huge influx of users lately, lemmy has gotten really, often unbearably slow. This is entirely my fault for not structuring the database caching (lemmy currently uses a SQL technique called materialized views), in a proper way.

With a small amount of users / posts, it seemed fine, but as we scaled up, this is proving not to be a good method to do caching. These past few days (even with all the adoption), I managed to build a way to do that increases speed by maybe 30%, but its still not good enough, so I’m tackling it from a few different angles. All my other work is on hold, because this seems to me to be the most important thing to handle right now.

In other news, !chapotraphouse@lemmy.ml is in the process of making a lemmy instance, and we’ve seen a few others pop up too. Once we deploy federation, we’ll be happy to federate with them, and link them in an official instance list.

Also we’ve got some movement on people building a lemmy mobile app, as well as @IronOxidizer@lemmy.ml 's building a lemmy-lite, a liteweight non-javascript front end, which when done, we’ll be happy to bundle with lemmy directly (Possibly at lemmy.ml/lite) which would be great to have.

My original ideas were to have a web app (like this one), a native android app written in kotlin + jetpack, and a terminal app like rtv / tuir, so its great to see development here.

Let me know anything I can do to improve the site, and especially be sure to add feature requests to the github. Thanks!