Today and tomorrow I’ll be at the Keeping it Realtime conference in Portland, learning about all the cool new interfaces available for a real-time web. Unfortunately, I wasn’t able to finish my liveblogging plugin before today … so you’ll be stuck hitting F5 repeatedly to get update from me in this space. On the other hand, this will serve as a real-world demonstration of why the non-real-time web is so ineffective for real-time communications.
Maybe we’ll both learn something!
- Secure by default
- Better examples – documentation that doesn’t suck
10:49am – Installing a quicky AJAX polling system so you don’t have to refresh any more …
10:42am – 10 minute break until the next session … Time to breathe for a minute …
10:39am – Having multiple sharing/interaction features on a site is ineffective. The user is one person, so breaking apart Facebook and Twitter and Tumbler and … sucks. There are ways to communicate between the two – Khris is recommending we all take a look at Backplane.
10:37am – Realtime is about different aspects of the web. Creating data, delivering data, storing data. But another great focus is processing the data to extract meaningful, marketable information.
10:31am – Great live example of a realtime interaction that isn’t a status update stream is the “Trend Watch” on reuters.com.
10:29am – Realtime is somehow associated to a list of updates presented in reverse chronological order. But that’s not all that it is. We need to break out of that stereotype. I agree 100%; there’s far more data that can be presented in realtime than just status updates. It’s just a matter of providing value so that you’re not just collecting data for data’s sake.
10:28am – “Once you lock in to one of these units, you can just rip through the rest of the industry.”
10:26am – Realtime on NBCs website makes keeping your phone nearby while watching TV essential to the experience. If you’re not watching the show and engaged with the site … you’re missing something. Fantastic use of technology!
10:24am – A concept called “push to air” allowed publishers to quickly push content and comments from a live Twitter/Facebook/Forum feed directly to an on-air TV show. This definitely makes it compelling for people to go to the site and interact with the feed. ”Hey, I might get on TV!”
10:20am – Print publishers and magazines can do interesting things, but they’re all going out of business and disappearing …
10:16am – Hearing about a simple product “anyone in this room could build in an afternoon,” realizing that I could build it in an afternoon, and hearing how much money it was sold for … I’m frustrated I wasn’t there first, but excited that I’m still there in the first handful of people in this industry. Definitely a lot of financial potential here.
10:14am – To stay relevant, old time publishers like the Washington Post are going to need to transition away from a static, “crap” experience and towards a realtime one. The new experience these days is Facebook and Twitter. It’s live and realtime. Who wants to go back to an old, static experience after that? I can definitely relate … I get more news from Twitter than I do CNN …
10:13am – “The transition from the static web to the real time web isn’t just cool and exciting. There’s a lot of money there!”
10:11am – “Twitter is doing 230 million checkins a day … and we’ll look back at that later and laugh and think it was a toy.”
10:09am – Look for the products and innovations that should be built a year from now or 5 years from now. If you focus on what needs to be built now, you’ve already missed the boat.
10:08am – Society tells you that you can’t predict the future. We think that’s crap.
10:05am – “The transition from the static web to the realtime web is as important as the transition from the quill to the printing press.”
10:02am – A “nontechnical” presentation at a tech-centered conference? Hmm …
9:54am – In the mean time, I’m wondering why so many “real time” applications (like the aforementioned Google Reader demo) are only realtime on the server side and not on the client side. It would be huge if my feed could update in realtime. Speaking as a publisher, it would be awesome if I could update my readers in realtime as well. I think there might be a definite use of adding a meta tag to the headers of my documents to link to a realtime hub.
It’s just a question of convincing more people to update content for the client in realtime once I start pushing content to aggregators in realtime.
9:53am – Awesome presentation with some live demos. Next up is Khris Loux talking about realtime and revenue. I’ll be taking a copious amount of notes.
9:50am – The Google Reader demo was a server-to-server interaction … not a server-to-client interaction. So while your feed would be updated on Google’s system, you wouldn’t see an update until you click the Reload button …
9:45am – Greetings to all of you reading this site in real-time. Google Analytics tells me there are 6 of you at the moment. Realtime web in action!
9:43am – Apparently Tumblr uses a hub to push feed content out to subscribers in real time. I’m now wondering why WordPress doesn’t use a similar setup … and just finally discovered a potential business use for SwiftStream at the same time …
9:40am – We use there parties: the publisher who has the data, the subscriber who wants the data, and the hub that routes data between the other two.
9:39am – The only widely-used protocol on the web is HTTP, even though there are better protocols out there. So to make a realtime web on a large scale, we’ll need to use what’s already available and ubiquitous.
9:33am – A clock is a real-time realtime example. You could poll it … wake up every minute and see if it’s time to get up, or just wait for the alarm to go off instead. I’d rather wait for the alarm.
9:32am – Realtime doesn’t mean it has to be now … realtime can be really slow.
9:30am – “The key to real time is to be like the kid in the backseat asking ‘are we there yet are we there yet are we there yet …’” I’m impressed, Julien must read my blog.
9:27am – Making the web real-time versus making a specific website real-time involves making services and web servers push content back and forth in real time.
9:25am – First session is a little late, but looks to be pretty good regardless. I heard Julien talking up his presentation during breakfast, so I’m looking forward to it. Now that they’ve gotten the microphone working, that is …