<?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: A Closer Look at a Troubling Anti-Scraping Ruling from Spring&#8211;Compulife Software v. Newman (Guest Blog Post)	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm</link>
	<description></description>
	<lastBuildDate>Mon, 11 Jan 2021 23:48:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Meester Bonetti		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2879</link>

		<dc:creator><![CDATA[Meester Bonetti]]></dc:creator>
		<pubDate>Mon, 11 Jan 2021 23:48:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2879</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2755&quot;&gt;James Pooley&lt;/a&gt;.

https://www.ipwatchdog.com/2020/07/14/improper-means-eleventh-circuits-dubious-trade-secrets-decision-compulife-software-v-newman-part-ii/id=123265/ in case you wanted to read an opinion from a competent IP attorney.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2755">James Pooley</a>.</p>
<p><a href="https://www.ipwatchdog.com/2020/07/14/improper-means-eleventh-circuits-dubious-trade-secrets-decision-compulife-software-v-newman-part-ii/id=123265/" rel="nofollow ugc">https://www.ipwatchdog.com/2020/07/14/improper-means-eleventh-circuits-dubious-trade-secrets-decision-compulife-software-v-newman-part-ii/id=123265/</a> in case you wanted to read an opinion from a competent IP attorney.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Moses		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2878</link>

		<dc:creator><![CDATA[Moses]]></dc:creator>
		<pubDate>Sat, 09 Jan 2021 17:03:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2878</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2755&quot;&gt;James Pooley&lt;/a&gt;.

