How could would a Nostr-HTML be?
You can verify this html, CSS, and JS scripts were signed by the author.
Discussion
can you give an explanation or reference to what eventID1 eventnID2 are?
Just other event types posted by the same author (or other authors).
Like this:
nevent1qqs298a5ywpqwksf3s7fnywdsffvrrsar6rd3j62sg59qhrku0gxxrsprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7w2xrln
Adding a nostr sig to every HTTP response would be interesting, even if not served by a relay
How could would a Nostr-HTML be?
<>
Why not standardize protocol "nostr://"?
Brave browser already supports several decentralized protocols, e.g. "ipfs://".
Sure, go for it.
I'm toy implementing a nostr based "browser", but I like the idea of keeping it based on markdown to give the rendering power to the person using it.
Markdown sucks, though. There are so many variants...
we should make a new one that brings in the best pieces of the different flavors.
Go for it.
Don't tell anyone, but...
Got this response from SimpleX devs a while back:
“we might need to develop another browser with integrated support of simplex messaging - it might be a better path than providing a general purpose browser integration that actually undermines the security. Browsers seem as ripe for disruption, tbh, as messengers are, but we won't go there sooner than in 2026”
