My "vision" for this is: I read this whole book a bunch of months ago:

Hypermedia: A Reintroduction

, haven't re-read it yet, but it wormed its way into my mind. (and these notes happened around the same time: ) I think hypermedia is a really promising way to potentially get super powerful clients with very minimal client-side code. that concept + the ability for nostr events to be arbitrarily complex has been stewing in my head as a way to get super malleable* UIs and applications. I don't know where this goes yet, or if it has any legs, but it seemed like a basic feed client was the first step. (might be wrongheaded, perhaps a much weirder, non-social client would be a better proving ground, dunno). All that to say: it's just a lot of random ideas banging together and I doubt any experiments or suggestions would overstep, since I don't yet have clear boundaries to begin with :) maybe a few guidelines would be: - keep events nostr protocol and relay compatible - adhere to hypermedia principles (I may be guilty of breaking this myself, haven't thoroughly reviewed) - try to do as little as possible on the server side aside from just massaging and re-forming stuff for hypermedia-style presentation - - ideally we minimize the footprint for distrust on the server. someone should be able to self-host it easily. and ideally we could host it simply in a secure enclave with cryptographic attestation to prove that there's no censorship or funny business happening on the server. but i'm digressing far here... - I don't know, making it up as I go along here --- * At some point I should explain what I mean by "malleable". but briefly: infinitely changeable and re-configurable by the user, no hard edges, amenable to being coaxed to inter-operate with other things at the user's direction, etc. etc. in a word: "purely ownable, in an end-user way"