Repository navigation
Sync: one-way links — receive only (send nothing) or send only - #120
Merged
Merged
Conversation
Copy public key used the Clipboard API, which exists only on HTTPS or localhost: on a node reached by its address it threw and did nothing, and the page showed only the fingerprint, so the fingerprint was pasted as DUG's key and refused (422) three times. The page now shows the whole public key to select; copying falls back to a selection where the API is missing (the API token's Copy too); the pin dialog says so when a fingerprint is pasted. change_refused audit records carry the reason the caller was told. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd only Settings → Nodes gets a Direction (send and receive, receive only, send only), enforced by the link whatever the transport carries. A node that receives only publishes nothing, never takes over reporting a track, and keeps its own track management and profile changes; "Ask peers to fill gaps" lets it send only summaries and wants. A node that sends only takes nothing in but answers trusted nodes' wants. The old Receive only toggle is renamed Accept no track management here (sync.no_local_management; receive_only still loads). The panel opens with a one-line summary of what the node does, notes on surprising combinations, a Taken in column, and an Add a node dialog that pins the key and shows the fingerprint to compare. The header badge shows a one-way node's direction. opentrack bridge takes ;send=off and ;send=repair per node. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md # ui/src/index.css # ui/src/pages/settings/NodesPanel.tsx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #117 (it reuses #117's Nodes-panel key display and fingerprint check). Merge #117 first, then retarget this to
main.Why
"Receive only" meant "accept no track management from this node's users". It never changed what the node sends: with sync on, a node always published its reports, decisions and summaries. So the setting promised the one thing it didn't do.
What
Direction (
sync.direction:both|receive|send), enforced by the link whatever the transport carries:sync.repair) allows onlysummaryandwant.wants.The old toggle is renamed "Accept no track management here" (
sync.no_local_management). Saved settings and config exports that usereceive_onlystill load, through a serde alias.The Nodes panel:
The header badge shows a one-way node's direction:
site OTK · receive only.opentrack bridgetakes;send=offand;send=repairper node.Docs: the admin guide gets a "One-way links" section with a two-node example. multi-node.md, sync-icd.md, reference.md and the CHANGELOG are updated.
Tests
reported_byset to the peer, and never reports.receive_onlydocuments load and are written back under the new name.send=parsing and which kinds are carried.syncDirectionsummary, badge, warnings and acceptance.-D warningsclean; fmt clean. UI: tsc, lint (0 errors), vitest 75, build.Checked on the 8091 test instance
Headless browser:
direction: "receive"; the header readssite OTT · receive onlyOn its NATS (
ot.sync.out.>, 14 s each):Settings were restored afterwards.
🤖 Generated with Claude Code