Saturday, August 9, 2008

Ten Ways Having Twins Has Changed My Tech and Online Life

The one thing that change always promises to bring is more change. And bringing twins into our household has definitely had an impact - changing how we manage our time, our sleep, our travels, and our activities. Now that Matthew and Sarah are seven weeks old, and with my being back at work for three full weeks, we have something resembling a routine. While I had always kidded that adding to newborns to the family would be "mildly disruptive", there has certainly been an impact to what I've been able to do with tech, both online and offline, since they arrived.

1. Whatever I'm Doing Has to Be Able to Stop At Any Time

So far, I haven't been able to teach Matthew or Sarah how to use an alarm clock, or how to make requests using a pad or paper, let alone e-mail. This means that their best way of requesting attention is crying, and I, or my wife, have to be on alert at all times. This means, for example, that I can't participate in any online gaming, even if it's as simple as hearts or cribbage, because I'd never know when I'd have to bail, and therefore, concede. Whatever I'm doing has to have the ability to be paused, or closed, without impacting somebody else.

2. I'm Not Getting Nearly As Much Online Activity Done In the Morning

Prior to having kids, I could spend a good hour answering e-mail, reading feeds, and getting caught up on the social networks before getting ready to head into the office. Now, that option is clearly gone, as I'm more likely to be awakened by someone who is hungry or needs attention than by my alarm clock. That activity now usually has to take place once they're taken care of and I've driven to the office, leaving my poor wife behind to fend for herself with a pair of ungrateful infants.

3. Scheduling Time for Evening Conference Calls Is A Lot Harder

As I don't typically wait around for press releases to hit my in box to write a story, most of my posts about new technology comes from engaging with developers early, trading e-mail, chatting on Google Talk, or taking a phone call. Now, while my intentions may be to take a call and get updated, it's absolutely likely that call will land in the middle of my feeding somebody, or our phone call could be interrupted by crying. So far, Sarah and Matthew have made their voices heard to Travis Parsons of Browzmi, Eric Marcoullier of Gnip and ReadBurner's Drew Olanoff, to name a few.

4. My iPod Touch Usage Has Gone Way Up

With the addition of the iPod Touch's 2.0 software, the product became much more useful - due to the push e-mail capability, Exchange integration, and of course, all the new applications. But the iPod Touch also has another advantage - stealth use, and one-handed browsing. It's not uncommon these days to be flat on my back with a kid resting on my chest, or sitting up and holding a bottle. This effectively eliminates my use of the laptop, but a WiFi-connected iPod Touch is a great backup plan to read e-mail, browse FriendFeed, access Safari bookmarks, and update Twitter. An added bonus? I can turn off the sound, so using the keyboard is completely silent - again, totally unachievable on the laptop.

5. Backing Up My Data Is Now More Important Than Ever

Despite having much of my life online, I've never been all that great at backing it up. I used to back up my mail and personal docs, or have an archive of company data, on a previous-generation iPod, and also used Apple's Backup program that came with .Mac. But my false sense of security went away a few years ago, when I stupidly left my iPod in the seat pocket on a plane between Chicago and Baltimore, never getting it back. So that wasn't good. Also, as my primary storage space (my laptop) has gone through its share of bumps and bruises, including getting crushed in a rented convertible this last Spring Training, I know that's not 100% reliable. Over time, as I've moved from machine to machine, I've lost very little, but it's been known to happen.

That said, I've moved our family photos to SmugMug, relying on the cloud as a backup to my own local storage, I've posted some early videos to YouTube, and I'm looking seriously at Apple's Time Capsule for home storage backup, because if I lose photos and videos of Matthew and Sarah at this stage, I'll never again get the chance to retake them.

6. My Online Activity Is More Purpose-Based Than Time Wasting

Jeremy Toeman once commented on FriendFeed that my activity on the service after having kids would never again approach the level it was prior to having kids. And while in the first few weeks after Matthew and Sarah came, I kept the same pace, if not increasing it, returning to the office and having that time eat into my schedule has probably made his prophecy true. While I'm still reading the same number of RSS feeds in Google Reader, still keep the blog updated, and still scan FriendFeed, Social Median and Twitter, I'm likely engaging in less idle chit chat and arbitrary "liking", which makes my statistics lower than before.

7. I've Dusted Off the Camera In a Big Way

I don't pepper the blog with photos of myself or my wife all that often, as I've never been much of a photographer, and quite honestly, I want the blog to be more about what I'm observing and thinking than my daily doings. I've also kept my wife's visibility low for her privacy. As a high school teacher, she doesn't exactly want her nosy students knowing her every move. That said, the twins are a lot more photogenic than either of us, and so far, friends online have really eaten up the pictures, so I'm rarely too far from our camera. And after seven weeks, I finally got Matthew and Sarah on video, and posted to YouTube. Videos of them should get more prominent going forward.

8. The Online Social Circle Is Seeing Change

Whereas previously, I would consider single guys or newlyweds my peers, I'm having a lot more opportunity to share stories and jokes with Web-savvy moms and dads who are similarly managing their time. I'm now talking a lot more with parent pals like Cyndy Aleo-Carreira and Carla Thompson or Jesse Stay and Jeremy Neal. Even uber-blogger Robert Scoble and I are probably talking as much about kids' weights and behaviors as we are debating social network behavior.

9. Blog Posts Often Get Interrupted

While I can still, on occasion, sit down and power through a post in 20 minutes or so, it's now just as likely that it will take two or three stops at the laptop to get some of the longer ones done, especially if screenshots or reviews are needed. This means a lot of saving, re-reading what I had started, and posting when I can, not exactly when I wanted to. I've even told people who want stories embargoed, when I do go that route, to get me the data well ahead of time so I can plan better.

10. No More Leaving the Cell Phone In the Other Room

If you have young kids, you know that the last thing you want to do is wake them up after some serious effort to get them to bed. That means better management of potential noise is required. Now, I can no longer casually put my cell phone down, with my keys and wallet, and walk away. Instead, I need to cart it, and the handset for our landline, with me whenever I've got the kids, or if they are sleeping, to avoid prolonged ringing and unnecessary wake-ups.

