Sensitive words

[starweavingdream]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

During my use, I found that some users would raise some very sensitive questions, and then take screenshots of these questions and the answers given by the model and use them for other non-normal purposes; although Dify provides relevant content review functions, it only has 100 lines, which is obviously not enough. Although it provides API calls, it is relatively redundant to set up a separate service for sensitive word management. And the cost will be a bit high.

I hope to have a sensitive word management function in Dify, that is, to maintain sensitive words in a table. Instead of being fixed in the chat room as it is now, the sensitive word information can only be limited to 100 lines, and the short input box is not so easy to maintain. I hope to reference the data from the sensitive word management here later.

2. Additional context or comments

No response

3. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[crazywoola]

What about using a knowledge base to achieve this feature?

[starweavingdream]

@crazywoola I think it is feasible, but it is better to have an attribute to distinguish the two, because the knowledge base needs to be indexed, but sensitive words do not need this. Of course, in order to avoid development costs, it is also possible to apply it directly.

[luckylhb90]

We used the aws guardrail feature, and unfortunately, we had to pay quite a bit.

[dosubot[bot]]

Hi, @starweavingdream. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You suggested enhancing the sensitive word management feature with a table-based system.
• Crazywoola proposed using a knowledge base, but you noted it would need attribute distinctions.
• Luckylhb90 mentioned AWS's guardrail feature, but it was costly.

Next Steps:

• Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
• Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!