Share by tag or regex

[aQuigs]

Would be useful to be able to share by some dimension that isn't a Folder. It'd help decouple my personal folder hierarchy from the shared use cases.

I could manually add all the folders but this is extra work and requires maintenance if I open a new folder elsewhere that I want to be saved

[dtkav]

hey @aQuigs -- thanks for the concept.

We've considered this a bit. A really important value for us is "Comfortably Private".
Basically we want a strong visual distinction that shows if something is shared or not.

I do think it would be possible to still have this distinction in the system you describe.

Do you think you could provide a bit more information about how your vault is laid out and how you'd like to collaborate? How would they organize the files on their machine?

[aQuigs]

Understandable, it's a good tenet. For some context, my vault is laid out such that projects can span multiple dirs. Something like:

/
    Config/
        FileClasses/ # MedataManager
            Project 1/
                ...
        <project 1 static data>
    Personal/
        My Project 1/
            ...
        My Project 2/
            Attachments to share/
            My Personal Instance/
            ... # Other dirs to share
    Work
        My Work Project 1/
            ...
    Templates/
        My Project 1/
            ...
        Project 2 Template.md

And I have multiple projects that I might choose to share with different groups at different times.

For example, to achieve use cases:

1. Share My Project 1:
   1. Move static data to its own dir
   2. Manually share 4 different dirs for each Relay
2. Share My Project 2:
   1. Share Attachments
   2. Move Project 2 Template to its own dir
   3. Share each Other dir explicitly
      1. Alternatively, move all dirs under a "to share" one, but this breaks down if I want different subsets in different relays.
         1. Not sure if that's really a valid use case, but in theory: if I wanted to share "production ready" version to one Relay for consumption and a "WIP" to another Relay for collaboration
   4. Remember to share any new dirs created under Project 2 in the future

It can be achieved today for the most part, but requires extra effort & some reorganizing for the sake of collaboration. I'd prefer to decouple my organization from implementation details of collaborators. I'm also trying to move away from folders moreso rely on tags

If I could tag each note or build some other pattern then the use cases are more implicit. It could be simply "share #project1" or "share notes with #project2 AND #experimental"

How would they organize the files on their machine?

That's an interesting question. Naive brainstorming options:

1. Mimic the structure from the source. Handle collisions somehow
2. Prompt for a "Relay folder" and mimic the source dir structure under there
3. Order them in a mode similar to the TagFolder plugin, although the heuristic might be tricky to get right
4. Maybe relays can be in "folder mode" or "tag mode" for ease of supporting simple and complex use cases without the workflows interfering with each other too much

[dtkav]

Thank you for the thorough explanation