clicking on some user links / @mentions in my bot logging channels is now giving a pop‐up denying access to the profile:

additionally, the right‐click menu on these no longer has any moderator actions:

this removes the ability to ban users who aren’t server members and have no posted messages using the GUI. (this has always been impossible on the mobile clients.) i believe they can still be manually banned by ID using commands, but having quick access to these actions from the bot logging channel was a big time‐saver, and more accessible for moderators who aren’t comfortable with commands.
my own testing has shown that this new behaviour only happens when the @mention only shows the user ID and hasn’t resolved to the display name yet (buggy behaviour that’s been around for years). scrolling around in the channel history or switching between channels such that the @mention is forced to reload can sometimes cause the @mention to change into a proper one that can be interacted with properly (this screenshot is of the exact same log message as the one above):

this does not happen because the user is no longer a server member. user profiles have always been accessible regardless of membership status, even if they don’t load everything:

i want to say this is a bug, but this new behaviour of telling me i don’t have access to these user links is consistent between the mobile and web/desktop clients. i have no idea what on earth Discord is doing, but it’s making our jobs as moderators needlessly more difficult.
you may have noticed that i apparently have access to a new “Mod View” feature in the proper right‐click menu. that looks like this:

this is moderately useful, but it does not work/load at all for users who aren’t server members. what’s the deal with Discord inhibiting moderators from taking actions on users who aren’t members?? users joining, posting some stuff that either gets caught by bots or that they delete shortly thereafter, leaving, and repeating this process is not an esoteric situation! if we didn’t have a bot logging message deletion and member join/leave events, we’d be hard‐pressed to do anything about these events unless we happened to be present the moment they happened!