Recently in Blogging World Category

Why I'm Still on Movable Type

After leaving Blogger years and years ago, I tried many different blogging engines (even developing my own, so to speak). None of them were as safe as my old way of just FTPing HTML files up to my host. Movable Type was the closest since it generated HTML files—it was like a hosted version of Blogger.

The downside was (and still is) that it runs on Perl. I'm not a PHP developer by any stretch, but I can fend for myself in WordPress when I have a task in mind. Perl, though, is just inscrutable to me; I don't have time to learn it and what little I have read doesn't make sense.

So why stick with it, especially in light of the recent malware attack? I briefly toyed with Textpattern last night but the thought of redoing my blog, site, and essays in yet another CMS left me stone cold. I've been down this road before and I just don't have time for it any more.

I've got so many other better things than to endlessly tweak my Web site. Perhaps I've matured in that regard. Or maybe part of maturity and wisdom is a jaded fatigue with youth's flitting.

Malware Done Got Me!

I apologize to anyone who has visited my blog in the last five days. I was running old Movable Type and someone exploited it. I got added to Google's malware warning service, unfortunately, so you might see some warnings until the request for review is complete.

It looks like it's time to figure out how to lock down Movable Type so that this doesn't happen again—it's such a pain to upgrade that there's always going to be some lag time between security release and updating.

No Comments

In moving my blog from Quick Blogcast to MovableType, I had a chance to revisit my decision to enable comments. Comments are always a mixed bag: the price of good discussion is eliminating comment spam—the blog's version of "broken windows." We've had decent success at it over at The New Clarion, but it took a long time to tweak the blacklist to get where it is today.

In the meantime, I had also started using Twitter quite aggressively. That is, essentially, a broadcast medium: you say things and people listen to them. There is some interaction but the key difference is that it's not exactly public.

That's the part about comments that I don't like. If you want to discuss some of my work, send me an email. If you want everyone to see your thoughts about what I've said, get your own forum. I don't care to host the opinions of those that disagree with me.

I have no regrets about turning off comments—I even did it over at Found on the Web. I spend zero time doing moderation and the extra work to send an email (while also not getting to vent in public) has severely limited the vitriol and bile.

WebException and the HttpWebResponse

The following code is used to make a request and get the results:

HttpWebRequest req = (HttpWebRequest)WebRequest.Create("http://bbrown.info/");
HttpWebResponse resp = (HttpWebResponse)req.GetResponse();
StreamReader reader = new StreamReader(resp.GetResponseStream());
string contents = reader.ReadToEnd();
resp.Close();

contents will contain the HTML of this blog if the server gives a 200 OK response. Anything else will throw a WebException. You can wrap the snippet above in a try-catch to handle a non-200, but the exception is thrown in the GetResponse call so you get nothing from the actual response. 404? May as well be a 500.

Today I discovered that the WebException itself has two properties: Response and Status. This Response is the same as the resp above so you can extract out the server response in the catch.

This whole behavior of HttpWebRequest is counterintuitive in the sense that a non-200 is not an exceptional circumstance; I would have expected the response to be accessible and the status code to be populated.

Feed and Social Distribution Session

Talk with Jerry Cain, Ari Steinberg (Manager of News Feed Team), and Tom Whitnah.

  • Use the right channel to deliver the right message. Overview of the old ways of communication with users. Requests: when one user wants another user to take a specific action. Notifications: user-to-user to tell a user an action has been taken towards her, app-to-user to tell a user about something important to her from the application. Feed story: when a user wants to share actions they've taken.
  • Feed is the center of communication on Facebook. Old: single stream, not interactive, only 25 slots. New: top stories as highlights, multiple streams of news, more room for application stories to appear, commenting on stories.
  • feed.publishTemplatizedAction: disaster, user-specific token sets made aggregation very difficult.
  • New methods: feed.registerTemplateBundle and feed.publishUserAction
  • Allow template bundles to include several templates per story size, ranging from user-specific to more general. You can define different templates within a bundle to handle 1, 2, and many aggregated stories.
  • Before you launch your application, think about the sort of templates you're going to be using. Calling the API method only allows for one-line stories. Feed forms: FB.Integration.showFeedDialog()
  • Great communications = happy users. Respect users' attention and their friends' attention.
  • Higher acceptance, lower ignore = more requests allocated.
  • Notifications: user-to-user, can be sent to any non-friends who are also users of the app; app-to-user, allocation is approximately seven per week per user.
  • More read, fewer hidden / spam = more notifications allocated.

