<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss1full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Reading</title>
    <link>http://pinboard.in//u:cloudseer/t:shared/</link>
    <description>Recommended interesting articles.</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://daringfireball.net/2011/11/fun_with_numbers" />
	<rdf:li rdf:resource="http://feeds.dashes.com/~r/AnilDash/~3/wWiqOCHbPPg/facebook-is-gaslighting-the-web.html" />
	<rdf:li rdf:resource="http://uxmovement.com/thinking/why-rounded-corners-are-easier-on-the-eyes/" />
	<rdf:li rdf:resource="http://nerdgap.com/my-very-first-dmca-takedown-notice/" />
	<rdf:li rdf:resource="http://blog.pinboard.in/2011/11/import_from_google_reader/" />
	<rdf:li rdf:resource="http://blog.wilshipley.com/2011/11/real-security-in-mac-os-x-requires.html" />
	<rdf:li rdf:resource="http://feedproxy.google.com/~r/37signals/beMH/~3/glsgdJGc6lg/3038-quick-little-ui-feedback-tip" />
	<rdf:li rdf:resource="http://nick.typepad.com/blog/2011/11/the-long-term-failure-of-web-apis.html" />
	<rdf:li rdf:resource="http://www.numbersforstartups.com/blog/2011/10/31/running-the-entire-business-from-an-ipad/" />
	<rdf:li rdf:resource="http://news.cnet.com/8301-10805_3-20128013-75/the-inside-story-of-how-microsoft-killed-its-courier-tablet/" />
	<rdf:li rdf:resource="http://processtypefoundry.com/fonts/elena/" />
	<rdf:li rdf:resource="http://tightwind.net/2011/10/how-apple-is-organized/" />
	<rdf:li rdf:resource="http://www.nytimes.com/2011/10/30/opinion/mona-simpsons-eulogy-for-steve-jobs.html?_r=1&amp;pagewanted=all" />
	<rdf:li rdf:resource="http://rss.gadgetopia.com/~r/gadgetopia/~3/UCYQHS4smOM/7281" />
	<rdf:li rdf:resource="http://thenextweb.com/apple/2011/10/28/the-next-disruptive-iphone-feature-high-definition-audio-calls/" />
	<rdf:li rdf:resource="http://alac.macosforge.org/" />
	<rdf:li rdf:resource="http://itunes.apple.com/us/app/bloomberg-tv/id460459302?mt=8&amp;ign-mpt=uo%3D4" />
	<rdf:li rdf:resource="http://daringfireball.net/2011/10/buy_our_devices_model" />
	<rdf:li rdf:resource="http://nick.typepad.com/blog/2011/10/what-the-upcoming-google-reader-changes-mean-for-feeddemon.html" />
	<rdf:li rdf:resource="http://my.opera.com/usability/blog/show.dml/36754672" />
	<rdf:li rdf:resource="http://consumerist.com/2011/10/apple-manager-makes-exception-and-makes-10-year-old-girls-dreams-come-true.html" />
	<rdf:li rdf:resource="http://www.marco.org/2011/10/20/how-to-bring-good-design-to-a-platform" />
	<rdf:li rdf:resource="http://typewritten.doormouse.org/" />
	<rdf:li rdf:resource="http://www.marco.org/2011/10/17/instapaper-4-released" />
	<rdf:li rdf:resource="http://www.macstories.net/stories/ios-5-icloud-tips-sharing-an-apple-id-with-your-family/" />
	<rdf:li rdf:resource="http://siliconfilter.com/google-engineer-google-is-a-prime-example-of-our-complete-failure-to-understand-platforms/" />
	<rdf:li rdf:resource="http://www.marco.org/2011/10/13/ios5-caches-cleaning" />
	<rdf:li rdf:resource="http://www.businessweek.com/technology/working-with-steve-jobs-10122011.html" />
	<rdf:li rdf:resource="http://allthingsd.com/20111005/the-steve-jobs-i-knew/?mod=tweet" />
	<rdf:li rdf:resource="http://store.apple.com/us/product/S4575?mco=MjU5MTk4MjQ" />
	<rdf:li rdf:resource="http://online.wsj.com/article/SB10001424052970203405504576603053795839250.html?ru=yahoo&amp;mod=yahoo_hs" />
	<rdf:li rdf:resource="http://feedproxy.google.com/~r/37signals/beMH/~3/dhYS3ymt-Dc/3018-api-design-for-humans" />
	<rdf:li rdf:resource="http://trentwalton.com/2011/09/20/unitasking/" />
	<rdf:li rdf:resource="http://www.zeldman.com/2011/09/15/boston-globes-responsive-redesign-discuss/" />
	<rdf:li rdf:resource="http://www.joelonsoftware.com/items/2011/09/13.html" />
	<rdf:li rdf:resource="http://ifttt.com/" />
	<rdf:li rdf:resource="http://feedproxy.google.com/~r/shawnblanc/~3/AqjXzxSbhZs/" />
	<rdf:li rdf:resource="http://fosspatents.blogspot.com/2011/09/shocker-for-android-oems-google.html" />
	<rdf:li rdf:resource="http://gigaom.com/2011/09/05/don-norman-google-doesnt-get-people-it-sells-them/" />
	<rdf:li rdf:resource="http://thisismynext.com/2011/08/16/fusion-garage-grid-10-pictures-video-preview/" />
	<rdf:li rdf:resource="http://mondaybynoon.com/feeder/?FeederAction=clicked&amp;feed=Posts+%28RSS2%29&amp;seed=http%3A%2F%2Fmondaybynoon.com%2F2011%2F08%2F17%2Feasy-content-deployment-for-wordpress-ramp%2F&amp;seed_title=Easy+Content+Deployment+for+WordPress%3A+RAMP" />
	<rdf:li rdf:resource="http://www.splatf.com/2011/08/gruber-motorola-balls/" />
	<rdf:li rdf:resource="http://tightwind.net/2011/08/jeff-bezoss-patent-reform-ideas/" />
	<rdf:li rdf:resource="http://www.technologyreview.com/blog/mimssbits/27080/?ref=rss" />
	<rdf:li rdf:resource="http://daringfireball.net/linked/2011/08/11/android-source-code" />
	<rdf:li rdf:resource="http://gigaom.com/2011/08/11/blaming-the-tools-britain-proposes-a-social-media-ban/" />
	<rdf:li rdf:resource="http://www.instapaper.com/go/195025596/text#" />
	<rdf:li rdf:resource="http://www.youtube.com/watch?v=BMgWTeCo6dQ&amp;feature=autoshare" />
	<rdf:li rdf:resource="http://whowritesforyou.com/2011/08/03/the-uses-of-cultivated-boredom-waiting-without-media/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-uses-of-cultivated-boredom-waiting-without-media" />
	<rdf:li rdf:resource="http://bits.blogs.nytimes.com/2009/09/09/in-qa-steve-jobs-snipes-at-amazon-and-praises-ice-cream/" />
      </rdf:Seq>
    </items>
  <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rdf+xml" href="http://feeds.feedburner.com/recommended-reading" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="recommended-reading" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /></channel><item rdf:about="http://daringfireball.net/2011/11/fun_with_numbers">
    <title>★ Fun With Numbers</title>
    <dc:date>2011-11-24T07:46:39+00:00</dc:date>
    <link>http://daringfireball.net/2011/11/fun_with_numbers</link>
    <dc:creator>cloudseer</dc:creator><dc:subject>shared</dc:subject>
<dc:identifier>http://pinboard.in/u:cloudseer/b:b22e037331c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feeds.dashes.com/~r/AnilDash/~3/wWiqOCHbPPg/facebook-is-gaslighting-the-web.html">
    <title>Facebook is gaslighting the web. We can fix it.</title>
    <dc:date>2011-11-21T19:10:53+00:00</dc:date>
    <link>http://feeds.dashes.com/~r/AnilDash/~3/wWiqOCHbPPg/facebook-is-gaslighting-the-web.html</link>
    <dc:creator>cloudseer</dc:creator><dc:subject>shared facebook danger</dc:subject>
<dc:identifier>http://pinboard.in/u:cloudseer/b:fea22ce2106a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:facebook" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:danger" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://uxmovement.com/thinking/why-rounded-corners-are-easier-on-the-eyes/">
    <title>Why Rounded Corners are Easier on the Eyes</title>
    <dc:date>2011-11-08T16:00:57+00:00</dc:date>
    <link>http://uxmovement.com/thinking/why-rounded-corners-are-easier-on-the-eyes/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Anthony Tseng on why rounded-corner rectangles in Web design are attractive, and it’s not just because they’re a current design trend.

