Here is the njump version, if your wiki doesn't do Asciidoc.
Discussion
Very odd I was just thinking something similar
Yes, @Beave is on us to go ahead and expand it with public and private/encrypted options, but I want to check the basic scaffolding, first.
It's an interesting concept because you can, of course, share these virtual drives with other npubs, copy or fork drives, etc. And because you can replace everything in the scaffold, you can move events around, add-or-remove events, etc.
Should be nostr:npub1q6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqhtt3sh , sorry. Typo.
Notes starting off as a flat hierarchy, where they can be organized by tags and unique ids, and then imposing a tree hierarchy for specific contexts,
AND then you can distribute the files/text across relays and servers. One can always worry about larger files, but if you're just working with text (as many file are- code, notes, collaborative docs) you really can go far. Anything requiring larger files just points to a server location.
nostr:nprofile1qqsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgpramhxw309u6rxdpsd4skjm3wv36kx6mydeejummjvuargwp58qhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hsv0qvag what do you think? I know you are working on distributed file storage.
Hard to talk about specifics from this context, but I would say insure that the file storage expectations are set up to work well with content-addressable data.
We've only been thinking of git blobs and blossom objects, so far.. Did you have something else in mind?
I guess what I had in mind was "arbitrary data" lol. Like if it's content addressable and the remote source is still alive, whatever may be at that hash is what the data for that "file" is.
I would think this would allow for being backend-agnostic. As long as there are bytes to be received from that address, bytes ye will get.
But I am pretty green on your whole system here so there might be plenty of reasons that wouldn't work? (MIME types come to mind immediately)
Yeah, that's what we were also thinking. Anything addressable could be included, really.
30040/41 contain a MIME-Type tag, but we just use that to guide rendering.