Q&A

  • Allow access to News Feed? Nope.
  • Handle instead of a bundle ID? Not yet.
  • Facebook applications versus Facebook Connect? No differentiation.
  • (me) Disclose allocations per user instead of aggregate? Can put it on the short-term roadmap, but wary of disclosing who is a tattletale.
  • Statistics data available via an API call? Someone was working on that but he didn't know the status of that work.
  • Set privacy in News Feeds? Not at this point but hopefully someday.
  • Timeline for new statistics to appear? In the next week or so.
  • Give visibility into an app's spamminess? Talked about it with the Reviews application but have found some spamminess within the Reviews application itself.
  • What kind of history for allocation reductions? Spamminess metrics last about a month.
  • Expand News Feed on friends to see more of a story? Haven't really thought it.
  • In stories themselves, possible to see how many times one was read in News Feed? Would like to, but not a high priority.
  • Add or view comments, available through API? Probably through fb:comments, not allow to add comments programmatically due to spam concerns.

Talk by Ruchi Sanghvi and Josh Elman. Here are my rough notes on the presentation:

  • The never-ending profile was the motivation behind the redesign.
  • Emphasizing feeds: increases engagement and encourage content creation
  • Simpler, cleaner profiles: easier profile navigation, clearer identity, more control
  • More control over profile: users decide about tabs, when to publish, and look of stories
  • "It all starts with the Wall": feed, publisher, profile boxes
  • Stories: one-line, short, or full (up to 500x700). Done with feed forms, using FBML or Javascript.
  • Publisher: different versions for user and friends,
  • Info tab: deep integration with structured information, should represent information about what the user's done. Info stuff is enabled through canvas page button using FBML or Javascript.
  • Tabs: provides the richest expression, hybrid of a profile box and canvas page (solely FBML, no advertising), no caching, 760 pixels wide, no autoplay, fb:visible-to-owner
  • Profile boxes: profile_main -> narrow, on Wall, wide and narrow appear on Boxes tab, Bookmarks will be migrated, must manually add a bookmark otherwise.
  • New permissions/lack of adding: reduces friction. First access provides user ID, friends, pic and names, publish feed stories, send requests. Add require_login to links to trigger permissions solicitation.

Q&A:

  • How do users first get into the app if they're not adding?: About page much more static.
  • Should apps offer all integration points and let users decide or pick some?: Both, but mostly the latter.
  • Is user info going to be available to all? Still limited to privacy settings.
  • What can the Publisher do?: Rehashed already shown options
  • Smiley app? Uses shared preferences, which has been available for 9 months
  • Can you detect whether a user is in new profile? Yes, part of API.
  • Widened Wall, is it final? Yes.
  • (from me) Extended permissions, is the Wiki list definitive? Yes.
  • Engagement metrics, what are they? Bunch of them. User can reorder boxes.
  • What are these info sections? Not a mini-feed, opposite of one. More for static information. Button on canvas page shows example, the user allows it, adds it to profile, and edits inline.
  • What new stats will be available, users who have added tabs? Yes.
  • Logged in user for tabs is viewer or user? Viewer. Tabs focus should be on the user.

Benjamin Ling Presentation

