mirror of
https://github.com/torlando-tech/pyxis.git
synced 2026-07-17 03:21:57 +00:00
torlando-techandClaude Opus 4.7
2eeb81e42f
Two related bugs in the conversation list: 1. Without GPS/NTP, Utilities::OS::time() returns uptime seconds — way smaller than any real unix-epoch message timestamp. The format_timestamp "diff < 0 → Future" branch then fired on every row. Add a sane-epoch threshold (2024-01-01) below which we render "?" instead, since "Future" is misleading when it just means "we don't know what time it is." 2. Identity::recall_app_data is in-memory only and lost on reboot. The conversation list always re-fell back to truncated hashes on cold start. Wire the three-tier resolution flow: live announce → MessageStore-persisted name → hash. When the live cache hits, write through to the persisted side via MessageStore::set_display_name so future cold boots get the name back immediately. Pulls in microLXMF 5531a59 (MessageStore display-name cache impl). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pyxis
An LXMF and LXST client firmware for T-Deck, built on a highly modified fork of microReticulum
Very much WIP, don't expect stability :)
Features
Reticulum transport over:
- RNode-compatible LoRa
- AutoInterface (local wifi)
- TCP Client
- BLE Interface (barely working if at all)
Other features:
- GPS-synced time
- One really annoying beep when you get a new message (user toggle)
- View the announce stream
- Choose a propagation node (and sync with it) (fixed in v0.2.1)
- Set auto announce timer
- Light up keyboard (user toggle)
Will crash in about 5 minutes of normal use (sorry)I had 5d uptime on v0.2.0 with BLE disabled- Make LXST voice calls (codec2 only, quality sounds horrible coming out the other end in Columba, needs work)
Why "Pyxis"
Pyxis, latin for "compass," is a constellation in the southern sky depicting a mariner's compass. Small but essential, the compass ensures every message finds its destination - even when the path is uncertain.