Showing posts with label CN. Show all posts
Showing posts with label CN. Show all posts

April 06, 2013

Allen Stern, Web 2.0 Tech Blogging Pioneer, Passes Away

Tonight, I found out, as did many of us in the tightly knit tech blogging community, that Allen Stern, the founder of Centernetworks, and later CloudContacts and Let's Talk Fitness, had passed away. No matter the reason, it was far too soon - and no matter of Wikipedia style dry obit can capture the loss of one of the tech blogging scene's first, finest and most fun, personalities, who was truly larger than life.

The news broke about three hours ago, in a Facebook post from Allen's sister, saying Allen had passed earlier in the week. For those of us who know Allen well, this is a big surprise. Allen's health, once a major cause for concern a couple years ago, had dramatically improved, as he lost more than 125 pounds through greatly improved diet and exercise. While I've talked about my own push to lose all of thirty pounds, thanks to Fitbit, the idea of losing 125 pounds is mind boggling.

Allen after his health kick, looked fantastic. (via his Facebook)

Before Allen's health kick, he made a name for himself running Centernetworks. Archive.org has it starting all the way back in 1999, but when I first started posting regularly here, CenterNetworks was one of the Techmeme regulars, and Allen was seemingly on every story. On top of his New York-centric view of the Valley and all things tech, he had a very funny and dry sense of humor, punctuated by my favorite bits of him as "The Blogger King", along with pompous Burger King crown, laying down the rules of the tech Web.

Allen, amid all the self-centered hipsters that entered the blogging scene, was genuine and personal. In 2008, when my twins were born, we had a fun blog back and forth that peaked with the month-plus old Matthew jokingly being hired as an intern at CenterNetworks, and later losing his role for sleeping on the job. We pretended to sue, and Allen later sent a model A Train, from one of his other passions, New York transit, which became one of my kids' favorite toys. Allen also was one of my most frequent email contacts, and always took the time for a phone call.

After he immersed himself into CloudContacts, Allen later sold Centernetworks, and later focused more on getting his body into shape. As he told me frequently, he was sluggish and in horrible repair two years ago around Google I/O, which was the last time I saw him, in 2011. He fought hard and made himself look dramatically better, part of the life change that came as he also moved out of urban New York and to suburban Austin, Texas.

I'll miss Allen. I missed it when he stopped posting as regularly to CenterNetworks as he once did. But more, I'll miss the fun email threads and fun phone calls that always left me laughing and feeling better. Death sucks and tonight, I'm sad. Bye, Allen.

March 20, 2009

CloudContacts Teleports Your Business Cards to the Virtual World

Like many of you no doubt, over the last several years, I've amassed a solid collection of business cards, from both work and social engagements. I have business cards in boxes, in piles on my desk, on my dresser and table at home, and in virtually every zipper pocket of my laptop bag. I have business cards from Web companies that haven't launched yet, and I have business cards from companies that have already gone out of business since we shook hands and traded paper. And while I always thought someday I would sit down and input each one by hand into my address book, it never happened. That's why when I heard about CenterNetworks' Allen Stern's new venture, CloudContacts, I was intrigued. When we met up at SXSW last week, I took the plunge, and have to say that not only did the service do exactly as I expected, but i tees up some interesting possibilities through advanced features I hadn't considered.

The first step of starting with CloudContacts is the one of getting your cards into the service. You could physically hand Allen a box, like I did at the event. You could mail CloudContacts your cards. You could scan the cards and e-mail him the results. Or you could even, with a feature announced last month, take a picture of the card(s) with your phone and e-mail it in.

Once CloudContacts has your cards, the real work takes place, and the cards are entered into the system. I gave Allen my cards on Saturday and gained a login by Monday, so turn-around time is very quick. Upon logging in, I was presented with a page that showed the contacts listed by first and last name, company, address, and phone, just like you would expect from online address book services, including the one Apple features in MobileMe.


But CloudContacts' true value comes from mainly two areas. The first is the one you would expect, where you can download all your contacts (in CSV file, VCards or as Yahoo! and GMail contacts), and the second is that when you click on "view" next to any card, you not only see a picture of the scanned business card, but you also get as much data out of the Web as CloudContacts could find, from a picture in Google Maps showing their address, to searches on LinkedIn and Facebook for their accounts, and even their last few tweets, if the card was lucky enough to have a Twitter account listed. You could even play super-geek and scan a code to have your phone call the person, if dialing proves too difficult.


