Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
11–20 of 33 posts
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#12Earlier quoted context omitted.
alway wonder why browsers don't keep at least a text version of the pages for search nowadays I expect browsers to incorporate small LLMs like Mistral out of the box
if history search worked better then you would visit google/bing less, so I expect pushback from browser vendors also: https://bugs.chromium.org/p/chromium/issues/detail?id=297648
> Shouldn't this be left to users to decide whether they want a feature or not.
Yes, those were good times. Nowadays, it's anathema to software vendors, and increasingly even to open source devs.
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#13Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#14Thank you. I really needed it.
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#15Earlier quoted context omitted.
What are those simple use cases, and where do you see Retrieval Augmented Generation fall over?
I think it works better if query is a larger chunk of text. Like, if you have an email from a customer and want to compose a response based on some relevant documentation, it should work well. But for a use case where you want to retrieve something from browsing history you would mainly use a short search query, just few words. in this case embeddings are too ambiguous and relevance of retrieved content is not great.
You’re right in saying there’s not enough semantic meaning in the text of the query. The domain of queries and the domain of documents are very different. That’s why a real retrieval system will train the query encoder and doc encoder to be closer in their embedding space using click data. This is what Google is doing.
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#16Earlier quoted context omitted.
alway wonder why browsers don't keep at least a text version of the pages for search nowadays I expect browsers to incorporate small LLMs like Mistral out of the box
if history search worked better then you would visit google/bing less, so I expect pushback from browser vendors also: https://bugs.chromium.org/p/chromium/issues/detail?id=297648
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#17Earlier quoted context omitted.
I think it works better if query is a larger chunk of text. Like, if you have an email from a customer and want to compose a response based on some relevant documentation, it should work well. But for a use case where you want to retrieve something from browsing history you would mainly use a short search query, just few words. in this case embeddings are too ambiguous and relevance of retrieved content is not great.
That’s not a problem with RAG itself that’s an issue with your retriever. In the original RAG paper they used two vanilla BERT models and cosine similarity but there’s no requirement you do that. Use any retriever that gets you high precision. Use BM25 if you want, it’s simple and cheap. You’re right in saying there’s not enough semantic meaning in the text of the query. The domain of queries and the domain of docume…
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#18Earlier quoted context omitted.
That’s not a problem with RAG itself that’s an issue with your retriever. In the original RAG paper they used two vanilla BERT models and cosine similarity but there’s no requirement you do that. Use any retriever that gets you high precision. Use BM25 if you want, it’s simple and cheap. You’re right in saying there’s not enough semantic meaning in the text of the query. The domain of queries and the domain of docume…
"train the query encoder and doc encoder to be closer in their embedding space using click data" <- Any papers/resources you know where I can learn more about this process?
https://pytorch.org/docs/stable/generated/torch.nn.TripletMa...
Triplet loss takes an anchor, positive, and negative. In this case the anchor is your query, the positive is a similar doc, and the negative is a dissimilar doc. When you train, backpropagate the loss to both the doc and the query encoder.
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#19I had an issue with my bookmarks where I used chrome for about a decade and then one fateful day, I allowed Microsoft edge to try to clone my bookmarks. It corrupted everything. Now I have hundreds of copies of duplicated folders and links. It would be great if this or another tool could help get it restored.
Re: Show HN: Autolicious – AI-powered bookmark cataloging Chrome extension
#20I had an issue with my bookmarks where I used chrome for about a decade and then one fateful day, I allowed Microsoft edge to try to clone my bookmarks. It corrupted everything. Now I have hundreds of copies of duplicated folders and links. It would be great if this or another tool could help get it restored.
While you're at it, I'd recommend to consider uploading the new bookmarks to a dedicated bookmark manager and avoid having the browser manage your bookmarks. For folks who rely on bookmarks, dedicated bookmark managers offer great value (eg. auto-archiving a copy of every bookmark to combat link rot). I currently use Raindrop, but if I were to start fresh I'd go with Linkwarden instead.