there were some caching issues in lemmy-ui where it would unnecessarily eat up disk space for caching without even making use of it properly. there was a change done in 0.19.12 that was supposed to mitigate this, but for users who have already collected this it won't automatically delete the unnecessary cache until they logout: https://github.com/LemmyNet/lemmy-ui/pull/3150
even when clearing this manually though i still see this take longer than you'd expect to load, it seems that the image cache is still slowing things down.
i also had some delays on images on the front page before all media loaded. i was able to speed things up again by executing await window.caches.delete("image-cache") in my browser dev tools console, but that is certainly not something to expect from regular users.
where are you located? do you have an example of things loading slowly? for me things are loading instantly, but if you're not within the EU you're likely dealing with latency across the globe
yes, post_read marks which posts a user has marked as read. it links post ids with user ids and adds a timestamp on top to allow for sorting.
edit:
for comments, lemmy only stores the number of read comments per post, which is what goes into person_post_aggregates. this is a tradeoff, it has some limitations, e.g. when comments are deleted or removed, which affects the total count. as there is also a timestamp attached it might be possible to use that in combination with comment creation times, though this would likely impact query performance quite a bit more.
looks like kbin.earth has a broken setup at some point where their user profiles were using http instead of https urls and that results in random breakage in lemmy:
something doesn't seem to be right there. i can reproduce it with this comment but not with other comments they created. also, the comment doesn't show up on their profile.
can you think of any solution that is not a variation of “keep finding fresh volunteers to work until they burn out”?
how would paying admins prevent burnout? the only difference i see here is that it is probably easier to find people willing to do it as a paid job than volunteers, but they can both burn out. this would just change it from "keep finding fresh volunteers" to "keep finding fresh job applicants".
I'm personally only involved in Ruud's side of things (mostly .world instances). Stux' platforms are managed separately, I can't say too much about those. Afaik finances between Ruud's instances and Stux' instances are also separate.
On the .world side, we currently have 6 active members for infra. For moderation, LW currently has 4 active instance admins plus some community team members with elevated privileges. Other .world platforms have moderation separate from LW. We certainly don't have resources to hire professional admins, but I'm sure that we would find a viable solution if Ruud ever wanted to leave things behind. Not all solutions require paying someone a salary for it, which seems to be your implication here.
I don't think "too big to fail" is as much of a factor here as the fact that LW is not the only FHF platform. Fedihosting Foundation, the non-profit behind Lemmy.World and our other platforms, existed before Lemmy.World already. While the Lemmy moderation team is working mostly independently from the rest of FHF, if the LW admin team disappeared there would still be FHF in a position to search for new admins and probably also at least temporarily step in without requiring to shut down the instance.
I don't see us going down anytime soon, and at current user numbers I don't think there's going to be a major difference in moderation workload with the influx of users compared to what we already have, but it really is not great for decentralization. We already try delegating the majority of moderation to community moderators where applicable, where on a lot of other instances the admin teams seem to be more involved in addressing community reports on admin level as well. For the most part we're dealing only with instance level topics in the admin team and provide some additional tooling to improve report notifications to community mods. There are even various benefits from a moderation perspective when users are all local and not remote, as with federation a lot of signals that would allow various types of abuse are unfortunately lost. That said, I would still prefer if there were more stable and larger instances overall, while not having a single instance stand out as massively larger than any other one. Friendly "competition" is almost always beneficial for everyone involved.
lemm.ee being the second largest instance and the shutdown only being announced less than a month before is unfortunately also not something that gives people looking for a stable instance much confidence. I hope this won't scare too many users away from Lemmy and that most will just find a new instance in the Fediverse.
Instance moderation and moderation in general are unfortunately tasks that can be very challenging at scale, even with just a few thousand users, especially when dealing with drama. It's not really a surprise that there are somewhat frequently posts from larger instances looking for new admins, while older admins on the same instance are becoming less active. Even if people aren't exhausted from their involvement, their circumstances in life may change, or they may no longer be interested in Lemmy as a platform in general, leading to a number of reasons why admins may not be as active as it seems when looking at the list of admins in an instance sidebar. It's often a thankless job with a lot of things happening in the background to deal with spam, trolls and other issues, which most users won't even see when done right.
as this has since been clarified by @nutomic@lemmy.ml, i have updated my comment above and can confirm that it is in fact 0% of lemmy.world/fedihosting foundation donations that go towards the lemmy.ml instance rather than 0.05%.
i've banned all the accounts i could identify as part of this scheme from lemmy.world now.
i originally sent them a warning before i was aware of the scale of this involving a bunch of alts with different usernames. if i had known that when i sent the warning it would've been a ban straight away.
they replied to my warning pretending they didn't know about any recent vote manipulation, so they're clearly not interested in acting in good faith going forward.
yes, we have a matrix room for coordinated efforts against spam and other types of abuse, which admins are welcome to join.
once lemmy allows reporting user profiles directly this will probably become more likely to reach the instances admins of instances that are less actively maintained as well.
I've sent out warnings to 10 other users in the past few days about similar behavior already and also banned two users for this type of behavior. one of them appealed and is unbanned again.
I also had this account in my list of such accounts, but I hadn't followed up on it yet, as I figured I'd just deal with the top n users and then review it again at a later point in time.
i've sent them a warning about this as well now that they'll get banned from our instance if they continue engaging in this behavior.
there were some caching issues in lemmy-ui where it would unnecessarily eat up disk space for caching without even making use of it properly. there was a change done in 0.19.12 that was supposed to mitigate this, but for users who have already collected this it won't automatically delete the unnecessary cache until they logout: https://github.com/LemmyNet/lemmy-ui/pull/3150
even when clearing this manually though i still see this take longer than you'd expect to load, it seems that the image cache is still slowing things down.
i also had some delays on images on the front page before all media loaded. i was able to speed things up again by executing
await window.caches.delete("image-cache")in my browser dev tools console, but that is certainly not something to expect from regular users.i've raised a new issue about this now: https://github.com/LemmyNet/lemmy-ui/issues/3195
meanwhile, you can also work around this by deleting cached data for lemmy.world in your browser, at least until it fills up again.