becouse of the multiple dots we could just replace the segments with

*

in the log turning a name like

example.example.test.md

into

*.*.*.md

that way it still would be visible when their are multiple

..

in a hierarchy name.

Additionally we may want to remove the hostname as well. Or replace it that way as well, since some hostnames can contain information that should not be shared as well. Should I open an issue for the log obfuscation?

yes!

Thanks for pointing this out! An info box calling attention ro this would probably be a really smart addition to the Dendron documentation, especially for academic teams. I'm in a team research project right now that would be way easier to manage with a tool like Dendron—and we also have this personally identifiable info responsibility. I could try to write something, but this weekend would be the absolute earliest I might have time. @kevins8

I wouldn't be the best person to write about this, since it's unusual for me to do research involving PII. But it's an important enough concern that I'd be willing to do a first draft of a notification / advisory box for the documentation, in hopes that better-informed people like @User or others might refine it from there.

Oh! And I should add that I don't have a strong opinion about the addition of telemetry itself. Just that the implications of this addition should be made very clear to anyone who might use Dendron for research as they establish their note-naming conventions.

+1 to concerns over sharing personal identifying information. This is a very significant concern for social scientists like myself, for whom dendron is a really handy tool!

https://github.com/dendronhq/dendron/issues/671 here is the issue

One Problem in General I see with Telemetry is that I would treat it like Analytic Cookies get treated under the

DSGVO

(The German law for Data Protection) in which Every Cookie That is not relevant to the Website you are using, needs to be

Opt In

and you could even get in trouble if you hide it behind a button like

Accept all Cookies

and make it harder to only accept the needed Cookies. There are some funny but understandable rules, around such things sadly telemetry has not yet such rules or Win doof wouldn't be calling home so much.

if you do, it would be a great starting point!

I use this every day of my life, so glad i found it

I would be happy to take a pass at some point, but I am not a lawyer

Wooo! 0.40

FYI footer text on dendron site looks jumbled on small screens

Looks like sidebar footer is overlapping the main content footer

It also looks like taking off

position: absolute

from

.site-footer

fixes the overlap on small displays (sidebar footer gets pushed to top) without affecting it on large displays.

just updated this. will get fixed in next weeks release 🙂 @User https://github.com/dendronhq/dendron/commit/7bcc72ab6ca59fd8de16056779b09776b1d6f10d

How do I bring up the lookup bar to create a new doc again

I've seemed to have forgotten cause ive been working out of the same notes for 1200 lines

docs show how to bring up the lookup bar but it seems to create a yml file this time around for the schema

not what im tryna do

COMMAND L

that needs to be uh, first thing on the docs

imo hahaha

UNLESS I MISSED IT

command L brings up lookup for notes, command shift L brings up lookup for schemas. you want command L 🙂

You can also type

>Dendron: Lookup

❤️

I find the first of these two commands clashes with the standard

⌘L

shortcut VS Code provides to select the current line At the moment I've updated my

keybindings.json

preferences with the following, but it's still not ideal (given it means the Dendron lookup only works when a file is open, and I always end up opening the lookup when trying to select the current line of a note).

{
  "key": "cmd+l",
  "command": "dendron.lookup",
  "when": "resourcePath =~ /path/to/parent/folder/"
}

It's definitely not a big thing but asking cos I assume I'm missing something obvious, or others have better ways of dealing with commands that conflict with existing hotkeys/shortcuts

Keybindings are a bit of an headache because vscode itself already has a lot of features. At the end some kind of remapping has to happen on the user's end. So now the problem we have to solve is figiring out a sensible default mapping so that it doesn't introduce too much friction. I started a discussion a while ago about this issue. Would love your input if you have any more to share : https://github.com/dendronhq/dendron/discussions/700