For me, the major test was downloading the 200+ cards I gave to CloudContacts, and then importing them into my Apple Address Book, which syncs up with my iPhone, Mail and most programs. It happened perfectly, recognizing potential duplicates I'd actually entered myself, and adding the rest. Now, all those business cards I was lugging around or running into can be sent to the big recycling bin in the sky.


The question is, now that the hard part is done, can Allen Stern and CloudContacts flip the data on its head and start to make a LinkedIn-like social network out of it? Will I in the future be able to see who else uploaded the same business card? It looks like the foundation is being laid for the service to become more than just a next generation address book. But even if it never does, it's already been a great benefit to me. You can find CloudContacts at http://www.cloudcontacts.com.

January 13, 2009

Some Things Are Worth Paying for Online and Others are Not

A month or so ago, following my review of the new Price Is Right application for the iPhone, the always conversational, if not controversial, Allen Stern of CenterNetworks asked "why people are so quickly willing to drop massive dollars on iphone apps" but will do whatever they can to avoid paying for content, including the use of ad blockers. As with offline purchases, everyone's rationale for purchasing can vary, but here's some of the thinking behind my own behavior:

Worth Buying: Something Tangible You Can Keep

The "Commerce" folder in my e-mail box is flooded with iTunes Store purchase receipts going back years, thanks to the Apple offering me thousands of songs I can purchase, films, television shows, and now applications for the iPhone. With hard drive capacities ever increasing, I have very little need to ever throw away a song, so purchasing it for keeps makes sense.

I also purchase software applications for my computer online, which when downloaded, are essentially there forever. Also, as downloadable software applications are typically the same content as retail boxes of software, I know they have equivalent value.

Not Worth Buying: Something You Don't Keep

Even if it would likely save me money over the long run, I won't pay for a subscription model of music. If I ever chose to stop paying, I would have no assets. So that doesn't make sense.

Not Worth Buying: Something Useless Tomorrow

Practically everything has a shelf life. Information and news ages faster than just about anything else out there. News that was breaking this morning is old news this evening and ancient by tomorrow. That's why I am no longer paying for Newsweek's print edition, or Sports Illustrated, Macworld, or even the Wall Street Journal online edition, as their content had already been discovered somewhere else closer to real time.

Worth Buying: Unique Insight and Direct Access

Thought it's unusual, some subscription models work, if online consumers believe they are getting more of the story, or get additional tips that free users are not getting. ESPN.com's Insider feature, though maligned by many, has been a must-renew each year, because much of their quality content is behind the paywall. Similarly, at times I have been a Wall Street Journal online subscriber, and previously a subscriber to TheStreet.com. The last two are particularly important because they deal with finance and many believe that the money they will make back off their content will more than outweigh the initial spend.

Not Worth Buying: Duplicate, Non-Unique Items

The "for pay" content successes are few and far between. Much of that is because it is getting easier and easier to publish content quickly these days, and if one source doesn't cover a story, another one will. In television, all the news networks and cable channels cover the big stories. In the blogosphere, most of the brand names echo each others' content, driving down the average quality, and practically making every single one of them replaceable. With very little unique content and access, none derive enough value for users to pay, except maybe out of pity.

Worth Buying: Time Wasters and Entertainment

It's a lot more fun to play cards or video games than it is to pay bills. And while office productivity applications might be among the most useful applications you have, the number of games you have on your PC or your mobile phone may outnumber these tools by a factor of 3-1 or more. For every Microsoft Office I have, I also have a handful of card games, board games or arcade games at the ready, each of which is probably in the $5 to $20 range to buy.

Not Worth Buying: Access to Social Communities

The very nature of social communities is that they rely on the people themselves to deliver the value, and on the Web, those communities are extremely mobile. As much fun as you may be having on Facebook, Twitter, LinkedIn, FriendFeed or other networks, you know you were probably spending the same amount of social capital somewhere else a few years ago, and you'll likely be spending it somewhere else in a few years. Given the entire community can move, you don't want to find out the last thing people will remember you by is your credit card number.

Worth Buying: Items With Offline World Equivalents

Lest I be seen as overlooking the entire world of e-commerce, yes, buying real-world goods and services online has value, so long as it correlates nicely with offline costs and deliverables. Online purchases of tickets, apparel, food, and services make sense. I'll pay for Quicken Online. I'll pay for Netflix videos. I'll pay for MLB.com broadcasts, and I'll buy physical items on eBay, Amazon and other merchants.

Not Worth Buying: Content