Benjamin Ling, Facebook's Director of Platform Program Management, gave a talk about the state of the platform. Here are my raw notes while listening:

  • Ecosystem isn't just devs and users. It's also ad networks, app dev companies, and academics
  • Guiding principles: meaningful, trustworthy, well-designed
  • Meaningful apps are: social (apps make the best use of the social graph. Example Lil' Green Patch), useful (solve real user problems. Example Carpool), expressive (helps users share about themselves. Example Graffiti), engaging (sustain user interest. Example Who Has the Biggest Brain?)
  • Trustworthy apps are: secure (protect user data and honor privacy), respectful (value user attention and time), transparent (clearly explain features)
  • Well-designed apps are: clean (intuitive and easy to use. Example Local Picks from tripadvisor), fast (allow users to engage more), robust (stable and reliable)
  • Waiting for the hammer to drop about the consequences of these principles…
  • So what they're going to do: 1) partner more closely with developers (garages, forum, hiring community manager—no mention of Wiki, damn); 2) keep ecosystem safe for users, fair for developers; help you create more, better apps.
  • Announcements: a) new and improved developer site; b) fbFund recipients; c) new fbFund ($2 million over next two months -> 25 semi-finalists get $25K -> users select 5 finalists, who get $250K); d) recognize apps that embody our principles (Facebook Verification—applications accepted starting September 1st, Facebook Great Apps program—more integrated experience, more content, early access—iLike and Causes); e) kill apps that violate policies; f) Facebook Connect for iPhone; g) supporting and contributing to the Open Web Fondation
  • Beta of Facebook Connect in summer, open to all users in fall

Zuckerberg Keynote

Here are my notes on the Zuckerberg keynote.

  • Start: boring.
  • Important to have a purpose behind the mission of the movement. *snore*
  • He calls it a "vacation" but he's describing a "vision quest."
  • An hour and a half of this. Uh oh.
  • "Mission: Give people the power to share and make the world more open and connected"
  • 90 million people are on Facebook as of July 23rd
  • 32% US, 68% international
  • Opening up the translation tools to application developers!!
  • 400,000 developers
  • Billion dollar ecosystem surrounding Facebook, if VC equaled real money
  • "Virtuous cycle of sharing" around feeds
  • iLike primarily spread and shared through feeds
  • Lessons learned from the last year: a) listen to developers more; b) build the right tools; c) need to reward good citizens and punish the bad behavers; d) simplicity and scale are important for sharing
  • Goals of next evolution: a) give people more powerful tools to share; b) Reward applications that help people share; c) Make things simpler
  • Feed sharing is contingent on enabling sharing
  • The new sharing paradigm will enable apps to allow friends to post stories to friends feeds
  • Showed the Bill O'Reilly Flips Out video
  • Demoed the new profile—without a hitch.
  • He thinks decentralization is the future. It sounds like using the Facebook API as a glue, which sounds like even less monetizable to my ears.
  • Facebook Connect is the product behind that vision
  • Goals of Connect: a) build the same kinds of apps across the Web; b) share information across the Web; c) Control your information across the Web
  • Facebook Connect demo time: Digg's up first
  • Digg's going to use Facebook as OpenId, essentially—an authentication source
  • Six Apart's up: MT plugin to integrate FB with comments, also auth source, publish it onto your feed using Publisher.
  • Citysearch demo: see friends' reviews, publish reviews to profile
  • Profile launched Monday, switchover over a period of time
  • Facebook Connect API keys available today, beta soon

Armchair Architects

In case you haven't heard, Twitter's been having some alarming downtime due to scaling issues. It's become quite popular and continues to grow significantly in both traffic and users every month. As more and more people come to rely on its unique service, these outages have grown increasingly frustrating and that has lead to a minor cottage industry in the blogosphere: complaining about Twitter and ponying up solutions to help them out of this situation.

So here's what they need to do: shut up and realize that, by and large, they've got no idea what problems the Twitter team is having and no credibility in offering advice. Oh, you thought I was going to join in the chorus. While I have some experience with scaling in working in online banking and then a popular hosted blogging engine, I won't pretend to have any special insight into the problem. Unfortunately, many of my fellow bloggers don't share my restraint.

Just to give you an idea of the scope of the problem, Dare Obasanjo's entry details some of the complications that become obvious after more than a superficial rumination. Some might say that attacking this is easy, but they're dead wrong. What's even worse, the application that the Twitter developers originally built wasn't what it has become.

Second guessing and judging based on insufficient (or absolutely no) evidence is practically the coin of the blogosphere. Twitter needs to fix their problems, but I guarantee that their team cares more about doing so than you ever will.

[UPDATE (5/30/2008): More details.]

Talking 'Bout My Integration

I deployed my most recent project at work today. It's a Facebook application that allows Quick Blogcast customers to link their accounts to their Facebook profiles.

