Repository navigation
F2.5 A conversation per ANSRVR group #285
Description
Split from #193: the part of F2.5 that 0.5.0 leaves out.
What. Each joined ANSRVR group gets its own conversation in Messages (F2.5 behavior 8). It holds what ANSRVR relays from the group's members, with each original sender, and what this station posted to the group. Posting from that conversation sends ANSRVR's post form (behavior 9). Conversations gain a Group field.
Today (0.5.0). Joining, leaving, posting and keep-alives work from the Bulletins panel. Everything ANSRVR sends back, its notices and any relay, lands in one ANSRVR conversation.
Waits on. APRS.NET recognising a message ANSRVR relays from a group, with the group, the original sender and the text: APRS.NET#272, paused on 2026-10-18. In a live test on APRS-IS, NZ0P-3 joined test groups and NZ0P-10 posted to them; ANSRVR answered "1 Message Sent", but no relay ever reached NZ0P-3. The relay format still needs a capture, perhaps between two stations with different base callsigns.
Spec: docs/features/F2.5-bulletins.md, behaviors 8, 9 and 12 (#284).
Activity
docs(F2.5): the per-group conversation is #285, in 0.6.0
gx1400 commentedon Oct 19, 2026
Off the 0.6.0 milestone (2026-10-19). It depends on APRS-NET/APRS.NET#281 (recognising relayed ANSRVR group messages), which is paused: in live tests ANSRVR never relayed a group message to another member. It gets a milestone again once a relay can be observed.
gx1400 commentedon Oct 27, 2026
The relay format is captured, receive-only, from two real groups (
NEDRandHOTG); the details are on APRS-NET/APRS.NET#281. A relay comes from the original poster, injected by ANSRVR's host (APWW11,qAO,KJ4ERJ-15), with the textN:<GROUP> <text>and no message ID. Built in #442, with recognition as a marked shim until APRS.NET has it.feat(messaging): a conversation per ANSRVR group
feat(messaging): a conversation per ANSRVR group
feat(messaging): a conversation per ANSRVR group