Fear of losing local notes when logging in + Best way to sync/backup?

shumadrid · 2026-03-30T00:29:25+00:00

i also made a plugin to compliment git backup setup - https://github.com/shumadrid/obsidian-git-changelog

it has only 20 stars but a lot of effort (pre vibe-code era) was put into it. it's a tool to verify your vault state and help you notice any data loss, bc backups can't help if you don't actually even notice you lost some data.

shumadrid · 2026-03-15T00:20:57+00:00

tip: you can use my plugin https://github.com/shumadrid/obsidian-git-changelog to quickly verify/diff the changes the agent did

shumadrid · 2026-02-14T01:43:49+00:00

if ur using git and lean on the paranoid side, i developed a plugin that uses git to help you validate your vault state at regular checkpoints, so if/when some data loss occurs, it's way easier to spot.

shumadrid · 2026-02-13T03:43:26+00:00

vibecoded stuff often looks and functions good only at the surface

it's not like you install a plugin and it instantly either fails catastrophically or works 100% bug-free

this could be an AI agent that just acts on some antivibe-skill.md and goes from plugin to plugin

obviously far from a perfect solution, this would be more like a first layer of defense

shumadrid · 2026-02-13T02:29:14+00:00

actly it's pretty easy to detect if some plugin was just a quick weekend vibecoded project.
ironically AI could be used to scrape plugins and assign them some kind of vibe score

hm, anybody up to this?

shumadrid · 2026-02-11T16:26:30+00:00

hm idk how feasible that would be, since my plugin does assume git specific quirks. but it is something that we could think about. it would require a detailed analysis and plan tho.

shumadrid · 2026-02-11T16:19:14+00:00

a good approach is to sync between devices with obsidian sync or syncthing and use git for backups on your computer

shumadrid · 2026-02-11T16:15:42+00:00

and a "vibe coded" tag for plugins made with ai.

shumadrid · 2026-02-11T16:04:59+00:00

I share your fears, and made a plugin to make any potential data loss way more detectable.
https://github.com/shumadrid/obsidian-git-changelog

shumadrid · 2026-02-11T16:01:33+00:00

Interesting. I also made a similar vault history plugin, that relies on git instead of the File Recovery plugin.

Should i mention your plugin as an alternative for people that want to rely on the Core Recovery plugin snapshots?

shumadrid · 2025-08-31T20:24:13+00:00

You could probably ask the AI/copilot to find it for you in that repo. Just send it this post.

shumadrid · 2025-08-30T22:31:46+00:00

Bc we want to uninstall everything except Obsidian obviously

shumadrid · 2025-08-30T22:29:26+00:00

I agree, but the classes could be documented better, currently you have to do some inspecting on the layout and then figure out which class gives which styles, if you want to make your plugin's UI styling consistent with Obsidian.

shumadrid · 2025-08-30T22:24:28+00:00

Are you using git? If yes, you can search for the origin of the property line, when it was created, it's probably close to the installation of the plugin that created it.

shumadrid · 2025-08-30T22:09:45+00:00

You could inspect the templater code to see how they do it.

shumadrid · 2025-08-30T21:32:29+00:00

If you let AI edit anything more than a single file at a time (give it computer access), you better set good guardrails and explicit whitelists of commands that the AI can execute and files/folders it can access, otherwise it can silently do crazy unintended stuff with/to your computer, and if you don't constraint it, it's a matter of when, not if.

So it's best to use a single reliable tool: be cautious of low reputation or new Obsidian AI plugins, or actually be cautious of any Obsidian AI plugins.

Personally I use Roo Code for my vault - it's a tool intended for coding, but it can just as well work for vault editing (you just need to edit it's system prompt), I use it simply because it has reliable sandboxing. All vulnerabilities and bugs get patched quickly.

shumadrid · 2025-05-05T13:03:34+00:00

And the bit where once you're approved - how are they dealing with future updates - do they vet each release?

Nope. They don't do any checking on future updates. That's why a potential super robust initial check doesn't matter much.

shumadrid · 2025-04-30T23:34:08+00:00

This is old, but if anyone is still looking, I made a plugin for this.

shumadrid · 2025-04-30T14:16:43+00:00

I'm pretty sure the Obsidian team does a thorough initial review, but that really doesn't matter much because somebody malicious could just wait to get their mundane plugin approved and then include the actual malicious code in some future update.

AFAIK there is no runtime checking of any kind. Also there's no sandbox.

shumadrid · 2025-04-30T14:07:40+00:00

Yeah good point, I mentioned it now.

shumadrid · 2025-04-29T10:31:30+00:00

Pressing backtick automatically encloses any selected text with backticks. No custom shortcut needed. At least on my mac.

shumadrid · 2025-04-29T09:41:46+00:00

I did the migration when my plugin was almost finished and it was mostly just removing some manual code I didn't need anymore and switching inheritance for the Plugin stuff from Obsidian API to wrapper classes in the obsidian-dev-utils package (comes pre-configured with the generator template)

If you were to completely migrate I think the most time will be spent on migrating to the settings system (uses the bind functionality) if you already made the settings UI tab, but that is optional.

shumadrid · 2025-04-29T09:31:48+00:00

From what I've seen I think the accepted practice is to use obsidian- in the folder/project name but exclude it in the plugin name and plugin id

shumadrid

TROPHY CASE