<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.artific.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.artific.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
	<title>202: Accepted</title>
	<link rel="alternate" type="text/html" href="http://artific.com/202/" />
	
	<id>tag:artific.com,2008:/202//4</id>
	<link rel="service.post" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4" title="202: Accepted" />
	<updated>2008-01-27T07:29:14Z</updated>
	<subtitle>A collection of informal posts about web and internet technology.</subtitle>
	<generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
<geo:lat>40.69989</geo:lat><geo:long>-73.99595</geo:long><link rel="self" href="http://feeds.artific.com/202Accepted" type="application/atom+xml" /><feedburner:emailServiceId>344414</feedburner:emailServiceId><feedburner:feedburnerHostname>http://www.feedburner.com</feedburner:feedburnerHostname><entry>
	<title>EOY 2007 Data Analysis</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/209476174/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=408" title="EOY 2007 Data Analysis" />
	<id>tag:artific.com,2008:/202//4.408</id>
	<published>2008-01-01T16:44:00Z</published>
	<updated>2008-01-27T07:29:14Z</updated>
	<summary type="html">Some end of year data analysis for artific.com</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2008/01/eoy_2007_data_analysis/comments.xml</wfw:commentRss>
	<category term="Webmastery" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;It's a new year and time for some dumb data analysis.&lt;/p&gt;

&lt;p&gt;Most interesting thing to me this year is that most of the traffic&lt;br /&gt;
to this site and my other sites (notably epcostello.net) is from &lt;br /&gt;
automated agents: search engines, random webcrawlers, &lt;span class="caps"&gt;SEO'&lt;/span&gt;s link injectors.&lt;/p&gt;


&lt;h2&gt;&lt;span class="caps"&gt;HTTP&lt;/span&gt; Status Codes:&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;155127&lt;/td&gt;&lt;td&gt;200&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;64662&lt;/td&gt;&lt;td&gt;304&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;11400&lt;/td&gt;&lt;td&gt;301&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6352&lt;/td&gt;&lt;td&gt;302&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5705&lt;/td&gt;&lt;td&gt;404&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5308&lt;/td&gt;&lt;td&gt;202&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2784&lt;/td&gt;&lt;td&gt;401&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1609&lt;/td&gt;&lt;td&gt;405&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;126&lt;/td&gt;&lt;td&gt;400&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;63&lt;/td&gt;&lt;td&gt;414&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;31&lt;/td&gt;&lt;td&gt;500&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;30&lt;/td&gt;&lt;td&gt;403&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3&lt;/td&gt;&lt;td&gt;501&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;


&lt;h2&gt;Top Ten Hosts&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;4551&lt;/td&gt;&lt;td&gt;66.249.73.200&lt;/td&gt;&lt;td&gt;crawl-66-249-73-200.googlebot.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2234&lt;/td&gt;&lt;td&gt;81.52.143.16&lt;/td&gt;&lt;td&gt;natcrawlbloc03.net.m1.fti.net&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1890&lt;/td&gt;&lt;td&gt;81.52.143.15&lt;/td&gt;&lt;td&gt;natcrawlbloc01.net.m1.fti.net.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1492&lt;/td&gt;&lt;td&gt;64.152.34.36&lt;/td&gt;&lt;td&gt;jfk-lv3-n4.panthercdn.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1380&lt;/td&gt;&lt;td&gt;38.99.203.110&lt;/td&gt;&lt;td&gt;Panscient_Data_Services.demarc.cogentco.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;991&lt;/td&gt;&lt;td&gt;128.194.135.94&lt;/td&gt;&lt;td&gt;web-crawler.irl.cs.tamu.edu&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;885&lt;/td&gt;&lt;td&gt;216.240.154.103&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;884&lt;/td&gt;&lt;td&gt;66.249.73.148&lt;/td&gt;&lt;td&gt;crawl-66-249-73-148.googlebot.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;800&lt;/td&gt;&lt;td&gt;64.92.162.210&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;773&lt;/td&gt;&lt;td&gt;72.30.177.225&lt;/td&gt;&lt;td&gt;wm509310.inktomisearch.com.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h2&gt;Raw Top Ten Requests&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;21547&lt;/td&gt;&lt;td&gt;/robots.txt&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;8030&lt;/td&gt;&lt;td&gt;/favicon.ico&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6801&lt;/td&gt;&lt;td&gt;/articles/2005/12/27/a_practically_u/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6062&lt;/td&gt;&lt;td&gt;/articles/nav-commenters.gif&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6055&lt;/td&gt;&lt;td&gt;/g/Google_logo_transparent.png&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5582&lt;/td&gt;&lt;td&gt;/d/4/js/ajax/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5290&lt;/td&gt;&lt;td&gt;/202/2006/06/disabling_trackbacks_in_movabl/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4445&lt;/td&gt;&lt;td&gt;/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4217&lt;/td&gt;&lt;td&gt;/g/feed-icon-16&amp;#215;16.png&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3993&lt;/td&gt;&lt;td&gt;/g/by-sa-3.0-88&amp;#215;31.png&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h2&gt;Filtered Top Ten Requests&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;21547&lt;/td&gt;&lt;td&gt;/robots.txt&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6801&lt;/td&gt;&lt;td&gt;/articles/2005/12/27/a_practically_u/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5290&lt;/td&gt;&lt;td&gt;/202/2006/06/disabling_trackbacks_in_movabl/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4445&lt;/td&gt;&lt;td&gt;/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2812&lt;/td&gt;&lt;td&gt;/202/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2664&lt;/td&gt;&lt;td&gt;/202/2006/12/google_reader_annoyances/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2121&lt;/td&gt;&lt;td&gt;/202/2006/10/social-bookmarking-and-attention/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1278&lt;/td&gt;&lt;td&gt;/202/2006/11/bloglines_new_features_playlis/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;912&lt;/td&gt;&lt;td&gt;/articles/&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;890&lt;/td&gt;&lt;td&gt;/202/2006/07/yet_another_spam_retaliation_t/&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h2&gt;Top 20 non-caching requestors of Robots.txt:&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;2353&lt;/td&gt;&lt;td&gt;crawl-66-249-73-200.googlebot.com&lt;/td&gt;&lt;td&gt;[66.249.73.200]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1404&lt;/td&gt;&lt;td&gt;natcrawlbloc03.net.m1.fti.net&lt;/td&gt;&lt;td&gt;[81.52.143.16]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;1192&lt;/td&gt;&lt;td&gt;natcrawlbloc01.net.m1.fti.net&lt;/td&gt;&lt;td&gt;[81.52.143.15]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;770&lt;/td&gt;&lt;td&gt;wm509310.inktomisearch.com&lt;/td&gt;&lt;td&gt;[72.30.177.225]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;736&lt;/td&gt;&lt;td colspan="2"&gt;ct501085.crawl.yahoo.net&lt;/td&gt;&lt;td&gt;[74.6.86.230]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;688&lt;/td&gt;&lt;td&gt;wm509458.inktomisearch.com&lt;/td&gt;&lt;td&gt;[74.6.74.202]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;498&lt;/td&gt;&lt;td&gt;crawl-66-249-73-148.googlebot.com&lt;/td&gt;&lt;td&gt;[66.249.73.148]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;496&lt;/td&gt;&lt;td&gt;livebot-65-55-213-74.search.live.com&lt;/td&gt;&lt;td&gt;[65.55.213.74]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;491&lt;/td&gt;&lt;td&gt;wm508816.inktomisearch.com&lt;/td&gt;&lt;td&gt;[74.6.69.173]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;342&lt;/td&gt;&lt;td colspan="2"&gt;lj512274.crawl.yahoo.net&lt;/td&gt;&lt;td&gt;[74.6.19.77]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;342&lt;/td&gt;&lt;td&gt;wm511001.inktomisearch.com&lt;/td&gt;&lt;td&gt;[72.30.252.135]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;327&lt;/td&gt;&lt;td&gt;natcrawlbloc02.net.s1.fti.net   [193.252.149.15]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;288&lt;/td&gt;&lt;td colspan="2"&gt;lm502044.crawl.yahoo.net&lt;/td&gt;&lt;td&gt;[72.30.226.173]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;262&lt;/td&gt;&lt;td colspan="2"&gt;ct501101.crawl.yahoo.net&lt;/td&gt;&lt;td&gt;[74.6.86.207]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;233&lt;/td&gt;&lt;td&gt;67.110.56.45.ptr.us.xo.net&lt;/td&gt;&lt;td&gt;[67.110.56.45]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;224&lt;/td&gt;&lt;td&gt;crawl-66-249-73-132.googlebot.com&lt;/td&gt;&lt;td&gt;[66.249.73.132]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;208&lt;/td&gt;&lt;td&gt;wm511565.inktomisearch.com&lt;/td&gt;&lt;td&gt;[72.30.226.209]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;206&lt;/td&gt;&lt;td&gt;c02.entireweb.com&lt;/td&gt;&lt;td&gt;[89.150.197.130]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;199&lt;/td&gt;&lt;td&gt;wm509426.inktomisearch.com&lt;/td&gt;&lt;td&gt;[74.6.75.46]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;197&lt;/td&gt;&lt;td&gt;ip67-95-51-86.z51-95-67.customer.algx.net&lt;/td&gt;&lt;td&gt;[67.95.51.86]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;p&gt;Last time robots.txt changed: 23 March 2007&lt;/p&gt;

&lt;h2&gt;Top Ten Referrers (filtered):&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;97488&lt;/td&gt;&lt;td&gt;"-"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;533&lt;/td&gt;&lt;td&gt;"http://neworder.box.sk/forum.php?page=last&amp;amp;did=multSecurity%20and%20Networking&amp;amp;thread=251392"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;244&lt;/td&gt;&lt;td&gt;"http://www.zenatode.org.uk/ian/internet/hotmail.xhtml"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;212&lt;/td&gt;&lt;td&gt;"http://my.yahoo.com/"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;142&lt;/td&gt;&lt;td&gt;"http://www.google.com/search?hl=en&amp;amp;q=phx.gbl"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;122&lt;/td&gt;&lt;td&gt;"http://www.stumbleupon.com/refer.php?url=http%3A%2F%2Fartific.com%2Farticles%2F2005%2F12%2F27%2Fa_practically_u%2F"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;117&lt;/td&gt;&lt;td&gt;"http://www.google.com/search?q=phx.gbl&amp;amp;ie=utf-8&amp;amp;oe=utf-8&amp;amp;aq=t&amp;amp;rls=org.mozilla:en-US:official&amp;amp;client=firefox-a"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;88&lt;/td&gt;&lt;td&gt;"http://www.google.com/search?hl=en&amp;amp;q=phx.gbl&amp;amp;btnG=Google+Search"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;68&lt;/td&gt;&lt;td&gt;"http://neworder.box.sk/forum.php?did=multSecurity%20and%20Networking&amp;amp;thread=251392"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;55&lt;/td&gt;&lt;td&gt;"http://www.dslreports.com/shownews/DNS-Hacks-Phishing-20-90182"&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;p&gt;Internal referrers and obviously junk referrers have been filtered out.&lt;/p&gt;

&lt;h2&gt;Top Ten Raw Search Requests:&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;1474&lt;/td&gt;&lt;td&gt;q=phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;260&lt;/td&gt;&lt;td&gt;q=phx.gbl"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;122&lt;/td&gt;&lt;td&gt;q=.phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;107&lt;/td&gt;&lt;td&gt;q=phx.gbl%3A1863&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;98&lt;/td&gt;&lt;td&gt;q=phx%2egbl"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;76&lt;/td&gt;&lt;td&gt;q=crawler.bloglines.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;62&lt;/td&gt;&lt;td&gt;q=phx.gbl+domain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;59&lt;/td&gt;&lt;td&gt;q=gbl+domain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;53&lt;/td&gt;&lt;td&gt;q=gbl+tld&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;42&lt;/td&gt;&lt;td&gt;q=%22phx.gbl%22&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h3&gt;Top 20 phx.gbl searches:&lt;/h3&gt;