✚ Permalink]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:1fc19df7d703/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nerdgap.com/my-very-first-dmca-takedown-notice/">
    <title>✚ My Very First DMCA Takedown Notice</title>
    <dc:date>2011-11-08T15:21:11+00:00</dc:date>
    <link>http://nerdgap.com/my-very-first-dmca-takedown-notice/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[One thing I’ve learned during my relatively short stint as a guy who sells something on the Internet is that people steal. A lot. Every now and then, I’ll do a Google search for the name of my ebook (or the filename of the download itself) and I’ll be staring at a big list of document hosting sites, Bit Torrent trackers and other such business. I would be lying if I said that my heart doesn’t sink a little when I see this stuff; not because of the lost revenue (which sucks), but in response to how quickly my fellow human beings will screw each other as long as they’re fairly confident they won’t get pinched.

As much as this bugs me, I’ve never felt like I had much recourse. Admittedly, I haven’t sent many sternly-worded emails to the operators of the sites illegally hosting my stuff, but that’s only because I was fairly certain I wouldn’t get a response. Perhaps I’m just cynical.

But all this is sorta beside the point.

A couple of weeks ago, I was doing one of the aforementioned “vanity searches” for my ebook and came across the entire document available for viewing on Scribd, a place where you can host documents, share them, etc. I’ve known about the site for awhile, but had never used it. Anyway, seeing my PDF up there was, as usual, frustrating.

Just for shits and giggles, though, I scrolled down to the site footer and found a link called “Copyright”, which I visited. The page briefly described what to do if you find material that infringes on a copyright. Turns out, you have to issue a DMCA Copyright Infringement Takedown Notification, which I’d heard of but always imagined needing a lawyer to put together. Turns out, it’s this teensy half-page document that a partially inebriated chimp could fill out between Jager bombs.

I downloaded the template, dropped in my name, email and street addresses and the URL where the infringing content lived, then pasted the whole mess into an email and sent it off.

About 6 minutes later, I got an email from a guy named Jason at Scribd informing me that my request had been received and that the document had been removed. Wow.

Clearly, it doesn’t always work this way. I imagine many, many notices like mine are received every day and immediately deleted without any action being taken. I must say, though, that I’m really impressed with Scribd. I don’t know that I’ll ever have much use for their services, but I’m happy to know that they’re taking this copyright bullcrap seriously.

I guess the big takeaway here is that it may be worth the time to fight back. Maybe.

]]></description>
<dc:subject>Articles shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:e192334be36f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Articles" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.pinboard.in/2011/11/import_from_google_reader/">
    <title>Import from Google Reader</title>
    <dc:date>2011-11-06T03:42:43+00:00</dc:date>
    <link>http://blog.pinboard.in/2011/11/import_from_google_reader/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[I've made it possible to import all your shared or starred articles from Google Reader into Pinboard.  You can find step-by-step instructions for this on the import page,
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:03ce1e321f69/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.wilshipley.com/2011/11/real-security-in-mac-os-x-requires.html">
    <title>Real Security in Mac OS X Requires Apple-Signed Certificates</title>
    <dc:date>2011-11-04T23:37:12+00:00</dc:date>
    <link>http://blog.wilshipley.com/2011/11/real-security-in-mac-os-x-requires.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Wil Shipley:



  There are three primary ways Apple increases security of
applications running on the Mac and the iPhone: Sandboxing, Code
Auditing, and Certification. While all these are incrementally
valuable, none is perfect on its own.


The problem Mac developers are facing is that the two that Apple
is enforcing on the Mac App Store (Sandboxing and Code Auditing)
are implemented currently to be actively bad for developers and
not particularly good for users. And the method that would provide
the most benefit for developers and users (Certification) isn’t
enforced broadly enough to be useful.



A thoughtful, detailed, and well-reasoned argument. Let’s hope Apple is listening.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:478c2fe26a73/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feedproxy.google.com/~r/37signals/beMH/~3/glsgdJGc6lg/3038-quick-little-ui-feedback-tip">
    <title>Quick little UI feedback tip</title>
    <dc:date>2011-11-04T18:39:00+00:00</dc:date>
    <link>http://feedproxy.google.com/~r/37signals/beMH/~3/glsgdJGc6lg/3038-quick-little-ui-feedback-tip</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Sometimes when I’m giving feedback on a UI, and I’m pointing out a spacing detail, I upload a little screenshot to Basecamp or Campfire to help make sure the feedback is clear.



	I wanted to share a little tweak to the feedback which I think is ultimately more useful. In this example I’m pointing out that the space above and below an element is not equal (and I think it should be).



	I used to do it like this:



	



	Two lines. One line above the element (text, in this case) extending to the next element above it, and one line below the element extending to the next element below it. The length of the lines shows the different spacing. That works, but the difference – especially when we’re talking about small units of pixels – isn’t as clear as it could be.



	Then I switched to doing it like this:



	



	Blocks like this are easier to see than thin one pixels lines. This is an improvement. But it’s still not as clear as it could be because it’s not as easy to judge the comparative volume of a rectangle as it is a square. So…



	This is how I do it now:



	



	The same vertical distance is covered, but now, since both blocks are perfect squares, we have related horizontal distance which helps you see how much bigger the difference is.



	Why not just say 24px vs 35px? Because I want to point out the physical difference, not the exact number of pixels. If we’re just talking numbers then it’s easy to assume 24px or 35px is right. But maybe the final size is 27px or 31px. I don’t want to get stuck on numbers when I provide feedback like this. The final number isn’t important as long as it’s the same (and it looks right).



	I hope this was helpful.

 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:040c0b243620/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nick.typepad.com/blog/2011/11/the-long-term-failure-of-web-apis.html">
    <title>The Long-Term Failure of Web APIs</title>
    <dc:date>2011-11-03T03:27:02+00:00</dc:date>
    <link>http://nick.typepad.com/blog/2011/11/the-long-term-failure-of-web-apis.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Years ago, when developers such as myself started the transition away from OS-specific APIs to web APIs, we believed that doing so would empower our software and save it from the confines of the desktop.

And we were right.

But we've also learned that while web APIs enable us to tap into a wealth of data, they can only be relied upon in the short term. The expiration date of software we create has been shortened due to the whims of those who create the web APIs we rely on.

I wrote the first version of HomeSite back in 1994, and seventeen years later I can still run it on the latest version of Windows.

I created FeedDemon 1.0 in 2003, and it was the first app I wrote that relied on web APIs. Now those APIs no longer exist, and almost every version of FeedDemon since then has required massive changes due to the shifting sands of the web APIs I've relied on.

You might think you're immune to this problem if you only integrate with APIs created by large players such as Twitter, Facebook and Google. But in recent years we've seen Twitter switch to a new authentication system, Facebook deprecate FBML, and Google discontinue several APIs. All of these changes have broken, or will break, existing apps.

The end result is that developers are spending more time upgrading their software to ensure that it continues to work with web APIs they've integrated with, and less time adding the features and refinements that would really benefit their customers.

That's a long-term failure, any way you look at it.
]]></description>
<dc:subject>Software Web/Tech shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:92bca89db8c0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Software" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Web/Tech" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.numbersforstartups.com/blog/2011/10/31/running-the-entire-business-from-an-ipad/">
    <title>Running the Entire Business from an iPad - NumbersForStartups Blog</title>
    <dc:date>2011-11-02T18:02:46+00:00</dc:date>
    <link>http://www.numbersforstartups.com/blog/2011/10/31/running-the-entire-business-from-an-ipad/</link>
    <dc:creator>cloudseer</dc:creator><dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:961e2caf42f2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://news.cnet.com/8301-10805_3-20128013-75/the-inside-story-of-how-microsoft-killed-its-courier-tablet/">
    <title>CNet: The Inside Story of How Microsoft Killed Its Courier Tablet</title>
    <dc:date>2011-11-02T00:50:10+00:00</dc:date>
    <link>http://news.cnet.com/8301-10805_3-20128013-75/the-inside-story-of-how-microsoft-killed-its-courier-tablet/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Interesting reporting by Jay Greene for CNet, but I’m not buying it that Courier was near completion. This, to me, is damning:



  When Courier died, there was not a single prototype that contained
all of the attributes of the vision: the industrial design, the
screen performance, the software experience, the correct weight,
and the battery life. Those existed individually, created in
parallel to keep the development process moving quickly. Those
prototypes wouldn’t have come together into a single unit until
very late in the development process, perhaps weeks before
manufacturing, which is common for cutting-edge consumer
electronics design. But on the team, there was little doubt that
they were moving quickly toward that final prototype.


“We were on the cusp of something really big,” said one Courier
team member.



One prototype that looks right, one with the right screen, one that has the right software, one that has the right weight, and one with the right battery life. Just mash them all together in a few weeks and you’re done. Sure.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:503f68b3cd9b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://processtypefoundry.com/fonts/elena/">
    <title>Elena</title>
    <dc:date>2011-11-01T12:54:25+00:00</dc:date>
    <link>http://processtypefoundry.com/fonts/elena/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[I think I’m in love.

∞
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:d2a1dda85ea8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tightwind.net/2011/10/how-apple-is-organized/">
    <title>How Apple is Organized</title>
    <dc:date>2011-10-30T19:50:30+00:00</dc:date>
    <link>http://tightwind.net/2011/10/how-apple-is-organized/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Apple is organized around functions, rather than divisions: 


The result is a command-and-control structure where ideas are shared at the top — if not below. Jobs often contrasts Apple’s approach with its competitors’. Sony (SNE), he has said, had too many divisions to create the iPod. Apple instead has functions. “It’s not synergy that makes it work” is how one observer paraphrases Jobs’ explanation of Apple’s approach. “It’s that we’re a unified team.”
…
Specialization is the norm at Apple, and as a result, Apple employees aren’t exposed to functions outside their area of expertise. Jennifer Bailey, the executive who runs Apple’s online store, for example, has no authority over the photographs on the site. Photographic images are handled companywide by Apple’s graphic arts department. Apple’s powerful retail chief, Ron Johnson, doesn’t control the inventory in his stores. Tim Cook, whose background is in supply-chain management, handles inventory across the company. (Johnson has plenty left to do, including site selection, in-store service, and store layout.)

This doesn’t just mean that the best person is handling a specific task (like the photos in Apple’s online store)—it also means that the company is interwoven and has no choice but to work together. Rather than have engineering lay out the specifications for a new product, hand it off to the design department so they can create a design that meets them, and then hand it off to marketing, Apple instead integrates design, engineering and marketing from the beginning of the process. 

 There’s a lot to learn from Apple’s corporate and business strategies, but I think there is even more to learn from how the company’s organized. Apple is defining how companies must be organized and managed to succeed in this century.

]]></description>
<dc:subject>Apple business links shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:eb4212fa3464/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Apple" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:business" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nytimes.com/2011/10/30/opinion/mona-simpsons-eulogy-for-steve-jobs.html?_r=1&amp;pagewanted=all">
    <title>Mona Simpson’s Eulogy for Her Brother</title>
    <dc:date>2011-10-30T19:35:55+00:00</dc:date>
    <link>http://www.nytimes.com/2011/10/30/opinion/mona-simpsons-eulogy-for-steve-jobs.html?_r=1&amp;pagewanted=all</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Heartbreaking and beautiful.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:bb786f7ea4b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rss.gadgetopia.com/~r/gadgetopia/~3/UCYQHS4smOM/7281">
    <title>The Effect of Consuming News at Work</title>
    <dc:date>2011-10-29T14:09:02+00:00</dc:date>
    <link>http://rss.gadgetopia.com/~r/gadgetopia/~3/UCYQHS4smOM/7281</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[
Professor Pablo Boczkowski on news consumption…: This is from a professor who has studied public news consumption.  He talks in the video, and the transcript is below.
 The entire thing is interesting, but I particularly liked this point:
  The people who tend to work in an office environment, with other coworkers, and get the news online at work, tend to identify the consumption of online news with the workplace. So when they leave the office, right, because there is that symbolic association between the consumption of news and the workplace, they don’t want, when they’re at home, or it’s the weekend, they don’t want to get the news online.
 So, our ability to consume news at work (which, let’s face it, is somewhat unique to the last decade), affects how we “place” news in our life and how we perceive it in relating to us.  News becomes a “business” concern, rather than a “personal” concern.
 I can’t even speculate on the long-term implications of that.

						
							Click here to comment on this entry
						

					
				
 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:fc7382ffe0b7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thenextweb.com/apple/2011/10/28/the-next-disruptive-iphone-feature-high-definition-audio-calls/">
    <title>→ The next disruptive iPhone feature? High definition audio calls</title>
    <dc:date>2011-10-28T01:13:19+00:00</dc:date>
    <link>http://thenextweb.com/apple/2011/10/28/the-next-disruptive-iphone-feature-high-definition-audio-calls/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Matthew Panzarino speculates on a possible “VoiceTime” feature in the future:



  But the fact is that the voice technology used by most cell phone carriers hasn’t received much attention, as the concentration has been on building out data networks and coverage areas.

  
  So now is the time for someone to improve the voice quality of our phones, and cut one more cord away while they’re at it.



This is a great idea.


Cellular voice transmission, like satellite radio and digital cable TV, lives in the sad world of extreme bandwidth conservation: it’s compressed, processed, and crushed down to the minimum quality threshold that customers will tolerate. (And then they crush it a little bit more, because what are you going to do about it, really?)


As we see with FaceTime, the iPhone’s hardware is capable of much higher audio quality if the bandwidth is available.


A theoretical “VoiceTime” feature implemented like FaceTime — a separate type of call that people must select each time — would be interesting.


But an implementation like iMessage, where it could switch over automatically whenever both ends of a call are compatible, and we’d all just start using fewer voice minutes… that would be the kind of ballsy move that I hope the post-Steve Apple keeps making.



∞ Permalink
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:3947660e6be7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alac.macosforge.org/">
    <title>Apple Lossless Audio Codec Now Open Source</title>
    <dc:date>2011-10-28T00:11:19+00:00</dc:date>
    <link>http://alac.macosforge.org/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Apple:



  The Apple Lossless Audio Codec project contains the sources for
the ALAC encoder and decoder. Also included is an example command
line utility, called alacconvert, to read and write audio data
to/from Core Audio Format (CAF) and WAVE files. A description of a
‘magic cookie’ for use with files based on the ISO base media file
format (e.g. MP4 and M4A) is included as well.



Apache-licensed.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:0a67a4376b43/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://itunes.apple.com/us/app/bloomberg-tv/id460459302?mt=8&amp;ign-mpt=uo%3D4">
    <title>Bloomberg TV+ for iPad</title>
    <dc:date>2011-10-27T16:50:15+00:00</dc:date>
    <link>http://itunes.apple.com/us/app/bloomberg-tv/id460459302?mt=8&amp;ign-mpt=uo%3D4</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[This is the future of TV. The full Bloomberg news channel, free of charge, on your iPad. Apps are the new channels.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:434fd94b0121/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://daringfireball.net/2011/10/buy_our_devices_model">
    <title>★ The Just-Buy-Our-Devices Model</title>
    <dc:date>2011-10-26T00:08:12+00:00</dc:date>
    <link>http://daringfireball.net/2011/10/buy_our_devices_model</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Tim Bajarin, “Why Google and Microsoft Hate Siri”: 



  Yes, Siri is an important product for enhancing our user interface
with the iPhone. But Siri is in its infancy. When it grows up, it
will be the front end to all types of searches conducted on
iPhones, iPads, Mac’s and even Apple TV. And, if I were Google
or Microsoft, perhaps I too would be playing down the impact of
Siri since they know full well that it is not just a threat to
their product platforms, but to their core businesses of search as
well. In fact, they should be quaking in their boots since Apple
is taking aim at their cash cow search businesses with their
technology and could very well impact their fortunes dramatically
in the future.



I think it’s a stretch to call search one of Microsoft’s “core businesses”. They’re still losing money — a lot of money, consistently, quarter after quarter — in their online services division. But they wouldn’t be sticking with it if they didn’t see it as a future core business.



  For Apple’s investors, the call for them to start paying
dividends on their cash hoard is too short-sighted. Instead, they
should be encouraging Apple to start buying up as many databases
and services they can and begin the process of entrenching
Siri’s role as the first line of offense when searching for a
product and service and get the search ad revenue from this for
themselves. I believe that if they do this, they could probably
add another $3-$5 billion in quarterly revenue to their already
healthy business model within three years, as search becomes
another profit center for Apple.



I think Bajarin is correct that Siri is a huge deal, and that if it truly thrives, it will adversely affect traditional web search like Google and Bing. But I can’t see Apple monetizing it through advertising. That’s tacky.


I see Apple “monetizing” Siri simply as a way to sell more devices — more iPhones now, more iPads (and who knows, maybe Macs?) in the future. Siri could be the interface to future products, like tiny little Nano-sized devices, or home entertainment systems. Google’s ad-driven model disrupted Microsoft’s pay-for-software-licenses model. Apple’s just-buy-our-devices-and-look-at-all-the-cool-shit-you-get-with-them model could disrupt Google’s ad-driven model.


Microsoft’s model was: you’d buy a device, then pay for licenses for Microsoft software. Google’s disruption was: hey, you don’t need to pay for Microsoft software if you’re willing to put up with our non-blinking mostly-text ads. Apple’s model is: you don’t even need to see those ads, just buy your devices from us. (Although you could argue that with the App Store, Apple is circling back to the pay-for-more-software model. But that’s not really a profit center for Apple.)


Siri doesn’t need to lead to advertising in order to add to Apple’s bottom line. Consider iCloud — Apple now offers free-of-charge online services ad-free. It’s a sunk cost in the name of the overall experience for Apple device buyers.
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:2016cbf4cf23/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nick.typepad.com/blog/2011/10/what-the-upcoming-google-reader-changes-mean-for-feeddemon.html">
    <title>What the Upcoming Google Reader Changes Mean for FeedDemon</title>
    <dc:date>2011-10-21T16:32:44+00:00</dc:date>
    <link>http://nick.typepad.com/blog/2011/10/what-the-upcoming-google-reader-changes-mean-for-feeddemon.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Yesterday Google announced some big changes to Google Reader which will impact FeedDemon (and every other application that uses the unofficial Google Reader API).

