Nothing4You

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.

they won’t be sent by infosec.pub directly, but other instances may send activities referencing content from infosec.pub, which will lead lemmy.ml to pull it from the source as well.

this includes for example posts and comments in lemmy.world communities, because lemmy.world will announce those to lemmy.ml.

to add to that, Lemmy currently does not handle site bans well if it’s not a home instance ban, as instances don’t keep track of which other instances have banned which users. this should get better with 1.0 though, as a PR to improve that was recently merged.

for now, there is a band-aid solution that federates community bans for all communities local to the instance the user got banned from, but that only includes communities that the user previously participated in, so they’ll still be able to participate in the local copies of other communities from the instance they’re banned from, it just won’t fully federate out.

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.