&lt;p&gt;phx.gbl is a pseudo-domain used by Microsoft for a variety of services. I wrote about it in &lt;a href="http://artific.com/articles/2005/12/27/a_practically_u/"&gt;On The Importances of Revers &lt;span class="caps"&gt;DNS&lt;/span&gt;&lt;/a&gt; which I now realize is still using the previous design system for this site.&lt;/p&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;1474&lt;/td&gt;&lt;td&gt;q=phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;260&lt;/td&gt;&lt;td&gt;q=phx.gbl"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;122&lt;/td&gt;&lt;td&gt;q=.phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;107&lt;/td&gt;&lt;td&gt;q=phx.gbl%3A1863&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;62&lt;/td&gt;&lt;td&gt;q=phx.gbl+domain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;42&lt;/td&gt;&lt;td&gt;q=%22phx.gbl%22&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;30&lt;/td&gt;&lt;td&gt;q=.phx.gbl%3A1863&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;29&lt;/td&gt;&lt;td&gt;q=@phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;26&lt;/td&gt;&lt;td&gt;q=%40phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;23&lt;/td&gt;&lt;td&gt;q=phx.gbl+netstat&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;22&lt;/td&gt;&lt;td&gt;q=phx.gbl+1863&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;22&lt;/td&gt;&lt;td&gt;q=.phx.gbl"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;19&lt;/td&gt;&lt;td&gt;q=phx.gbl%3A1863"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;18&lt;/td&gt;&lt;td&gt;q=by2msg2204708.phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;17&lt;/td&gt;&lt;td&gt;q=what+is+phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;15&lt;/td&gt;&lt;td&gt;q=netstat+phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;15&lt;/td&gt;&lt;td&gt;q=by1msg4176104.phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;14&lt;/td&gt;&lt;td&gt;q=phx.gbl+msn&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;q=by2msg2204912.phx.gbl&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;q=%22phx.gbl%22"&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h3&gt;Top 20 Non-phx.gbl searches:&lt;/h3&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;76&lt;/td&gt;&lt;td&gt;q=crawler.bloglines.com&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;38&lt;/td&gt;&lt;td&gt;q=artific&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;16&lt;/td&gt;&lt;td&gt;q=infobackground&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;15&lt;/td&gt;&lt;td&gt;q=ed+costello&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;15&lt;/td&gt;&lt;td&gt;q=207.46.108.36&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;15&lt;/td&gt;&lt;td&gt;q=202+Accepted&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;q=crawler.bloglines.com"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;q=207.46.111.86&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;q=202+accepted&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;11&lt;/td&gt;&lt;td&gt;q=spam+retaliation&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;11&lt;/td&gt;&lt;td&gt;q=InfoBackground&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;10&lt;/td&gt;&lt;td&gt;q=google+reader+rename+folder&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;10&lt;/td&gt;&lt;td&gt;q=Reverse+DNS&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;9&lt;/td&gt;&lt;td&gt;q=kb05474&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;9&lt;/td&gt;&lt;td&gt;q=importance+of+reverse+dns&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;9&lt;/td&gt;&lt;td&gt;q=crawler.bloglines.com+&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;q=nokia+espionage&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;q=iab+ad+units&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;q=hotmail+reverse+dns&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;q=tvpath.com&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;


&lt;p&gt;In March 2007 I wrote my own  trackback  endpoint  in &lt;span class="caps"&gt;PHP &lt;/span&gt;which logs all of the trackback data to a file instead of beating up my MovableType installation and MySQL database.&lt;/p&gt;

&lt;p&gt;Trackbacks Received since 21 March 2007: 10258&lt;/p&gt;

&lt;p&gt;Number of Valid Trackbacks: 0&lt;/p&gt;

&lt;h2&gt;Top Ten Trackback Sources:&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;447&lt;/td&gt;&lt;td&gt;207-234-131-237.ptr.primarydns.com&lt;/td&gt;&lt;td&gt;[207.234.131.237]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;156&lt;/td&gt;&lt;td&gt;movinglabs.com  [195.242.99.80]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;150&lt;/td&gt;&lt;td&gt;u15250532.onlinehome-server.com [74.208.14.63]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;144&lt;/td&gt;&lt;td&gt;218.189.232.72.static.reverse.ltdomains.com&lt;/td&gt;&lt;td&gt;[72.232.189.218]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;124&lt;/td&gt;&lt;td&gt;[206.123.73.15] [206.123.73.15]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;122&lt;/td&gt;&lt;td colspan="2"&gt;server.camelotwealthcreation.com&lt;/td&gt;&lt;td&gt;[69.50.210.8]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;113&lt;/td&gt;&lt;td&gt;giantlogic.net  [208.101.35.52]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;99&lt;/td&gt;&lt;td&gt;89-149-195-161.internetserviceteam.com  [89.149.195.161]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;96&lt;/td&gt;&lt;td&gt;u15251680.onlinehome-server.com [74.208.14.215]&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;95&lt;/td&gt;&lt;td&gt;210.219.232.72.static.reverse.ltdomains.com&lt;/td&gt;&lt;td&gt;[72.232.219.210]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;h2&gt;Top Fifteen Trackback Titles:&lt;/h2&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;169&lt;/td&gt;&lt;td&gt;"Tramadol."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;151&lt;/td&gt;&lt;td&gt;"Phentermine."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;119&lt;/td&gt;&lt;td&gt;"Xanax."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;94&lt;/td&gt;&lt;td&gt;"Cialis."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;62&lt;/td&gt;&lt;td&gt;"Lexapro."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;56&lt;/td&gt;&lt;td&gt;"Ephedra."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;52&lt;/td&gt;&lt;td&gt;"Valium."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;52&lt;/td&gt;&lt;td&gt;"Ultram."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;47&lt;/td&gt;&lt;td&gt;"Zoloft."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;43&lt;/td&gt;&lt;td&gt;"Ambien."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;42&lt;/td&gt;&lt;td&gt;"Fioricet."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;37&lt;/td&gt;&lt;td&gt;"Percocet."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;37&lt;/td&gt;&lt;td&gt;"Cheapphentermine."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;37&lt;/td&gt;&lt;td&gt;"Adderall."&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;34&lt;/td&gt;&lt;td&gt;"Soma."&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=IqdnVH"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=IqdnVH" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=1hM3LxD"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=1hM3LxD" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=fmrh2LD"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=fmrh2LD" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=CgTPzmd"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=CgTPzmd" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/209476174" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2008 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2008%2F01%2Feoy_2007_data_analysis%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2008/01/eoy_2007_data_analysis/</feedburner:origLink></entry>
<entry>
	<title>End of year domain cleanup</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/194168378/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=393" title="End of year domain cleanup" />
	<id>tag:artific.com,2007:/202//4.393</id>
	<published>2007-12-03T03:04:32Z</published>
	<updated>2007-12-03T03:07:59Z</updated>
	<summary type="html">Selling a mess of domains from projects and ideas which never took off.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/12/end_of_year_domain_cleanup/comments.xml</wfw:commentRss>
	<category term="Sales" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I have the following domains available for sale through &lt;a href="http://sedo.com/"&gt;Sedo&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://admarket.tv/"&gt;admarket.tv&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://adrenalinest.com/"&gt;adrenalinest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://adrenalinist.com/"&gt;adrenalinist.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://adrenalist.com/"&gt;adrenalist.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://bagelhound.com/"&gt;bagelhound.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://creativecomputing.info/"&gt;creativecomputing.info&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://datafog.info/"&gt;datafog.info&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://datasmog.info/"&gt;datasmog.info&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://dripldu.com/"&gt;dripldu.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://dripldu.net/"&gt;dripldu.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://dripldu.mobi/"&gt;dripldu.mobi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://drippledew.com/"&gt;drippledew.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://drippledoo.com/"&gt;drippledoo.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://egotropic.com/"&gt;egotropic.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://egotropy.com/"&gt;egotropy.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://experiencebasedmedicine.com/"&gt;experiencebasedmedicine.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://footonground.com/"&gt;footonground.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://identro.com/"&gt;identro.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://identro.net/"&gt;identro.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://jripldu.com/"&gt;jripldu.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://memorybox.mobi/"&gt;memorybox.mobi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://my-piedaterre.com/"&gt;my-piedaterre.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://my-weblog.org/"&gt;my-weblog.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://my-weblog.com/"&gt;my-weblog.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://mydataquest.com/"&gt;mydataquest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://mydatequest.com/"&gt;mydatequest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://myfeedquest.com/"&gt;myfeedquest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://myhealthquest.mobi/"&gt;myhealthquest.mobi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://mymusicquest.com/"&gt;mymusicquest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://mynewsquest.com/"&gt;mynewsquest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://myshopquest.com/"&gt;myshopquest.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://newsweir.com/"&gt;newsweir.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://peedatear.com/"&gt;peedatear.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://peedaterr.com/"&gt;peedaterr.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://peedaterre.com/"&gt;peedaterre.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://piedaterr.com/"&gt;piedaterr.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://pihaven.net/"&gt;pihaven.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://pihaven.org/"&gt;pihaven.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://provincetopia.com/"&gt;provincetopia.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://provincialist.com/"&gt;provincialist.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://provincialist.net/"&gt;provincialist.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://provincialist.org/"&gt;provincialist.org&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://spotmarket.tv/"&gt;spotmarket.tv&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://townist.com/"&gt;townist.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://tristatepolitics.com/"&gt;tristatepolitics.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://tristatepolitics.net/"&gt;tristatepolitics.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://tristatepolitics.tv/"&gt;tristatepolitics.tv&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://tristatepolitics.us/"&gt;tristatepolitics.us&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://xprx.net/"&gt;xprx.net&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Acquire them through &lt;a href="http://sedo.com/"&gt;Sedo&lt;/a&gt; or contact
me at &lt;a href="mailto:sales@artific.com"&gt;sales @ artific.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=dxn0Zt"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=dxn0Zt" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=90uKBsC"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=90uKBsC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=484pZsC"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=484pZsC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=JzQOVkc"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=JzQOVkc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/194168378" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F12%2Fend_of_year_domain_cleanup%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/12/end_of_year_domain_cleanup/</feedburner:origLink></entry>
<entry>
	<title>Reboot</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/180639029/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=373" title="Reboot" />
	<id>tag:artific.com,2007:/202//4.373</id>
	<published>2007-11-06T16:12:00Z</published>
	<updated>2008-01-27T07:29:43Z</updated>
	<summary type="html">I realized I sort of fell off the blog beat here. I've rebuilt the site (again) using the Yahoo! User Interface Library which I've been getting to know and use for various sites over the past year. I'm currently at...</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/11/reboot/comments.xml</wfw:commentRss>
	<category term="Metadiscourse" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I realized I sort of fell off the blog beat here.
I've rebuilt the site (again) using the &lt;a href="http://developer.yahoo.com/yui/"&gt;Yahoo! User Interface Library&lt;/a&gt; which I've been getting to know and use for various sites over the past year.
I'm currently at the &lt;a href="http://defragcon.com/"&gt;Defrag 2007&lt;/a&gt; conference in Denver, CO and am enjoying it, it's serving (for me) as an introduction to the intersection of the current crop of social tools and enterprises.&lt;/p&gt;
&lt;p&gt;I'll post some notes from Defrag later today.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=5DLU1y"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=5DLU1y" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=2dDvTnB"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=2dDvTnB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=8XYVMWB"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=8XYVMWB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=MRCcwvb"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=MRCcwvb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/180639029" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F11%2Freboot%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/11/reboot/</feedburner:origLink></entry>
<entry>
	<title>Feedburner's Migration to Google notice</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064543/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=221" title="Feedburner's Migration to Google notice" />
	<id>tag:artific.com,2007:/202//4.221</id>
	<published>2007-06-02T17:39:49Z</published>
	<updated>2007-11-05T22:10:03Z</updated>
	<summary type="html">FeedBurner has given customers 14 days (until 15 June 2007) to either accept migration of data to Google (the default choice) or to opt-out and delete their accounts.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/06/feedburners_14_day_migration_optout_window/comments.xml</wfw:commentRss>
	<category term="Observations" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I just attempted to log into my FeedBurner account and got the following notice (in addition to the login information):&lt;/p&gt;
&lt;blockquote cite="http://www.feedburner.com/fb/a/login"&gt;&lt;p&gt;NOTE: Service of FeedBurner publisher accounts will not be interrupted as a result of the acquisition by Google. You will have a 14-day interim period ending June 15, 2007 to opt-out of allowing Google to service your account. If you take no action by June 15, 2007, the rights to your data will transfer from FeedBurner to Google. Opting out will terminate your user agreement with FeedBurner, permanently delete your FeedBurner account, feeds, and all related statistical data and history, and prevent the transfer of your data rights to Google. To opt-out, contact us via accountx@feedburner.com, provide your FeedBurner account Username, and request to have your FeedBurner account deleted. We will contact you at your registered email address to confirm your deletion request before completing it.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;While I don't object to the sale or to the company merging into the Google Borg, 14 days seems to be &lt;em&gt;awfully short&lt;/em&gt; to give notice to those who don't want to continue using FeedBurner after it becomes part of Google.  I have feeds which I ceased advertising years ago, which either return 301 redirects or 410 gone messages and they still get tens of hits per day. If you delete your FeedBurner account you can't redirect the subscribers using that account (unless you either redirect using a 302 or 307 redirect from a URL you control, or you used the feeds.&lt;em&gt;yoursitename.tld&lt;/em&gt; service, which you could simply point back to a site you control).  
With summer vacations and the vagaries of feed updates my guess is that many people or organizations who do opt-out of the FeedBurner-Google migration will lose many readers, who will just get dropped.&lt;/p&gt;
&lt;p&gt;FeedBurner should allow, for a limited time, say 60 days, the ability to opt-out in some way and redirect the feed elsewhere.&lt;/p&gt;
&lt;p&gt;An interesting exercise would be to track the people who drop their FeedBurner feeds (and accounts), picking out the feeds with the highest traffic volume and registering them for yourself (unless FB has changed to blocking re-registration of a feed URL).&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=hZyzvp"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=hZyzvp" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=RYmvgdG0"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=RYmvgdG0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=dfkJUkcd"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=dfkJUkcd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=PTEYr62o"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=PTEYr62o" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064543" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F06%2Ffeedburners_14_day_migration_optout_window%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/06/feedburners_14_day_migration_optout_window/</feedburner:origLink></entry>
<entry>
	<title>TwitterSense</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064544/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=217" title="TwitterSense" />
	<id>tag:artific.com,2007:/202//4.217</id>
	<published>2007-05-30T23:04:41Z</published>
	<updated>2008-01-27T07:30:09Z</updated>
	<summary type="html">Twitter has added Google Adsense ads to individual status messages, only visible if you're not logged into twitter.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/05/post/comments.xml</wfw:commentRss>
	<category term="Twitter" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I noticed yesterday that &lt;a href="http://twitter.com/"&gt;twitter&lt;/a&gt; has added Google Adsense ads to the individual status message pages, but only if you are not logged into twitter. 
