Hu: Bookmarks is a massive feature in web-dev, as much as the browser–itself. Bookmarks is like a library, where the books are hyperlinks<Turing>. Personal-dash provides the organization layer, around this library, that provides the architecture that makes the storage of a large number of books possible.
H3S1: Internal-browsing enables 9^n complexity scaling:
Usage case-study: why is it important that links have different targets? The reason is that # in p-dash, links can either be external, opening some WebSockets docs, or internal, opening another dash-page, with more links. The internal links, I want, to open in the same tab. As an example, the API link #2 here, opens in the same tab, and into the page, in the second screen-cap: P.dash-pages are also layered, and the layers are quantified, so you can see that web-sockets is layer 3, and any internal from that, would be layer 4, and so forth. If 9 links per layer, then in 4 layers, 9^4=6,561, Being able to create my own dash, just for browsing WebSockets docs, which are distributed among both Mozilla, WhatWG, YouTube, and Wikipedia, will help me re-access them much faster, in the process of development, to the very specific pages I need, guided by the notes, and text titles, to find the specific paragraph, or code-line, in a way that simply bookmarking can’t. This is protocol-bookmarks<Turing>
