Thanks for your videos, they get my little brain a pondering. I would be interested in watching a group of Logseq gurus, brainstorm about their user stories. What would the top ten story categories be? How does Logseq fulfill each story? I am not a power user yet, but here’s a few of my stories: - ## #U1: As a writer, using Logseq - ### #S1: I need to be confident that the document I spend years writing will be safe. - ### #S2: I need a journal that I can use in a manner which I am comfortable with. - ## #U2: As a requirements engineer, using Logseq - ### #S3: I don’t want to spend more time maintaining my documents than I do writing them. - ### #S4: I need to isolate my projects, but still search across them.
Thank you for the video. I am looking forward to be able to have Tana like tags in LogSeq. I have been thinking on switching to Tana because it is more convenient to use their supertags, but I prefer LogSeq for many other reasons like the ability to filter on backlinks at the bottom of a page and how it shows the last entries first. I did a live query on Tana for some scenarios but its not the same.
Totally get this, I love the idea of Tana, but want open source and have control over my data. So knowing that this function is on it's way really helps with sticking with Logseq. Having to memorize my data structures (okay, I have it in a page obviously) really clutters my space.
apt update only updates the cache. you need to also use apt upgrade or apt dist-upgrade to apply the updates. apt dist-upgrade auto removes old unused packages
I don't want to sound like a pessimist, but I feel like it's a wrong path. If they want fast loading - then lets write MD-related stuff in Rust/Go. But adding all these fields, types etc - is a path to nowhere. It adds big complexity and takes away flexibility of text documents. After all, is it a knowledge database software, or an applications prototyping tool? It looks like waste of time. As for collective editing - I agree with the expressed arguments. But I'd prefer to have a powerful, stable and featured single-user text database w/o any SQL/whatever database than a multi-user monster which pretends to be another Microsoft Access.
Fair enough, personally I think the 2 way MD sync option that will come after this will allow for the best of both. Clean Markdown files and easier merging of data. That said I also want to make a video on why I think that Markdown as a backend is flawed to begin with. But still collecting all the talking points for that one as it's a complex topic.
![Lp. Последняя Реальность #107 РОДНОЙ ДОМ [Финал] • Майнкрафт](http://i.ytimg.com/vi/IK3QKzKUlHM/mqdefault.jpg)
Thanks for your videos, they get my little brain a pondering.
I would be interested in watching a group of Logseq gurus, brainstorm about their user stories. What would the top ten story categories be? How does Logseq fulfill each story?
I am not a power user yet, but here’s a few of my stories:
- ## #U1: As a writer, using Logseq
- ### #S1: I need to be confident that the document I spend years writing will be safe.
- ### #S2: I need a journal that I can use in a manner which I am comfortable with.
- ## #U2: As a requirements engineer, using Logseq
- ### #S3: I don’t want to spend more time maintaining my documents than I do writing them.
- ### #S4: I need to isolate my projects, but still search across them.
That sounds like a fun livestream
Thank you for the video.
I am looking forward to be able to have Tana like tags in LogSeq. I have been thinking on switching to Tana because it is more convenient to use their supertags, but I prefer LogSeq for many other reasons like the ability to filter on backlinks at the bottom of a page and how it shows the last entries first. I did a live query on Tana for some scenarios but its not the same.
Totally get this, I love the idea of Tana, but want open source and have control over my data. So knowing that this function is on it's way really helps with sticking with Logseq. Having to memorize my data structures (okay, I have it in a page obviously) really clutters my space.
apt update only updates the cache. you need to also use apt upgrade or apt dist-upgrade to apply the updates. apt dist-upgrade auto removes old unused packages
Forgot the basics during the live stream, and used to my system auto updating by cron every day. Will give it a go on the wsl
Just to make sure, this new version is still local right? No cloud involvement whatsoever?
Yes, fully local
I don't want to sound like a pessimist, but I feel like it's a wrong path. If they want fast loading - then lets write MD-related stuff in Rust/Go. But adding all these fields, types etc - is a path to nowhere. It adds big complexity and takes away flexibility of text documents. After all, is it a knowledge database software, or an applications prototyping tool? It looks like waste of time. As for collective editing - I agree with the expressed arguments. But I'd prefer to have a powerful, stable and featured single-user text database w/o any SQL/whatever database than a multi-user monster which pretends to be another Microsoft Access.
Fair enough, personally I think the 2 way MD sync option that will come after this will allow for the best of both. Clean Markdown files and easier merging of data. That said I also want to make a video on why I think that Markdown as a backend is flawed to begin with. But still collecting all the talking points for that one as it's a complex topic.