Bases (.base) sync #47
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#47
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #37. Depends on the
structuredfile kind.What Relay does
Synced by default as of 0.8.12, but requires storage — a paid plan or
self-hosted storage. (
relay.md/updates/relay-0-8-12, read 21 Sep 2026.)The design question they have not answered
Their issue #45 is open and blocked on exactly this: a
.basefile mixes aquery with a view, and syncing the view forces everyone's sort order and
filters. Their maintainer says so directly.
We should decide it rather than inherit it: sync the query, treat view state as
local. If that turns out to be wrong, it is a smaller mistake than the reverse —
a shared sort order that silently overrides what someone set is the kind of
invisible loss
CLAUDE.mdwarns about, applied to preferences rather than prose.What we do today
.baseis a blob — last-writer-wins with a conflict copy.Risk
risk:none.Verification
Two vaults with different sort orders both keep theirs while the query converges.
Moved to the Vikunja board as NEC-24: https://projectron.nerchure.com/tasks/24