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
Would it be possible to add an optional setting to limit the number of interactions that a user can have with the GPT chatbot? Kind of like the way Bing Chat limits you to 30 questions.
The number of interactions should be configurable at a site level and also at an instance level with a maximum equal to the value set in the plugin's settings, if one is set. Once a user runs out of questions, they would be able to restart a new chat session but lose the context of the current conversation. An interaction counter should be displayed with each interaction.
The reason for this request is to try to curb abuse (and cost) associated with people using the chatbot for unrelated purposes and also to reduce the cost of resubmitting an ever-growing history.
Another option might be to limit its memory to X number of interactions and then drop the oldest one as the conversation goes on. I must confess that I have not thought this option through and suspect that loss of context might end up being confusing.
Let me know if you have any questions.
Best regards,
Michael
The text was updated successfully, but these errors were encountered:
Hi @Limekiller ,
Would it be possible to add an optional setting to limit the number of interactions that a user can have with the GPT chatbot? Kind of like the way Bing Chat limits you to 30 questions.
The number of interactions should be configurable at a site level and also at an instance level with a maximum equal to the value set in the plugin's settings, if one is set. Once a user runs out of questions, they would be able to restart a new chat session but lose the context of the current conversation. An interaction counter should be displayed with each interaction.
The reason for this request is to try to curb abuse (and cost) associated with people using the chatbot for unrelated purposes and also to reduce the cost of resubmitting an ever-growing history.
Another option might be to limit its memory to X number of interactions and then drop the oldest one as the conversation goes on. I must confess that I have not thought this option through and suspect that loss of context might end up being confusing.
Let me know if you have any questions.
Best regards,
Michael
The text was updated successfully, but these errors were encountered: