Feature Request: Safe Deletion & Rename Sync between Raindrop and Obsidian

[jiangaq]

Hi @frostmute 👋

First of all, thank you for building Make-It-Rain — it’s been a great bridge between Raindrop and Obsidian.
I’d like to propose a new feature to make the synchronization workflow more complete and safer.

🧭 Problem

Currently, when a Raindrop item is deleted or renamed on the Raindrop side, the corresponding note in Obsidian remains unchanged.
Over time, this can lead to “orphaned” or outdated notes that no longer reflect the real state of the Raindrop library.

💡 Proposed Feature

Add an optional safe sync mode that:

1. During sync, compares all local notes (by raindrop_id in frontmatter) against the current Raindrop API data.

2. Detects Raindrop items that have been deleted or renamed remotely.

3. Before performing any local changes, displays a confirmation dialog / list view showing:

   • Which items are missing remotely (potential deletions)
   • Which items have renamed titles or changed metadata

4. Allows the user to manually choose which actions to apply (delete / rename / ignore).

5. Shows a clear warning before any local file is deleted or renamed.

⚙️ Optional Settings

• Enable or disable “Remote deletion/rename detection” in plugin settings.
• Choose automatic or manual confirmation behavior.
• Option to move deleted items to an Archive/ folder instead of hard deletion.

✅ Benefits

• Keeps Obsidian vault in sync with the actual Raindrop library state.
• Prevents data drift and duplicate clutter.
• Maintains full control and safety (no silent deletions).

Thanks for considering this request — I think this feature would make Make-It-Rain a truly complete two-way synchronization tool!

[frostmute]

Hi @jiangaq,

Thank you for this incredibly thoughtful feature request — and for the kind words about the plugin. I apologize for the long silence; I got overwhelmed and stepped away from the project for a bit. That's not fair to users like you who took time to engage constructively.

On your proposal: This is excellent. Bidirectional sync with safety controls is exactly what would make this a "complete" integration. Your detailed spec — confirmation dialogs, archive option, settings toggles — is spot-on.

Current status: This is on the roadmap (I had "bi-directional synchronization with Raindrop" noted) but honestly, it's a significant undertaking that I haven't had bandwidth for. Your issue helps me prioritize it.

Next steps:

• I'm doing a maintenance pass now to clear the backlog
• Bidirectional sync is a big feature — I'll need to scope it properly
• If you're interested in contributing or testing when I start on it, I'd love the help

I'm committed to being more responsive going forward. Thanks again for the detailed write-up — this is how good features get built.

— @frostmute

[frostmute]

Just an update.... I've got this sooooorta worked out. But before proceeding with this additional functionality, I'm completely refactoring the project away from the 'one-giant-file' as it currently stands and breaking it out into a modular system. This will make future additions much easier to implement in addition to making it WAAAY easier for anyone that wants to contribute going forward.

Stay tuned!

— @frostmute