I know that bringing a blog into your Facebook profile is nothing new. There are many such applications out there right now that can do that. But I think this Quick Blogcast version is unique in that you can make it so that your friends and visitors never leave Facebook, even to comment! What's more, we leverage nearly all of the Facebook integration points. This allows the Quick Blogcast customer to publicize his or her blog to the fullest extent while still respecting the conventions and norms of the Facebook world. While that may not sound like much, it's been quite a learning experience for me.

For one thing, I had to master the Facebook API. Luckily, I only had to learn it secondhand because I had an excellent framework called Facebook.NET to lean on. After a month or so of experience, I even felt conversant enough to help others and supply patches. In so doing, I apparently really helped the developer of Thugz Passion, a game which I've grown to enjoy.

It was also a chance to get to know memcached better. I used the terrific Enyim.com Memcached framework to interact with a Win32 port of the service. I wish I knew enough C++ to move that project to the current version of the Linux original. I futilely check the danga email archives to see whether anyone's gotten impatient with progress and just did it on their own.

I was (and am) very impressed by memcached, which is an excellent (and free) distributed caching system. ASP.NET is top-notch at scaling but its caching mechanisms (namely, the object bags like Cache, Application, and Session) can easily become bottlenecks after enough usage is thrown at them. I think memcached offers a way out—it's certainly worked wonders in the Linux world.