In an effort to better integrate with Google+, Reader is retiring friending, following and shared link blogs. That means the social features in FeedDemon that rely on Google Reader will eventually stop working.

They won't stop working right away, though. Google will continue to support those features in its API even after they disappear from Reader's UI. But at some point (I don't know when yet) they will cease to function, and you'll be unable to share articles in FeedDemon or follow the shared articles of other users.

Before that happens, I'll release a new version of FeedDemon that removes those features. But I won't do that until the new Reader goes live and I have a chance to test against it, which will likely take a few weeks.

I am, of course, disappointed to see those features disappear. I know a lot of FeedDemon customers will miss them, and I'll personally mourn the loss of shared articles since that's something I use every day.
]]></description>
<dc:subject>FeedDemon shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:a217d0b3ee5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:FeedDemon" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://my.opera.com/usability/blog/show.dml/36754672">
    <title>Trash It</title>
    <dc:date>2011-10-20T22:28:52+00:00</dc:date>
    <link>http://my.opera.com/usability/blog/show.dml/36754672</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Just watched my friend get a new phone.  An Android.He, like most, started installing new applications and having fun and then, like most, decided to uninstall some.  He kept complaining to me that he couldn't get them to uninstall, he said he'd keep trying and they wouldn't go away.  Finally, I asked him what was happening?  He explained he was uninstalling it but they wouldn't go away.So I watched him do it.  He opened the home menu, grabbed an application icon by pressing and holding, the icon then "floats" as this functionality was used to drop icons on the "desktop" view.  So he took the icon and dropped it onto the trashcan that appeared.It was a priceless moment."Trash" is for getting rid of something and that's what he wanted to do.  After all, on his windows machine or even an Mac you drag stuff into the "trash" or "recycle" to get rid of it.  Now, my fix for this would be a pop-up asking whether they wanted to simply delete the icon or uninstall the application but that seems a bit cumbersome....A completely valid interpretation of the interface, in my opinion.]]></description>
<dc:subject>uninstall confusion trash android shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:bf174c6d8751/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:uninstall" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:confusion" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:trash" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:android" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://consumerist.com/2011/10/apple-manager-makes-exception-and-makes-10-year-old-girls-dreams-come-true.html">
    <title>Apple Manager Breaks Rule, Makes 10-Year-Old Girl’s Dreams Come True</title>
    <dc:date>2011-10-20T19:28:32+00:00</dc:date>
    <link>http://consumerist.com/2011/10/apple-manager-makes-exception-and-makes-10-year-old-girls-dreams-come-true.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Such a great story.

(via @rickstawarz.)

∞

]]></description>
<dc:subject>Links shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:4a31ff1cd3fa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.marco.org/2011/10/20/how-to-bring-good-design-to-a-platform">
    <title>How to bring good design to a platform</title>
    <dc:date>2011-10-20T04:05:28+00:00</dc:date>
    <link>http://www.marco.org/2011/10/20/how-to-bring-good-design-to-a-platform</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[
Demonstrate from the top that high quality and attention to detail are prioritized and appreciated above everything else, including being the first to market, having the most features, or having the most aggressive prices. If you can get those as well, that’s great, but quality will not be sacrificed to do so.
Instill these values in your staff. If you can’t, hire a staff for which you can. Better yet, hire a staff for which you don’t need to.
Aggressively pursue simplification, elegance, craftsmanship, and the highest-class user experiences in the product line. Ruthlessly cut or hold features or entire products that aren’t good enough.
Make it pretty.


How not to bring good design to a platform


Skip steps 1–3 above.
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:b2a2dddaed97/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://typewritten.doormouse.org/">
    <title>The Amazing Type-Writer</title>
    <dc:date>2011-10-17T18:40:20+00:00</dc:date>
    <link>http://typewritten.doormouse.org/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[My favorite new iPhone app in months. It’s a cross between a painstakingly skeuomorphic old-timey typewriter and an-Instagram-ish public gallery for sharing your output. Great fun with a price that blows the competition out of the water.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:023b7d1549c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.marco.org/2011/10/17/instapaper-4-released">
    <title>Introducing Instapaper 4.0 for iPad and iPhone</title>
    <dc:date>2011-10-17T13:52:28+00:00</dc:date>
    <link>http://www.marco.org/2011/10/17/instapaper-4-released</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[





This is a big update. (Impatient? App Store link.)


Navigation

The iPad browsing interface has been completely redesigned to feel more at home in the iPad environment. Instead of just being a blown-up full-screen list, it’s now a more touch-friendly grid, with all navigation available in any orientation:


The iPad list screen


On iPhone, the navigation has also been unified and restyled:


 The iPhone list screens


Reading

The iPhone reading screens also no longer show the top status bar by default (but there’s an option to put it back). This gives a larger, less distracting reading area without sacrificing easy access to the toolbar or annoying customers with finicky full-screen tap modes.


 The iPhone reading screen (dark mode, right)


Want to check the time periodically without leaving the status bar visible all the time? Just tap the Actions button in the toolbar and the status bar will slide in.


Articles from many sites now display the site title, author name, and published date when available:


(Availability of author, title, and date information will increase over time.)


The scroll bar on the right side is now draggable: simply touch the indicator for a moment to activate it, then drag to quickly scroll through an article. With the small activation delay, you won’t accidentally invoke it when scrolling normally, but it’s easy to activate when you want to.


Reading at night in dark mode is now even better, because under iOS 5, Instapaper now supports true hardware brightness control. Adjustable brightness is now also available on iPhone for the first time:





To finally end the long-standing confusion and debates between Archiving and Deleting articles, they now peacefully coexist everywhere:





When you’ve Liked an article, the Delete option is not shown, since deleting it would also remove it from your Liked list.


Wikipedia

Selecting text and tapping Define can now look up terms in Wikipedia (online) in addition to the offline dictionary:





Footnotes

Footnotes from most websites are now converted to a “…” button that shows them in a popover so you don’t need to jump to the bottom to read them:





This is a huge improvement in the usefulness of footnotes while reading. Showing similar popups with Javascript to all web browsers should really be a feature of all blogging software that generates footnotes.


Multi-select

Articles can now be multi-selected, like Apple’s Mail and Photos apps, for archiving, deleting, or moving to folders:





Browsing

Instead of just showing Liked articles from online friends who use Instapaper, the Friends panel can now show all links posted to your Facebook news feed, Twitter timeline, or Tumblr Dashboard:





So even if your friends don’t use Instapaper as much as you do, you can still find plenty of great articles to read.


For more great articles, the Editors section has been rewritten. Now sourced exclusively from Give Me Something To Read (a.k.a. Editor’s Picks), the new interface is faster to load, faster to browse, and faster to save articles to read later:





Search

Instapaper now has a true search feature, available as part of the $1/month Subscription.


Subscribers can now search the full contents of every article they’ve ever saved to Instapaper: unread, filed into folders, or in the Archive. (Deleted items can’t be searched because they’re really deleted.)


The new search feature is built right into the app:


(This replaces the old downloaded-articles-only search in the app.)


Search is available for all Subscribers in the app today. It will be available on the website next week.


You can also now subscribe via In-App Purchase. It’s called Search Subscription. The website Subscription and the new Search Subscription in the app are the same thing, with the same features, just purchased in different ways: either PayPal or In-App Purchase.


App Directory

The new App Directory showcases apps that integrate with Instapaper in various ways, such as sending articles to Instapaper or receiving links and selected text from the Share panel:


 


And more

Other changes in the 4.0 app:



Articles in the list or grid can be swiped to reveal a quick action menu
The in-article styling has been improved
New settings can customize the number of Liked/Archived articles stored on device
The iPhone font (ᴀA) panel has been redesigned to be like iPad’s
The iPhone share forms for Twitter, Tumblr, Facebook, Pinboard, and Evernote have been redesigned
YouTube URLs now open in the system’s YouTube app
A new setting has been added to use Apple’s dictionary under iOS 5
Tilt scrolling is now smoother and works better in all orientations
The Share panel can now send to Tweetbot and The Hit List
When updating, the entire table no longer reloads after each article downloads. It now just reloads once after the main update request, showing all (even un-downloaded) articles, and they enable themselves as they get downloaded.
Tons of performance improvements and bugfixes
New icon


This is a great update. Download it now.
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:d2972ad5f494/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.macstories.net/stories/ios-5-icloud-tips-sharing-an-apple-id-with-your-family/">
    <title>Sharing an Apple ID With Your Family</title>
    <dc:date>2011-10-14T23:16:10+00:00</dc:date>
    <link>http://www.macstories.net/stories/ios-5-icloud-tips-sharing-an-apple-id-with-your-family/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Fantastic article that I was really hoping somebody would write.