Content itself is not king as once was thought. With the advent of wire services and RSS, content created in one place can move to another in rapid speed. Syndicated content can build up a shell of a site and make it a destination. Bloggers can niche themselves and create original content, or they can be repeaters and post many times a day, putting quality in the wind. Building a Web site is very cheap right now, and creating content is very cheap as well. While consumers are suffering with a reduction in the availability of great content by those who practice their craft well, the amount of content available is overwhelming, and if one publication disappears, another can rise up almost instantly to take its place. Even the biggest brands we know today in content can be replaced.

For many content producers who have made this their craft, the realization can be very frustrating, as they know their efforts have value, but as consumers, we don't always recognize it. I may be perfectly okay in shelling out $8 to play the Price Is Right on my iPhone, or I'll pay $10 to download an album from iTunes, but ask for $1 an RSS feed, and I'll say no. Cognitively, that is broken. But that is where we are.

Any other thoughts? There's no way my list is complete. And Allen, I expect to hear from you on what I'm missing.

December 17, 2008

The Best Solution to Embargo Angst? Write Something Else.

As blogging approaches the traditional role of journalism, traditional elements of journalism, including public relations firms, embargoes, briefings, and bias are going to surface, as they have with traditional marketing, media and business for centuries. Today's flare-up, kicked off by one of the best discussion starters on the Web, TechCrunch's Michael Arrington, isn't the first time embargoes have been slammed, and it certainly won't be the last time. Back in August, I discussed why I believed the embargo process was both broken, but necessary, and Marshall Kirkpatrick of ReadWriteWeb followed on with a great take of his own.

I think the bigger issue is not that embargoes are being broken - which they are by blogs both big and small - but instead, that there are a large number of sites who act like they are the only game in town, and that they must cover every single story.

To those guys, please stop. Seriously.

In the tech blogging sphere, there is a serious echo chamber. While I look forward to banging through my Google Reader feeds every day, I can pretty much bank on seeing the same story, spun a different way, a good dozen or two dozen times by every single tech blog - even if it's clear that they are just reporting that someone else reported the news. If you see a story has been covered already and you have nothing to add - leave it alone.

Given the ease of news distribution, let's now write with the assumption that everybody reading your site is reading a few others as well. If you see a story broken by TechCrunch, or ReadWriteWeb or Mashable or VentureBeat or CenterNetworks, there's no need to pile on and become story number 18 on the topic. Let it go and write about something else - unless you have unique insight, unique quotes or access.

In my day job, I work with press releases and embargoes and reporters on a frequent basis. There is a need to be sure announcements go out when the products and partners are ready, or the customer is ready to take press calls. But Arrington is no doubt right that, as king of the hill, which TechCrunch is, some companies and PR teams are making coverage on the site practically mandatory, and near harassment of him and his team is no doubt occurring.

When trying to get coverage elsewhere, memorably one time in 2006 in Computerworld, I know I aggressively called the feature reporter every few hours until they finally picked up. After berating them for covering a competitor, and not our story, I got hung up on (no doubt deservedly so). I can only imagine being a TechCrunch reporter getting hit over and over by desperate firms, begging for coverage and honoring of their embargo.

A suggestion to those PR teams, please stop. Seriously.

Take your story somewhere else, to one of the many other tech blogs who write well, and will give your company or service its due. There are many new writers who have posts to file, and they want your story - and they will honor your requested embargo.

On this site, when I was running the whole thing myself, and now, with the great team of writers we have here, no embargo has ever been broken. On one occasion, I prematurely posted the Seesmic/Disqus integration news, having forgotten the day it was due, but I promptly deleted and reposted the next day. But one of the major reasons I haven't broken an embargo is because I strive, and ask my cohorts the same, to write things that are new. Cover new stories and new angles and be unique. If it has been covered somewhere else, let it go. We're not TechCrunch, and we're not trying to be.

TechCrunch doesn't have time for stories like Gawkk.com, which we covered last night. They probably aren't interested in stories like the one today on Resume Donkey, or Monday's announcement of Twit Or Fit. TechCrunch also doesn't have the leisure anymore of introducing great new blogs, as we do every month, or highlighting how to better use FriendFeed and Twitter, as we can. That's because they have taken on a new role, as a very real media company, and with their focus on Google, Microsoft, Facebook, Yahoo! and other big companies, there's room down at the bottom for us small fry to find the stories that are in the cracks.

It takes a different mentality to find new companies and new angles that nobody else has written before, that doesn't require a PR firm's input or embargo. And it takes strength from the PR firms to turn away from their top target and take the story somewhere else. While I don't think today's missive from Arrington will do just that, it might make some think different about the way they blog and distribute stories.

November 24, 2008

Introducing Exchange Rates for Blog Comments and Interactions

