episode 2

What is Web 2.0

3 Comments

No interview so Josh and I pontificate about Web 2.0 stuff.

You need a Flash plugin to view this player
play now
Time: 36 mins 11 secs13.3 MB

shownotes

  • Props to furiousBall for A fog.
  • Kevin mentions us on the TwiT podcast!
  • We got dugg! 567 diggs and counting.
  • We are F-list celebrities! Some of the interviewees have heard of us now because of the show!
  • Jeff Barr from Amazon wants to talk to us
  • Flock software is awesome!
  • Thank you for the feedback, we are going to explore further web 2.0 technology in depth.
  • Web 2.0 Meme foo camp map.
  • Don’t lock a user into your site, Microsoft office file formats, and scoble.
  • AOL opening their content for everyone and 2400 baud modems.
  • APIs and 37Signals.
  • Technology and web2.0 aren’t combined strickly together.
  • Rails black voodoo database mojo…
  • Meebo is Rails, Writely is ASP.
  • Google maps mashups.
  • Kevin Burton came up with a Metacast using feedburner.
  • Jotalot and how we learned to write Ajax easily.
  • ETech 2005 tagging discussion.
  • Community vs. the individual and how to weight tagging.
  • Tagging vs. Search and how tags are beneficial.
  • Microformats and relTags.
  • Social Aspect is important.
  • LinkedIn and how it works.
  • Participation vs. Publishing – Blogs are a great example
  • Building web services with APIs allow the user to customize and mashup however they want
  • Journalists and Chris’ high horse!
  • Hoodwink.d and how it works.
  • Flock and breadcrumbs and how it can be dangerous or hard to grow without an API.
  • Writely and how we want to try it!
  • A non-web app?!?
  • Meebo is a slick IM app, it allows users to get around firewalls for IM.
  • Non-ajax IM Alternative?
  • TechCrunch and Read/Write Web are two cool web2.0 news sites.
  • Future Interviews
  • Om Malik
  • Jeff Bar from Amazon
  • Flock
  • Kevin Rose, if we can find him!!
  • Steelpixel and the ending music (A fog, again)

Comments

byBraxton Beyer added September 29, 2005
Avatar
I haven't made it all the way tthrough this show episode yet, but at the beginning you mentioned how some poeple think Ajax is bad because it breaks the back button. I personally think it depends on what the user is doing. If the webpage uses Ajax simply to enhance their browsing then they should still have the back button. But if the webpage becomes an "application" then I think you shouldn't have a back button. None of your desktop applications have back buttons. As you mentioned it can actually be detrimental in some cases. People need to really start thinking of these new creations as applications and not just webpages. With widgets and the like more and more of these will not even be in the browser in the future. I just wanted to see what you and your other listeners thought.
byJosh added September 30, 2005
Avatar
Braxton, Thanks for listening! I do agree that Ajax should be used to enhance the browsing experience, but that can take a wrong turn. Part of the problem is most people *expect* to be able to use the back button while browsing, it is a learned UI behavior. So when you build something like a rails app and use Ajax to do database record deletion, it "breaks" the back button as I mentioned on the podcast. Perhaps a simple fix would be to set and track some kind of session var to help rehide those divs that were hidden by the Ajax deletion. Does that make sense? Seems like a small but easy workaround to me.
byPete Cashmore added October 02, 2005
Avatar
I don't want to be picky or anything, but Jeff Barr has two Rs, not one. Cheers.

Add your comment