You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to improve the interaction between both fields.
Many comments are indicating changes to the machine itself and should better be submitted via "Report Change". When a comment is could we should add a first pop-up (preceding the current one with the warning about public visibility) where we ask the user whether this is only a comment or a change / improvement of machine features (e.g., status, paywall, multimachine etc). Users could then either click Report change (Switches to the other view) or proceed with Understood, this is a comment.
We could also try to it automatically with a LLM that is extracting potential machine changes and submitting those separately
In the ReportChange view we should add an obligatory comment field that asks the user to explain their changes. This should help us to check whether the change is trustworthy
The text was updated successfully, but these errors were encountered:
We have to improve the interaction between both fields.
Many comments are indicating changes to the machine itself and should better be submitted via "Report Change". When a comment is could we should add a first pop-up (preceding the current one with the warning about public visibility) where we ask the user whether this is only a comment or a change / improvement of machine features (e.g., status, paywall, multimachine etc). Users could then either click
Report change
(Switches to the other view) or proceed withUnderstood, this is a comment
.We could also try to it automatically with a LLM that is extracting potential machine changes and submitting those separately
In the ReportChange view we should add an obligatory comment field that asks the user to explain their changes. This should help us to check whether the change is trustworthy
The text was updated successfully, but these errors were encountered: