How does Colanode manage conflict resolution between local and server data when syncing after offline edits, especially for structured databases and pages powered by Yjs?
Show HN: Colanode, open-source and local-first Slack and Notion alternative
51–55 of 55 posts
Re: Show HN: Colanode, open-source and local-first Slack and Notion alternative
#52These products are neat, but what about the data? Notion is a tragedy when it comes to export or migration. I didn’t see any bragging about the exportability of content from this one, but that’s the main thing I look for now.
Hi, thanks for bringing this up! We don’t have export or migration features in place yet, but we are planning to add them. Which export formats would be most useful to you? And when you mention migration, are you thinking about moving data from similar tools into Colanode or vice-versa? If so, which specific tools would you like to be able to migrate to/from?
You have to offer export consistent with your import tools or you demonstrate lock in by design.
This gets around version drift with binary export formats.
Static export, as PDF or other non-native markup format is not what is required. This is hard copy, not backup.
Re: Show HN: Colanode, open-source and local-first Slack and Notion alternative
#53[dead]
Re: Show HN: Colanode, open-source and local-first Slack and Notion alternative
#54[dead]
Re: Show HN: Colanode, open-source and local-first Slack and Notion alternative
#55[dead]