I knew having kids would be more than "mildly disruptive", and any disruptions so far have been far outweighed by the many benefits of being a father, for sure. But I know that having crossed that chasm means that how I used to operate online is never going to be exactly the same. It should be fun to keep watching as Matthew and Sarah get to 6 months, a year, 2 years and beyond, to find out what activities stay, and which go. Change always begets more change, and I know more change is coming.

Labels: , ,

Could UDO Be The Next Killer App?

By Mark Dykeman of Broadcasting Brain (FriendFeed/Twitter)

The iPhone and its similarly-gifted sibling, the iPod Touch, combine wireless Internet access and an innovative, flexible user interface to perform a number of functions from a single device. As Apple works to own the mobile phone market - as it has done with trendy personal computers, laptops, and digital music devices - many may be wondering what the next innovation will be.

I think I've found something that could be the next big thing, and a very practical thing at that: UDO, or universal device operation.

Put simply, UDO (pronounced "you do") would be a technology that would allow you to operate any electronic device that used certain control protocols and that were subject to certain security standards. You could use UDO technology, in theory, to:
  • Lock and unlock objects (car doors, office buildings, etc.)
  • Activate machines (car starter, home appliances, etc.)
  • Command or use machines like a standard remote control
We have bits and pieces of this technology strewn about the world today, including:
  • Remote controlled car locks and car starters, either by wireless remote or mobile phone
  • Building access via RFID chips in security badges
  • Dedicated remote controls (e.g. TV, home entertainment center, model airplanes)
  • Wireless/RF scanning of barcodes to execute instructions
If we had a single technology or protocol, using wireless Internet or other communication channels, that we could use to program devices to follow certain commands, you'd have something more versatile and powerful than the Space:1999 comlock (a portable video communicator that could also lock or unlock certain kinds of doors using wireless technology).

The iPhone's interface and wireless capability would seem to be ideal for portability, touch sensitivity, and flexible interface.

There are some considerations:

This protocol would have to be built in to virtually every electronic device to be useful. This might include additional hardware and software for these devices.

Security would be key:
    You might want to use biometrics to restrict access to your UDO control
    It would have to be cost effective
    It would have to be dead simple to use.
I think this would be a very practical use of Internet/Web technology which could be adopted by large numbers of users and would be a logical extension of the directions that the iPhone and Touch are heading in.

What are your thoughts on UDO, and where would you like to see this implemented?

Labels: , ,

Wednesday, July 30, 2008

New Facebook Design Confuses Many, Obscures Features

