Oddbean

Thanks, that makes sense. Question - do you think Amaya is way too complex for an average user and that's why it never took off? Could it be that the reason it's so complex is that it mixes data with representation? Html is all about how it looks, which can be infinitely detailed and complex, while people mostly care about data - those domain specific fields they fill.

Amaya didnt take off because it was a poor UX and there was no funding for it to compete along side the giant browsers. Exactly as you say, editing HTML is ok for geeks, but not for normies. The idea was for individual fields to be editable using HTTP PATCH, for example. With a marked up view. Remember this was 1994, so no ajax, bad tooling, barely even a DOM, no websockets. New standards had to be made for the editor to be useful too. What is needed is a way to edit, with user identity, such as with NIP98, so that you can control who has access. All of these things can now be achieved. That's what I hope to build with NosDAV, and, while still early, I think I've made quite a bit of progress. Also I would like to put the functionality back in the browser ... one day ... https://www.npmjs.com/package/worldwideweb

When you say that those things can now be achieved, which parts of nostr do you think would be used, aside from user identities and nip98? Relays, signed events, event kinds? Do you have a more detailed outline of the new architecture?

Yes, mainly taproot and schnorr for identity and signing, login, authetnication, encryption, payments etc. Keep relays, and add personal storage. I have some outlines in solid lite, and nosdav which will be the nostr oriented version, but more work is needed: https://solid-lite.org/ and https://nosdav.com/