I affectionately call this integration app Quick FaceBlogBookCast. It cracks me up every time; it's easily the most cumbersome portmanteau I've come across. (I can't believe I forgot the other Facebook app I released today: Domain Center for Facebook! It's a way to spontaneously generate domain name suggestions from the information contained on your Facebook profile. The algorithms right now are pretty coarse, but I plan to refine them each and every release until they're uncannily right some day.)

[The views expressed on this website/weblog are mine alone and do not necessarily reflect the views of Go Daddy Software, Inc.]

My Contribution

I've finally contributed something original to the Internet. I've chronicled many interesting things over at Found on the Web and I always felt like I needed to make something that others would use, get a kick out of, and then blog themselves. At last I've done it!

I call it the Meme Obfuscation Machine, which I just now noticed can be shortened to MOM—which I will not do. I had a spare domain that I've been paying for since 2003 (bridgeforsale.com) so I decided to donate it to the cause.

I created it Friday, February 29th. I've been intrigued by the phenomenon known as the Rick Roll for a couple of weeks now but on Friday it struck me that at some point it's just too obvious that you're being Rick Rolled. I remembered the serpentine redirects they used to use in the Slashdot community to land people at Goatse and suddenly it all just clicked.

It took me an hour to get all the necessary mod_rewrite rules down pat and then another hour to write up the Web site and hand-rolled feeds. The basic idea is that you craft a URL to suit your mark. For example, if your friend is a woodworking enthusiast (and who isn't), send him a link to www.bridgeforsale.com/articles/stunning-cabinet-plans-for-free.php. He'll gleefully click it and find himself on the business end of a Rick Astley.

I decided to make Rick Roll the default behavior for now so that any extension not already mapped (.aspx for Goatse, .jsp for Just Google It) would go to the campy video. But if you want the link to work forever, use ".php" or leave off the extension since those will be future proofed. Future meme additions will take up undefined extensions.

I hope this serves you well. Either way, I had a blast making it.

Poof Goes the Ads

When they finish the process of better and better targeted advertising, that's when the whole idea of advertising will go poof, will disappear. If it's perfectly targeted, it isn't advertising, it's information. Information is welcome, advertising is offensive. Who wants to pay to create information that's discarded? Who wants to pay to be a nuisance? Wouldn't it be better to pay to get the information to the people who want it? Are you afraid no one wants your information? Then maybe you'd better do some research and make a product that people actually want to know about. Dave Winer

After reading that quote from Dare Obasanjo's recent blog entry, I was floored by its pregnancy. The best advertising—like the best sales tactics—is invisible: it is about matching someone's needs perfectly. You're no longer selling to them, you're helping them and they can't buy your product fast enough. What has the progression of advertising been but a long, slow march towards better and better targeting?

I think the end of advertising, this withering away of the message, occurs when the consumer tells the advertiser exactly what advertisement he or she wants to hear. At that point, it really is just information. For me, an excellent example was the fad of the late 90s: the personal agent. Back then, the vision was that people would create "intelligent" agents to go out and do their bidding. The consumer would say "tell me about flights with window seats going from Phoenix to LA leaving December 3rd around 4ish" and the agent would come back with details and ticket information. In reality, that's the pinnacle of marketing—if the airline conceived the agent. Otherwise, it's really more like a search engine or travel agent.

Like Dare, I think this is the future. The agent was an idea ahead of its time; the breathless contemporaneous accounts read more like science fiction when compared with the available technology. Technology has caught up, though, and this user-generated marketing is going to be big.

Scalping Ain't Easy

John Gruber recently wrote:

Peter Kafka, at Silicon Alley Insider, claims the "obvious solution" to Hannah Montana ticket scalping—wherein $67 tickets are being re-sold for upwards of $250—is to raise the initial selling prices of the tickets, so that the money die-hard fans are willing to pay goes to the artist and concert promoter, rather than to the scalper, and then to reduce the prices after the initial high-priced demand passes.

Good advice, I say. And, of course, it's exactly what Apple did with the iPhone. Except Silicon Alley Insider didn't see it that way with the iPhone, writing "To us, this move suggests the phone is not selling as well as Apple had hoped," and "[The real issue] is Apple's obvious misjudgment of the market for a flagship product."

The problem is that concert promoters and the venues they book at aren't terribly interested in maximizing their revenue from ticket sales. Their primary concern is filling up the venues. They charge a premium for location and a premium for certain acts, but they don't exactly go after the scalper market because that market actually makes the process more efficient.

If the venue were to charge scalper-level pricing, scalpers wouldn't buy the tickets in order to re-sell them. The people who buy the scalper's inflated ticket prices may or may not pay the same amount to the venue and the concert promoters have no idea how much people would be willing to pay or even what the size of the market might be for these tickets. So they price the original tickets at a level that works for them.

Scalpers then speculatively buy those tickets in the hopes that they can make some profit through arbitrage. If they can't move the tickets, then they're out the money. So they only buy what they think they can sell. The concert venue gets to sell out (and make money from the full audience through concession sales, programs, t-shirts, and such) and the scalper gets the chance to make substantial profits with little effort.

Scalping is a legitimate and useful service. People just don't like paying more than the face value for anything.

Don't Be a Turtle

The blogosphere is afire with repudiation of offensive speech, catalyzed by Kathy Sierra's decision to stop blogging forever (or, presumably, until such speech isn't part of the Internet—e.g., an end to flamewars). Let me start this entry by saying that I like Kathy's blog: I can't think of a single entry that I haven't enjoyed and I have tremendous respect for her as a blogger and as an evangelist for evangelism. But I'm sorry to say that this move and the mob response really rankles me.

First, I've lost some respect for Kathy because this isn't, in my experience, how strong women behave in the face of adversity or withering statements. Rather than recoiling and stifling your voice, I think a strong person would shout louder. The person or people responsible for the statements she cites want her to shut up, they want her to stop blogging. Complying with such demands just emboldens them in the future.

The cry of misogyny seems misplaced to me because the vile statements and epithets were directed at Kathy Sierra. They strike me as hatred of one woman, not women in general. Maybe the posters are misogynists, maybe they aren't. With anonymity comes the inability to distinguish between copycats and amplifiers. You just can't know that two people going by the same name are the same person or vice versa.

Further, as death threats go, they seem pretty low-key. Michelle Malkin's litany of death threats she's compiled is pretty scary. The worst offense that I read was about desiring to see her in a noose. Maybe I've got thicker skin, but that doesn't seem specific—something I think actionable death threats have to be to get the police involved. Intimidation isn't the same as death threats; let's not conflate bullying with thuggery.

The response from the blogosphere has alternated between self-serving statements like Robert Scoble's staging a sympathy blogging strike for a week and falling over themselves to deplore those making the comments. Meanwhile, the story got picked up by the BBC and the San Francisco Chronicle. Traffic and discussion have surged to the blogs that have covered this story, but I'm sure no one could possibly have had that in mind in making their public denunciations. (I am well aware of the irony of me making an entry about this story. But I don't have traffic, don't expect any from this, and am only writing this because the whole thing bugs me.)

To my mind, this is the latest in the Trottist campaign for civility. Nearly every one of the screeds I've read admonishing the perpetrators (including Kathy's original entry) position this as a threat to the blogging world. It's as if this sort of behavior is the norm or even an insidious part of the blogosphere. In my travels (and online they're extensive), I've come across plenty of incivility but rarely threats. I've had a few on my blogs (even on my family one) and I've had some illicit requests for my daughter's picture. They rattled me every time. But I did what was ultimately within my power: deleted the comments, banned the IPs, removed the pictures, and changed my behavior for the future. I didn't stop blogging; I just started blogging better. If someone threatened my life, I'd brush it off unless I had some reason to believe that it wasn't just talk. Like if they were left on my voice mail or nailed to my door. A comment on a public site is just too easy to make. I'd want to see that the person had made some effort to inject himself into my life.

