#Logseq honest review
๐ข #FOSS with AGPL license (in theory)
๐ด In reality it depends on a closed source module responsible for sync, dubious legality and misleading
๐ก Developed almost privately by a Venture Capitals funded company but accepting small contributions on GitHub and donations on OpenCollective
๐ข Store notes in #Markdown (or in less supported #OrgMode) locally
๐ก Forces indented lists in .md files and it doesn’t support normal paragraphs at all
๐ก Introduces syntax that breaks Markdown in a very bad way instead of using code blocks where possible (in Advanced Queries?)
๐ก Based on Electron, NodeJS and NPM
๐ก UI and business logic mixed together, it forces you to always run the whole UI, including for sync
๐ข Available for Linux on FlatHub (unofficially)
๐ด AppImage is the only officially supported way to install on Linux
๐ก No official reproducible builds but unofficial Flatpak ones are reproducible
๐ก Not in F-droid (and the closed source sync feature wouldn’t be allowed there anyway), you have to grab their APK manually or automatically
๐ข Supports Wayland but not by default
๐ข Custom CSS
๐ก Fixed UI, no tabs, no split view
๐ก Multi-window means multiple conflicting whole instances
๐ข Plugins platform
๐ด Plugins marketplace based on GitHub
๐ก Poor integration of plugins especially from UI/UX PoV
๐ข Very interesting concept of PDF annotations
๐ก PDF annotations not stored in the .pdf as standard annotations
๐ก PDF annotations stored in their own .md files with odd names
๐ข LaTeX formulas support
๐ก No native PDF export and in general problematic
๐ก Too many menus, command palettes and other redundant UI elements
๐ข Queries with simple syntax and UI
๐ก Advanced Queries are too often needed
๐ข Datalog query language in Advanced Queries
๐ก Very broken aliases feature
๐ก Inconsistent requirements of capitalize, lowercase etc in query syntax and elsewhere that even break some functionalities
๐ข Macros
๐ก Macros don’t work with most syntax, including Advanced Queries
๐ข Supports HTML and Hiccup syntax
๐ข Supports embedding Web pages using iframes
๐ข Sync is e2e encrypted
๐ด The code for e2e encryption can’t be audited because it is closed source
๐ก Tons of functionalities must be configured by editing a EDN file that it is very easy to break
๐ข Forum based on Discourse
๐ด Use (and abuse) of Discord, even release announcements are made there
๐ก Some Matrix bridges
Concept: 8/10
Execution: 5/10
CC @logseq
Given the points above and the fact I backed #Logseq for a long time but addressing these issues may require years and maybe the project won’t survive anyway that long, what should I do? Move to a simpler but better supported system like #Emacs or wait and hope Logseq team figure out priorities?
Recent “AI” (sigh) native integration in Logseq (using OpenAI according to a GitHub branch of theirs, again zero communication by the team) lower my hopes a lot.
If they take money from people they should make clear what it will be used for.
#Logseq team setup a Feature Request category in the official forum and users are prompted to vote FRs there.
For a long time the top ones are: epub annotations, vim shortcuts, longform writing, custom todo/done/doing keywords and filters for page content and not only references section.
All of these (except maybe vim shortcuts) perfectly align with what Logseq provided so far in my opinion.
I see no development on GitHub about these, the team develops privately, the only thing we have is an outdated Trello board that has never been respected nor actual new features are listed there. It looks like the board of a Logseq from a parallel universe.
But now I see an “AI” branch on GitHub by the founder and lead developer that it seems a deep integration of Logseq with OpenAI services. To my knowledge no one made a Feature Request for it. It looks like they are focusing on what they want or what they expect people to like, ignoring the feedback system they setup.
CC @logseq
@post @logseq I have to agree with you on the FRs. The way it is currently implemented does not work. This is especially as after using Logseq for a few years and being close to it, I am still unsure where exactly to post FRs (forum, GitHub, Discord, Twitter). On top of that as you mention, most top requests are not actually implemented - I understand it can be hard and very time-consuming, but I feel there should be a lot more communication from the devs.
There are different ways to integrate “AI” tech and using OpenAI services is not a privacy-oriented one though.
Logseq description on GitHub is:
“A privacy-first, open-source platform for knowledge management and collaboration”
On the other hand, OpenAI’s ChatGPT was blocked in Italy by the Italian authorities for severely violating privacy legislation and I don’t understand why other countries don’t follow.
There is the plugins platform for this kind of things and plugins using OpenAI are already available. The team shipping native integration with OpenAI out of nothing isn’t just a communication issue in my opinion.
@post @logseq
Agree. From what I understand the AI should be privacy orientated and local only - hopefully how will be made clearer