By Jesse Stay of Stay N' Alive (Identi.ca/FriendFeed)
(UPDATE: I wrote this post originally with the intent to show several missing features, which appeared to be missing to me over the last week or so. As you can read in the comments, I was very quickly corrected - either Facebook has recently re-added those features in place, or they are, as I mentioned in this post, just hard to find! I realized we had something bigger on our hands - If Facebook can confuse me, how many others will also be confused? I've modified this post to reflect that.)
With every new site redesign comes angry users ready to criticize the change. People just don't like change. I saw this first when I redesigned the site, SteepAndCheap.com (where I went by the nick, "SAC Hacker" in the forums). We saw every possible reaction to the new design on SteepAndCheap a few years ago, but in the end, people settled down, got used to it, and realized it was actually better for them in the long run. We're seeing this currently with Facebook's new design, even when only 5% of their users have actually switched to the new design! However, some of that outrage may be warranted, as you know (look in the comments), I originally wrote this thinking several features were missing, only to realize even I was confused at where to find them!

Facebook seems to have moved the Pages and Groups on users' profile pages. Now, to access Pages or Groups, one has to click one page deep from the main profile Page into the "Info" tab, and if you scroll down your Pages and Groups will be in the main section below. What's even more odd is that there is no way to drag those Groups or Pages around like there was before in order to put them higher up for users to see. Facebook evidently does not want users to see Pages and Groups as the first things users see when they visit your profile, as the company seems to be saving the business portions of Facebook for later. They seem have put low priority on them lately.

It's obvious that Applications have now moved to the "boxes" tab, and Facebook has made this clear in several announcements and blog posts recently. They did cut developers short however in the time frame they offered, and developers aren't happy either. For this reason you'll see most of your applications in that Boxes tab, rather than on your main Profile page, and applications like the FriendFeed app on Facebook no longer display detailed information in your news feed, but rather, "so and so has new activity in FriendFeed".

Lastly, up until just recently it appears (because there is an entire thread of people here that seemed to be missing it), a much needed and appreciated feature, the "ignore all" feature for applications was gone entirely. Facebook seems to be trying to remove spammy activity by applications, but somehow this was overlooked when they launched the new design it appears. It's a welcome sight to see that "ignore all" button back in your requests again.

As you can tell from the original revision of this post that I mentioned above, even I was confused by the new design (and I wrote two books about Facebook)! While I like how clean the new design is, getting to know where features are and aren't will take some time. This is going to confuse many of you, and there will be some backlash. My hope is, that with time, all this will work out for a better, cleaner, less spammy Facebook that we can all appreciate.

There are probably many more things that have moved or changed - please share them and your frustrations in the comments!

Labels: , ,

Monday, July 28, 2008

Me-Too Software and Web Apps Often Find Their Own Niche

As the price to develop Web applications and communities has decreased, and investment in people is less-demanding, it's no surprise that we've seen a boom in sites with significant similarities - be they social networking, lifestreaming, status updaters, online file storage or virtual worlds. While the rule holds true in software as it does in Silicon Valley, that the vast majority of products may meet a less than optimal fate, the potential payout continues to draw development, with new brand names hitting our RSS feeds on a daily basis.

The seeming onslaught of new services had the omnipresent Chris Brogan asking frustratedly yesterday, "Who's writing all these me too software apps? Do they feel accomplished?" Brogan later gave the services Kwippy and Yokway as examples of two services that had recently come across his view, adding, "(I) just dont' see why we need yet another of something we have in spades. Where's the innovation?"

Sometimes, in this age of instant analysis, determining the differentiation and purpose of a new site can be hard, especially as the bloggers and technology reporters try and grasp the new site and place it in the context of existing applications that are more well-known. (See: Inquisitr: Yokway: Sort of FriendFeed Meets Del.icio.us for one example)

Whether it's in the name of differentiation or competition, it's rare that a developer or startup team will be aiming to make a carbon copy of an existing site. RSSmeme debuted, after ReadBurner, to show the most shared items in Google Reader, and progressed differently, offering a custom FeedFlare and featuring deeper index with more linkblogs than ReadBurner, while ReadBurner partnered with multiple RSS engines, including NewsGator and Netvibes. Facebook was like MySpace and Friendster before it, but initially just for the college set and later high school, before opening up, and later adding a development platform.

There is a long history of services and software that have striking similarities to one another. That a product exists doesn't mean that any potential competing product should walk away and cede the market, delivering a monopoly. As Disqus' CEO Daniel Ha told me back in June, the existence of competitors like SezWho, Intense Debate and JS-Kit help let him know he's in a worthwhile market to pursue, even if it's a rare blogger who has plans to implement multiple commenting engines. The existence of Digg didn't stop Mixx from debuting, and the existence of HotBot, Lycos and Excite didn't look like too much of a hurdle for Google to get going.

Rob Diana of Regular Geek, in the FriendFeed comment thread spawned by Brogan's question, said, "Until someone dominates the space you will see a lot of similar applications," while Clint Ecker wrote, "The market will bear out the niche products and the unsatisfactory ones will fade away and disappear until the community has selected the 'best' service."

But even the selection of a "best service" doesn't mean there won't be more developers trying to crack the market. Plurk and Identi.ca are two recent approaches to microblogging, taking on Twitter. And Cuil's entry into the search market came at a time when Google's enjoyed its largest market share ever. The likelihood of these challenger sites to replace the market behemoths is very small, both short term and longer term, but just about every site and service can develop a dedicated community who swears by it - arguably making the developers' efforts worthwhile. You recently saw this happen when the niche community sites of Ballhype and Showhype, arguably Digg clones, were acquired for $3 million.

From the outside looking in, developers don't see themselves as copycats. Instead, they likely see opportunity, finding weaknesses in a competitor's offering, or finding a new way to seemingly offer the best of both worlds. And just because they aren't enjoying a majority market share in a given metric by a certain time period doesn't mean their efforts were in vain. There's no hard and fast law saying you need to sign up for every lifestreaming service, every social network, every microblogging client and every RSS reader, but as more options and alternatives are out there, there will be a small group of people who prefers the new entrant, whether it be for its GUI, its compatibility with plug-ins, widgets or extensions, or implied productivity.

As an early adopter, I'll usually be checking out most of these services, and I welcome more. It's not about finding how much they're all the same, but determining the differences, and seeing what I can do that's new. I might, sometimes, never use a service again, if I don't find it to do what I had hoped. But often, when I check back in a few months later, I'll find a small community that's calling it home, or see the development didn't stop at day one, making it a richer experience. So, development community, keep it coming. Let's see those new apps, the new innovation, and the new services. It will never be enough.

Labels: , , , , ,

Tuesday, July 22, 2008

Identi.ca Launches SMS Support, Sort Of.

Guest Post By Jesse Stay of Stay N' Alive (Twitter/FriendFeed)

It seems, amongst all the identi.ca, Twhirl and Posty hoopla, today we seemed to have missed one important feature -- that identi.ca, at some point recently, launched SMS notifications via their settings interface.

Currently, if you log into identi.ca, then click on settings in the header, you'll notice a new tab in your settings called "SMS". If you click on the SMS tab it allows you to set up your cell phone among various carriers and notifications will be sent to you if you opt to do so.


The service doesn't seem to have full SMS support yet though, as they are apparently utilizing SMS via e-mail which according to my own sources in the industry, isn't the most reliable method of sending SMS. I tried it out, and while it seemed to work well by sending all my friends' updates to my cell phone (there is no ability yet that I'm aware to turn off notifications for individuals via SMS, which is a major problem), the messages I received were unorganized and hard to read.

Each one was also sent from a different number, making it hard to keep all the messages in one place. It also seems that you can't post messages back to identi.ca from your cell phone, another must have if it is going to be a true competitor with Twitter or Jaiku. You can see how bad it got after 10 messages or so on my iPhone.

Having SMS available as an option on identi.ca is a nice, and very welcome, addition. This shows they are truly in the game and have strong potential to be a mobile status and communication tool like Twitter. For me, I like to use SMS with Twitter to filter out the posts of the thousand or so I follow into a small segment I can pay attention to. SMS also enables me to easily message others via one interface, and post statuses from wherever I am located. Knowing this is on its way with identi.ca, along with Monday's launch of both Twhirl and Posty integration, makes them a strong consideration for me to begin using much more often now. However, I still think they have a long way to go before they fully match Twitter's feature-set and can compete head-on.

I'm excited to see where this all ends up. You can find me actively using identi.ca at http://identi.ca/jessestay. Louis can similarly be found at http://identi.ca/louisgray.

Labels: , , ,

Thursday, July 17, 2008

Twitter Chokes Unauthenticated API Requests By IP, Sites Gasp for Air

Twitter's struggles with handling high user load have been well documented. To help the embattled site stay up between Fail Whales, they've at times reduced features to just try and keep afloat, blocking the replies tab, reducing pagination, and blocking Instant Messaging, for example.

They've also visibly tweaked the rate for authenticated API hits, first down from 70 to 20 and back up to 100. But until recently, unauthenticated API requests were unlimited, which all changed Wednesday night around 5 p.m. Pacific Time, when Twitter ratcheted them down to the same 100 per hour per IP address, effectively crushing many external services that relied on Twitter for their data. And this was done without public mention on the Twitter blog.

As you can see in this Google Groups thread, Alex Payne of Twitter told developers last Thursday:
"In our continued effort to keep things fast and prevent abuse we're planning on introducing rate-limiting by IP for unauthenticated API requests. We'll allow 100 unauthenticated requests per IP per hour, just as we currently do with authenticated requests. Please let us know if you foresee any ghastly issues with this change."
And while that sounds all nice and dandy, there were a number of developers who did see "ghastly issues", ranging from Kee Hinckley, CEO of Somewhere, Inc., Richard Cunningham of FriendBinder, and Joel Strellner of Twitturly, each of whom runs a product that depends strongly on unauthenticated API requests from the microblogging service.

