<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/topics-files/atom2xhtml.xsl" type="text/xsl"?>
<!-- This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers. -->
<feed xmlns="http://www.w3.org/2005/Atom"
><title
>Blog@Case Topics: apple</title
><link rel="self" href="http://blog.case.edu/topics/apple"
 /><id
>http://blog.case.edu/topics/apple</id
><category term="apple" label="apple"
 /><link rel="related" href="http://blog.case.edu/topics/linkblog" title="linkblog"
 /><link rel="related" href="http://blog.case.edu/topics/osx" title="osx"
 /><link rel="related" href="http://blog.case.edu/topics/mainblog" title="mainblog"
 /><link rel="related" href="http://blog.case.edu/topics/computing" title="computing"
 /><link rel="related" href="http://blog.case.edu/topics/itunes" title="itunes"
 /><link rel="related" href="http://blog.case.edu/topics/case%20blog" title="case blog"
 /><link rel="related" href="http://blog.case.edu/topics/failures%20of%20technology" title="failures of technology"
 /><link rel="related" href="http://blog.case.edu/topics/windows" title="windows"
 /><link rel="related" href="http://blog.case.edu/topics/at&amp;t" title="at&amp;t"
 /><link rel="related" href="http://blog.case.edu/topics/microsoft" title="microsoft"
 /><link rel="related" href="http://blog.case.edu/topics/open%20source" title="open source"
 /><contributor
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></contributor
><contributor
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></contributor
><updated
>2008-04-28T06:32:14Z</updated
><entry
><title
>iTunes Genius FAIL</title
><link href="http://blog.case.edu/gps10/2008/09/10/itunes_genius_fail"
 /><id
