Welcome everyone and special greetings to the developers out there, usually working in the background. Today, we start our “dev diary” regarding the Finnoq protocol, in order to give you all the brief insights on what we are currently working. Although we have planned to do this regularly, our work might not allow us to publish every week. One may remark that writing is probably not a developer’s most enjoyable task, but we will try to keep our community up-dated with our insights. Promise!
After this short introduction to our dev diary, let’s get started with the first topic and our first entry:
Introducing… the Finnoq Telegram Bot!
After the industrial revolution, human beings have witnessed the center stage usurpation of machines. When we think about a robot, we think about a heavy steel body that….
Nope just kidding. This isn’t a thesis paper, and not how we wanna structure the dev diary.
As you may have already noticed, Finnoq is active on a variety of channels, and the community is growing rapidly (especially our Telegram Channel). As few have so far volunteered to actively supervise the channel 24/7, (surprise surprise) we started to implement a bot. In this fashion, we are able to welcome new members as well as offer additional features, such as delivering our integral papers (overview, litepaper, whitepaper) or information that are part of frequently asked questions (FAQs). It makes it even easier to interact and understand the long-term plans of Finnoq.
Visit the Finnoq Telegram Channel and try it out (the link can be found in the pinned message).
Additionally, we at Finnoq create a protocol for decentralized opinion markets. Thus, we also implemented an additional opinion bot so everyone is able to participate in an early stage (even before Alpha is up).
TO SHOW YOU WHATS UNDER THE HOOD AND HOW IT LOOKS:
For the development we used the official Telegram Bot API in combination with Google Apps Script.
We employed a 'webhook' to begin coding. The bot is triggered by receiving messages, which means every time someone interacts with the bot by sending a message, the message along with some more data is sent to the code. The message and data received is used to make decisions based on logic, pushing messages back and saving answers in our databases.
For example, if we employ our bot for quizzes or polls, the answers given from community members will be analysed. As opposed to a ‘getUpdates’-style bot, which can diffuse information without interaction from the end user (with required activation from the developer), ‘webhook’ acts only based on end-user engagement. This is what our blended code looks like:
We hope you enjoyed our first dev diary. We look forward to having many more, discussing what is happening from the dev’s perspective at Finnoq.
If you have any questions, suggestions or comments, our developers will be happy to hear!
Cheers!
