Eine komplett willkürliche Auswahl von aktuellen Postings und Links, die mich interessieren und die ich für mich bewerte. Die Bewertung ist also höchst subjektiv, manchmal vermutlich auch sinnfrei.
Ein Punkt gedeutet: »Interessiert vermutlich wieder nur mich…?«
Vier Punkte bedeuten: »Das sollte aber wirklich jeder gelesen haben, aber echt…!«
One shouldn’t really need an excuse to embed this fantastic performance by Thelonious Monk, but now there is one: NIDCD researchers believe that they have identified the cognitive neural substrate of jazz improvisation.
For the study, which is published in the open access journal PLoS One, Charles Lamb and Allen Braun recruited six professional jazz pianists. The participants were asked to play a specially-designed keyboard whilst their brain activity was monitored with functional magnetic resonance imaging.
In the control condition, the musicians were asked to play an ascending or descending scale, while during the experimental condition, they were allowed to improvise. The researchers were thus able to compare the brain activity correlated with performing a simple task in which the participants‹ musical creativity was highly constrained, to that correlated with the far more complex improvised task.
It was found that the improvised condition was characterized by reduced activity in the dorsolateral prefrontal cortex, a region of the brain thought to be involved in the planning, organization and execution of behaviours. The implication is that deactivation activity in this area underlies the spontaneity required for the musicians‹ improvisation.
Read the comments on this post…
Facebook has launched pages for upcoming musicians and film makers. The social networks move parallels that of rival MySpace.
There is a set of tools that we generally use to determine how popular something is on the web: Google Trends, Blogpulse Trend Search, Technorati, del.icio.us, various social networking sites, etc.
We can now add another source to that list: Twitter, thanks to a new Twitter mashup called Twittermeter.
Over the past year, Twitter has become the consummate "buzz" platform. It is often the first place people go to talk about news or gossip, to the point where it has at times scooped major news organizations. Unfortunately, Twitter has a poor signal to noise ratio, and it can be rather muddled. So tracking buzz on Twitter has been a rather tall order.
Enter Twittermeter. Twittermeter uses the Twitter API to scrape the site’s public feed and creates a database of every word sent over Twitter. Though database overages have forced the site to display only results for the past week, they have data since November 6th, 2007 totaling over 14.5 million words from 2.1 million status messages.
Twittermeter creates buzz graphs comparing words. For example, the graph below for the word "earthquake," clearly shows a spike during the UK quake that took place earlier this week.

Twittermeter is another tool we can add to our arsenal when measuring buzz and popularity on the Internet. We‹d love to see the service offer a more robust feature set, including the ability to search for phrases, specific a data range, and offer embeddable graphs.
If you have photos, videos, music, audio, and blogs scattered across the web, you may not know how many people are viewing and responding to them. Now, with a new service called Traackr, you can organize and manage your content on the web. With Traackr, you can keep track of the popularity of your content, measure your influence, and interact with other content producers, too.
When you sign up for Traackr, you "subscribe" to various content sharing services by entering in your account information on your profile page. At the moment, this list includes YouTube, Flickr, Revver, Dailymotion, MySpace, Vox, and Last.fm.
After subscribing, your videos, photos, songs, etc. will automatically be added to your library via Traackr’s auto-discovery service. This process may take up to 24 hours.
Once your content has populated into the Traackr service, you‹ll be provided with stats like number of views, comments, and ratings, as well as trend graphs which show stats over time. Traackr will also show which of your tags get the most views. Your daily numbers are compared with others on the service and you are given a buzz and popularity rating out of 100, which is added to your profile.

You can also use Traackr’s "Campaigns" feature to mix and mash up your content by creating groupings of your media objects. By starting a "campaign," you can compare these groupings to each other to see which ones are the best performers. Using the data the campaigns provide, you can make decisions on what is the best way to market your content in the future.

