Rate Limiting
# 👀feature-requestsf
freezing-carpenter-9818
04/08/2024, 4:29 PMI think this really does need to be introduced. A lot of people have API Rate anxiety. We need to have a feature where we can enable a message limit in our bot settings, this will be based on per conversation. Looped conversations have a great risk of being misused and i feel as though we should some kind method in place to stop that especially when a bot is using external tools.
Please could we see this implemented soon.
r
rich-battery-69172
04/09/2024, 1:21 PMI think Botpress could provide some high-level protection but this wouldn't be bullet proof. It really depends on the messaging channel. For example, on Webchat, Webhook and API integrations we could use the IP address, since the client communicates directly with the integration via HTTP. For other channels, we would need to limit on some other unique identifiers such as phone number for Whatsapp & Telegram.
Limiting by conversation may not be sufficent protection, as with webchat you can simply clear your cookies and start a new conversation?
q
quick-musician-29561
04/14/2024, 1:49 PMCheck if what I mentioned in today's messages is one possible idea and solution for message limiting until Botpress releases an official feature
https://discord.com/channels/1108396290624213082/1227955163373768714/1229064920155422750
quick-musician-29561
04/14/2024, 1:50 PM"The first version used four GPT-3.5 research agents. Now, I'm adding an option for users to select 'fastest models' or 'latest models.' The latest models are the most effective LLMs so far, with seven agents improving each others results them, including GPT-4, Claude-3, Mixtral-8x7b, and Llama2-70b. **For the 'latest' models, I'll add a 'limit messages' feature, allowing each chatbot user to use these more expensive LLMs and APIs only twice a day (in a 24-hour period). The 'fastest models,' using GPT-3.5, will always be available.**"
quick-musician-29561
04/14/2024, 1:58 PMI'm not using CRON or scheduled triggers for that, due to many things we tested earlier where those didn't work. If the user reloads the page often enough, or clears the cache, user variables are reset to zero. So even though they have already used 2 messages, 'used messages' shows as 0. So, I created a custom solution where we store timestamps and remaining messages in a KB table. It's easy and quick, and chatbot users can't reset those with any tricks (users login with username and password).
quick-musician-29561
04/14/2024, 1:59 PMf
fresh-fireman-491
04/14/2024, 3:05 PMJust an idea, while reading Devmiks and AAs messages.
We could either hide the bot completely from the website or just remove the input field after x amount of messages
6 Views