To implement this, you may want to start from this 🌈

In T15749#16629, @avivey wrote:

Maybe put the warning above the box, so it catches all actions, not just comments?

:p

I was responding to the previous comment which...

Our company uses the Phorge, and we use Keycloak as IAM. Keycloak is a very popular OAuth2/SAML provider now.

Maybe put the warning above the box, so it catches all actions, not just comments?

GitHub/Facebook is already supported as an Login/Registration providers.

Yes will be great to see a SAML or Oauth support for external authorities like:

• Keycloak
• Entra ID
• Github
• Facebook
• WeChat / WeCom

Interesting. I see. Maybe expanding its controller that should be this one:

Yeah, in this one special place it doesn't matter; But that page already have a special body, so we can save even the extra click by putting the message right there...

OK I see. Indeed we should not put any similar button anywhere else.

But in Diffusion, that button is hidden behind a "Actions -> Manage" button, inside a screen that also has dozens of other admin actions. The clutter cost there is minimized.

I see. Maybe the root problem is that I'm in love with that Diffusion popup 🤔

In that case, we don't even need another button - just add a line to the "deleted message" that says something like "To completely remove the history from the database, contact your admin".

Premising the user already have an Delete Document button.

I feel that adding such a button would clutter the UI.
Users should generally "know" that in order to really delete things, they need to go to the admin, because they don't have the permissions anyway; And adding that just for the once-in-a-while that the admin needs this...

I mean, we can maybe have a "Delete" button that just shows the related CLI command, like I've seen around (Diffusion maybe)

I don't think we actually allow "deleting" from the web ui, only hiding it (in the sense that the data is not removed from the database).

This feature request could also be expanded to:

I agree, badges seems like the right way to go. They are an underutilized feature really, IMO.

I've looked down some of the links of this request, and it looks like the definition of "new user" should be install-specific, and open to interpretation.

there is a presentation from eric brechner, who was in microsofts xbox development, about kanban. he does it on whiteboard, extremely sinple:
https://www.youtube.com/watch?v=CD0y-aU1sXo

I don't see the point in having this feature. What is it for?

Should this be configurable and behind a feature flag, as some Phorge installations may not want this (plus may slow down performance a little bit)?

I think a dedicated policy for "Can send messages" would be better, to cover more cases. It would be strange that all participants must also be allowed to edit all settings.