Never been this tired just from upgrading my software

Feedback
1

  • I am running 3 independent graphs for their own purposes, which means that the key features vary for each graph.

  • Wanted

    • I was considering an upgrade expecting enhanced UI in terms of snappy responsiveness,

    • with self-hosted sync, publish server on my OCI,

    • maintaining full control over my single source of truth in text-based files, yes markdown or sort of.

  • Costs

    • fragmented channels and mixture of signal and noise.

      • The website hosts 2.0 installer while the link to official documentation covers the old version.

      • I found OG, DB versions seem underway but neither is official. For instance, there is not a single word about DB on logseq.com, except discuss.logseq.com. Are common users willing to devote their time for making decisions on installation or upgrade?

      • As a result, I have no conviction the information on the official website is a reliable signal or just negligible noise.

      • While official Logseq remains 2.0 for windows desktop on the website, the community is heated up with new DB version and its new branch in the name of OG but no official feedback on it. Only community discussions.

      • Does Logseq team target only the users who wouldn’t be intimidated by the developer-friendly UI on Github? Or just avid users who are willing to join and voice out in the official forum? But the raised fund seems more than that.

    • nowhere to find up-to-date signals.

      • Once confirmed the existence of two signals regarding my software, I was unable to discern whether the information that I am reading is up-to-date or not.

      • Commonly, any brochure comes with the latest information without saying that “This is the last price, you’ll get what you see!” If so we say it’s “reliable.” In the case of Logseq, I had to be an information digger to keep myself posted from the 2 Github documents and the flux of chats in discord, and the other dispersed links all over the forum. In the end, I told myself “hey, the info on the official website is not precise, not reliable.”

  • Voice or exit

    • I am voicing out expecting any feedback or reactions from the team.

    • I need just a single source of truth regarding,

      • what will happen to my .md files. Is the md-to-DB mirroring confirmed?

      • Is it clear that Zotero plugin will be omitted by the first party?

      • Is whiteboard coming back? When? Or is it dropped?

      • Does it cost this level of time and effort to decide on an upgrade? Sadly I haven’t tried the real migration but the research on migration costs my time a lot.

      • If not available for doing this, please at least remove the information that doesn’t fit your releases. Let me hear your voice in easier way, people usually do it on their website. You have your own, right?

    • Or exit?

      • but sadly, few choices are available for those who want an open-source md PKM tool freed from folder-based hierarchical structure.

      • I am not willing to enjoy this level of fatigue for upgrading my tool. This is way much than I can tolerate. The upgrade is eating up my time.

2

Good questions yonggeun. I hope you get some solid answers from the team.

1 Like
3

Given that these very valid questions have gone unanswered for 7 days, and considering the generally disastrous communication coupled with virtually no progress in program development, we’ll probably have to slowly but surely start looking for a vibrant and actively maintained alternative. Even though, after 5 years of active use, I still don’t want to—and can’t—admit it to myself. Logseq is actually a great program, if it weren’t for the bugs that haven’t been fixed for years and the very poor performance with slightly larger graphs.

1 Like
4

I would suggest trying out tine on github

1 Like
5

Happy to meet you on the same page. Sadly no feedback yet.

1 Like
6

Exactly! I am still enjoying logseq. The app truly has cured my procrastination to the level no app has ever reached before. Its solid and tenacious implementation towards a complete outline-based PKM really changed the way I organize my life. But for me logseq is waning as it is losing its key momentum, the users’ faith.

Actually I tested one of my logseq graph on the combination of obsidian with quartz. Regardless of the minor glitches and the intrinsically distinctive approach, the new combination is way more reliable, communicable and swift. I am still in the middle of weighing the cost of switching between logseq and obsidian. But I found no reason to refuse obsidian for its clear vision and effective development management.

7

Good idea. Unfortunately a repo with the 865 issues in the queue terrifies me. So I tried reaching tien on discord.

8

or you meant this? https://tine.page/
Looks charm. Thanks.

9

I had the problem that logseq became so slow after the 3 years with it that it did not work for me anymore. searching can be slow for me come up but not writing notes and opening the app.

since I was still on markdown I decided to open the graph in obsidian and vscode with foam (or the outdated but still working loam fork). a lot of things don’t work the same but the two most important things do: outlining I can with regular markdown lists too and the zotflow plugin it’s just so much better than logseqs build in pdf and zotero support.
I thought I would switch back and forth but I have found that it is easier to use basic text search than to open logseq.

so effectively I will never switch to logseq db because a) I already switched somewhere else despite lock second theory being the better choice and b) it would prevent me from switching away instantly even if the performance would be better