From 211be6081d91ac16390cc3bea360cded19560af0 Mon Sep 17 00:00:00 2001 From: Marc Froehlich Date: Fri, 28 Aug 2026 22:08:31 +0200 Subject: [PATCH] manual: described dual chat --- docs/PROJECT_CONTEXT.md | 10 ++++-- github_docs/de-Benutzeroberflaeche.md | 4 +-- github_docs/de-Funktionen.md | 8 ++--- github_docs/de-Konfiguration.md | 11 +++--- github_docs/en-Configuration.md | 11 +++--- github_docs/en-Features.md | 8 ++--- github_docs/en-User-Interface.md | 4 +-- website/src/features/dual-chat.md | 48 ++++++++++++++------------ website/src/features/macros.md | 2 +- website/src/features/qso-monitoring.md | 6 ++-- 10 files changed, 62 insertions(+), 50 deletions(-) diff --git a/docs/PROJECT_CONTEXT.md b/docs/PROJECT_CONTEXT.md index d8eb3bf0..6cf048f5 100644 --- a/docs/PROJECT_CONTEXT.md +++ b/docs/PROJECT_CONTEXT.md @@ -1,6 +1,6 @@ # KST4Contest Project Context -Last reviewed: 2026-08-27 +Last reviewed: 2026-08-28 This file is the durable technical project context for KST4Contest. It is not a user manual and not a replacement for the changelog. Current code, tests and authoritative external specifications remain the source of truth when this document is stale or ambiguous. @@ -65,10 +65,16 @@ Known integration areas include: CR/LF framing, XML framing, ports/transports, callsign normalization and frequency formatting are protocol behaviour and must not be changed as incidental cleanup. +### ON4KST session and authentication + +- One KST4Contest connection uses one authenticated ON4KST TCP session with one local login callsign, one password and one locator. +- The primary category is part of the initial login. A distinct second category is added to the same session through ON4KST Single Sign-on; it must not create a second TCP connection or local login. +- The local visible chat name, message context, QRG and beacon configuration remain category-specific. + ### ON4KST session liveness - After 90 seconds without inbound data, the application keeps the established empty CRLF heartbeat. -- At about 180 seconds of inbound idle time, the TCP session sends one `RDXQ|
|` probe. The probe state belongs to the session, so a two-category login still sends only one probe per idle phase. +- At about 180 seconds of inbound idle time, the TCP session sends one `RDXQ|
|` probe. The probe state belongs to the session, so a two-category session still sends only one probe per idle phase. - Any subsequent inbound server frame confirms the probe. `DXQ` is accepted as the expected internal response and is not published as chat content. - If no inbound frame arrives by about 210 seconds, the existing reconnect flow remains responsible for replacing the session. - Probe diagnostics contain the session id, main category, opcode and timing only. They must not include credentials, complete server frames or normal chat messages. diff --git a/github_docs/de-Benutzeroberflaeche.md b/github_docs/de-Benutzeroberflaeche.md index 8aeaaf1b..28431a85 100644 --- a/github_docs/de-Benutzeroberflaeche.md +++ b/github_docs/de-Benutzeroberflaeche.md @@ -4,7 +4,7 @@ ## Verbinden mit dem Chat -Vor dem ersten Verbindungsaufbau müssen im Einstellungsfenster mindestens Rufzeichen, Passwort, Locator und primäre Chat-Kategorie konfiguriert werden. Soll zusätzlich eine zweite Kategorie verwendet werden, muss auch deren Login aktiviert und vollständig eingerichtet sein. +Vor dem ersten Verbindungsaufbau müssen im Einstellungsfenster ein lokales Login-Rufzeichen, Passwort, Locator und die primäre Chat-Kategorie konfiguriert werden. Soll zusätzlich eine zweite Kategorie verwendet werden, wird sie dort aktiviert und ausgewählt. KST4Contest meldet sich einmal an und ergänzt die zweite Kategorie per Single Sign-on innerhalb derselben TCP-Sitzung. Die Verbindung kann auf zwei Wegen aufgebaut werden: @@ -54,7 +54,7 @@ Beide Hinweise blinken ungefähr zwölf Sekunden und verschwinden anschließend ### PM-Fenster (oben links) -Das PM-Fenster zeigt die an die eigenen Chat-Logins gerichteten Privatnachrichten und die zugehörigen ausgehenden Antworten. +Das PM-Fenster zeigt die an die eigenen sichtbaren Chat-Namen gerichteten Privatnachrichten und die zugehörigen ausgehenden Antworten. Nicht selbst gesendete Nachrichten erscheinen dort zusätzlich, wenn ihr Text ohne Beachtung der Groß- und Kleinschreibung das konfigurierte eigene Login-Rufzeichen enthält. Das gilt für öffentliche Nachrichten an `ALL` ebenso wie für gerichtete Nachrichten zwischen anderen Chatteilnehmern. Gerade im zweiten Fall lässt sich dieses PM-Catching flapsig als **„Lästererkennung“** bezeichnen. diff --git a/github_docs/de-Funktionen.md b/github_docs/de-Funktionen.md index d5f25216..87916d71 100644 --- a/github_docs/de-Funktionen.md +++ b/github_docs/de-Funktionen.md @@ -308,7 +308,7 @@ Konfiguration, erkannte QRG-Anfragen und genaue Kategorienzuordnung: [Konfigurat ## Multi-Channel-Login (ab v1.26) -Gleichzeitiger Login in **zwei Chat-Kategorien** (z. B. 144 MHz und 432 MHz). Beide Chats werden parallel überwacht. +KST4Contest meldet sich mit einem lokalen Rufzeichen, Passwort und Locator einmal bei ON4KST an. Eine zweite Chat-Kategorie (z. B. 144 MHz und 432 MHz) wird per Single Sign-on innerhalb derselben TCP-Sitzung ergänzt. Beide Kategorien werden parallel überwacht; der eigene sichtbare Chat-Name, Nachrichtenkontext, QRG und Beacon bleiben je Kategorie getrennt. --- @@ -322,7 +322,7 @@ Die grüne Altersskala der Privatnachrichten bleibt in beiden Darstellungen erha ## Opposite Station Multi-Callsign Login-Tagging (ab v1.26) -Unterstützung für Stationen, die mit mehreren Rufzeichen gleichzeitig im Chat aktiv sind (z. B. Expedition-Setups). +Unterstützung für Gegenstationen, die mit mehreren vollständigen Rufzeichen gleichzeitig im Chat aktiv sind (z. B. Expedition-Setups). Vollständiges Rufzeichen und Chat-Kategorie bleiben getrennte Teilnehmeridentitäten; Worked-, Band- und Prioritätsdaten werden über das Basisrufzeichen gemeinsam ausgewertet. --- @@ -438,7 +438,7 @@ Sniffed: (DN9APW-70 > 9A0BB-23) pse sked 19:30 Das ist ein wichtiger Unterschied. Das Monitoring fasst die Varianten zusammen, damit keine Nachricht übersehen wird. Das Nachrichtenrouting fasst sie nicht zusammen, weil andernfalls nicht mehr eindeutig wäre, welcher Login tatsächlich angesprochen wurde. -Das Basisrufzeichen wird außerdem unabhängig von der Chat-Kategorie ausgewertet. Ist KST4Contest gleichzeitig mit zwei Kategorien verbunden, gilt derselbe Monitoring-Eintrag für beide Nachrichtenströme. Die Kategorie der einzelnen Nachricht bleibt dabei erhalten. +Das Basisrufzeichen wird außerdem unabhängig von der Chat-Kategorie ausgewertet. Sind in derselben ON4KST-Sitzung zwei Kategorien aktiv, gilt derselbe Monitoring-Eintrag für beide Nachrichtenströme. Die Kategorie der einzelnen Nachricht bleibt dabei erhalten. Erfasst werden: @@ -703,7 +703,7 @@ Die Timeline ist eine Vorschau. AirScout-Daten können sich ändern, und ein ein KST4Contest kann wiederkehrende CQ-Nachrichten in den öffentlichen Chat senden. Der Beacon ist für längeres CQ-Rufen auf einer festen Frequenz gedacht: Die eigene QRG wird regelmäßig veröffentlicht, ohne dass derselbe Text von Hand wiederholt werden muss. -Beide Chat-Kategorien verwenden ein gemeinsames Intervall, besitzen aber jeweils einen eigenen Aktivierungsschalter und Nachrichtentext. Der zweite Beacon wird nur gesendet, wenn auch der zweite Chat aktiviert und verbunden ist. +Beide Chat-Kategorien verwenden ein gemeinsames Intervall, besitzen aber jeweils einen eigenen Aktivierungsschalter und Nachrichtentext. Der zweite Beacon wird nur gesendet, wenn die zweite Kategorie in derselben ON4KST-Sitzung aktiviert und vollständig synchronisiert ist. Globale Variablen wie `MYQRG`, `SECONDQRG`, `MYLOCATOR` oder `MYQTF` werden unmittelbar vor jeder Aussendung neu aufgelöst. Eine zwischenzeitlich vom Logprogramm aktualisierte QRG kann dadurch bereits im nächsten Beacon erscheinen. diff --git a/github_docs/de-Konfiguration.md b/github_docs/de-Konfiguration.md index 8ddaae71..1a5c629c 100644 --- a/github_docs/de-Konfiguration.md +++ b/github_docs/de-Konfiguration.md @@ -14,14 +14,15 @@ Nach dem ersten Start öffnet sich das **Einstellungsfenster** – dieses ist de ### Login und Chat-Kategorien -Hier werden die Zugangsdaten für den ON4KST-Chat eingetragen (Rufzeichen und Passwort). -Zudem wird die **primäre Chat-Kategorie** (z. B. IARU Region 1 VHF/Microwave) ausgewählt. +Hier werden das eine lokale Login-Rufzeichen und Passwort für den ON4KST-Chat eingetragen. Zudem wird die **primäre Chat-Kategorie** (z. B. IARU Region 1 VHF/Microwave) ausgewählt. -Mit der Option für einen **zweiten Chat** (Multi-Channel-Login) kann man sich gleichzeitig in eine weitere Kategorie (z. B. UHF/SHF) einloggen. Beide Chats werden dann parallel überwacht. Hier kann optional auch ein abweichender Login-Name für den zweiten Chat vergeben werden (nützlich für Opposite Station Multi-Callsign Logging). +Mit der Option für einen **zweiten Chat** (Multi-Channel-Login) wird eine weitere Kategorie (z. B. UHF/SHF) per Single Sign-on in derselben ON4KST-TCP-Sitzung aktiviert. KST4Contest öffnet dafür keine zweite TCP-Verbindung und verwendet weder ein zweites lokales Login-Rufzeichen noch ein zweites Passwort. + +**Name in Chat 2** ist der eigene sichtbare Chat-Name in der zweiten Kategorie, kein zweites Login. Der sichtbare Chat-Name, der Nachrichtenkontext, die QRG und der Beacon bleiben für beide Kategorien getrennt. **Opposite Station Multi-Callsign Login-Tagging** bezieht sich dagegen ausschließlich auf Gegenstationen, die mit mehreren vollständigen Rufzeichen im Chat erscheinen. ### Rufzeichen und Locator -Eigenes Rufzeichen und Maidenhead-Locator (6-stellig, z. B. `JN49IJ`) eintragen. Diese Werte werden für Distanz- und Richtungsberechnungen benötigt. +Eigenes Rufzeichen und Maidenhead-Locator (6-stellig, z. B. `JN49IJ`) eintragen. ON4KST verwendet für beide Kategorien denselben Locator der einen TCP-Sitzung. Die Werte werden außerdem für Distanz- und Richtungsberechnungen benötigt. ### Aktivierte Bänder @@ -576,7 +577,7 @@ KST4Contest verwendet einen gemeinsamen Timer für beide Chat-Kategorien. Aktivi - **Beacon message** enthält den öffentlichen Nachrichtentext dieser Kategorie. - **Shared beacon interval** legt das gemeinsame Intervall für beide Kategorien fest. -Sind beide Beacons aktiviert, werden sie beim selben Timer-Lauf nacheinander in ihren jeweiligen Kategorien gesendet. Der zweite Beacon wird nur berücksichtigt, wenn auch der zweite Chat aktiviert und verbunden ist. +Sind beide Beacons aktiviert, werden sie beim selben Timer-Lauf nacheinander in ihren jeweiligen Kategorien gesendet. Der zweite Beacon wird nur berücksichtigt, wenn die zweite Kategorie in derselben ON4KST-Sitzung aktiviert und vollständig synchronisiert ist. ### Intervall und Timer-Verhalten diff --git a/github_docs/en-Configuration.md b/github_docs/en-Configuration.md index b2bcd15e..b58802c9 100644 --- a/github_docs/en-Configuration.md +++ b/github_docs/en-Configuration.md @@ -14,14 +14,15 @@ After the first start, the **settings window** opens – this is the central sta ### Login and Chat Categories -Enter your ON4KST chat credentials here (callsign and password). -Also, select the **primary chat category** (e.g., IARU Region 1 VHF/Microwave). +Enter the one local login callsign and password used for the ON4KST chat. Also select the **primary chat category** (e.g. IARU Region 1 VHF/Microwave). -With the option for a **second chat** (Multi-Channel Login), you can log in to another category simultaneously (e.g., UHF/SHF). Both chats will then be monitored in parallel. You can optionally specify a different login name for the second chat (useful for Opposite Station Multi-Callsign Logging). +The **second chat** option (Multi-Channel Login) adds another category (e.g. UHF/SHF) to the same ON4KST TCP session through Single Sign-on. KST4Contest does not open a second TCP connection and does not use another local login callsign or password. + +**Name in Chat 2** is the local name shown in the second category, not a second login. The visible chat name, message context, QRG and beacon remain separate for each category. **Opposite Station Multi-Callsign Login Tagging**, by contrast, refers exclusively to remote stations which appear in the chat under several complete callsigns. ### Callsign and Locator -Enter your own callsign and Maidenhead locator (6 characters, e.g., `JN49IJ`). These values are needed for distance and direction calculations. +Enter your own callsign and Maidenhead locator (6 characters, e.g. `JN49IJ`). ON4KST uses the same locator for both categories in the one TCP session. These values are also used for distance and direction calculations. ### Active Bands @@ -576,7 +577,7 @@ KST4Contest uses one shared timer for both chat categories. Each category nevert - **Beacon message** contains the public message for that category. - **Shared beacon interval** sets the common interval used by both categories. -When both beacons are enabled, they are sent one after the other in their respective categories during the same timer run. The second beacon is only considered while the second chat is enabled and connected. +When both beacons are enabled, they are sent one after the other in their respective categories during the same timer run. The second beacon is only considered while the second category is enabled and fully synchronised in the same ON4KST session. ### Interval and timer behaviour diff --git a/github_docs/en-Features.md b/github_docs/en-Features.md index d72b4b85..6dc441dd 100644 --- a/github_docs/en-Features.md +++ b/github_docs/en-Features.md @@ -307,7 +307,7 @@ Configuration, recognised QRG requests and category handling: [Configuration – ## Multi-Channel Login (from v1.26) -Simultaneous login to **two chat categories** (e.g. 144 MHz and 432 MHz). Both chats are monitored in parallel. +KST4Contest signs in to ON4KST once with one local callsign, password and locator. A second chat category (e.g. 144 MHz and 432 MHz) is added through Single Sign-on within the same TCP session. Both categories are monitored in parallel, while the local visible chat name, message context, QRG and beacon remain separate for each category. --- @@ -321,7 +321,7 @@ The green private-message age scale remains available in both designs. Text colo ## Opposite Station Multi-Callsign Login Tagging (from v1.26) -Support for stations that are active in the chat with multiple callsigns simultaneously (e.g. expedition setups). +Support for remote stations which are active in the chat under several complete callsigns at the same time (e.g. expedition setups). The complete callsign and chat category remain separate participant identities, while Worked, band and priority data are shared through the base callsign. --- @@ -437,7 +437,7 @@ Sniffed: (DN9APW-70 > 9A0BB-23) pse sked 19:30 This distinction is intentional. Monitoring aggregates the variants so that their communication remains visible. Message routing does not aggregate them because the intended login would otherwise become ambiguous. -The base callsign is evaluated across both connected chat categories. The category of each individual message remains unchanged. +The base callsign is evaluated across both chat categories in the shared ON4KST session. The category of each individual message remains unchanged. The monitoring view includes: @@ -703,7 +703,7 @@ The timeline is a preview. AirScout data can change, and a stored sked guarantee KST4Contest can send recurring CQ messages to the public chat. The beacon is intended for longer periods of calling CQ on a fixed frequency: it publishes the local QRG regularly without requiring the operator to enter the same text again. -Both chat categories use one shared interval, but each category has its own enable setting and message template. The second beacon is only sent while the second chat is enabled and connected. +Both chat categories use one shared interval, but each category has its own enable setting and message template. The second beacon is only sent while the second category is enabled and fully synchronised in the shared ON4KST session. Global variables such as `MYQRG`, `SECONDQRG`, `MYLOCATOR` and `MYQTF` are resolved immediately before every transmission. A QRG updated by the logging software can therefore appear in the next beacon. diff --git a/github_docs/en-User-Interface.md b/github_docs/en-User-Interface.md index ac1854a8..cfcc0180 100644 --- a/github_docs/en-User-Interface.md +++ b/github_docs/en-User-Interface.md @@ -4,7 +4,7 @@ ## Connecting to the Chat -Before connecting for the first time, configure at least the callsign, password, locator and primary chat category in the settings window. If a second category is required, its login must also be enabled and configured completely. +Before connecting for the first time, configure one local login callsign, password, locator and the primary chat category in the settings window. If a second category is required, enable and select it there. KST4Contest signs in once and adds the second category through Single Sign-on within the same TCP session. The connection can be started in two ways: @@ -54,7 +54,7 @@ Both indicators flash for approximately twelve seconds and then disappear. Their ### PM Window (top left) -The PM window shows private messages addressed to the local chat logins and the corresponding outgoing replies. +The PM window shows private messages addressed to the local visible chat names and the corresponding outgoing replies. Messages not sent by the local station are also shown when their text contains the configured local login callsign, ignoring letter case. This applies to public messages addressed to `ALL` and to directed messages between other chat participants. The informal description **“gossip detection”** is particularly apt for the latter case. diff --git a/website/src/features/dual-chat.md b/website/src/features/dual-chat.md index 1558003d..3e34b464 100644 --- a/website/src/features/dual-chat.md +++ b/website/src/features/dual-chat.md @@ -4,7 +4,7 @@ icon: 💬 category: ON4KST Chat since: "1.26" summary: Monitor two ON4KST categories in one interface while preserving the complete callsign and category required for correct message routing. -description: KST4Contest combines two ON4KST chat sessions, keeps individual logins separate and shares station-related Worked, band and priority information through the normalised base callsign. +description: KST4Contest uses one authenticated ON4KST TCP session for two chat categories, keeps their message contexts separate and shares station-related Worked, band and priority information through the normalised base callsign. tagsList: - ON4KST - dual chat @@ -29,27 +29,31 @@ VHF, UHF and microwave activity is not always concentrated in one ON4KST categor Opening two unrelated chat clients would show both message streams, but every comparison between them would remain manual. Worked status, band information, active stations and sked context would still be distributed across separate windows. -KST4Contest therefore opens up to two ON4KST chat sessions and processes both in one operating context. +KST4Contest therefore signs in once and adds a second chat category through ON4KST Single Sign-on when required. Both categories use the same TCP session and are processed in one operating context. ![Primary and secondary chat settings](/manual/assets/client_settings_window_station.png) -## Two connections remain two connections +## One connection, two category contexts -The primary and secondary chat sessions retain their own: +KST4Contest authenticates the ON4KST TCP session with one local login callsign, one password and one locator. The primary category is part of that login. If a second category is enabled, the client adds it to the same session through Single Sign-on. It does not open another TCP connection or perform a second local login. + +The primary and secondary categories still retain their own: - ON4KST chat category; -- login callsign; +- visible local chat name; - public message stream; -- destination category for outgoing messages; and -- active login entries. +- message context and destination category for outgoing messages; +- local QRG; +- beacon enable setting and message template; and +- active chat-member entries. -The second session can use the same local callsign as the primary session or a separately configured callsign. A different login may be useful when the station uses category- or band-specific suffixes. +The **Name in Chat 2** field changes the local name shown in the second category. It is not a second login callsign. Both categories continue to use the one callsign and locator supplied when the TCP session was authenticated. -Combining the display does not turn both sessions into one ON4KST connection. Messages must still be sent through the category in which the intended destination is active. +One connection therefore does not mean one combined message stream. Messages must still be sent in the category in which the intended destination is active. ## What identifies an active chat member? -An active login is identified by: +For remote chat participants, an active member is identified by: 1. the complete visible callsign, including its suffix; and 2. the ON4KST chat category. @@ -65,7 +69,7 @@ Consider the following active entries: | `9A0BB-23` | 2 | separate | | `9A0BB-13` | 2 | separate | -All four entries belong to the same base callsign, but they are four different chat logins. Joining, updating or leaving the chat affects only the corresponding complete callsign in the corresponding category. +All four entries belong to the same base callsign, but they are four different chat-member identities. Joining, updating or leaving the chat affects only the corresponding complete callsign in the corresponding category. This is particularly important for `9A0BB-2` and `9A0BB-70`: because both use the same category, the category alone cannot distinguish them. @@ -73,7 +77,7 @@ This is particularly important for `9A0BB-2` and `9A0BB-70`: because both use th ## How are messages routed? -When a row is selected, KST4Contest retains both the complete callsign and its category. A private message is addressed to that complete callsign and sent through the corresponding chat session. +When a row is selected, KST4Contest retains both the complete callsign and its category. A private message is addressed to that complete callsign and sent in the corresponding category within the shared session. Selecting `9A0BB-70` in category 1 therefore creates a message for `9A0BB-70` in category 1. It is not silently reduced to `9A0BB`, and it is not sent through category 2 merely because another variant is active there. @@ -86,11 +90,11 @@ The same distinction is used for: - sked reminder messages; and - leaving or updating an active chat entry. -The different variants do not have to be able to send messages to each other. That is not the purpose of the function. They must remain correctly reachable by other stations and receive the messages addressed to their respective login. +The different variants do not have to be able to send messages to each other. That is not the purpose of the function. They must remain correctly reachable by other stations and receive the messages addressed to their respective chat-member identity. ## What is shared through the base callsign? -Some information describes the radio station rather than one temporary chat login. This information is aggregated through the normalised base callsign. +Some information describes a remote radio station rather than one temporary chat-member identity. This information is aggregated through the normalised base callsign. For the examples above, the common base callsign is `9A0BB`. @@ -109,7 +113,7 @@ Per-band information is still retained. Working the station on 70 MHz does not m ## Why are band hints combined? -A station may use its visible login names to describe the available bands: +A remote station may use its visible chat names to describe the available bands: - `9A0BB-2` - `9A0BB-70` @@ -124,13 +128,13 @@ A manual NOT-QRV mark still takes precedence. An automatically detected suffix o ## Why is the Priority Score not duplicated? -The Priority Score represents the operating priority of the station, not the number of chat logins it happens to use. +The Priority Score represents the operating priority of the remote station, not the number of chat-member identities it happens to use. KST4Contest therefore calculates the score for the normalised base callsign and projects it to the active variants. Several suffixes do not create several independent priority candidates merely by being logged in more than once. The individual rows remain selectable because the correct message destination still matters. -In plain terms: one station should not occupy half the priority list, but the operator must still be able to contact the correct login. +In plain terms: one station should not occupy half the priority list, but the operator must still be able to contact the correct chat-member identity. ## Categories are context, not proof of a band @@ -150,7 +154,7 @@ Categories unrelated to the supported VHF, UHF, microwave or EME workflows are i Sharing the station context does not merge everything associated with the base callsign. -The following remain tied to the individual login or message: +The following remain tied to the individual remote chat member or message: - complete message destination; - chat category; @@ -158,15 +162,15 @@ The following remain tied to the individual login or message: - visible callsign suffix; - join and leave state; - the specific row selected by the operator; and -- message history associated with that login and category. +- message history associated with that chat member and category. -This distinction is the basis of the dual-chat implementation: operational information may be shared where it describes the same radio station, while communication remains attached to the actual ON4KST login. +This distinction is the basis of the dual-chat implementation: operational information may be shared where it describes the same remote radio station, while communication remains attached to the complete ON4KST callsign and category. ## Practical limitations -The shared base-callsign model assumes that suffix variants separated by `-` belong to the same underlying amateur-radio station. That is appropriate for common logins such as `-2`, `-70`, `-144` or `-432`. +The shared base-callsign model assumes that suffix variants separated by `-` belong to the same underlying amateur-radio station. That is appropriate for common remote chat names such as `-2`, `-70`, `-144` or `-432`. -KST4Contest cannot determine whether two operators behind those logins are using one station, several independently operated stations or a distributed contest setup. Worked and band information is therefore shared at callsign level, while the operator remains responsible for selecting the correct chat destination. +KST4Contest cannot determine whether two operators behind those chat entries are using one station, several independently operated stations or a distributed contest setup. Worked and band information is therefore shared at callsign level, while the operator remains responsible for selecting the correct chat destination. [Read how both chat categories are configured.](/manual/en/configuration/#login-and-chat-categories) diff --git a/website/src/features/macros.md b/website/src/features/macros.md index b878323a..98d5b1b3 100644 --- a/website/src/features/macros.md +++ b/website/src/features/macros.md @@ -170,7 +170,7 @@ A public beacon has no selected remote station. It can therefore use only global ![Beacon settings for both chat categories](/manual/assets/client_settings_window_beacon.png) -Each chat category has its own enable setting and message template. Both categories use the same timer interval. The second beacon is sent only when the second chat login and its beacon are enabled. +Each chat category has its own enable setting and message template. Both categories use the same timer interval. The second beacon is sent only when the second category and its beacon are enabled in the shared ON4KST session. Global variables are evaluated again on every timer run. A QRG changed by the logger can therefore be included in the next beacon without editing its template. diff --git a/website/src/features/qso-monitoring.md b/website/src/features/qso-monitoring.md index daab02c5..7536fe63 100644 --- a/website/src/features/qso-monitoring.md +++ b/website/src/features/qso-monitoring.md @@ -72,13 +72,13 @@ The base callsign is used to decide whether a message should be shown in the mon A message for `DN9APW-70` therefore remains a message for `DN9APW-70`. It is not redirected to `DN9APW`, `DN9APW-2` or another suffix. -This is the same distinction used elsewhere in KST4Contest: station-related information may be shared through the base callsign, while communication remains attached to the actual ON4KST login. +This is the same distinction used elsewhere in KST4Contest: station-related information may be shared through the base callsign, while communication remains attached to the remote participant's complete callsign and category. ## Both chat categories are included -When two ON4KST categories are connected, the same monitoring list applies to both. There is no need to configure the station separately for each category. +When two ON4KST categories are active in the same session, the same monitoring list applies to both. There is no need to configure the station separately for each category. -The category of the individual message remains part of its context. Combining the monitoring view does not merge the underlying chat connections. +The category of the individual message remains part of its context. Combining the monitoring view does not merge the category-specific message streams or create separate chat connections. ## What the function does not do