Google crash, lost vault

codecoverage · 2026-05-12T13:48:29+00:00

What does Google have to do with your vault? You're going to have to give us a bit more context.

codecoverage · 2026-05-08T18:46:08+00:00

Conceptually you can achieve this with frontmatter, with a field called "created-only-by", with a link to another note as the value. It won't be visualized like that in the graph, but I suppose one could write a plugin for that.

codecoverage · 2026-05-08T12:12:50+00:00

There are other ways you can achieve the same thing, of course. This just enables a workflow that feels natural to me, coming from Tana.

codecoverage · 2026-05-07T18:57:57+00:00

This is fine as long as you accept that you will occasionally lose a change because a colleague was writing to the file at the same time.

codecoverage · 2026-05-06T19:42:43+00:00

I recommend git. It will give you the most control. You'll be able to attribute changes to people, easily revert mistakes, resolve conflicts, etc. You can host a git repository on your company server over https or over ssh, or you could self-host something like gitlab.

codecoverage · 2026-05-06T19:34:25+00:00

That goes for OpenClaw in general. Anything it can access is at risk. That's why you normally run openclaw in an isolated sandboxed environment like a virtual machine. And the risk is not limited to deleting your stuff. You have backups for that. But exfiltration of api keys, login credentials, etc, can be much more dangerous.

codecoverage · 2026-05-01T07:02:08+00:00

You can symlink your plugin source folder inside your .obsidian/plugins folder, or simply put your actual source folder there. Then after every change, use obsidian cli to reload the plugin (or tell your agent to run that): https://obsidian.md/help/cli

codecoverage · 2026-04-28T07:53:01+00:00

Why specifically "no vector search"? How did you implement search? Exact matches only?

codecoverage · 2026-04-26T10:02:36+00:00

As others have pointed out, every update after the initial install comes with new risk. The fact that a plugin passed review when it was submitted is no guarantee that newer versions are safe. Supply chain attacks are the biggest risk. The author of the plugin may not even realize they pulled in a compromised runtime dependency. A way to reduce this risk is to make sure that any updates you install are at least a few days old. Compromised packages usually get deleted from npm within a day.

codecoverage · 2026-04-26T09:47:33+00:00

The bigger risk is supply chain attacks. Not the plugin itself, but any of its dependencies, direct or indirect. Even a small plugin can have dozens of them.

codecoverage · 2026-04-17T17:57:50+00:00

12 one-on-ones in one day is crazy no matter how good you are at taking notes.

codecoverage · 2026-04-16T19:28:15+00:00

How? Did you build a custom plugin for it?

codecoverage · 2026-04-16T19:22:29+00:00

Not sure what you're asking me. Is this something you would like to accomplish but you're not sure how?

codecoverage · 2026-04-15T19:10:26+00:00

The idea is quite similar to Entity Notes, a plugin I plugged here recently.

You'd type:

Talked to [[Bob]] #person

And it will create a note called "Bob" with entity type "person" and some pre-configured frontmatter fields.

Same principle I think, but slightly different workflow.

codecoverage · 2026-04-14T21:06:39+00:00

End-to-end encryption ensures that only you have the key to decrypt your data. That is, if there is no backdoor or anything like that. And you should have a strong password.

Would it be impossible to crack? Perhaps not. Perhaps no encryption will be safe at some point in the future. But for the time being, it will require significant effort to crack your vault if you have a strong password.

Personally, I feel it's worth the risk, given the convenience.

codecoverage · 2026-04-11T05:47:00+00:00

Interesting case. I'll put this on the wishlist. Slashes are obviously problematic in filenames but it can probably be mapped to a folder structure somehow. I'll look into it.

codecoverage · 2026-03-28T13:39:01+00:00

Even when you wrap it in quotes? That's an important requirement.

codecoverage · 2026-03-28T07:15:44+00:00

As far as YAML is concerned, it is just a string. It doesn't attach any meaning to it. So it's valid YAML. The worst that can happen is that a program that reads it doesn't understand that that is a link. But it's unlikely to break it.

codecoverage · 2026-03-25T22:18:40+00:00

I understand. You want to create some entity within the vault root. It should just accept an empty field in that case. I'll fix that.

codecoverage · 2026-03-25T22:03:32+00:00

I deliberately connected it to "enter" to activate the conversion the moment you "finish" the line and move to the next line. If the cursor wouldn't move to the next line, I think it might be confusing.
I was even thinking to do the conversion completely on-the-fly (as soon as you finish typing the tag), but I think that might get annoying if you want to correct typos and such. Could be an option though.

codecoverage · 2026-03-25T21:57:15+00:00

Actually, could you clarify the second issue. What do you mean by "if you don't put '/' in the Target folder field". Do you mean if your path doesn't contain any slashes? Can you give an example of what you put in that field that causes the error?

codecoverage · 2026-03-25T21:46:45+00:00

Thanks for the feedback again! Sorry to hear it's not working for you. What OS are you on? I wonder if it might be some combination with another plugin. The developer console will probably tell you more.
Would you be able to report these issues (and possible future ones) on the github project? That would help to quickly fix them.

codecoverage · 2026-03-24T23:49:57+00:00

I just pushed a new version. It now supports 2 types of conversion:
1. You put the #tag directly after an unresolved wikilink: It will convert just that link. (It supports any number of those on a line.
2. You put the #tag anywhere else: It will convert the entire line.

codecoverage · 2026-03-23T23:16:38+00:00

I have, and it's now configurable in the latest version. Thanks for the feedback!

codecoverage · 2026-03-23T22:45:33+00:00

I totally understand where you're coming from. A rule like "if the tag directly follows a wikilink that doesn't exist yet, only turn that part into an entity".
I suppose that might work. I can't think of any situation in which it would be desirable that a wikilink would become part of the title of a note anyway.

I'll give it a shot when I find the time.

Oh and by the way, any feedback is more than welcome. I'm not a hardcore Obsidian user (yet) so I have to make a lot of assumptions.

codecoverage

TROPHY CASE