But it didn't stop Twitter from making the change, even as Jodee Rich of PeopleBrowsr wrote, "this will blow us out of the water."

Since throttling down the unauthenticated API requests, services that rely on this data are a mere shadow of their former selves.


Twitturly says on status page: "Due to recent changes in Twitter's API, Twitturly is slowly dying."

Similarly, Twist's Twitter charts only show a fraction of the data they did at the beginning of the week. (See: "morning", "starbucks" and "computer".)


Twist's Twitter Search for "Morning"


Twist's Twitter Search for "Lunch vs. Dinner"

In response to the changes, FriendBinder's Cunningham said he will now be changing all API requests to Twitter to be authenticated, to work around the problem. He wrote me, in an e-mail, "There are also some parts of the API we cannot even attempt now. User authenticated requests limits are shared with other sites that the user has used - so we might not be able to get any updates for them if some other site hit the limit for them."

You can see this yourself by trying sites that aim to help you bulk follow those Twitter users who are following you. If you use a site like Twitter Karma, and then try to use Less Friends, you will get a nasty note that says you have exceeded your 100 requests per hour limit. And if you're like me, having fallen way behind on following folks, you might be revisiting one of these sites religiously every hour for the next few days until you're caught up.


Less Friends and Twitter Karma Get a Mere Fraction of the Updates

Last month, Jesse Stay wrote that developers were bailing on Twitter, thanks to outages and broken APIs. With changes like this, despite improved uptime of late, the end to Twitter's problems is nowhere in sight, and services that hoped to tap into their API this way are sore out of luck.

Note: These restrictions do not impact the four golden partners of Twitter's XMPP feature, including Zappos, Summize, FriendFeed and Twittervision.

Labels: , ,

Friday, July 4, 2008

TweetDeck: New Twitter AIR App With Summize Integration, Groups

For many, given the up and down status of Twitter, the search functionality of Summize has become a must-have to find conversations, replies, and topics. A new AIR app, debuting today, called TweetDeck, features full integration with Summize, and lets you customize your Twitter experience, through dedicated columns for your feed, your replies, searches, and even the ability to create custom groups of those you follow on Twitter for a micro-feed.

Authored by Iain Dodsworth, TweetDeck (available here), could give other AIR options, like Twhirl and Feedalizer some new competition. While I'm not typically a huge fan of AIR apps, I found TweetDeck to offer a great number of customizations that have me keeping it open and on the desktop around the clock.


The TweetDeck Interface (Click for Larger Image)

TweetDeck offers four major columns in which to organize Twitter data: "All Tweets", essentially your friends' timeline, "Replies", showing replies to you, the equivalent of Twitter's replies tab, "Search", which will keep a running search window open for a term you've selected, and "Group", which lets you make a sub-set of those you follow on Twitter, and make a miniature timeline.

Unlike some applications, whose preferred mode is single column, getting me only my Twitter stream, TweetDeck is actually very well built for being used in full-screen mode, of course, running in the background. Now, with one glance, I can see all updates, see all replies, and keep my eye out for keywords. And rather than force me to go out to Summize to search a keyword, TweetDeck has integrated Summize's search capability and also its ability to find replies, although, in version 0.15 beta, released just this morning, Twitter replies now have precedence, should there be duplicates.

You can also, of course, post your own Tweets from within the app, just by hitting the "Tweet" button at the top and entering what you want to say. TweetDeck counts down the number of characters to make sure you don't exceed 140.

The recent strain at Twitter has resulted in the service reducing the number of API calls developers can make to get Twitter updates, and there, TweetDeck has you covered as well, so you learn if there's any slowness, where to lay the blame.

In the bottom right corner, TweetDeck reports: "Twitter Status: Pretty much ok" or "Twitter Status: Rate limit exceeded" when there's a problem. It also provides a status as to when it was last updated, how many tweets were received, and when the next update is expected, polling every couple minutes.

In addition to the integrated search functionality, I was most impressed by the grouping function. I was able to create a group called "Lady Digerati", and could hand-pick which Tweeters would be followed, including @corvida, @sarahintampa, @veronica, @TheMacMommy, @NicoleSimon and others. You could, of course, make your own sub-groups to get a different subset.

While Jesse Stay and others have said Twitter's major issues have decimated the developer community's efforts around Twitter, there are still some looking to innovate, TweetDeck being a good example. Of course, given it's early status, there might be some issues, but it's worth taking a look, as the application has some great potential.

Labels: , , ,

Monday, June 23, 2008

Is Your Web Getting Filtered? What's Blocked or Unlocked?

Entering our third full day here at Lucille Packard Childrens' Hospital with our twins, I have to say I'm impressed with the easy access to high-speed wireless Web. For me, wireless high-speed access is a must, and I don't have much to complain about. Interestingly, the hospital's system, by default, has instituted filters, in theory to protect them legally, and maybe to conserve on bandwidth. This doesn't bother me too much, but as I surf, seemingly with one hand tied behind my back, I find that the sites they've opted to block, and those they've allowed to go through at times have me scratching my head.

I noticed I couldn't log into my Mac Mail via the desktop application right away, but Webmail was fine. I later noticed some sites were blocked when I tried to visit Athletics Nation and follow yesterday's A's game. Safari reported being unable to visit the site. I checked other Sports Blogs Nation sites. Those too, were all down.


A Sample of Approved Sites and Those Blocked


Then, after many on FriendFeed had demanded some early photos of Sarah and Matthew, I tried to take the pictures I had from the last two days and post them to Flickr, feeding the beast. But they were blocked. Then, I tried to log on to my FTP site and upload them to louisgray.com directly. No dice, again.


Sorry, can't upload via FTP!

Luckily, I did find a work-around. By sending the photos via the great Mail2FF program, as attachments, the photos themselves were saved on Amazon's Web Service and archived there. (It's the same way I "cheated" and got FriendFeed to host the graphics in this post for me)

After last night's post on my 10 beliefs in blogging and the Web, I saw someone had posted the story to Hacker News. But I couldn't see who, again, thanks to it being blocked.

IM Blocked: iChat and Google Talk don't get through.