∞

]]></description>
<dc:subject>Links shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:24bb5b07e6ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://siliconfilter.com/google-engineer-google-is-a-prime-example-of-our-complete-failure-to-understand-platforms/">
    <title>Google Engineer: “Google+ is a Prime Example of Our Complete Failure to Understand Platforms”</title>
    <dc:date>2011-10-14T04:12:56+00:00</dc:date>
    <link>http://siliconfilter.com/google-engineer-google-is-a-prime-example-of-our-complete-failure-to-understand-platforms/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Wow.

Yegge makes a cogent argument and I find it strangely impressive that he’s got the huevos to make a statement like this (which, if I understand it, was meant to be shared with all of Google, internally).

But, still. Wow.

(via 512px)

∞

]]></description>
<dc:subject>Links shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:d30968b99708/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.marco.org/2011/10/13/ios5-caches-cleaning">
    <title>Cleaning…</title>
    <dc:date>2011-10-13T19:58:17+00:00</dc:date>
    <link>http://www.marco.org/2011/10/13/ios5-caches-cleaning</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[This is going to be a problem:


(Screenshot by someone on Twitter two weeks ago. I can’t find the tweet now — sorry.)


Every iOS app has its own “home” directory where it can store files. Every file and directory that an app puts there, except anything in a Caches or tmp directory, gets backed up when you sync your device to iTunes.


Prior to iOS 5, the system never deleted the contents of Caches and tmp, so they were safe places for apps to put data that should always be available but could be redownloaded if the user did a complete restore or otherwise lost all data, and therefore shouldn’t be taking up space in backups and slowing down syncs.


In iOS 5, since iCloud backups are now possible, Apple has started cracking down on apps that store too much in any backed-up directory, such as Documents. Many developers have recently received emails from Apple like this:



  In recent testing it appears that [your app] stores a fair amount of data in its Documents folder.

  
  Since iCloud backups are performed daily over Wi-Fi for each user’s iOS device, it’s important to ensure the best possible user experience by minimizing the amount of data being stored by your app.

  
  In addition to purchased music, apps, books, Camera roll, and device settings, everything in your app’s home directory, including its Documents folder, is backed up to iCloud.

  
  Data stored in the application bundle itself, the caches directory, and the temp directory is not backed up to iCloud. Your app should store data in these locations according to the iCloud Data Storage Guidelines on <http://developer.apple.com/icloud/documentation/data-storage/>.

  
  Please review these guidelines, make any required changes to your app, and submit an update to the App Store.



And that documentation page makes it pretty clear:



  
  Only documents and other data that is user-generated, or that cannot otherwise be recreated by your application, should be stored in the <Application_Home>/Documents directory and will be automatically backed up by iCloud.
  Data that can be downloaded again or regenerated should be stored in the <Application_Home>/Library/Caches directory. Examples of files you should put in the Caches directory include database cache files and downloadable content, such as that used by magazine, newspaper, and map applications.
  


Sounds easy: just move anything that can be redownloaded to Caches.


Instapaper has stored its downloaded articles in Caches for years, since I didn’t want to slow down iTunes syncing for my customers or enlarge their backups unnecessarily, and full restores don’t happen often enough for it to be a problem for most people. This new policy now locks me into using Caches: I no longer have a choice.


But in iOS 5, there’s an important change: Caches and tmp — the only two directories that aren’t backed up — are “cleaned” out when the device is low on space.


A handful of developers reported this problem happening to them with Instapaper before iOS 5 was even released to the public — I’m dreading the influx of reports about this now that iOS 5 is available to everyone.





There’s no longer anywhere to store files that don’t need to be backed up (or can’t be, by the new policy) but shouldn’t be randomly deleted. This is problematic for lots of apps, including this quick list off the top of my head:



Instapaper and anything that saves web articles for offline reading
Ebook and comic-book apps (including iBooks, if the rules apply to it)
Podcast clients (the rules don’t apply to synced podcasts from iTunes)
Offline Wikipedia apps
Offline mapping programs


The common theme is offline. It’s easy to assume that this isn’t a big problem — that surely, anything downloadable can be redownloaded at any time. But that’s not the case.


A common scenario: an Instapaper customer is stocking up an iPad for a long flight. She syncs a bunch of movies and podcasts, downloads some magazines, and buys a few new games, leaving very little free space. Right before boarding, she remembers to download the newest issue of The Economist. (I think highly of my customers.) This causes free space to fall below the threshold that triggers the cleaner, which — in the background, unbeknownst to her — deletes everything that was saved in Instapaper. Later in the flight, with no internet connectivity, she goes to launch Instapaper and finds it completely empty.


(Last week, almost this exact scenario happened to one of my customers.)


It creates a terrible experience for everyone:



She has nothing to read. (She already finished The Economist.)
My app appears to have failed and deleted her data, which makes it seem unreliable and decreases her opinion of it. If I’m lucky, she’ll email support and I’ll at least get a chance to explain myself. She’ll probably either be quietly dissatisfied or leave a 1-star review in the App Store telling everyone else that my app is unreliable and deletes data without warning, which will decrease my sales (and Apple’s 30% of those sales).
She had a terrible experience on her iPad, which now seems less reliable as a whole, which reflects poorly on Apple and iOS.


It gets worse as you consider how often redownloading data isn’t a good option or isn’t even possible:



Devices that are offline during large parts of the day, such as iPod Touches and Wi-Fi iPads
3G devices roaming internationally
Any devices, even on Wi-Fi, connected to a network with expensive data transfer or with a low monthly transfer limit (a common scenario outside the U.S.)
Devices in rural areas, where even the best home “broadband” connections available are very slow and can’t redownload hundreds of megs quickly
Devices that are about to be carried out of Wi-Fi range when the owner realizes that his content has been deleted but he’s about to be late for work or the kids are getting rained on after soccer practice or the dog is about to explode and he needs to leave right now


But even with available, fast, unlimited internet connectivity, randomly deleting an app’s data is still a problem:


When customers save an article with Instapaper, get a book in iBooks, or download a podcast with Instacast, they expect it to be there next time they launch the app. Even though it’s technically redownloadable, customers see that as their data — they put it there, and it’s theirs to remove if and when they see fit.


When the cleaner wipes it out, it appears that the app has failed and deleted their data. And customers won’t know that it’s an iOS 5 behavior — they’ll understandably blame the app developers. Even though it’s not our fault, it’s certainly going to become our problem.


There needs to be a file storage location that behaves the way Caches did before iOS 5: it’s not backed up to iTunes or iCloud, it’s not synced, but it’s also never deleted unless the app is deleted.
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:14c740cf1069/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.businessweek.com/technology/working-with-steve-jobs-10122011.html">
    <title>Speaking of Grains of Salt Regarding Businessweek Stories</title>
    <dc:date>2011-10-13T17:34:47+00:00</dc:date>
    <link>http://www.businessweek.com/technology/working-with-steve-jobs-10122011.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[From a Peter Burrows piece for Businessweek, “Working With Steve Jobs”, interviewing former AOL CEO Barry Schuler:



  Steve Jobs was a genius, but he knew his limits.


“He was never a guy who tried to make believe he had expertise
in something,” said Barry Schuler, now a partner at venture
capital firm Draper Fisher Jurvetson.


That was clear to Schuler when he got a call from Jobs in early
1997 to come over to his old offices at NeXT Software in Redwood
City, Calif. Jobs, at that point, hadn’t yet agreed to run Apple
on a permanent basis.


“What’s this Internet thing?” Schuler recalled Jobs asking.
“I don’t get it. What are people doing on it? What do they
like about it?”



Steve Jobs didn’t get the Internet? In 1997? OK, sure. Here’s Steve Jobs, in his classic interview with Wired in 1996:



  The Web is exciting for two reasons. One, it’s ubiquitous. There
will be Web dial tone everywhere. And anything that’s ubiquitous
gets interesting. Two, I don’t think Microsoft will figure out a
way to own it. There’s going to be a lot more innovation, and that
will create a place where there isn’t this dark cloud of
dominance. […]


If you look at things I’ve done in my life, they have an element
of democratizing. The Web is an incredible democratizer. A small
company can look as large as a big company and be as accessible as
a big company on the Web. Big companies spend hundreds of millions
of dollars building their distribution channels. And the Web is
going to completely neutralize that advantage.



Yeah, he didn’t get it at all.


Update: Here’s Jobs in 1985 — 1985! — in his classic interview with Playboy:



  The most compelling reason for most people to buy a computer for
the home will be to link it into a nationwide communications
network. We’re just in the beginning stages of what will be a
truly remarkable breakthrough for most people — as remarkable as
the telephone.



