osdc / bots Goto Github PK

Describe the bug
Bot is not sending the greeeting message whenever a new user joins the server

Expected behavior
Bot should greet the person with the greeting message...

New feature

Leverage any of the pastebin api's available out there and integrate it with our bot.

Why to we need it?

To paste the logs sent by any member for an encountered issue for convenience of other members in the chat who want to help them out.

Directions/Approach

Using the API as mentioned in http://ix.io/ and https://paste.rs/ ( any one of em or any other better alternative if available )

New feature

Discord uses some really cool welcome messages, we would love to have them in our bot too.

Directions/Approach

Just tweak the function where we send the welcome message and randomly select a string of various hard-coded welcome messages.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

Bot crashes when the command '/nextmeetup' is given. No subsequent commands given to the bot produce a result unless the bot is restarted.

Expected to give details of the next meetup if there is a meetup scheduled, and print 'No meetup scheduled' if meetup is not scheduled.

OS: Manjaro, Linux 5.8

New Feature/Enhancement

As of now, we only add the Date and the Title of our OSDC meetups. A new field of Venue needs to be added.

Directions

We can change the data schema here - https://github.com/osdc/bots/blob/master/telegram-bot/meetup.go#L33 and further changes need to be made in this /addmeetups function - https://github.com/osdc/bots/blob/master/telegram-bot/meetup.go#L57

First Time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

/cc @daemon1024

Currently the bot doesn't validate in /nextmeetup command. The bot should check if the current time is past the scheduled events time, it should respond with no meetup scheduled.

Directions/Approach

The comparison should happen after we have fetched from the database and before we start formatting the final message.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

We currently use else.. if chains for various commands implemented in the bot. It is fine for the very few commands we have but as we scale to add more commands and more features it will cause a lot of unorganized code and make it harder to debug. So we should implement a handler for that.

The discord.js guide has an amazing explanation of how to implement it.
https://discordjs.guide/command-handling/

If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

New feature

The bot sends a " I don't know that command " message when it encounters an unknown command. The bot should delete it's message after a few seconds when the user has perceived it.

Hi, If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

Describe the bug
Whenever someone message with !help or !xkcd command both the specific message and the default message are send by bot.

Expected behavior
The bot should only send the specific message for that particular command and not the default one.

Screenshots

New feature

We already have a really nice welcome message. I wanted to add our social links as well as the code of conduct to the message itself so as the new folks get more context about what we are in the welcome message itself.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

Changes to be made

Updating the above mentioned repository link with https://github.com/osdc/bots

Hi, If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue. and follow Contributing to the bot 🔥✨

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

Changes to be made

In contributing.md - > Setting up the bot -> step 1 -> the link to Botfather is broken.
this is the correct link.

Changes to be made

The bot should respond with something like " Please provide the name of the note " when no arguements are provided with the command /fetchnote

Hi, If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

New feature

Currently the discord bot doesn't respond to unknown triggers, but it should let the user know about the command being invalid.

Directions/Approach

https://github.com/osdc/bots/blob/6adc0b2cdd6b3258dfc32376272901e3cb5c1585/discord-bot/bot.js Add an else case. May need to convert the existing if statements to else if.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow README to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

New feature

Implementation of reminder for OSDC Meetups whose details are updated by the admin through the /addmeetups command.

Directions/Approach

Open to discussion.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

ESLint performs automated scans of your JavaScript files for common syntax and style errors.

https://eslint.org/docs/user-guide/getting-started

Prettier scans your files for style issues and automatically reformats your code to ensure consistent rules are being followed for indentation, spacing, semicolons, single quotes vs double quotes, etc.

https://prettier.io/docs/en/install.html

These will help us streamline our codebase as well as the review process.

Hi, If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️.

Changes to be made

• OSDC has its Discord server at https://discord.gg/2sv322nY9v .
• It needs to be added here likewise as for other platforms - https://github.com/osdc/bots/blob/master/telegram-bot/main.go#L187-L188

