This makes a lot of sense! I’m going to give it another shot with these insights in mind. I think if I frame it as a future-facing tool like you describe I’ll avoid a lot of my previous mistakes.

Thanks for explaining :)

This is really helpful, thanks!

I think I need more practice with knowing when to create a node. In the past, every single entry would look like this:

I went to [Alice] birthday party and met [Bob]. We talked about [clouds].

And that got very cumbersome. I like your suggestion of using back links to create a better summary document.

Got it, I see what you mean. Thanks for this!

I keep failing to make Zettelkasten and org-roam work for me. Do you use a single knowledge base for your whole life, with millions of tags and pages? Or should I be making separate directories for each project? Is the “daily journal” the best place to put everything, with well tagged entries?

You don’t have to answer all of those!

I won’t be using these features, but I’m not sure there’s cause for concern. The implementation seems very sensible and legitimately privacy-centric. The LLM runs locally and is meant as an very basic email proofreader. The crypto wallet is a likely an extension of the password management tech they’ve already developed, with transaction features that some people care about.

I can see why some people want these features, and I’m glad there are new alternatives.

What a weird situation. I suppose it’s nice those workarounds exist, even if they’re not ideal.

Interesting! I assume it involves a smart plug and an automation script that monitors battery level?

Wow, Graphene really doesn’t have charging limits?

I assume this is the discussion you referred to, and I think it broke my trust in the project.

Edit: As far as I can tell, many of the frustrating parts of that thread are from random posters and not devs. I’m still annoyed that such a basic feature is considered controversial.