Customisation Sync, not Hidden File Sync, for the tablet's interface - #84
Merged
Merged
Conversation
Both compose.yaml and SETUP.md named Hidden File Sync as the way the stripped-back interface reaches the Android tablet. Not false — it does cover .obsidian/ — but it points at the wrong one of LiveSync's two overlapping features for this setup. Upstream is explicit that they are not to be mixed: "Hidden File Sync is a separate feature with different setup, selection, and conflict behaviour; do not use both features to manage the same files." They resolve conflicts differently, so running both over the same content is a way to lose settings. Customisation Sync is the right one here because it is device-aware. Two Macs and a tablet are not three copies of one machine: the tablet should not be loading desktop-only plugins, and Hidden File Sync mirrors .obsidian/ wholesale with no lever for that. Customisation Sync pins state to a named device and applies it deliberately, which is also upstream's own recommendation for getting a desktop plugin setup onto mobile. Adds a "Syncing the interface itself" section covering the distinction, the requirement to name devices before applying anything, and the ordering constraint — enable it only once plain note sync works on all three devices, since doing it during setup gives you a sync problem and a config problem at once with no way to tell them apart. Marked as not verified: neither feature has been run on this instance, and upstream's docs/hidden_file_sync.md is a 404, so this comes from docs/settings.md and the maintainer's discussion threads. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Follow-up to #82 and #83. Both
compose.yamlandSETUP.mdnamed Hidden File Sync as the way the stripped-back interface reaches the Android tablet. Not false — it does cover.obsidian/— but it points at the wrong one of LiveSync's two overlapping features for this setup.Why it matters
Upstream is explicit that the two are not to be mixed:
They resolve conflicts differently, so running both over the same content is a way to lose settings — which makes "which one" a real decision rather than a naming detail.
Why Customisation Sync
.obsidian/as filesThe device model is the whole argument. Two Macs and a tablet are not three copies of one machine: the tablet shouldn't be loading desktop-only plugins, and Hidden File Sync mirrors
.obsidian/wholesale with no lever for that. Customisation Sync pins state to a named device and applies it deliberately — also upstream's own recommendation for getting a desktop plugin setup onto mobile.Also captured
Not verified
Neither feature has been run on this instance, and upstream's
docs/hidden_file_sync.mdis a 404 — this comes fromdocs/settings.mdand the maintainer's discussion threads. Flagged inline in SETUP.md rather than presented as tested.Comments and docs only;
compose.yamlre-checked withpodman compose config. No behaviour change.🤖 Generated with Claude Code