If you use the Campaigns feature, you will also be put on Traackr’s "digerati" map, which is their fancy way of saying that your profile and assets are public and ranked in comparison with others. Using the "Explore" option, you can browse other profiles, or click "find people like me" to connect with others of similar interests.
Traackr’s web site still seems a tad rough around the edges. Signing up for services, for example, meant typing in your username, and pressing "enter", but it took trial-and-error to figure that out, as there was no "OK" button present to confirm your entry. The sign-up process also allowed you to enter in all your usernames one after the other, without confirming each selection, only to discover there was no "Save" button at the bottom to save all your entries.
That being said, the service that Traackr provides could be a very useful tool for web artists like song writers, videographers, video bloggers, photographers, poets, and more. With Traackr’s statistics, you‹ll know right away, your social "net worth" on the web.
It’s a pretty good bet that if you‹re not making a Twitter or Facebook application, you‹re probably making a lifestreaming application. Okay, so not everyone is into lifestreaming, but it is one of the hottest areas for development out there, and there are an overwhelming amount of services offering a way to aggregate all the little bits of your online life (which, for the purpose of this post, is the definition of lifestreaming that we‹ll use). Richard MacManus wrote an excellent primer on lifestreaming in January, but we touched on just 5 such services. The purpose of this post, rather than to review, is to just list the various options out there.
Lifestreaming apps generally fall into two categories: those that help you keep track of and display your own lifestream and those that help you keep track of your friend’s lifestreams (or both). For the sake of clarity, we‹ve focused mainly on the former for this list.
Are there any we missed? Which is your favorite? Let us know in the comments below.
We‹ve all seen the signs. Ding dong the page view is dead… well, dying. First Compete announced that they would be using attention-based web metrics, or Attention Metrics for short. Then Facebook announced that they will move to a similar metric. Perhaps most importantly, Nielsen NetRatings announced last July that they would stop using page views for comparing popularity on the web, and move towards more attention based metrics. Also, Microsoft announced this week the release of a new ROI measurement tool called "engagement mapping".
This is a guest post by Muhammad Saleem, a social media consultant and a top-ranked community member on multiple social news sites.
The reasoning is simple enough: While unique visits and page views are useful in measuring how much incoming traffic a site has, it isn’t exactly a good or accurate way of measuring impact or even engagement. You could have high incoming traffic (for example, any site that is hugely successful on social sites) but if there is an incredibly high exit rate and only 30 seconds to a minute spent on the site, the traffic numbers don’t mean much (i.e. not all traffic is created equal). Furthermore, the rise of new web technologies such as AJAX which don’t require page reloads to refresh elements or modules in a page, or video embeds (such as from YouTube) that allow you to watch a video and then browse related videos without ever refreshing the page, are making page views a mostly inaccurate measure and rendering it largely irrelevant.
While most people agree that page views are becoming irrelevant, the same people are uncertain about the future. For example, many agree that attention-based metrics are the future. Attention metrics calculate the total time spent on a site or interacting with a page (or element on a page in the case of Facebook applications) as a percentage of total time that people spend online, to measure a site’s relative importance on the web. However, there are many others, like the Tel Aviv-based Nuconomy Studio and even Yahoo’s Buzz, that believe using factors like comments on posts, ratings from users, number of times something is shared, and clicks on ads as a measure of how popular something is is a better/more accurate metric.
The problem it seems, arises because there is a disconnect between the advertising industry and the publishing industry. The reason why there is an eternal quest for traffic, not only in terms of unique visitors, but also maximizing page views per visitor, is because advertising networks let you in on the basis of how much traffic you‹re generating, and your eventual income is based on the number of impressions (and clicks). While it is true that the page view as a metric is on it’s way out, this isn’t going to happen unless a new metric comes from within the advertising industry, which, with over $20 billion at stake, has the most to gain from a more accurate way of determining where to spend their money.
But it’s not that simple either. As Scott Ross explains, different web technologies and applications have unique effects on different sites. What technologies you use and how they effect engagement and interaction on your site may depend on the size of your site, the niche you operate in, and a host of other factors. In fact, the metric that is most applicable could even change from page to page depending on the content on those pages. That being the case, perhaps one metric that is applied to everyone is just not enough and just not practical/efficient. As web technologies evolve, the page view is bound to die as a metric, but unless the advertising industry can get it’s act together and work alongside the publishing industry, a good set of new metrics that would be widely adopted is not imminent.
Technology, broadly, is a tool or set of tools aimed at making some aspect of life better, easier, or more efficient. On the web, that could mean scripting languages that make it easier for developers to create applications, or it could mean applications that make it easier for us to accomplish a task. Let’s not debate the definition of the word technology, but rather, is web technology working for you? Are so-called web 2.0 applications making your life easier or overloading you with too much information?
"It is no secret that we live in an information overload age," is how Alex Iskold began his must-read Attention Economy overview that was published on ReadWriteWeb about one year ago. We‹re constantly bombarded with information these days – news, blogs, photos, videos, Twitter, emails, text messages, phone calls, etc. All of these things are vying for and tugging at our attention.
So the question becomes: is the technology that is supposed to make our lives easier, actually overwhelming us and making our lives more difficult? And if so, how do we escape the negative effect of technology overload?
The latest in the compelling series of Oxford 2.0 debates over at the Economist web site (which we covered in December) deals with the proposition: If the promise of technology is to simplify our lives, it is failing.
Arguing on the pro side (that technology is complicating our lives) is Richard Szafranski, Partner, Toffler Associates. On the con side (that technology is simplifying our lives) is John Maeda, President Elect of the Rhode Island School of Design. The debate runs until March 6 and spectators are right now split 64%-34% in favor of the con side.
The Economist debate is speaking broadly to technology as a whole (which might include everything from the hammer and nail to the Large Hadron Collider), but the relevance to our problem of information overload is undeniable.
From Szafranski’s opening statement:
"We – hundreds of millions of us and growing – embrace the very technologies that make our lives and our relationships more difficult and fill many of our waking moments with activity. We love – to the point of gluttony – to communicate, play, invent, learn, imagine and acquire. Information technology has given us tools to do all of those anywhere and round the clock. We are awash in the benefits that high-bandwidth fixed and mobile wireless communications, email, text messages, pictures, games, data and information give us, including instant access to thousands of products. The seductive ease with which we can engage in any and all of those activities, or quests or endeavours makes it difficult and stressful to not be overwhelmed by choices. Choosing takes time and our time is not unlimited. Devices and applications that save us labour in one area may merely allow us, and sometimes seem to compel us, to invest labour in other areas.
We say or hear, "I must do my email tonight, or by tomorrow I’ll have over 600 to read." We want to buy a pot. Search on "pottery" and get 254,000,000 results. We want to find the John Li we met at a conference. Search on "John Li" and get 8,600,000 results. Do I do email, narrow the searches, eat dinner, pick up my laundry or call a friend? Because technology has spawned numerous complex variations I must repeatedly go through the act of evaluating and choosing – a labour of deciding. Technology has imposed the encumbrance of over-choice on us."
And from Maeda’s first parry:
"Recognize simplicity as being about two goals realized simultaneously: the saving of time to realize efficiencies, and later wasting the time that you have gained on some humanly pursuit. Thus true simplicity in life is one part technology, and the other part away from technology.
We voluntarily let technology enter our lives in the infantile state that it currently exists, and the challenge is to wait for it to mature to something we can all be proud of. Patience is a virtue I am told, and I await the many improvements that lie ahead. To say that technology is failing to simplify our lives misses the point that in the past decade we have lived in an era of breakneck innovation. This pace is fortunately slowing and industries are retrenching so that design-led approaches can take command to give root to more meaningful technology experiences."
Szafranski is arguing that the benefit of technology has been overwhelmed by the sheer complexity and enormity of it. Technology may have solved some problems, but it has created others that are just as negative, or perhaps worse. Or, for example, Google gives us access to so much information that finding what we‹re looking for is such a complex task that our lives are worse off for it. On the other hand, Maeda’s argument is that information technology is so new that we‹re only now beginning to refine it in ways that make it more simple. It can be a tad overwhelming when a Google search return 4 million results, but give it a few years and it is bound to get better.
This is an intensely interesting debate, and we thought it would be fun to try to continue it here with a focus on web technologies. Is the information overload that we‹re all acutely experiencing worth the utility we‹re getting out of it? Has technology on the web failed us or has it made our lives easier? What do you think? The floor is open for debate, let us know your thoughts in the comments.
Image via a Geico ad.
A company called WorkLight, Inc. is hoping to bridge the gap between the ease-of-use of the social applications consumers use at home and the complexity of the enterprise applications that are used in business. To do so, WorkLight isn’t just taking enterprise applications and adding web 2.0-like features, they are actually taking the social applications and tools that already exist and are adapting them for business use. Currently, the company works with fourteen of the most common social networks and social tools, including MySpace, Facebook, Netvibes, iGoogle, RSS, del.icio.us, and more to create enterprise-grade applications. The software, which was previously Linux-only, has now been made available for Windows servers, too.
Yesterday, we looked at the growing tech populism trend in IT, now let’s look in more detail at this specific example and see how WorkLight brings social computing tools into the enterprise environment.
The WorkLight software is a secure, scalable, server-based application that is what allows workers to view their enterprise data in any of a number of web applications and forms, both inside and outside the firewall.
The WorkLight server, which would run in the customer’s own data center, previously only worked on Linux platforms, but a Windows version is now available. (Note: their web site has not yet been updated with this information.) The architecture used to build WorkLight is standard Java and a J2EE framework, so it can be deployed on any J2EE-compliant platform.
To extract the data from the enterprise applications and/or other internal data sources, WorkLight uses application "adapters." These adapters can be for common interfaces, like SQL or web services, or can be designed for specific applications. The software comes with many standard application adapters "out of the box," but an included API allows for custom-built adapter creation. Once the adapters are connected to the data sources, configuration is done, programming-free, via XML documents.
The company’s employees can then display the data through tools like RSS, web-based homepages, desktop gadgets, social bookmarks, application mashups, and more. In total, WorkLight works with fourteen consumer technologies: MySpace, Facebook, iGoogle, Netvibes, Microsoft Live, Yahoo widgets, Apple Dashboard, Google Desktop, Windows Vista Sidebar, del.icio.us, RSS, Google Gears, and Adobe AIR.
WorkLight Gadget Accessing SAP Data
The company, WorkLight, Inc., has developed four specific solutions using their WorkLight software:

