Nuh 🔻 on Nostr: I am happy to do that work if I have collaborators, but currently I only occasionally ...
I am happy to do that work if I have collaborators, but currently I only occasionally work on this in my free time, so so far I only have the vague goals that I shared and I also believe that beyond goals and principles, you can't predict how the thing will look or feel or evolve... you can only discover that as you build it.
But I also can paint a picture of a browser-like interface, where you have a filesystem and editors to encourage you to write and publish websites (think Obsidian), then bookmarks are used to enhance public keys with human readable names and maybe favicons, private contacts and bookmarks synced between devices but not public, not very confident in WoT but maybe worth trying, and then a "launcher" page whenever you create a new tab to see your most often used apps, and whenver you visit a website that detects it is running in this new web, it can ask for permissions which if granted it is considered "installed", the permissions management would be the most complex work.
You can't do stuff like Nostr with this system, but you can do anything you can imagine doing with Email and Google Drive if it was more open and interoperable, and if Email was as secure as Signal.
You can go to more extremes like writing all software including a Lightning node in wasm, since this web platform gives you both storage and networking unlike web browsers... but the only upside for that would be the free private storage logic and backup.
Honestly the platform should do three main jobs and everything else is extra;
1. Make key management manageable! Including your root identity, and encryption keys and keeping track of who is allowed to read what and who should receive new keys after revoking someone's access and how many devices have access to what etc.
2. Manage the relationship with your cloud providers, including mirrors, and deal with notifications if the provider needs more money or want to terminate your relationship, and when you need more storage or traffic, as well as backup so they don't rug pull your data.
3. Bookmarks, history and contacts lists to make keys usuable.
Sandboxing wasm apps can come later... it is enough at first to just give normal web apps permissions to read and write from and to some folders, and we can discuss if raw sockets should be allowed later.
This is a long way to say.. I think if this project has any chance it would be because of writing code and making prototypes not because whether or not we perfected a roadmap
But I also can paint a picture of a browser-like interface, where you have a filesystem and editors to encourage you to write and publish websites (think Obsidian), then bookmarks are used to enhance public keys with human readable names and maybe favicons, private contacts and bookmarks synced between devices but not public, not very confident in WoT but maybe worth trying, and then a "launcher" page whenever you create a new tab to see your most often used apps, and whenver you visit a website that detects it is running in this new web, it can ask for permissions which if granted it is considered "installed", the permissions management would be the most complex work.
You can't do stuff like Nostr with this system, but you can do anything you can imagine doing with Email and Google Drive if it was more open and interoperable, and if Email was as secure as Signal.
You can go to more extremes like writing all software including a Lightning node in wasm, since this web platform gives you both storage and networking unlike web browsers... but the only upside for that would be the free private storage logic and backup.
Honestly the platform should do three main jobs and everything else is extra;
1. Make key management manageable! Including your root identity, and encryption keys and keeping track of who is allowed to read what and who should receive new keys after revoking someone's access and how many devices have access to what etc.
2. Manage the relationship with your cloud providers, including mirrors, and deal with notifications if the provider needs more money or want to terminate your relationship, and when you need more storage or traffic, as well as backup so they don't rug pull your data.
3. Bookmarks, history and contacts lists to make keys usuable.
Sandboxing wasm apps can come later... it is enough at first to just give normal web apps permissions to read and write from and to some folders, and we can discuss if raw sockets should be allowed later.
This is a long way to say.. I think if this project has any chance it would be because of writing code and making prototypes not because whether or not we perfected a roadmap