<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: blaine-cook</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/blaine-cook.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-01-31T13:57:53+00:00</updated><author><name>Simon Willison</name></author><entry><title>Hot Code Loading in Node.js</title><link href="https://simonwillison.net/2010/Jan/31/liminal/#atom-tag" rel="alternate"/><published>2010-01-31T13:57:53+00:00</published><updated>2010-01-31T13:57:53+00:00</updated><id>https://simonwillison.net/2010/Jan/31/liminal/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://romeda.org/blog/2010/01/hot-code-loading-in-nodejs.html?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A LiminalExistence %28Liminal Existence%29"&gt;Hot Code Loading in Node.js&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Blaine Cook’s patch for Node.js that enables Erlang-style hot code loading, so you can switch out your application logic without restarting the server or affecting existing requests. This could make deploying new versions of Node applications trivial. I’d love to see a Node hosting service that allows you to simply upload a script file and have it execute on the Web.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/deployment"&gt;deployment&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/erlang"&gt;erlang&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nodejs"&gt;nodejs&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="deployment"/><category term="erlang"/><category term="javascript"/><category term="nodejs"/></entry><entry><title>Quoting Blaine Cook</title><link href="https://simonwillison.net/2009/Aug/13/blaine/#atom-tag" rel="alternate"/><published>2009-08-13T13:06:46+00:00</published><updated>2009-08-13T13:06:46+00:00</updated><id>https://simonwillison.net/2009/Aug/13/blaine/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://delicious.com/lattice/distributed social networking twitter facebook"&gt;&lt;p&gt;When we get the tools to do distributed Twitter, etc., we get the tools to communicate in stanzas richer than those allowed by our decades-old email clients. Never mind Apple being anti-competitive, social networks are the peak of monopolistic behaviour today.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://delicious.com/lattice/distributed social networking twitter facebook"&gt;Blaine Cook&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apple"&gt;apple&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/distributedsocialnetworks"&gt;distributedsocialnetworks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/facebook"&gt;facebook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-networks"&gt;social-networks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="apple"/><category term="blaine-cook"/><category term="distributedsocialnetworks"/><category term="facebook"/><category term="social-networks"/><category term="twitter"/></entry><entry><title>The Twitter administrator hack was a dictionary attack</title><link href="https://simonwillison.net/2009/Jan/6/twitterhack/#atom-tag" rel="alternate"/><published>2009-01-06T23:56:20+00:00</published><updated>2009-01-06T23:56:20+00:00</updated><id>https://simonwillison.net/2009/Jan/6/twitterhack/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://simonwillison.net/2009/Jan/2/adactio/#c43001"&gt;The Twitter administrator hack was a dictionary attack&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I quoted Blaine earlier suggesting that the recent Twitter mass-hack was due to a Twitter admin password being scooped up by a rogue third party application—this was not the case, as Alex Payne explains in a comment.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/alex-payne"&gt;alex-payne&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="alex-payne"/><category term="blaine-cook"/><category term="security"/><category term="twitter"/></entry><entry><title>Quoting Blaine Cook</title><link href="https://simonwillison.net/2008/Aug/14/oauth/#atom-tag" rel="alternate"/><published>2008-08-14T10:01:37+00:00</published><updated>2008-08-14T10:01:37+00:00</updated><id>https://simonwillison.net/2008/Aug/14/oauth/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.lukeredpath.co.uk/2008/8/12/on-iphones-and-user-credentials"&gt;&lt;p&gt;OAuth came out of my worry that if the Twitter API became popular, we'd be spreading passwords all around the web. OAuth took longer to finish than it took for the Twitter API to become popular, and as a result many Twitter users' passwords are scattered pretty carelessly around the web. This is a terrible situation, and one we as responsible web developers should work to prevent.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.lukeredpath.co.uk/2008/8/12/on-iphones-and-user-credentials"&gt;Blaine Cook&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/passwords"&gt;passwords&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/phishing"&gt;phishing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitterapi"&gt;twitterapi&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="oauth"/><category term="passwords"/><category term="phishing"/><category term="security"/><category term="twitter"/><category term="twitterapi"/></entry><entry><title>RubyForge: Starling</title><link href="https://simonwillison.net/2008/Jan/11/rubyforge/#atom-tag" rel="alternate"/><published>2008-01-11T21:47:26+00:00</published><updated>2008-01-11T21:47:26+00:00</updated><id>https://simonwillison.net/2008/Jan/11/rubyforge/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://rubyforge.org/projects/starling/"&gt;RubyForge: Starling&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“Starling is a light-weight persistent queue server that speaks the MemCache protocol. It was built to drive Twitter’s backend, and is in production across Twitter’s cluster.”


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/memcached"&gt;memcached&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/message-queues"&gt;message-queues&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/messaging"&gt;messaging&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/queue"&gt;queue&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ruby"&gt;ruby&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rubyforge"&gt;rubyforge&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/starling"&gt;starling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="memcached"/><category term="message-queues"/><category term="messaging"/><category term="queue"/><category term="ruby"/><category term="rubyforge"/><category term="starling"/><category term="twitter"/></entry><entry><title>SELECT * FROM everything, or why databases are awesome</title><link href="https://simonwillison.net/2007/Jun/22/liminal/#atom-tag" rel="alternate"/><published>2007-06-22T00:40:09+00:00</published><updated>2007-06-22T00:40:09+00:00</updated><id>https://simonwillison.net/2007/Jun/22/liminal/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://romeda.org/blog/2007/06/select-from-everything-or-why-databases.html"&gt;SELECT * FROM everything, or why databases are awesome&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I’m beginning to think that for scalable applications the thinner your ORM is the better—if you even use one at all.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/databases"&gt;databases&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/orm"&gt;orm&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sql"&gt;sql&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="databases"/><category term="orm"/><category term="rails"/><category term="scaling"/><category term="sql"/><category term="twitter"/></entry><entry><title>Scaling Twitter</title><link href="https://simonwillison.net/2007/Apr/23/scaling/#atom-tag" rel="alternate"/><published>2007-04-23T11:02:11+00:00</published><updated>2007-04-23T11:02:11+00:00</updated><id>https://simonwillison.net/2007/Apr/23/scaling/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.slideshare.net/Blaine/scaling-twitter/"&gt;Scaling Twitter&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Slides from Blaine’s recent talk.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://romeda.org/blog/2007/04/slides-for-scaling-twitter-talk-xtech.html"&gt;Blaine Cook&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blaine-cook"&gt;blaine-cook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="blaine-cook"/><category term="rails"/><category term="scaling"/><category term="twitter"/></entry></feed>