WorkLight’s WorkBook application
The WorkLight solution provides security functionality so the enterprise data stays safe. WorkLight securely integrates the data with web-based aggregators, so no data is being stored on 3rd party servers. SSL encryption is used while the data is in transit and several different authentication methods are supported, including HTTP basic, form-based, multi-factor, or the company’s existing authentication schemes can be used, like single sign-on. The cached data on the WorkLight servers can be encrypted, if desired, and user requests for information are logged with time stamps, user info, and identifiers of the data accessed.
With WorkLight’s customized tools, businesses could increase employee productivity since the staff would either already know how to use the social applications and tools or would be able to learn them quicker than the traditional enterprise applications. Companies that choose to embrace this growing trend will ultimately be one step ahead of their competitors. Says Chris Shipley, executive producer of DEMO, where WorkLight was on display in December of ›07, "We are breaking away from putting technology at the center and we are putting people at the center who have the authority to influence technology." WorkLight is certainly proof of this new shift.
This is the first article in the four-part series, "The Highly Extensible CSS Interface". Markup and images for this article:
Throughout the duration of this series, we‹ll be speaking extensively about markup – XHTML, CSS, and a little scripting. Marking up a website is akin to speaking Spanish. There’s more than one way say something, and there’s certainly more than one way to code something. (¿Puerco, cochino, cual es?)
As you plumb through my code, I‹m hopeful you‹ll see things that you might code differently or even improve upon. Or put more plainly, I expect you to call me out on things that deserve refinement or just plain suck. After all, we collectively better ourselves as a community by exchanging ideas and opinions for approaches to problem solving, and markup practices are certainly no exception. Fair enough?
When drafting markup, the factors I consider most important are that it be as 1) meaningful and as 2) lightweight as possible.
When we say "meaningful" we mean the HTML elements and selector names we choose appropriately represent the content in such a way that if we were to experience the web with all styling removed, the hierarchy and structure of the content would still make sense. Long gone are the days of spacer gifs and repeated br elements (with which some of you reading this may not even have experience), replaced with elements which logically, or semantically, represent the content:
ol)h1)blockquote and cite)This approach requires that we remove presentational information from our thinking, a concept described comprehensively by Andy Clarke in his remarkable book, Transcending CSS. I still vividly recall my early experiences with CSS as we coded a rather large-scale web application, thinking we were cleverly creating a series of presentational class names that allowed us to mark up content with elegant clarity such as this:
<p>
…only to endure a painful day of reckoning when the application required a redesign, whose 500 templates were to become anything but red Arial 10px type. I can has do-over?
When we say "lightweight" we mean marking up our content with the least number of parts possible for all things markup – elements, attributes, and values for HTML; selectors, properties, and values for CSS. For example,
<a href=""><spanhttp://cameronmoll.com/articles/widget/1-foundation.html">demo example by diving into some of the foundational code.reset.css
When I first began coding CSS-styled sites several years ago, it was common to declare a few "global" styles at the top of the master style sheet:body,a img,h1,h2,h3,h4,h5,h6etc. What was done back then as a means of overriding the default styles of any given browser eventually evolved into today’s practice of using a "reset" style sheet, typically named reset.css. As stated by the team at Yahoo, a reset style sheet "removes and neutralizes the inconsistent default styling of HTML elements, creating a level playing field across A-grade browsers…." If CSS frameworks such as Yahoo Grids or Blueprint are your thing, each of these come equipped with a reset style sheet built in. Alternatively, you can roll your own or use one written by others in the community. I personally prefer Eric Meyer’s Reset CSS, and this is the reset style sheet used in the demo for the series. (Note: The demo CSS was written before Eric’s January 2008 version of Reset CSS and therefore uses the May 2007 version. I‹ve not gone back to update the CSS to adopt his latest version. Notes about the subtle differences can be found here.) I use a single style sheet, master.css, to "import" any number of style sheets for a site. I declare the reset style sheet first, thereby allowing any style sheets that come after to override the reset styles as needed:
@import url("reset.css");@import url("screen.css");@import ...
All styles for screen display are then listed in screen.css.
Herein begins one of the first components of extensibility: An interface that adapts to different display sizes (or browser widths). Perhaps the easiest way to accomplish this is to create a fully fluid layout (width: 100%;), which can accommodate virtually any display or browser width. However, fluid layouts create wide, illegible line lengths on larger displays, among many other issues.
However, to reap the extensibility benefits of a fluid layout while accounting for issues such as line length, we need only to set limits for the maximum and minimum width of our layout. I first demonstrated this technique in the fictitious Tuscany Luxury Resorts layout created for CSS Mastery. Expand and contract your browser’s width, and watch how the layout expands and contracts but stops at 740px and 1200px. This is accomplished using the max-width and min-width properties.
Because IE7 wasn’t publicly available when this site was created more than two years ago, and because IE6 ignores the max-width and min-width properties, the markup required a nasty hack to target IE and force it to replicate max/min-width using a JavaScript extension.
Welcome to 2008. Although IE7 market share isn’t dominant enough to write off IE6 entirely just yet, we can at least begin to explore interfaces that leverage the many CSS2 and CSS3 properties now supported by IE7. And of course, these newly supported properties include max-width and min-width – no need for nasty JS hacks.
We‹ll talk more about resolution dependence in Part II, but for now we‹ll add a few lines of markup and a couple scripts to start the process. To do so, we‹ll use Cameron Adams’s excellent Resolution Dependent Layout technique. First, we reference two scripts in the HTML <head>:
<script type="text/javascript" src="scripts/event_listeners.js"></script><script type="text/javascript" src="scripts/resolution.js"></script>
Second, we add an alternate style sheet which the above scripts will import as the browser width expands and contracts beyond 1200px and 750px, respectively:
<link rel="alternate stylesheet" href="css/1024.css" type="text/css" title="1024 x 768" />
Notice that this style sheet is added to the <head> rather than being referenced by master.css.
Also take note that you can do the max/min-width thing without the need for Cameron Adams’s scripts. However, we‹ll leverage his technique extensively to do some pretty sweet tricks with the content and navigation elements in Part II Parts II & III. But for that, you‹ll have to wait another week. Peace out, yo.