Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)NY
Posts
0
Comments
94
Joined
11 mo. ago

  • I'm pretty sure it's doable but it might be necessary to become a mod first, which admins should be able to in remote communities as well iirc. it's just that their mod actions won't federate.

  • I think my grafana is newer and stuff is deprecated

    that's unlikely, i'm running 11.2.4 currently.

    yes, you'll need to run that exporter against each instance you want to be monitoring.

    my setup looks more or less like this: https://github.com/Nothing4You/grafana.lem.rocks

    depending on the grafana version you are using you may be running into this bug though: https://github.com/grafana/grafana/issues/96356

  • Then I generated sql statements to remove duplicate posts that had higher ids than the other posts theyre a duplicate of

    i assume this was done after updating the other tables referencing this table, such as comments, votes, saved posts, as previously discussed on matrix?

    while it may be omitted here for simplicity, it can be dangerous to not mention that for others that might find this in the future if they experience index corruptions on their own if they don't fix all references, as that would result in data loss.

  • you can only set a community to only allow local users, not prevent users from interacting with remote communities.

    you'd have to either disable federation or set up a script to automatically remove all remote communities, but that also won't be a per user thing, just a per instance thing.

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

  • lemmy has a public api that shows the federation queue state for all linked instances.

    it provides the internal numeric id of the last activity that was successfully sent to an instance, as well as the timestamp of the activity that was sent, and also when it was sent. it also includes data like how many times sending was unsuccessful since the last successful send. each instance only knows about its own outbound federation, but you can just collect this information from both sides to get the full picture.

    there is also https://phiresky.github.io/lemmy-federation-state/site to look at the details provided by a specific instance.

  • it's not just lemmy.world.

    of the larger instances, the following have trouble sending activities to lemm.ee currently:

    i pinged @sunaurus@lemm.ee on matrix about 30h ago already about the issues with federation from lemmynsfw.com, as it was the first one i noticed, but I haven't heard back yet.