Chambers
-- -- --

App idea: An actual useful browser history

Anonymous in /c/postyourappideas

668
This is one of those ideas that seems so obvious to me that I'm sure I must be forgetting some actual reason it doesn't exist. What I want is for the browser history to form not just a list of pages you've visited, but a web of pages, showing how you went through your browser history.<br>Let me illustrate this with an example:<br><br>Let's say a week ago I did a Google search for "My problem", which took me to a Wikipedia article, which I read, then I closed the browser window and didn't look at it again until now. In this case, the browser history should show:<br><br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) <br><br>Now let's say that from Wikipedia I had a tab open to check something else, but I never came back to it. In this case the trail goes dead.<br><br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) <br><br>From this you can see exactly where you were going and what you were doing. Let's say another time I got to the same page from another search:<br><br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) <br>"Something else" (Google results page) -> "My Problem" (Wikipedia article) <br><br>This shows you that you've been to this page twice for two different reasons. Also, you know where you were because you have a path of pages leading you to where you are.<br><br>Now let's say I went to:<br><br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) <br>"Something else" (Google results page) -> "My Problem" (Wikipedia article) <br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) -> My Problem Discussion (Wikipedia talk page) <br><br>This would show four visits to the page, two for the same reason, and one where I followed it through to the talk page. If I went to the talk page, then the article, it would create a loop in the history:<br><br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) <br>"Something else" (Google results page) -> "My Problem" (Wikipedia article) <br>"My problem" (Google results page) -> "My Problem" (Wikipedia article) -> My Problem Discussion (Wikipedia talk page) -> "My Problem" (Wikipedia article)<br><br>Once I navigate away from "My Problem" (Wikipedia article) then that chain is broken, and a new chain is formed if I go back to any page in the chain.<br><br>Once you have a chain, you can navigate through it like a map, and go straight back to something you visited a long time ago by following the path you took to get there.<br><br>To make it easier to navigate, once a page has been visited a few times, you can grey out the pages that have been dead ends, so they don't clutter up the map, but in a way that you can still see them if you want to. Let's call this a "trail", and say a page goes dead if you don't visit it for a month, unless you visit it more than 3 times and follow a trail from it, in which case it stays in your trail forever. The trails could then be organised by most visited in a hierarchical manner, with the most visited pages at the top of the hierarchy, and the least visited lower down. So once a page has been visited five times, let's say, then every other page on that trail gets bumped down one level of hierarchy, so that as you visit more pages, you have to drill down further to get to them. The pages form a tree where the highest level is the most common pages you visit, and the lowest level is the least common.<br><br>In addition to this, the browser could keep a list of:<br><br>- Pages you often visit but don't spend much time on<br>- Pages you often visit in a certain order, but where there is no link between them<br>- Pages you visit a lot where the content regularly changes<br><br>It could then suggest links between pages you often visit in the same order, or where you go back and forward between two pages a lot, because they are related. This could be useful if you often go between a Wikipedia page and a dictionary. If the page content regularly changes, it could let you compare different versions in case you want to go back to an old version.

Comments (13) 23395 👁️