<?xml version="1.0"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:neowin="https://www.neowin.net/">
	<channel>
		<title>Neowin News Feed for: Quin69</title>
		<link>https://www.neowin.net/news/tag/quin69/</link>
        <atom:link href="https://www.neowin.net/news/rss/quin69/" rel="self" type="application/rss+xml" />
		<description>Neowin News Feed for: Quin69</description>
		<language>en-us</language>
		<generator>Neowin Ignition News</generator>
		<managingEditor>editor@neowin.net (Managing Editor)</managingEditor>
		<webMaster>developers@neowin.net (Neowin Developers)</webMaster>
		<ttl>5</ttl>
		<image>
			<title>Neowin.net</title>
			<url>https://www.neowin.net/images/pegasus/icon.png</url>
			<link>https://www.neowin.net</link>
		</image>
		        <item>
            <title>Blizzard reportedly staged Diablo 4 Q&amp;A with fake accounts </title>
            <link>https://www.neowin.net/news/blizzard-reportedly-staged-diablo-4-qa-with-fake-accounts/</link>
            <description>&lt;div style="float:left;margin-right:10px;"&gt;&lt;img src="https://cdn.neowin.com/news/images/uploaded/2023/05/1685224282_blizzard-fake-q-a_medium.jpg" alt="" /&gt;&lt;/div&gt;Twitch streamer alleges Blizzard staged Diablo 4 Q&amp;amp;A by using fake accounts for softball questions. Fans question transparency and demand accountability. Here&amp;#039;s what happened in the Blizzard stream. &lt;a href="https://www.neowin.net/news/blizzard-reportedly-staged-diablo-4-qa-with-fake-accounts/"&gt;Read more...&lt;/a&gt;</description>
            <author>Omer Dursun</author>
            <pubDate>Sat, 27 May 2023 22:00:01 +0000</pubDate>
            <guid>https://www.neowin.net/news/blizzard-reportedly-staged-diablo-4-qa-with-fake-accounts/</guid>
            <media:thumbnail url="https://cdn.neowin.com/news/images/uploaded/2023/05/1685224282_blizzard-fake-q-a_story.jpg" width="760" height="428" />
            <neowin:tags>#Diablo4 #Blizzard</neowin:tags>                    </item>
        	</channel>
</rss>
