Nothing4You

0.4.1 is pretty old, but the link you provided leads to a manifest.toml that seems to indicate 0.5.17.

pict-rs introduced temp file cleanup in 0.5.10, but that might not have cleaned up old media if you only recently upgraded.

from a short look at the repo i didn't see where /lemmy/magick/ is defined, so i'm not sure if that is indeed the pict-rs temp folder.

modlog view is a bit broken currently and doesn't make much sense if you don't know how it works.

the modlog view currently merges the different types of modlog entries in a single view, but the pagination doesn't make much sense that way.

for example, removing a comment is an action that happens quite frequently, but removing a community does not. the modlog shows e.g. up to 20 actions per modlog entry type, so you may see comment removals for the last few hours, but community removals could be for the past year. then when you hit next page, you'll see the next page for each type, but the times make even less sense now. you'll see entries 20-40 for comments, but also 20-40 for communities.

the timeline will be consistent when you filter for specific entry types.

you can simply check your profile and modlog on the instance in question. it'll show that you got banned from that instance 8 days ago. since you didn't participate in any community on that instance there were no community bans federated out. instance bans currently don't federate, only community bans for communities on the instance you got banned from, if you have previously participated in them.

not sure about the yunohost setup, but this sounds a bit like you may be running an old pict-rs version that had a bug that lead to temporary files not being cleaned up. especially newer versions will clean up the temp folders on startup even if some old stuff was left behind previously. which version of pict-rs are you running?

seems like just nobody thought of closing it before, it was already implemented.

this is most likely the case, pict-rs headers allow caching basically forever and don't include revalidation. i'll bring this up with the pict-rs dev about changing the default or adding a config option for this.

something like s-maxage should do the job, though it'd probably be up to the instance operator to decide on a sane value for that, as it will always be a tradeoff.

ideally, lemmy would have a mechanism for cache purging, but i suspect that this might be something that people will have to implement themselves using the 1.0 plugin system at some point, as it's probably not going to become core functionality to support e.g. cloudflare cache purging.

edit: it seems that the 1 year cache is already an override by aussie.zone - pict-rs only sets a 7 day max-age, which is passed on by lemmy as can be seen e.g. on lemmy.ml, which isn't behind cloudflare, or on progamming.dev, which is behind cloudflare but doesn't seem to be overriding it.

eingeschränkt.

wenn du in Lemmy eine instanz blockierst werden erst mal nur communities von der instanz ausgeblendet, aber die nuzter der instanzen wirst du weiterhin in anderen communities antreffen. ein paar apps haben das meine ich clientseitig umgesetzt um auch nutzer von den geblockten instanzen auszublenden, aber das ist dann nur in den entsprechenden apps so.

grafana.lem.rocks isn't operated by lemmy.world.

as I was traveling for the past couple days I didn't get to fix earlier, but everything should be working again now.

mod actions generally do federate correctly, at least on the latest lemmy versions. it's just reports that don't.

but in general, you will need an account on the community instance to get full federation abilities when you take potential instance bans and defederations into account. even when it's not a defederation, if a user is banned from your instance but not from the community instance their posts won't make it to you.

this doesn't really change anything for how remote users are displayed, it's a change to properly support hosting lemmy-ui on a different domain than the lemmy backend/api.

what are you referring to with mastodon short.domain handles?

the unban itself federates, but on community bans the user gets unsubscribed from the communities, which deletes the associated subscription in the db.

skimming over the code it seems to be only happening in case of community bans (including the ones derived from instance bans on 0.19), but it should also remove your local subscription on your own instance. as long as that federates it should still be picked up by lemmy-federate eventually, as your local instance should also have removed that when receiving the community ban.

it might be debatable whether subscriptions should get removed with community bans for public communities, but overall the code logic seems to be there. i haven't tested this end to end yet.

instance bans currently generally don’t federate and won’t show in the modlog of your home instance, but recent lemmy versions are automatically issuing community bans for all communities on that instance that you participated in, which allows you to at least see this in some cases indirectly.

1.0 will federate instance bans, but i haven't looked at the implementation in detail yet and i'm not sure if this is already implemented to be shown in the modlog.