Yep, but that is just exposing events from nostr relays. It's not the website itself. It's just a way to go around the fact that browsers don't resolve nostr:<ID> yet.
Login to reply
Replies (6)
Agreed.
...yet.
View quoted note →
Impervious.ai has been going this route with forking a browser, might be the simplest way to have it implemented: an existing product still early in development
And also open source of course, but I'm sure they'd be very into integrating nostr
Why a browser? Why couldn't the web server stitch all the content together on-the-fly and serve it like any other static content?
Because we shouldn't even need a centralized webserver.