Tag: technology

  • Apple TV? SlingCatcher? Mac Mini? Something Else???

    Apple today officially announced the little box formerly known as the iTV, now dubbed the Apple TV. Nothing new has really been announced, and the honours of the day of course duly went to the quite stunning iPhone. The Apple TV price tag was confirmed, at US $299.

    Pretty neat and cheap little device, but one detail to note is that it will not ship with a cable to link it to your TV (see What’s in the box), which will probably fetch another US $20 or more at purchase time.

    Also, unless 3rd-party cable providers jump on the bandwagon, and/or that the device itself does not make use of Macrovision-like DRM technologies, the Apple TV will also not be compatible with analog TV sets (See the connection options), unless plugged in an intermediary solution like a cable/satellite set-top box or other. This is of course conveniently in line with the media industry’s quest to plugging the infamous analog hole (booh, there be dragons in there!).

    For those just as tempted as I to press the shiny pre-order button, I’d suggest to consider the family=AppleTV in the URL at the online Apple Store. Can you see the bigger-drive-coming-soon flag too?

    On another front, Sling Media announced (1, 2) the upcoming release of their very similar offering, the SlingCatcher, at the Consumer Electronics Show.

    We will probably have to watch for the same limitations as the former device, but one big point is that this solution is currently said to be media agnostic.

    This is an important fact in my context, since I have digital videos that go back to close to 10 years now, and some of them will not play in Quicktime without the addition of extra codecs (such as wmv, xvid, divx, etc). Apple currently only lists the iTunes compatible H.264 and MP4 (without avi encapsulations).

    Other codecs enabled via plug-ins do not import into iTunes at this time (2007-01-09), but interestingly will play in Front Row. I say this is interesting because Front Row seems to use iTunes for video playback (iTunes is launched in the background). Apple probably doesn’t want to have to deal with the AVI metadata format.


    But there might still be hope, if the Update Software seen in the Settings view is not just an interface to the Mac OS X Software Update utility, and allows for additional plugins to be installed. Or, like in Front Row, if it is possible to stream movies from mounted server, instead of the iTune daap Bonjour/ZeroConf-based streaming protocol (or video-enabled successor?). If I was a 3rd-party QT codec provider, I’d probably be begging them to do so right now, but as much as I enjoy their products, Apple doesn’t have the best record for letting others play with their toys.

    The price tag for the SlingCatcher is currently pre-announced at around US $200, or about $100 less than the Apple TV. The better solutions for me could still be a Mac Mini using Front Row, which has its own upsides (full feldged OS, analog adapter, DVD player/burner, external expandability, etc) and problems (US $599 v. > 300, thicker, etc). Or also a PS3 running Linux.

    Um, again left with decisions… Bah, I still have a few weeks to decide before my birthday anyway. ๐Ÿ˜‰

    Update: 2007-01-10: Apple does not actually manufacture/(re-)brand connection cables at all. The ones listed on their site are actually made by Xtreme Mac. Also, some of the same questions/concerns I had have been addressed by some of the Ars Technica editors.

  • Screenshots of Fedora Core 6 in VMWare Fusion Beta

    Please note: this is an early report, and more details will be posted as I have more time to dig deeper into Fusion. Loads of screenshots in the meantime.

    As I mentioned earlier, VMWare Fusion for Mac has had its first beta version released publicly today. My first thought was to try the existing Fedora Core 6 x86 virtual machine I put up for download a few weeks ago, to see if it would run as is on my 2006 Core Duo Macbook.

    Having experience with both VMWare on other platforms and Parallels Desktop on the Mac, I was eager to see how the two compared. Having moved VMs between OS platforms with VMWare, I really wanted to know if the Mac would indeed be treated equally.

    So since I’m busy packing for a holiday trip, and only have little time for it, I thought I’d post screenshots of how it all went. Hint: it’s all good. ๐Ÿ™‚ You can go ahead and download my VM image, and give it a shot for yourself.

    I’m only going to embed a few screenshots below, so the page stays light, but here is a complete archive: FC6_in_VMWare_Fusion_Beta-SCREENSHOTS-20061222.zip (71 screenshots. SHA1SUM: 0e468e48e8727ff842258e720b323960f19b92ad)

  • VMware Virtualization for Mac Beta Released

    The new VMware desktop product for the Mac, codenamed Fusion, allows Intel-based Macs to run x86 operating systems, such as Windows, Linux, NetWare and Solaris, in virtual machines at the same time as Mac OS X. It is built on VMware’s rock-solid and advanced desktop virtualization platform that is used by over four million users today.

    The beta is now freely downloadable. Looks like Parallels is going to have some competition. Eager to see how this pans out, or if Apple builds virtualization in their next-gen OS.

    I also wonder if the VMWare images I have built will work as is on my Mac. Can’t wait to try it.

    Hoping Parallels and Fusion won’t somehow conflict whe installed on the same box.

  • The New Blogger.com Is Live and Out of Beta

    The new Blogger service is coming out of beta as I’m writing this (2006-12-19, between 8:30 and 8:45 PM EST), and you’ll notice that everything that was going to beta.blogger.com before is now being handled by www2.blogger.com. This post is actually being served by the new Blogger environment.

    Here are screenshots of what we were faced with for a few minutes.



    All seems to now be back online, since I can post this, and you can read it. ๐Ÿ™‚
    A bit sluggish right now (still caching?), but back and kicking nonetheless.

    The reason I found out was that I was writing another post when I noticed a most likely AJAX activated box, under the editing area, that was warning me that the app could not connect to the db for saving. Advanced warning? Very nice feature in and of itself, if true, since I don’t remember clicking the save or publish buttons. Would be interesting to implement if not. Might have been the live preview though, but I didn’t think the view switch required a remote connection. Might be iframe-based. Argh, now I’m curious and I’ve got to look into this… ๐Ÿ˜‰

    So big thanks, congratulations, and keep up the great work Blogger devs!

    Considering the service was down for the public for what I estimate to be around 15 minutes, that was one smooth upgrade, especially considering the scale. I deal with systems that have thousands of concurrent signed-in sessions, and I know what that means, so I can only imagine what they are facing…

    Now this puts a whole new spin on a previous post I wrote just a few days ago. The subject might just become a lot more interesting to a lot more people who now have to switch their accounts and blogs to the new platform. See Integrating the Digg Box in your Blogger Beta Posts.

    Update: 2006-12-19 ~ 9:10 PM:

    It’s confirmed. From the Blogger homepage: We’re out of beta and ready to go.

    Also, note the new no beta logo, once logged in:

    This post, as it turns out, is truly an homage to what Blogger is all about to me: a publishing tool for life, as it happens, in real time.

    Update: 2006-12-20 ~ 8:15 AM:

    Wow, the speed improvements are considerable! ๐Ÿ™‚

  • Hello to Fairbanks, AK

    Well Google Analytics tells me that my most returning visitor(s) seem(s) to be either physically located or connecting from/through Fairbanks, Alaska.


    We’ve been running the Urchin log analysis software at work long before their Google takeover, but the integration potential with the search giant are truly endless. I, for one, sure am having a lot of fun playing with all the cool stats they’re providing site owners with.

    But in the meantime, if there’s any truth to those stats, hello to you in Fairbanks, and thanks for reading. If nothing else, we’re also almost sharing a climate. ๐Ÿ˜‰

  • New Digg Features Released, Fresh from the Oven

    See Kevin Rose’s blog post for full details and a demo screencast.

    Big update today. Tons of new features to share with you โ€“ many inspired by feedback youโ€™ve given us over the last few months (thanks!). Check out this video for a quick overview, or read below for more details.

  • Funny Software Comments in Google Code Search

    Major geek humour warning…

    • Step 1: Programmers leave silly comments all over their code.
    • Step 2: Google launches Code Search.
    • Step 3: Enjoy! ๐Ÿ™‚

  • Integrating the Digg Box in your Blogger Posts

    Update: 2007-07-26: Updated formatting after import from Blogger.com.

    Update: 2007-02-06: I have posted another how-to to showcase the easiest way to integrate with the newly upgraded Digg tools. On the other end, the following content has also been updated with the new tools’ URLs and illustrates another take on integration allowing for more flexibility for content publishers.

    Update: 2006-12-19: the new Blogger is out of beta. ๐Ÿ™‚ The template hack below is now more valid than ever.

    I’ve been wanting to embed the iconic Digg Story Button in my pages, but unfortunately, the API requires Javascript and tekArtist is currently (2006-12-17) running on the (update: now out of) beta of the Blogger service, which does not allow the <script> tag to be used in blog posts.

    Another challenge is that the API expects you to set a variable holding the reference URL on digg.com (urlOfStory above). This means that I also somehow needed to store this URL for each of my dugg posts for the tool to work. Again, easy enough if I could use JS in my blog posts, but not so since I can’t here.

    In most contexts, the Digg code is fairly simple to embed:

    <script>
      digg_url = 'urlOfStory';
    </script>
    <script src="http://digg.com/tools/diggthis.js"></script>

    One thing I did find was a way to add Del.icio.us and Digg hotlinks to your Blogger Beta posts by editing your template, and using widget tags for layout. Javascript is allowed at the template level in Blogger, but since you only have one such template (for the index, posts, listings, etc), flexibility is provided through their custom template markup, which will be important in this context.

    I was still short of a place to store the Digg URL at the post level when I remembered that Blogger will let you activate a link field in your blog posts, for people who mainly point to other sites through their post’s title (coincidentally, like Digg does too). I primarily use my blog to write original content, so I link my titles to each post’s permalink, which let’s me use that data field to store, say, a Digg URL. ๐Ÿ™‚

    The requirements are met: Javascript support, and a convenient way to store and manage the stories URL on Digg.

    Now, will this hack actually work for you?

    Are you using Blogger Beta? (update: now out of beta, hack more valid than ever)
    If you’re not using Blogger, this article will only satisfy your curiousity. If you’re using Blogger and haven’t converted you blog to the beta version yet, better hurry because you will have to soon.

    Is your blog set to save post pages?

    This is actually more of a Digg (and other social sites) requirement, since we need different URLs to submit. To verify this in the new Blogger, go to your Blogger Dashboard ยป Settings ยป Archiving ยป Enable Post Pages? Be sure to select yes.

    Are you pointing to external URLs through your post titles?

    To verify, go to your Blogger Dashboard ยป New Post. If you see and use a Link text field under the Title field, then this hack might not be for you, since we use the field to store the Digg data. If the feature is off, and you want to use this trick, go to your Blogger Dashboard ยป Settings ยป Formatting ยป Show Link Field. Be sure to select yes.

    Are you comfortable editing the raw XML of your Blogger template?
    Enough said. If you’re still reading at this point, I’ll just assume you are.

    Are you willing to showcase the fact that you’re not Digg-worthy?
    ๐Ÿ˜‰ If you’re not into showing how some your posts aren’t getting dugg enough (see above?), delete the URL from the Link field, and the box will forever disappear in the swarm’s abyss. ๐Ÿ™‚

    And now finally, on to the code! Go to your Blogger Dashboard ยป Layout ยป Edit HTML. Be sure to check the Expand Widget Templates checkbox.

    First locate the following markup:

    <h3 class='post-title'>

    Remove the code around it involving data:post.link:

    <b:if cond='data:post.link'>...

    This ensure we do not have a conflict with the default template behaviour for the link data. Namely, to use the link, when set, instead of permalink as post titles destination (see update below for more details).

    Then locate the following markup:

    <p><data:post.body/></p>

    And replace it with:

    <p>
      <b:if cond='data:post.link'>
        <span style="margin: 0px 10px 0px 0px; float: left;">
          <script>
            digg_url = '<data:post.link/>';
          </script>
          <script src="http://digg.com/tools/diggthis.js"> </script>
        </span>
        <data:post.body/>
      <b:else/>
        <data:post.body/>
      </b:if>
    </p>

    Voilร !

    In short: if a link (Digg URL) is set for this post, set the digg_url to the latter and call the Digg API Javascript, with a left floating span so your content wraps neatly around the generated iframe. Else, just show show the post.

    For extra Karma, here is also the code for the Add to bar I have at the end of each post. The Digg button will disappear if your are using the above trick, so people do not try to resubmit the post more than once (and since they can Digg it using the box).

    Locate the following markup:

    <p class='post-footer-line post-footer-line-3'/>

    After it, add the following:

    <p class='post-footer-line post-footer-addtolinks'>
      Add to:
      <b:if cond='data:post.link == ""'>
        <a expr:href='"http://digg.com/submit?phase=2&amp;url=" + data:post.url + "&amp;title=" + data:post.title' target='_blank' title='Add to Digg'><img align='absmiddle' alt='Digg. ' border='0' height='16' hspace='0' src='http://img2.imagepile.net/images/ycc2106/61822091.png' style='border:none;' vspace='0' width='16'/></a>
      </b:if>
      <a expr:href='" http://www.netscape.com/submit/?U=" + data:post.url + "&amp;T=" + data:post.title' target='_blank' title='Add to Netscape'><img align='absmiddle' alt='Netscape. ' border='0' height='16' hspace='0' src='http://img2.imagepile.net/images/ycc2106/subfolders/icons//99985netscape.png' style='border:none;' vspace='0' width='16'/></a>
      <a expr:href='" http://www.google.com/bookmarks/mark?op=edit&amp;output=popup&amp;bkmk=" + data:post.url + "&amp;title=" + data:post.title' target='_blank' title='Add to Google Bookmarks'><img align='absmiddle' alt='Google Bookmarks. ' border='0' height='16' hspace='0' src='http://img2.imagepile.net/images/ycc2106/35814433.png' style='border:none;' vspace='0' width='16'/></a>
      <a expr:href='"http://del.icio.us/post?url=" + data:post.url + "&amp;title=" + data:post.title' target='_blank' title='Add to Del.icio.us'><img align='absmiddle' alt='Del.icio.us. ' border='0' height='16' hspace='0' src='http://img2.imagepile.net/images/ycc2106/65682475.png' style='border:none;' vspace='0' width='16'/></a>
      <a expr:href='"http://reddit.com/submit?url=" + data:post.url + "&amp;title=" + data:post.title' target='_blank' title='Add to Reddit'><img align='absmiddle' alt='Reddit. ' border='0' height='18' hspace='0' src='http://img2.imagepile.net/images/ycc2106/16304077.gif' style='border:none;' vspace='0' width='18'/></a>
    </p>

    I’ll still keep an eye out for other implementations, but as of now, I’m quite satisfied with the way I found. Hoping it might help others out there.

    Now if only I could write diggable content… ;p

    Update: 2007-01-18:

    People have been asking for more details about the <h3> manipulation for post titles. I had kept the above explanation very generic, because the code I had to change in the template I started from (Tic-Tac) might not be the same than in other templates, but I’ll be more specific below.

    The code I originally had to generate the post titles was:

    <b:if cond='data:post.title'>
      <h3 class='post-title'>
        <b:if cond='data:post.link'>
          <a expr:href='data:post.link'><data:post.title/></a>
        <b:else/>
          <b:if cond='data:post.url'>
            <a expr:href='data:post.url'><data:post.title/></a>
          <b:else/>
            <data:post.title/>
          </b:if>
        </b:if>
      </h3>
    </b:if>

    Which I replaced with:

    <b:if cond='data:post.title'>
      <h3 class='post-title'>
        <b:if cond='data:post.url'>
          <a expr:href='data:post.url'><data:post.title/></a>
        <b:else/>
          <data:post.title/>
        </b:if>
      </h3>
    </b:if>
  • Lightweight Feed Reader for Web-Enabled Devices

    screenshotUpdate: 2007-06-02: An upgraded version is now available.

    If like me you commute to and from work by public transit, you might also enjoy spending some of that time catching up with the latest news. Newspapers still seem popular, but they aren’t the most up-to-date and are quite impractical in a crowd. TV phones and podcasts are very neat, but they all imply audio or video and are therefore not always the easiest way to scan through the info, at least in my opinion.

    For quite some time now, what I found really fits my needs best is a simple web-based RSS/Atom feed reader that I can access from my mobile phone’s browser. So I wrote one, of course. Or more accurately, I recently rewrote my old one using the SimpleXML feature built in PHP 5+.

    The 12 requirements I set myself were:

    • K.I.S.S.: viewing tool is likely to be a small screen device, screen reader, etc.
    • Use only PHP, XML, XHTML and CSS (no DB, Javascript […] this time).
    • Typing-free user interface, selection-only user input.
    • Output standard XHTML for maximum accessibility and portability.
    • Have stylesheets for different viewing environment (handheld, screen, etc).
    • Use local caching for the remote feeds, with a 30 minutes refresh interval.
    • Clean and limit in size the entries’ descriptions to only provide an excerpt if the feed publishes all of the article’s content, instead of a synopsis.
    • Have a paging feature to keep the output very light for low memory devices.
    • Offer multiple pre-defined source selections.
    • Let users choose the number of items per page.
    • Be secure in regards to user input, caching, etc.
    • And all this in less than 500 lines, including detailed comments.

    With all this in mind, I came up with a little utility I call parseMe, which you can freely download below. Not a very creative name by any stretch, but a short one, which helps when thumb-typing the url on a phone numerical keyboard.

    • Online demo: See this mobile feed reader in action.
    • Downloads: Latest and historical packages.
    • SHA1SUM: SHA1 sum for the above files.
    • INSTALL: Basic installation instructions to get you going.
    • COPYING: Software license, GPL.
    • AUTHORS: Credits file.

    There is not enough there for me to make it a full blown project, so feel free to do with it what you want. All the code is released under the GPL. The bundled feed icon is the current standard one, as provided by feedicons.com.

    parseMe requires PHP 5+, a web server and a writable filesystem for caching. I have, so far, tested it under Apache 2+ on Fedora Core 5/6 and Ubuntu 6.10, as well as Apache 1.3.33 on Mac OS X (using PHP 5 from entropy.ch). It might also just run as is on Windows, using the various PHP and Web server options on that platform. Same goes for other platforms supported by PHP 5.

    There you go, enjoy. And if you don’t have a web account to run your own copy of the app, feel free to access the above demo from your mobile devices, but you’ll probably find the default feed list quite limited very fast.

    And for the record, if you are looking for more mobile browsing destinations, Google is starting to have quite a few nice products. The following links go to the mobile versions of the Google tools:

    Unfortunately, my phone can’t remember my Google account info, as implemented in their login form, so having to sign-in every time still makes running my own little typing-free and customizable app that much more convenient for me. ๐Ÿ™‚

  • Pre-Order a PS3 with Linux Installed

    TerraSoft is now taking pre-orders for Sony PlayStation 3 with Yellow Dog Linux 5 pre-installed. YDL5 is based on Fedora Core 5.

    If you already have the new console, you can also just order the new YDL5 distro on DVD, or download it via TerraSoft’s YDL.net Enhanced. Both options have support options.

    You can also wait a few more days and download it during the week of December 25, or take the more experimental road, and do it the other way.