Here's two examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unauthenticated: &lt;a href="http://cache.artific.com/202/83047932_unauth.html" onclick="window.open('http://cache.artific.com/202/83047932_unauth.html','popup','width=697,height=601,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"&gt;&lt;img src="http://cache.artific.com/202/tn_83047932_unauth.png" align="absmiddle" border="0" valign="absmiddle" width="240" height="206" alt="Thumbnail of screenshot of twitter.com" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Authenticated (no AdSense): &lt;a href="http://cache.artific.com/202/83047932_auth.html" onclick="window.open('http://cache.artific.com/202/83047932_auth.html','popup','width=697,height=601,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"&gt;&lt;img src="http://cache.artific.com/202/tn_83047932_auth.png" width="240" height="206" align="absmiddle" valign="absmiddle" border="0" alt="Thumbnail of screenshot of twitter.com" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="pc"&gt;Twitter have also added a tab to your &lt;a href="http://twitter.com/home"&gt;twitter home page&lt;/a&gt; showing "replies" (messages sent to @&lt;em&gt;username&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;ins title="20070531T1828Z"&gt;Update: fixed images and thumbnails.&lt;/ins&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=zITXTW"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=zITXTW" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=FyZ4Vpao"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=FyZ4Vpao" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=RkrlLfwk"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=RkrlLfwk" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=Nd1NnLAQ"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=Nd1NnLAQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064544" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F05%2Fpost%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/05/post/</feedburner:origLink></entry>
<entry>
	<title>How Staples.com lost my business today</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064545/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=213" title="How Staples.com lost my business today" />
	<id>tag:artific.com,2007:/202//4.213</id>
	<published>2007-05-23T18:05:15Z</published>
	<updated>2007-11-05T21:57:55Z</updated>
	<summary type="html">Staples.com's custom stamp tool pre-reqs MSIE.  Still.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/05/how_staplescom_lost_my_business/comments.xml</wfw:commentRss>
	<category term="Opinion &amp; Analysis" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;My wife and I are in the process of moving.
In the scheme of things, we're not moving all that far (approximately 660 meters if Google Earth can be trusted).
In New York City you only need to move an avenue or two to be in a completely different neighborhood.&lt;/p&gt;
&lt;p&gt;So, we're moving, and I want to get various things lined up.  
I used the &lt;a href="https://moversguide.usps.com/"&gt;U.S.P.S. online address change form&lt;/a&gt;, am forwarding all of our mail to a P.O. Box to "cleanse" our data trail in Corporate America's databanks, and am trying to figure out our broadband solution (the new building &lt;q&gt;has a T1&lt;/q&gt; we're told with no limit on the exclamations.  That might have been cool in 1998, but we have and use a 7Mbs DSL line today, which makes a piddling T1 look downright like dialup.  I digress.).&lt;/p&gt;
&lt;p&gt;I have found it handy to have a stamp with our address on it for the rare times we actually send postal mail, so I went to Staples.com to order a stamp online.
I have an account there, which is probably the only reason I thought to go there.
After tooling around the site for 30 seconds I got asked if I wanted to go to the Staples Custom Printing Shop.
On clicking "ok", I ended up at http://www.staples.marktheworld.com/browsercheck.asp, which is apparently where Staples has outsourced their custom stamp printing to.
The browsercheck.asp in the URL should give away what happened next:&lt;/p&gt;
&lt;blockquote cite="http://www.staples.marktheworld.com/browsercheck.asp"&gt;&lt;p&gt;We are sorry for the inconvenience. Our site currently supports only Internet Explorer version 4.0 or higher. This is due to the advanced features used in the product customization process.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="pc"&gt;Come on.  
I mean, sure, they probably used an ActiveX control written in 1999 to show what the stamp would look like.
And MSIE is used by, what, 80% of the worldwide marketplace?  
And they probably don't want to waste the precious investment in the ActiveX and ASP coding.
The net result is that they lost me as a customer, there is no reason, today, to be designing web applications solely for one browser platform.  None.
I will accept that if you're on a tightly controlled intranet you might consider it, but really there's just no reason for this.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=nHwb2E"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=nHwb2E" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=VKGLHbmo"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=VKGLHbmo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=lob3akWd"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=lob3akWd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=qvEIhytM"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=qvEIhytM" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064545" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F05%2Fhow_staplescom_lost_my_business%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/05/how_staplescom_lost_my_business/</feedburner:origLink></entry>
<entry>
	<title>Twitter Bug or Mis-design: location applies to all tweets</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064546/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=199" title="Twitter Bug or Mis-design: location applies to all tweets" />
	<id>tag:artific.com,2007:/202//4.199</id>
	<published>2007-05-05T14:44:29Z</published>
	<updated>2007-10-07T05:49:22Z</updated>
	<summary type="html">Twitter's location field is dynamic, meaning that statuses are not tied to the location they were posted from but instead get whatever is the user's current location.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/05/twitter_location_field/comments.xml</wfw:commentRss>
	<category term="Twitter" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I had some unexpected travel this week, spending much of Thursday and Friday driving between NYC and DC on I-95.
While in DC I was curious to see how &lt;a href="http://twitter.com/"&gt;Twitter&lt;/a&gt; handles changes to the user's location.  Your location is echoed back in your Twitter homepage as well as in the various status feeds.
&lt;a href="http://twittervision.com/"&gt;Twittervision&lt;/a&gt; uses the location field to plot tweets on a Google map.&lt;/p&gt;
&lt;p&gt;From what I can tell, Twitter only keeps the current location, and uses that to fill in the &amp;lt;location&amp;gt; field in the various feeds.  I think this is a mistake and a design flaw:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Tweets are frequently location-specific, location is part of the "content" of the tweet, it helps set the context for the tweet.&lt;/li&gt;
&lt;li&gt;If you can't depend on the location being "accurate", you can't build a service atop twitter which reliably uses the location to take action.  If I only update twitter daily and I'm travelling around a lot, I don't want to get alerts related to a tweet I posted earlier in the week from one location when I'm in a completely different city and the topic/alert would no longer be relevant.&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="pc"&gt;Now, whining aside, I can see why you wouldn't want to build a history of locations since the location is (currently) free-form.  
You'd probably want to normalize the locations, would you do that across the entire user base or on a user-by-user basis?&lt;/p&gt;
&lt;p&gt;What I would do though is store the user's location with each tweet so that locational context is preserved.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=M8kr2k"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=M8kr2k" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=M56dsqEc"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=M56dsqEc" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=j2YcxTLn"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=j2YcxTLn" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=KFzLJMCQ"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=KFzLJMCQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064546" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F05%2Ftwitter_location_field%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/05/twitter_location_field/</feedburner:origLink></entry>
<entry>
	<title>Twittering Tweets Trouble The Times' Truthseekers</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064547/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=192" title="Twittering Tweets Trouble The Times' Truthseekers" />
	<id>tag:artific.com,2007:/202//4.192</id>
	<published>2007-04-22T20:29:39Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">There doesn't have to be a there-there to play with and enjoy twitter.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/04/twittering_tweets_trouble_the/comments.xml</wfw:commentRss>
	<category term="Twitter" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I find the ongoing attempts to "get" &lt;a href="http://twitter.com/"&gt;twitter&lt;/a&gt; interesting, as if everything must have a defined purpose in order to be.  I use twitter, play around with writing code for it, and I have absolutely no idea what it will be in a year, if it's even around.&lt;/p&gt;
&lt;p&gt;The latest article is a New York Times piece &lt;a href="http://www.nytimes.com/2007/04/22/business/yourmoney/22stream.html" title="The New York Times: From Many Tweets, One Loud Voice on the Internet (22 April 2007)"&gt;From Many Tweets, One Loud Voice on the Internet&lt;/a&gt;.  The article doesn't add much to the discussion, but I did like this statement attributed to &lt;cite&gt;Evan Williams&lt;/cite&gt;: &lt;q cite="http://www.nytimes.com/2007/04/22/business/yourmoney/22stream.html"&gt;Twitter is best understood as a highly flexible messaging system that swiftly routes messages, composed on a variety of devices, to the people who have elected to receive them in the medium the recipients prefer.&lt;/q&gt;&lt;/p&gt;
&lt;p&gt;I wrote elsewhere that I could see twitter becoming a sort of personal message queuing system.  It's asynchronous, you just keep writing messages to the queue and your consumers, your readers, your receivers can get the messages on their cell or I/M immediately, or on their twitter page, your twitter page, or via a web feed.&lt;/p&gt;
&lt;p&gt;The 140 character limit imposes brevity, there's a penalty if you try sending too much information.  You just can't afford to wrap a SOAP or other XML language around your message.&lt;/p&gt;
&lt;p&gt;It's tempting to make it into something big, something major, because it must be something major to get all the attention it's receiving, right?  Why can't people just enjoy it for what it is, a simple messaging system.  You don't have to use it, you don't have to subscribe to it, it isn't required.  If you don't want to use it, then don't.&lt;/p&gt;
&lt;p&gt;The Times' writer &lt;cite&gt;Jason Pontin&lt;/cite&gt; writes:&lt;/p&gt;
&lt;blockquote cite="http://www.nytimes.com/2007/04/22/business/yourmoney/22stream.html"&gt;But I also strongly disliked the radical self-revelation of Twitter. I wasn’t sure that it was good for my intimate circle to know so much about my daily rounds, or healthy for me to tell them. A little secretiveness is, perhaps, a necessary lubricant in our social relations. I wondered whether twittering could ever have broad appeal.&lt;/blockquote&gt;
&lt;p class="pc"&gt;I recall a similar complaint about blogging.  You reveal as much or as little about yourself as you want to, no one forces you to reveal more than you choose to.&lt;/p&gt;
&lt;p class="note"&gt;My twitter account is &lt;a href="http://twitter.com/epc"&gt;twitter.com/epc&lt;/a&gt;. 
You can follow me to see when I'm walking the dogs.
Apologies for the headline.&lt;/p&gt;