The blocking seems well intended, but random. It makes sense that I shouldn't have access to Fleshbot or AdultFriendFinder (mind you, I just checked them to see if they were filtered), but it makes less sense to have sites like Sports Blogs Nation blocked, when ESPN.com is approved, or to have Hacker News blocked if Techmeme is given a pass.

I'm lucky that I usually don't encounter Web filters. I have free-flowing access at home and at work, and this weekend's experience has been outside the norm. If you are filtered, whether it be at work, at school, or at the library, what sites have you found blocked that you think are wrongly stopped? I'm curious to see if this setup is too aggressive, or in line with your own experience.

Labels: , ,

Wednesday, June 18, 2008

twitAbit Debuts as New Service to Escape Twitter Downtime

Many Twitter users have a love/hate relationship with the service. They love what it does, helping people communicate in real time, from the Web or their mobile phones, but they hate that it hasn't scaled to meet demand. In its place, a new crop of services is rising to work around the downtime. The latest, debuting today, is called twitAbit, which leverages store and forward capabilities to ensure that Twitter fail doesn't ensure your own fail.

The Twitter "fail whale" is well known and a great number of users are looking for a way out. Some have left Twitter. Some are just using it less. Others have moved on, to Plurk, to FriendFeed, or Pownce. But leaving Twitter comes at a high cost for those who have invested time in building relationships, and in some cases, thousands of followers. Even despite the many outages, the vast majority of Twitter's user base has largely stuck it out, hoping for better times.


But if those better times don't come right away, twitAbit is prepared. The service offers a simple form, asking for your user name and password, what you are doing, and a link. It appears to be a project of betaworks, and was announced on the switchAbit Web site, which RSS and blogging guru Dave Winer announced back in May.

At the time of posting, Winer promised Flickr to Twitter functionality, and a second Twitter application, most likely twitAbit, Although it's not 100% clear, he has spoken of a need for a decentralized Twitter, and this could be the first step.

Also: You can see Winer's first "tweet" from twitAbit back on June 13th.

Labels: , ,

Monday, June 16, 2008

OneSpot Makes Publishing Personalized Memetrackers Simple

News aggregation sites that can help highlight the freshest, most relevant or most popular news from around the Web are essential to separating the signal from the noise. But all too often, these memetrackers are siloed, without readers having all that much input into what's considered most relevant, or determining what content gets in and what does not.

The success of Gabe Rivera's Techmeme has had many thinking how they could create their own personal Techmeme, featuring the best of the Web, but only for those topics they're most interested in, or from those sources they choose. Gabe's product, despite some competition from BlogRunner and Megite, as well as others, has remained the most relevant and accepted leader in the space, but its algorithm has left some people wanting more.

Duncan Riley of The Inquisitr leverages FriendFeed, building what he called QMeme, displaying the most popular content on FriendFeed over the last 24 hours from those he follows. Corvida of SheGeeks once said LinkRiver was her own personal Techmeme. Rafe Needleman of WebWare once called ReadBurner a Techmeme for Google Reader. But none of these solutions, while interesting, offer the individual manageability of a new product that's now come available to the Web at large: OneSpot.

Already in place at the Wall Street Journal and the Washington Post, as well as some more vertically-oriented sites, OneSpot enables anybody to leverage the service's more than 250,000 RSS feeds to design and configure a personal meme, simply by starting with a few "trusted" RSS feeds, and letting OneSpot do the hard work of finding similar feeds on the same topic, and then determining the most popular content.

The result is a highly customizable personal memetracker that can be displayed on a full Web page or as a widget, drawing from the criteria you set, and publishing as frequently as you would like.


The OneSpot Dashboard Lets Me Choose Topics and Schedules

In the last few weeks, I created three memetrackers using OneSpot. One used my blog as the center of the universe (as most bloggers would like). One focused on technology at large. A third, and so far, the most interesting to me, focuses solely on the creators and participants in social media, link aggregation and lifestreaming.

See:
LouisGray.com: Top Stories > OneSpot
LouisGray.com: Social Media Top Stories > OneSpot
LouisGray.com: Technology Top Stories > OneSpot

To configure my personal OneSpot publication, I entered a few "Trusted Feeds", and OneSpot then found thousands of "Related Feeds", allowing me to see the name of the feed, when it was last updated, and giving me two choices: to add the feed to my "Trusted" bucket, or to "Remove" it from the list of options.

I found OneSpot's recommendation engine to be very good. If I showed louisgray.com as a Trusted Feed, OneSpot recommended SheGeeks, The Last Podcast, the Official ReadBurner Blog, Benjamin Golub, Webomatica and a few others, no doubt leveraging my own previous linking behavior.


Trusted Feeds I Posted to my Social Media OneSpot


Related Feeds Suggested for my Social Media OneSpot

For the Social Media publication, I had added the main blogs for FriendFeed, ReadBurner, Toluu, Shyftr and others, and OneSpot recommended I also add blogs from Assetbar and Twitter. Very cool.

OneSpot is extremely flexible, letting me schedule updates as frequently as 60 minutes apart, letting me customize the memetracker's look and feel, or even to add up/down voting recommendations or comments. At a time when news organizations like the Associated Press are throwing up roadblocks in how you link to or highlight their content, why not use OneSpot to make your own memetracker using sources you trust?

Labels: , , , ,

Feedly Brings New Social Experience to Start Page, Leveraging RSS

In the last two years, there have been a number of attempts at taking what's been a solitary experience of reading one's RSS feeds in isolation, and adding new social elements, sharing feeds with friends, discovering new feeds, or adding comments and notes.

Following a lengthy incubation period, intended to get the product rock-solid with an army of features and a sharp interface, Feedly hits the Web today with their own take on the social start page - using your Google Reader subscriptions at its core, but layering on intelligence that learns from you, including your reading patterns, to personalize your information waterfall.


The Feedly Cover Page

Feedly was first known as Feeddo, but recently changed its name to eliminate confusion with other products on the market, and has been in private testing for several months. I first started talking with Edwin Khodabakchian back in mid-February, and even then, the project had been under scrutiny from more than 100 early testers for the better part of three months. The goal? To bring a new, graphical, view of feeds, via Google Reader, and add multiple social layers on top of what's already recognized as the world's most-popular online RSS engine.

