<?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: If a Lawyer Accepts a TOS While Investigating a Claim, Does It Bind the Client to Arbitration?	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2022/03/if-a-lawyer-accepts-a-tos-while-investigating-a-claim-does-it-bind-the-client-to-arbitration.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2022/03/if-a-lawyer-accepts-a-tos-while-investigating-a-claim-does-it-bind-the-client-to-arbitration.htm</link>
	<description></description>
	<lastBuildDate>Thu, 31 Mar 2022 23:23:38 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Policy Building Blocks: What Do We Mean When We Talk About Liability &#124; Techdirt		</title>
		<link>https://blog.ericgoldman.org/archives/2022/03/if-a-lawyer-accepts-a-tos-while-investigating-a-claim-does-it-bind-the-client-to-arbitration.htm#comment-3222</link>

		<dc:creator><![CDATA[Policy Building Blocks: What Do We Mean When We Talk About Liability &#124; Techdirt]]></dc:creator>
		<pubDate>Thu, 31 Mar 2022 23:23:38 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=23721#comment-3222</guid>

					<description><![CDATA[[&#8230;] liability, which we see come up in tech policy (see, for instance, discussions around &#8220;terms of service,&#8221; which are largely construed as contracts). A contract essentially is an agreement between [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] liability, which we see come up in tech policy (see, for instance, discussions around &#8220;terms of service,&#8221; which are largely construed as contracts). A contract essentially is an agreement between [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