&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=sYMzl9"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=sYMzl9" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=Q01BP6UR"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=Q01BP6UR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=ZQK4ChQH"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=ZQK4ChQH" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=sLX3yMkz"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=sLX3yMkz" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064547" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F04%2Ftwittering_tweets_trouble_the%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/04/twittering_tweets_trouble_the/</feedburner:origLink></entry>
<entry>
	<title>DOM templating with JavaScript?</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064548/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=187" title="DOM templating with JavaScript?" />
	<id>tag:artific.com,2007:/202//4.187</id>
	<published>2007-04-20T05:47:19Z</published>
	<updated>2008-01-27T07:30:48Z</updated>
	<summary type="html">I've been doing more and more JavaScript programming. I've run into a situation where I want to create a fragment then clone it repeatedly, changing a couple of ids and node values (picture a form with maybe ten fields, I...</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/04/dom_templating_with_javascript/comments.xml</wfw:commentRss>
	<category term="Programming" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I've been doing more and more JavaScript programming.
I've run into a situation where I want to create a fragment then clone it repeatedly, changing a couple of ids and node values (picture a form with maybe ten fields, I want to update the value of a couple of fields and the id of a couple of fields and then add the result to the DOM).&lt;/p&gt;
&lt;p&gt;It feels like overkill to walk the tree for each change.  
I kind of want to do a sprintf().
I am wondering if I can fetch the element by the technically duplicate id and change the node value and id to something else, before appending it to the tree with the original node (where the duplicate id could conflict).&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=nu5VXm"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=nu5VXm" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=otOIbjlh"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=otOIbjlh" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=4lgdxgaQ"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=4lgdxgaQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=SyNKGosv"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=SyNKGosv" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064548" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F04%2Fdom_templating_with_javascript%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/04/dom_templating_with_javascript/</feedburner:origLink></entry>
<entry>
	<title>Twitter API ideas</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064549/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=168" title="Twitter API ideas" />
	<id>tag:artific.com,2007:/202//4.168</id>
	<published>2007-03-30T06:37:28Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">Some ideas for additions to the Twitter API</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/twitter_api_ideas/comments.xml</wfw:commentRss>
	<category term="Twitter" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;I am tinkering with &lt;a href="http://twitter.com/"&gt;Twitter&lt;/a&gt; and working on something which uses the API, here's some ideas for further API enhancements:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adopt an authentication model like Flickr's for 3&lt;sup&gt;rd&lt;/sup&gt; party agents so that users can permit an agent to have access to their information or act on their behalf without having to have the user's userid and password passed to the 3rd party.&lt;/li&gt;
&lt;li&gt;Add a method to retrieve and set a user's location.  For bonus points, a method to retrieve any user's location information (or at least users who are your "friends" or "favorites").
This information is already exposed in the datastream returned from http://twitter.com/statuses/friends_timeline.xml.&lt;/li&gt;
&lt;li&gt;Add a method to retrieve &lt;em&gt;only&lt;/em&gt; the updates for a given user, or at least only "my" updates.&lt;/li&gt;
&lt;li&gt;Add a method to retrieve updates &lt;em&gt;since&lt;/em&gt; a given time.&lt;/li&gt;
&lt;li&gt;Add a method to add, remove, and forget friends (though I realize this could be horribly abused, so maybe not a great idea).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I noticed one glitch while destroying the design of my &lt;a href="http://twitter.com/epc"&gt;twitter page&lt;/a&gt;: you can change the link color, and allegedly the background color, but the background color change does not apply to all relevant elements, while the link color affects all text elements.  So for example you could set the link color to &lt;code&gt;white&lt;/code&gt; and the background to &lt;code&gt;black&lt;/code&gt; but certain fields will retain a background color of &lt;code&gt;white&lt;/code&gt; and thus all links will become invisible.&lt;/p&gt;
&lt;p&gt;I previously wrote about twitter in &lt;a href="http://artific.com/202/2007/03/twittering/"&gt;Twittering&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=dwbgfH"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=dwbgfH" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=k7eV7wPP"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=k7eV7wPP" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=vDUNKEKO"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=vDUNKEKO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=2UqwqS5m"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=2UqwqS5m" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064549" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F03%2Ftwitter_api_ideas%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/03/twitter_api_ideas/</feedburner:origLink></entry>
<entry>
	<title>ETech 2007 Day 2 p.m. sessions</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064550/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=166" title="ETech 2007 Day 2 p.m. sessions" />
	<id>tag:artific.com,2007:/202//4.166</id>
	<published>2007-03-28T23:10:03Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">Notes from: Don MacAskill of Smugmug, on privacy by Marc Hedlund of Wesabe</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/etech_2007_day_2_pm_sessions/comments.xml</wfw:commentRss>
	<category term="ETech" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;h2&gt;Don MacAskill (SmugMug) -- Set Amazon's Servers on Fire, Not Yours&lt;/h2&gt;

&lt;p&gt;Smugmug 140MM photos, no debt, profitable since first year.  192TB stored at &lt;span class="caps"&gt;S3. &lt;/span&gt; Doubling yearly.&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;S3::Simple Storage Service.  $0.15/Gb/month w/replicats. &lt;span class="caps"&gt;REST API. &lt;/span&gt; Fast, not 15K-SCSI fast, but internet fast.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Why use them?&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;not a lot of web scale expertise on planet earth&lt;/li&gt;
&lt;li&gt;reputation for systems&lt;/li&gt;
&lt;li&gt;[he] once competed with Amazon - fatbrain&lt;/li&gt;
&lt;li&gt;They eat their own dogfood.  Dozens of products.&lt;/li&gt;
&lt;li&gt;Focus on the app, not the muck.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Show me the money!&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Guestimate: ~$500k save per year&lt;/li&gt;
&lt;li&gt;Actual:
&lt;ul&gt;
&lt;li&gt;Growth: 64MM photos -&amp;gt; 140MM photos&lt;/li&gt;
&lt;li&gt;Disks would cost $40k -&amp;gt; $100k/month&lt;/li&gt;
&lt;li&gt;$922K would have been spent&lt;/li&gt;
&lt;li&gt;$230K spent instead&lt;/li&gt;
&lt;li&gt;$692K in cold, hard savings&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Nasty taxes (on capital goods)! $295K 'saved' in cash flow. Bonus!&lt;/li&gt;
&lt;li&gt;Reselling disks to recoupe dunk costs&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;this is a partial cost of ownership number&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;sweet spots&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;perfect for startups &amp;amp; small companies&lt;/li&gt;
&lt;li&gt;ideal for &lt;em&gt;store lots, serve little&lt;/em&gt; businesses of all sizes&lt;/li&gt;
&lt;li&gt;not so great (yet) for serving lots if you're a medium or large sized business.  Transfer costs high if you can buy bandwidth in 1Gbps+ chunks.&lt;/li&gt;
&lt;li&gt;We're a &lt;em&gt;store lots, serve lots&lt;/em&gt; company.  What to do?&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Like SmugFS&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Architecture remarkably similar to internal Smug filesystem&lt;/li&gt;
&lt;li&gt;Similar to lots of startups&lt;/li&gt;
&lt;li&gt;Stupid we're all building the same thing&lt;/li&gt;
&lt;li&gt;Easy to drop in&lt;/li&gt;
&lt;li&gt;Started on Monday, live in on production on Friday&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;S3 evolution&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;started just doing secondary storage.  Too cold!&lt;/li&gt;
&lt;li&gt;Tried out as Primary.  Too hot!&lt;/li&gt;
&lt;li&gt;Finally hot &amp;amp; cold model == just right!&lt;/li&gt;
&lt;li&gt;Amazon gets 100% of the data&lt;/li&gt;
&lt;li&gt;Smugmug keeps &lt;em&gt;hot&lt;/em&gt; data local (about 10%)&lt;/li&gt;
&lt;li&gt;95% reduction in # of disks bought&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Sample Request&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;they check for image in cache, if not there they log it and then retrieve the image from S3 and return to client&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Proxy vs Redirect vs Direct Links&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Build SmugMug-&amp;gt;S3 with multiple mods&lt;/li&gt;
&lt;li&gt;Can flip a switch to change&lt;/li&gt;
&lt;li&gt;Nearly 100% served are proxy reads&lt;/li&gt;
&lt;li&gt;Sometimes &lt;span class="caps"&gt;HTTP &lt;/span&gt;redirects&lt;/li&gt;
&lt;li&gt;Rarely direct S3 links&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Permissions&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;SmugMug has complicated permissions&lt;/li&gt;
&lt;li&gt;Passwords, privacy, external links&lt;/li&gt;
&lt;li&gt;Proxying allows strong protection&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;&lt;span class="caps"&gt;REST &lt;/span&gt;vs &lt;span class="caps"&gt;SOAP&lt;/span&gt;&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;loves rest, hates &lt;span class="caps"&gt;SOAP&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Lightweight&lt;/li&gt;
&lt;li&gt;Nothing useful added with &lt;span class="caps"&gt;SOAP'&lt;/span&gt;s complexity&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Reliability&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;not 100%, close though&lt;/li&gt;
&lt;li&gt;more reliable than SmugFS&lt;/li&gt;
&lt;li&gt;no service level agreement&lt;/li&gt;
&lt;li&gt;Lots of failure points:
&lt;ul&gt;
&lt;li&gt;SmugMug's datacenter&lt;/li&gt;
&lt;li&gt;Internet backbones&lt;/li&gt;
&lt;li&gt;Amazon's datacenter&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;No other software, hardware, or service [they] use is 100% reliable either&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Handling failure&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Build from day one with dailure in mind.&lt;/li&gt;
&lt;li&gt;Stuff breaks, try again&lt;/li&gt;
&lt;li&gt;Writes ail? Write locally, sync later.&lt;/li&gt;
&lt;li&gt;Reads fail? Handle Intelligently. Alerts?&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Performance&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Fast for reads and writes&lt;/li&gt;
&lt;li&gt;Mostly speed of light limited 20-80ms&lt;/li&gt;
&lt;li&gt;Parallel I/O for massive throughput. 100s of Mbps&lt;/li&gt;
&lt;li&gt;Machine measurable, human indistinguishable&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;&lt;span class="caps"&gt;CDN&lt;/span&gt;?&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;S3 is not a &lt;span class="caps"&gt;CDN&lt;/span&gt;[content delivery network]&lt;/li&gt;
&lt;li&gt;it's storage&lt;/li&gt;
&lt;li&gt;no global locations yet&lt;/li&gt;
&lt;li&gt;limited edge caching&lt;/li&gt;
&lt;li&gt;perhaps a future Amazon web service?&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;How do they do their proxy reads?&lt;/h3&gt;

&lt;p&gt;Store and forward vs stream&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;Store and forward
&lt;ul&gt;
&lt;li&gt;great resiliency&lt;/li&gt;
&lt;li&gt;poor performance&lt;/li&gt;
&lt;li&gt;if it's a big file, really poor performance&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;Stream
&lt;ul&gt;
&lt;li&gt;poor resiliency&lt;/li&gt;
&lt;li&gt;great performance&lt;/li&gt;
&lt;li&gt;do a quick &lt;span class="caps"&gt;HEAD &lt;/span&gt;first to verify&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;The speed of light problem&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;he was misquoted as saying Amazon was slow when trying to explain the speed of light&lt;/li&gt;
&lt;li&gt;Amazon has not solved fasther than light data transmission.  yet.&lt;/li&gt;
&lt;li&gt;unavoidable, make sure your application can tolerate&lt;/li&gt;
&lt;li&gt;parallelized I/O can mask problem&lt;/li&gt;
&lt;li&gt;caching can help&lt;/li&gt;
&lt;li&gt;streaming can help&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Outages and Problems&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;not perfect, five major issues&lt;/li&gt;
&lt;li&gt;3 outages of 15-30 minutes, 2 were core switch failures and one &lt;span class="caps"&gt;DNS &lt;/span&gt;problem.  Amazon.com affected.&lt;/li&gt;
&lt;li&gt;2 performance degradations.  On a smugmug customer noticed, another wasn't noticed&lt;/li&gt;
&lt;li&gt;Not a big deal, everything fails, expect it.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;&lt;span class="caps"&gt;SLA,&lt;/span&gt; Service and Support&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Smugmug do not care about &lt;span class="caps"&gt;SLA, &lt;/span&gt;but others might&lt;/li&gt;
&lt;li&gt;Service Support: One area where Amazon is weak.
&lt;ul&gt;
&lt;li&gt;This is a utility&lt;/li&gt;
&lt;li&gt;They need a service status dashboard&lt;/li&gt;
&lt;li&gt;Pro-active customer notifications&lt;/li&gt;
&lt;li&gt;Ability to get a hold of a human&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Support for developers is quite good.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;Amazon.com's customer service is good, &lt;span class="caps"&gt;AWS &lt;/span&gt;will likely catch up&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Saving SmugMug's butts&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;knocked out power to ~70TB of storage.  Oops!&lt;/li&gt;
&lt;li&gt;Moved datacenters during normal business hours, customers not affected&lt;/li&gt;
&lt;li&gt;Stupid bugs&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Miscellaneous Tips&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;use cURL
&lt;ul&gt;
&lt;li&gt;fasther&lt;/li&gt;
&lt;li&gt;more reliable&lt;/li&gt;
&lt;li&gt;storing vs streaming is simple&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;make stuff as asynchronous as possible
&lt;ul&gt;
&lt;li&gt;hides speed of light issues&lt;/li&gt;
&lt;li&gt;hides or masks problems&lt;/li&gt;
&lt;li&gt;fast customer service&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Elastic Compute Cloud (EC2)&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Like S3 but for computing
&lt;ul&gt;
&lt;li&gt;scale up or down via &lt;span class="caps"&gt;API&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;web servers, procesing boxes, development test beds, etc&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;Launching large &lt;span class="caps"&gt;EC2 &lt;/span&gt;implementation "soon"
&lt;ul&gt;
&lt;li&gt;image processing&lt;/li&gt;
&lt;li&gt;500k-1M photos/day&lt;/li&gt;
&lt;li&gt;10-20 terapixels/day processed&lt;/li&gt;
&lt;li&gt;peaky traffic on weekends, holidays&lt;/li&gt;
&lt;li&gt;ridiculously parallel&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Simple Queue Service (SQS)&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Simple, reliable queueing&lt;/li&gt;
&lt;li&gt;Mates well with &lt;span class="caps"&gt;EC2 &lt;/span&gt;and S3
&lt;ul&gt;
&lt;li&gt;Stick jobs in &lt;span class="caps"&gt;SQS&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;retrieve jobs with &lt;span class="caps"&gt;EC2 &lt;/span&gt;instances using S3 data&lt;/li&gt;
&lt;li&gt;run jobs, report status to &lt;span class="caps"&gt;SQS&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;$0.10/1000 items
&lt;ul&gt;
&lt;li&gt;Priced well for small projects&lt;/li&gt;
&lt;li&gt;gets costly for large ones (millions)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Missing Pieces&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Database &lt;span class="caps"&gt;API &lt;/span&gt;or DB grade &lt;span class="caps"&gt;EC2 &lt;/span&gt;instances
&lt;ul&gt;
&lt;li&gt;Fast (lots of local spindles, lots of &lt;span class="caps"&gt;RAM&lt;/span&gt;)&lt;/li&gt;
&lt;li&gt;Persistent&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;Load Balancer &lt;span class="caps"&gt;API&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Single IP in front of lots of &lt;span class="caps"&gt;EC2 &lt;/span&gt;instances&lt;/li&gt;
&lt;li&gt;Programmable to add/remove/change clusters&lt;/li&gt;
&lt;li&gt;Can be done with software on an &lt;span class="caps"&gt;EC2 &lt;/span&gt;instance, but painful&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;&lt;span class="caps"&gt;CDN&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Slides to be at http://blogs.smugmug.com/&lt;/p&gt;



&lt;ul&gt;
&lt;li&gt;How are they using &lt;span class="caps"&gt;EC2&lt;/span&gt;?
&lt;ul&gt;
&lt;li&gt;The &lt;span class="caps"&gt;EC2 &lt;/span&gt;instances invoke smugmug &lt;span class="caps"&gt;API&lt;/span&gt;s to do work. The SmugMug servers don't really know much about &lt;span class="caps"&gt;EC2&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;I asked: &lt;q&gt;Has their use of Amazon been an issue, either to outside investors or customers?&lt;/q&gt;
&lt;ul&gt;
&lt;li&gt;Not an issue, they have no outside investors, and further they've talked with VCs to raise the issue that startups &lt;em&gt;should&lt;/em&gt; be looking at Amazon's services (and if not, why not)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;Superninja Privacy Techniques for web Application Developers&lt;/h2&gt;

&lt;p&gt;Marc Hedlud and Brad ...? from Wesabe.  Wesabe is a personal finance web application.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; Keep critical data local.  If there's data you'd never ever ever want to lose, don't put it on a web site.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt; created a wesabe uploader for Mac/Windows to keep bank credentials on your computer.  The uploader downloads data from bank sites, strips certain data out of the files, then uploads to Wesabe.
&lt;li&gt; don't trust the site.  sensitive data filtered before it ever reaches the server.
&lt;li&gt; requires a download
&lt;li&gt; puts burden on user to maintain a secure machine (same risk as using a web browser to bank)
&lt;li&gt; if successful, risk of trojan targeting
&lt;/ul&gt;

&lt;li&gt;Use a privacy wall to separate public and private data&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt; use secret key as index in db
&lt;li&gt; secret key is only computed when user is logged in (they use hash(password + salt))
&lt;li&gt; secret key stored in session data
&lt;li&gt; other paths through the db: need to ensure that if you're using a privacy wall all transactions must traverse the privacy wall
&lt;li&gt; the data itself can leak information
&lt;li&gt; logs and exception reports can capture leaked information
&lt;/ul&gt;&lt;ul&gt;
&lt;li&gt; password changin and recovery becomes trickier 
&lt;li&gt; use a &lt;em&gt;locker&lt;/em&gt; generate a one time key for user stored in locker
&lt;li&gt; encrypt using the locker rather than the password
&lt;li&gt; troubleshooting can be harder
&lt;/ul&gt;
&lt;li&gt;Use partitioning to protect against breaches&lt;/li&gt;
&lt;ul&gt;&lt;li&gt; keep pools of sensitive data separate&lt;/li&gt;
&lt;li&gt; eg membership and financial records kept separate&lt;/li&gt;
&lt;li&gt; no relationship between them other than status&lt;/li&gt;
&lt;li&gt; reduces impact of any brach -- firewalls off anything truly identifiable&lt;/li&gt;
&lt;li&gt; allow separate politices and approaches by data type&lt;/li&gt;
&lt;li&gt; pretty much zero drawbacks other than implementation time&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;data fuzzing and log scrubbing&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt; (currently) no requirement to retain specific data on users of a server (in the US)&lt;/li&gt;
&lt;li&gt; Subpoena / warrant may require that you give up all data on a user&lt;/li&gt;
&lt;li&gt; Different countries have different data retention politices (see epic.org)&lt;/li&gt;
&lt;li&gt; filter key parameters from logs&lt;/li&gt;
&lt;li&gt; remove some of the precision of IP addresses&lt;/li&gt;
&lt;li&gt; remove precision from timestamps since they too can be used to identify someone (cf. example of whistleblower information)&lt;/li&gt;
&lt;/ul&gt;&lt;ul&gt;
&lt;li&gt; prevents leakage of passwords&lt;/li&gt;
&lt;li&gt; avoids giving attackers / law enforcement a way through the privacy wall&lt;/li&gt;
&lt;li&gt; loss of certain private data may require you to notify your customers&lt;/li&gt;
&lt;li&gt; best protection is to delete your logs&lt;/li&gt;
&lt;li&gt; important to have a public policy in place (cf link to eff.org policy information)&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt; no protection against wiretap orders&lt;/li&gt;
&lt;li&gt; difficult to cover all your bases (use centralized logging)&lt;/li&gt;&lt;/ul&gt;
&lt;li&gt; use voting algorithms to determine public information&lt;/li&gt;

&lt;ul&gt;
&lt;li&gt; "the esp game" to tag things at &lt;span class="caps"&gt;CMU.&lt;/span&gt;edu.  If two people tag something the same thing at the same time, maybe that's a good tag to apply.&lt;/li&gt;
&lt;li&gt; look at google image labeller&lt;/li&gt;
&lt;li&gt; when people agree on a term, it's common knowledge&lt;/li&gt;
&lt;li&gt; if enough people agree, it's probably publicly known&lt;/li&gt;

&lt;li&gt; private transactions shouldn't be shown on the site&lt;/li&gt;
&lt;li&gt; lots of users naming a merchange probably means it's public&lt;/li&gt;

&lt;li&gt; works on opaque information&lt;/li&gt;
&lt;li&gt; reliable -- very few faults since launch&lt;/li&gt;
&lt;li&gt; no manual work needed&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;drawbacks&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt; information is hidden until threshold met (understates available info)&lt;/li&gt;
&lt;li&gt; can leak data if threshhold is too low&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt; miscellaneous&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt; hash your passwords. don't store in plaintext.&lt;/li&gt;
&lt;li&gt; random (non-sequential) database ids.  Don't use auto-inc ids in public data.&lt;/li&gt;
&lt;li&gt; data bill of rights -- your data is your data. can export, delete, etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt; more information&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;eff guidelines for online service providers &lt;a href="http://www.eff.org/osp"&gt;http://www.eff.org/osp/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt; brad's blog: &lt;a href="http://blog.footle.org"&gt;http://blog.footle.org/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt; privacy software tools for web apps &lt;a href="http://dev.riseup.net/privacy/"&gt;http://dev.riseup.net/privacy/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=UG31dD"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=UG31dD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=1Hp9m0s9"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=1Hp9m0s9" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=pNshAgFm"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=pNshAgFm" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=Qy45atxU"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=Qy45atxU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064550" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F03%2Fetech_2007_day_2_pm_sessions%2F</feedburner:awareness><category term="SQS" scheme="http://rss.financialcontent.com/stocksymbol" /><feedburner:origLink>http://artific.com/202/2007/03/etech_2007_day_2_pm_sessions/</feedburner:origLink></entry>
<entry>
	<title>ETech 2007 Day 2 a.m. sessions</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064551/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=165" title="ETech 2007 Day 2 a.m. sessions" />
	<id>tag:artific.com,2007:/202//4.165</id>
	<published>2007-03-28T18:16:02Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">Raw notes from the morning session of Etech 2007 Day 2: Mike Kuniavsky, danah boyd, Raph Koster, Chad Dickerson</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/etech_2007_day_2_am_sessions/comments.xml</wfw:commentRss>
	<category term="ETech" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;h2&gt;Mike Kuniavsky -- The Coming Age of Magic&lt;/h2&gt;

&lt;p&gt;Ubiquitous computing design studio&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;"the hidden middle of Moore's Law".  The processing power in the middle is high and the price is at commodity levels.&lt;/li&gt;
&lt;li&gt;eg: 486 was $1000 in 1989, is $0.53 in 2007.&lt;/li&gt;
&lt;li&gt;now that &lt;span class="caps"&gt;CPU &lt;/span&gt;power is cheap enough, can put 486 power, information processing power, into commodity items&lt;/li&gt;
&lt;li&gt;ubicom allows us to embed knowledge into our tools&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;the old paradigm of terminal oriented computing does not work for ubiquitous devices &lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;animism represetnign at a gut level&lt;/li&gt;
&lt;li&gt;&lt;em&gt;animism&lt;/em&gt; means labeling inamimate objects as living, attrobuting characterisints of aniumate objects to inanimate objects (typically humans) and making predictions ore explanations about inanimate objects based on knownled about animate objects (again usually represented y human beings)&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;Sony MagicLink, running MagicCap by General Magic, circa 1995.  &lt;br /&gt;
Core development principle was to couple portable computer with networked communications.&lt;/li&gt;
&lt;li&gt;levereaged experience with Mac &lt;span class="caps"&gt;UI, &lt;/span&gt;extended desktop metaphor to portable network device metaphor&lt;/li&gt;
&lt;li&gt;used literal desktop metaphor.  stuck closely to the metaphore, like hallways, furniture&lt;/li&gt;
&lt;li&gt;ie "Downtown" as a direction.  tall shiny building as the Internet.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;how does that metaphor allow people to get work done?&lt;/li&gt;
&lt;li&gt;The desktop metaphor does not work for ubiquitous computing.  Sticking a basic unmodified PC into an everyday object will not take off.&lt;br /&gt;
Creates an information management problem on top of all the other problems the user is trying to solve.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;there must be a better way to deisgning devices for people&lt;/h3&gt;

&lt;p&gt;there must be an existing metaphor for how objects and devices interact with people&lt;/p&gt;

&lt;p&gt;there is...it's magic.  not the vast majority of magical concepts in each culture, but very specifically enchanted objects.&lt;/p&gt;

&lt;p&gt;portable network aware information processing appliances&lt;br /&gt;
p. not advocating pretending the technology is magic or that the technology works by magic&lt;/p&gt;

&lt;p&gt;what distinguishes them is the ability to have independent behavious&lt;/p&gt;

&lt;h3&gt;characteristics of "magical" objects&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;everyday&lt;/li&gt;
&lt;li&gt;familiar&lt;/li&gt;
&lt;li&gt;physical&lt;/li&gt;
&lt;li&gt;no screen (no assumption of text output, graphic output)&lt;/li&gt;
&lt;li&gt;Not human.  they have some behavior but we don't expect that to be like us.&lt;/li&gt;
&lt;li&gt;Not superhuman.  ulitmately we're in control, they're not in control of us.&lt;/li&gt;
&lt;li&gt;We don't believe in magic.  Healthy disbelief in magic.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;examples of ubicom devices&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;orb from ambient devices&lt;/li&gt;
&lt;li&gt;nokia medallion&lt;/li&gt;
&lt;li&gt;various wand devices.  that people are already using the &lt;em&gt;magic term&lt;/em&gt; wand to describe these devices&lt;/li&gt;
&lt;li&gt;enchanted rabbit - nabaztag&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Ubiquitous computing emergence is the byproduct of market forces and commodity information processing prices.&lt;br /&gt;
Easier to go with familiar patterns than to go with new ones.&lt;br /&gt;
Enchanted objects ar ethe most familiar of all.&lt;br /&gt;
metaphore is powerful, we need to be conscious of its power.&lt;/p&gt;

&lt;p&gt;Magic, good magic, does not conceal, cripple or ?? , it explains.&lt;/p&gt;

&lt;p&gt;q: can you express the dangerousness of a device to a user in terms of the metaphor&lt;br /&gt;
a: not really.  in mythology there isn't that kind of implicit relationship either.  you don't know how powerful something is just by looking at it.&lt;/p&gt;

&lt;h2&gt;danah boyd -- incantations for muggles&lt;/h2&gt;

&lt;p&gt;what happens when we start to mock the people we're creating for, does that make us "evil"&lt;br /&gt;
what are our responsibilities?&lt;/p&gt;

&lt;p&gt;perhaps we're not the wizards, perhaps we're the muggles?&lt;/p&gt;

&lt;p&gt;maybe we're trying to model things after the magic of everyday life.&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;what are the spells we cast on one another?  &lt;/li&gt;
&lt;li&gt;what are the spells that people through their practices and rituals cast upon us?&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;"if you build it they will come"  &lt;br /&gt;
what is the backside of the technology we're developing?  People&lt;br /&gt;
how to segment people to undersand that there are different people who are not like you&lt;br /&gt;
not see the world as one big homogeneous group&lt;/p&gt;

&lt;h3&gt;life stages&lt;/h3&gt;

&lt;p&gt;one way of segmenting people&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;identity formation and role-seeking
&lt;ul&gt;
&lt;li&gt;you, teens, college students&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;integration and coupling
&lt;ul&gt;
&lt;li&gt;20-somethings&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;societal contribution
&lt;ul&gt;
&lt;li&gt;professional life, marriage...&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;reflection and storytelling
&lt;ul&gt;
&lt;li&gt;retirement&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;that teens look at their parents, peers, see model roles, model&lt;br /&gt;
behaviours, see social categories.  Trying to figure out the social&lt;br /&gt;
world around them.  That we're defined by the people around us, defined&lt;br /&gt;
by civilisation and social interaction.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;that status used to be coupled with getting integrated into the work force, now they are separated&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;who am I and how can I contribute?&lt;/li&gt;
&lt;li&gt;that many young people are engaged in jobs but not careers.  Working to make ends meet.&lt;/li&gt;
&lt;li&gt;real drive for coupling around mid-twenties&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;strong myth, 1950s idea of how to exist in society (but it was a social construction even in the 1950s)&lt;/li&gt;
&lt;li&gt;gives us a goal to work towards, a cornerstone of what we're doing&lt;/li&gt;
&lt;li&gt;as we get older roles shift&lt;/li&gt;
&lt;li&gt;start to be more concerned about what matters to us, what life is about&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;it's a way of getting to the priorities people have&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;what do people care about?  Their priorities shift depending on their life stage.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;america is not like silicon valley&lt;/li&gt;
&lt;li&gt;that teens are going to social networking sites to get friends, build status&lt;/li&gt;
&lt;li&gt;move through different technologies because they meet different needs&lt;/li&gt;
&lt;li&gt;linkedin -- no value to a teenager&lt;/li&gt;
&lt;li&gt;note that there's still not many social networking sites dedicated to older generation&lt;/li&gt;
&lt;li&gt;young people want a different kind of validation than older people&lt;/li&gt;
&lt;li&gt;corporations have very different needs than technology dreamers or people.  &lt;/li&gt;
&lt;li&gt;that corporations answer to shareholders, gain more users, grow grow grow&lt;/li&gt;
&lt;li&gt;that teens are ok with ads, they understand that that's how the service is free, but make the ads relevant&lt;/li&gt;
&lt;li&gt;that growth has consequences&lt;/li&gt;
&lt;li&gt;comparison of "My So Called Life" and BtVS.  &lt;span class="caps"&gt;MSCL &lt;/span&gt;had stunning demos but not enough to be kept by &lt;span class="caps"&gt;ABC &lt;/span&gt;as it was getting only one demo and not a wide audience.  WB on the other hand realized they could focus on niche audiences and draw in broader audiences.&lt;/li&gt;
&lt;li&gt;technology companies have taken the &lt;span class="caps"&gt;ABC &lt;/span&gt;model instead of the WB model.&lt;/li&gt;
&lt;li&gt;case study: Facebook.  Used to be right of passage, then FB opened up to high schools.  "Didn't want to be on a site with his younger brother".  FB continues to open up to more and more audiences.&lt;/li&gt;
&lt;li&gt;Expansion has costs: you start to get people angry with you.  One response is lock-in, which in turn has further costs.&lt;/li&gt;
&lt;li&gt;If you tell your users that they're not valuable, they respond: by protesting, by creating fake users, by leaving your service...&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;What happens when people and technology come together?&lt;/li&gt;
&lt;li&gt;Example: soldiers in Iraq, etsy creating communities around art they create,&lt;/li&gt;
&lt;li&gt;find other people who are passionate about what they are doing&lt;/li&gt;
&lt;li&gt;started with Stage 3 people but occurring with Stage 4 folks as well&lt;/li&gt;
&lt;li&gt;of course not everything is positive.  what comes out of some user practices is not necessarily good for society&lt;/li&gt;
&lt;li&gt;for better or worse, technology reflects what's going on in the real world and some of it is ugly.&lt;/li&gt;
&lt;li&gt;sites dedicated to people who have died, becoming proof of existence for their peers who continue to interact and respond on places like the decedents myspace page&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;social media are people&lt;/li&gt;
&lt;li&gt;social media reflects existing practices and modify these practices&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;some characteristics of social media&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;persistence -- that comment from 1995 can still be found&lt;/li&gt;
&lt;li&gt;searchability -- your future employer can find your frat party hijinks&lt;/li&gt;
&lt;li&gt;replicability -- can't tell the original from the duplicate.  &lt;/li&gt;
&lt;li&gt;invisible audiences -- no sense of who you are talking to when you're online.  don't know the social context of what's going on.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;what does it mean to apply these scales to individual interactions&lt;/li&gt;
&lt;li&gt;offline we had physical walls&lt;/li&gt;
&lt;li&gt;can determine what norms exist within certain boundaries&lt;/li&gt;
&lt;li&gt;way we communicate determined by environment around us&lt;/li&gt;
&lt;li&gt;what happens when it is online, you lose the context&lt;/li&gt;
&lt;li&gt;how do you train a generation to speak to all people all the time&lt;/li&gt;
&lt;li&gt;we are always "in public" but there are different modes of operation depending on the context.&lt;/li&gt;
&lt;li&gt;online the social context is not as well-formed&lt;/li&gt;
&lt;li&gt;can't go into ostrich mode&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;eveyrthing we understand about public and private separations is changing due to technology&lt;/li&gt;
&lt;li&gt;young people are taking this and running with it, even if we don't understand all of the implications of the technology we have created&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;what does it mean that you have so many audiences, how many can you follow?&lt;/li&gt;
&lt;li&gt;twitter: cognitive overload.  is it really building social relationships?&lt;/li&gt;
&lt;li&gt;will your twitter friends be there when you're in a crisis?&lt;/li&gt;
&lt;li&gt;twitter gives a way to feel you have presence&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;what does it mean that we have all of these technologies that create more and more influx of information?&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;mobile brings with it location data, presence data.  will radically shift practice.  &lt;/li&gt;
&lt;li&gt;people will figure things out, may not be the healthiest plans&lt;/li&gt;
&lt;li&gt;we through technologyu are shifting and changing the architecture of society and people are figuring out how to work around it for better or worse&lt;/li&gt;
&lt;li&gt;as technologists, do we go into ostrich mode or do we engage with how our architecture changes society&lt;/li&gt;
&lt;li&gt;what happens when magic goes both ways, it is not all positive, it has repercussions on society.  What happens to the star wars kid?  What happesn to the guy fired for blogging?&lt;/li&gt;
&lt;li&gt;What are the consequences and how do you prepare for them?&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;how do we make a community that we love to be a part of?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;second half of morning&lt;/p&gt;

&lt;h2&gt;Raph Koster &lt;/h2&gt;

&lt;p&gt;things that work have underlying structure.  They have a grammar. Example: Solar by Miles Davis.  &lt;/p&gt;

&lt;p&gt;When somthing works, it works at many levels.&lt;/p&gt;

&lt;p&gt;Things can be desconstructed into smaller things.  Songs are made of smaller songs.  Sentences decompose into &lt;span class="caps"&gt;SVO, &lt;/span&gt;then words, then syllables, then phonemes, then letters.&lt;/p&gt;

&lt;p&gt;Games are made out of games.&lt;/p&gt;

&lt;p&gt;games are designed to evoke fun.  Each individual game within a game has to evoke fun, to enterain.&lt;/p&gt;

&lt;p&gt;Fun as a chemical response.  Fun also arises because of certain characteristics.  You're meeting a challenge, understanding how it is presented, mastering how the model works.&lt;/p&gt;

&lt;p&gt;Research shows four types of fun:&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;hard&lt;/li&gt;
&lt;li&gt;easy&lt;/li&gt;
&lt;li&gt;visceral&lt;/li&gt;
&lt;li&gt;social&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;or:&lt;/p&gt;

&lt;table&gt;&lt;tr&gt;&lt;td&gt;Hard&lt;/td&gt;&lt;td&gt;Easy&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Visceral&lt;/td&gt;&lt;td&gt;Social&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;

&lt;p&gt;games focus on hard fun, tough problems and making you solve them&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Hard fun grammar&lt;/em&gt;: Hard fun is about solving problems&lt;br /&gt;
games are about making choices, interactive design.&lt;/p&gt;

&lt;h3&gt;the magic ingredients&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;Territory
&lt;ul&gt;
&lt;li&gt;Where you interact should matter&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Preparation
&lt;ul&gt;
&lt;li&gt;when you interact should matter, previous interactions should take into account&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Core Mechancic
&lt;ul&gt;
&lt;li&gt;how should matter&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Range of challegense
&lt;ul&gt;
&lt;li&gt;what &lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Choice of abilities
&lt;ul&gt;
&lt;li&gt;With? should matter. What tools you have should matter, should feel different.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Variable Feedback
&lt;ul&gt;
&lt;li&gt;For?  What you are buying for should matter.  There should be feedback&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Bad return on investment
&lt;ul&gt;
&lt;li&gt;Few? Sometimes you don't get what you want&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Cost of failure
&lt;ul&gt;
&lt;li&gt;Phooey: game needs to tell you that you failed at something.  Fun comes from learning, and failure is important in learning.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;How? &lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;The core &lt;span class="caps"&gt;VERB &lt;/span&gt;has to be repeatable.  if it isn't something people care to do over and over again people will cease to use it.&lt;/li&gt;
&lt;li&gt;Something that requires &lt;em&gt;Skill&lt;/em&gt;.  In order to learn you have to &lt;em&gt;feel&lt;/em&gt; you are growing more competent.&lt;/li&gt;
&lt;li&gt;Something that can handle &lt;em&gt;statistical variation&lt;/em&gt;.  What you want is for the game to acknowledge the fact that some tasks are more difficult than others though they seem to be the same.  &lt;/li&gt;
&lt;li&gt;Something that is &lt;em&gt;competitive&lt;/em&gt;.  You're competing against others, against yourself.  Ratings, metrics, and other people need to see it.&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;When&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Everything you did before must matter&lt;/em&gt;.  The system needs to remember what you did before.&lt;/li&gt;
&lt;li&gt;Whatever the opponent last did to you should matter too.   &lt;em&gt;Never start an interaction with no &lt;strong&gt;context&lt;/strong&gt;&lt;/em&gt;.  What else has the user already done?&lt;/li&gt;
&lt;li&gt;The user should be able to prepare for the encounter &lt;em&gt;in different ways&lt;/em&gt;.  Need to prepare different ways for taking on a challenge.&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;Where&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;The territory and topology should affect the outcome&lt;/li&gt;
&lt;li&gt;doing the same thing in different places should make a difference.  &lt;em&gt;The same challenge in different locales should be a fresh scenario.&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;What&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;The same verb must be applicable to many different challenges.&lt;/li&gt;
&lt;li&gt;think of a verb as a hammer.  You should present users with lots of kinds of &lt;em&gt;Nails&lt;/em&gt;.&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;with&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;Users should be able to solve the challenge with their choice of tools.&lt;/li&gt;
&lt;li&gt;And you should reward them with different feedback for it.  The feedback should be tailored to the tools and context even if the task has been performed before.  The path by which users come should be acknowledged.&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;All of the above can be quantified.  You can arrive at a statistical measure, a rating, for every challenge.  You can them some up the difficulty.&lt;/p&gt;

&lt;h4&gt;For?&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;games with only one outcome are ...boring&lt;/li&gt;
&lt;li&gt;variable feedback keeps things lively&lt;/li&gt;
&lt;li&gt;usually the best feedback is a greater challenge presented by the opponent&lt;/li&gt;
&lt;li&gt;sometimes it's a pleasant surprise.&lt;/li&gt;
&lt;li&gt;either way, it has to be highly visible.  Others need to know, it draws and drives participation.&lt;/li&gt;
&lt;li&gt;bottomfeeding is bad for fun.&lt;/li&gt;
&lt;li&gt;low risk activity for high reward is bad for fun.&lt;/li&gt;
&lt;li&gt;you need to drive users to challenges at the edge of ability&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;phooey&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;making a wrong choice has to be a setback.  need to realize you've done a wrong thing.&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;The absence of any of these features makes &lt;em&gt;any&lt;/em&gt; form of interaction less fun.&lt;/p&gt;

&lt;h2&gt;Chad Dickerson -- Hacking Yahoo!&lt;/h2&gt;


&lt;ul&gt;
&lt;li&gt;Hack Day at Yahoo!, extending the formula inside out&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;hack day rules&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;build something in 24 hours, no power points&lt;/li&gt;
&lt;li&gt;present it to everyone in 90 seconds&lt;/li&gt;
&lt;li&gt;no prior review of projects, anything goes&lt;/li&gt;
&lt;li&gt;that's it&lt;/li&gt;
&lt;li&gt;100s of prototypes built&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Why do Open Hack day?&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;build more engaged community around &lt;span class="caps"&gt;YDN&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;share the spirit of internal hack days&lt;/li&gt;
&lt;li&gt;create excitement about Yahoo's &lt;span class="caps"&gt;API&lt;/span&gt;s&lt;/li&gt;
&lt;li&gt;leverage the capabilityes and scale of Yahoo! to deliver uniqely compelling event&lt;/li&gt;
&lt;li&gt;We had been opening Yahoo! &lt;span class="caps"&gt;APIS, &lt;/span&gt;why not open Yahoo itself&lt;/li&gt;
&lt;li&gt;show yahoo on a personal level&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;hack day cycle of innovation&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;yahoo creates new apis&lt;/li&gt;
&lt;li&gt;battle tested &lt;span class="caps"&gt;API&lt;/span&gt;s exposed to new users&lt;/li&gt;
&lt;li&gt;&lt;span class="caps"&gt;YDN &lt;/span&gt;developers hack on the apis to create new things&lt;/li&gt;
&lt;li&gt;and a bullet that went by too quickly to capture&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;made Yahoo! developers available, stayed up all night with the "hackers".&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;brought in entertainment, Beck&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;open request for invite for only 400 slots, no fee&lt;/li&gt;
&lt;li&gt;simple criterion:
&lt;ul&gt;
&lt;li&gt;will you be building something using at least on Yahoo! &lt;span class="caps"&gt;API&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;geographic diversity -- not just the usual Silicon Valley crowd&lt;/li&gt;
&lt;li&gt;rapid fire demos, no prescreen, no powerpoints&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;hacking your company's cultural "software"&lt;/li&gt;
&lt;li&gt;invited competitors&lt;/li&gt;
&lt;li&gt;got strong emotional responses from attendees&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;overclocking your facility's "hardware"&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;a lot of amazing talent held within your organization&lt;/li&gt;
&lt;li&gt;they let people camp on the holy grass at Yahoo!  Convincing groundskeepers that sleeping on grass was ok.&lt;/li&gt;
&lt;li&gt;had to make sure environment supported having hacking contest onsite, turning off sprinklers for example&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Surprises&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;left event really open&lt;/li&gt;
&lt;li&gt;class friday, hack saturday, present hacks saturday evening&lt;/li&gt;
&lt;/ul&gt;



&lt;h4&gt;prizes&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;Blogging in Motion: purse using pedometer and cell phone to upload photo every 100 steps to flickr www.blogginginmotion.com&lt;/li&gt;
&lt;li&gt;&lt;em&gt;ybox&lt;/em&gt; turned old tv into image display www.uncommonprojects.org/ybox&lt;/li&gt;
&lt;li&gt;the puppets, made fun of Yahoo! and Silicon Valley work culture in Beck provided video&lt;/li&gt;
&lt;li&gt;q. to be open you have to be open to people making fun of you and your culture&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Another beck video http://yodel.yahoo.com/2006/09/30/the-hackers-are-here/ [um, potentially nsfw, masturbating puppet video]&lt;/p&gt;

&lt;h4&gt;feedback&lt;/h4&gt;


&lt;ul&gt;
&lt;li&gt;Yahoo! as Punk Rock (Brooke Maury)&lt;/li&gt;
&lt;li&gt;one of the most difficult aspects was getting the local news to understand what was going on.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=ltWy9P"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=ltWy9P" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=Fdr0Iryu"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=Fdr0Iryu" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=QxpDAawN"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=QxpDAawN" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=T3iPaAwv"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=T3iPaAwv" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064551" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F03%2Fetech_2007_day_2_am_sessions%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/03/etech_2007_day_2_am_sessions/</feedburner:origLink></entry>
<entry>
	<title>Notes from etech Day 1, Morning Session [27 March 2007]</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064552/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=163" title="Notes from etech Day 1, Morning Session [27 March 2007]" />
	<id>tag:artific.com,2007:/202//4.163</id>
	<published>2007-03-28T16:49:44Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">Raw notes from the morning session of ETech 2007 Day one with talks by Jeff Jonas, Werner vogels, Jane McGonigal, and Jeff Hawkins and a discussion amongst Tim O'Reilly, Peter Bloom and Bill Janeway.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/etech20070327am/comments.xml</wfw:commentRss>
	<category term="ETech" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;These are my raw notes from Day 1's morning session  I think I have edited out any extraneous comments.  

&lt;h2&gt;Jeff Jonas -- &lt;span class="caps"&gt;IBM&lt;/span&gt;&lt;/h2&gt;

&lt;p&gt;Real time trip wires: black list + all other known possible problem makers and mix it into a mashup&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;Problem of enterprise amnesia: database silos, thief databases not merged with employee dbs or marketing dbs.&lt;/li&gt;
&lt;li&gt;"Perception isolation" -- leading cause of enterprise unintelligence&lt;/li&gt;
&lt;li&gt;"Perception integration" means integrated context&lt;/li&gt;
&lt;li&gt;Want a system to observe and publish discoveries.&lt;/li&gt;
&lt;li&gt;more intelligent systems created when you put data and persistent queries into the same data space.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;notion of "perceptual analytics"&lt;/li&gt;
&lt;li&gt;"relevance finds the consumer"&lt;/li&gt;
&lt;li&gt;"when data and queries are treated the same then queries find queries"&lt;/li&gt;
&lt;li&gt;observation that .6% difference between humans andchimpanzees, no wonder information systems are so screwed.&lt;/li&gt;
&lt;li&gt;federated search hopeless for just in time context if trying to deliver enterpsie intelligence&lt;/li&gt;
&lt;li&gt;must have enough features for context construction&lt;/li&gt;
&lt;li&gt;can't bulk load data, must incrementally lean&lt;/li&gt;
&lt;li&gt;"sequence neutrality" -- no matter the order of arrival of the data, the end state remains the same.&lt;/li&gt;
&lt;li&gt;need to fix the past, fix connections as you load data.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;notion that dreaming is deep recontextualisation&lt;/li&gt;
&lt;li&gt;has a blog&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;how to handle ambiguity -- add more observations&lt;/li&gt;
&lt;/ul&gt;



&lt;h2&gt;Bill Janeway, Peter Bloom, Tim &lt;span class="caps"&gt;O'R&lt;/span&gt;eilly&lt;/h2&gt;


&lt;ul&gt;
&lt;li&gt;bloom: that there's three themes: 
&lt;ul&gt;
&lt;li&gt;extracting signal from noise&lt;/li&gt;
&lt;li&gt;reduction of latency&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;That &lt;span class="caps"&gt;NYSE &lt;/span&gt;trades average 30 ms, hedge funds demand 1000 trades/second&lt;/li&gt;
&lt;li&gt;Even in the era of the internet location matters, example of company moving transaction server closer to &lt;span class="caps"&gt;NYSE &lt;/span&gt;to shave 10ms off tp.&lt;/li&gt;
&lt;li&gt;Example of India prohibiting electronic communication between markets.  Solution was to have guys watching two screens and typing in to two systems at the same time to do the arbitrage.  Ie, Mechanical Turk&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;generation focused on transactional efficiency&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;war game over exposure to quais-proprietary information, who owns that and what to do with that?&lt;/li&gt;
&lt;li&gt;notion that hedge funds give up their "clickstream" to prime brokers, hedge funds use alternative trading systems to try to hide their trading data from others&lt;/li&gt;
&lt;li&gt;preserving anonymity by breaking apart transactions across multiple markets&lt;/li&gt;
&lt;li&gt;"dark pools of liquidity"&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;"tradestation" -- all of the former proprietary data is available now in consumer package for $100.  users can trade models with each other.  darwinian evolution of trading models.&lt;/li&gt;
&lt;li&gt;reminder that in answer o the 87 crash due to program trading imposition of hard stops.&lt;/li&gt;
&lt;li&gt;slow down of markets during crises, is it a problem or a way of enforcing liquidity?&lt;/li&gt;
&lt;li&gt;removing latency means there's less time for you to reconsider your decision if it was a mistake&lt;/li&gt;
&lt;/ul&gt;



&lt;h2&gt;werner vogels, cto of amazon&lt;/h2&gt;


&lt;ul&gt;
&lt;li&gt;"web scale computing" , building your business around ideas and not resources&lt;/li&gt;
&lt;li&gt;sales pitch for amazon's services&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;computing, storage, queuing&lt;/li&gt;
&lt;li&gt;pay-go&lt;/li&gt;
&lt;li&gt;&lt;span class="caps"&gt;GWA &lt;/span&gt;for real systems&lt;/li&gt;
&lt;li&gt;claims 99.9% availability&lt;/li&gt;
&lt;li&gt;amazon machine image -- how does this compare to media temple's grid service?&lt;/li&gt;
&lt;li&gt;sharing of machine images by community&lt;/li&gt;
&lt;li&gt;switch to rightscale.com demo &lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;Jane McGonigal&lt;/h2&gt;

&lt;p&gt;url: www.avantgame.com/happiness . hacking the real world to be more like a game&lt;/p&gt;

&lt;p&gt;What are the design strategies for showing users alternate realities?&lt;/p&gt;

&lt;p&gt;technologists as happiness hackers&lt;/p&gt;

&lt;h3&gt;future forecast&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;quality of life as the primary metric for evaluating everyday technologies&lt;/li&gt;
&lt;li&gt;positive psychology as a principla explcit influence on design&lt;/li&gt;
&lt;li&gt;public expectation that tech companies have a vision for life worth living&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;science of happiness&lt;/h3&gt;

&lt;p&gt;"three realms of happiness"&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;pleasure - satisfaction&lt;/li&gt;
&lt;li&gt;engagement - immersion, responsive systems&lt;/li&gt;
&lt;li&gt;meaning: having a powerful role in the world at large&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;how does engagement in second life, games, influence real life?&lt;/li&gt;
&lt;li&gt;ubiquitous, alternate reality games, activating the world around us&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;example: ministry of reshelving (flickrtag:reshelving) move "1984" from fiction to &lt;span class="caps"&gt;U.S. &lt;/span&gt;history, current events, etc.&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;example: assassin with random acts of kindness.&lt;/li&gt;
&lt;li&gt;using games to teach interaction in the social environment&lt;/li&gt;
&lt;li&gt;"world without oil" alternate reality for the public good. 4/30/07&lt;/li&gt;
&lt;li&gt;worldwithoutoil.org&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;"the new games are supergames" &lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;super sized, massive scale, lot of people engaged, online collective intelligences&lt;/li&gt;
&lt;li&gt;superimposed (hybrid experience)&lt;/li&gt;
&lt;li&gt;suerpheroic (real place, not role play)&lt;/li&gt;
&lt;li&gt;supercomputing (parallel problem solving and collective action)&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;notion of being part of something bigger&lt;/li&gt;
&lt;li&gt;one common design trait is that there is a call to action to work towards a larger goal.&lt;/li&gt;
&lt;li&gt;search for shared meaning&lt;/li&gt;
&lt;li&gt;ubiquitous games more popular with female players than you see in video games&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;happiness measures&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;UPenn measures, via questions/statements:
&lt;ul&gt;
&lt;li&gt;"I am optimistic about the future&lt;/li&gt;
&lt;li&gt;I feel close to most people even if I do not know them well&lt;/li&gt;
&lt;li&gt;I feel that ....this makes the world a better place.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;Six happiness classes&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;wisdom&lt;/li&gt;
&lt;li&gt;courage&lt;/li&gt;
&lt;li&gt;humanity&lt;/li&gt;
&lt;li&gt;justice&lt;/li&gt;
&lt;li&gt;temperence&lt;/li&gt;
&lt;li&gt;transcendance&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;do our technologies pass the "death bed test"&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;happiness gained by assessing life backwards&lt;/li&gt;
&lt;li&gt;How will the time spent with our technologies look in retrsospect?  What kind of life will our technologies have enabled, supported?&lt;/li&gt;
&lt;/ul&gt;



&lt;blockquote&gt;&lt;p&gt;Invest a portion of your timeenergy and resources towards undersand and innovating happieness, it's the new capital. &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;make your technology not only feel good but also do good and expose good&lt;br /&gt;
...two more that i didn't catch, but slides at http://avantgame.com/happiness&lt;/p&gt;

&lt;h2&gt;jeff hawkins&lt;/h2&gt;


&lt;ul&gt;
&lt;li&gt;cofounder of numenta&lt;/li&gt;
&lt;li&gt;&lt;em&gt;why can't a computer be more like a brain?&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;have no computers today that you can show a picture and say what is this, where humans can do&lt;/li&gt;
&lt;li&gt;no computers that can understand language or talk like a human&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;why are computers unable to do what brains do?&lt;/h3&gt;

&lt;p&gt;suppositons:&lt;/p&gt;


&lt;ol&gt;
&lt;li&gt;computers are not powerful enough&lt;/li&gt;
&lt;li&gt;brains are too complex to understand&lt;/li&gt;
&lt;li&gt;brains work on quantum principles&lt;/li&gt;
&lt;li&gt;brains are "magic"&lt;/li&gt;
&lt;/ol&gt;





&lt;ul&gt;
&lt;li&gt;representations built hierarchically, need to build model of the world&lt;/li&gt;
&lt;li&gt;built from the sensory data, learned.&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;hierarchical temporal memory (HTM)&lt;/h3&gt;


&lt;ul&gt;
&lt;li&gt;a theory of how neocortex works&lt;/li&gt;
&lt;li&gt;&lt;span class="caps"&gt;HTM &lt;/span&gt;also a technology
&lt;ul&gt;
&lt;li&gt;hierarchy of memory nodes&lt;/li&gt;
&lt;li&gt;learns by exposure to sensory patterns&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;



&lt;h3&gt;how does htm work?&lt;/h3&gt;


&lt;ol&gt;
&lt;li&gt;creats a model of its world&lt;/li&gt;
&lt;li&gt;recognizes new patterns&lt;/li&gt;
&lt;li&gt;predicts&lt;/li&gt;
&lt;li&gt;generates behavior, &lt;/li&gt;
&lt;/ol&gt;





&lt;ul&gt;
&lt;li&gt;numenta platform for intelligent computing&lt;/li&gt;
&lt;li&gt;kind of losing the thread here.&lt;/li&gt;
&lt;li&gt;demo of pattern recognition.&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;applications against precise timing or high order temporal data.  See http://www.numenta.com &lt;/p&gt;

&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=zAd3aa"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=zAd3aa" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=aXuchlBf"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=aXuchlBf" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=lJr8KUfM"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=lJr8KUfM" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=cWSLCmvi"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=cWSLCmvi" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064552" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F03%2Fetech20070327am%2F</feedburner:awareness><category term="HTM" scheme="http://rss.financialcontent.com/stocksymbol" /><feedburner:origLink>http://artific.com/202/2007/03/etech20070327am/</feedburner:origLink></entry>
<entry>
	<title>Some ideas about authentication</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064553/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=162" title="Some ideas about authentication" />
	<id>tag:artific.com,2007:/202//4.162</id>
	<published>2007-03-28T09:07:31Z</published>
	<updated>2008-01-27T07:31:42Z</updated>
	<summary type="html">Outline of some ideas I have had about enabling robots to register for authenticated access to resources and branching into automating authentication for traditional browser user agents.</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/some_ideas_about_authenticatio/comments.xml</wfw:commentRss>
	<category term="Authentication &amp; Identity" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;Several years ago a friend posed this problem: her corporate intranet team was mandated to use the in-house search engine.  This search engine had a fatal flaw: it had no way to index entitled or authenticated content, thus much of the company's intranet was invisible and not showing up in the search engine.  Some solutions had been discussed: dual path the authentication code so permit access by the crawler, hardcode userids and passwords into the crawler, temporarily turn off authentication when the crawler did an index run.  None were really practical: the company had a distributed intranet, there were hundreds of web sites with different sorts of authentication in use; hardcoding information is just asking for trouble as is temporarily turning off the security.&lt;/p&gt;
&lt;p&gt;Although my friend has since left that company, I have been thinking about the problem since then, toying with solutions, thinking up variations, but never really putting ink to paper so to speak.&lt;/p&gt;
&lt;p&gt;What started as a question about allowing robots access to entitled content digressed into issues about automatically registering and authenticating any user agent to such content, and in turn authenticating agents between web services and authenticating agents as proxies for users.&lt;/p&gt;
&lt;p&gt;Although identity and authentication are of interest to me, they're not my specialty and I readily concede not being up to the minute with the latest information about &lt;a href="http://openid.net/"&gt;OpenID&lt;/a&gt; or Cardspace.  So I offer the following ideas with this disclaimer: they're just ideas, I do not claim any originality, I just would like to see if we can push solutions a bit quicker.&lt;/p&gt;
&lt;p&gt;The ideas are briefly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automating the registration and authentication of robots and web crawlers to entitled content or what I call "robots.xml".&lt;/li&gt;
&lt;li&gt;Automating the registration and authentication of consumers to entitled content, "agents.xml".&lt;/li&gt;
&lt;li&gt;Use public keys to sign requests from agents to web APIs instead of asking users to submit their userid and passwords to third party sites.&lt;/li&gt;
&lt;li&gt;Use browser based public keys to sign agent requests to authorize agents to act as proxies for the consumer.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I outline the first two ideas below and plan to expand on them in future posts.  The last two (using public keys for API requests) need some more thought put into them.  I think where my head is at is using the &lt;a href="http://www.flickr.com/services/api/"&gt;flickr API&lt;/a&gt; as a starting point, but standardizing on a PGP or S/MIME signature to sign requests rather than have each service come up with a different signature method.&lt;/p&gt;
&lt;p class="note"&gt;&lt;ins title="20070328T1723Z"&gt;Note: this has been modified to correct an error about &lt;em&gt;which&lt;/em&gt; status code could return authentication metadata (from &lt;code&gt;403&lt;/code&gt; to &lt;code&gt;401&lt;/code&gt;).&lt;/ins&gt;&lt;/p&gt;
&lt;h2&gt;robots.xml&lt;/h2&gt;
&lt;p&gt;My initial solution to my friend's problem was to update the &lt;a href="http://www.robotstxt.org/wc/exclusion.html#robotstxt"&gt;Robot Exclusion Protocol&lt;/a&gt;.  Move from a flat ASCII text file format to an XML format, add in some elements to designate protected URLs and other elements to designate authentication methods, mix in a few complaints which have arisen over the years about robots.txt, simmer with a few demonstration APIs and then try to convince every automated agent to adapt a new REP.&lt;/p&gt;
&lt;p&gt;As I have thought about it, instead I think what I would propose is an extension to Google's &lt;a href="http://www.sitemaps.org/"&gt;Sitemaps protocol&lt;/a&gt; to add in elements to denote what URLs are protected (perhaps &amp;lt;authenticate&amp;gt; or &amp;lt;entitle&amp;gt;?) and where the agent should go to register and request an authentication token.  I would add a few additional stanzas or elements requesting (and presenting) contact and support information, something sorely lacking in the relationship between robots and sites today.  Finally you'd want an element describing what the robot can do with the content (index?  cache?).&lt;/p&gt;
&lt;p&gt;A complying server would respond to a request for an authenticated document with a standard HTTP &lt;del title="20070328T1723Z"&gt;403&lt;/del&gt; &lt;ins title="20070328T1723Z"&gt;401&lt;/ins&gt; status, but include a reference to the robots.xml or sitemaps file covering the URL in a &amp;lt;link&amp;gt; element.  Perhaps something like:&lt;/p&gt;
&lt;blockquote class="code"&gt;&amp;lt;link rel="authentication" href="http://example.com/sitemap.xml"&amp;gt;&lt;/blockquote&gt;
&lt;p&gt;A complying user agent would not request the sitemap file until it received a &lt;del title="20070328T1723Z"&gt;403&lt;/del&gt; &lt;ins title="20070328T1723Z"&gt;401&lt;/ins&gt; status response.  Only then would it look for a sitemap file (relying either on a Link: HTTP header or a &amp;lt;link&amp;gt; element in the response).&lt;/p&gt;
&lt;p&gt;I will write about this in more detail in a separate post.  My goal with this proposal would be to create a standard, XML based, method and process for granting access to authenticated content.&lt;/p&gt;
&lt;h2&gt;agents.xml&lt;/h2&gt;
&lt;p&gt;Once you have an automated means to request and grant access to authenticated content for use by robots, why not extend it to users as well?  For starters, you likely want to collect different information from a robot than from a user.  Secondly users are more concerned about their privacy and may not want to be automatically registered or logged into a web site.&lt;/p&gt;
&lt;p&gt;Many browsers today support semi-automated authentication: they offer to store a "userid" and "password" if they encounter a form with an input element of type password.  However, in some testing I did last year I discovered that browsers will typically take the field immediately "next to" the password field, without regard to whether it really is or is not the "userid" that matches the password.&lt;/p&gt;
&lt;p&gt;What I propose then is a variation on the extended sitemaps.xml file, call it agents.xml if you need a name.&lt;/p&gt;
&lt;p&gt;A complying server would respond to a request for authenticated content with a 403 status.  In addition to the &amp;lt;link&amp;gt; element provided for robots, we add a second &amp;lt;link&amp;gt; element for non-robot user agents.&lt;/p&gt;
&lt;p&gt;A complying user agent would retrieve the agents.xml file, parse it, determine whether or not it has registered for the site previously (if so, use the cached identification information to attempt to log into the site).  If it hasn't registered before it should prompt the user to confirm if it should register automatically, disclosing what information the site is requesting and submitting a registration request once confirmed.&lt;/p&gt;
&lt;p&gt;This is very similar to what &lt;a href="http://www.identityblog.com/"&gt;Kim Cameron&lt;/a&gt; of Microsoft has proposed &lt;a href="http://msdn2.microsoft.com/en-us/netframework/aa663320.aspx"&gt;Cardspace&lt;/a&gt;.  I need to delve into the Cardspace documents because I think that there is a there there that I've ignored due to an aversion to all things WS-* and Soap. &lt;/p&gt;
&lt;p&gt;One difference is that I personally think it is bad web server form to use redirects to deny access to a resource.  Where Cardspace uses redirects to a login form, I would use a &lt;ins title="20070328T1723Z"&gt;401&lt;/ins&gt; status.&lt;/p&gt;
&lt;p&gt;A second difference is that I think that we should provide a way to automate registration and authentication to sites which are not ready to jump to third party authentication.  If a site wishes to use userid / password authentication (granting access either through Basic / Digest authentication or Cookie based authentication) then so be it.  Yes it is a pain, and it does not relieve us of the multiple userid/password problem, but if a site could cogently describe the endpoints for authentication and the rules for the userid, password, and other registration fields, browsers could intelligently managed one's account space and create smarter browser based account managers.&lt;/p&gt;
&lt;p&gt;Nothing in this solution should preclude using OpenID, Cardspace, or whatever else comes along.  The server should indicate what authentication methods it supports.  The user agent should determine which methods it supports and either automatically authenticate or display the site's &lt;ins title="20070328T1723Z"&gt;401&lt;/ins&gt; error page which presumably would contain links to a non-automated registration scheme.&lt;/p&gt;
&lt;p&gt;Again, I plan to write this up in more detail and work on some prototype implementations. 
I would like to read some more about Cardspace and the &lt;a href="http://openid.net/specs/openid-simple-registration-extension-1_0.html"&gt;simple registration extensions to OpenID&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://feeds.artific.com/~a/202Accepted?a=HG3IlC"&gt;&lt;img src="http://feeds.artific.com/~a/202Accepted?i=HG3IlC" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.artific.com/~f/202Accepted?a=7hfubClE"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=7hfubClE" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=rFxxnbDU"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=rFxxnbDU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.artific.com/~f/202Accepted?a=Jum3Ukzk"&gt;&lt;img src="http://feeds.artific.com/~f/202Accepted?i=Jum3Ukzk" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.artific.com/~r/202Accepted/~4/139064553" height="1" width="1"/&gt;</content>
<rights type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Copyright 2007 Artific Consulting LLC.</p>
<p>Licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5</a> license.</p></div></rights>
<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=202Accepted&amp;itemurl=http%3A%2F%2Fartific.com%2F202%2F2007%2F03%2Fsome_ideas_about_authenticatio%2F</feedburner:awareness><feedburner:origLink>http://artific.com/202/2007/03/some_ideas_about_authenticatio/</feedburner:origLink></entry>
<entry>
	<title>Following etech</title>
	<link rel="alternate" type="text/html" href="http://feeds.artific.com/~r/202Accepted/~3/139064554/" />
	<link rel="edit" type="application/atom+xml" href="https://artific.com/scripts/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=160" title="Following etech" />
	<id>tag:artific.com,2007:/202//4.160</id>
	<published>2007-03-27T16:47:39Z</published>
	<updated>2007-10-07T00:50:17Z</updated>
	<summary type="html">As I wrote early I'm not live-blogging, I find I stop listening to the presentations and conversations and end up being a conduit for words. Nice for the blog, but that's not why I'm here. To that end, I set...</summary>
	<author>
		<name>Ed Costello</name>
		<uri>http://epcostello.net/ego/</uri>
		<email>contact@artific.com</email>
	</author>
	<wfw:commentRss>http://artific.com/202/2007/03/following_etech/comments.xml</wfw:commentRss>
	<category term="ETech" />

	<content type="html" xml:lang="en" xml:base="http://artific.com/202/">
&lt;p&gt;As I 