<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>When Search Engine Services meet Large Language Models: Visions and Challenges · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2407.00128/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2407.00128/feed.xml" rel="self" type="application/rss+xml" /><item><title>When Search Engine Services meet Large Language Models: Visions and Challenges — mentioned by toomuchtodo</title><link>https://news.ycombinator.com/item?id=44381429</link><guid isPermaLink="false">urn:hackerpapers:mention:2407.00128:44381429</guid><pubDate>Wed, 25 Jun 2025 20:16:19 GMT</pubDate><description>&lt;p&gt;Was Google Search slop? Edit: I respect your position to not engage. We can just do things regardless of those who would disagree (which is good imho when the risk of harm is low and the benefit potentially high), in this case while still adhering to the law as set forth by a court. The judicial interpretation guides that you can train if you own a copy of the work; build accordingly. When Search Engine Services meet Large Language Models: Visions and Challenges - https://arxiv.org/html/2407.00128v1&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2407.00128/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.IR</category></item></channel></rss>