>http://blog.case.edu/gps10/2008/09/10/itunes_genius_fail</id
><published
>2008-09-10T06:55:29Z</published
><updated
>2008-09-10T07:11:02Z</updated
><category term="Apple" label="Apple"
 /><category term="iTunes" label="iTunes"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I downloaded iTunes 8 today in hopes that it would fix the 1+ hour sync times with my iPhone (it did). I saw the news blurbs about the new "Genius" feature, so I thought I'd give a try. First, I had to transcode a few albums from FLAC to MP3 (because iTunes can't read FLAC files, sigh). So, I quickly converted the complete Led Zeppelin studio discography (all 10 discs from the 
<a href="http://www.amazon.com/Complete-Studio-Recordings-Led-Zeppelin/dp/B000002IWP">Complete Studio Recordings</a> collection) and imported them in iTunes. I clicked on a random album, and things got funky. A screenshot can best illustrate. 
<a href="http://blog.case.edu/gps10/2008/09/10/genius_fail.jpg">
<img alt="genius_fail.jpg" src="http://blog.case.edu/gps10/2008/09/10/genius_fail-thumb.jpg" width="400" height="229" />
</a> Um, yeah. Not only was I playing Stairway when it said I was missing it, but I also had every single track in the list of "missing" tracks. Helloooo? It got even better when I imported Abbey Road from The Beatles (published on the Apple label, of course).
<blockquote>Genius sidebar could not find matches for your specific selection, but here are the Top Songs and Albums in the iTunes Store.</blockquote>In all fairness, Genius did seem to work pretty well for a few more recent artists (like Coldplay and U2). Since recommendations appear to be limited to what is in the iTunes Store (I don't want this to sound like criticism because it is likely a calculated business decision), I think I'll stick to 
<a href="http://www.last.fm/">Last.fm</a>'s recommendation engine for now. It may not be as pretty, but it has a wider scope of coverage and more than one player can 
<a href="http://www.last.fm/help/faq?category=Scrobbling#201">Scrobble</a> to it.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Fluid.app</title
><link href="http://blog.case.edu/jeremy.smith/2008/04/28/fluidapp"
 /><id
>http://blog.case.edu/jeremy.smith/2008/04/28/fluidapp</id
><published
>2008-04-28T06:31:59Z</published
><updated
>2008-04-28T06:32:14Z</updated
><category term="apple" label="apple"
 /><category term="linkblog" label="linkblog"
 /><category term="osx" label="osx"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p>
<a title="Fluid - Free Site Specific Browser for Mac OS X Leopard" href="http://fluidapp.com/">Fluid.app</a> is good stuff. That is all.</p>
</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Leopard Destroys fink</title
><link href="http://blog.case.edu/jeremy.smith/2008/03/13/leopard_destroys_fink"
 /><id
>http://blog.case.edu/jeremy.smith/2008/03/13/leopard_destroys_fink</id
><published
>2008-03-13T06:41:41Z</published
><updated
>2008-03-13T06:41:42Z</updated
><category term="apple" label="apple"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p>A piece of information that would have been 
<em>really</em> nice to have about 12 hours ago: upgrading to 
<a title="Apple - Mac OS X Leopard" href="http://www.apple.com/macosx/">Leopard</a> completely messes up 
<a title="Fink - Home" href="http://finkproject.org/">fink</a>. I'm in the process of trying to repair things now. It's been a very time intensive process, and it doesn't look like it's going to be getting any easier any time soon.</p>
</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Java Doesn't "Just Build"</title
><link href="http://blog.case.edu/jeremy.smith/2007/10/31/java_doesnt_just_build"
 /><id
>http://blog.case.edu/jeremy.smith/2007/10/31/java_doesnt_just_build</id
><published
>2007-10-31T21:47:05Z</published
><updated
>2007-10-31T22:17:35Z</updated
><category term="apple" label="apple"
 /><category term="java" label="java"
 /><category term="linkblog" label="linkblog"
 /><category term="osx" label="osx"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Daring Fireball: Shipping Means Prioritizing" href="http://daringfireball.net/2007/10/shipping_means_prioritizing">Shipping Means Prioritizing</a>
<blockquote>Because that's how [Perl, Python, and Ruby] are designed and engineered &#8211; they're made to "just build" on any Unix-like OS. It's not Apple's responsibility that Java isn't like that &#8211; it's Sun's.</blockquote>I find that to be the perfect response to Tim Bray's 
<a title="ongoing &#239;&#191;&#189; No Leopard" href="http://www.tbray.org/ongoing/When/200x/2007/10/30/No-Leopard">No Java 6 on Leopard?</a></div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Obligatory Post on the iPhone</title
><link href="http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone"
 /><id
>http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone</id
><published
>2007-06-25T14:00:00Z</published
><updated
>2007-06-25T14:00:02Z</updated
><category term="AT&amp;T" label="AT&amp;T"
 /><category term="Apple" label="Apple"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="iPhone" label="iPhone"
 /><category term="internet" label="internet"
 /><category term="technology" label="technology"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>First off, congratulations to Apple and Steve Jobs for creating such a frenzy over a device that only few have actually seen being operated. There are few companies in the world that can generate this much anticipation for a product. Hats off to you. Because I live in Silicon Valley, everything tech is amplified about 100x compared to most parts of the country/world. And, since Apple's headquarters are only a few miles away (I think it is less than 3 miles from my apartment), the iPhone hype here has been almost untolerable. Everywhere you look, iPhone this, iPhone that. Every blog. iPhone. iPhone. iPhone. June 29 is almost here. Cingular (I guess it is the "new AT&amp;T" now), is preparing for people to be camping out overnight to be the first to get their hands on the devices. It is sheer madness. All of this excitement over a portable electronic device! Fortunately for my sanity, I've managed to remain calm about the iPhone. The reason is I don't want one. Well, technically, I'd like one, but I won't be buying one. My reasons are plentiful. Here are the top three:
<ul>
<li>The iPhone doesn't have a detachable battery -- Seriously, WTF? It is one thing for my iPod to run out of battery (which it does very often since I have almost exhausted the usable life out of the battery), it is another to run out of battery on my phone. Even if the battery life is great (I'm a little skeptic about the 
<a href="http://www.apple.com/iphone/specs.html">advertised battery life</a>), I still want the ability to change the battery. When the battery eventually loses its charge capacity, I want the freedom to replace it without replacing the whole device.</li>
<li>No 3G -- The non-WIFI network speed of the non-3G iPhone will be pathetic. Currently, most of AT&amp;T's EDGE network averages about 40kbps -- slower than a 56k dial-up modem! AT&amp;T has been upgrading their network lately to try to boost performance to 80kbps -- slightly faster than a 56k modem. Even if they max out, they can only get max performance at about 4x 56k speeds. The WIFI connection is a different story. It will probably be able to go over 1Mbps (5x faster than max EDGE speed). Of course, when you are in the store doing all the cool online activities with the iPhone, it will be going over WIFI. I picture many customers walking out of the store and saying, "why is the network so slow now?". They will find out that they have to use WIFI for a better browsing experience. Of course, WIFI will drain your battery like nothing else. So, you will either get great network performance or longer battery life. I don't want to make that decision! It will be interesting to see how many initial buyers complain about the EDGE network speed. With Google Maps on EDGE now, I find it barely usable. Will it be the same on iPhone? Time will tell.</li>
<li>It is the first model -- If I've learned anything about Apple products, it is to wait for the second model. There will be so many software refinements and hardware improvements, that you will be glad you waited. I wouldn't be surprised if a second generation was available by February 2008.</li>
</ul>In summary, being an early adopted of this product is just too risky or foolish for me. I commend Apple at designing an amazing product and building anticipation, but I just can't buy one just yet. Once the dust settles and iPhone survives the test of time (and adds a few more features, like 3G), I will probably be in the market for an iPhone, or any of the numerous competitors that are quickly entering the market. Finally, I wish the early adopters good luck. You will drop and good chunk of change on the device and service plan. I hope you get a great return on your investment.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Freshman Mac Usage</title
><link href="http://blog.case.edu/jeremy.smith/2006/10/23/freshman_mac_usage"
 /><id
>http://blog.case.edu/jeremy.smith/2006/10/23/freshman_mac_usage</id
><published
>2006-10-23T19:31:37Z</published
><updated
>2006-10-23T19:31:56Z</updated
><category term="apple" label="apple"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I've recently heard a number being bandied about that the incoming Freshman's usage of Apple computers is up to 
<strong>16%</strong>. I'm assuming a survey or something was done by 
<a href="http://wiki.case.edu/ITS">ITS</a> (maybe?) or the 
<a href="http://wiki.case.edu/Registrar">Registrar</a> or 
<a href="http://wiki.case.edu/Student_Life">Student Life</a> or somebody... Does anyone have the scoop on this? Is this number posted online anywhere? Because if it is not posted on the Internet, it simply isn't true.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Ubuntu</title
><link href="http://blog.case.edu/jeremy.smith/2006/09/11/ubuntu"
 /><id
>http://blog.case.edu/jeremy.smith/2006/09/11/ubuntu</id
><published
>2006-09-11T22:53:19Z</published
><updated
>2006-09-11T22:58:20Z</updated
><category term="Failures of Technology" label="Failures of Technology"
 /><category term="apple" label="apple"
 /><category term="mainblog" label="mainblog"
 /><category term="microsoft" label="microsoft"
 /><category term="open source" label="open source"
 /><category term="osx" label="osx"
 /><category term="ubuntu" label="ubuntu"
 /><category term="windows" label="windows"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I have no "religious" ties to any piece of software or "software philosophy." Many think of me as an 