Editor's Note: Allen Stern and CenterNetworks are not affiliated with this post or the exchange rates table -- yet. The CN logo has been helpfully borrowed.


In May, Mathew Ingram, Fred Wilson and others said that for non-professional bloggers, comments were how they got paid. The interaction and discussion that takes place on blogs, between the author and the consumer, is what most write for - the conversation. But recent tools that let people comment elsewhere, or interact on the original content in other ways has some saying users' actions simply aren't enough. As much of the conversation moves off the original blog, or people are sharing items in Google Reader or hitting "like" in FriendFeed, they are showing interest, but not engaging, causing some to wish for a simpler time when those services didn't allow users to show passive approval.

One of the more outspoken voices on this topic has been Allen Stern of CenterNetworks, who wrote on this blog earlier this month:
"early adopters are screwing early adopter blogs - period. Clicking share on google reader is not like leaving a comment on the source. Clicking like on ff or retweeting on twitter is not the same as leaving a comment on the source. I will have more on this soon as I think that lazyness has slowly ruined what was something beautiful."
And while he and I don't always line up with our beliefs on the same spot in the blog evolution chart, there is no question that some activities do more to encourage the original author and their content than do others.

In that spirit, here is the first attempt at an exchange rate for interacting with blogs. As Allen has been a chief proponent of giving original authors their due, I believe the unit of metric is best labeled as a "CN", in honor of CenterNetworks. It's also no coincidence you could call these "C Notes" or "Comment Notes".

To start, I argue that a comment on the original author's blog post should be counted as "1 CN", to establish a baseline.


Actions that are worth more than 1 CN, depending on one's network size and influence, include:
  • Making a comment on the original blog, then blogging about that discussion on your own blog. (10 CN)
  • Writing a new blog post on the same topic and linking back to the original author as the source. (5 CN)
  • Submitting the blog post to StumbleUpon with a strong description and good tagging. (3 CN)
  • Submitting the blog post to Digg, Reddit, or Hacker News. (2 CN)

Actions that are worth between 1/2 CN and 1 CN, depending on one's network size and influence, include:
  • Retweeting the item on Twitter. (.8 CN)
  • Digging an already submitted story. (.6 CN)
  • Adding a vote on Reddit, Hacker News, or Mixx. (.5 CN)
Actions that are worth less than 1/2 CN, depending on one's network size or influence, include:
  • Posting the item natively to FriendFeed. (.4 CN)
  • Posting the item to Socialmedian or Strands. (.3 CN)
  • Posting the item to Facebook. (.25 CN)
  • Adding the item to your Tumblr blog. (.25 CN)
  • Sharing the item in Google Reader. (.25 CN)
  • Adding the item to your Delicious. (.2 CN)
  • Adding a comment on the original item on FriendFeed. (.2 CN)
  • Liking the item on FriendFeed. (.1 CN)
  • Adding a comment to a reshare of the item on FriendFeed. (.1 CN)
  • Liking a reshare of the item on FriendFeed. (.05 CN)
  • Adding a comment on the item in Shyftr. (.05 CN)
  • Adding a comment on the item in Facebook. (.05 CN)
These exchange rates show current market valuations, and are subject to change, based on the increase and decrease in popularity of associated networks and the sway of conventional opinion. Rates quoted are valid as of November 23rd, 2008, and were determined by a non-scientific measure of effort, influence and reach of the aforementioned external sites and activities.

As your activity gets further and further away from the original blog post, and the blog post becomes less of the story, but the third-party service gets to be more of the story or the destination, it delivers less perceived value to the original author, be it psychological, social, or in some cases, actually financial. While some of us early adopters are all too happy to expand a blog post's reach through our various social networks, and enjoy the new communities that are built there, it's not surprising that those who are seeing less activity on the original source of their stories are feeling something's amiss. I know that as I've gotten busier, I've taken less time to comment on the many blog posts out there, even as I'm making comments on the various social media sites, and sharing like I always have through Google Reader.

So if you want to show your appreciation to the author of a blog you've found particularly insightful of late, or who has opened your eyes to a new topic, don't just take the easy way out and hit "share" as the item flows through your RSS reader, or hit "like" on your social site, but take the extra time to rise up the CN chart and put some food on that blogger's table by making a comment and engaging. Allen and many others will be happy you did.

October 20, 2008

My Kids' Early Lives Are Already Entwined In Social Media

So far, I've held off on doing the silly thing, signing up my 4-month old twins, Matthew and Sarah, with user names to popular Web services, even though others thought I would. I haven't purchased them domain names, dedicated servers, or purchased them their own digital devices - yet.