Thanks to John Siracusa for the link.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:acbfd89eb9a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://allthingsd.com/20111005/the-steve-jobs-i-knew/?mod=tweet">
    <title>→ The Steve Jobs I Knew</title>
    <dc:date>2011-10-06T15:15:43+00:00</dc:date>
    <link>http://allthingsd.com/20111005/the-steve-jobs-i-knew/?mod=tweet</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Walt Mossberg, in a great collection of personal anecdotes:



  Earlier in the day, before Gates arrived, I did a solo onstage interview with Jobs, and asked him what it was like to be a major Windows developer, since Apple’s iTunes program was by then installed on hundreds of millions of Windows PCs.

  
  He quipped: “It’s like giving a glass of ice water to someone in Hell.” When Gates later arrived and heard about the comment, he was, naturally, enraged, because my partner Kara Swisher and I had assured both men that we hoped to keep the joint session on a high plane.

  
  In a pre-interview meeting, Gates said to Jobs: “So I guess I’m the representative from Hell.” Jobs merely handed Gates a cold bottle of water he was carrying. The tension was broken, and the interview was a triumph, with both men acting like statesmen.




∞ Permalink
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:cc22f6ea21b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://store.apple.com/us/product/S4575?mco=MjU5MTk4MjQ">
    <title>AppleCare+</title>
    <dc:date>2011-10-04T20:28:30+00:00</dc:date>
    <link>http://store.apple.com/us/product/S4575?mco=MjU5MTk4MjQ</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Now if you drop your iPhone you can get it fixed for $49:



  AppleCare+ for iPhone extends repair coverage and technical support to two years from the original purchase date of your iPhone and adds coverage for up to two incidents of accidental damage due to handling, each subject to a $49 service fee.



I’ve never damaged any my iPhones beyond a scuff on their edge, but I know more than a few people who have done some major damage. Though I will say that there is one person in this home who will be getting their first iPhone later this month, and she may also happen to be good at accidentally dropping things.

✚ Permalink]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:b2e8ab16d24b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://online.wsj.com/article/SB10001424052970203405504576603053795839250.html?ru=yahoo&amp;mod=yahoo_hs">
    <title>→ Sprint to ‘Bet the Company’ on Apple’s iPhone</title>
    <dc:date>2011-10-03T18:45:38+00:00</dc:date>
    <link>http://online.wsj.com/article/SB10001424052970203405504576603053795839250.html?ru=yahoo&amp;mod=yahoo_hs</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[The Wall Street Journal outs a huge Sprint iPhone deal:



  Mr. Hesse told the board the carrier would have to agree to purchase at least 30.5 million iPhones over the next four years—a commitment of $20 billion at current rates—whether or not it could find people to buy them, according to people familiar with the matter.



Also interesting:



  The board ultimately signed off on what the company internally called the “Sony” project, concluding Sprint couldn’t compete otherwise. Directors figured, “How can we pass this up? We have to have it,” the person familiar with the matter said.

  
  […]

  
  The lack of the iPhone is “the No. 1 reason customers leave or switch,” Mr. Hesse said at an industry conference last month.



Wow.



∞ Permalink
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:d774fb37a21c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feedproxy.google.com/~r/37signals/beMH/~3/dhYS3ymt-Dc/3018-api-design-for-humans">
    <title>API design for humans</title>
    <dc:date>2011-09-28T17:28:00+00:00</dc:date>
    <link>http://feedproxy.google.com/~r/37signals/beMH/~3/dhYS3ymt-Dc/3018-api-design-for-humans</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[One of the things about working with data at 37signals is that I end up  interacting with a lot of different APIs—I’ve used at least ten third-party APIs in the last few months, as well as all of our public APIs and a variety of internal interfaces. I’ve used wrappers in a couple different languages, and written a few of my own. It’s fair to say I’ve developed some strong opinions about API design and documentation from a data consumer’s perspective.



	From my experience, there are a few things that really end up mattering from an API usability perspective (I’ll leave arguments about what is truly REST, or whether XML or JSON is actually better technically to someone else).



Tell me more: documentation is king

	I have some preferences for actual API design (see below), but I will completely trade them for clear documentation. Clear documentation includes:



	
	Examples that show the full request. This can be a full example using curl like we provide in our API documentation, or just a clear statement of the request like Campaign Monitor does for each of their methods.
	


	
	Examples that show what the expected response is. One of the most frustrating things when reading API documentation is not knowing what I’m going to get back when I utilize the API—showing mock data goes along way towards this. Really good API documentation like this would let you write an entire wrapper without ever making a single request to the API. Campaign Monitor and MailChimp both have good, but very different takes on this.
	


	
	A listing of error codes, what they mean, and what the most common cause of receiving them is. I’m generally not the biggest fan of the Adwords API in many ways, but they are a great example of exhaustively documenting every single response code they return.
	


	
	A searchable HTML interface. Whether it’s visually appealing doesn’t really matter much, and Google indexing it is plenty of search. What doesn’t work for me is when the API documentation is in PDF, or I have to authenticate to get access to it.
	


	
	Communication of versioning and deprecation schedules. There’s some debate about whether versioning is better than gradual evolution, but regardless, anytime you’re changing something in a way that might break someone’s existing code, fair warning is required, and it should be on your documentation site. Sometimes you have to make a change for security reasons that don’t allow much advance notice, but wherever possible, providing a couple of weeks notice goes a long way. The Github API  clearly shows what will be removed when and shows the differences between versions clearly.
	
More...

 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:5715da16cf78/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://trentwalton.com/2011/09/20/unitasking/">
    <title>Unitasking</title>
    <dc:date>2011-09-22T19:23:40+00:00</dc:date>
    <link>http://trentwalton.com/2011/09/20/unitasking/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Trent Walton:



  I have a big monitor that sits on a big desk, which is littered with stacks of paper the same way my iMac is littered with stacks of apps. I see corners of windows everywhere, peeking out and siphoning shreds of attention away from the task at hand. This need to navigate from one app to the next has facilitated my evolution into a multitasking machine. Not since the arcade edition of Street Fighter II have I mastered so many gestures and key commands. Utilities like Mission Control, Alfred App, and Better Touch Tool, summoned by various combos of taps and swipes, have become key to the way I work. Emails get answered while to-do lists are created while graphics are exported while sites get updated. Notifications pop-up, and I suppress them. I am master of my desktop environment, and it’s wearing me out.


✚ Permalink]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:dcbadce91f9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zeldman.com/2011/09/15/boston-globes-responsive-redesign-discuss/">
    <title>Boston Globe’s Responsive Redesign. Discuss.</title>
    <dc:date>2011-09-15T15:03:12+00:00</dc:date>
    <link>http://www.zeldman.com/2011/09/15/boston-globes-responsive-redesign-discuss/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[

AS EVERY WEB DESIGNER not living under a rock hopefully already knows, The Boston Globe has had a responsive redesign at the hands of some of today’s best designers and developers:

The spare Globe website has a responsive design that adapts to different window sizes, browsers and devices, and it has a built-in Instapaper-type feature that saves articles for reading off various devices on the subway. The overhaul has incorporated the talents of Boston design firms Filament Group, and Upstatement, as well as a large internal team, and pre-empts the need to build separate apps for each device.—New York Observer

As the first responsive redesign of a “real” website (i.e. a large, corporately financed, widely read newspaper site rather than some designer’s blog), the site has the potential to raise public awareness of this flexible, standards-based, multi-platform and user-focused web design approach, and deepen perceptions of its legitimacy, much as Mike Davidson’s standards-based redesign of ESPN.com in 2003 helped convince nonbelievers to take a second look at designing with web standards:

In a major step in the evolution of website design, the Boston Globe relaunched their site today using a Responsive Design approach. For a consistent experience across mobile and desktop browsers, they redesigned the site to add and remove columns to the layout based on the width of your browser window.

This marks the first major, high-traffic, content-heavy website to adopt a responsive design. The lead consultant behind the project is none other than Ethan Marcotte, the designer who wrote the book on responsive design. Much as ESPN changed the way we worked by being one of the first to launch a fully CSS driven site a decade ago, the Boston Globe’s redesign has the potential to completely alter the way we approach web design.—Beaconfire Wire

More work remains to be done. Some sections of the paper have not yet converted, and some site architecture has yet to be refreshed, so it is too early to call the overhaul a complete success. But it is clear that Ethan Marcotte, author of Responsive Web Design and creator of responsive design, together with the geniuses at Filament Group, Upstatement, and the Globe’s internal design/development team have managed to work beautifully together and to solve design problems some of us don’t even know exist.

