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.
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.
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.
I didn’t mean only showing Anubis to unauthenticated users; this was in response to OP mentioning to add this before posting or commenting, which would be the opposite of removing it for authenticated users.
slrpnk.net has some first hand experience for this, as @poVoq@slrpnk.net already deployed anubis in front of lemmy-ui.
it wouldn’t be that complicated to add it to lemmy-ansible if people are interested in having the option.
i don’t see the argument for having this before user interaction though; the main goal of this is to fight malicious crawlers. for authenticated users, solutions like this are completely unnecessary as these can simply and much more efficiently be addressed through rate limits without putting users on low end hardware at a disadvantage and contributing to global warming.
it’s literally explained in the post that it uses admin credentials
it should cover all federated actions.
any instance admin can decide to ban you on their instance or remove your content on their instance, but unless it’s a local community or they’re mod of the community these actions won’t federate and will only apply to that specific instance.
the most useful one to look at is generally the one on the user’s home instance, as that should list all actions that federated.
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.
it’s also the case for deletions without account deletions, but iirc there is some delay before it gets rewritten in the db to allow the user to undelete it for a bit of time.
instances get added automatically once they reach a threshold of monthly active users. iirc it’s >6 mau, you could check the code to confirm.
you can find your user info in the /api/v3/site response. the /api/v3/user endpoint requires a name or person id.
i recommend checking out https://join-lemmy.org/api/classes/LemmyHttp.html
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.
delegating authentication to another service.
one of the more commonly known options would be sign in with google, but this is also quite useful for providers hosting multiple services. a provider could host a service that handles authentication and then you only have to login once and will automatically get logged in for their lemmy, xmpp, wiki and other services they might be providing.
verification emails are usually sent immediately. if there are delays you should check your junk folder, and if it’s not there it probably won’t arrive anymore. depending on the instance you signed up on there may be alternative methods to reach out to the instance admins about this. note that private messages from mastodon to lemmy do not work unfortunately.
also adding my vote for the second one
account names cannot be changed.
you can only change your display name, which is available in the settings.
whether display names or usernames are shown depends on the interface/client and user settings where available.
the only way to change the username is to create a new account.
i can see rust being a bit more challenging to support properly in an IDE and there still being various special cases not handled properly, and i’m glad that it’s free to use non-commercially, but with jetbrains rustrover i frequently see it calling out errors in code that happily compiles, autocomplete being semi-random in how it wants to complete today, which seems to have gotten worse with their recent AI pushes, and even a couple times the entire IDE locking up not too long ago, though i don’t remember whether the last part was in rustrover or one of their other IDEs. overall pycharm has been pretty stable for me, as long as you provide it with a pre-existing venv or let it create one for you, as the integration with the latest and greatest™ python package manager may not be there yet.