w2g VS docs

A friend of Conor White-Sullivan (Roam's creator) propped up his own take on how to do a notetaking system that does support edges, and then he went a step further and opened it for everyone to edit, so it's just a single shared graph:

<https://github.com/w2g/w2g>

Mek works at the Internet Archive, and it clearly follows the same spirit of "we'll operate the service, feel free to bring your own frontend if you don't like ours". I wasn't happy with the way that one at graph.global tries to subvert/duplicate native browser features, so I put up a minimal "client" for browsing existing nodes that feels similar to the default one, sans annoyances on those specific axes:

<https://graph.5apps.com/LP/streamline>

I never got around to allowing editing, unfortunately. You'll have to use the default frontend for that (annoying, since it's buggy) or write a client of your own.

The key issue I see with the graph.global model is that you have to use triples. I've found that this results in big hurdles for throughput—i.e., the opposite of notational velocity. The ideal thing would probably be to allow a Roam-like system where you can start out by simply linking two related nodes, and then fill the edge details after the fact. You could sort of approximate this with w2g as it stands by just using a generic is-related-to connector and then reify the relation. This does mean you would lose the ability to query by relation unless you add further attributes or went back and edited the original connector to replace it with something more appropriate before reification. Stopping in your tracks to find the appropriate connector is something I found to have lots of overhead.

This is, in theory, what graph.global is supposed to be (by Mek from OpenLibrary / Internet Archive).

<https://github.com/w2g/w2g>

Looks cool! I couldn’t tell from the homepage, but it looks like they support cross-device syncing [1]. The big gap left is the rich plugin environment that Obsidian has.

1: https://docs.logseq.com/#/page/how%20to%20sync%20your%20logs...

I've become a big fan of LogSeq for these reasons. In LogSeq, you have pages and trees of data (aka blocks[1]. All can be cross-referenced or embeded between each context. It's quite nice.

1: https://docs.logseq.com/#/page/the%20basics%20of%20block%20r...

https://github.com/logseq/docs > Code > local > Download zip

You clearly didn't use it much or maybe you didn't take a look at the documentation: https://docs.logseq.com

Official Docs Official Plugin Dev Doc

Would you be so kind and give an example of such a tagged block? I had a look at the documentation and only found https://docs.logseq.com/#/page/how%20to%20create%20pages%20i... that does not addresses blocks.

Also another use for logseq is that you can deploy your notes or some of them as static HTML. the documentation website above is an example. Its hosted on GitHub pages: https://github.com/logseq/docs

Yep. There's a plugin API, https://docs.logseq.com/#/page/Plugins, used by 180+ plugins. Logseq can also be scripted from the commandline in node.js with https://github.com/logseq/nbb-logseq#projects-using-nbb-logs.... There are examples for creating a github action, a CLI or creating custom web apps

Cmd-K to find any line in your notes and Cmd-shift-K to find any line in your page. Starting with 0.8.3 there is also a native find-in-page feature, https://docs.logseq.com/#/page/Find%20in%20page, which can search anything that is visible including results of queries