I seem to be only getting 113 characters for messages #187

Closed
opened 2026-10-27 15:43:07 +01:00 by adam · 9 comments
Owner

Describe the bug
i seem to only be getting 113 characters to respond to messages? is this normal or is it a bug!

usually its 127 ??

Image

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using
0.9.12

**Describe the bug** i seem to only be getting 113 characters to respond to messages? is this normal or is it a bug! usually its 127 ?? <img width="3711" height="2775" alt="Image" src="https://github.com/user-attachments/assets/596e0ed3-b0be-43a0-afb9-fe9838530127" /> **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** 0.9.12 <!-- github-sync-id:4298215457 -->
adam closed this issue 2026-10-27 15:43:07 +01:00
Author
Owner

Which bytes you are using? 1/2/3?

Which bytes you are using? 1/2/3? <!-- github-comment-id:4284572494 -->
Author
Owner

using 1 byte

Image
using 1 byte <img width="3950" height="2962" alt="Image" src="https://github.com/user-attachments/assets/3b1da9ec-5766-47cf-abb7-f95f0767b706" /> <!-- github-comment-id:4284608982 -->
Author
Owner

I have 116 max characters in a public channel in version 0.9.12. Usually the max. also depends on username length. My username is 7 characters long. I don't remember what was the limit in v0.9.11.

In private message I have 125 max. characters.

Path hash length: 1 byte.

I have 116 max characters in a public channel in version 0.9.12. Usually the max. also depends on username length. My username is 7 characters long. I don't remember what was the limit in v0.9.11. In private message I have 125 max. characters. Path hash length: 1 byte. <!-- github-comment-id:4291597546 -->
Author
Owner

fix implemented in v0.9.12.1

  • Messages/WebUI: derive DM and channel composer counters from MeshCore's 160-byte message limit, the current node-name prefix, and the local mirrored-message buffers so device UI and WebUI match the real send/storage cap (#187).
fix implemented in v0.9.12.1 - Messages/WebUI: derive DM and channel composer counters from MeshCore's 160-byte message limit, the current node-name prefix, and the local mirrored-message buffers so device UI and WebUI match the real send/storage cap (#187). <!-- github-comment-id:4307556033 -->
Author
Owner

Was this in the meantime fixed for you, @BUDDHADECK2?
If so, please close, if not, report here that still not fixed because comment says that it should have been fixed.

I see that I can now type 150 characters in a channel or private message.

EDIT: I have confirmed that, at least over only a few hops, the 150 characters also were transmitted on a public channel. So maybe this issue can now be closed, @dabeani? But private channel confirmation still outstanding.

Regards!

