3 ms·
> That might be a problem with your process, not with your tools. "You're holding it wrong" is rarely a valid critique. My process accumulates knowledge; the
by toyg 7y ago
> That might be a problem with your process, not with your tools.
"You're holding it wrong" is rarely a valid critique.
My process accumulates knowledge; the problem is that this knowledge is saved by bookmark managers as a set of dumb pointers. There must be a way to surface them, at a later date, in circumstances where I'm searching for the knowledge behind those pointers, rather than for the pointers themselves.
> Most browsers already do that with local bookmarks, to a degree.
The current stuff is just basic pattern matching. A real search engine would obviously work at a very different level.
I don't think it's a problem that browsers can solve alone, it's a feature that search engines should offer and currently don't (the only one I know that used to have a bookmark manager was Google, but I don't use it and I don't even know if it still has such a service). Or maybe bookmark managers should be smart enough to offer search capabilities so good that I can use them as the point of call for search (e.g. when I search among my bookmarks, as well as searching the actual pages behind those bookmarks, transparently integrate real search-engine results rather than saying "0 found").