3 ms·

>I will happily bookmark this and that, but it's unlikely I'll ever actually go back to the bookmark. That might be a problem with your process, not with your

>I will happily bookmark this and that, but it's unlikely I'll ever actually go back to the bookmark. That might be a problem with your process, not with your tools. >I wish a non-Google search engine would offer a bookmark manager that integrates into its everyday search, giving preferential treatment to previously-bookmarked material. Most browsers already do that with local bookmarks, to a degree. (they don't search the article contents, only the bookmark tags and titles).

jborichevskiy 7y ago
> Most browsers already do that with local bookmarks, to a degree. (they don't search the article contents, only the bookmark tags and titles). That’s a pretty big problem- the specific term I remember is rarely in the title or URL. Not to mention all the times I’ve returned to the same bookmark only to see the content have been deleted or the domain expired. Default bookmark managers in browsers are complete rubbish.
- yabadabadoes 7y ago
  It seems to me like you want an offline cache. How can something local deal with searching the content of a possibly deleted page?
  - jborichevskiy 7y ago
    Local cache would definitely be the (easiest) way of solving it. Tools like Memex [0] are most of the way there. But a text-only copy on my local device isn't great if the content had special formatting in presentation. Also, it misses out on images or embedded videos. That's where something like ArchiveBox [1] comes in. > ArchiveBox takes a list of website URLs you want to archive, and creates a local, static, browsable HTML clone of the content from those websites (it saves HTML, JS, media files, PDFs, images and more). But really what I'd like to see at some point is an opt-in community tool where every page I visit that fits a certain criteria (URL, topic, special mark by me, etc) is fully cloned and uploaded to IPFS [2] for anyone interested in that topic to find and use later - regardless of what happens to the source content. Definitely a host of legal issues around this, but not impossible. 0 - https://worldbrain.io/ https://worldbrain.io/ 1 - https://github.com/pirate/ArchiveBox https://github.com/pirate/ArchiveBox 2 - https://ipfs.io/ https://ipfs.io/
iamstartup 7y ago
>>I will happily bookmark this and that, but it's unlikely I'll ever actually go back to the bookmark. >That might be a problem with your process, not with your tools. Sure, great startups make problems your problems. Haha.
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").

jborichevskiy 7y ago

> Most browsers already do that with local bookmarks, to a degree. (they don't search the article contents, only the bookmark tags and titles). That’s a pretty big problem- the specific term I remember is rarely in the title or URL. Not to mention all the times I’ve returned to the same bookmark only to see the content have been deleted or the domain expired. Default bookmark managers in browsers are complete rubbish.

yabadabadoes 7y ago
It seems to me like you want an offline cache. How can something local deal with searching the content of a possibly deleted page?
- jborichevskiy 7y ago
  Local cache would definitely be the (easiest) way of solving it. Tools like Memex [0] are most of the way there. But a text-only copy on my local device isn't great if the content had special formatting in presentation. Also, it misses out on images or embedded videos. That's where something like ArchiveBox [1] comes in. > ArchiveBox takes a list of website URLs you want to archive, and creates a local, static, browsable HTML clone of the content from those websites (it saves HTML, JS, media files, PDFs, images and more). But really what I'd like to see at some point is an opt-in community tool where every page I visit that fits a certain criteria (URL, topic, special mark by me, etc) is fully cloned and uploaded to IPFS [2] for anyone interested in that topic to find and use later - regardless of what happens to the source content. Definitely a host of legal issues around this, but not impossible. 0 - https://worldbrain.io/ https://worldbrain.io/ 1 - https://github.com/pirate/ArchiveBox https://github.com/pirate/ArchiveBox 2 - https://ipfs.io/ https://ipfs.io/

iamstartup 7y ago

>>I will happily bookmark this and that, but it's unlikely I'll ever actually go back to the bookmark. >That might be a problem with your process, not with your tools. Sure, great startups make problems your problems. Haha.

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").