<a title="Jeremy Smith's blog: Hats" href="http://blog.case.edu/jms18/2005/05/27/hats">open source zealot</a>, but I'm not. I think of software as nothing but tools, and I don't care how the hammer is made; it just needs to work for me. In a lot of situations, I tend to think of software as 
<a title="Jeremy Smith's blog: First 2005 Autocross Wrap-up" href="http://blog.case.edu/jms18/2005/05/15/first_2005_autocross_wrapup">cars</a> in that 
<a title="Jeremy Smith's blog: Choosing Platforms" href="http://blog.case.edu/jms18/2005/11/02/choosing_platforms">I like to be able to tinker with its innards</a>, but it's not a make-or-break thing for me. Afterall, on my two desktops, I use 
<a href="http://microsoft.com">Windows</a> and 
<a href="http://www.apple.com/macosx">OSX</a> (epitomies of closed source systems); and I have 
<a title="Jeremy Smith's blog: I Must Be the Most Demanding User in the World" href="http://blog.case.edu/jms18/2005/02/23/demanding_user">impossibly high expectations</a>. And, yes, I have read 
<a title="dive into mark" href="http://diveintomark.org/">Mark Pilgrim's</a> 
<a title="Freedom 0 [dive into mark]" href="http://diveintomark.org/archives/2004/05/14/freedom-0">Freedom 0</a> and 
<a title="When the bough breaks [dive into mark]" href="http://diveintomark.org/archives/2006/06/02/when-the-bough-breaks">When the bough breaks</a>; and yes, I agree with everything he says... to a point... I just want stuff that works &#8211; and Windows and OSX have always fulfilled that requirement for me and I have never been bitten by the data lockin problems that Mark has experienced (maybe I just don't generate a lot of locally stored data?). So anyways, as I was saying, I use Windows on the desktop located in my office. But what I should be saying is "I 
<strong>used</strong> to use Windows on the desktop located in my office." It finally came to the point where I was spending too much time grooming the tool rather than using it to get my stuff done. It was time for it to go, and go it did. I'm typing this post up via 
<a title="Welcome - Ubuntu: Linux for human beings" href="http://www.ubuntu.com/">Ubuntu</a>. I'm going to follow this post up with some others such as "What Broke the Window's Back," "Why Ubuntu," "First 
<strong>N</strong> Things a New Ubuntu User Should Do," etc. If you are already a Ubuntu user and have any tips or tricks to dish out, please do (for example, how to make it not so ugly).</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Apple To Release Wiki Server</title
><link href="http://blog.case.edu/gps10/2006/08/08/apple_to_release_wiki_server"
 /><id
>http://blog.case.edu/gps10/2006/08/08/apple_to_release_wiki_server</id
><published
>2006-08-08T07:00:41Z</published
><updated
>2006-08-08T07:05:13Z</updated
><category term="Apple" label="Apple"
 /><category term="Wiki" label="Wiki"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a href="http://www.apple.com/server/macosx/leopard/wikiserver.html">Wiki server part of Leopard</a>
<blockquote>No syntax or markup knowledge is required &#226;&#8364;&#8221; the Wiki Server comes with full drag-and-drop support</blockquote>
<blockquote>you can also access a group calendar to track meetings and deadlines or send messages to a mailing list to keep others informed. There is a blog feature that&#226;&#8364;&#8482;s perfect for brainstorming or commenting on work. And there&#226;&#8364;&#8482;s an option for subscribing to a podcast</blockquote>Apple, you never cease to amaze me.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Announcing the iTunes@Case Project</title
><link href="http://blog.case.edu/jeremy.smith/2006/03/20/case_itunes"
 /><id
>http://blog.case.edu/jeremy.smith/2006/03/20/case_itunes</id
><published
>2006-03-20T19:59:59Z</published
><updated
>2006-03-20T20:00:47Z</updated
><category term="General Information Technology" label="General Information Technology"
 /><category term="IT in Higher Ed" label="IT in Higher Ed"
 /><category term="apple" label="apple"
 /><category term="itunes" label="itunes"
 /><category term="mainblog" label="mainblog"
 /><category term="project management" label="project management"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Case Western Reserve University" href="http://www.case.edu/">Case</a> has been accepted into 
