Part of Message is rendered where username should show. #248

New Issue

2026-10-27T15:45:47+01:00

adam commented

2026-10-27 15:45:47 +01:00

Describe the bug

This seems to be the inverse behaviour of #131:

I have a case, where the actual message is rendered inside the field where the sending username should be shown.

In that case: A room server message.

It shows:
<Moin, na spitze... >-) -- whereas the actual message was Moin, na spitze... :-) and send by the user Wahni @home 🤖 -- the username should have appeared inside the <>.
So, the correct display shouls have been:
<Wahni @home ?> Moin, na spitze... :-)

Photographs:

How it is in MC Term:

How it should be correct (from official MeshCore app):

Details view of the problematic room server message in MC Term:

Details view of the same message in official MeshCore app:

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.12

Regards!

**Describe the bug** This seems to be the inverse behaviour of #131: I have a case, where the actual message is rendered inside the field where the sending username should be shown. In that case: A room server message. It shows: `<Moin, na spitze... >-)` -- whereas the actual message was `Moin, na spitze... :-)` and send by the user `Wahni @home 🤖` -- the username should have appeared inside the `<>`. So, the correct display shouls have been: `<Wahni @home ?> Moin, na spitze... :-)` Photographs: --- How it is in MC Term: <img width="775" height="571" alt="Image" src="https://github.com/user-attachments/assets/bf906229-d389-4b61-b1a1-ebb8e368c80c" /> How it should be correct (from [official MeshCore app](https://files.liamcottle.net/MeshCore/)): <img width="670" height="578" alt="Image" src="https://github.com/user-attachments/assets/ba07b160-7d32-467c-8fdb-b4067a3b9420" /> Details view of the problematic room server message in MC Term: <img width="712" height="533" alt="Image" src="https://github.com/user-attachments/assets/e508050e-f239-46a3-b69b-d44834999533" /> Details view of the same message in [official MeshCore app](https://files.liamcottle.net/MeshCore/): <img width="607" height="715" alt="Image" src="https://github.com/user-attachments/assets/e9577dee-3771-4b5c-bffc-71387b7a55ab" /> --- **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.12 Regards!

adam closed this issue

2026-10-27 15:45:47 +01:00

adam commented

2026-10-27 15:45:48 +01:00

###Fixed (v0.9.12.1)

Room server messages: fix the message body being rendered in the sender-name field when the room server uses signed-plain delivery (i.e., the actual sender was resolved from the signing key prefix). (#248).

###Fixed (v0.9.12.1) - Room server messages: fix the message body being rendered in the sender-name field when the room server uses signed-plain delivery (i.e., the actual sender was resolved from the signing key prefix). (#248).

adam commented

2026-10-27 15:45:49 +01:00

Closing for now and would re-open if it would re-appear.

Closing for now and would re-open if it would re-appear.

adam commented

2026-10-27 15:45:49 +01:00

I’d like to add a request. Specifically, why isn’t it possible for the system to send two separate messages in succession if you write more than 150 characters?

I’d like to add a request. Specifically, why isn’t it possible for the system to send two separate messages in succession if you write more than 150 characters?

adam commented

2026-10-27 15:45:50 +01:00

I’d like to add a request. Specifically, why isn’t it possible for the system to send two separate messages in succession if you write more than 150 characters?

Do you want to open a sepearate issue with a "[Feature wish]" for this, @HB3YDM?

(And from my experience, reliability of messages making it through is not so good. So if messages are split up, indicators should be added to the individual messages, denoting which one in a series of many it is.

Could be done automagically!, e.g.:

Prefix [2/5] if it is the second of 5 messages Calculation of total number be done automatically, prefix added automatically, and everything set up that the total length (prefix + text) is less than 150 or 127 or whatever is the limit characters.*

Nice idea :-).)

> *I’d like to add a request. Specifically, why isn’t it possible for the system to send two separate messages in succession if you write more than 150 characters?* Do you want to [open a sepearate issue](https://github.com/dabeani/meshcoreterm/issues/new) with a "[Feature wish]" for this, @HB3YDM? *(And from my experience, reliability of messages making it through is not so good. So if messages are split up, indicators should be added to the individual messages, denoting which one in a series of many it is.* *Could be done automagically!, e.g.:* *Prefix `[2/5]` if it is the second of 5 messages* Calculation of total number be done automatically, prefix added automatically, and everything set up that the total length (prefix + text) is less than 150 or 127 or whatever is the limit characters.* *Nice idea :-).)*

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#248