I value your feedback on my proposal @WhiteNoise, however, I believe there’s a need to rethink how Obsidian handles text and related assets.
My proposal, titled “Future-proofing Obsidian: Proposal for a TextBundle-oriented Asset Management”, focused not on TextBundles themselves, but the “TextBundle philosophy” - the view of a note as a mix of text and other assets.
Notes in Obsidian are often a blend of text and images, losing significant context without their assets. The markdown-only approach future-proofs the text but leaves the whole note (text + assets) vulnerable.
I must express my disappointment at the swift merging of my request with an unrelated topic. A feature request is a conversation starter, an inquiry: “Do others share this need?” It doesn’t call for immediate implementation.
Additionally, maintaining visibility of a feature request, even if initially perceived as irrelevant, fosters open dialogue without incurring costs or harm. Before removing a user’s contribution from the feature request section and relegating it to an unrelated “plugin idea”, initiating a discussion and seeking clarification could be a more respectful and productive approach.
Given this, I propose we refocus my original request on “future-proofing the link between assets and text”. This would allow developers to explore a range of solutions that address this core issue.
Thank you for your consideration.