Audio/Mobile Blogging News
Covering the evolution of syndicated messaging (audio,text and video) over the web

My Audioblogging Channel



Stories












Subscribe to "Audio/Mobile Blogging News" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.
 

 

Tuesday, December 16, 2003
 

 

Piano blog

After listening to this piece played on the piano, you can start to imagine the many ways music could be used on the web.

Note: This audio file took me less then 10 seconds to download.

  0312162243  Go

Message from the Audlink community.


10:56:41 PM  comment []    trackback []  

 

Enclose or stream

Interesting comments about enclosures from Sjoerd.

Sjoerd says "So the only good reason to use enclosures is when you have high-quality video with high bitrates. That said, it doesn't actually hurt anyone to use enclosures, as long as you also provide a link to the enclosure in the description of the item."

I agree that enclosures are great for downloading large video files.  When I download audioblog files they are usually short and small (less then 5 minutes) which makes them download very quickly.  Enclosurers are really unnecessary in many cases of audioblogging.  We need something else in RSS today to deal with this unique case - small audio messsages. We need the audio message flag.  That is exactly where I'm positioning SAM - Syndicated Audio Messaging.  The S can stand for Short, Small, Simple, Syndicated - what ever we want.  Stay tuned.

Sjoerd Visscher's weblog: Enclose or stream. Christopher Lydon Interviews Adam Curry. I had not yet listened to any of these interviews, and as Adam Curry always as something interesting to say, I thought I'd listen to this one. So I clicked on the link to the mp3 of the interview, expecting a Save to disk dialog. …


10:06:36 PM  comment []    trackback []  

 

Scoble makes Longhorn offer to Harvard for RSS 3.0

Wow.  Looks like ATOM has done it's job.  Competition is great!

Scoble says "RSS 3.0 should be positioned as "the best way to do syndication on Microsoft's Longhorn."

IMHO Scoble's offer/spin to Harvard would clearly be the straw that kills RSS forward motion and future as a messaging spec leader.  I also think it is to early for Harvard to make such an emotional market move.  Why would they do that?  What would be in it for them in the long term?  IMHO, it's to much of a short term gain.  It would be over before they got started. 

We all know Microsoft would love to have a popular syndication spec positioned on it's new Microsoft Longhorn.  Nothing like spreading some FUD to try to get one.  I think Harvard is smarter then this. They also know the market is smarter then this.  What ever happened to the idea of working to keep open standards open for all/ever?

IMHO finding a solution to keep the RSS spec open, moving it forward as a community without big company control and major input is the only way to go. 

I believe we will see Harvard respond in some way to ATOM's latest forward movement.  They can't afford to do nothing or be seen as partipating in the old emotional polarizing wars (that they were not part of) that were just bad for the whole field. 

It'll be interesting to see how Harvard positions RSS in the short term.

Robert Scoble: Scobleizer Weblog: A letter to Harvard about Syndication.

A Note to Harvard University:

Dave Winer handed you a major gift when he turned RSS 2.0 over to Harvard. One that, I'm sure, you might not yet fully appreciate.

I've seen the light. Syndication will clearly be a major part of what happens next in the computer world. Already my ability to read Web sites has increased ten fold (I now read about 640 RSS feeds in the time it used to take me to read less than 60 HTML-based Web sites).

You think RSS isn't changing things? Heck, just look at politics. Here's a new RSS news aggregator that one of the top presidential candidates, Howard Dean, is using to push news out to his followers.

The fact that Harvard now owns the RSS specification will let Harvard play in a whole new realm of technology that our society will use. That is if Harvard doesn't blow it between now and 2005.

That's what this letter is all about.

Today Harvard's spec, RSS 2.0, is the leader in the syndication race. But, if everything remains the way it is today, RSS won't be on top for long.

Why not?

Because the market is changing. Just over the weekend there was a corner turn in the Atom camp. Atom is a format (and an API) that competes with RSS. Why is that? Because Atom started with the RSS spec and improved on it. What was the corner turn? Over the weekend Sam Ruby shipped a set of slides that spelled out quite clearly just how it is better.

That alone didn't mean much. But, today, my favorite news aggregator (NewsGator) supports both Atom and RSS. NewsGator is built on Microsoft's .NET platform. Why is that important? Well, today it might not seem to be. But, we're building our next version of Windows (code-named Longhorn) and Longhorn gives tons of new capabilities to .NET developers that haven't existed before.

Why is that a problem? Because Microsoft's developers are starting to compare RSS 2.0 and Atom and I'm seeing more and more of them switch to Atom because of the advantages laid out in Sam Ruby's slides.

What does that trend mean? Well, the value of the gift that Dave Winer gave you is going down every day. It might not look important today. Very few people are supporting Atom today. Well, except for Google, Six Apart, and IBM. Do they matter to this industry? Will the products they ship have an impact on the weblogging and syndication markets? To the Internet itself? You betcha!

Which is why I'm writing this letter. It's a roadmap of how Harvard will end up being the syndication leader in 2006, instead of Atom, er Google and IBM.

Here's what I'd do if I were at Harvard and in charge of the RSS spec:

1) Announce there will be an RSS 3.0 and that it will be the most thought-out syndication specification ever.

2) Announce that RSS 3.0 will ship on July 1, 2005. That date is important. For one, 18 months is long enough to really do some serious work. For two, RSS 3.0 should be positioned as "the best way to do syndication on Microsoft's Longhorn." The betas for Longhorn should really be rocking by that date, so you'll have tons of new developers trying to build innovative things for Longhorn. More on that later. For three, it would freeze the market for 18 months because "Mr. Safe" will not want to move away from RSS before he sees what the future of RSS will be. Also, "Mr. Safe" will want to stick on a platform that will be compatible with RSS 3.0. Today that platform is RSS 2.0.