For the record, I think the comments left were disgusting, rude, and inappropriate. Death threats? Maybe, but I don't really know the law. I think there's a bunch of overreaction from nearly everyone involved. The proper response is to delete the comments if it's within your power, ignore the specific participants (they'd love the attention and traffic), and publicly state your indefatigability. Anything less plays right into their hands.

[UPDATE: Oh, I reread Kathy's entry. I think talking about slitting someone's throat is worse than the noose comment. So it's more vile than I originally read. Still too vague to be a death threat to my mind. Also, on further reflection, I think parents should do whatever they think is best to protect their children and families. So while I wouldn't have expected Kathy to close up shop, I can't exactly fault her for it if she thought her family was at risk.]

[UPDATE (4/2/2007): Kathy's posted a blog entry. It notes that she's going to be on CNN today talking about this. Scoble notes that he was supposed to be on that program too, but he got cut. This all seems more and more disingenuous as it plays out. Death threats are no laughing matter, but shouldn't we reserve the outrage and fear for when they're credible?]

[UPDATE 2 (4/2/2007): This is a good article on the subject from Kuro5hin.]

Up in Arms

Last week, Flickr announced that they were going to be converting "old skool" members over to the Yahoo authentication system. As one of those users, I'm not looking forward to the merge but I'm not blowing a gasket about it.

It was neat signing in as an "old skool" member even though I'm pretty sure that there was no real difference in doing so. I've always felt a little tinge about getting in on things before they were popular or widely recognized for their greatness. It's pretty stupid when you get right down to it, but I like to think of myself as an early adopter.

My major fear over the merge is that there's going to be some screw-up. We've got 3,721 photos (about 5,000 or so still left to upload). Earlier this year, we purchased a pro membership and decided to use Flickr as an alternate backup location. We've carefully titled every photo (and tagged many of them) and I'd hate to see all that work go down the crapper so that Yahoo can more easily data mine my account. I'm sure that they've thought through the process, but it's one of those points where bad things happen. I hate bad things happening.

But realistically, I'll suck it up and convert. I don't have any particular beef with Yahoo and I've always liked Flickr as a Web application. They've been berry berry good to me so I'll stick with them.

Permission to Link Considered Harmful

The nature of the Internet is decentralization and an attendant lack of control. I think this is one of the reasons why it has become as popular as it is—even though CompuServe, AOL, and Minitel all had tread similar ground prior to the Internet boom. The fact that it was built with precisely this nature is fascinating and amazing at the same time, especially given that it originated as a military and government project. (Side note: its purpose, however, was not to reroute around damage caused by a nuclear war as is commonly thought.)

Since the Web has exploded in popularity, many entities and individuals have bristled at this systemic lack of control. They don't like the unbridled power of the free Web, just as they didn't like the power of the free press in previous era. They send out cease and desist orders to have content removed, they try to stifle free speech by subjecting bloggers to the same onerous restrictions as campaigns, and they attempt to control how other Web sites link to them. The latter is the matter I'd like to focus on.

The recent case in Texas is only the latest example of the phenomenon. For years, many companies have been trying to stifle linking entirely. This is a ludicrous notion that is antithetical to both the nature of the Web as well as the actual self-interest of the companies. Linking brings traffic, recognition, and influence—there's a whole industry built up around soliticiting linkage. To be sure, there are problems with linking but they fall under the leeching of bandwidth, which is an actionable property rights infringement.

Lately, though, I've noticed a disturbing trend among people where they don't want links to their blogs because they don't want people reading their sites. They think that their employers, their friends, or their family won't find their site if they keep a low profile or use a fake name. Security through obscurity (or, in this case, privacy through obscurity) is a chimera: if it's on a public site without password protection, you can consider that everyone you know has or will read your writing. If Google can find it, I can find it via Google. Promise. Operating under assumption will save you a lot of grief and embarrasment.

Anyone or anything that seeks to require permission to link to their site is a fool. In my capacity as a link blogger, I never consider whether or not I should ask about linking to a site. My rule of thumb is that if it's something I can see then it's something I can link. If you don't want me doing that, then make your blog or site private—there's plenty of tools that allow you to do just that. Otherwise, suck it up and enjoy the traffic.

Harsh Thoughts, Frequently Delivered

I've been reading Violent Acres for a bit now and I'm really torn about it. On the one hand, it's very well-written and takes controversial sides. That's refreshing in the blogging world of sameness. On the other hand, it oftens seems to be controversial for controversy's sake—a John C. Dvorak of the political and cultural realm. With all the ads on the site, it's hard to tell whether she's an Ann Coulter for advertising or a serious blogger who's just trying to cash in.

This recent entry, though, has cinched it for me. It's another salvo in the long-winded tirade against the phenomenon known alternately as the "echo chamber" and a "circle jerk".

If you don’t have the guts to step outside of your comfort zones, you will never grow and change as a person. If being well liked is more important than being yourself, then you will never say anything of value. If you don’t have the balls to be hated, then you don’t deserve to be loved.

This sentiment sounds bold and fresh at first blush, but rapidly unravels when you start to think it through. It's a false dichotomy—there's more to writing than being loved or hated. There's plenty of reasons for writing that are not incendiary: education, edification, or clarification, for example. Any of those reasons could involve a style that is qualifying or tempered or measured. Writing need not be passionate or inflammatory to be effective—any traipse through the literature of any culture would indicate that.

I've come to the conclusion that she is a troll, taking positions and writing explosive commentary for the purpose of driving traffic. It's been quite successful, but I don't like it and it seems phony. I think her popularity is akin to Dr. Phil's: he's got nuggets of wisdom and good advice but people watch him for the outrageous things he says. I'm done—unsubscribed.

Grammar Girl

I discovered Grammar Girl awhile ago but thought nothing more of her at the time than "Oh, she's using Quick Blog." Then a co-worker brought this CNN article to my attention and I realized that she's actually quite popular.

I don't know why but it's always astounding to me when I find a Quick Blog being popular or being used by someone high-profile. I shouldn't be surprised—it is a quality product after all—but I can't help it.

The views expressed on this website/weblog are mine alone and do not necessarily reflect the views of Go Daddy.com Software, Inc.

Respect Your Daddy

The good thing to come out of last night's meeting was a newfound respect for Go Daddy, my employer. Now don't get me wrong, I love my job and think Go Daddy's a great place to work. But the blogosphere has not been kind to Go Daddy.

Since that's where I spend my life, I've acquired a certain tint to how I think the world perceives us. Google is revered, but Go Daddy is often mocked and derided. It always felt like we were regarded as Web 2.0 for beginners. So I had it in my head that we were one of those great but misunderstood companies.

But last night I got to interact with some real people. They couldn't sing the praises of Go Daddy enough. Incredible customer service, excellent product offerings, great value. It was an eye opener.

I never really thought that our 24/7 phone-based customer service was anything special. Or helpful, from some of the escalations I've seen. But thinking about it more, I realized that I, as a developer, only get to respond to incidents where things have gone far wrong or for too long. My time listening in on customer service and sitting with them was very different and I had attributed it to lucking upon the good reps. But I think now that the bad ones that I had encounterd via escalations were the exception.

There's a reason why we're the number one domain registrar and shared hosting provider. There's cheaper companies out there, but they're cheaper in other ways as well. And the barriers to leaving hosts and registrars is quite low. There's got to be some compelling about our offering to grow as spectacularly as we have.

I'm glad that I found it.

[The views expressed on this website/weblog are mine alone and do not necessarily reflect the views of Go Daddy Software, Inc.]

Social Media Clubbing

Last night I attended my second meeting of the Phoenix branch of the Social Media Club. The first meeting was utterly useless and I gave the club three strikes before I was done with it entirely. After last night's meeting, I'm going to say that's it out. (I couldn't give it the second strike because it conflicted with a holiday party.)

