I see a lot of feature requests for Logseq to emulate some Obsidian feature. I get that these products are similar, but they are also different. I like that Obsidian appears to be built atop a plugin architecture where everything, even the core, is a plugin. I like that because it means I can opt out of a lot of cruft I don’t want (e.g. Zotero) but which is integrated into Logseq by default.
Other than that, I don’t like the idea of Logseq becoming more like Obsidian. I like the Logseq user experience better than Obsidian, at this point. So the notion of Logseq doing Obsidian is lost on me.
Now if the Obsidian must-haves are nothing more than plugins, that’s great because that doesn’t impose one person’s view (Obsidian does X better) on the whole community. And if Logseq makes plugins a centerpiece to its design then lots of Obsidian-like things can be supported via plugins.
As far as collaboration goes, I am sure Obsidian and Logseq are cross pollinating but I see no way around having to rewrite features/plugins for both. Basically, all this request amounts to is configurability. Let users choose what things to configure to be more like Obsidian and, with plugins, that’s possible.