| 22 Apr 2024 |
|  io joined the room. | 12:02:33 |
|  watchsky joined the room. | 12:43:54 |
|  weynhamz | 13:06:29 |
|  jordangarrison joined the room. | 14:58:43 |
|  w1nterl0ng joined the room. | 19:19:29 |
| 23 Apr 2024 |
|  daviddobbs joined the room. | 01:42:09 |
|  rheidter joined the room. | 09:58:57 |
|  necessaryillusions42 | 15:05:17 |
|  capfredf joined the room. | 15:28:31 |
| 24 Apr 2024 |
|  lizlizlou joined the room. | 01:04:45 |
 kiop2507 | There's almost no place for feedback on the Chinese channel, so I can only send it here | 03:58:34 |
| kiop2507 changed their display name from kiop to kiop2507. | 03:58:35 |
| kiop2507 | iOS doesn't sync well with the Mac, and it's very hard to sync only to find that the synced pages are null. No content on the Mac is synchronized
This has been a problem for years, and Logseq hasn't solved it. | 04:00:10 |
 .luhmann | The developers are working on a major refactoring of the app that will be based primarily on a database rather than flat files. This will take a few more months (at least) but should eventually solve the sync issues. It is a high priority for the developers because it will also be the basis for "real time collaboration" and publishing features which will be part of the new Logseq Pro paid tier which is central to their plans to become profitable. | 04:34:07 |
|  notablynoted changed their profile picture. | 06:15:20 |
| kiop2507 | What you expressed and what I said are two different things. Even synchronizing files via icloud should not have the above problem. Not losing files is the most basic ethic of an app. | 07:08:51 |
 Ramses | We do not support third-party sync tools like iCloud or Dropbox. As you've noticed, there are too many issues with it that are impossible to fix for our devs. They've tried, and it's a time and energy sync that's better spent working towards our own sync solution. That will also make Logseq a more sustainable project. | 10:08:19 |
| Ramses | We have Logseq Sync in beta, and while not perfect it works much better than iCloud with its quirks. I'm happy to give you a free extended trial if you privately message me the email address you'd like to use for your account.
https://blog.logseq.com/how-to-setup-and-use-logseq-sync/ | 10:09:27 |
| Ramses | * We do not support third-party sync tools like iCloud or Dropbox. As you've noticed, there are too many issues with it that are impossible to fix for our devs. They've tried, and it's a time and energy drain that's better spent working towards our own sync solution. That will also make Logseq a more sustainable project. | 10:09:45 |
|  addcool joined the room. | 15:21:34 |
| kiop2507 | Many other note taking programs that sync via iCloud don't have this problem. craft, simplenote, including Obsidian which is similar to Logseq. why is it that Logseq is the only one that can't be fixed? I also don't see the Obsidian team using statements like yours LAI to incentivize users to have to pay. You're not really paying attention to user feedback. It's clearly a bug. if it's not, according to you, it's a technical trick to incentivize users to pay which isn't very smart. | 16:21:57 |
| Ramses | Why the animosity? Logseq works different from the apps you mention, not only because it's an outliner tool and the others you mention are more like "regular" Markdown editors that work with a regular document structure.
When I say the the core devs looked into the issue, I mean it. They've tried for close to two years to make Logseq play nice with iCloud and other solutions, and it just didn't take with Logseq architecture. It's not simply a bug, it's an architectural decision that was taken early that complicates things.
This has nothing to do with tactics. It has to do with providing a good user experience. If you don't like the experience that Logseq offers, you're free to choose any other tool that you mentioned that supposedly works better. But please don't come barging in here with such negativity and making statements like "it's clearly a bug" when I tell you it's not. If you think it is, feel free to try to fix the issue—Logseq is open source after all. | 16:32:59 |
| Ramses | Plus, there are still other ways to Sync if you take the time to search in the Discord or forum (https://discuss.logseq.com). For example, lots of people have a great experience with SyncThing and Git. But asking things in a friendly way goes a long way, instead of immediately starting negatively with how the Chinese Discord isn't active or assuming things are malicious tactics when they are not and there's been a ton of conversations about it on both this Discord and the forum. | 16:39:19 |
 generalchaosdaemon | I would love to hear their schedule from them. Where did you get this estimate of "a few more months"? I'm coming here after participating on a reddit thread where people are not too happy about the stewardship of the app.
https://www.reddit.com/r/logseq/comments/1cc6jiz/the_logseq_team_is_a_terrible_steward_of_logseq/ | 23:54:19 |
| generalchaosdaemon | the animosity is related to the perceived underperformance and expectation management from the logseq development team. | 23:55:22 |
| generalchaosdaemon | * the animosity is related to the perceived underperformance and poor expectation management from the logseq development team. | 23:55:31 |
| .luhmann | There is no official timeline. It will be done when it is done. You can look at Github and see that the small dedicated team are working hard on this every day. I say a few more months because they haven't even started limited beta testing yet and once they do it will be at least a few months before something is ready for the general public. | 23:57:23 |
| generalchaosdaemon | do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? | 23:58:53 |
| 25 Apr 2024 |
| generalchaosdaemon | ok so this channel is feedback. Here's my feedback. I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. | 00:01:50 |
| .luhmann | There is one major task: the refactoring of the backend. After this big task is done they will likely go back to more incrimental updates. Before you jump ship I suggest looking at some of the previews of what will be possible after the refactor. You can jump to about 14 min in this video: https://www.youtube.com/watch?v=fRWwznJFkJM | 00:03:45 |