I have a pretty high standard for organizations and meetings. If I'm not getting something out of them that I can't get elsewhere, then I'm not going to bother. I'm not into any sort of networking because it generally devolves into a sales pitch coupled with feigned interest in my life and work. I've got better things to do; even watching Law and Order reruns is a better use of my time than that sort of thing.

So last night's meeting was on some drivel called the New Media Release. It's supposed to be Press Release 2.0—boy am I glad they didn't think of that—with the ability to get past blogger's bozo filters in a single bound. As far as I can tell, it's a press release littered with graphics, movies, links to post to social bookmarking sites, and a litter of buzzwords. The example from the club itself is decidedly underwhelming: it looks like a press release embedded in a blog entry. Ho hum.

That was pretty bad, but the deciding factor for me was Francine Hardaway. She just wouldn't stop talking, a problem she herself noted in her entry on last night's meeting. But that's not the big problem I have with her: there were several annoying sorts there that loved the sound of their voices. She's one of those insufferable types that is so self-absorbed and pretentious that it made me want to leave mid-meeting. From the name-dropping ("As my friend Scoble said", "As so-and-so said, you do read so-and-so, right?") to the tedious anecdotes (Paraphrase: "Social media is everywhere ... I was attending a real estate conference ... My daughter, who own's her own company, was reading Engadget ... sent me an email with photos of the new iPhone ... All the real estate professionals around me were agog over the pictures and asking questions ... See it's everywhere because they weren't reading blogs during the presentation.") to the elitist pretensions ("Us tech people", "Of course this is baby stuff for us", "I've been in PR for 17 years", "I've been blogging since before it was called blogging", "And they said that Phoenix was too small to have a social media club") to the constant stream of buzzwords ("background himself"), she just rubs me the wrong way. I couldn't imagine attending another meeting of Francine's klatch.

