-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deactivated users should not be suggested in chat/comments mentions and on the sharee endpoint. #9948
Comments
GitMate.io thinks possibly related issues are #6755 (Disabled users should not be suggested in the sharee dialog), #4555 (Mentioned user not clickable after posting a comment), #753 (user mentions in comments), #6038 (User shouldn't be shown in contactlist if the account is deactivated), and #2443 (Missing pieces: user mentions in Comments). |
Also it should not be possible to initiate a Talk conversation with a disabled user. At present you can, by clicking on the |
@diplodata that is the same issue. It's all using the same endpoint ;) |
This comment was marked as outdated.
This comment was marked as outdated.
Disabling users was designed to only reject them logging in. If we want this to change, we ought to write a comprehensive concept describing what the consequences shall be generally, not just about a single point. |
This comment was marked as outdated.
This comment was marked as outdated.
Still an issue |
But maybe bug is the wrong label. It's more of a discussion field of what the scope is and to clarify it. Currently it fails to match 90% of the user expectations. |
then lets use a different label :) |
See nextcloud/spreed#959
Or does anyone know a reason why they should? @MorrisJobke @blizzz
The text was updated successfully, but these errors were encountered: