• 0 Posts
  • 68 Comments
Joined 11 months ago
cake
Cake day: March 24th, 2024

help-circle



  • You basically can’t if your instance was set up before 0.19.4, as there won’t be any association between users and uploads for older uploads. You also can’t do this without breaking thumbnails everywhere unfortunately.

    The latest Lemmy version has a fix where thumbnails now are actually stored at a reasonable resolution for thumbnails, but old thumbnails may be quite large, and this does not retroactively shrink older thumbnails.

    It’s possible to pull image aliases from the DB and ignore them when iterating over aliases within pict-rs, but you these will only be manual uploads, not automatic uploads like generated thumbnails. For posts by local users, deleting thumbnails will also end up breaking them for 0.19.5+ instances, as they should reuse the original thumbnail url.


  • fwiw, the estimate number only states the max amount of activities behind. the real number can be lower, but not higher (unless sending is entirely broken on the instance being checked).

    each activity being sent has a numeric id in the database. lemmy has an api that returns the id of the last activity that was either successfully sent to an instance or skipped when it didn’t need to get sent (e.g. pm to a user on a different instance). there may also be holes in activity ids due to postgres implementation details for auto-incrementing sequence ids.

    for determining the highest known activity id to compare it with the last activity id sent to a specific instance, you can just go through the successfully sent ids for all instances in the response and find the highest number across them all. then you can calculate the difference between the highest number and the number for the specific instance.

    depending on the lemmy version and timing of the action, it can take up to 30 seconds for the activity queue to deal with new activities, so on a somewhat busy instance the delta is likely rarely going to be zero.






  • pretty much, yeah. lemmy has a persistent federation queue instead of fire and forget requests when activities get generated. this means activities can be retried if they fail. this allows for (theoretically) lossless federation even if an instance is down for maintenance or other reasons. if mbin has a similar system maybe they could expose that as well, but unless the system is fairly similar in the way it represents this data it will be challenging to integrate it in a view like this without having to create dedicated mbin dashboard.




  • at least the image resizing topic has recently been fixed in lemmy, thumbnails sizes are limited (at the time of thumbnail creation) in the latest release. I’d have to look closer at the other stuff, the api part is unlikely to have changed and will affect all frontends, but js part should differ depending on the front end. some instances already use other frontends by default and there is also a replacement for lemmy-ui being worked on (lemmy-ui-leptos), but I don’t know how they compare. either.

    it should be taken into account though how much of this is cacheable as well, as it will then typically only affect the first load for the static files.

    I can totally understand the issues in general though, I’ve been living with a 64kbps uplink for several years in the past.