First an apology for going silent in this thread for a while. I’ve had a lot going on in my personal life, including some family health issues (everyone is OK, just things to work through!). But I remain very interested in this idea and hopeful that an actual sync/integration plugin could be developed in time.
For me this would be one of the principle reasons to integrate with Obsidian. I think it’s clear at this point that Fibery will probably never have the vibrancy of development community that Obsidian does, and that’s OK. It would be even more “OK” though if we could have at least some access to all the capability in those plugins, while also taking advantage of what Fibery has to offer (which I agree is generally better than Obsidian in many respects).
- Offline and local access to my core data (text, markdown, hopefully structured data too, i.e. databases, although this seems much harder to sync properly)
- Use of Obsidian’s advanced text editing environment, customizable hotkeys, etc.
- Alternate and powerful views and UI affordances for working with text, e.g. Tabs, flexible Panes, Themes, and perhaps one of my biggest motivators: Canvas view
- Since this one is important enough, I’ll repeat it as its own point: Canvas View. Because of its importance to me, and what I think it represents, I’ll elaborate further on it separately below.
- Ability to leverage local tools to operate on my content/data (making an Obsidian sync inherently creates a local archive of markdown files that can be manipulated by any local or even cloud tool, provided it connects to Obsidian, and which then syncs legibly back into Obsidian)
- Ability to utilize any number of mobile markdown/Obsidian apps for a far superior mobile experience, especially for the kind of quick note-taking, list management (e.g. shopping list), etc. that I mostly want for mobile (and which is fairly horrible with Fibery at the moment)
- Access to the development community and all Obsidian plugins (since almost all Obsidian plugins fundamentally operate on markdown content, their manipulations/functions are mostly codified in a way that could be synced into Fibery legibly)
So about Canvas View: to me this is an (unfortunately) far superior “Whiteboard” function that sprang from nowhere in Obsidian and already does the most important knowledge organization things better than Fibery (for the most part), including embedding full contents of notes/docs, better and smoother visual connections, frames, embedding active websites, and more. Honestly this one feature was one of the most motivating things for me to want a sync and I started using Obsidian exclusively for tracking my personal therapy work due to the ability to create visual maps of my “Parts” (IFS therapy model), but it is equally if not more powerful and applicable to many business cases.
I’ve tried to use the Fibery whiteboard for similar things in the past and it’s just too buggy, inconsistent, and inadequate. And unfortunately it does not appear to be getting much development focus for the moment, understandably given the many competing priorities, but this just gets right back to the main point: Fibery team can’t and won’t “do it all”, but what if they don’t have to? What if we can reliably sync and in general operate compatibly on the same content with another tool that massively expands Fibery’s accessible functionality? Then the Fibery devs don’t have to do everything.
Imagine if the Obsidian ↔ Fibery sync plugin had existed already a year ago. Then all of the cool AI tools that immediately sprung up (some within days or a mere week of ChatGPT API availability) could have been usable on Fibery content from the moment that plugin became available. Likewise as soon as Canvas became available I could start my IFS mapping, but those docs/pages that I created in Obsidian would also be available in Fibery right away, and I could link to and search on them for other purposes for which Fibery is better, while still maintaining the advantages of Obsidian’s Canvas.
I also hope that such a direct and well-developed sync could actually make Fibery the de facto/default “other” tool that Obsidian users turn to and become comfortable with when Obsidian alone doesn’t do all they need. Right now this is Notion mostly, and a few others. What if it were Fibery? The massive and popular Obsidian community could actually help popularize Fibery for individual PKM use cases, which could in turn make Fibery more popular overall (just as personal Notion use seems to have translated heavily into organizational use).
In short, this whole idea is - to me - fairly significant in its potential impact, and I think to a degree it should be considered with a little distance from the fact that it would be syncing with one specific tool (Obsidian). If you think of it more like a local backup and interop system which allows you to reliably operate on Fibery content with any number of other Markdown-compatible tools, both offline and online, then it gets closer to the hoped-for reality and potential impact. It just happens to be enabled by working through Obsidian, which makes sense because it’s a mature, robust, and popular tool, with a good API, and strong development community. So while a true stand-alone local markdown sync tool for Fibery could be made, I think it makes more sense to leverage the Obsidian advantages (given it is free anyway), speeding up development and popularity/reach with minimal downsides. Even if the only reason to make it sync with Obsidian was to be able to access that community, it’s reason enough: a Fibery-only local sync would only be of real interest to existing Fibery customers, whereas an Obsidian plugin that syncs directly and reliably with a powerful, collaborative cloud dev/proj management and database tool would potentially be of great interest to many Obsidians, i.e. expanding Fibery’s market. We just need a developer or two to take on the creation of the plugin…
Fantastic, thank you! Because of your interest and that of a few others (including myself), I am strongly considering setting up an OpenCollective for this project. That would allow us to safely contribute money to it in a way that is quantifiable and can be clearly and reliably demonstrated to any potentially interested developer(s) (as opposed to the more nebulous - though greatly appreciated - pledges of support here). Is that something you would consider supporting, even with just an initial contribution of say $100 or something?
You’re probably right, but why wait? 
In a distant future I’m hopeful that Fibery will encompass everything I need/want Obsidian for right now, and implement it all in a superior way. But realistically that’s probably not going to happen, and even if it does, in the meantime I have to make do with a lot of limitations vs. my needs. An Obsidian sync plugin could, I think, solve a lot of challenges in the short-medium term. Maybe we can even get Fibery team itself to contribute a little toward the effort? 
