home.social

#logseq — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #logseq, aggregated by home.social.

fetched live
  1. Some performance upgrades for really, really long pages. Here are 5000 blocks, indented and all.

    iPhone 15 handles it without hickups. 👌🏻

    #mimir #logseq #obsidian #pkm

  2. Looks like I recommend #logseq and colleagues are using it. Unfortunately I do not know who and cannot warn them that they unknowingly switched to the database version.

    Had at least 2 colleagues telling me they had problems with logseq recently. Told them to install logseq-og

    What a shit show.

  3. Looks like I recommend #logseq and colleagues are using it. Unfortunately I do not know who and cannot warn them that they unknowingly switched to the database version.

    Had at least 2 colleagues telling me they had problems with logseq recently. Told them to install logseq-og

    What a shit show.

  4. I'm really enjoying working with @logseq as a note taking and knowledge management tool.

    Unfortunately I've created distinct graphs for different projects I'm involved in at work. But it seems quite heavy lifting to merge them together into one to allow for better cross-likability and task management across my 'work life'.

    The new 'DB' version takes a bit of getting used to for me, but I can see the benefits over the previous 'OG' (markdown files) version.

    If you haven't used it, yet, but are into stuff like #Obsidian, give it a shot. It's open source and fully cross-platform. #Logseq has a very low overhead of friction when working with it. Everything is a node, and it can all be linked with ease.

    #OpenSource #tools #FLOSS

  5. I'm really enjoying working with @logseq as a note taking and knowledge management tool.

    Unfortunately I've created distinct graphs for different projects I'm involved in at work. But it seems quite heavy lifting to merge them together into one to allow for better cross-likability and task management across my 'work life'.

    The new 'DB' version takes a bit of getting used to for me, but I can see the benefits over the previous 'OG' (markdown files) version.

    If you haven't used it, yet, but are into stuff like #Obsidian, give it a shot. It's open source and fully cross-platform. #Logseq has a very low overhead of friction when working with it. Everything is a node, and it can all be linked with ease.

    #OpenSource #tools #FLOSS

  6. 👂 Interested? Get early access, become a member of the 'inner circle'. Only email required: https://tally.so/r/yPbWLd

    I’ve always loved the idea of an outliner, yet I have to find one that doesn’t require a course to figure out. Or isn't just plain ugly.
    In 2016, I started a career in UI/UX. This year, I’ve started my passion project: Mimir. An outliner and expression of everything I’ve learned since then.

    Mimir is deliberately limited, yet not stunted. Users can make and add oEmbed widgets per block. They can use the URI for power functions. The rest of the features should be easily understood.

    There’s ✅:
    A journal view and loose pages
    Wikilinking and showing backlinks
    Block-level referencing
    Simple formatting of text
    TODO/DONE task management
    Simple 'templates'
    URI-support (for Apple Shortcuts or other automation)
    oEmbed anything (sandboxed)
    Cloud sync
    Export to Plaintext

    There’s NOT ⛔️
    Multiple ‘vaults’
    Markdown files
    iCloud sync
    Open-source
    Web-access
    Document-mode
    Image support (not natively)

    I am making this application for myself. Yet, several people have shown interest. And that feels like an opportunity. The plan is to release it with one-time payment for each major release, across platforms. It would include free, encrypted, hosted in the EU, cloud sync. Starting with macOS and iOS, and with enough interest, Android and Windows after.

    #obsidian #logseq #pkm #notetaking #indiedev #indieapps

  7. 👂 Interested? Get early access, become a member of the 'inner circle'. Only email required: https://tally.so/r/yPbWLd

    I’ve always loved the idea of an outliner, yet I have to find one that doesn’t require a course to figure out. Or isn't just plain ugly.
    In 2016, I started a career in UI/UX. This year, I’ve started my passion project: Mimir. An outliner and expression of everything I’ve learned since then.

    Mimir is deliberately limited, yet not stunted. Users can make and add oEmbed widgets per block. They can use the URI for power functions. The rest of the features should be easily understood.

    There’s ✅:
    A journal view and loose pages
    Wikilinking and showing backlinks
    Block-level referencing
    Simple formatting of text
    TODO/DONE task management
    Simple 'templates'
    URI-support (for Apple Shortcuts or other automation)
    oEmbed anything (sandboxed)
    Cloud sync
    Export to Plaintext

    There’s NOT ⛔️
    Multiple ‘vaults’
    Markdown files
    iCloud sync
    Open-source
    Web-access
    Document-mode
    Image support (not natively)

    I am making this application for myself. Yet, several people have shown interest. And that feels like an opportunity. The plan is to release it with one-time payment for each major release, across platforms. It would include free, encrypted, hosted in the EU, cloud sync. Starting with macOS and iOS, and with enough interest, Android and Windows after.

    #obsidian #logseq #pkm #notetaking #indiedev #indieapps

  8. @itskamrankhan In a free/libre and extremely capable software called #orgmode whose limits are only bound by the limits of your imagination. (1)

    Through #FOSS and (in contrast to #Markdown (3)) well designed and easily re-used clear text data format #orgdown (2, 5), I do have many possibilities to generate input for it and re-use output in other tools. Orgdown is recognized without any manual conversion in lots of tools (4).

    Let me cite Dominik's tenth rule: Any sufficiently complicated #PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode.

    1 karl-voit.at/orgmode/
    2 karl-voit.at/2021/11/27/orgdow
    3 karl-voit.at/2025/08/17/Markdo
    4 gitlab.com/publicvoit/orgdown/
    5 gitlab.com/publicvoit/orgdown

    #Emacs #PKM #Zettelkasten #Obsidian #MD #notion #logseq

  9. @itskamrankhan In a free/libre and extremely capable software called #orgmode whose limits are only bound by the limits of your imagination. (1)

    Through #FOSS and (in contrast to #Markdown (3)) well designed and easily re-used clear text data format #orgdown (2, 5), I do have many possibilities to generate input for it and re-use output in other tools. Orgdown is recognized without any manual conversion in lots of tools (4).

    Let me cite Dominik's tenth rule: Any sufficiently complicated #PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode.

    1 karl-voit.at/orgmode/
    2 karl-voit.at/2021/11/27/orgdow
    3 karl-voit.at/2025/08/17/Markdo
    4 gitlab.com/publicvoit/orgdown/
    5 gitlab.com/publicvoit/orgdown

    #Emacs #PKM #Zettelkasten #Obsidian #MD #notion #logseq

  10. Some keyboard toolbar work.

    It seemed such a good idea to make the icons swap. Most important action near the thumb.

    But now I am not so sure.

    Thoughts?

    #ux #ui #design #logseq #obsidian #mimir #indiedev

  11. Loki our Shiba Inu and I agreed. We are going to hike more.

    I wanted to remember our adventures in #Mimir.

    So here's a map builder based on .gpx! Positions are entirely stored in the URL. 😎 Nothing saved on disk. Well … except for the URL in the block.

    oEmbed enables so many fun additions without feature creep and code bloat. 👍

    #logseq #obsidian #indiedev #pkm #journaling

  12. Задолбали тормоза #logseq. Переехал на #obsidian. Привычка оформлять заметки в виде outline никуда не делась. За 3 года хорошо въелось в пальцы;)

  13. Задолбали тормоза #logseq. Переехал на #obsidian. Привычка оформлять заметки в виде outline никуда не делась. За 3 года хорошо въелось в пальцы;)

  14. Got your research in?

    Ready to start writing your article?

    Outline a bit differently. Get the creative juices going?

    Just drag and drop! Courtesy of HTML5 their DnD API. 😁

    This was actually not a hard thing to implement.

    #logseq #obsidian #roamresearch #indiedev #mimir #iawriter

  15. #Mimir on iPad is a thing now. It works out of the box, few quirks with the keyboard and the stoplight in the left corner there. But pretty minor things.

    My poor iPad 2018 though. It's on its last legs.

    #indiedev #dev #logseq #obsidian

  16. Do you use #Logseq (OG) with auto-committing? Tired of "Auto saved by Logseq"? Can't be bothered to push manually? Well look no further, my friends!

    github.com/Xophmeister/logseq-

  17. Only took 5 years off my life but, hey! oEmbed is a thing. Now to styling it to make it less jarring visually.

    Can't allow clicking to open in browser from the embed itself. Security reasons. Maybe I can make a fullscreen exception. Would be good…

    I practically did this to have Youtube play while I take notes anyway. Everything else is a nice bonus.

    #logseq #obsidian #pkm #mimir

  18. @pedersen Having used #Logseq for quite some time I want something that's built to be database-backed and handle syncing between devices from the start. Logseq development really slowed to a crawl surrounding the "DB version"

    Also, I've been wanting to learn Rust, and I have a really slow ARM laptop, so something without a big ol' electron frontend would be nice too.

  19. @pedersen Having used #Logseq for quite some time I want something that's built to be database-backed and handle syncing between devices from the start. Logseq development really slowed to a crawl surrounding the "DB version"

    Also, I've been wanting to learn Rust, and I have a really slow ARM laptop, so something without a big ol' electron frontend would be nice too.

  20. Several people have asked whether Mimir will ever get released to the public.

    A few thoughts I have about this prospect, if ever!
    ⁃ It’s a very opinionated piece of software. I will not build in features that I won’t use.
    ⁃ It’ll be a high price up front, no-subscription type of deal. One payment per platform. ≈€20-€50 per license.
    ⁃ Pay for upgrading major versions. Small incremental updates free.
    ⁃ It would have a free, build-in sync service. The current solution? UX wise I am against. That also means it’ll never have attachments and image hosting.
    ⁃ The safe-keeping of your notes would be downloading a zip of your database in plain text. Could even be a monthly email with an expiring link.
    ⁃ I’d probably have some AI do the support and bug tracking.

    Essentially Culture Code their Things business model.

    Still interested?😆

    #obsidian #logseq #pkm #mimir #indiedev #notetaking

  21. Be honest. How much do you really look at your "Unlinked References" in your #PKM setup?

    What if your software at least offered you to link something up when you're in the same headspace, instead of behind a toggle.

    Well. Mimir does now. 😅 It was a struggle to get the effect right, but I think this is getting there.

    #mimir #logseq #obsidian #indiedev #outliner #notetaking #roam

  22. Having an URI with #mimir also opens up (oldschool) JS bookmarklets.

    Handy for saving articles.

    Or … extract todos from a page you're visiting.
    Or … save a Mastodon post?
    Or … you think of something.

    #logseq #obsidian #pkm #notetaking #buildinpublic #indiedev

  23. It was meant to be a temporary Product Icon for Mimir. But it's growing on me. Thoughts? Dark mode and clear variant also look pretty good.

    #mimir #logseq #indiedev #obsidian

  24. Practical guide to personal knowledge management: choose between Obsidian, Logseq, and DokuWiki, understand PKM methods like Zettelkasten and PARA, and build self-hosted knowledge systems.

    #Obsidian #Logseq #DokuWiki #Self-Hosting #SelfHosting #Knowledge-Management

    glukhov.org/knowledge-manageme

  25. Practical guide to personal knowledge management: choose between Obsidian, Logseq, and DokuWiki, understand PKM methods like Zettelkasten and PARA, and build self-hosted knowledge systems.

    -Hosting -Management

    glukhov.org/knowledge-manageme

  26. Building my own outliner has given me respect for both #Roamresearch and #logseq their engineering teams.

    I now also understand why Logseq DB is taking this long. They are dealing with a feature set that is mind-boggling. (And, I wouldn't be surprised that it will be their demise in the end).

    There are SO many edge-cases and unusual #UX quirks.

    #mimir

  27. @AugierLe42e @victorhery perso j'utilisais #logseq et maintenant @silverbulletmd dans une note de journal avec un hashtag dédié
    En suivant le lien du hashtag j'avais tous les backlink vers les entrées du journal et on pouvait suivre la fréquence et l'intensité de mes migraines

  28. @AugierLe42e @victorhery perso j'utilisais #logseq et maintenant @silverbulletmd dans une note de journal avec un hashtag dédié
    En suivant le lien du hashtag j'avais tous les backlink vers les entrées du journal et on pouvait suivre la fréquence et l'intensité de mes migraines

  29. Thoughts?

    When I design, I am hyper-focused on re-using systems and simple affordances.

    After a few sketches, I came to the conclusion that I don't need a grandeur task system. There's already pages with linked references.

    Two obstacles:

    • The round-trip of checking off all the tasks on different pages. (Can't edit inline in backlinks.)
    • I needed to able to switch from [[TODO]] to [[DONE]] easier than activating edit-mode, clicking into it, selecting four characters, and typing done.

    This is the solution I came up with: begin block with 'todo' (case-insensitive) and it'll be a [[todo]] in disguise, styled.

    Clicking it changes it to [[done]], instead of navigating to [[todo]].

    #obsidian #notetaking #pkm #outliner #logseq #roamresearch

  30. @julien @taseroth You're right, it's not.

    However they managed to tick all the other boxes of that definition which is the important part here from my point of view.

    I've lost #Orgdown file sync for good (not coming back) and I need to convert all my data files to a different format even if I'd continue using #logseq.

    What would you call that instead?

    Therefore, I certainly migrate the data to a different solution where major breaking changes are less likely.

  31. @julien @taseroth

    en.wikipedia.org/wiki/Enshitti

    "Enshittification [...] is a process in which two-sided online products and services decline in quality over time. Initially, vendors create high-quality offerings to attract users, then they degrade those offerings to better serve business customers, and finally degrade their services to both users and business customers to maximise short-term profits for shareholders."

    I'd say we do have a match using that definition.

    I can really understand their rationale but they had an open FOSS product which now creates heavy lock-in effects as well as removing very crucial features.

    Playing with open cards would have been better: look, we're giving our SW away for free but we want to do business and therefore expect breaking changes as well as future lock in. 🤷

    Besides: there are several options for FOSS projects to make money.

    #logseq

  32. @julien Well, with the major changes (discussed for a year or so), #logseq is dead to me and many other users: (temporary?) no file sync, database only, removed support for #Orgdown syntax, proprietary sync (a paid service?), ...

    If you haven't migrated, you may do so now depending on your requirements: karl-voit.at/2021/01/18/tool-c

    karl-voit.at/orgmode/ is the best solution out there by far but many people can't use it. For very simple use cases, #Silverbullet seems nice. However, it also has #Markdown which is a downer as well: karl-voit.at/2025/08/17/Markdo At least, they are aware of its downsides: silverbullet.md/Markdown

    HTH
    #publicvoit

  33. Shoot. Seems like #Logseq 2.0 broke my 700 pages of markdown notes. WTF.

  34. @Cyber I've stopped using logseq because it was getting so slow, and the IOS version has been unusable for years. Buuuut I really do not want a DB version, I want my stuff in files. And I do simplynot understand why you need to use a DB to be fast ... files are not slow! But maybe it's a side-effect of electron-based apps being horrible slow anyways .... #logseq

    So now I'm using neovim - but this is not an alternative for many people. So I'm sad about this.

  35. Practical guide to personal knowledge management: choose between Obsidian, Logseq, and DokuWiki, understand PKM methods like Zettelkasten and PARA, and build self-hosted knowledge systems.

    -Hosting -Management

    glukhov.org/knowledge-manageme

  36. Wait a second.

    For my Mimir #outliner … why use wikilink syntax ([[]]) instead of … the hashtag! It's essentially the same in my use case.

    And it is much easier to type and understand.

    #pkm #obsidian #logseq

  37. Ich bin es von Logseq gewöhnt, mit `[[Wor` eine Vervollständigung zu bekommen, das auszuwählen und dann wird ein Link zu `[[Wort]]`eingebaut. Wie macht ihr das mit orgmode?

    Dabei ist bei mir `Wort` eine Überschrift mit einer ID `Wort`. Der Weg C-c C-l und `id:Wort` einzugeben oder direkt `[[id:Wort][Wort]]` einzugeben, erscheint mir fehlerbehaftet. Ich hätte gern eine Art Autovervollständigung. Ideen?

    #logseq #orgmode #emacs