3) Open up a mailing list, a wiki, and a weblog to track progress on RSS 3.0 and encourage community inclusion.

4) Work with Microsoft to ensure that RSS 3.0 will be able to take advantage of Longhorn's new capabilities (in specific, focus on learning Indigo and WinFS). Build a prototype (er, have MSN build one) that would demonstrate some of the features of RSS 3.0 -- make this prototype so killer that it gets used on stage at the Longhorn launch (in fact, make it even better than that, so it gets included with every copy of Longhorn that's shipped).

5) Make sure RSS 3.0 is simply the best-of-breed syndication protocol. Translation: don't let Microsoft or Google come up with a better spec that has more features.

Why would you do all of this?

Well, imagine what'll happen to Harvard's name recognition if your syndication format gets demonstrated on stage by Bill Gates? Imagine where future software engineering students will want to attend. Harvard or Stanford? Hmmm. Stanford generated Google. You do the math. How much does a single student pay nowadays? $150,000+ to attend Harvard for four years? How many students decide to attend Stanford because that's where Google and Yahoo were started?

But, it'd take some vision. It'd take some chutzpah.

Of course, if you don't have the vision, that's OK. Atom is there to take over if you fumble the football.


6:33:57 AM  comment []    trackback []  

 

Syndication in Longhorn

Can you imagine thinking and really believing the world will wait 5 years for your platform to deliver applications that others can deliver today.  By the end of the year we will have choices galore for home entertainment systems and they won't be coming from Microsoft or be running Windows.  Microsoft will still be working on fixing all the security holes in their last OS version.  In 5 years we will be levels past where we are today.  Will LongHorn development keep trying to keep up?  Will it ever deliver any new solution not in the market already?  What are these guys thinking?  What ever happened to growing your brand with the market?  5 years is way to long to not deliver anything new.  Microsoft is starting to sound and look like a phone company.

Scoble says "These are just some of the changes coming. Others are simply because of the trends of the industry. Always on computing. Service Based Architectures -- you know, apps that get and display data from Services -- will dominate by 2010. Seamless wireless. Processor power galore. Video cards with 256MB of memory or more. New Tablet-style form factors. Integration with home entertainment systems. Multiple digital cameras at home and at work."

Syndication in Longhorn?.

In my rant earlier, I hinted that syndication could change on Longhorn. But, how?

Well, Longhorn fixes some things that are holding back SmartClient adoption today. For instance, on Longhorn there's a new application delivery model. Translation: it's easier to install a Longhorn app than it is to install a Windows XP app. That'll get more people to try more software.

There's also a new security model (well, actually we'll ship most of that with XP's Service Pack 2). So, users will be more likely to install software because they'll be less likely to get viruses or spyware.

Finally there are tons of new capabilities in Longhorn. For instance, today our filesystem is pretty limited. You can have files. You can have folders. That's about it. In Longhorn you can store a ton of metadata with your files. You can also find those files much more easily. Why is that important to syndication? Because now you have a file system that supports sending files out via a syndication feed, storing them locally, and then letting users get to them in new and interesting ways.

Also, now that we have a really nice compositing engine, we can give a world-class reading experience to syndication users. One problem with RSS is that my news reader really is pretty ugly. It displays text in an ugly way. In the future that won't be true. In fact, the "underspecfied nature" of RSS might actually work to Longhorn's advantage in the future because developers could make readers that display text much nicer (and the user would be in control of fonts and such).

These are just some of the changes coming. Others are simply because of the trends of the industry. Always on computing. Service Based Architectures -- you know, apps that get and display data from Services -- will dominate by 2010. Seamless wireless. Processor power galore. Video cards with 256MB of memory or more. New Tablet-style form factors. Integration with home entertainment systems. Multiple digital cameras at home and at work.

All of these things are adding up to the increased need for syndication-style publishing. Longhorn will deliver there. Will today's syndication formats be enough? I don't think so -- does RSS or Atom provide enough functionality to deliver five videos and then display them properly in a .NET app running in Longhorn's composition engine? Which is why I think we'll need an RSS 3.0 (or, a future version of Atom or maybe even a format we don't forsee today).

But, I'm sure someone will call me an idiot within the next 24 hours. Here, let me get that out of the way for you. I'm an idiot. Now, can we talk about where the future will be? Hint: it probably won't work out how either me or you will expect it to.

Maybe we should take this up on the Longhorn Blogs. What will syndication look like on Longhorn? What are some user experiences that we could build for Longhorn users that aren't possible on XP?

[The Scobleizer Weblog]

5:55:44 AM  comment []    trackback []  

 

Flash streaming video hits the Web (MacCentral)

Yahoo! News - Technology: Flash streaming video hits the Web (MacCentral). MacCentral - San Francisco, California-based Macromedia Inc. will announce on Tuesday plans to partner with VitalStream Inc. to provide customers with the Flash Video Streaming Service. The new service will stream Flash video much the same way that Apple Computer Inc. uses Akamai Technologies' network to stream its QuickTime content. 


5:48:50 AM  comment []    trackback []  

 

AOL to unveil new Winamp

AOL to unveil new Winamp. Free and paid version of the multimedia player are set to debut this week, say sources, as the software returns to its simpler roots. [CNET News.com - Front Door]


5:38:36 AM  comment []    trackback []  


Click here to visit the Radio UserLand website. © Copyright 2004 Harold Gilchrist.
Last update: 1/1/2004; 7:38:43 AM.
This theme is based on the SoundWaves (blue) Manila theme.
December 2003
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
Nov   Jan