This sort of half witted nonsense is what happens when attorneys believe that simply because of the fact they passed the BAR they actually posses a high level of intellect.  EVERY website is designed to allow an individual access to the site, and not necessarily designed for automated access.  However, ALL well written websites must be designed to work well when accessed by automated software if the website proprietor has any intentions for his/her website to crawl to the top of GOOGLE searches.  Claiming that a website was &quot;constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time&quot; shows how passing a State or States bar exam does NOT guarantee the  attorney in question has even the most basic level of intelligence.  In fact, the attorney for the Plaintiff this case bet his entire case (in BOTH trials) on the hope that the Judge is as ignorant technically as you are. In the first trial he (the attorney for the Plaintiff) failed miserably because  Judge Hopkins was an experienced programmer for 20 years prior to becoming an attorney.  Whether or not that same attorney&#039;s intentional deception will work in the new trial outcome remains to be seen.  Claiming that anything that Compulife software produced was &quot;Carefully designed&quot; certainly shows you have not read the transcripts of even the first trial (I don&#039;t think the second trial transcripts are public record until the trial is concluded).]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2755">James Pooley</a>.</p>
<p>This sort of half witted nonsense is what happens when attorneys believe that simply because of the fact they passed the BAR they actually posses a high level of intellect.  EVERY website is designed to allow an individual access to the site, and not necessarily designed for automated access.  However, ALL well written websites must be designed to work well when accessed by automated software if the website proprietor has any intentions for his/her website to crawl to the top of GOOGLE searches.  Claiming that a website was &#8220;constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time&#8221; shows how passing a State or States bar exam does NOT guarantee the  attorney in question has even the most basic level of intelligence.  In fact, the attorney for the Plaintiff this case bet his entire case (in BOTH trials) on the hope that the Judge is as ignorant technically as you are. In the first trial he (the attorney for the Plaintiff) failed miserably because  Judge Hopkins was an experienced programmer for 20 years prior to becoming an attorney.  Whether or not that same attorney&#8217;s intentional deception will work in the new trial outcome remains to be seen.  Claiming that anything that Compulife software produced was &#8220;Carefully designed&#8221; certainly shows you have not read the transcripts of even the first trial (I don&#8217;t think the second trial transcripts are public record until the trial is concluded).</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Moses		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2821</link>

		<dc:creator><![CDATA[Moses]]></dc:creator>
		<pubDate>Fri, 20 Nov 2020 23:45:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2821</guid>

					<description><![CDATA[The &quot;Transformative Database&quot; term is a rarely used term, but the term typically is used for applications that turn data from one format to another such as an export to XML from a tab delimited file, or other data format.  This term is simply a made up term by Robert Barney himself and used by his attorney to confuse the technically challenged into believing there is some sort of high tech magic and genius involved in an outdated unnecessarily complex hack job of an application. One I might add where his programmer could not be bothered to add the simplest of protections.  It says he went out of his way to protect his database with a &quot;Digital Watermark&quot;. In fact he added a two characters to one of his least quoted carriers quotes.  The simple code takes his users 3 numeric digit user id and performs a few bit wise operations on it to create a two byte code.  He did this after one of many scraping incidents so he would know which user of his was actually being scraped.  

As far as the &quot;Transformative Database&quot; it is nothing more than the sort of database a programmer would build to hold federal, State and Local income tax rate tables to retrieve for payroll calculations.  No rocket science going on there, trust me.]]></description>
			<content:encoded><![CDATA[<p>The &#8220;Transformative Database&#8221; term is a rarely used term, but the term typically is used for applications that turn data from one format to another such as an export to XML from a tab delimited file, or other data format.  This term is simply a made up term by Robert Barney himself and used by his attorney to confuse the technically challenged into believing there is some sort of high tech magic and genius involved in an outdated unnecessarily complex hack job of an application. One I might add where his programmer could not be bothered to add the simplest of protections.  It says he went out of his way to protect his database with a &#8220;Digital Watermark&#8221;. In fact he added a two characters to one of his least quoted carriers quotes.  The simple code takes his users 3 numeric digit user id and performs a few bit wise operations on it to create a two byte code.  He did this after one of many scraping incidents so he would know which user of his was actually being scraped.  </p>
<p>As far as the &#8220;Transformative Database&#8221; it is nothing more than the sort of database a programmer would build to hold federal, State and Local income tax rate tables to retrieve for payroll calculations.  No rocket science going on there, trust me.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Moses		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2820</link>

		<dc:creator><![CDATA[Moses]]></dc:creator>
		<pubDate>Fri, 20 Nov 2020 23:16:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2820</guid>

					<description><![CDATA[&quot;second, because the database was the core of its business model, the plaintiff was unusually protective of its database. It was so protective of the database that it added a digital watermark to it, which appeared on the defendant’s website. So unique and special was the plaintiff’s database, that the court called it the “Transformative Database.”

Most databases aren’t copyrighted. Most aren’t that transformative. Most instances of copying aren’t quite so brazen as the defendants’ here. These were all material considerations driving the outcome. As such, most plaintiffs are unlikely to share the facts that drove this result and may not be able to successfully rely on this case as precedent (though I’m sure plenty will try).&quot;

100% Factually incorrect.  The Database DID not have a copywrite, however immediately prior to filing these cases and at least 5 years post production, Compulife registered copyrights on two versions of simple 10 field web form.  Nothing in that simple and poorly written HTML form is unique in anyway (although the troubled Mr. Barney thinks because in addition to 50 states with numeric value properties according to alphabetic order he added the District of Columbia (which became 52) and second New York entry for New York Businesses it threw off the numbers following.  That he claims makes his simple web form a unique work of genius.   In addition the Name properties assigned to the Option tags, radio buttons and text boxes are camel cased and the required export fields in the HTTP request generated, and the programmer copied the exact Camel Casing and spelling of variables in his C++ web engine that will ultimately receive these parameters, they qualify as some sort of unique trade secret. That is simply false.  

In addition to all this the so called &quot;finding of facts&quot; used to access applicable case law used in the appellate court decision ARE NOT the findings of fact but rather a direct plagiarism of Compulife&#039;s owner&#039;s pre-trial deposition.  It should be noted that Robert Barney does not have even the slightest level of technical expertise and his statements alone in an irate  deposition are not and where not the courts findings of facts.  The reason for this mishap was intentional and the result of Compulife&#039;s council intentionally deceiving the court.]]></description>
			<content:encoded><![CDATA[<p>&#8220;second, because the database was the core of its business model, the plaintiff was unusually protective of its database. It was so protective of the database that it added a digital watermark to it, which appeared on the defendant’s website. So unique and special was the plaintiff’s database, that the court called it the “Transformative Database.”</p>
<p>Most databases aren’t copyrighted. Most aren’t that transformative. Most instances of copying aren’t quite so brazen as the defendants’ here. These were all material considerations driving the outcome. As such, most plaintiffs are unlikely to share the facts that drove this result and may not be able to successfully rely on this case as precedent (though I’m sure plenty will try).&#8221;</p>
<p>100% Factually incorrect.  The Database DID not have a copywrite, however immediately prior to filing these cases and at least 5 years post production, Compulife registered copyrights on two versions of simple 10 field web form.  Nothing in that simple and poorly written HTML form is unique in anyway (although the troubled Mr. Barney thinks because in addition to 50 states with numeric value properties according to alphabetic order he added the District of Columbia (which became 52) and second New York entry for New York Businesses it threw off the numbers following.  That he claims makes his simple web form a unique work of genius.   In addition the Name properties assigned to the Option tags, radio buttons and text boxes are camel cased and the required export fields in the HTTP request generated, and the programmer copied the exact Camel Casing and spelling of variables in his C++ web engine that will ultimately receive these parameters, they qualify as some sort of unique trade secret. That is simply false.  </p>
<p>In addition to all this the so called &#8220;finding of facts&#8221; used to access applicable case law used in the appellate court decision ARE NOT the findings of fact but rather a direct plagiarism of Compulife&#8217;s owner&#8217;s pre-trial deposition.  It should be noted that Robert Barney does not have even the slightest level of technical expertise and his statements alone in an irate  deposition are not and where not the courts findings of facts.  The reason for this mishap was intentional and the result of Compulife&#8217;s council intentionally deceiving the court.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Moses		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2819</link>

		<dc:creator><![CDATA[Moses]]></dc:creator>
		<pubDate>Fri, 20 Nov 2020 23:03:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2819</guid>

					<description><![CDATA[&quot;Although the Transformative Database is based on publicly available information—namely, individual insurers’ rate tables—it can’t be replicated without a specialized method and formula known only within Compulife.&quot;

Patently false as are the numerous claims.  Absolutely nothing about this database can not be duplicated by anyone with even a sub standard intelligence level (Mr. Barney certainly qualifies in that regard)

The claims of software piracy are even more ridiculous in this case.]]></description>
			<content:encoded><![CDATA[<p>&#8220;Although the Transformative Database is based on publicly available information—namely, individual insurers’ rate tables—it can’t be replicated without a specialized method and formula known only within Compulife.&#8221;</p>
<p>Patently false as are the numerous claims.  Absolutely nothing about this database can not be duplicated by anyone with even a sub standard intelligence level (Mr. Barney certainly qualifies in that regard)</p>
<p>The claims of software piracy are even more ridiculous in this case.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James Pooley		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2755</link>

		<dc:creator><![CDATA[James Pooley]]></dc:creator>
		<pubDate>Tue, 22 Sep 2020 16:42:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2755</guid>

					<description><![CDATA[Eric and Kieran, this is a very thoughtful post -- however, as to the trade secret issues I disagree.  Coincidentally today I posted on the same topic on IP Watchdog, where I argued that the Compulife opinion is a logical application of the flexibility that characterizes the &quot;improper means&quot; element of trade secret misappropriation.  Where I think your analysis fails is in  broadly characterizing Compulife&#039;s database as &quot;publicly accessible.&quot;  That elides the very important fact that its public accessibility was constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time. Sort of like a turnstile in the subway.  The defendant created robotic software to defeat that limitation, in violation of the user agreement.  So what they did shouldn&#039;t fairly be characterized as simply taking &quot;publicly accessible&quot; data; instead, they created a tool that would fake a human inquiry and repeat it 42 million times!  The database was no more &quot;publicly accessible&quot; than was the construction site in the DuPont v Christopher case.  In order to get to the valuable stuff you had to create a &quot;trick&quot; to get around the system -- then it was (as the U.S. Supreme Court called it when citing DuPont with approval in Kewanee v. Bicron) &quot;aerial reconnaissance&quot;, and now it&#039;s &quot;data scraping&quot;.  The question is whether, by defeating the reasonable expectations of the trade secret owner through technological means, you have done something that disturbs the &quot;standards of commercial ethics&quot; (as the Kewanee court described one of the twin pillars of trade secret law).  The Compulife court merely held that that was a permissible way to analyze the case, and unless we&#039;re going to revisit Kewanee and the foundations of trade secret law, I think they got that part absolutely right.  Just because a restaurant sets up a self-serve smorgasbord doesn&#039;t mean that a competitor can drive up a truck and load up all the food for the cost of one meal.  What the defendants did in Compulife was clearly unfair, unless your view is that any limitations on use are inappropriate and unenforceable as a matter of policy.]]></description>
			<content:encoded><![CDATA[<p>Eric and Kieran, this is a very thoughtful post &#8212; however, as to the trade secret issues I disagree.  Coincidentally today I posted on the same topic on IP Watchdog, where I argued that the Compulife opinion is a logical application of the flexibility that characterizes the &#8220;improper means&#8221; element of trade secret misappropriation.  Where I think your analysis fails is in  broadly characterizing Compulife&#8217;s database as &#8220;publicly accessible.&#8221;  That elides the very important fact that its public accessibility was constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time. Sort of like a turnstile in the subway.  The defendant created robotic software to defeat that limitation, in violation of the user agreement.  So what they did shouldn&#8217;t fairly be characterized as simply taking &#8220;publicly accessible&#8221; data; instead, they created a tool that would fake a human inquiry and repeat it 42 million times!  The database was no more &#8220;publicly accessible&#8221; than was the construction site in the DuPont v Christopher case.  In order to get to the valuable stuff you had to create a &#8220;trick&#8221; to get around the system &#8212; then it was (as the U.S. Supreme Court called it when citing DuPont with approval in Kewanee v. Bicron) &#8220;aerial reconnaissance&#8221;, and now it&#8217;s &#8220;data scraping&#8221;.  The question is whether, by defeating the reasonable expectations of the trade secret owner through technological means, you have done something that disturbs the &#8220;standards of commercial ethics&#8221; (as the Kewanee court described one of the twin pillars of trade secret law).  The Compulife court merely held that that was a permissible way to analyze the case, and unless we&#8217;re going to revisit Kewanee and the foundations of trade secret law, I think they got that part absolutely right.  Just because a restaurant sets up a self-serve smorgasbord doesn&#8217;t mean that a competitor can drive up a truck and load up all the food for the cost of one meal.  What the defendants did in Compulife was clearly unfair, unless your view is that any limitations on use are inappropriate and unenforceable as a matter of policy.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James Pooley		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2753</link>

		<dc:creator><![CDATA[James Pooley]]></dc:creator>
		<pubDate>Mon, 21 Sep 2020 18:20:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2753</guid>

					<description><![CDATA[Eric, another very thoughtful post -- however, as to the trade secret issues I disagree.  Coincidentally today I posted on the same topic on IP Watchdog, where I argued that the Compulife opinion is a logical application of the flexibility that characterizes the &quot;improper means&quot; element of trade secret misappropriation.  Where I think your analysis fails is in  broadly characterizing Compulife&#039;s database as &quot;publicly accessible.&quot;  That elides the very important fact that its public accessibility was constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time.  Sort of like a turnstile in the subway.  The defendant created robotic software to defeat that limitation, in violation of the user agreement.  So what they did shouldn&#039;t fairly be characterized as simply taking &quot;publicly accessible&quot; data; instead, they created a tool that would fake a human inquiry and repeat it 42 million times!  The database was no more &quot;publicly accessible&quot; than was the construction site in the DuPont v Christopher case.  In order to get to the valuable stuff you had to create a &quot;trick&quot; to get around the system -- then it was (as the U.S. Supreme Court called it when citing DuPont with approval in Kewanee v. Bicron) &quot;aerial reconnaissance&quot;, and now it&#039;s &quot;data scraping&quot;.  The question is whether, by defeating the reasonable expectations of the trade secret owner through technological means, you have done something that disturbs the &quot;standards of commercial ethics&quot; (as the Kewanee court described one of the twin pillars of trade secret law).  The Compulife court merely held that that was a permissible way to analyze the case, and unless we&#039;re going to revisit Kewanee and the foundations of trade secret law, I think they got that part absolutely right.  Just because a restaurant sets up a self-serve smorgasbord doesn&#039;t mean that a competitor can drive up a truck and load up all the food for the cost of one meal.  What the defendants did in Compulife was clearly unfair, unless your view is that any limitations on use are inappropriate and unenforceable as a matter of policy.]]></description>
			<content:encoded><![CDATA[<p>Eric, another very thoughtful post &#8212; however, as to the trade secret issues I disagree.  Coincidentally today I posted on the same topic on IP Watchdog, where I argued that the Compulife opinion is a logical application of the flexibility that characterizes the &#8220;improper means&#8221; element of trade secret misappropriation.  Where I think your analysis fails is in  broadly characterizing Compulife&#8217;s database as &#8220;publicly accessible.&#8221;  That elides the very important fact that its public accessibility was constructed carefully to ensure that one person at a time would be able to access one insurance quote at a time.  Sort of like a turnstile in the subway.  The defendant created robotic software to defeat that limitation, in violation of the user agreement.  So what they did shouldn&#8217;t fairly be characterized as simply taking &#8220;publicly accessible&#8221; data; instead, they created a tool that would fake a human inquiry and repeat it 42 million times!  The database was no more &#8220;publicly accessible&#8221; than was the construction site in the DuPont v Christopher case.  In order to get to the valuable stuff you had to create a &#8220;trick&#8221; to get around the system &#8212; then it was (as the U.S. Supreme Court called it when citing DuPont with approval in Kewanee v. Bicron) &#8220;aerial reconnaissance&#8221;, and now it&#8217;s &#8220;data scraping&#8221;.  The question is whether, by defeating the reasonable expectations of the trade secret owner through technological means, you have done something that disturbs the &#8220;standards of commercial ethics&#8221; (as the Kewanee court described one of the twin pillars of trade secret law).  The Compulife court merely held that that was a permissible way to analyze the case, and unless we&#8217;re going to revisit Kewanee and the foundations of trade secret law, I think they got that part absolutely right.  Just because a restaurant sets up a self-serve smorgasbord doesn&#8217;t mean that a competitor can drive up a truck and load up all the food for the cost of one meal.  What the defendants did in Compulife was clearly unfair, unless your view is that any limitations on use are inappropriate and unenforceable as a matter of policy.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: News of the Week; September 16, 2020 &#8211; Communications Law at Allard Hall		</title>
		<link>https://blog.ericgoldman.org/archives/2020/09/a-closer-look-at-a-troubling-anti-scraping-ruling-from-spring-compulife-software-v-newman-guest-blog-post.htm#comment-2752</link>

		<dc:creator><![CDATA[News of the Week; September 16, 2020 &#8211; Communications Law at Allard Hall]]></dc:creator>
		<pubDate>Mon, 21 Sep 2020 02:31:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=21672#comment-2752</guid>

					<description><![CDATA[[&#8230;] A Closer Look at a Troubling Anti-Scraping Ruling from Spring &#8211; Compulife Software v. Newman [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] A Closer Look at a Troubling Anti-Scraping Ruling from Spring &#8211; Compulife Software v. Newman [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
