Tuesday, March 17, 2009

Live Tweeting

Last week, I set Twitter to follow Rebecca Lobo as she tweeted from the sidelines of one of the UConn Big East games. She kept up a constant conversation, and it was too much to take in, so I quickly "unfollowed".

Schrock iPhone tweetsToday, I was so excited about the new iPhone OS3, that I decided to share the keynote via Twitter. I was not there in person but refreshing a few tech blogs as they posted quotes and photos, most notably Engadget, and summarizing what I saw and read.

The keynote was 90 minutes long, and I tweeted a lot. I tried to stick to the important points, but did interject some personal comments at times. After about 30 minutes, even though I was receiving direct messages from some of my followers who were interested and grateful I was summarizing for them, I became worried. I have over 2600 followers in Twitter and perhaps only a small group of them would be interested in the iPhone information.

Would I lose valuable members of my PLN because I tweeted every 30 seconds for 90 minutes? Would people find it too much to take in, just as I had with Rebecca Lobo's sideline updates? What if someone was receiving their tweets via SMS and they incurred charges for an overage of text messages? Would people be upset, when they opened Twitter or their Twitter client, when tons of messages from me clogged up their screen?

So, what should I have done? Should I have used CoverItLive or some other backchannel tool and just posted the URL to Twitter? Should I have only followed the blogs and put a link in Twitter to the most comprehensive coverage page based on what I had read?

I will have to give it more thought, but I don't think Twitter is the right place to "live blog". Your thoughts?

Sunday, March 01, 2009

Old browsers never die...

I receive monthly statistics about my personal Web site that gives me a lot of data. I can see that the most popular pages at http://kathyschrock.net/ are my blog, Kathy Schrock's Kaffeeklatsch, my Unofficial Guide to American Graffiti, and Rockwell Schrock's Boolean Machine, an interactive demonstration of Boolean search strategies usable on an interactive whiteboard.

Netscape browser floppyHowever, the statistic I also find interesting is the one that tells me which Web browsers the visitors are using who come to my site. This past month, Netscape 4 led the way with Firefox and IE6 not too far behind. Those three covered about 66% of the visitors.

The surprise comes when I look at the bottom of the list. About 10% of the visitors to my site use browsers such as WebTV 1.x and WebTV 2.x, Netscape 2 and 3, Internet Explorer 2, 3, and 5, Safari 1, Firefox 0 and 1, and AOL 3 and 4.

The users of these older Web browsers can probably get to my site, and navigate it, since it does not deploy the use of too many new technologies. I can just imagine the frustration these users feel when they try to visit some cool new sites or employ the use of some new Web 2.0 tools. Granted, their computers may not be able to handle the plug-ins or add-ons that some of these new technologies require, and they will continue to be frustrated until they can get a newer commputer.

Some of your teachers may not realize there are updates available to their Internet browsers that will run on older machines. Or that there are some additional browsers, such as Avant and Opera, that may work for their particular situation.

A short mention of something like this at a PD session or a faculty meeting could provide one of your teachers with the information he or she needs to be able to effectively use their older computer to navigate the Web sites of today.

(And while we are on the subject, perhaps talking about upgrading their Adobe Acrobat Reader to the highest version possible for their machine might make sense, too! You can still find the a download of Acrobat Reader 5 for Windows 95 and 98 if you look around!)

Photo courtesy of OiMax as per the Creative Commons licensing.