MrKaplan @ MrKaplan @lemmy.world

other accounts:

---

Read more

Posts

2

Comments

366

Joined

1 yr. ago

Moderating

---

probably, this caching is just affecting the default lemmy web interface.

other apps or web interfaces may have their own caching implementations, though for web based stuff it's typically fine to leave it up to the browser, as long as there are suitable cache-control headers sent by the server.

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.

how long does it take in an incognito browser window?

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

i think it was just never cleaned up after you fixed it on your end.

merging accounts together is rather painful afaik. there are a total of 15 users or so with http://kbin.earth/ actor ids in our db :/

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.

yay, database inconsistencies.

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.

at least in lemmy's db structure, it wouldn't make that much of a difference compared to other tables that use significantly more space:

how does that affect db bloat? or rather, how does it protect from that?

please mark this post as nsfw as soon as possible. the next lemmy version should enforce this when the community is marked as nsfw, but most instances are running the stable version that does not have this functionality yet.

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".

Ruud and Stux are not the only people involved.

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.

probably. the check for higher modes was changed for 0.19.6 in https://github.com/LemmyNet/lemmy/pull/4860, but before that it seems like all mods could remove other mods.

I've removed both other mods now

they can, but only those that were appointed after them

internal team discussion relating to that request. searching by trump was not really an option, but searching for the username did bring it up.

you requested this here: https://midwest.social/comment/12017524

you can leave the mod team by using the "Leave mod team" button on the community page

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.