3 ms·
I would design it as a Web of Apps rather than the Web of Docs. Lots of current issues are because it started as a Web of Docs, yet what people wanted was the
by solus_factor 6y ago
I would design it as a Web of Apps rather than the Web of Docs.
Lots of current issues are because it started as a Web of Docs, yet what people wanted was the Web of Apps.
It would also be based on UDP rather than TCP.
There will be no cookies, Local Storage covers it.
Authentication based on public key cryptography.
Search similar to RSS, where each site provides an API feed, not bots scanning content.
And on and on it goes :-)
- avmich 6y ago> I would design it as a Web of Apps rather than the Web of Docs. These are two significantly different use cases. Maybe there are more? Like, apps can be split further into classes? > Lots of current issues are because it started as a Web of Docs, yet what people wanted was the Web of Apps. Disagree, lots of people today point out that the grass was greener when we had the Web of Docs, and want that state back. > It would also be based on UDP rather than TCP. TCP is just a rather common case - lots of cases want to have guarantees with data. We probably want to be able to use UDP as well, don't we go towards that with WebRTC? > There will be no cookies, Local Storage covers it. So it wouldn't work outside of the session? We'll need to keep entering passwords?.. I think some Internet things could be improved as well, not only Web.