no, each nsite file is a single replaceable event with its "d" tag set to its absolute path. the nsite-manager just groups the files into folder to make it easier for humans to navigate
Discussion
Yeah, it's pretty cool. 🤙
I'll tag you for a review on our filesystem. Probably a technique you'd at least be interested in.
Could we use 30040s to index blossom files? I don't see why not.
Any event is already allowed for. If they're not events, we would just need some other UID to reference them.
What kind of filesystem are you working on? is it something using nostr events?
Yes. We're using 30040 indexes as folders and creating a scaffold for them, to gain full UNIX functionality, with drives and tracebacks and symlinks.
Every dir is just a file, after all.
Sound heavy, but if your able to get it to work that would be cool
nsite omits the folder because they are not necessary, the nsite events are focusted on showing the latest version of the site. So keeping history would make things slower and break more
Michael has been working on making trees more performant, and we actually need the folder-hierarchy view for #Alexandria, as an alternative for card-view, so it should be interesting.
We'll see, how it works, but a couple of other devs have been tinkering with the same concept, so the use case is there.
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr would be grateful for your feedback.