Earlier quoted context omitted.
Could you provide an example of one of the well written explanations?
just go and look at any of the vendors selling “zero trust” solutions. They all have white papers available about how a) perimeter security is “dead” and b) how their specific flavor of zero trust is the One True zero trust and the only thing you can trust to protect your data. You will without exception need to provide an email address to access these white papers, so their inside sales team can ensure you fully und…
Ditching Obsidian and building my own
501–510 of 570 posts
Re: Ditching Obsidian and building my own
#502Earlier quoted context omitted.
Ah ok. I guess that means when a user leaves the team, you have to re-encrypt the codebase with a new symetric key (as the user would still know the old symetric key)?
Depending on the threat model you want to protect against, yes. For example, although a revoked user doesn't have direct access to data anymore, they could technically collude with us to get future encrypted messages and then decrypt them. At the moment rekeying is only possible by exporting a workspace, changing its key (with a command line tool), and then reimporting it.
Re: Ditching Obsidian and building my own
#503About a year ago I did the same migration: Obsidian to self-hosted Directus. My main reasons were: - Straightforward queries. I have a lot of structured data in my notes and lesson plans, and being able to work with SQL was ideal. - A web app was much more reliable than Obsidian's third-party sync platforms. - I could extend Directus to do all sorts of other things. I eventually built my wedding planner and website b…
You're the first person I've heard of that has gone this route. Cool to know I'm not alone. And yeah I have the same gripes around the writing experience. I prefer Vim so I've been looking into ways I can use my notes as local markdown which sync on save. Of course, keeping the Directus editor for my mobile device edits.
It's highly eclectic, but might give you some ideas?
Re: Ditching Obsidian and building my own
#504Earlier quoted context omitted.
I think what they meant is that if it's hosted online / home-network, only allow access to all services through a VPN. Wireguard is relatively easy to setup, and you can configure all your services to only be available through wireguard. Ever since ssh almost got backdoor-ed, the only thing "exposed" on my servers is Wireguard, which is UDP based and therefore harder to know if it's running. SSH also goes over wiregu…
> ... Wireguard, which is UDP based and therefore harder to know if it's running. Isn't it basically impossible to know if it's running unless you have an authorize key? I thought it didn't respond at all unless you ping a valid entry key off it.
Re: Ditching Obsidian and building my own
#505Earlier quoted context omitted.
NAT busting, and no key management. What extra dependencies does Tailscale have?
Well, the dependency on Tailscale's servers, for one. You're getting that NAT-busting because Tailscale is running servers to handle that for you, and you're getting around key management by having them manage your keys and overlay their own auth layer for you.
Re: Ditching Obsidian and building my own
#506Earlier quoted context omitted.
NAT busting, and no key management. What extra dependencies does Tailscale have?
How do you identify yourself to Tailscale?
Re: Ditching Obsidian and building my own
#507Re: Ditching Obsidian and building my own
#508Earlier quoted context omitted.
> I think my only other question is around my preferred "Daily Journal" workflow and unreferenced tags how do you generally go about that? Trilium has the concept of day notes¹, incrementally building a time-structured hierarchy (years/months/days, but you can configure that however you want), under which you can park your notes. Or you can just let them stay unordered under an "#inbox"² for later categorisation. It'…
Oh that all sounds super neat! My current workflow is to drop almost everything into my daily notes, whether time-based, time independent, or reference. The non-time-based notes I'll #tag and logseq will create a new page for the tag or add the block to that page's references. That way I have both my thoughts on a #topic, and when I thought about it. If I go back and look at the topic and notice a bunch of notes abou…
For instance, if you type "I went to @ThatOldPub with @Alfred", @ThatOldPub can be created on the fly as a [Place], and just like every other [Place], it will have an attribute ~location=@London (@London being itself a note of type [City] itself having as attribute ~country=@UK, …) ready for you to fill now or later. Same goes for @Alfred being a Person.
That way you are not just building a graph of "related things" with their name as a weak link, you are creating a semantic graph of typed entities, where notes can be approached not just from edge-to-edge but as clusters, and manipulated in bulk.
> The other thing I like are "unreferenced blocks" where if I don't think to tag a stray thought I have about, say, RAG, it'll still show up on my #rag page.
I never trusted that mode, that puts too strong a constraint on how you would name your tags, with essentially typos flying under the radar and leaving an impression that there might be more "strays" than meets the eye. That said, Trilium has a vivid ecosystem of tools, scripts and extensions surrounding it¹, and if hunting for missed references sounds fun, there you go²!
¹: https://github.com/Nriver/awesome-trilium ²: https://github.com/Nriver/trilium-py?tab=readme-ov-file#adva...
Re: Ditching Obsidian and building my own
#509Earlier quoted context omitted.
Well, the dependency on Tailscale's servers, for one. You're getting that NAT-busting because Tailscale is running servers to handle that for you, and you're getting around key management by having them manage your keys and overlay their own auth layer for you.
So Tailscale has "extra dependencies" on Tailscale. Gotcha.
Re: Ditching Obsidian and building my own
#510Earlier quoted context omitted.
Oh that all sounds super neat! My current workflow is to drop almost everything into my daily notes, whether time-based, time independent, or reference. The non-time-based notes I'll #tag and logseq will create a new page for the tag or add the block to that page's references. That way I have both my thoughts on a #topic, and when I thought about it. If I go back and look at the topic and notice a bunch of notes abou…
Yep, you can totally do that with Trilium. Instead of #topic, you would type @topic in the body of your note, Trilium will autocomplete trying to find matching references (containing "topic" in either their name or attributes or path or prefix), and if none exists, a new "topic" note will be proposed to be created on the fly. You will also be asked whether the new note should derive from a Template or not, and that's…
I think I'm sold. Thank you for answering all of my questions so thoroughly.