Congratulations to the Globe for its vision and these designers and developers for their brilliant work.


			
				
			
		
]]></description>
<dc:subject>A_Book_Apart A_List_Apart Design Ethan_Marcotte Layout Responsive_Web_Design Web_Design Web_Design_History Web_Standards shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:f9a71db72316/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:A_Book_Apart" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:A_List_Apart" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Design" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Ethan_Marcotte" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Layout" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Responsive_Web_Design" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Web_Design" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Web_Design_History" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Web_Standards" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.joelonsoftware.com/items/2011/09/13.html">
    <title>Announcing Trello</title>
    <dc:date>2011-09-13T17:44:10+00:00</dc:date>
    <link>http://www.joelonsoftware.com/items/2011/09/13.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Around the time of Fog Creek Software's ten year anniversary, I started thinking that if we want to keep our employees excited and motivated for another ten years, we were going to need some new things to work on. It occurred to me that we could easily afford to make four little two-person teams to launch four new products. That would give our developers more chances to move around from product to product when they got bored, which would make Fog Creek Software an even better place to work.

Each team, we decided, would be guided by the spirit of lean startups. They would ship early and often. They would listen to real-world customers instead of building things in an ivory tower. And they wouldn't be afraid to pivot endlessly until they made something that people wanted.

Next, we needed some business ideas. After ten years in management I still never knew what anyone was supposed to be working on. Once in a while I would walk around asking everyone what they were doing, and half the time, my reaction was "why the hell are you working on THAT?" So one of the teams started working on finding better ways to keep track of who was working on what. It had to be super simple and friction-free so that everyone would use it, but it had to be powerful, too.

We had an early idea called FIVE THINGS. Everybody would have a list of exactly five things that they were allowed to work on. The top two were things they were actively doing right now. The other three were things that they would do as soon as they finished the first two. But nobody was ever allowed to have SIX things assigned to them. If you have too many things on your to-do list, your motivation tends to sag.

Five Things wasn't the right idea, but it led us to the idea that became Trello. Pretty soon we had four programmers and two summer interns working on it. We started dogfooding the product when it was only 700 lines of code, and even in that super-simple form, we found it incredibly useful. By the end of the summer we realized we had a hit on our hands: an incredibly simple, easy-to-understand way for teams to collaborate online.



So without further ado, I'd like to introduce you to Fog Creek's newest product: Trello.


Read more about what Trello does
Sign up, it's awesome! 
Need to hire a really great programmer? Want a job that doesn't drive you crazy? Visit the Joel on Software Job Board: Great software jobs, great people.

]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:2ab3a41def42/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ifttt.com/">
    <title>ifttt — If This Then That</title>
    <dc:date>2011-09-13T17:42:27+00:00</dc:date>
    <link>http://ifttt.com/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[New(-ish) automation service, acts like glue between a wide variety of online services. Think: Automator for the web. Ambitious and clever, and they take a novel approach to making the interface obvious and easy. Check out the list of most-popular recipes to get an idea of the things you can do with it.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:a23d53c3811b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feedproxy.google.com/~r/shawnblanc/~3/AqjXzxSbhZs/">
    <title>VirtualHostX 3.0 [Sponsor]</title>
    <dc:date>2011-09-13T04:47:43+00:00</dc:date>
    <link>http://feedproxy.google.com/~r/shawnblanc/~3/AqjXzxSbhZs/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[My thanks to Tyler Hall for sponsoring the RSS feed this week to promote his Mac app, VirtualHostX 3.0.


In short, VirtualHostX is a Mac app for setting up, running, and managing virtual hosts on your Mac.


As any professional Web developer knows, doing your development locally is simply how it’s done. Setting up your Mac to run the necessary server software is the best way to build and develop websites and web apps. And if you have more than a single site you’re building and working on then you’re going to want to set up virtual hosts. And that is where VirtualHostX comes in.


This app is professional-grade, and it has been used by many of the best in the business for years.



Sean Sperte recommended VirtualHostX in 2008 as one of the most important tools to setting up a killer, local web development environment on your Mac.

Derek Punslan, one of the guys who helped me cut my teeth on Mac and web nerdery back in 2006 and 2007, has been recommending VirtualHostX since 2009.

Brian Warren, the senior designer/developer at Happy Cog Studios uses VirtualHostX.



VirtualHostX works on top of the server software on your Mac. Your Mac can easily be used as an Apache server, and all you need to do is install PHP and MySQL. Most people, myself included, recommend you use MAMP for that. MAMP is free and it installs all the necessary server software so your Mac can run websites which require databases (i.e. local WordPress installs).


I suggest you read Sean or Aaron’s tutorials on getting MAMP set up and then installing VirtualHostX. The setup is extremely easy (it took me longer to download MAMP than to set it up), and in just a few clicks you’ll be all set to install and run a WordPress or Expression Engine website right from within your Mac.


For a long time I did my web design and development on a live server. I guess that is fine (though it is a bit dangerous, but hey, that’s how I roll), but doing web design and development locally is so much better and more convenient for two primary reasons: speed and speed. Moreover, you can design and develop even when you’re not connected to the Internet.


(Note that if you’re using Typekit, you can add your localhost sites to your Typekit Kit. Simply edit your Kit and add “localhost” as well as whatever URL you chose for your local development URL to the domains list.)


Version 3.0 of VirtualHostX, which just shipped a few days ago, has some very clever new features. Namely Lift Off, a new Domain Details tab, and a new icon.


With Lift Off you can share your site with anyone online. I can’t tell you how many times I’ve received emails or Twitter DMs with a screenshot of a site that a friend is working on. If that friend were using VirtualHostX they could send me a working URL via Lift Off and I could see the live site in my browser.


Tyler describes Lift Off like this:



  Lift Off creates a secure connection between your Mac and the VirtualHostX Cloud then gives you a unique URL that you can pass around to your boss, client, or friend to view your site.

  
  Since your virtual host is being served live off of your Mac, there’s no uploading files or waiting. Changes you make locally appear automatically for your users.



The second big update is the Domain Details tab. It’s a tab that is specific to each virtual host you have set up. In there you can log and store all the various details related to the domain you are doing design and development for (such as FTP, SSH, DNS, database config info, and more).


VirtualHostX 3.0 would be worth it for its new features alone. You can try it for free to see for yourself, but you may want to pick it up soon as it’s currently on sale for shawnblanc.net readers.

✚ Permalink]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:a4ae0f85cc50/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fosspatents.blogspot.com/2011/09/shocker-for-android-oems-google.html">
    <title>‘Do Not Develop in the Open’</title>
    <dc:date>2011-09-07T20:00:50+00:00</dc:date>
    <link>http://fosspatents.blogspot.com/2011/09/shocker-for-android-oems-google.html</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Information from the Oracle v. Google lawsuit includes these bullet points from an internal Google presentation:



  
Do not develop in the open. Instead, make source code available
after innovation is complete

Lead device concept: Give early access to the software to
partners who build and distribute devices to our specification
(ie [sic], Motorola and Verizon). They get a non-contractual time to
market advantage and in return they align to our standard.





 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:feb6a9e60f14/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gigaom.com/2011/09/05/don-norman-google-doesnt-get-people-it-sells-them/">
    <title>Don Norman: Google Doesn’t Get People, It Sells Them</title>
    <dc:date>2011-09-05T21:55:41+00:00</dc:date>
    <link>http://gigaom.com/2011/09/05/don-norman-google-doesnt-get-people-it-sells-them/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[The truth has an anti-Google bias.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:b33f313f8b4f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thisismynext.com/2011/08/16/fusion-garage-grid-10-pictures-video-preview/">
    <title>‘Very, Very Responsive’</title>
    <dc:date>2011-08-18T07:06:14+00:00</dc:date>
    <link>http://thisismynext.com/2011/08/16/fusion-garage-grid-10-pictures-video-preview/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Dieter Bohn from The Verge, at around the 1:20 mark in his video review of Fusion Garage’s new Grid 10 forked-version-of-Android tablet: “Taking a look at the pinch-to-zoom action, it’s very, very responsive. I’m really impressed with what they’ve managed to do here.”


If my iPad’s pinch-to-zoom were that choppy, I’d take it back to the Apple Store, because I’d know there was something seriously wrong with it.


(Via Marco Arment.)



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:0304b9b74849/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mondaybynoon.com/feeder/?FeederAction=clicked&amp;feed=Posts+%28RSS2%29&amp;seed=http%3A%2F%2Fmondaybynoon.com%2F2011%2F08%2F17%2Feasy-content-deployment-for-wordpress-ramp%2F&amp;seed_title=Easy+Content+Deployment+for+WordPress%3A+RAMP">
    <title>Easy Content Deployment for WordPress: RAMP</title>
    <dc:date>2011-08-17T23:43:49+00:00</dc:date>
    <link>http://mondaybynoon.com/feeder/?FeederAction=clicked&amp;feed=Posts+%28RSS2%29&amp;seed=http%3A%2F%2Fmondaybynoon.com%2F2011%2F08%2F17%2Feasy-content-deployment-for-wordpress-ramp%2F&amp;seed_title=Easy+Content+Deployment+for+WordPress%3A+RAMP</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Easy Content Deployment for WordPress: RAMP.

