n0th1ng-else / voice-to-text-bot Goto Github PK

For some reason, there are duplicates in development DB, so it seems that we need to handle such cases and avoid duplications as much as possible

enable donations via robokassa

Since I am not a designer I am having troubles to get an awesome bot picture. Looking for one, any suggestions are welcome!

Right now stat contains last user name who applied a voice message, should be group name for groups

retry if telegram threw a error during the init

Right now logs do now show what happened with the replica when external system tries to shut it down. We want to try to track such events

• add exceptions
• add thdead id for events

tag:app.8cf913a16282f43bfdad831afe02f5adf638a0d0
logtype:json
http:
clientHost:54.74.88.42
contentType:application/json
json:
id:telegram-bot
level:error
message:Unable to recognize the file
metadata-0-code:13
metadata-0-details:Received RST_STREAM with code 2 (Internal server error)
metadata-0-note:Exception occurred in retry method that was not classified as transient
prefix:no
timestamp:2020-08-12T17:24:01.039Z

seems that we have a lifecycle event that fires on pod restart. We want to implement a triggert for that event

• audio/mpeg
• audio/mp3
• audio/m4a
• audio/x-m4a
• audio/mpeg3
• audio/x-vorbis+ogg
• audio/x-aac

We want to run a daemon on destroy to pick up telegram messages

server
level:error
message:Unknown route /bot/message/c4b247a3e37e43eb7e140a2576138926
timestamp:2020-07-01T19:49:03.595Z

Sounds like we want to handle everything /bot/message/:id and then show some error/warn if it is not our entrypoint

Use google analytics to collect the insights.

in groups users use commands like /support@AudioMessBot - we should support it

https://rowanmanning.com/posts/node-cluster-and-express/

since the process is all set, it is interesting if we can implement the same feature in whatsapp messager

• Groups vs Direct messages
• Groups usage vs Direct messages (in total files recognized)
• Installs vs Usages redesign - show percentage
• Installs per day cumulative
• Installs per day average (add on the existing graph)

Add language command for bot so it will suggest switching between RU and EN

Currently, Google recognition engine does not support 44100, so need to get some research

Right now it is unclear what kind of action user called to analyze particular issue in logs. We need to enrich logs with more data. WHat kind of action do they call, was it successful or not etc

d:telegram-bot
level:error
message:Unable to get the lang
timestamp:2020-06-16T09:28:33.200Z
0:
code:100
message:XMLHttpRequest failed: {"UNSENT":0,"OPENED":1,"HEADERS_RECEIVED":2,"LOADING":3,"DONE":4,"readyState":4,"responseText":"","responseXML":"","status":503,"statusText":null,"withCredentials":false}

Cover DB cache by tests and turn it on on the production env

telegram api supports setMyCommands

thing. gonna use it

• detect how many chars is supported (the idea is 4096)
• Handle sending long messages into multiple TG messages (maybe something like this https://www.stefanjudis.com/today-i-learned/how-to-split-javascript-strings-with-intl-segmenter/)

{
  "@timestamp": "2023-01-02T15:27:39.766Z",
  "severity": "error",
  "message": "ETELEGRAM Request failed with status code 400",
  "level": "error",
  "title": "Unable to recognize the file",
  "id": "telegram-bot",
  "prefix": "thread-1",
  "appVersion": "app.0f1f995f3fb5622ec474a956c1261c5b111369ce",
  "code": 400,
  "response": {
    "ok": false,
    "error_code": 400,
    "description": "Bad Request: message is too long"
  },
  "url": "/bot/sendMessage",
  "stack": "Error: ETELEGRAM Request failed with status code 400\n    at /usr/src/app/dist/src/telegram/api/index.js:127:19\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\nAxiosError: Request failed with status code 400\n    at settle (/usr/src/app/node_modules/axios/dist/node/axios.cjs:1855:12)\n    at IncomingMessage.handleStreamEnd (/usr/src/app/node_modules/axios/dist/node/axios.cjs:2704:11)\n    at IncomingMessage.emit (node:events:539:35)\n    at IncomingMessage.emit (node:domain:475:12)\n    at endReadableNT (node:internal/streams/readable:1345:12)\n    at processTicksAndRejections (node:internal/process/task_queues:83:21)",
  "@timestamp_received": "2023-01-02T15:27:41.101Z",
  "logsene_orig_type": "application-logs"
}

make sure we did not use the same twice

use https://github.com/conventional-changelog/standard-version

https://medium.com/@jsilvax/automate-semantic-versioning-with-conventional-commits-d76a9f45f2fa

I can see duplications happen to be in production DB and service resolves them. But I dont know the difference between this or that duplicated record. We need to put more details into logs

So it will be more secured and less smelling
https://sonarcloud.io/pricing

Currently, the bot is disabled for groups. So it might be a worthy case to have it in there. need some research

cache last 50-100 get requests into DB

add badges (sonar, version, usages)

make table responsive

level:error
message:[Id] [ChatId] Unable to recognize the file AwACAgIAAxkBAAIxXF8FxNuSKWTDCsW3Hv5CxnDXq70fAAIoBwACR30wSBrbPQABj2tXZxoE
metadata-0-code:ETELEGRAM
timestamp:2020-07-08T13:07:06.488Z
metadata-0-response:{ headers: { date: "Wed, 08 Jul 2020 13:07:05 GMT", access-control-allow-origin: "*", server: "nginx/1.16.1", content-length: "84", content-type: "application/json", connection: "keep-alive", strict-transport-security: "max-age=31536000; includeSubDomains; preload", access-control-expose-headers: "Content-Length,Content-Type,Date,Server,Connection" }, request: { headers: { content-length: 3034, content-type: "application/x-www-form-urlencoded" }, method: "POST", uri: { path: "/:/sendMessage", protocol: "https:", hostname: "api.telegram.org", port: 443, host: "api.telegram.org", href: "https://api.telegram.org/sendMessage", slashes: true, pathname: "/:/sendMessage" } }, body: { description: "Forbidden: bot was blocked by the user", error_code: 403, ok: false }, statusCode: 403 }

url tag is not supported, so we want to make it plain string

node-telegram-bot-api seems to be packed with features. It is more than enough for the bot. Gonna write own telegram api client that will implement only features bot need

not sure if this is the case