This is because I expect by the time they're ready to use them that many of the brands will have changed, and because to have yet another login (or two) would be too tempting, and I'd find myself tweeting as an infant, and that would be completely silly. Also, who knows what kind of user names these kids will want once they've realized they have a choice? Surely not the fuddy-duddy version I'm bound to select.

In March, I said loudly, Our Unborn Kids Will Wear Your Web 2.0 Schwag. And while they're still small, and haven't grown into everything, they're doing their best. (Not that they wouldn't mind more logo clothes - e-mail me if you're interested.)

But, consider the following, all of which are true:All this has happened before the pair have learned to crawl, talk, read, or walk. But they're growing up in front of laptop screens, they've been pictured with the iPhone, and have attended Silicon Valley gatherings. Sarah met Loic Lemeur of Seesmic, and both met Drew Olanoff of Strands and MG Siegler of VentureBeat.


Matthew Goes LOLCat for Strands

Whether they realize it or not, as social media becomes more intertwined with every aspect of our lives, they too have become intertwined with social media.


Sarah Gets Chatty Last Thursday On YouTube

Today, Matthew and Sarah turn four months old, so they are effectively 1/3 years old. While I've gone light in terms of dousing the blog with their pictures, you can stay updated in a few places:

August 20, 2008

Why the Embargo Process Is Broken and Why We Still Need It

In the world of public relations, press management and blogging, an embargo sets a date and time by which a story can be written. Often, the embargo date and time coincides with a press release from the company, a Web site refresh, or the product's availability. Assuming all goes well, an embargo restricts all outlets from publishing a story until all is ready, and assuming multiple parties have been briefed, you can expect a waterfall of stories and press coverage to flow in a short period of time.


But, as you know, any time humans are involved, things can go awry, especially, as you see often in the blogosphere, you have a large number of media outlets that cover similar spaces, and a scarcity of topics. The resulting clamor to be heard amongst the noise, when so many different people are writing very similar stories, makes for an environment where the slightest bit of mistrust can turn into a simmering feud, or outright frustrating and finger-pointing, be it at a competitive blog, or the people behind the service being launched. Add in to the mix a rising number of inexperienced writers, prone to mistakes, with high levels of visibility, and this can happen with some regularity.

To start, why would a company ask for an embargo?
    1. To be sure a product would not be pre-announced before it was ready.
    2. To prepare and have enough time to brief all interested parties.
    3. To ensure no favoritism was shown to any media outlet.
Why would media/press/bloggers agree to an embargo?
    1. If they wouldn't agree, the company might not give them the story.
    2. Because an embargo often comes with news ahead of time, allowing time for writing.
    3. The service might have given them an interesting non-standard angle.
At an enterprise company, a media and analyst tour typically consists of a series of face to face meetings, plus conference calls, with an agreed upon date for a press release that coincides with the product's launch. Reporters often are looking for customer references and analyst references to validate the company's claims or add a wrinkle to the story.

For more bare-bones operations, including startups focused in the Web space, face to face meetings are less necessary. Sometimes, a series of e-mails, with potential for a phone call, is all that's needed. That's why you, on most blogs, rarely see quotes from a company's executives or customers, even if they had an extensive beta. Most bloggers, even if they have tested a product themselves, are echoing a press release or e-mail introduction from the service's founder. Again, a date is usually referenced in the e-mail to "go live".

Sounds good. Right? So why do these nicely laid plans fall apart?

On the company side:
    1. Sometimes an embargo is for "everybody except one or two publications", who are allowed to break it.
    2. Sometimes the Web site or company blog can go live before the embargo, in effect, scooping themselves.
    3. Sometimes a story isn't all that much of a secret, and things leak to the point there's no reason for an embargo.
On the media/blog side:
    1. Going first is seen as being "special", even if it's a matter of minutes.
    2. Being first can make the originating blog get more attention and linkage, or prominence on sites like Techmeme.
    3. Some blog management systems aren't fool-proof, enabling stories to go "before their time".

Clearly, you have some juxtaposed issues. The company launching an announcement would benefit from being covered by the most publications as possible, seen by the highest number of people. This is augmented by a need to be seen by publications with a high level of prestige. (Think Wall Street Journal, News.com, eWeek, TechCrunch, etc.) But there's something of a magnetic pull on press or blogs to go early, whether that's at midnight on the day of launch, or by posting five minutes before an embargo is lifted, and simply moving the timestamp, as has been known to happen. Blogs and press publications get a lot of visibility through gaining exclusives, and even if the same announcement has been sent to a wide audience, to hit the "post" button a little early, getting the word out first makes you appear more "in the know".