Khodabakchian brings a strong resume to the project, once being a Chief Architect at Netscape, and later, the CTO of eCommerce at AOL, following that company's acquisition of Netscape, as well as four years as the co-founder and CEO of Collaxa, later acquired by Oracle. Khodabakchian also considers the team behind Yokway close friends and has been a visible early beta tester of that product.

The months and months of quiet effort appear to have paid off. If you have a FireFox browser, you'll want to see this new approach to taking in the day's news. In my own testing, I kept uncovering new features, and I'm sure I won't get them all here. But here are some of the main elements:

The Magazine Cover

Feedly looks at itself as a start page and magazine hybrid. The main cover page, noted by an icon that looks like a book, shows the latest new items from subscribed feeds, using your own learned reading activity, combined with your sharing history in Google Reader, to bring what's anticipated to be your most interesting stories to the very front. Feedly also, in the bottom right corner of the page, has an "Explore" option, where new stories from similar feeds you may not subscribe to, are available.

Like most feed readers, you can click on any of the articles' headlines, and view the full item. But Feedly isn't intended to be a passive experience. From the article, you can:

1. Save it for later reading.
2. Annotate it (more on this later)
3. Recommend it to friends
4. E-mail it.
5. Send a note about the article using your Twitter acount.
6. Preview it, giving a glimpse of how it looks from the source site.
7. Copy the link to your clipboard.

From that article, I can go back to the cover page, view other articles from that source, or make a new selection from my Feedly toolbar.

What's New

The What's New page combines the latest updates from your subscribed feeds with recommended articles from friends, and again, highlights those feeds and items you are most likely to read, based on your past behavior.


Due to Feedly's tight integration with Google Reader, the items in the What's New page are segmented by topic, gathered from your folders in Google Reader. Mine, for instance, include "Technology", "Web 2", "Apple News", "Mac Rumors" and "Misc" for all other blogs.

While viewing "What's New", I can not only see what the latest feed items are, but on the right, all sources of news are listed, with the number of available items at each source. If there's a new story from one site, it'll be bolded. If I've already read all the stories, they won't be.

As with the cover page, the lower right corner always offers me new feeds to add, should I find them interesting.

The Wall


The Wall can act as your social springboard to both shared items in Google Reader and Twitter updates. If you opt in to synching your Twitter account with Feedly, you can use the Feedly interface to get tweets from friends, as well as see items shared by friends within Google Reader.

This can become a two-way conversation as you annotate articles or send posts out to Twitter from Feedly.

Integrated Google Search

While some sites don't think about search until well after launch, Feedly has developed an extensive tie-in with Google Search and Google Reader on day one.

For example, if I search for the term "Caramilk", a word not often used, I not only found an article from Mark Evans called "What's the Caramilk Secret", but also related items, including WinExtra's Would you hammer a nail with a shovel? and Tris Hussey's response, FriendFeed explodes onto the scene, but it is still an information fire hose, both of which referenced Mark's article.


Feedly's Results for "Caramilk"

Searches for more frequent terms, like Apple and Yahoo!, had their expected 1000+ results, in reverse chronological order.

Annotation and Sharing

Similar to Google Reader shared notes, you can make notes on any item within Feedly and share it on "The Wall". But unlike Google Reader, you can highlight the portion you're commenting on, and make notes, as you are more accustomed to seeing in Microsoft Word's Track Changes option.

On any item, you can either click the "annotate" option, or select the desired text, and an option comes up to either "search related articles" or "highlight". If you chose to highlight, the selected text is in fact highlighted, and you can add a comment. As you can see in the below two examples, I was able to add comments next to articles from both Sarah Perez and Steven Hodson, and my own avatar was displayed next to each.


A Note on WinExtra's Item in Feedly


A Note on Sarah Perez' Item in Feedly

Tweeting an article is similarly easy. If I find an article I like, I just click "tweet" and a new box opens up with the headline, an automatically generated TinyURL, and a note on how many characters I have before running out of Twitter's 140 character limit.


Clicking e-mail opens another box with a simple "To:" field, and a "Note" field. As you start typing, Feedly automatically shows contacts you have in your GMail address book. Select one of those, or enter a new contact, and hit send.


Managing Feeds

Feedly is 100% synchronized with Google Reader. Add a subscription through Feedly, and it will show up in your Google Reader. Read an article in Feedly? It's marked read in Google Reader. Recommend it in Feedly? It's shared in Google Reader. Want to move a blog from one folder to another in Google Reader? You can do that through Feedly. Feedly essentially brings you all the aspects of Google Reader we've grown accustomed to, but displays them in a new, friendly, visual way, while extending the feed universe out to Twitter and e-mail, and adding social elements.



Feedly also takes things a step further, showing all your feeds in a single dashboard view, letting you toggle your favorites, or in a unique twist, offering what's called "Spring Cleaning", where, in theory, should you get bogged down with too many updates, feeds are flagged warm or cool based on your reading behavior and how often you mark them as favorites.

Other services, like Assetbar, got dinged for packing in too many features and not focusing on delivering a clean interface. Feedly has largely avoided this problem through strong segmentation between portions of the service, and through leveraging existing accounts, including your Google profile, existing friends in Google Reader and your GMail account.

If you're the type of RSS power user who wants to read hundreds of items through aggressive keyboard navigation, then Google Reader still can't be beat, but if you want to pick the very best from the many feeds you have, share items with friends and find new sources for news, Feedly is a compelling option. They've clearly done a lot of work to make their solution feature rich, with a flexible, clean, user interface, and options not found anywhere else.

Check out the new offering at www.feedly.com.

Labels: , , , ,

Sunday, June 15, 2008

Why Disqus Is Winning the Web Comment Battles, and What's Next

Tonight, I was lucky enough to have dinner with Daniel Ha, the CEO and co-founder of Disqus. One of the advantages of being in the Silicon Valley is that in many cases, I can actually engage with and meet the people who are moving the industry forward, and while I don't consider myself a big-league hob-nobber, the occasional social visit can be rewarding. I won't jeopardize future meetings by giving away the company store, but I definitely came away from the evening feeling even more committed to Disqus and the company's strategy than I was before.

