Nostr Web Client

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.

liminal 🦠 3w ago

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

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 3w ago

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.

liminal 🦠 3w ago

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

Silberengel 3w ago

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?

Silberengel 3w ago

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