Whether intentional or not, blogs are rewarded for breaking embargoes, even if it hurts the launching service. And there's rarely any level of repercussion, as competing blogs in the know of the embargo are not naming names.

Of late, I've seen a healthy dose of complaining by some bloggers that other blogs have willingly or unwillingly violated an agreed-upon embargo. Yet, interestingly, it's a rare person who will name the offending party, even after their activity has clearly irked them.

See for instance:
    Svetlana Gladkova of Profy:
    "Very-very angry. Is it impossible to run a blog without breaking embargoes these days???"
    08:23 PM August 18, 2008

    Allen Stern of CenterNetworks:

    "wtf is up with the broken embargoes this past week - 3 today, 5 in the last week - im feeling like busting out a video tonight"
    06:32 PM August 18, 2008

    Marshall Kirkpatrick of ReadWriteWeb:
    "PR just called to say that mainstream media guy broke embargo, lol. you can't trust those mainstream media types with embargoes!"
    02:18 PM August 15, 2008
Notice how even though they claim frustration and anger, nobody says who the offending parties are...

Embargoes serve a real purpose for the company making the announcement. They are there to build time to polish the product, to enable true beta testing, to set up press activity with multiple targets, and to get one's message distributed. Embargoes serve a purpose for the blogging community, for those who choose to follow them, to help guide an editorial calendar, or to be sure you're also talking about a story on the day of its debut. And while some people might wish they disappear, it's not going to happen, so long as companies look to synchronize their internal and external activity.

As we see a rise in the total number of bloggers writing on the same topics, the issue of some sites trying to get out a step ahead of others isn't going to go away. Those that play by the rules and follow the agreed-upon embargoes, are on occasion, going to get burned. But what doesn't help the situation is that nobody is making a list and checking it twice. Why complain if nobody is going to name names? If there are one, two, three or ten blogs that regularly break an embargo, and it's clear there is a pattern, it should be visible, and these sites should be avoided by companies like the plague.

I believe in and honor embargoes. I also love exclusives, and think that there is more than one way to launch a product. But this practice is tried and true, so long as we have more transparency. What disincentive is there for bloggers who break embargoes if nobody steps up?

August 07, 2008

Exposed: Blogging's Secret Next Generation

By Jesse Stay of Stay N' Alive (Identi.ca/FriendFeed)

I'm afraid to admit it, and feel ashamed for the Stay family name, but I can't take all the credit for my last article on Facebook removing features and the confusing nature of the new design. Yes, it's a shame, but I'm going to have to tell you the real story behind us guest bloggers on LouisGray.com. You see, it's not really us blogging most of the time. Louis Gray has an entire army of baby guest bloggers that post for him regularly. Louis recruits us, but in reality he really is looking for the amazing talents of our babies.

I'm going to come clean on this one though. I'm going to have to blame most of my last article about Facebook on my 4 month old son, Jesse III, who has recently been recruited as a new guest blogger for LouisGray.com. It appears we got the II's (from my name) and III's (from his name) mixed up as we were entering our logins that night and he very easily and mistakenly posted as myself that night.

I caught the mistake the next day and was able to quickly correct it, showing that Facebook's new design was definitely not easy enough for a baby to use. I mean, if he couldn't figure out the new Facebook redesign, how could I? I have since docked his allowance and limited him to just one binky per day for the incident, and it will never happen again. Coincidently, it was also him who posted on my blog awhile back, under his own name, saying he was on hiatus from Twitter. He didn't tell me beforehand and I was stuck eating his words as people thought it was actually me leaving Twitter. I mean, why couldn't Twitter allow suffix meta tags so we didn't have to share the same username? I have since found his counsel quite comforting though, as Identi.ca and FriendFeed seem to be working out pretty well for me so far. He certainly knows how to cause a stir though!

Louis Gray, in his open, family-oriented format, is no stranger to baby-blogging. After all, it was his baby Matthew that recently was the center (no pun intended) of the Gray Family/CenterNetworks controversy, and after much heartache and emotions he is now back blogging so I hear for his Dad when his Dad is too busy with work. You often wonder how Louis does it, following everything on FriendFeed, posting sometimes multiple times a day to this blog, and now on SocialMedian. Well, the answer is, so I hear, he doesn't - this is a family establishment here on LouisGray.com and Matthew is as much a part of the family as the rest of our babies are.

