Dessalines
admin
creator
87M

Lots of stuff this last week, as you can tell the DB changes got merged, so Lemmy is really fast now.

While @nutomic@lemmy.ml was working on some back-end re-organizing to reduce our compile times, I finished a lot of outstanding front end tickets, including:

  • You can now remove your avatars.
  • Adding code contributors to the sidebar.
  • Added selecting for quoting comments.
  • Some redirects to login / sign up page when not logged in.
  • Blocking a page refresh when forms are filled. (We already had route change blocking).
  • Cake days added. Thanks to @Filip785@lemmy.ml
  • Fixed prev / next not showing correctly.
@Kamui
67M

Thank you, everyone, for your hard work!

Dessalines
admin
creator
27M

np :)

@nutomic
admin
57M

This week I was mainly working on reorganizing the backend, and splitting it into different cargo workspaces. I mainly did that with the goal of speeding up compilation time, but unfortunately that wasnt successful, its exactly as slow as before (3m 40s for a clean build on my Ryzen 5 2600). The reason is that Diesel, our library for interacting with the database is completely dominating compilation time. There is one thing we could do to, but it would require another database rework.

For visualization, the long bar in the graph below is Diesel, and Lemmy itself can only be compiled once that is finished (which takes around 95s for me).

Other than that, we approved new rules for the Lemmy Council, which are much clearer and easier to understand (PR for it is here).

but the database library version doesn’t change that often, which means you could somehow cache that.

@nutomic
admin
26M

There are a many use cases where the time for a clean build matters:

  • a new contributor compiles the project for the first time
  • continuous integration often builds everything from scratch
  • docker builds dont have good dependency caching

Besides, I can sometimes see Diesel being rebuilt in incremental builds for no reason at all, and it sucks waiting almost two minutes for that.

@nutomic
admin
27M

Actually I wanted to write a bit more about the workspaces, but forgot while taking the screenshot. Besides faster compilation, the workspaces are also useful for splitting a project into smaller units that are easier to manage. This means someone can now work on the database without affecting someone who works in the activitypub code (as long as the public interface doesnt change). It also gets much easier to see how the code should be split up, for example I noticed that it doesnt make sense encoding and decoding jwt tokens in the database, so I moved it out of there.

Freeplay
26M

Move the collapse comment button to the left. It’s just a much easier place to find and click, since you know where it will always be (and not be moved around due to the length of the text)

Dessalines
admin
creator
16M

That’s a thing from old reddit that I’m not a fan of… none of the mobile clients this front-end is based off of, do that anymore. This is mainly taking front end ideas from boost and slide, some really slick reddit apps for android.

The user should always go first. I might even re-arrange the front page to move votes from that old-school left bar, to below the post title, but that’ll come later.

@Alex1138
16M

I would like the notification icon a bit more visible, it’s waaay off to the right and it’d be nice if it were a bit more apparent

@yogthos
26M

I kind of like it where it myself. It’s there, but also not obtrusive right now.

How do I mod a community?

I haven’t been able to find anything in the docs and it’s not self evident to me

e: I guess I’m asking, can I delete other peoples posts? I see both sides; it would be good to enforce community rules, don’t want to be like reddit

Dessalines
admin
creator
17M

Mod actions are done on comments / posts. For any communities you mod, click the 3 dot menu on the right, and mod actions will appear.

Everything about Lemmy; bugs, gripes, praises, and advocacy.