athens VS logseq

You might be interested in how in Athens we modelled properties as named (map-like) block relationships: https://github.com/athensresearch/athens/blob/main/doc/adr/0026-properties.md

https://github.com/athensresearch/athens

The underlying in memory datalog style database that can run in the browser that enables these apps

There is a docker compose file on there github that made things easy to get started. Has a web interface and was very quick. You could have multiple users as well.

I need a guide how to install athens for installing previously downloaded go packages. I have created a binary file from athens https://github.com/athensresearch/athens and configure .toml with path to local storage, also change the storage parameter to [disk

Athens

Get the docker compose manager. Create a new stack and put in the docker Compose file from Athens. Change to the ports and volumes you want and you are good to go.

Has anyone successfully running a selfhosted version of Athens from athensreseach. There is a demo. They even have a document page with some help for docker.

Does anyone have a "lab notebook" style of PKM in Emacs?

I used to use Org-Roam in Emacs, but fell in love with Logseq [0], primarily because

1. it has a "daily journal" default workflow (though individual pages are supported)

2. the support of datalog queries

3. templates

This basically allows me to make templates for things I need (e.g. meeting notes, etc) and to write a few key queries (that are also templated for reuse) to do things like get the most overdue tasks, upcoming, things I promised to others, things I'm waiting on, etc. I can even drill down and get that stuff for an individual "page", e.g. "Emacs" or "C++".

The lack of a "lab journal" format + flexible queries makes going back to other solutions not as enticing, as the "perfect artifact" of wiki-esque editing (and not being able to easily see backlinks) is not as easy. I can open my Logseq folder, make a "meeting" template, then #tag the people and topics discussed, and be able to go back later and make a query to see when I discussed #topic with #person.

I would love to move this back into Emacs, as I hate having a separate tool for PKM, so if anyone has a similar workflow (or at least flexible queries on "tags" and task status, backlinks, etc, even without the daily journal thing), I'd be grateful for any tips.

[0] https://logseq.com/

logseq fully free and open-source Obsidan-like tool with fewer plugins, however, it also gives you a chance to complex everything a lot. I have been using it for less than a year, however at some point, I noticed that I'm writing longer forms in Obsidian, and daily notes in Logseq. Why? Due Logseq design. It starts everything as a new point with -, even if it's a standard Markdown. We’re starting everything at a new point. Issues?

I would recommend https://logseq.com/

Progress on the `master` branch is a bit slow because there's a transition towards using a database instead of the filesystem https://github.com/logseq/logseq/tree/feat/db

https://discuss.logseq.com/t/why-the-database-version-and-ho...

Unfortunately, I think it's ultimately unethical to support the normalization of closed-source text-editing software, because it sets a bad precedent for the level of trust a user should have in their computing environment. For this reason, I much prefer Logseq. https://logseq.com/

I really like Logseq, and I feel it's the only one of the note-taking tools that has the tradeoffs I want (outliner, local-first, focuses on content on a block-by-block basis, has backlinks), but recently there's been not much happening, and the mobile app has been slightly broken for me for a while now (when opening a note I often can't add new bullet points, so I end up writing notes in an invalid format).

I'm really looking forward to their db-oriented version which is supposed to be merged into main (here's the long-lived branch[0]) this month. Presumably that will bring the project back up to speed, since that branch is currently almost 4k (!!!) commits ahead of main.

At the same time, I'm a bit worried about how the company is gonna sustain itself. After all they raised quite a bit of money, while at the same time I'm not sure how large a market there is for commercialisation of an open-source PKM app like this. Esp. since it looks like its market-share is maybe ~1/10th that of Obsidian (based on most popular plugin download counts). TFA is kind of related to this.

While Obsidian is great from a sustainability perspective (it seems to me) but unfortunately it comes short of being a good outliner.

[0]: https://github.com/logseq/logseq/tree/feat/db

The best tool for this I've found so far is Logseq [0]. The only things that come close in functionality are some really custom Emacs roll-your-own things that were just too hard for me as a basic Doom Emacs defaults user, and Anytype. However, I couldn't understand the storage of Anytype enough to convince me that my work would be okay with it (e.g. encryption, but IPFS-ing your files all over the place, maybe?).

Anyway, here are the reasons to consider Logseq for a "lab journal". Note all of these features are unique to Logseq (except the ones I note, afaik), but the subset of them are from what I can tell:

1. Local storage: this is just messing around with markdown on a local file. You can keep it in your corporate storage as a regular folder, at home, it is completely separate from your data sync setup and you can choose what you want. They are working a new database-backed version of the files for faster querying (though I have >10k files in it now and it does fine).

2. Open source: Obsidian, a popular alternative, is not open source. Considering this carries confidential info and all my personal stuff (not at work though!), I gotta trust my tools.

3. Killer feature that only Logseq has: custom, datalog query engine to query your existing notes and aggregate things. Other tools have some similar thing, but it's mostly akin to "search" and possibly ANDing some terms together, but Logseq has much more advanced uses enabled by this engine.

The datalog and querying feel initially like a "draw the rest of the fucking owl" meme, as it is up to you to decide whether you want to create namespace hierarchies (e.g. should your `vim` page be `devtools/vim`, just `vim`, or tagged with `devtools`?), but once you figure out a system, it takes a bit to craft a few clever queries and reuse them with templates.

I have a reasonably slick system for this, where I have a set of queries prioritized by due date / priority on my home page, along with incoming (waiting for someone) and outgoing (someone waiting on me) dependencies. I organize things with a series of "project" pages that each have a very long query to aggregate all my daily journal entries (and other pages) that are tagged with anything related to that project page (e.g. I have a page `CMake Template Repository` where I'm trying to create a github template repo for C++ projects so I don't have to write it from scratch each time). It has really helped me get things done despite having a bit of ADHD. If there's enough interest, I can try to write this up in a blog post.

[0] https://logseq.com/

Logseq support via our Logseq Plugin