Do a Nostr client that saves each event as an individual file. Notifications is just a folder, sort by date and get your feed. Each feed is a folder. File thumbnail renders and previews the event. If the posts has images/media, cache those images inside the .media of each folder. Symbolic links everywhere. Then each event kind could open in a different preview client.

It's Nostr's own "file" explorer.

Reply to this note

Please Login to reply.

Discussion

I think there's some very potent brainstorming ahead. nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z would be very interested, as she's written a nostr directory system spec

nostr:nevent1qydhwumn8ghj7argv43kjarpv3jkctnwdaehgu339e3k7mgprdmhxue69uhhyetvv9ujuamfdd5kvun9v4jxjcfw0puh5qg6waehxw309ahhymre94ex2mrp0yhxjmthv9kxgtn9w5qzplpfyjyds3x2h6e5xeg9ywr25smzfhzatm9gt4qsmclpeaj4c300g9uqa6

This is different. There are no need for specs. All I want to see is the performance/ easy of use of a client that stores everything separately in disk, in the same way we do for images. And then users can see everything they want to keep or delete from a regular explorer.

Fair but my main point is Silberengel would likely be a good anchoring point for these ideas, spec or not.

An OS directory system is just a collection of hierarchical lists containing references to storage space.

What is the benefit of using the native one, rather than using one on a local relay, and the references pointing to events in the database? Performance?

Also, wouldn't that be a step backward? I thought OS are moving away from files and toward events...

What would I get if I told #shakespeare to actually create this?

No idea

Try it πŸ€·β€β™‚οΈ

Didn't nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp do that on nak? The filesystem relay thing.

Nobody uses it except nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw

Who do you think came up with it in the first place

Use copyparty as the explorer.

You can mount Nostr as a FUSE filesystem in NAK.

How would you work around platform limitations on number of file descriptors that can be open at once? Or the incredible amount of overhead that would require? Or the fact that symbolic links are not a thing on Windows?

IMO, a filesystem is not the right tool for the job, a database is.

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe como funciona o sistema de datas e horΓ‘rios nos posts do Nostr?

Eu sei que os usuΓ‘rios assinam as postagens pela chave privada e isso nΓ£o pode ser adulterado, mas e sobre a data e o horΓ‘rio?

Faz parte do mesmo, portanto nΓ£o pode ser alterado tbm