Yeah I’ve been wrapping my head around the Obsidian philosophy of portability, and there’s lots of power that Obsidian, as a browser/viewer/sorter of files, could bring to the point that it’s questionable if a particular use is actually portable anymore and thus should be embedded/copied (whether explicit or hidden).
For example, if you use the tags & backlinks panel to source all kinds of info onto “Great Places” note. “Great Places” file may only have reflective/commentary text in it, but the backlink’s aggregation (and ideally ability to save/set filters in the future) is what is actually pulling in the “content” make’s “Great Places” what it is, a list of lines from other files. In order to future proof the “Great Places” file & retain the actual function it had in Obsidian a text copy/embed of the header (or line UID pluggin
of the files/line that are being viewed in the backlink panel may be necessary.
I’m not sure if that’s ideal, but it does seem like a nice workaround for allowing more “particular/risky” plugins that the user knows isn’t super portable, but at least some of the plugins “function” gets copied into your file as a backup.