Was this in the meantime fixed for you, @BUDDHADECK2? If so, please close, if not, report here that still not fixed because [comment says that it should have been fixed](#issuecomment-4307556033). I see that I can now type 150 characters in a channel or private message. *EDIT: I have confirmed that, at least over only a few hops, the 150 characters also were transmitted on a public channel. So maybe this issue can now be closed, @dabeani? But private channel confirmation still outstanding.* Regards! <!-- github-comment-id:4606097834 -->
Author
Owner

Was this in the meantime fixed for you, @BUDDHADECK2?
If so, please close, if not, report here that still not fixed because comment says that it should have been fixed.

I see that I can now type 150 characters in a channel or private message.

Still need to test how much actually gets transmitted.

Regards!

How many more times do I have to say I no longer have mc term installed ! If you need any of my posts removing speak to the admin ie the developer who owns this page !

> Was this in the meantime fixed for you, @BUDDHADECK2? > If so, please close, if not, report here that still not fixed because [comment says that it should have been fixed](#issuecomment-4307556033). > > I see that I can now type 150 characters in a channel or private message. > > Still need to test how much actually gets transmitted. > > Regards! How many more times do I have to say I no longer have mc term installed ! If you need any of my posts removing speak to the admin ie the developer who owns this page ! <!-- github-comment-id:4606139756 -->
Author
Owner

Was this in the meantime fixed for you, @BUDDHADECK2?
If so, please close, if not, report here that still not fixed because comment says that it should have been fixed.
I see that I can now type 150 characters in a channel or private message.
Still need to test how much actually gets transmitted.
Regards!

How many more times do I have to say I no longer have mc term installed ! If you need any of my posts removing speak to the admin ie the developer who owns this page !

You wrote that you want to check back here later, so I could assume that eventually, when you do that, and there is a new release, you would test it at some point in the future.

And, actually, you did say that you stop using MC Term, and later you wrote about another issue, so that also in my eyes did erode the statement that you completely stopped using it.

Issues are nothing where a fast reaction is needed (usually, if it is not a critical security bug, but in MeshCore we should not assume any security anyway).

I do not need your post removed, I just try to help maintain which issues are still to be kept open and which are resolved and can be closed (not removed).

You appear pretty pissed-off to me.

Regards!

> > Was this in the meantime fixed for you, [@BUDDHADECK2](https://github.com/BUDDHADECK2)? > > If so, please close, if not, report here that still not fixed because [comment says that it should have been fixed](#issuecomment-4307556033). > > I see that I can now type 150 characters in a channel or private message. > > Still need to test how much actually gets transmitted. > > Regards! > > *How many more times do I have to say I no longer have mc term installed ! If you need any of my posts removing speak to the admin ie the developer who owns this page !* You wrote that you want to check back here later, so I could assume that eventually, _when_ you do that, and there is a new release, you would test it at some point in the future. And, actually, you did say that you stop using MC Term, and later you wrote about another issue, so that also in my eyes did erode the statement that you completely stopped using it. Issues are nothing where a fast reaction is needed (usually, if it is not a critical security bug, but in MeshCore we should not assume any security anyway). I do not need your post removed, I just try to help maintain which issues are still to be kept open and which are resolved and can be closed (not removed). You appear pretty pissed-off to me. Regards! <!-- github-comment-id:4606162366 -->
Author
Owner

I said I may come back to using mc term and maybe I won't ! If you need to fill your life with admin tasks maybe ask Bernhard for admin rights ? Then you can edit delete and change posts accordingly ! I have much respect for Bernhard and his push to provide the community with a fantastic bit of software at this moment it's not installed on my tdeck ! Feel free requesting all my posts closed ! And finally no idea what gives you the impression I'm anything but happy ! Unless you're a trained physiologist! Thank you 👋👋

I said I may come back to using mc term and maybe I won't ! If you need to fill your life with admin tasks maybe ask Bernhard for admin rights ? Then you can edit delete and change posts accordingly ! I have much respect for Bernhard and his push to provide the community with a fantastic bit of software at this moment it's not installed on my tdeck ! Feel free requesting all my posts closed ! And finally no idea what gives you the impression I'm anything but happy ! Unless you're a trained physiologist! Thank you 👋👋 <!-- github-comment-id:4606223851 -->
Author
Owner

calm down guys, thank you for beeing with me even when mcterm is right now not in use. I am happy to get your support and i understand how much work this consumes. Its not easy for me to test every bit and byte - as you know, so i need people like you and others to get better. Time is limited but i keep going with it and try my best to optimize and fulfill enhancements/bugs.

i will close it now, but if someone figure out an issue with this, feel free to open a new issue and (would be nice to) link it together to keep history.

Thank you!! 💛

calm down guys, thank you for beeing with me even when mcterm is right now not in use. I am happy to get your support and i understand how much work this consumes. Its not easy for me to test every bit and byte - as you know, so i need people like you and others to get better. Time is limited but i keep going with it and try my best to optimize and fulfill enhancements/bugs. i will close it now, but if someone figure out an issue with this, feel free to open a new issue and (would be nice to) link it together to keep history. Thank you!! 💛 <!-- github-comment-id:4607594855 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#187