<a title="Apple" href="http://www.apple.com/">Apple's</a> 
<a title="Apple - Education - iTunes U" href="http://www.apple.com/education/solutions/itunes_u/">iTunes U</a> program. What this means is, eventually, users at Case will be able to distribute their digital media through iTunes: course related material, public lectures, podcasts, videocasts, etc. And people will be able to download it, subscribe to it, access it, preview it via iTunes. To get a sense of this, you can check out 
<a title="Stanford on iTunes" href="http://itunes.stanford.edu/">Stanford on iTunes</a>. The project is just beginning. And we've decided to handle shepherding this project to implementation in a different manner than we normally do with our IT projects. We're going to experiment with a more open style of running the project. In this vein, we've drafted a 
<a title="iTunes@Case: Case Western Reserve University" href="http://itunes.case.edu/charter/">charter for a working group</a> that will operate much like an 
<a title="EDUCAUSE | About EDUCAUSE | EDUCAUSE Home Page" href="http://www.educause.edu">eduCause</a>, 
<a title="Internet2 - Home" href="http://www.internet2.edu/">Internet2</a>, or 
<a title="IETF Home Page" href="http://www.ietf.org/">IETF</a> Working Group. The charter basically consists of the following:
<blockquote>This 
<acronym title="Working Group">WG</acronym> is supposed to implement iTunes@Case. Everybody play nice. A few co-chairs are around to make sure everyone is playing nice and to steer the group through ruts. The meat is in the discussion. Have at it.</blockquote>Let me add some emphasis to 
<strong>this is an 
<em>experiment</em></strong>. I think that this project lends itself well to attempting to manage a project in this manner. But we will see. So, if you are a member of the Case community (be you faculty, staff, student, what-have-you), and you would like to participate in the WG &#8212; go sign up to the mailing list: 
<a href="https://lists.case.edu/wws/info/itunes">itunes@case.edu</a>. We've setup a 
<a title="iTunes@Case Project Wiki" href="http://itunes.case.edu/wiki/view">wiki</a> (this time, I thought I'd try out 
<a title="TWiki - Enterprise Collaboration Platform and Wiki" href="http://twiki.org/">TWiki</a>
<sup>1</sup>) that is readable by everyone and editable by the members of the mailing list
<sup>2</sup>. We've got a basic 
<a title="RoadMap" href="http://itunes.case.edu/wiki/view/Main/RoadMap">Roadmap</a> fleshed out. But we don't have much more than that. Like I said, we're just getting underway. So... you interested? 
<a href="https://lists.case.edu/wws/info/itunes">Sign-up</a>. We've got to figure out what to call it &#8212; 
<strong>iTunes@Case</strong>, 
<strong>iTunes U @ Case</strong>, 
<strong>Case iTunes</strong>? How exactly does authentication happen? What about authorization i.e. how does it know to only allow students actually enrolled in a course access to that course's digital media? We need to generate documentation. We need to identify facilities that can help generate digital media. We need to determine the best use cases. We need to identify ways to foster adoption. Plus, it's cool. Bringing iTunes to the campus... It's a neat idea.
<br />
<br />
<sup>1</sup>Yea, this is directly related to experimenting with the 
<a title="Jeremy Smith's blog: Top 3 Most Wanted Services From ITS: #2) Wiki Farm" href="http://blog.case.edu/jms18/2006/02/01/three_wanted_its_services_wiki_farm">usefulness of a wiki farm</a> service. 
<sup>2</sup>Synchonizing who is on the mailing list and who can edit the wiki is done by hand. There's no magical 
<code>mod_authz_sympa</code> I could use, but 
<a title="Jeremy Smith's blog: Top 3 Most Wanted Services From ITS: #1) Social Software" href="http://blog.case.edu/jms18/2006/02/03/three_wanted_its_services_social_software">I wish there was</a>.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Planet Case Mac Widget</title
><link href="http://blog.case.edu/jeremy.smith/2005/12/05/planet_case_mac_widget"
 /><id
>http://blog.case.edu/jeremy.smith/2005/12/05/planet_case_mac_widget</id
><published
>2005-12-06T04:47:47Z</published
><updated
>2005-12-06T04:53:51Z</updated
><category term="apple" label="apple"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><category term="osx" label="osx"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Arcanum" href="http://blog.case.edu/clk13/">Casey Kearns</a> creates a 
<a title="Arcanum: First Entry - Planet Case Widget" href="http://blog.case.edu/clk13/2005/12/05/first_entry_planet_case_widget">Mac widget</a> for 
<a title="Planet Case" href="http://planet.case.edu/">Planet Case</a>. 
<em>Nice!</em></div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
></feed
>
