Will logseq sync be open source?

Questions & Help
1

There was some discussion about this question with Tienson on Discord, and I thought it would be good to share a summary of that conversation here.

  1. Logseq MD relies on RSAPI for sync. This is open source.

  2. Logseq DB will rely on the new RTC implementation for sync. This will not be open source. The reason given is a lack of resources to support self-hosting and customizations of the code.

  3. Third party sync solutions will be allowed, but it may be difficult. People would need to sync the sqlite database, which can be done with Git (there is built-in support for Git with sqlite). But some advanced sync features may not be supported with this method.

  4. To ensure trust and safety, the team will invite people to audit the code. Also, RTC will support e2ee so no sensitive information will be sent to the Logseq servers.

6 Likes
2

What advanced sync features might not be supported? As long as I have an independent means of syncing my private digital diary I’m fine.

1 Like
3

Perhaps collaboration, in the future

4

This is so sad, I wanted to pay for sync in the future but i will never pay for a proprietary software :frowning:

2 Likes
5

I think it’s easier to link to the conversation in Discord, as this was discussed. According to @tienson:

Although people can still use Git or other tools to sync the sqlite file between multiple devices, RTC handles the conflicts automatically, with Git or other tools such as Dropbox, you need resolve conflicts in some situations.

1 Like
6

I can’t help but think ElectricSQL is perfect for this, literally made to sync sqlite to a remote postgres (and the opposite)

2 Likes
7

Is Logseq MD going to continue to be developed? Admittedly, it’s been awhile since I looked for any updates about this. Things like PDF reading on the Android app would be a game changer for me, but I already knew I won’t be switching to the DB version, and this bolsters that decision.

I’m wondering both if the existing team will continue working on the MD version at all, but also if any efforts are coalescing around some people taking responsibility for development of the MD version as a fork.

2 Likes
8

Yes, they will soon be merging the MD and DB versions into a single desktop app which will bring a lot of the bug fixes from the DB version over to the MD version as well. (You will have the choice for each new graph as to whether you want it to use MD or DB.)

This means that the MD version will continue to get updates since it will be the same core app. The core app will also continue to be open source and free. It is just the paid sync solution which will be closed.

3 Likes
9

Do you know where/if there’s a list of the features from the DB version branch that will be available in the MD version?
I suspect due to speed/querying requirements that there won’t be perfect 1:1 feature parity, though I’d be curious to see what’s been “backported.”

1 Like
10

Best to open up a new thread for that question.

11

I am paying for sync. Not because I use it much but I figured it was a good way to say thanks and support development.

But the whole reason why I was using Logseq and not Obsidian or something else was because it was open source and I could always self host.

With those advantages going out the window and the whole communication situation I think I might just as well switch to Obsidian.

2 Likes
12

I’m in a similar place. I’ve made several years of monthly donations to support their efforts while the product languished, initially with very little explanation. I’m very disappointed by this shift.

2 Likes