Thread - Nostr Hypermedia

I agree. But I think we need a filesystem-like API for writing path-value pairs and listing directories. Something like gundb

GitHub

GitHub - amark/gun: An open source cybersecurity protocol for syncing decentralized graph data.

An open source cybersecurity protocol for syncing decentralized graph data. - amark/gun

Nostr is not going to work as a universal data layer if every list (directory) update overwrites the previous list and every new application needs to define its own event kinds that relays may need to integrate.

↑ Parent

Replies (5)

brugeman artur@nostr.band 2 years ago

Well I didn't mean that you should write all internal app state to nostr, just the high level stuff that needs interoperability and discovery. And relays usually support new event kinds out of the box, that is the whole point of them.

petri _@petrikajander.com 2 years ago

Would this help? View quoted note →

Vitor Pamplona _@vitorpamplona.com 2 years ago

Basically NIP 78. Apps should use 30078 for key-valye storage in tags.

GitHub

nips/78.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

1 replies ↓

El Gorila 🇦🇷 agustin@primal.net 2 years ago

we fix this with

Welcome to – Nextra

Nextra: the next docs builder

npub1hmy7...wap5 2 years ago

I told you humans would fuck up a good thing. Siri’s the virus and a high five. Listen it’s going sideways