<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: eric-miraglia</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/eric-miraglia.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-10-15T17:23:38+00:00</updated><author><name>Simon Willison</name></author><entry><title>Page Inlink Analyzer</title><link href="https://simonwillison.net/2008/Oct/15/inlink/#atom-tag" rel="alternate"/><published>2008-10-15T17:23:38+00:00</published><updated>2008-10-15T17:23:38+00:00</updated><id>https://simonwillison.net/2008/Oct/15/inlink/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://ericmiraglia.com/inlink/"&gt;Page Inlink Analyzer&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Here’s why I’m so keen on JSONP APIs—Eric Miraglia’s tool fires off dozens of cross-domain JSON requests to pull together information about inbound links to your site from Yahoo! Site Explorer and del.icio.us. I imagine it would have been uneconomic for him to provide the tool if it had to proxy every request through his own server.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.ejeliot.com/blog/132"&gt;Ed Eliot&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apis"&gt;apis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/delicious"&gt;delicious&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/eric-miraglia"&gt;eric-miraglia&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/json"&gt;json&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jsonp"&gt;jsonp&lt;/a&gt;&lt;/p&gt;



</summary><category term="apis"/><category term="delicious"/><category term="eric-miraglia"/><category term="javascript"/><category term="json"/><category term="jsonp"/></entry></feed>