As you already know, I first added Disqus to my blog with Daniel's help, after finding I was unable to integrate the service into my Blogger template. He went above and beyond the call of duty to get me up and running, doing such an excellent job that the effort was noted by Mashable.

This customers-first attitude shown on the Web was evident off-line as well. Daniel more than once apologized for the brief downtime Disqus suffered last Friday, saying that he had awakened to a swarm of e-mails from frustrated users, not to mention my post, and said that we were right to call them on it, as Disqus comments are now such an integral part of our blogs. He assured me the team knew the issues behind it and was working diligently to make sure another similar outage would never occur. Disqus' popular sidebar widget was to blame, putting a great deal of strain on the service, which has since been lessened.

Also, during the meal, Daniel asked me a question that he says he loves asking users, "How can we make Disqus work even better for you?"

Had I been properly prepared, I could have brought an index card along with responses at the ready. Duncan Riley, for instance, wants trackbacks and FriendFeed integration. I asked for better statistics and analytics, and had questions on how older posts were displayed on my Disqus dashboard. But the truth is that I'm already quite happy with Disqus, and have grown to expect to see it on other blogs, making myself less likely to comment on other sites that don't offer the centralized comments feature.

On a personal note, I was struck by how young Daniel was. At the old age of 31, I'm now reaching the point where just about every Major League Baseball player I like is younger than me. But the CEO of a company I think could have a big impact on the future of the Web being 22, and a UC Davis computer science graduate just this year? That's not fair, and I'm not used to it. Coincidentally, my youngest sister also graduated from Davis on Saturday, sharing Daniel's class year.

Daniel started Disqus in 2007 with friend Jason Yan while in Davis, and this month, doubled the team, adding two new coders, Andrew Badr and Devin Naquin. (See: The New Guy and Hello, world!)

Andrew's already busy letting people know about upcoming features, promising the addition of trackbacks "sometime in the next week.", on the Oracle AppsLab blog. He also answers many people's fears as to the portability of the data, saying, "Better options for import and export are in the works, and will be part of our next major release."

As I wrote at the end of May, Daniel has helped lead Disqus to the forefront of blog comment services in a short time, partly due to his aggressively pursuing relationships with partners. While some companies have targeted Disqus with competitive pot-shots, Daniel said that having others in the field helps to reassure him that it's a good market to pursue. If nobody else was interested in the space, he would undoubtedly be wondering just why.

Disqus is well-known to be funded by Fred Wilson with Union Square Ventures and Paul Graham with Y Combinator, among others, and while some VCs may try to demand immediate revenues or even profits from even the smallest of ventures, Disqus is not yet under such pressure. They've definitely had talks about how to monetize and start bringing in money, but if you thought they were about to start with advertising, you'd be wrong. Disqus will not always be a zero-revenue company, but Daniel says advertising's not in the plans.

For a service that's already got what I believe to the best solution with threaded conversations, a strong GUI and centralized activity, Disqus is continuing to work hard to maintain their lead. Andrew's comments point to near-term release of importing, exporting and trackbacks, and Daniel seems to have an extremely level perspective on what could be a challenging environment for anyone, let alone a 22 year-old entrepreneur. I believe we need a lot more people like Daniel focused on delivering a great customer experience with real benefits, who are less focused on the day to day fights between competitors than they are on getting the service perfected.

Labels: , , ,

Friday, June 13, 2008

Giving a Service Wings By Pushing Them from the Nest

For those of us blogging who like to break the news by announcing new services, and using our site as their platform to debut, it can be tempting to pull an "old world" journalism mentality and claim that topic as "our turf", resenting anybody else who tries to step in and steal the thunder by posting the news first, or even feeling betrayed if the entrepreneur takes the news somewhere else. But I've seen that after what I consider an incubation period, the fastest-growing services do best when I can step back and let them take their first steps away from the nest, as they engage with other bloggers, gaining them a new audience and greater exposure.

In this analogy, it can be nerve-wracking to see the little ones as they leave the nest. I worry the new caregivers might not see them in the same way I do. The new influencer might be cruel or may not recognize their talents. But to try and protect them by keeping them in the nest could stunt their growth.

As mentioned in yesterday's popular post, the first stage of being an early adopter can at times be indistinguishable from the service's PR or Marketing firm, as you try to make a product you like extremely visible. You've no doubt seen me do this, as I'll not just help by introducing a product, but keeping you posted on its updates, from Assetbar to ReadBurner, FriendFeedMachine, RSSmeme and Toluu.

But there comes a time when the right thing to do is let go, when the service has gained such momentum that I instead suggest the developer reach out to other sites to get a broader perspective and more exposure, so that their service is less tied in with me, and seen, instead as more of the broader landscape.

Don't get me wrong. I love exclusives, and part of my journalism background makes the little hairs on the back of my neck stand up when I know that someone who might be considered competition is writing about the same topic at the same time with the same deadline. But lately, for services that have gotten some traction, I've opted out of story opportunities and encouraged the developer to get some new voices talking instead.

A prime example of this was with Toluu yesterday. On Wednesday, Caleb Elston reached out to me with some great new service updates, including details on subscriptions within Toluu by feed, and story popularity, in part helped by AideRSS. I told Caleb that instead of waiting for me, to take his outreach to the next level, and it worked, without question. Yesterday ended up being a record-setting day for Toluu, after what Hutch Carpenter called a great example of social media marketing, by participating and reaching out to bloggers and following Toluu references on both FriendFeed and Twitter.

Similarly, RSSmeme announced options to find similar sharers of data to you, and integrated widgets on each page that show top tags and sharers for that blog or topic. See: Using RSSmeme To Find Similar Sharers: Louis Gray’s Example. Having just given RSSmeme a ton of credit last Saturday on being the authority on Google Reader sharing notes, I again waved the white flag, and told Benjamin to spread the word. He did, leveraging a custom room on FriendFeed for RSSmeme, to update followers, also adding RSSmeme as a user of the service, and today, leveraging the FriendFeed API to speed up the site.

You can see how other services have taken steps to leave the nest, as other sites, often much bigger than mine, take up the rallying cry:

ReadBurner:
The Inquisitr: ReadBurner Gets Digg Like Features

Shyftr:
Mashable: Shyftr Beats Google Reader with OPML Imports