By far the most hideous part of continuous development is database migration. While we have stellar tools for source code management, the database layer seems to be just abstracted enough to be painful.

I’ve just learned of RAMP through the stream of tweets from #wcsf and I’m impressed.



RAMP does what it can to tackle the problem we never want to deal with: keeping your staged WordPress content in community with your production WordPress content.

RAMP allows you to make all the changes you need in your staging environment, then selectively push these changes to your production site. You can set up a new section of your site, upload some images to fill out a nice carousel for it, and add a link to it on your home page. Once this content has been reviewed and approved, you can go to your RAMP page, select these content changes, and push them to your production site.

Do take the time to check out their video tour, the entire process seems extremely polished from start to finish.
]]></description>
<dc:subject>Asides WordPress content_deployment content_staging plugin RAMP shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:feb7c9ddd529/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Asides" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:WordPress" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:content_deployment" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:content_staging" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:plugin" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:RAMP" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.splatf.com/2011/08/gruber-motorola-balls/">
    <title>How Motorola got Google to pay up: “By the balls”</title>
    <dc:date>2011-08-16T04:38:30+00:00</dc:date>
    <link>http://www.splatf.com/2011/08/gruber-motorola-balls/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Smart post by John Gruber:

I think Motorola knew they had Google by the balls. Google needed Motorola’s patent library to defend Android as a whole, Motorola knew it, and they made Google pay and pay handsomely. I don’t think it’s curious at all why Google didn’t simply license Motorola’s patents. Motorola held out for a full acquisition at a premium far above the company’s actual value, and threatened to go after its sibling Android partners if Google didn’t acquiesce.
]]></description>
<dc:subject>News Google Motorola shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:03835411126d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:News" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Google" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Motorola" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tightwind.net/2011/08/jeff-bezoss-patent-reform-ideas/">
    <title>Jeff Bezos’s Patent Reform Ideas</title>
    <dc:date>2011-08-13T00:14:10+00:00</dc:date>
    <link>http://tightwind.net/2011/08/jeff-bezoss-patent-reform-ideas/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Jeff Bezos has a few excellent ideas for how to reform our patent system: 

Much (much, much, much) remains to be worked out, but here’s an outline of what I have in mind:

1. That the patent laws should recognize that business method and software patents are fundamentally different than other kinds of patents.

2. That business method and software patents should have a much shorter lifespan than the current 17 years — I would propose 3 to 5 years. This isn’t like drug companies, which need long patent windows because of clinical testing, or like complicated physical processes, where you might have to tool up and build factories. Especially in the age of the Internet, a good software innovation can catch a lot of wind in 3 or 5 years.

3. That when the law changes, this new lifespan should take effect retroactively so that we don’t have to wait 17 years for the current patents to enter the public domain.

4. That for business method and software patents there be a short (maybe 1 month?) public comment period before the patent number is issued. This would give the Internet community the opportunity to provide prior art references to the patent examiners at a time when it could really help. (Thanks to my friend Brewster Kahle for this suggestion.)

Two and four are brilliant. Reducing patent lifespans to 3-5 years would instantly make our current patent problems much smaller, because not only would patents be invalidated rather quickly, but because their lifespan is so short, people would have much less reason to file them in the first place.

 By the way, note the date on this.

]]></description>
<dc:subject>links Politics Web shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:b99cf4ad98d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Politics" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Web" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.technologyreview.com/blog/mimssbits/27080/?ref=rss">
    <title>Eliminating Batteries</title>
    <dc:date>2011-08-12T15:20:30+00:00</dc:date>
    <link>http://www.technologyreview.com/blog/mimssbits/27080/?ref=rss</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Christopher Mims:
The average human expends between 100 and 200 watts of power when exercising vigorously, but your iPhone can only accept up to 2.5 watts when charging. Somewhere, somehow, there’s got to be an inexpensive and reliable way to connect these two realities.
I hear that submerging humans in goo works pretty well.
∞
]]></description>
<dc:subject>Links battery humans life shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:c7fd7f25c9fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:Links" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:battery" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:humans" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:life" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://daringfireball.net/linked/2011/08/11/android-source-code">
    <title>Daring Fireball Linked List: Android Fail English? That's Unpossible.</title>
    <dc:date>2011-08-12T08:20:53+00:00</dc:date>
    <link>http://daringfireball.net/linked/2011/08/11/android-source-code</link>
    <dc:creator>cloudseer</dc:creator><dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:6426da4b53cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gigaom.com/2011/08/11/blaming-the-tools-britain-proposes-a-social-media-ban/">
    <title>Speaking of Tools</title>
    <dc:date>2011-08-11T21:21:49+00:00</dc:date>
    <link>http://gigaom.com/2011/08/11/blaming-the-tools-britain-proposes-a-social-media-ban/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Mathew Ingram, GigaOm:



  In the wake of the riots in London, the British government says it’s considering shutting down access to social networks — as well as Research In Motion’s BlackBerry messenger service — and is asking the companies involved to help. Prime Minister David Cameron said not only is his government considering banning individuals from social media if they are suspected of causing disorder, but it has asked Twitter and other providers to take down posts that are contributing to “unrest.”




 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:1a86e230ecb3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.instapaper.com/go/195025596/text#">
    <title>Slicehost Articles: Linux file permission concepts</title>
    <dc:date>2011-08-11T10:47:43+00:00</dc:date>
    <link>http://www.instapaper.com/go/195025596/text#</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Linux file permissions are strange and wondrous
things. Start down the path of understanding by looking at the core
concepts behind them before moving on to practical
applications]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:6eb4356efa5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.youtube.com/watch?v=BMgWTeCo6dQ&amp;feature=autoshare">
    <title>Friction - Flip The Page (FULL)</title>
    <dc:date>2011-08-09T08:53:25+00:00</dc:date>
    <link>http://www.youtube.com/watch?v=BMgWTeCo6dQ&amp;feature=autoshare</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[I liked a YouTube video: Yes!

Buy here: http://itunes.apple.com/gb/album/someone-ep/id450467700

http://www.facebook.com/frictiondeejay

Image: http://www.sendspace.com/file/4cl3iq


http://www.facebook.com/pages/Knockeasy/195466127179943]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:765f02a87af3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://whowritesforyou.com/2011/08/03/the-uses-of-cultivated-boredom-waiting-without-media/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-uses-of-cultivated-boredom-waiting-without-media">
    <title>The Uses Of Cultivated Boredom: Waiting Without Media</title>
    <dc:date>2011-08-03T12:00:00+00:00</dc:date>
    <link>http://whowritesforyou.com/2011/08/03/the-uses-of-cultivated-boredom-waiting-without-media/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-uses-of-cultivated-boredom-waiting-without-media</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[
How much of every day do you spend waiting? If you’re a parent with young children I know that you wait. Wait to pick them up. Wait while they have activities. Wait for them to go to sleep. Wait for them to . . .

Even without children, life is often filed with waiting. And many of us fill that waiting time with media. We check our email, read something, check something. Anything to stave off boredom.

But boredom is a precursor state to thinking and imagination, so don’t be so quick to push it away.

At least once this week try an experiment. When you have to wait somewhere for something, just wait. Sit there. Welcome boredom.

And see where your mind takes you.

The Uses Of Cultivated Boredom: Waiting Without Media is a post from: First Today, Then Tomorrow. If you enjoyed or benefited from this post, please share, tweet, or link!


								 
Share/Bookmark
]]></description>
<dc:subject>The_life_of_the_mind writing boredom imagination shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:86b2f0c114b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:The_life_of_the_mind" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:writing" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:boredom" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:imagination" />
	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bits.blogs.nytimes.com/2009/09/09/in-qa-steve-jobs-snipes-at-amazon-and-praises-ice-cream/">
    <title>Steve Jobs on Reporting Sales Numbers</title>
    <dc:date>2011-08-01T14:58:36+00:00</dc:date>
    <link>http://bits.blogs.nytimes.com/2009/09/09/in-qa-steve-jobs-snipes-at-amazon-and-praises-ice-cream/</link>
    <dc:creator>cloudseer</dc:creator><description><![CDATA[Still thinking about Samsung’s decision to stop reporting sales numbers for phones and tablets. Here’s Steve Jobs in an interview with David Pogue two years ago:



  He said that Apple doesn’t see e-books as a big market at this
point, and pointed out that Amazon.com, for example, doesn’t
ever say how many Kindles it sells. “Usually, if they sell a lot
of something, you want to tell everybody.”



This is true for Apple, as well. I’m pretty sure the only time they’ve mentioned sales numbers for Apple TV is when it crossed the million-units-sold mark last December. They don’t put Apple TV numbers in their quarterly results.



 ★ 
]]></description>
<dc:subject>shared</dc:subject>
<dc:source>http://reader.google.com/</dc:source>
<dc:identifier>http://pinboard.in/u:cloudseer/b:cd83add88f25/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="http://pinboard.in/u:cloudseer/t:shared" />
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>