Hi, If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️.

Describe the bug
When /save <Title> <Content> is used if the content doesnt have any link in markdown format i.e [link title](link) the bot crashes due to index out of range

Expected behavior

The bot should avoid parsing markdown links if the matches are zero

Additional context

Logs : https://del.dog/asadingapp

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

Describe the bug
The bot reminds about the upcoming meetup 2 hours before the scheduled time. But this functionality seems to be working randomly.

Expected behavior
It should be streamlined and should work as designed.

System Description
Operating System : Heroku

Additional context
Works fine whenever debugged locally till now, so needs deeper debugging.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

The repository should have a more generic README and CONTRIBUTING Guide as it hosts various bots of our community.

The current README and CONTRIBUTING Guide are focused on the telegram-bot so it should be moved into telegram-bot folder.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

New feature

Currently, the /addmeetups and /getmeetups commands use local json files to store and retrieve data. Using a database such as MongoDB will easen up the process and will also keep data synchronized.

Directions/Approach

I guess most of the changes need to be made in meetups.go file in the addmeetups and getmeetups functions. We can use this mongo go driver - https://www.mongodb.com/blog/post/mongodb-go-driver-tutorial

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

Context

Sometimes community members send messages with large word count, which can potentially interrupt an ongoing conversation and hamper reading useful messages. A enhancement in bot to handle this potential spam can solve this.

Directions/Approach

Some of the approaches can be

• Forwarding the message to OT Group and delete from main group. (Suggested by Suraj Ajay)
• Paste the content on pastebin ( #30 might make this easier )

This needs to be implemented with exception to messages from OSDC Core-Team

New feature

Directions/Approach

• https://blog.alexellis.io/golang-writing-unit-tests/
• https://gobyexample.com/testing

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

New feature

Say, if the user delete's their message which called the bot to do some function, then the bot will also delete it's own message.

Directions/Approach

We'll put a condition, that if the user delete's their message, we check for the bot's MessageID for the text it displayed for the user , and then delete it.

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

First-time Contributors

If it is the first time that you contribute to the bot, follow these steps:

1. You need to have git & golang available on your machine.
   • To install Git - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
   • To setup golang, follow the doc here - https://golang.org/doc/install
2. Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue.
3. Ping Botfather on Telegram and make your instance of OSDC-Bot bot by selecting /newbot from the options it provides.
4. Copy the TELEGRAM_TOKEN provided by Botfather.
5. Fork this repo.
6. Run git clone https://github.com/<YOUR_USERNAME>/bots.git && cd bots/telegram-bot
7. If you have installed golang, run go build .
8. Wait ⏳
9. Run export TELEGRAM_TOKEN=<botfather_token>
10. Now, run ./telegram-bot. The bot would be running at the user handle provided by you.
11. Make changes according to the issue. Test the working of the changes.
12. Commit the changes and then run git push origin master and then open a PR! 🎉

Description

Currently the meetup time and reminder schedules are stored in Local timezone of the host machine.
This creates issues when the bot is deployed on some cloud platform because the Local time for the host machine may be different.

Changes to be made

In meetup.go, replace instances where Local time is used, to use Indian time instead.

One such instance:-

This might be helpful:- https://golang.org/pkg/time/#LoadLocation

First time contributors

Hi, If it is the first time that you contribute to the bot:

Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., follow Contributing to the bot 🔥✨ and feel free to ask anything related to this issue ✌️

Describe the bug

There are lots of edge cases and instances where bot crashes due to some unexpected syntax or error.

Example : Unexpected syntax in /addmeetup

Expected behavior

The bot shouldn't crash instead it should respond with something like " Unexpected behaviour, please try again "

** Additional Context **

We are using log.Fatal / log.Fatalln when an error occurs. This causes the program to call os.exit(1) which is an undesirable behaviour.

Instead we should log.Print the errors as well as a bot response for the same.