LinkRiver:
SheGeeks: LinkRiver is My Personal Techmeme

Part of being a good partner to new services is knowing when to let go, and to see if the service has wings. A few weeks ago, I wrote to one pair of entrepreneurs, "Let me know if there's anything else I can do, but I do believe it's going to come down to you guys being more visible." With everything else that's going on, I can't possibly do it all myself. That's why, even though it can be bittersweet on occasion, the right thing to do is let them take a risk and let go. It gives others, like Corvida, the opportunity to do a social media roundup on service updates, and it's best for the community at large.

Labels: , , , , , ,

Thursday, June 12, 2008

The Five Stages Of Early Adopter Behavior

Early adopters serve an important role in the world of Web services and technology gadgetry. helping to act in a multi-pronged position that can blur the line between journalist, customer and partner.

The best early adopters not only help spread the word about a new product, but they can help argue its features, they are eager to offer feedback to its developers, and at times can be indistinguishable from the service's PR or Marketing team. But with time, if not coddled, this crowd can often turn against the very service they helped champion, as they move on to the next new thing, sometimes taking an army of followers with them.

This relationship between service and early adopter is a healthy one, assuming the Web service has, in the interim, grown to the point they no longer need the initial proponent's efforts, having expanded to a more mainstream audience, or achieved sustainable organic growth. But if this doesn't happen, it's a very short trip from promotion to abandonment indeed.

With not too much research, you can see evidence for five major stages of early adopter behavior, as I've summarized below.


1. Discovery, QA and Spreading the Word

The first weeks and months of a service can be very exciting. The early adopter often works with the developer behind the scenes to learn as much as they can about a product, often posting a new story that introduces the site. If there are any bugs with the product, they are easily glossed over as ones which will undoubtedly soon be fixed. If the site doesn't seem all that useful without a multitude of users, this too can be ignored, as the early adopter hopes everyone will see the service's full potential, and will use it the way they expect to.

In this phase, the early adopter has what can be construed as a personal interest in the success of the product, as he or she has gone out on a limb to associate the name with the third party brand. The adopter will not only be a frequent user of the service, but will track other posts or comments about it everywhere, and repeat the agreed upon talking points. Should they actually find a major issue with the product, they will e-mail or call the developers directly, rather than making the issues public.

At times, everything on the Web can be seen through the lenses of just how this new product will be affected, or how it could change everything else. All of a sudden, what may have been a hammer is proclaimed to be a Swiss Army Knife.

2. Promotion and Collaboration

As the service gains momentum, the early adopter befriends the first users of the product, who may have nothing in common except that they share interest in that product. At times, the product may be used only to discuss the product itself.

The early adopter, as new voices discover the service, will push follow-up posts, giving public suggestions to the company, in an extremely positive way, on how they believe the service should change and grow, showing themselves, in front of the world, to be an integral part of the product's development. Should the product incorporate any of these suggestions, whether due to the adopter's input or not, the early adopter will either take credit, or follow up and show how they were "right".

Now using the product a great deal, at the exclusion of others, the early adopter will openly mock those people who haven't jumped aboard yet, pointing them out as being stuck in the past, or married to clearly inferior products.

3. Mainstream Use and Engagement

Having grown tired of the part-time job of delivering free PR for the service, at this point the early adopter no longer feels the need to architect every story and every product through the lens of the service. Instead, having felt vindicated that the masses are now seeing the potential he always knew the product had, he or she remains engaged, trying to act as a "model citizen" for the product, engaging with newer users, but keeping in mind the higher visibility and trying to act as an example.

At this point, follow-on users have now picked up the ball in terms of promoting the product, announcing each of its aspects in the same breath-taking manner the early adopter once did for the service itself. At this point, the early adopter already knows his or her readers and peers know they like the product, and the need to constantly remind people they are using it is no longer necessary.

4. Sense of Entitlement, Nitpicking and Reduced Use

At this point, often in part due to favorable feedback from the service's authors, the early adopter feels a sense of entitlement, that the product absolutely must be architected in the way they say so, even if to move in that direction wouldn't serve the larger installed base. Now, instead of suggesting quick ways the service could update, the calls are more like ultimatums, and if not quickly seeing a response, the early adopter can get extremely frustrated, at times, seeing this annoyance bubble up to the same degree their first comments on the product reeked of praise.

Now disgruntled, the early adopter can be seen using the product less frequently, with less enthusiasm, and will even take consecutive days off, hoping the remaining audience notices the change.

5. Migration to Something New, Call to Move Followers

Having come full circle, from the exciting discovery stage, where the adopter considered themselves a team player, helping a threadbare company grow on the back of continuous praise and promotion, to a high-profile user role, the individual can come crashing down, lashing out at the product, the company's leadership or the product direction. The adopter often finds a tangential service that now draws their eye, and is seen as a replacement for the original product.

The adopter will, at this point, start heaping lavish praise upon the new product, in a quest to assert their dominance, and prove that they can, again, make a service successful, and to prove that all their belly-aching in the preceding months was valid. The adopter will use their blog and both the new and old service to call followers to migrate as a group, both helping the new shiny toy, and in turn, damaging the old one, out of spite and frustration.



On the Web, this process can be extremely fast. One month's golden boy can be next month's afterthought. One week's addiction can be next week's memory. For a service to succeed, it needs to attract those early adopters who can help propel a strong population, but it needs to do all it can to keep those adopters feeling like partners and mainstream users, before letting neglect fire up their egos so much that they leave you altogether. Making a successful Web service is more than writing the best code. It's also about relationships. And while the early adopter crowd is notoriously fickle, they're not going away all that soon.

Take a tally in your head of some of the services you use each day. If you're an early adopter, what stage are you in? If you're not an early adopter, but you know someone who is, what products do they make themselves part of? And do you see these stages progress? I know I do.

Labels: ,

Saturday, May 31, 2008

Dealing With Capacity Overload and "Laying Off" Features

If you take a step back and think about popular Web services, be they RSS feed readers, communications tools, social networks, link aggregators or lifestreams, their core deliverable is data. The way they are differentiating is through enabling that data to be accessed by more people, and manipulated in new ways. But as their popularity grows, with more users, more features, and richer media, be it photographs, music, or video, the data can spiral out of control, demanding l