The ‘new media’ evolution according to a millennial photographer.

Posts Tagged ‘standards’

Google Wave: The End of the Wild Web

There will be many – many – blog posts written on Google Wave, and there already have been so many created, that I’m sure this one will be lost in the void, but for whomever keeps ‘The Record,’ add me to it saying: “Google Wave will revolutionize communication.”

I’m throughly shocked by the number of naysayers out there. The reaction on Twitter after the announcement, and the excellent review of the event on TechCruch, was mixed. Some were just as enthusiastic as me, but many have the wait-and-see attitude that, to me, doesn’t recognize the pure awesomeness that is Google Wave. There are only two obstacles Google Wave has to overcome to become as widely used as Google Search that I can see: market penetration and standards adoption.

HTML5

The switch to Wave is going to rely on HTML5, a standard that has been 5 years in the making. That’s a really long time coming. The same year the standard got it’s start gave birth to Facebook, Gmail was still new, and IE was still 91% of the browser market. In Internet terms, HTML5 has been in progress since the middle ages.

Changing the basic language of the web is a drastic change, and we need to be sure that the standard is right. Yet, surely we can adapt to adding new standards at a quicker rate? Because all “modern” browsers are open-source, and have a track record for continuous innovation, it’s inconceivable to me that was couldn’t innovate on a faster scale.

Five years is an awful long time, and it’s incredible how much – of the draft spec – the browsers are already supporting. HTML5 will bring about a friendlier internet – one that feels like a desktop experience. We have the technology to deliver that – why wouldn’t we?

Read the rest of this post →


‘New Media’ Chaos

I have too much going on in my life right now. I'm back at school and shooting a ton. Not only shooting, but I'm back to editing.

I have created/taken the position of "Exponent of the Evolution" at The Daily Orange, my student newspaper. I had previously served a year as the photo editor for the paper, and has sort of assumed that my time there was up.

Little did I know that the opportunity would arise to use a lot of the knowledge that I've linked to and talked about on this blog in the 'real world' (however real an independent daily college paper is).

As the Exponent of the Evolution, I have 3 areas of responsibility:

  1. Promotion and advocacy of 'new media' at the paper. Blogging, audio slideshows, video, podcasting, video podcasting, etc.
  2. Establishing and expanding the paper's online precense. This can be simple, like promoting the website in print, or publishing headlines on twitter, to more complicated things like the creation of a new CMS for college papers.
  3. Monetizing. I serve as an advisor to the business side of the paper for online ads. Best online ad practices, new revenue streams, etc

The good news is this: this job has never existed before, and it desperately has needed to. It is critical for the survival of newspapers in the internet age to adapt to the new, online world. At this point, no newspaper has done it successfully.

Papers like The Guardian, The New York Times, and The Washington Post, have made leaps in the online realm, but none of them are able to sustain their operation entirely off revenue from the online side of the business. If print is dead, it is critical that newspapers, as the sole remaining journalists, figure out a revenue and distribution model that can maintain them.

Since this is already a bit of a disjointed, stream-of-consciousness post written at 6am out of pent up guilt for not writing a real post for so long. Let me provide a list of what I have done for the DO:

  • Twittering of all headlines @dailyorange. Our popular sports blog gets special designation for it's posts (as do videos).
  • Establishment of Final Cut Pro as our go-to video and audio slideshow editor. The result, as a movie, has a superior quality over soundslides or slideshowpro.
  • Our sports section has been publishing 'graphics' prior to games that give details on players, what to look forward to, who to watch, etc. We're trying to move this to an interactive, online, format.
  • I've developed a hypothesis: the lone reporter/photojournalist is dead. Instead, reporting will be done in teams that function like (pardon the analogy) terrorist cells. They will be largely autonomous, have a mission (a beat), and be comprised of a small group of people who have unique skills.
    TV media has been doing this for a long time – they always send out at least a camera man and a reporter.
    These teams will consist of 2-3 people (with an editor back in the office) who need to have 5 skills between them. Those skills are: 1) video 2) audio 3) photo 4) writing 5) 'personality. The last is a poor term for describing the person who is the 'on camera personality' – the person who is the front man for the team – recognizable to the public. These skills can be divided in any manner among the 2-3 members of the team.
    I've been working on this 'hypothesis' for months now, recognizing that in this new world it is impractical to expect a single reporter/photog to be able to deliver a complete multimedia piece. Non only is it impossible to shoot video, sound, and photos at the same time, but it cannot all be complied on deadline. Having a team of people working on the same project allows them to deliver a complete multimedia package for every story – on deadline.
    The point: I've decided to test the hypothesis: I have a 3 person team (who's beat has yet to be determined). At this point, they're producing a video a week on a chosen topic. We'll see where this goes.
  • Our sports section now has 2 video podcasts: On the Beat and Just Le Jus. Publishing 3 times a week, I'm hoping that this sort of thing will spread to other sections of the paper (working on Opinion).
  • I'm the front man for the DO at coPress, a collective of college newspapers who are developing an opensource, custom, content management system for college newspapers. I've written the first blog post of coPress here. This is a move to get our paper off College Publisher, and onto a more workable CMS – a critical goal for the long-term sustainability of our paper.
  • I've hired a couple of web developers (well, had hired, looks like I'm going to have to fight the board on this one) to help develop our CMS. This marks the first time the DO has hired someone specifically to develop code for our site. The sports graphics are a good example of the power that this brings.
  • We are now using vimeo for all of our videos. It's a flexible system that allows HD content hosting. We'll have our own branded player eventually, but for now, this is a great, turn-key solution.
  • Google ads don't make a ton of money, but they are something, and provide great filler for when we can't sell local ads.
  • In order to figure out who is visiting our site (and how), it's critical to have a good suite of analytics software. We're now using Google Analytics
  • Our sports section has been live blogging for about a year now from games. I'm trying to get this work ethic expanded to other sections.

I think that's the list for now. We're/I'm working on doing more. I was just approved as a full time hire, but I'm still doing the job of more than one person, and could really use additional staff to make this all work. I'll end by sharing a very rough audio slideshow I did for a local walk for cancer.


Light the Night from Daily Orange on Vimeo.


Neowin.net – Microsoft to Snub Standards Compliant Mode in IE8

Neowin.net - Microsoft to snub standards compliant mode in IE8

well, crap.


IEBlog : Microsofts Interoperability Principles and IE8

Score! IE8 will end the incredible hassle of having to treat Internet Explorer like a retarded child in web development. It's a shame we're gonna have to wait a few years, but still… this is really good news. IEBlog : Microsofts Interoperability Principles and IE8

We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.