I actually originally put this on #Alexandria, using 30040s as folders, but it seemed sort of redundant with the ToC, and I need folders where the order of the content isn't essential.
And then I got to thinking about nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q and his notes, and it was like... where to put the notes, tho? Cuz like, if you hang the 30041s directly on the npub, then it's great because it's "my notes", right? And then you could go look at them from the note viewer. So, I built that.
And then nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf was like, but what if he wants to use something other than 30041s to take notes with? And how does he organize the notes? Then we need 30040s, but then his folder of notes ends up on Alexandria, as if it were a publication. But publications are meant to be _curated_ and this is just "my notes", all lumped together in cyberspace.
And what if he wants to share a folder with someone else? Then it's really stupid. He should be able to have n number of folders and share them, so the folders should originate from himself; they should be independent things, with only his signature on them. But how do you figure out the top folder? You have to mount the top folder on top of something, but we have no distinct hardware to mount on. So, let's mount on an event.
So, that's where I'm at, now.
To be clear on my actual needs (which might be simpler than what you describe, I don't know).
- Write Stuff
- Label Stuff
- Index Stuff together in a publication that I can share / publish
- Target Stuff to Communities (which are pubkeys and which can be private)
- Collab on Stuff
I personally don't need the in between "folder" thing.
Either I need Labels (categorization) or I need an Index (ordered, coherent whole).
This gives you an index to put lots of different stuff in, while you work on it, and then you can select items from the index to put them together into a publication. And the index can be flat and monolithic, like "My Notes" and you just throw everything into one big index/folder/directory, or they can be organized into multiple indexes on one level, or they can be nested, so that you can group similar things together.
Or, you can put them straight into a publication, but that already exists. And then it shows up in every curated publication feed, as if it were a coherent, curated document with a predetermined order.
I have hashtags and kind 1985 labels implemented. Other labeling could be added.
The drives have the visibility "public" (published to all relays you have access to) or "protected" (published to one relay and containing a "-" tag. A "private" visibility could be added, later, with encryption, but that makes collaboration more difficult and for now I'm just leaving events unsigned and saved to the local db (so that you can continue to edit them), and you have to sign-and-publish, to make them visible to someone not using your machine. So, there's a deliberate "send it out" step, that is separate from the "write it down" step. The way Obsidian Nostr plugins work, basically, but Nostr-native.
No multisig on the events, but you can add any event to any index, even if it isn't your event, and people can clone/fork your index and then edit that and submit a change back to you, to update yours.
It's more, than you asked for, but I was going to build it, anyway, so here it is.
You can also define multiple drives, and have one "public" and one "protected", and choose which one you share with whom.
I allow for categorization, grouping, a hierarchy, and differentiating visibility, but displaying this in a file explorer. Feels much more intuitive.
And I have a search, filters, and sorting, for all levels or for the entire explorer.
One event could be in multiple folders on different drives, so you could see where all you put one event.
And an event can literally be anything. This isn't only kind 30041. You could have a folder of your favorite emojis, or cool kind 20 images, or citation events to scientific journals or web pages, or something. That's why I went ahead and added the citations. Scientists and engineers like to keep track of things they've seen, elsewhere, or good AI prompts they've used, so that they can use those as references, later.
