Hacker News new | ask | show | jobs
by romaniv 3433 days ago
From the link:

>But if I try to revisit this later, it’s impossible. I can remember what I found, but it wasn’t a linear progression, therefore my browser history is useless.

If I want to find a page I visited more than three days ago, seeing a tree of history is not going to help me much more than seeing a linear list. There is just way too much information to sift through manually.

The obvious solution is to add full-text indexing by page content. And maybe even store pages for offline use. Perhaps when you enter special browsing mode akin to "private browsing" (although it would be the exact opposite, since it would retain more information).

I am aware of the complex issues this would require to solve, but those capabilities would qualitatively transform browsing and give users back some modicum of control over their page navigation. These days Google is our history. We remember a few keywords and instead of sifting through a giant list of URLs we simply search. Again, sifting through giant tree is not going to be any simpler. In fact, in terms of visual identification it might be more difficult than skimming a list.

...

Some simple machine learning algorithm that learns to bookmark and auto-tag pages would be an awesome feature/experiment as well.

...

And filtering open tabs by a keyword. Many people use tabs as a sort of dynamic set of bookmakers. Partly because they (sort of) preserve page content locally.

2 comments

> The obvious solution is to add full-text indexing by page content. And maybe even store pages for offline use.

I built something that did exactly this, over ten years ago! I was a much less capable developer then, and it never worked as well as I wanted, so it was never truly finished.

Today this would be even harder, with the prevalence of web pages that are actually _heavily_ dynamic apps. Navigation to a new "page" is a much fuzzier concept now. What gets indexed? How do I generally know what content is/is not addressable by URL?

> And filtering open tabs by a keyword.

https://support.mozilla.org/en-US/kb/awesome-bar-search-fire...

"Add % to search for matches in your currently open tabs."

>Today this would be even harder, with the prevalence of web pages that are actually _heavily_ dynamic apps. Navigation to a new "page" is a much fuzzier concept now. What gets indexed?

This kind of stuff is why I am an advocate of progressive enhancement. It's not about whether someone has JS disabled or not. It's about using HTML as a semantic representation of information rather than a mere rendering layer. The second option might seem more convenient at times, but the first one opens a lot more doors for innovation in the long run.

Some of what you describe here is on the table and we plan on sharing details on that in the followup posts.