But don't get me wrong, it's not just an issue of personality. The entire notion of the club strikes me as missing the point. It is dominated by marketers whose sole goal appears to be penetrating through to and using the fora of user-generated content producers. How can we get our stuff noticed by bloggers? How can we get our "viral" video onto YouTube? How can we adapt our current way of doing things to the real-time, no-holds-barred new media?

At the same time, however, it's aiming for those interested in social media who don't know much about it. (Its aim is errant because I think that type probably doesn't even know SMC exists and wouldn't attend even if they did.) So it becomes a social media for dummies forum. Let's talk a bit about del.icio.us. Let's have a meeting about how to get your blog recognized by search engines.

The missing party in this is the social media producer: the blogger, the podcaster, the vlogger. But that's where it's at, man. These people could really stand to meet each other, bounce ideas off each other, and get acquainted. That is what I hoped this club would be about, but it'll never happened if it's dominated by marketing flacks. There were a few bloggers there, but I couldn't get a read on whether they thought it was a waste of time as well. Oh, apparently, a couple of them liked it.

The social media producer, however, doesn't need a club for tutorials or acquiring knowledge. The producer is, by definition, comfortable with the Web and there are far better resources on the Web than could ever be assembled in an over-crowded wine room at La Madeleine. So it's not about the presentation by Francine (that would have to stop); it should be about sharing information or advice with people you've never met in person. That's the only advantage a geographically-based meeting has over a virtual one.

If I were changing things (and I don't care enough at this point to even bother trying), I'd have each meeting have a theme relevant to the producers: getting traffic, best services, thinking up content ideas. And then people ask questions, get answers, and share knowledge in a freewheeling conversation. Or announce the topic, have people introduce themselves, and then end the meeting while people gravitate around to talk about the theme.

And for chrissakes, get a meeting room without a substantial table taking up 90% of the floor space, relegating people to the walls and outside the room.

About this Archive

This page is an archive of recent entries in the Blogging World category.

Blackberry is the previous category.

Business is the next category.

Find recent content on the main index or look in the archives to find all content.

Feedback to

Monthly Archives