Logseq - A privacy-first, open-source knowledge base

Congrats! Y'all have come a long way. 👏🏾

I like that it doesn't put a lot of constraints on how you organize information.

LogSeq is great. I've used a bunch of other tools in the past which were all clunky in some way. LogSeq takes a different approach, which I think fits the human mind more. We take life a day at a time, creating memories as we go, remembering details over that history. LogSeq is similar, you can simply write what's going on into the daily journal log, no need to create a page, folder, or structure. Just write. Tag what you're talking about inline and LogSeq will pull all the related notes you've made in the past together, into it's graph database. You can use it really simply, like that, and not have to get into the more complex ways some others use it.

Many many thinks for your developing the great tool! Logseq is the most confortable tool for writing I've ever tried for reasons: 1. **block instead of article**: I dont' have to think about writing an article anymore. I just write down whatever I think is meaningful. 2. **native support of tags**: the most light-weight way to organize blocks(ideas) 3. **show block after writing**: this feature overcame the inconvenience of traditional markdown based writing and shortened the cycle "write-view-modify". 4. **block based link/embed": the killing feature!!!! 5. **block make re-org of notes much easier**: just drag and put bock to re-org the notes The features I hope Logseq to have: 1. **more powerful export API**: Logseq decouples writing from publishing. But we still need to publish content in some cases. And the publishing should be automatic. I personally prefer publishing through tools "blogdown" and "bookdown" which are tools developed in R and using Markdown as basic intermediate format with Latex support. I'm using some Python scripts to convert the .md by Logseq to Rmd files used by "blogdown" and "bookdown". 2. **improved Excalidraw support**: for example: a pure view mode when not editing the draw block; automatically converting to a SVG file and updating link when exporting. 3. **native support of diagram.net**: diagram.net (draw.io) is a better tool over Excalidraw in many cases. 4 **option to embed block content, not the block structure**: currently when a block is embedded, the embedded block structure shows as content of the embedding block. This is not natural in some cases because the content is just needed to be in both places. Here are just my personal suggestions: 1. Logseq is quite a different note-taking tool. I prefer calling it "content-organzing" tool. I think markdown format is not quite suitable as Logseq file format. Logseq is about "content+structure", Markdown is about "content+format". For long-term, markdown format will limit the development of Logseq. Markdown is a good export format because many tools are support it and Markdown can be converted into many different final publish format. But the purpose of Markdown format is not the same as Logseq's. 2. I don't like to think about the format when writing in Loqseq. For example, I prefer not writing heading with "#" because Logseq knows this is the first-level heading. When it's exported, may Logseq add the "#" automatically? Just for your reference! Thanks again for your great job!!

I've started using Logseq and I really like it! It is slowly but steadily changing how I take and organise my notes. Would love a built-in sync functionality to seamlessly sync between mobile and laptop.