Cyndy Aleo-Carreira is also a welcomed guest blogger on LouisGray.com. What you may not know is that her 2-year old daughter, Pete, has been moonlighting on the side of her job with CenterNetworks.com to occasionally help out her mom on LouisGray.com. Yes, while Matthew has been criticized by Allen Stern for slacking on the job, sweet little Pete has also been spending a little time over here helping out in her spare time. We certainly appreciate the help! In fact, Cyndy's first post to LouisGray.com was actually a Seesmic video from her daughter, Pete. Cyndy does such great posts, it's hard to tell which ones her daughter may actually be helping her out on and which ones are actually Cyndy. Thank goodness they don't have the same name!

Next time you read a LouisGray.com guest post, think of the babies behind those posts. We may put our names in front of them, but in reality, our babies are the true reason behind Louis Gray's success. Louis wasn't joking when he said he is an "early adopter".

Jesse III's next post will be on Facebook privacy, for babies.

August 02, 2008

I Got a Mac OS X Trojan and Infected CenterNetworks. Oops.

As a sometimes smug Mac user for the overwhelming majority of my computer-using life, virus warnings, anti-virus software and security updates were always something "those other guys" had to deal with. Using my Mac, I would even have colleagues send me attachments from their Windows machines which they thought were viruses, so I could open them up in a text editor and see what mischief they had intended to cause. But today, I realized my laptop had somehow acquired a rare trojan that does hit Mac OS X, and the results of the bugger were actually more harmful for Allen Stern of CenterNetworks than they were for me. Oops.

This morning, Allen Stern presented a new video following a press conference he held that discussed his take on the "firing" of my son Matthew, who had secured a short-lived position in CenterNetworks' San Francisco bureau. As usual, Stern's tongue-in-cheek humor and deadpan delivery were very good. The conclusion reached by his video was that Matthew would be compensated out of court with the delivery of an "I love New York" t-shirt, and I quickly commented on his site that we agreed to the settlement.

But amusingly, having posted my comment, I noticed that virtually all of the ads on Allen's site were for pills that solved erectile dysfunction, and all the banners were rotating images of Viagra, Cialis and Levitra, which made no sense on Allen's tech blog, and had absolutely zero to do with his story on my kid. So, I made screenshots, and jokingly sent a note to FriendFeed, saying, “I Just Hope the Money from these Ads Keeps CN "Up".


CenterNetworks' Ads Were All In Pill Form for Me

Allen, looking at the pictures and then back at his site, thought I was joking. But I wasn't. When he realized I was serious, this set off a flurry of calls by him to his advertising partners, swapping out of ads, and testing both on his side and mine, as we tried to figure out... was it him, or was it me?

Turns out it was all me, and separated by 3,000 miles, I was causing Allen's blood pressure to rise for no good reason. It turned out that at some point, recently, some file I downloaded hijacked my DNS settings on my MacBook Pro, and selectively overlaid his banner ads from Tribal Fusion, on both CenterNetworks and HTMLCenter, with these stupid Viagra ads. Meanwhile, my wife's laptop was fine, showing normal ads, while I was viewing the world through an odd filter.

So, I did some searching on the Web and found I had likely run into one of the few pieces of known Mac OS X malware out there, a Trojan, which disguised itself as a clean file. So, I decided to finally get some real anti-virus software to take a look at it, and found a solution from Intego called Virus Barrier, which looked a lot more Mac-friendly than dreck the Symantec guys offer. Sure enough, after paying to buy their software, installing, and rebooting, the offending file was found, masquerading as a QuickTime extension. The Intego software let me delete it, and all of a sudden, all was well. Allen's site now shows normal ads, and he doesn't carry the mark of a dope dealer.


Intego Virus Barrier Going Through My Files



Aha! A trojan has been located and destroyed!

Of course, this now raises the question... how did I get this on my machine? Some of the stories I read said the trojan could have been hiding in the form of a fake card game application, and others, as a tool that lets you watch adult videos. So... neither one of those makes sense. But despite that mystery, the good news is that I think it's all resolved. I have a product that will protect my Mac in the future if anything like this happens again, and I still know Allen Stern is on the up and up - a great blogger with a good sense of humor and values as well. It's just disappointing my stupid error somewhere dragged him through the mud through my "learning process".

July 30, 2008

Matthew's Story: From CenterNetworks' Future to Fired In A Month

Finding a writing position at a brand-name blog is hard to do, especially without having a significant resume, not to mention any references. So when Allen Stern of CenterNetworks offered my newborn son, Matthew, a position on his excellent blog, we of course struck at the deal. But in just a month, what at first seemed like a dream come true turned out to be a sordid tale of broken promises, unsafe working conditions and tears. A week after Stern publicly announced Matthew's firing, as a family, we've decided to tell our side of the story.

