Would a nostr filesystem (as a fuse) called nostrfs even make sense?
* Mounting a nostrfs would require having a private key hot, needed to sign every change.
* Mounting config would have to specify the relays.
* Creating a file would be equivalent to creating a note
* Directory tree could represent the tree of notes and their comments. Or it could be used to automatically specify tags or different event kinds (not sure what would be more useful).
* Deleting a file would delete a note
* Editing the file would delete the note and create a new one (until there is a NIP for note editing).
Why? Why not. Imagine using nostr by just using a file browser and and getting replies by seeing files appear.
sommerfeld
npub16r…kz5pl
2023-01-27 16:18:55
Author Public Key
npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5plSeen on
wss://relay.noswhere.comPublished at
2023-01-27 16:18:55Event JSON
{
"id": "7f15c67c77843e3849b76abeaf792a2e659dba67518a34fe354f21522416513b",
"pubkey": "d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c",
"created_at": 1674836335,
"kind": 1,
"tags": [],
"content": "Would a nostr filesystem (as a fuse) called nostrfs even make sense?\n\n* Mounting a nostrfs would require having a private key hot, needed to sign every change.\n* Mounting config would have to specify the relays.\n* Creating a file would be equivalent to creating a note\n* Directory tree could represent the tree of notes and their comments. Or it could be used to automatically specify tags or different event kinds (not sure what would be more useful).\n* Deleting a file would delete a note\n* Editing the file would delete the note and create a new one (until there is a NIP for note editing).\n\nWhy? Why not. Imagine using nostr by just using a file browser and and getting replies by seeing files appear.",
"sig": "5bf3b0718923f45f6467484d799d3b88df4daea27bebfcbccf2a8919dcd71c13d002dcd3dcaa4d3da1b665ab074831e37db5cb5f090f7e96c3773b68c47ea94c"
}