Channel replies do _not_ keep the original message's scope, although stated in release notes. #364

Open
opened 2026-10-27 15:50:53 +01:00 by adam · 0 comments
Owner

Describe the bug

release notes for v0.9.14 say

Replies now keep the original message's scope: When you reply to a channel message, the reply is sent using the same region scope the original message was posted under, instead of switching to the channel's current default scope — so your reply reaches the same audience the original post did, even if the channel's scope has changed since. A [Reply: scope] tag (device) or Reply: scope label (WebUI) appears on the message box while this applies, so you can see it before sending.

I tried: Not working (according to the message details of the sent message: The firmware shows that the sent message has the scope of the channel -- explicitly set, or if unset then default scope -- even when the message I had opened from where I did tap "Reply" had a different scope).

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.14

Additional remarks

Seems that you let your LLM agents just adding false statements about stuff they claim they have integrated, whether it is reality or not.
This puts a lot of stress on the users to make quality control.

Regards!

**Describe the bug** [release notes](https://github.com/dabeani/meshcoreterm/releases/tag/v0.9.14) for v0.9.14 say > **Replies now keep the original message's scope:** When you reply to a channel message, the reply is sent using the same region scope the original message was posted under, instead of switching to the channel's current default scope — so your reply reaches the same audience the original post did, even if the channel's scope has changed since. A [Reply: scope] tag (device) or Reply: scope label (WebUI) appears on the message box while this applies, so you can see it before sending. I tried: Not working (according to the message details of the sent message: The firmware shows that the sent message has the scope of the channel -- explicitly set, or if unset then default scope -- even when the message I had opened from where I did tap "Reply" had a different scope). **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.14 **Additional remarks** Seems that you let your LLM agents just adding false statements about stuff they _claim_ they have integrated, whether it is reality or not. This puts a lot of stress on the users to make quality control. Regards! <!-- github-sync-id:5789889887 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#364