Does not finish the message. No markup markdown about edgegpt-telegram-bot

[scmanjarrez]

Related #75. I didn't expect Bing answer more than 4k tokens. Do you mind sharing the prompt?

[x4team]

Related #75. I didn't expect Bing answer more than 4k tokens. Do you mind sharing the prompt?

According to the new rules, Bing responds even with 64kb !!!!

I made my bot send the message as a text file, because I couldn't split the message into parts with the markdown markup preserved, since there are big problems with markdown parsing in telegram

[x4team]

my prompt:

Imagine that you are a python senior developer with a lot of experience. I'm a junior and you help me write a telegram bot in python using the aiogram library. Below are the lists of commands, you can use them to determine all the necessary functionality.
All tokens and passwords should be stored in config.json, and the database for each chat user and his personal boards in a common db.json file with python dictionaries.

/start - welcome message with text "Hi! I'm your assistant with tasks. Here is a list of commands you can use"
/addboard "BOT" - add board with name BOT and sections with names: backlog, todo, inprogress, done
/getboards - get all boards name
/deleteboard "BOT" - delete board BOT and all tasks in it board

/selectboard BOT - activate BOT board
/tasks - get all tasks in BOT board
/add  "BOT-1. Hello" - add task to backlog section by default
/del BOT-1 - remove task 1  from backlog or todo or inprogress or done
/backlog BOT-1 - move task BOT-1 to backlog section
/todo BOT-1  - move task BOT-1 to todo section
/inprogress BOT-1 - move task BOT-1 to inprogress section
/done BOT-1 - move task BOT-1 to done
Also use emojis in all reply messages to users on command

[x4team]

UPDATE: 64k for questions, and max 8k for answers (for Russian)

[scmanjarrez]

Yeah... That's my concern, how to handle the markdown in long messages. But your approach may be the only way. I'll think about it

[Eikosa]

Yeah... That's my concern, how to handle the markdown in long messages. But your approach may be the only way. I'll think about it

In long messages containing code, it can send it as a document, otherwise it can split the message.