Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

The key connecting element of a lot of the examples of "Memex" is the web platform - http, html, css, js, etc. - and that it is both a document and app delivery system. That is the secret that has made it work. All the examples of file sharing still have a http interface to connect to.

As he touches on, the missing, or a least somewhat disjointed, element is local data and connecting to that from other web destinations. My hope, and belief, is that we are breaking down those local <-> server barriers with newer JS APIs for better file like local storage.

It's just a pity in a way that the web browser and web server were not combined into one element from the start. It's still too hard to make content available on the network from your personal device without a server.

His conclusion about the need to cognitively organise such trails/collections though could well change in the coming years - and potentially sooner. It's clear the LLMs are good at organising and summarising text and data. I'm expecting us to be using tools that will ingest all our work activity (documents, meeting, email, calls, browsing) and automatically curate and file it with a chat based ui to extract that data. We just desperately need that to be local and not server based.



Didn’t Netscape Navigator have a server included? And an email client and an HTML Editor?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: