techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#logseq

5 posts5 participants0 posts today

I'm working hard this week on #SOURCE issue two, an experimental quarterly "pay as you feel" magazine about #opensource. As a sneak peak we'll be looking at getting started with #godot, using #logseq and #syncthing for a 2nd brain system, simple ways to contribute to #openstreetmap and the #termux application for android! Should be out in Aug (or earlier!). Issue one was an experimental issue looking at Computational Fluid Dynamics with #FreeCAD DL here.. concretedog.blogspot.com/2025/
Boosts welcome!

🖥️ After 5 years of daily-driving Linux, I finally made a video breaking down my full workflow — the tools I use every day and why I stick with them.

▶️ Arch Linux, Hyprland, Jellyfin, Logseq, Zen Browser — minimal, efficient, and self-hosted where it matters.

Would love your feedback, it’s my first video!

🎥 youtu.be/xqR_cnO0htY
#Linux #ArchLinux #FOSS #Hyprland #Jellyfin #Logseq #SelfHosted #LinuxDesktop

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

Почему-то я не могу выбрать для себя инструменты и пользоваться ими.

Всё никак не могу выбрать инструмент для ведения своей knowledge base.

Сейчас использую
#DokuWiki + #Logseq.

Но Logseq мне не нравится тем, что он на
#Electron, а DokuWiki я почему-то решил вести на английском.

Вот и вчера весь вечер смотрел ролики про
#OrgRoam. Хочу теперь туда переехать. Там можно и вики вести и дневничок писать. Вот только картинки не будет отображать, но не знаю нужны ли они мне.

Весь в раздумьях теперь...
:blobfoxnotlikethis:

#logseq has revolutionised my life.

I don't yet even use more than its basic functionality, but here's how my meeting cycle goes:
* Notes on my daily journal, peppered with hashtags and future dates as needed.
* Review hashtags when time allows, and move journal notes onto hashtag-related pages.
* Review future dates and consolidate items on same dates into agendas.
* Set up meetings, and copy-paste agenda into invitations.
* Run meeting, using agenda.
* Repeat.

Additionally:
* I've never had a better-structured backlog before.
* I'm evolving habits of note-taking that generate meaningful documentation.
* People are beginning to fear my follow-ups, cuz I never forget.

Starting to get an enjoyable vibe from using the #Logseq DB Alpha.

It is basically a new app, so I'm no longer expecting ye aulde Logseq features.

Still. Property links need to show up consistently in backlinks, as special relations—they do for "up", but not "uses". Probably for the same reason those connections don't show up in the graph view.

But I can add nearly arbitrary properties to a node, and that's helped my workflow.

Replied to bitbonk

@bitbonk

#Logseq uses an in-memory database, DataScript, and to store on disk it uses MD/Org files. So during the RAM<->disk movement there is also the translation to/from MD/Org. With Logseq DB they added a SQLite DB (a file on the disk) to dump DataScript there before translating to/from Markdown, disentangling RAM<->disk from DataScript<->Markdown. The plan is to "sync" the DB with local Markdown files in the future and remove the current MD mode, so probably it won't get new features.

Man, this whole #Logseq DB transition is confusing.

So Logseq MD will continue to be supported on desktop and mobile and I can always decide whether I use DB or MD for new graphs, correct?

What features will not be available or not work as well when I choose an MD based graph? (e.g., sync and RTC)

What features will not be available or not work as well when I choose a DB based graph? (e.g., self hosting with sync)

discuss.logseq.com/t/logseq-db

@logseq

Logseq · Logseq DB Unofficial FAQSo Logseq MD will continue to be supported on desktop and mobile and I can always decide whether I use DB or MD for new graphs, correct? What features will not be available or not work as well when I choose an MD based graph? (e.g., sync and RTC) What features will not be available or not work as well when I choose an DB based graph? (e.g., self hosting with sync)

The #logseq devs finally merged their famous DB backend into Main. Hope they can now refocus on making the best personal knowledge management system even better. It's been too long.

Dung Nguyen created a slash commands package for #emacs . This looks like it can help in adding #logseq niceties into my #orgroam setup, and I can think of several other places this would work great too.

github.com/bluzky/slash-comman

Seen on @sacha 's amazing newsletter.

Missing slash commands pakage for emacs. Contribute to bluzky/slash-commands development by creating an account on GitHub.
GitHubGitHub - bluzky/slash-commands: Missing slash commands pakage for emacsMissing slash commands pakage for emacs. Contribute to bluzky/slash-commands development by creating an account on GitHub.

Using the current file-based #Logseq instead of the in-development database version. There is so much less friction, especially around workflow bits involving plugins.

And you know how it is with PKMs. Plugins are embedded in easily half my workflow.