What's the best method to track the most recent command in a chatbot?

Other Questions Telegram bot
1

I’m working on a chatbot and need help figuring out how to keep track of user commands. Here’s what I want to do:

  1. User sends a command like /ShowPic some_info
  2. User sends a picture
  3. User sends another picture
  4. User sends a third picture

I need to make sure the pictures are sent right after the /ShowPic command. I thought about saving each command in a database or using a cache system, but I’m worried about performance.

Is there a better way to do this? Maybe something built into the bot API that can remember the last command without needing to check the database every time?

I’m using C# but I’m open to ideas in other languages too. Thanks for any help!

2

From my experience, a simple yet effective approach is using a time-based tracking system. You could store the timestamp of the last /ShowPic command for each user, then check if incoming messages are within a certain timeframe (say, 2 minutes). This method is lightweight and doesn’t require complex state management.

In C#, you could use a ConcurrentDictionary<string, DateTime> to store user IDs and command timestamps. When a picture comes in, check if the user’s last command time is recent enough. This approach is fast, scales well, and handles multiple users without database overhead.

Remember to periodically clean up old entries to prevent memory bloat. This method has worked well in several of my projects, balancing simplicity and efficiency.

3

As someone who’s been in your shoes, I can tell you that tracking recent commands doesn’t have to be complicated. I’ve found that using a simple in-memory dictionary works wonders for this kind of scenario. It’s blazing fast compared to hitting a database every time.

Here’s what I do: I use the user’s ID as the key and store their last command as the value. When they send the /ShowPic command, I update their entry. Then, for the next few messages, I check if they’re sending pictures. If they are, I process them accordingly. If not, or after a certain timeout, I clear their entry.

This approach has served me well in several projects. It’s lightweight, efficient, and doesn’t require any extra infrastructure. Plus, it’s easy to implement in C# with a ConcurrentDictionary if you’re worried about thread safety. Just remember to handle cleanup periodically to prevent memory bloat if you have a lot of users.

4

hey luke, have u tried using a simple in-memory dictionary? it’s way faster than a database for this. just store the user ID as the key and their last command as the value. clear it when they send pics or after a timeout. no need to overcomplicate things, right?