Are you sure, it only watches channels not DM (I think!)
Sure, log above is from primary channel we were speaking.
For some reason bot rearrange our messages backwards in responce to messages command.
When primary channel goes:
msg1
msg2
msg3
Bot in history sends me in DM:
MSG:
msg3
msg2
msg1
> Are you sure, it only watches channels not DM (I think!)
Sure, log above is from primary channel we were speaking.
For some reason bot rearrange our messages backwards in responce to messages command.
When primary channel goes:
msg1
msg2
msg3
Bot in history sends me in DM:
MSG:
msg3
msg2
msg1
<!-- github-comment-id:3382609954 -->
Even more, you can trt way more bigger messages to make it in chunks, it will brake it more.
Oh wait, current implementation just sends me only part of my big message at all)
2025-10-08 20:52:09,266 | INFO | Device:1 Channel:0 Ignoring Message: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ не обязателен. From: ZedIsSttn1
2025-10-08 20:52:27,089 | INFO | Device:1 Channel: 0 Received DM: messages From: ZedIsSttn1
2025-10-08 20:52:27,091 | DEBUG | System: Bot detected Commands:[{'cmd': 'messages', 'index': 0}] From: ZedIsSttn1
2025-10-08 20:52:29,292 | INFO | Device:1 Sending DM: 📨Messages: ZedIsSttn1: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ н... To: ZedIsSttn1
Even more, you can trt way more bigger messages to make it in chunks, it will brake it more.
Oh wait, current implementation just sends me only part of my big message at all)
2025-10-08 20:52:09,266 | INFO | Device:1 Channel:0 Ignoring Message: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ не обязателен. From: ZedIsSttn1
2025-10-08 20:52:27,089 | INFO | Device:1 Channel: 0 Received DM: messages From: ZedIsSttn1
2025-10-08 20:52:27,091 | DEBUG | System: Bot detected Commands:[{'cmd': 'messages', 'index': 0}] From: ZedIsSttn1
2025-10-08 20:52:29,292 | INFO | Device:1 Sending DM: 📨Messages: ZedIsSttn1: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ н... To: ZedIsSttn1
<!-- github-comment-id:3382622479 -->
Well, so the problem1 is a rearranged history strings in a bot DM message in responce of messages command.
And problem2 it just sends only one big message in history for some reason )
Well, so the problem1 is a rearranged history strings in a bot DM message in responce of messages command.
And problem2 it just sends only one big message in history for some reason )
<!-- github-comment-id:3382638726 -->
This is all expected behavior it will chunk if needed.
This isn't like store and foward it's more like, limited voicemail
This is all expected behavior it will chunk if needed.
This isn't like store and foward it's more like, limited voicemail
<!-- github-comment-id:3384027328 -->
Sad but ok, at least it doesn't produced an error.
Chunked messages isn,t a problem, it's order inside one bot message is a problem anyway.
Sad but ok, at least it doesn't produced an error.
Chunked messages isn,t a problem, it's order inside one bot message is a problem anyway.
<!-- github-comment-id:3384094722 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When chat goes:
1
2
3
Bot sends
3
2
1
2025-10-08 19:31:19,529 | INFO | Device:1 Channel:0 Ignoring Message: Как прохождение нынче?) с горок до КФУ кто нить добил? From: greenSky
2025-10-08 19:31:47,099 | INFO | Device:1 Channel:0 Ignoring Message: Сообщение 1. From: ZedIsSttn1
2025-10-08 19:32:01,066 | INFO | Device:1 Channel:0 Ignoring Message: Сообщение 2. Очередность 2. From: ZedIsSttn1
2025-10-08 19:32:11,316 | INFO | Device:1 Channel: 0 Received DM: messages From: ZedIsSttn1
2025-10-08 19:32:11,318 | DEBUG | System: Bot detected Commands:[{'cmd': 'messages', 'index': 0}] From: ZedIsSttn1
2025-10-08 19:32:13,519 | INFO | Device:1 Sending DM: 📨Messages: ZedIsSttn1: Сообщение 2. Очередность 2. ZedIsSttn1: Сообщение 1. greenSky : Как прохождение нынче?) с горок до КФУ кто ни... To: ZedIsSttn1
Are you sure, it only watches channels not DM (I think!)
Sure, log above is from primary channel we were speaking.
For some reason bot rearrange our messages backwards in responce to messages command.
When primary channel goes:
msg1
msg2
msg3
Bot in history sends me in DM:
MSG:
msg3
msg2
msg1
Even more, you can trt way more bigger messages to make it in chunks, it will brake it more.
Oh wait, current implementation just sends me only part of my big message at all)
2025-10-08 20:52:09,266 | INFO | Device:1 Channel:0 Ignoring Message: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ не обязателен. From: ZedIsSttn1
2025-10-08 20:52:27,089 | INFO | Device:1 Channel: 0 Received DM: messages From: ZedIsSttn1
2025-10-08 20:52:27,091 | DEBUG | System: Bot detected Commands:[{'cmd': 'messages', 'index': 0}] From: ZedIsSttn1
2025-10-08 20:52:29,292 | INFO | Device:1 Sending DM: 📨Messages: ZedIsSttn1: Так, это большое тестовое сообщение свыше сотни символов, близко к пределу в 200. Проход 1. Ответ н... To: ZedIsSttn1
Well, so the problem1 is a rearranged history strings in a bot DM message in responce of messages command.
And problem2 it just sends only one big message in history for some reason )
This is all expected behavior it will chunk if needed.
This isn't like store and foward it's more like, limited voicemail
Sad but ok, at least it doesn't produced an error.
Chunked messages isn,t a problem, it's order inside one bot message is a problem anyway.
I can add a reverse sort option?
That would be nice if possible.