The fierce competition between East Coast and West Coast blogs these days is rivaling the old time feuds between East Coast and West Coast rappers. Based in New York, Stern has long been seeking the opportunity to open a Silicon Valley bureau, so this spring, when he learned we were expecting twins, he struck early, asking to sign up "whichever of the two kids was bigger". I naively accepted, not knowing that his request was due to the incredible stress that blogging and filing stories can be for a newborn.


Matthew Signed On to CenterNetworks In Days

Matthew and Sarah arrived on June 20th, he weighing a robust 5 pounds, and she, trailing at 4 pounds, 3 ounces. That made Matthew the candidate of record. The next four days were a whirlwind of deal-making, contracts being faxed from coast to coast, with little being given up on either side. Finally, the agreement completed, Matthew announced his signing, and was photographed with the world-famous CN sticker. The next day, Stern announced it to the world, and while he said "Of all the people I've hired over the years, this negotiation was the toughest," his listed demands were later proven to be a slap in the face.


Stern's Initial Set of Promises Included a New iPhone


But Stern Later Went Back On His Word


Over the next two weeks, Matthew made significant headway with CN, reaching out to Bay Area startups, reviewing alpha versions of Mac software and Web services, and even, somehow, transcribing quarterly conference calls. But while Stern publicly lauded his efforts in an update, the long hours, fatigue and strain were already becoming quite clear. As you can see from the follow-on post, Stern had openly reneged on the promised iPhone 3G, saying Matthew would get it "under no circumstances", despite it being promised in the initial agreement. Similarly, the promised crib with LCD panel and Wii Fit never materialized, which Stern attributed to "inventory shortages". Making matters worse, Stern would frequently call Matthew's home number at the start of East Coast business hours to talk strategy, despite it being only 5 a.m. Pacific.

The long hours and stress saw Matthew often falling asleep in front of his keyboard after filing a news story. He soon began to complain that he was unable to relax and casually visit his favorite sites, fearing an irate Stern would notice the gap in submissions and send yet another series of e-mails with even more assignments. And with every "like" or comment he placed on FriendFeed, Stern would just lose it - saying he was slacking off, or even worse, claiming he was manipulating activity on the site through creating hundreds of fake accounts. But it wasn't true, and try as Matthew would to explain he was just trying to catch up on the world outside of CenterNetworks, Stern wouldn't listen, ranting about how Mashable had scooped him on some new Facebook widget, or how ReadWriteWeb had gotten an exclusive look into a new AIR application that sent updates to Flickr and Twitter simultaneously, on Matthew's watch. The once promising job with significant career potential had spiraled into despair of inter-office politics and accusations that left Matthew depressed and unwilling to spend time with his sister or peers.


Matthew's Long Hours At CN Took Their Toll

It all came crashing down early last week, on July 21st. The first sign was when Matthew's CenterNetworks e-mail stopped working, and the daily shipment of Barnum and Bailey animal crackers didn't arrive. Then, two of the stories Matthew had filed were printed under Stern's byline, without his being mentioned as a contributing reporter. But Stern wouldn't take phone calls and Matthew was left to fend for himself. The next day, we realized what had happened. Stern, in a public missive, fired Matthew, without contacting him or myself, and continuing his rant about how Matthew was slacking off and creating FriendFeed accounts, accusations later proven untrue by FriendFeed interns Dan Hsaio and Ross Miller, who looked into the the service's logs following the allegations.


Stern's Hallucinations Fueled the Firing

Over the last eight days, as a family we've had to do a lot of soul-searching. Matthew, for one, swears he's had it with the blogging business, though it's not clear what line of profession he intends to take next. And if that weren't enough, on Monday, the long-promised Barney poster finally arrived, a stark reminder of one of the many unfulfilled promises by Stern and his crew. What should have been a case of spotting talent early, and helping to guide a young prodigy through the ranks instead was one that smacked of servitude, double-speaking and unhappiness. While we know we have a legal case against Stern and CenterNetworks proper over the unfulfilled iPhone, lack of proper advance notice of contract termination, and unfair child labor practices, we're going to swallow our pride and move on as a family. It's been hard, but we felt the right thing was to leave with our heads held high, without dragging this out through the morass that is the American judicial system.

So Pete "Peanut" Carreira, Stern may be whispering sweet nothings to you now and calling you a serious Seesmic star, but watch your back and protect yourself before what happened to Matthew happens to you as well.