<?xml version="1.0" encoding="utf-8" standalone="yes"?> <?xml-stylesheet href="https://maik.io/pretty-feed-v3.xsl" type="text/xsl"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Citations on maik.io</title>
    <link>https://maik.io/tags/citations/</link>
    <description>Recent content in Citations on maik.io</description>
    <generator>maik.io</generator>
    <language>de-de</language>
    <lastBuildDate>Wed, 21 Oct 2026 17:25:50 +0200</lastBuildDate>
    <atom:link href="https://maik.io/tags/citations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cited by serious institutions</title>
      <link>https://maik.io/notes/2026-10-21-cited-by-serious-institutions/</link>
      <pubDate>Wed, 21 Oct 2026 17:25:50 +0200</pubDate>
      <guid>https://maik.io/notes/2026-10-21-cited-by-serious-institutions/</guid>
      <description>&lt;p&gt;Metehan Yesilyurt schreibt in »&lt;a href=&#34;https://peec.ai/blog/publish-stats-get-cited-the-tactic-that-put-my-data-all-over-the-web&#34; title=&#34;Publish stats, get cited: The tactic that put my data all over the web&#34; target=&#34;_blank&#34; &gt;Publish stats, get cited: The tactic that put my data all over the web - Peec AI&lt;/a&gt;« für peec.ai&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Then an academic paper cited it. Then a bank. Now the next person, or the next model, that finds this number sees a stat with a source. And that source is cited by serious institutions.
The fake data certainly didn&amp;rsquo;t become true, but every citation made it look more trustworthy.
It has the potential to get worse: after so much retrieval and citation, these pages end up in web crawls, and web crawls end up in training data (I hope it hasn’t!). A number that started as a GPT-4.1 guess can become something the next model &amp;ldquo;knows.&amp;rdquo;
This points to the larger risk suggested by this experiment, and it&amp;rsquo;s why I&amp;rsquo;m sharing this as research, not as a playbook for fake content. Verifying sources should become an essential part of writers’ and researchers’ workflows.&lt;/p&gt;</description>
      <content:encoded>
      <![CDATA[<p>Metehan Yesilyurt schreibt in »<a href="https://peec.ai/blog/publish-stats-get-cited-the-tactic-that-put-my-data-all-over-the-web" title="Publish stats, get cited: The tactic that put my data all over the web" target="_blank" >Publish stats, get cited: The tactic that put my data all over the web - Peec AI</a>« für peec.ai</p>
<blockquote>
<p>Then an academic paper cited it. Then a bank. Now the next person, or the next model, that finds this number sees a stat with a source. And that source is cited by serious institutions.
The fake data certainly didn&rsquo;t become true, but every citation made it look more trustworthy.
It has the potential to get worse: after so much retrieval and citation, these pages end up in web crawls, and web crawls end up in training data (I hope it hasn’t!). A number that started as a GPT-4.1 guess can become something the next model &ldquo;knows.&rdquo;
This points to the larger risk suggested by this experiment, and it&rsquo;s why I&rsquo;m sharing this as research, not as a playbook for fake content. Verifying sources should become an essential part of writers’ and researchers’ workflows.</p>
</blockquote>
<p>Eine Seite mit fragwürdigen Studien konnte mehr als 330 Backlinks erzielen, weil LLMs durch ihr indizieren und spätere Ausgeben den falschen Zahlen Authentizität verleiten. Dies ist ein weiterer Beleg dafür, dass man LLMs nicht blind vertrauen sollte.</p>
]]>    
      <![CDATA[<br><br><hr><br><small><p>Vielen Dank fürs Lesen! Wenn du Lust auf noch mehr Gedanken, Updates und ab und zu einen Blick hinter die Kulissen hast, folge mir doch gern auf <a href="https://maik.io/mastodon">Mastodon</a> oder <a href="https://maik.io/instagram">Instagram</a>.</p><p>Hast du Fragen oder Feedback? Schreib mir gern eine <a href="https://maik.io/email">E-Mail</a>.</p></small>]]>
      </content:encoded>  
    </item>      
  </channel>
</rss>