MarekZegare4 7a5247d5d4 fix(companion): show the sender's own timestamp for synced/queued messages ...

DM, room and channel history always stamped a message with receipt time
(rtc_clock.getCurrentTime()), even though the sender's real timestamp was
already available (and, for DMs/rooms, already threaded through to
addDMMsg -- just never used for display). Live-received messages hid this
because receipt lags origination by only seconds, but a room-sync replay or
an offline-queued message held by a repeater can arrive long after it was
sent, so a burst of backlog messages all showed as "just now".

storeDMMsg() now prefers msg_ts (falling back to receipt time only when
unknown). addChannelMsg() gained a timestamp parameter, threaded from
onChannelMessageRecv() down through AbstractUITask/UITask, with the same
fallback. The DM dedup check and outgoing-message timestamps are unaffected
(they use msg_ts directly, already correct).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-28 11:00:45 +02:00

..

companion_radio

fix(companion): show the sender's own timestamp for synced/queued messages

2026-06-28 11:00:45 +02:00

kiss_modem

Rename bootComplete() to onBootComplete() for naming consistency

2026-05-25 09:50:28 -04:00

simple_repeater

* version 1.16.0

2026-06-06 21:09:38 +10:00

simple_room_server

* version 1.16.0

2026-06-06 21:09:38 +10:00

simple_secure_chat

refactor(BaseChatMesh): extract onDiscoveredAdvert to keep upstream signature

2026-06-08 20:37:22 +02:00

simple_sensor

* version 1.16.0

2026-06-06 21:09:38 +10:00