SaifURLs-bot Used AI

After I created the last devlog, and thought that I had finished everything and went to make the testing video. I found a problem in updating and deleting short URLs. However, I was sure that I had tested that before, and all is working fine. After hours and hours trying to find what happened and living in the console. I was finally able to find the problem. The problem is that the database doesn't return the createdBy field in the shorturls, so reading that field to check whether the user is the owner of the shorturl by comparing their ID with the createdBy ID in the shorturls database always returns an error. How then, I was able to update and delete, I was using a super admin user in testing that made me able to edit and delete. That was a shock for me since that meant that the main website of the service wasn't working either, and I won't never recognize this problem. But thanks god, everything is working now.

I have finished the project with all of its functions and commands
That's what I have done briefly:

• Add /todo command: Complete setup guide for new users with step-by-step API key instructions
• Add /justtest command: Temporary test API key for SoM/Converge participants

• Automatic bot command setup: Deletes old commands and sets current command list

• Update command descriptions and help text

• Enhanced main menu with setup hints for users without API keys

• Updated welcome message to prominently feature /todo command

• Add setupBotCommands() function for automatic command management

• Integrate command setup into bot initialization process

• Clean up unused imports and fix linting issues

• Remove duplicate command setting logic

• Update systemd-compatible environment variable format

• /todo - Setup guide for new users

• /justtest - Get test API key (SoM/Converge only)

and more, and the project is now ready for production.

I have solved the bugs in setting the API key functions, added a check API key existence function, and a shorturls existing function in the core api to make the process of validation better. I also created the shorturls functions, getting, creating, and deleting, and I will work on completing them in the coming hours.
- Added shorturl.services.js to handle user interactions for creating, viewing, updating, and deleting short URLs.

What I have done, too:
- Integrated API utility functions for short URL operations in shorturl.js.
- Created api.utils.js for Axios instance configuration.
- Developed apikey.js to check API key existence.
- Enhanced crypto.utils.js for better encryption key validation.
- Added domain preference management for users.

In this devlog, I have completed the functionality of the API key management. Now, the users could set, update, delete, and view their API keys. I also implemented a contact command. I also created the bot page and the contact form page on the main website, mainly to manage the contact if there is any problems are found by the users in the bot, and it could be used by the main site users. I also make the /start command create a user in the database, and /apikey show an inline keyboard where each button creates a callback to handle functions. The set and update API keys function only updates the API key of the user without affecting the other information.

This time, I have understood a lot of concepts, and things have become clear. Now I have created a MongoDB database with a mongoose schema. Created the crypto functions to encrypt and decrypt. I have also understood a core concept in bot development, which is the difference between polling and webhooks. The polling is a way where the bot asks the service or platform if there is any message it should answer. This process is repeated every period of time and doesn't require a running server, only a running script. The webhook is another technique where the platform, in my case Telegram, sends the message to the bot whenever the users send it. However, that needs a running public server with an address for Telegram to send the messages to. The webhook technique is better for enterprises but harder to set up. At the end, I have set the /apikey command with set and update functions within an inline keyboard that sends a callback for running the functions, currently completing the other functions.

First time creating a Telegram bot. Most of the time is spent on choosing the best library or framework for building the website. I have tried setting up a project with NestJS, but found that things will be more complicated than I need. Since I aim to make it as simple as possible and depend on the API keys from my main service, SaifURLs, and that will avoid me from creating a complete authentication for users, just let them set the API key, and they can work as they want. My service, SaifURLs, already provides API keys for users if needed after they sign up, and then they can get the key from the developer page. Okay, after trying NestJS, I have tried ExpressJS with Telegram main API but wanted more easier tool. Until I found a library called node-telegram-bot-api, it was the simplest way to create the bot, and I am using it now.