<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Court Sanctions Plaintiff&#8217;s Lawyer for Unverified Claims That the Defendant Was Hiding&#8211;Guangzhou Youlan Technology Co. Ltd. v. Onbrill World	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2025/11/court-sanctions-plaintiffs-lawyer-for-unverified-claims-that-the-defendant-was-hiding-guangzhou-youlan-technology-co-ltd-v-onbrill-world.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2025/11/court-sanctions-plaintiffs-lawyer-for-unverified-claims-that-the-defendant-was-hiding-guangzhou-youlan-technology-co-ltd-v-onbrill-world.htm</link>
	<description></description>
	<lastBuildDate>Tue, 02 Dec 2025 17:14:29 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Another Shill Article Tries to Normalize the SAD Scheme - Technology &#38; Marketing Law Blog		</title>
		<link>https://blog.ericgoldman.org/archives/2025/11/court-sanctions-plaintiffs-lawyer-for-unverified-claims-that-the-defendant-was-hiding-guangzhou-youlan-technology-co-ltd-v-onbrill-world.htm#comment-4516</link>

		<dc:creator><![CDATA[Another Shill Article Tries to Normalize the SAD Scheme - Technology &#38; Marketing Law Blog]]></dc:creator>
		<pubDate>Tue, 02 Dec 2025 17:14:29 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28294#comment-4516</guid>

					<description><![CDATA[[&#8230;] Court Sanctions Plaintiff’s Lawyer for Unverified Claims That the Defendant Was Hiding–Guangzhou&#8230; [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Court Sanctions Plaintiff’s Lawyer for Unverified Claims That the Defendant Was Hiding–Guangzhou&#8230; [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
