Skip to content

FEATURES.md

Latest commit

 

History

History
73 lines (57 loc) · 3.14 KB

FEATURES.md

File metadata and controls

73 lines (57 loc) · 3.14 KB
Raw

Features

A closer look at what Drive Bridge does. Setup steps and every setting are in TECHNICAL.md.

Two-way sync

Your vault and one Google Drive folder stay in step, on desktop and on phones. Syncs run on startup, on a schedule, when you leave Obsidian, as you edit (realtime), or by hand from the ribbon, the command palette or the settings. Sync this file syncs just the open note, from its header or the file menu. A manual sync can list every planned change for you to confirm first, and undo any one of them: keep the other side's version, or bring a deleted file back. On a large Drive, Changes only asks Drive what changed instead of listing everything each time, with a full scan once a day to be safe. Details: Sync strategies, Sync behavior.

Sees every file

Most Drive plugins only see files they created themselves. Drive Bridge uses full Drive access, so anything that lands in its folder, from an AI assistant, a script, a teammate or a backup job, comes into your vault on the next sync. Filter rules decide what is left out. Details: Why the full drive scope.

Nothing silently lost

  • Conflicting edits keep both versions (note.md and note.conflict.md), or are merged with Smart merge. Strategies that replace a version are marked with a warning.
  • A sync that would delete more than 50 files, or 5% of the vault, stops and asks. Keep them copies each file back.
  • Vault deletions are confirmed in automatic syncs, and deleted files go to the trash on both sides.
  • Never delete on Drive keeps Drive as an archive of everything.
  • No frontmatter, tags or markers are ever added to your notes.

Details: Conflict resolve strategies.

Easy setup

  • A guided list of the four one-time Google Cloud steps, each with a button to its page; pasting the downloaded client file fills in the ID and secret.
  • Sign in with Google in the settings, on desktop and on phones. No terminal needed.
  • Export settings on one device and Import settings on the next: the Google account travels encrypted with your passphrase.

Details: Setup.

Recovers on its own

  • An interrupted sync (Obsidian closed, offline, cancelled) picks up where it stopped.
  • Requests to Google are retried with backoff.
  • A file that keeps failing is skipped and named instead of blocking the rest, and can be retried later.
  • Last sync shows the result in plain words, such as Can't reach Google. The last 30 syncs are listed with what moved, and the log opens in a window.

Private by design

  • Your own Google Cloud client; nothing is compiled into the plugin.
  • The client secret and refresh token stay in the device's secure storage, never in synced files.
  • Requests go only to Google, plus a webhook URL if you set one.
  • No telemetry, no analytics, no code downloaded at runtime.
  • The plugin never touches the clipboard: logs, reports and exports are shown for you to select and copy.

Details: PRIVACY.md, Security model.