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.
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
looks like the federation issues were just related to feddit.nl sending to lemmy.world, did you figure out what caused this?
the lemmy backend was supposed to mark posts in NSFW communities as NSFW automatically going forward, which is why the UI option in standard lemmy-ui was removed to mark a post as NSFW if the community is NSFW.
unfortunately while the UI change made it to 0.19, the backend change didn't, so currently people posting in NSFW communities from 0.19.11 lemmy-ui will not have a choice to mark their posts NSFW.
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-maxageshould 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.