other accounts:

  • 2 Posts
  • 316 Comments
Joined 1 year ago
cake
Cake day: February 10th, 2024

help-circle



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






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