Utah Open Source Planet

This is something that has been on my mind for quite some time (think years), but I’ve refused to blog it, because it goes against the beliefs of many of my friends. In short, this post is going to hurt, but I just can’t hold out on it any longer.

Question: Are you one that pirates music? Movies? Software? Any other digital media that is otherwise copyrighted in a manner that would consider your actions piracy? If so, then I have a second question for you: Do you believe in the principles of freedom and liberty? Then this post is for you.

I’m going to shoot straight- piracy is a slap in the face for those of us fighting for copyright restrictions to be lifted, for Digital Restrictions Management wiped from the face of the Earth, and the DCMA over turned. The fact of the matter is, we hate the RIAA, MPAA, blood sucking lawyers, and everything else wrong with copyright just as much as pirates. However, we recognize there are more mature ways to reaching our goals, and we further recognize that piracy is just hurting our cause, not helping it.

Think about it for a second. If you pirate music, books, movies, software, or any other copyright material, what are you saying? At first thought, you’re sticking it to the man, right? You’re also harming material that is open, in the public domain, or otherwise copyrighted in a manner that let’s you share to your hearts content (commonly referred to as “copyleft”). Look at all the artists who have chosen independent labels, if any label at all, that encourages sharing of their music. Instead, you’re sharing Tori Amos, Metallica or some other artist. What you’re saying, is their music is better, but I doubt you’ve given the other music a try, haven’t you? What about proprietary software? You’re saying that you don’t want to pay these outrageous prices on software. You’re also saying that this application is superior to Free Software. The same can be said for images, books, videos, and other digital works. Piracy isn’t liberating anything, it’s just making it so you don’t have to pay, and it’s making more laws on copyright further complicating the system. It’s not the solution to the problem.

Now, I understand the want, or even need, to get these materials. Maybe school requires Microsoft Office. Can you use OpenOffice.org, or some other Open Source office suite? If so, why pirate Microsoft Office? If you absolutely need that specific office suite, surely the school has student discounts. What about Metallica? I was just as pissed as the next guy when they went against Napster, but pirating their music only says you still like the band, and you still like their tunes. Why not boycott them? Why not find another artist in metal that allows sharing and free distribution? If you just like their tunes so much, why not listen to them on a radio service, like Last.fm? Using a service like this, not only will you get Metallica tunes, you’ll also get similar artists that you may not have known about. Discovering new artists is a great way to support music in the Free Culture. If you must have their stuff, is it really that hard to pay a dollar on Amazon or iTunes? If you don’t want the money reaching Metallica, why not get their albums from a gray market shop?

Piracy just doesn’t equate to honesty as well, no matter how you look at it. You’re not being honest in your dealings with your fellowman, and if you’re engaging in piracy, how can others trust you in different aspects of your life? Sure, you can admit that you’re a pirate, but you’re still not honest with the law. You’re not honest with the artists or developers. As much as it sucks sometimes, we should believe in honoring, obeying and sustaining the law. I’m not saying follow the law blindly, and there are always times when we should lobby changes to the law. This seems more the right path than ignoring the law and engaging in piracy, don’t you think? Now, we’re not perfect law abiding citizens. I for one have a hard time sticking to posted speed limits on the road and coming to a complete stop at stop signs, so I’m certainly not one get all high and mighty, but is that an excuse for me to break other laws? Further, what if I place something in your care that requires your trust? Can I trust you won’t put it on bittorrent, or otherwise break my trust?

Piracy especially is troubling for those of us who believe in the Free Software ideals. Here, we’re fighting the good fight for software freedom, then in the dark corners of the basement, we’re pirating proprietary software. Isn’t this hypocritical? You either believe in the ideals or you don’t. Playing both sides doesn’t work. Further, as already mentioned, pirating the software only pisses off the software execs and their lawyers, making the whole copyright process more complicated- it’s doing nothing to liberate the software at all. Boycotting the software, and using competitive open source applications are a couple ways of getting the point out that software should be liberated. If no one is using their software, how can they continue with their business models?

Finally, I admit to being a pirate many years ago. I had a collection of gigabytes of music, videos and software. I was on the peer-to-peer networks night and day. However, when I thought about it, I realized that my actions could not be justified. How could I promote and advocate “copyleft” licenses and continue doing what I was doing? No man can serve two masters, and I had to make a choice. I deleted my entire repository of music, videos, books, software and anything else that was pirated, and started anew. This was nearly five years ago, and guess what? I don’t miss any of it. I have all the music I want to listen to through Last.fm. I have all the software I want to install through my distribution’s software repositories. When I need movies or music, I hit up the gray market shops, getting them for cheap and in excellent condition.

Give yourself a soul-searching moment. Think about your beliefs and then your actions. I think you’ll find that piracy just isn’t the right way to go about removing all the restrictions we currently face. Piracy only makes more ridiculous laws and prevents the Free Culture from furthering it’s cause.

With all the whoo hah about why GNote sucks for Tomboy, mono is patent encumbered software by Microsoft, people eating FUD for breakfast, and other things, one argument I’ve failed to read is this:

GNote can bring Tomboy to Red Hat Enterprise Linux, as Red Hat will not ship mono with its flagship product.

Whatever Red Hat’s reasons are for not shipping mono with RHEL, GNote is a major win for the open source community. Different people and different operating systems have different needs, and providing yet another application to fill a need is what Free Software is all about. This gives Red Hat the opportunity, if it desires, to bring Tomboy to RHEL through GNote.

Lastly, let’s not forget the Free Software Definition, which it seems GNote is taking advantage of:

• Run the program, for any purpose
• Study how the program works, and adapt it to your needs
• Redistribute copies so you can help your neighbor
• Improve the program, and release your improvements to the public, so that the whole community benefits

This morning I had the opportunity to present via O’Reilly Webinar on Facebook development. I covered the basics of how to get started in Facebook development, and the resources that would get you going. I mentioned I’d post these slides online, so here they are. I was hoping to get audio attached to them, but we’re still waiting on that. Regardless, if you want me to present this to your organization or group, feel free to contact me.

This is a picture of my Great-Grandfather, Joseph Stay. With a son named after him, I’ve spent some time reading about him and learning about the experiences of his life that I can pass down to my son. One of my favorite things to do in my spare time (when I get any) is to read about the lives of my ancestors. My faith teaches about life both before and after this life, and as such, it’s important for me to know who came before me and how I came to be. Besides that, it’s just plain fun.

Some of my ancestors were very good at tracking their lives and what they did. Some of them kept journals and records, so that their progenitors could learn about them after they passed away. I have a journal like this, as do my parents and grandparents. These journals show a glimpse into our successes, trials, and failures, and what we did to overcome them in hopes that our children and those that come after us can learn from our own mistakes and make their lives better.

This concept is great, except it only applies to those after this life - only they can learn from us because we often keep these details secret. What if we could share the skills we have, let others try them out, play with them, learn from them, just as we’re able to do with the experience we’ve learned from our ancestors, but in this life?

This is the reason I like the concept of “Open Source”, which started with Software, but really, could be applied in all expertise. The concept of “Open Source” is all about sharing the experiences we have in this life and allowing others, still in this life to try those experiences out, apply their own experience, and continue to share with others. It’s just what our ancestors did for us, but applied to this life.

What if we all, in everything we did, shared what we did with those in this life, instead of planning for the next, so that we could start that legacy of learning right here and right now. What if we as a society were working together instead of just us and those that follow us after this life? Why do we have to wait until we’re dead to let others learn about what we’ve done?

I’ve been throwing hints on Twitter over the last week or two that I’ve been working on this, and with a little extra time I finally got it together. Today I’d like to announce that, as of this moment, we have some really cool new features for Twitter users on SocialToo.com, all in one place!

SocialToo, which is trying to be “Your Companion to the Social Web”, is seeking to build the tools and utilities that compliment your experience on the social networks you belong to. Up until now, anyone could sign up and automatically get the ability to have it follow all those on Twitter that follow you. The script ran once a day, and would do all the work for you, while also enabling you to blacklist users you don’t want it to follow. This enables you to automate, while making exceptions, making management of your friends on Twitter much easier. In addition, by providing Facebook credentials it would redirect “yourusername.socialtoo.com” to your Facebook profile.

Today, I’d like to announce some new features:

• First of all, for those with less than 2,000 followers (this is due to a Twitter limit), we’re now updating your followers up to the hour - as Twitter improves their API I’ll update this to work even more realtime. We’re working with Twitter on getting their API improved to handle this. If you have 2,000 followers or more instead of just once a day, we’re now updating every 6 hours, so even your followers will update faster than before.
• Today, we’re adding the ability to add a message that we’ll send to all your new followers via direct message. This can be a great opportunity to thank your followers, or, as a business account, tell them about a unique promotion you are running. However, if you’re just signing up and aren’t already following those who follow you, we recommend waiting until your account syncs up before turning this on, or all those we follow will get dm’d, even if they’re not new followers. This should only be applicable to new accounts - if you have an existing account, check your preferences and be sure to turn this feature on!
• In addition, if you have a bunch of people who followed you, you followed back, and then they stopped following you (this is the case for many Twitter spammers), we’ve added the ability to turn on a feature that unfollows those that are not following you back. I think it’s who you follow that matters, so my recommendation is to use this feature sparingly, and turn it off when your account is back in sync. You can use it however you want though.
• We’ve got a fresh new design! - okay, I admit, we’re not perfect yet, and were this the golden days I’d say we’re still technically in “beta” (I hate that excuse though), but we got a superstar designer to offer some help on the design for this - thanks so much to our designer!! You know who you are. The new design will come into play much more in the next round of features.
• My favorite feature: follower statistics. Not only are we now tracking those that follow you, but we’re also tracking those that stopped following you. You’ll now get an e-mail every night telling you the followers that stopped following you, and who your new followers are (and consequently who you followed). This is turned off for all existing users - go into your preferences to turn this on and find out details about those you’re following and those who may have unfollowed you (and we’ll soon provide other statistics to help you find out why).

As planned, I think we’re changing the game in making your social experience better all in one place with these tools. You may be familiar with other sites that do similar things out there, but you will quickly find that SocialToo.com is easier to set up, more automated, more accurate, and much less hassle than some of the other services out there.

Oh, and there’s one more really big thing. You’ll have to wait a few weeks to hear our next announcement though. Much more on the way!

You can sign up at http://socialtoo.com (that’s T-O-O, like “tool”, or “also”). Follow us on Twitter at @socialtoo for more updates!

Luke Stay is my younger brother, and fellow geek like myself. I like his writing style so I asked him to start guest-blogging on Stay N’ Alive. You can follow Luke on his blog at http://lukestay.com, or on Twitter at http://twitter.com/afrowhitey, or FriendFeed at http://friendfeed.com/afrowhitey. –Jesse

About 6 months or so ago, my brother, Jesse, would not quit talking about some crazy new service he was using online called Twitter. One day, I got bored enough and decided to check it out. Little did I know, that service would serve as some sort of wormhole, propelling me helplessly through cyberspace into a strange new world, referred to by its own inhabitants as, “Web 2.0.”

I suppose I should start off with a little background on myself. I primarily work as a Stagehand in Las Vegas, NV for the local branch of IATSE. My area of expertise there is as an Audio/Visual Technician. As an A/V Tech, I am paid to install large screens, large digital projectors, large plasma screens, and many other audio/visual components for the various conventions and conferences that come to town. Sadly, I still use a 32” analog TV as my primary source of entertainment at home (yes, I did already get my free digital converter box, thanks for asking). I am an A/V geek, an A/V geek with debt that can’t afford any of the high-end components he installs on a semi-daily basis. It’s a sad existence, I know.

That being said, I am no stranger to computers or the Internet. I grew up trying to get my family’s ancient computer to do things it shouldn’t have been able to do and crashed it many times in the process. I learned computers by trying to get the family computer back up and running before Dad could come home to find out what I had done … again. I took programming courses in High School and Java in College, but ultimately decided programming was not for me. Instead, I chose to study film and have aspired to the life of a screenwriter ever since. I can’t write my own code, but I can understand most code and manipulate it to do what I want. In summary, I am a computer geek with a pretty lame disguise.

I started using Twitter mostly out of curiosity. At first, I just followed Jesse and watched, observing this strange society for a month or so. Then, I started to contribute, replying to some of Jesse’s tweets. This got his attention, and in turn, got me some more followers and a much larger society to observe. Things were pretty quiet at first, mostly Tweets about what people were doing, or what people were reading, or what new technology Apple was about to release, but then came a sort of uprising. I was witnessing a revolution.

These were the days of the infamous “Fail Whale.” Twitter was down and the natives were getting restless. The few tweets I saw actually come through were mostly complaints about their ruthless Twitter overloads. “Where did @replies go?” and “Why isn’t Twhirl working?” and “Can’t anybody do anything about this?” and “Will somebody PLEASE think of the children?!”

Just when things were looking the grimmest, new services began to pop up. Some began to move their discussions to FriendFeed, but that didn’t seem to work as a Twitter replacement. Others seemed to drop off the face of the planet, or at least the Web 2.0 planet. Others still stuck to their guns, pledging their allegiance to Twitter despite all its faults. Then, a new alternative emerged, Identi.ca.

Identi.ca billed itself as Twitter for the people; by the people, and quickly amassed an army of rebels set on taking down the evil, unreliable Twitter Empire. Among its strongest advocates were @JesseStay, @MarinaMartin, and @ThomAllen, and a majority of the small group of people I followed on Twitter. I decided to switch. My name is Luke after all, and Luke would never let himself be seen cavorting around with the supporters of the Empire. Not even Uncle Owen would do that.

In one month, I saw more activity and more of a community on Identi.ca than I ever had on Twitter. People were coding furiously, tapping into the new open-source API that Identi.ca offered. Bridges were built, new friendships were formed, manifestos were written, and new blogs emerged to welcome in the new recruits. Then, almost as quickly as it started, the revolution ended.

I came home from vacation and began to notice a lot of decreased activity on Identi.ca. Only one or two of the people I followed were posting regularly. I turned on my old Twitter account and there they were. The revolution had ended. The rebel army had lost. There would be no triumphant Ewok songs to welcome in the new era.

I learned a lot during my time on Identi.ca. I learned how to track certain terms. I learned how to find more interesting people to follow. I saw a lot of interesting conversations. Most importantly though, Identi.ca served as a sort of microcosm to the way this Web 2.0 world worked. There was a problem on the web, a shiny new service with lots of great features arose, and the masses followed like a swarm of hungry locusts. Then the old service, still much larger than the new one, fixed a lot of its problems, and the swarm came back home.

Since then, I’ve branched out a little on Twitter. I began to get my own followers and have my own little network of videographers, editors, and film geeks. I’m even following Dave Matthews (@DaveJMatthews) and Stefan Lessard (@SLessard) from the Dave Matthews Band (who are surprisingly active). My observations shifted somewhat to FriendFeed as I begin to utilize Twitter more and more, and I see the same sort of Identi.ca cycle on a much smaller scale almost daily. The Web 2.0 world finds some new product or feature, rushes out to play with it, review it, love it, or hate it, and then drops it completely as some other new product or feature is announced.

I remain a somewhat casual observer. I learned my lesson. In this strange new world, it’s better to wait out the flurry of hype that comes with the latest new web gadget to see if it actually takes root. If the locals drop it after a month or less, I don’t bother. Who knows, it may be the next Empire Strikes Back, or it may just be another Star Wars spin-off; a Star Wars Christmas Special in hiding.

I am such a geek

Joseph Scott, developer at Automattic, posted that Wordpress.com has recently broken 4 million total blogs. He further mentions that it took just 4 months to go from 3 million to 4 million. Assuming the rate isn’t exponential, it will just be end of December when they hit 5 million blogs. What would be even more fascinating is to know how many self-hosted blogs on Wordpress are currently running. (This blog is a Wordpress MU install)

Wordpress seems to be no Facebook, but perhaps as projects like BuddyPress take off and people begin to virally create blogs and content with their friends it will get to that level. Where Wordpress still has left to compete is with microblogging sites like Twitter - perhaps, with the large user base that they currently have we could see this happen in the near future.

There are rumors that Facebook has been working on their own Wordpress plugin for Facebook. This is troubling for those of us developers that are developing for Facebook Connect, as it shows that Facebook could in one sweep, wipe any developer writing for the Facebook Connect platform out without any advanced notice. It only appeared that in the past, this type of thing only happened on the Facebook website itself, as Facebook has a right to, but I’ve seen it myself with my own development on Facebook Connect today.

Fair enough. I like competition, although I’d love this to be a community effort. So, since we know Facebook is working on their own Wordpress plugin for Facebook, and we know Facebook isn’t willing to divulge their code yet. Since I’ve already devoted 20 or so of my own hours to the exact same project with no knowledge from Facebook, and am just now learning that Facebook was working on this behind the scenes incognito with no involvement from the community, I’d like to release my own plugin to the public, under the GPL v2.0 today, in the hopes the public can help with development and further building of this plugin, as a community, not just under Facebook’s roof.

It’s very troubling to see Facebook develop on external apps outside of Facebook like this - it only shows that Facebook is not afraid to encroach on other developers’ projects and that any one of us is at risk of having a useful project, our time and effort (I had no intentions on making money from this), wiped out in an instant. Sure, Facebook has every right to compete, but the least courtesy of notifying developers it already knows would be competition. With such a Wordpress plugin this also encroaches on Six Apart’s announced integration with Facebook Connect, and puts Facebook in direct competition with Six Apart instead of making it Automattic’s problem.

It’s my sincere hope that Facebook decides not to continue such projects internally, but instead contributes to existing projects if they must do so. Facebook should in no way be competing with the developers that use their platform without warning, or risk us not being willing to contribute such things in the future. Let’s work together on this Facebook - how about a “we need help” board, or an “internal projects” board so we can know what you’re working on in advance. In this way we can work with you instead of parallel to you and hours spent doing so won’t be wasted. Or how about a little nudge to people like Six Apart saying, “we may just have to compete with you on this in the future” so their own time isn’t wasted with the integration.

Why should I keep building external web apps that integrate and send users to Facebook if Facebook is just going to replace my web apps in the end anyway?

So, I’m going to release my code here right now in hopes we can make this a community project - it requires you to set up your own app for your blog under the Facebook Developers site (just set your callback URL to your own website’s URL), and you must take your application key and enter it into the admin section. Only developers of the Facebook app itself can login through Facebook Connect until Facebook launches (one more advantage Facebook has over us developers - they know when they are launching, and therefore know how much time they have to develop these things, another reason to leave it to us developers in order to keep it fair). To install on your blog after doing so, just unzip the folder in your plugins folder, and activate your plugin under the plugins section in Wordpress. After that, any Facebook user will be able to leave comments, under their own authentication, Facebook avatar, and name without having to re-enter it each time. We’ll be integrating this more in the future - if you can help please let me know! My project is a community project, not owned by Facebook, completely owned by me and you for the benefit of the community.

You can download it here.

You can see it in action on my test site, http://socialmediacast.staynalive.com - check out the Hello World post to see the existing comments. Note you will not be able to log in to Facebook Connect on that site because you are not a developer on the app for that site.

Now, I know I ranted a bit - it’s late, but I hope this makes some sort of sense. Am I out of line here? Should I just scrap my code completely and let Facebook do this? Is it a wise move for Facebook to keep making external apps like this that integrate with Facebook? What’s the best way for Facebook to approach this? I welcome your comments below.

I mentioned earlier I was going to announce a big change this week. I’m “on the move“, as Jeremiah Owyang would put it. Today was my first day working full time at a new Silicon Valley startup with offices here in Utah, where I will be leading their Social Product strategy moving forward. I am phasing off my regular consulting, and moving to this new Entrepreneurial effort in helping them grow.

At the moment, I can’t reveal much more, other than the fact that we’re building the next era in Interactive Entertainment on the iPhone. The company I’m working with right now started out as a client of mine, and I liked their product so much I decided it would be worth helping them out full time. I believe fully that we are going to change much of the way you watch TV today. We will be launching most likely next week, and you can follow the Twitter account @MediaMyWay to catch our launch announcement and follow our updates (I’ll also point you there from my Twitter account when we launch - we’ll announce it there first!). Other Twitter accounts you can follow for updates and “clues” are @JustintheWhitt, @Romay, and our CEO, @BradPelo.

How will this affect the other stuff I do? In reality, not much is changing, other than what I do full time. I have received permission to keep SocialToo.com going part-time, as it has, unless it takes off. Expect some very cool things to come from SocialToo in the near future - we’re working on a completely new design and a really cool new feature that will be released in the next couple weeks.

As far as my blogging and book-writing is concerned, I see nothing changing, and I intend fully to continue blogging regular, unbiased articles that I feel inspire and educate. I will disclose where necessary if I feel my current employment has any influence in what I am writing. I still hope to continue writing in other capacities as well, as long as speak as I’m asked to do (I’m speaking in Dallas next week to the Dallas Chamber of Commerce, in fact - come see me speak!).

So, keep watching the @MediaMyWay Twitter account, and you can also follow this blog and I’ll be sure you’re aware of the latest of our happenings (we’ll have a company blog here shortly, which I’ll let you know about). In the meantime I’ll keep posting regular, educational, and original content as I always have and always will. “Stay” Tuned!

As I am speaking, Utah is having their yearly Open Source conference. If you’re in Utah or outside Utah (most of my audience is outside Utah), it is well worth the trip with some great topics from ssh tips and tricks to Wordpress Performance and Scalability by Utah’s own Joseph Scott from Automattic. I would be there myself but I have deadlines I have to meet this week (I have a big announcement to make next week which will explain my lack of time this week). However, as I was tracking the updates from the conference, I noticed there seem to be way more people updating from Twitter vs. the Open Source-based blogging tool, Identi.ca. In fact, I notice many Open Source proponents even outside Utah embracing Twitter over the Open Source-based Identi.ca and I wonder why.

Now, I wasn’t paying attention during OSCON so I don’t know if it was the same there, but I’m willing to bet there was a lot of activity going on within the Twitter network there that really should have been happening over on Identi.ca. I’m wondering if it’s just lack of education about Identi.ca, or if our views of the principles behind Open Source have changed.

I remember a day where in each company I worked for I would do all I could to try and get them to let me run Linux on my desktop. I still run vim and I still run open tools like Apache, MySQL, and Perl. In some (remember Red Hat 5?), I was making a sacrifice by doing so, because I knew I had complete flexibility to make the changes and configurations necessary to make it do what I wanted to do if it did not yet do it.

When I was an Engineer at Backcountry.com we thrived on this principle. It actually made us more productive as a company because when we used Open Source software, we could configure it the way we wanted when it wasn’t working the way we wanted it to as a company. This would have costed us hundreds of thousands of dollars in custom software changes if we used a shrink-wrapped solution. Not only that but we could give back to a great cause if it didn’t meet our needs, and in fact we gave back quite a few changes to the Open Source community because of this principle.

Now, if you are not one of those types that went out of your way to use open source software for the principle, and because of the reasons I mention above, then I’m not talking to you here. However, I’m calling each and every one of the Open Source advocates out that are on Twitter and have not yet tried, nor use Identi.ca on a regular basis. This is no different than running Linux on your desktop as in the examples I mentioned above. If Identi.ca is not working the way you want it to, as an Open Source Advocate and promoter, you have a responsibility to jump in and contribute the areas you don’t have access to. That’s the true spirit of Open Source, plain and simple! Here are the reasons why you can feel good using Identi.ca, or build your own Laconi.ca instance that can communicate with Identi.ca:

• You own the content you post - All posts through a Laconi.ca instance are published under the Creative Commons license, meaning the publisher cannot own the content of its users. This is very much in the spirit of Open Source.
• Identi.ca is based on open source software - as already mentioned, Identi.ca is based on the Laconi.ca source code. You can even set up your own instance and have it talk to other Laconi.ca instances. If you don’t like what Identi.ca does, then fix it, publish your own instance, or give back to Identi.ca!
• Identi.ca talks with an Open Protocol, OpenMicroBlogging Protocol - Not only are you given source that talks this protocol, but you can write your own software that talks this protocol, and it will communicate with any other software that speaks this protocol. See my post on OpenMicroBlogger for an example of this in action. This is called “Federation”, and IMO it’s the essence of Open Standards and communication.
• Identi.ca has almost all the same features as Twitter, and more - as I’ll explain in a minute, this probably doesn’t matter, but the only features it lacks are direct messaging and SMS. SMS is expensive, and most likely won’t last on even Twitter - it costs too much! Direct messaging can be resolved by means such as e-mail or text messaging in a much cleaner fashion, although there are rumors of some working on even that. What it has that Twitter doesn’t though, and this is powerful, is that all Laconi.ca instances support XMPP out of the box, which means live-streamed updates straight from users, in real-time. Not only that, but you can track those updates, as well as any update on any Laconi.ca instance via Track functionality. Also, via OMB protocol above, you can subscribe to users on other services other than Identi.ca, and vice versa.

Let’s not get me wrong here - I’m not telling you to abandon your network on Twitter. I’m saying if you support and promote Open Source standards and refuse to use an open service like Identi.ca that is based on Open standards, you are living a double standard. You can still use Twitter in the meantime. I still use Windows and Mac for functionality I don’t get on Linux until me or someone else is able to replace that functionality for something better. The concepts are the same. I still use Twitter occasionally.

Also, many are giving the excuse of, “my network is bigger on Twitter”. I’d first like to point you to my listening/follower ratio article on LouisGray.com as to how strong your network really is on Twitter, but in addition to that, let’s pull in the Linux example again. How many Linux desktops are there in the wild? How many Windows desktops are there? We use Open Source because it allows us to configure it to do what we need it to do, and often we can get the job done better because of that. We don’t care if the majority of the population is using another closed tool because we can do much more with the open tools we’re a part of.

I’d really like to see some more Open Source proponents using Identi.ca as their primary posting platform. If you would still like to use Twitter that’s fine - there’s a bridge to enable you to do that, but it’s time we stood to our principles and why we’re using Open Source in the first place. Please don’t consider this a criticism, but rather a Bearhug to come help us out in this cause.

You can find me on Identi.ca at http://identi.ca/jessestay.

It all started with this post today. A supposed “employee ‘close to the deal’” told blogger, Zach Klein (who doesn’t seem to allow comments on his blog) that The Church of Jesus Christ of Latter-day Saints’ Family History division had made an unsolicited bid to purchase Facebook. Nothing else - no other background, no other resources to confirm the deal. Soon after, ValleyWag, the first to the scene and first large blog to publish anything about it, was blogging rumors they are well known for spreading. Soon after, Venturebeat and the Industry Standard were blogging about it, quoting Brady Brim-DeForest, who ironically was claiming this as news, not a rumor at all - I’m unaware of where he got it, but his news broke after Valleywag’s. TheInquisitr, while I’m sure had no ill-intentions, even made fun of the manner with some very radical and somewhat inaccurate claims that I know have offended some members of the LDS Faith that read the blog. The blogosphere seems to be a mess today in regards to regard for religion, faith, and respect for one another’s belief. It appears the LDS Church has become the punch-line of the blogosphere’s Jokes and I’m getting really tired of it.

Now, let’s talk about rumors. The blogosphere is known for spreading rumors - I’ve hated them from the get-go, but let’s face it, it’s a part of many blogs out there, and it may not be going away any time soon. (I think I could do an entire post about rumors in and of itself) I expect an occasional rumor about Microsoft trying to buy Yahoo, or Facebook employees leaving the company because they are mad with Executives, or even a crazy one like the iPhone 2.0 coming with 2 cameras and iChat video support. Frankly, I never share those (well, rarely), but they are fun to read because, well, they’re funny. But rumors like an entire Faith buying a huge company like Facebook are ridiculous, unfounded, and frankly offensive to me that anyone would take such a rumor seriously when the Faith is my own. It’s a religion, people - tell me one reason a religious Faith would need a social network like Facebook to further its mission. Do you seriously believe any religion would be so stupid as to try this? People would leave Facebook in droves if that were to happen, and a network like Facebook has no good way of building up the members of the Faith itself. The claim is absolutely ridiculous, and I can’t believe established bloggers are taking this serious enough to share with others! There seems to be a serious lack of understanding between the blogosphere and the LDS Faith and I’d like to figure out a way to put an end to it.

Let’s go back to earlier this year. You may remember my “Shame on You TechCrunch” post I wrote awhile back, calling out the writers at CrunchGear for an extremely biased, and very misunderstood and inconsiderate interview of Penn Juliette, in which he claimed Mormons had “magic underwear” (as a Mormon, I affirm to you, that my underwear is not magic), and went on to encourage him as he talked about how easy religious women were, degrading women at the same time. While I still will not read CrunchGear because of that, I have lifted my boycott of TechCrunch (just because there is no way to avoid it - I also did not know Arrington at all at the time), but as you can see, there is a blatent misunderstanding of the LDS Faith in the blogosphere. CrunchGear still stands by their article and has refused to make any statement to the contrary.

Now, to give credit to those that have blogged about this today, Eric Eldon (of VentureBeat) does have a great point in that the LDS Church does actively invest in stock to retain and increase the value of its members donations through Tithing, and Facebook employees are selling stock. Like Louis Gray, I too give 10% of my wages in the form of Tithing to the Church, and I sincerely hope they invest it wisely and don’t just waste it away. I know their investments are wise though, and even the “widow’s mite” is considered and cared for. The Church itself never publishes these investments and it would be impossible to know if some are in Facebook or some are in Microsoft or some are in Google. They take these donations as sacred, and every effort is taken to maintain the sacredness of those donations. However, an outright acquisition of Facebook would be proposterous and completely out of line with the Church’s history.

Every one of these bloggers could have done a simple Tweet in fact, and quickly gotten a response from Mormons on how ridiculous the claims are. Or they could have shot Louis Gray, or me, or Matt Asay, or Phil Windley, or other Mormon bloggers an e-mail asking us if the claims were true. It took me about 5-10 minutes to send an e-mail to the LDS church and get a response back (which, btw, said the claims are not true and unfounded), and in fact, the LDS Church CIO is even on Twitter - an e-mail or even simple dm to him may have done the trick.

Now, I’m not necessarily trying to call out these specific bloggers, but rather point out the problem in general - I respect most of them in fact and really enjoy their regular blog posts. I’m just trying to make a shoutout to the blogosphere that we’re here if you have questions! Let’s start an open dialogue about the Mormon Faith - do you have questions? We’d really like to answer them before you assume and blog inaccuracies in the first place. Please, don’t hesitate to contact me, Louis Gray, or any other Mormon blogger if you have any hestitancy before posting an article. It’s time we put an end to this nonsense, once and for all.

Last week I spoke about how the ‘@’ on Twitter and other microblogging services may no longer be necessary due to the addition of the in_reply_to_status_id API call on services like Twitter and Identi.ca. In the comments of that article you mentioned several examples why that would still be necessary. I’ve spent the weekend contemplating these and still argue with a proper infrastructure these would not be necessary. In my own opinion, services like Twitter and even Identi.ca are broken because there is no easy way to tag individuals and people without cluttering up actual content with unorthodox, unorganized ways of tagging data and people. We, the users have had to come up with our own ways to do so socially, and I think that’s a hack. Let’s go over a few:

Addressing a specific person or group of people publicly.

With current infrastructure on microblogging platforms, this is the one problem that will cause people to continue to need to use the @ sign. There is no easy way currently to say you want to make sure a particular individual or group of individuals see a specific message. This is different than a reply which the recently added API calls resolve, in that these types of messages are not necessarily in reply to anyone. So instead we have to clutter up our posts by prefixing our post with the intended recipient at the beginning, whereas if a proper infrastructure were provided, we could focus solely on the content.

Facebook has overcome this pretty well with allowing you to “tag” individuals in a Facebook Note that you would like to see the message, or that might be in the message itself. Twitter, Laconi.ca, and others need to look into a new API call to allow users to tag other individuals so this is no longer needed. Imagine, for instance, if Twhirl let you choose from your list of friends and tag them in the post you are sharing. You could then have pure message in your 140 characters and not have to worry about the intended audience.

Common English (or your language) names

I mentioned before that @ wasn’t necessary, perhaps even if there weren’t an API call provided to link replies. Microblogging clients should be able to read each username and look at your friends, and tell immediately that you are referring to one of them, adding them to your list of replies.

However, this gets tricky when you get to someone with a username that is common English or even another language. For instance, what if my username were “stay”? Every time any of my friends said they were “stay”ing somewhere I would get a notification stating they were replying to me or addressing to me.

The solution for this again would be fixed with a simple person tagging system like what I recommend above. Allowing me to specify the intended users in the message would allow clients to know I was addressing those users without me having to further clutter up the actual message with meta information that doesn’t need to be there.

Hashtags

Hashtags need to be gone, plain and simple. All Twitter and Identi.ca and even FriendFeed need to add is a simple meta layer to their API, and beyond just allowing me to tag individuals to my messages, allowing me to add tag keywords to identify my message and make it more searchable. Tags clutter up our messages as well and keep us from being able to say what we need to say in 140 characters. In fact, I argue that meta layer should be completely flexibly - imagine if I could append whatever I wanted to a message. Location information, what I’m eating at the time, websites I’m surfing, etc. (I’m just listing those in theory - those could be messages themselves, but some are meta information) Part of our 140 character message should not be words not pertinent to the intended message itself.

SMS and XMPP/Track

So you ask, if we add a meta layer on top of all this, how can I then tag my messages and tag people in my messages via SMS or XMPP (Jabber)? SMS and XMPP should be treated as clients. The SMS client should be just like any other GUI client out there, just text based. I should be able to type “help” and have it give me a list of commands I can type to make it do what I want. Part of that client could be to include #hashtags and @intended’s to specify meta information about the message, but those should be part of the additional 20 characters SMS gives me outside of the 140 Characters microblogging requires. All of the same goes for XMPP. XMPP could provide an even richer experience since it isn’t bound by the 160 character limit SMS gives people. For a great example, see Dustin Sallings‘ Track XMPP clients for both Twitter and Identi.ca (Identi.ca is real time!). Type help to his client and it gives you a whole list of things you can do with it. I’m sure this could easily be expanded further to allow tagging, person tagging, and more.

Twitter and Identi.ca’s announcements supporting linking of replies via the API last week is a very welcome announcement. With just a few more tweaks I think we’re on our way to a much cleaner microblogging environment that is even more searchable, more focused on content, and definitely more organized. For now I’m stuck using ‘@’ and #hashtags.

You can follow me on identi.ca at http://identi.ca/jessestay or FriendFeed at http://friendfeed.com/jessestay.

I broke news last night on LouisGray.com about Twitter enabling a new API feature, “in_reply_to_status_id”, to allow developers to tie replies to their original reply source. Immediately afterwards Evan Prodromou of Identi.ca added the same functionality to the Laconi.ca source code, making two of the most popular microblogging platforms, Twitter and Identi.ca, along with the already supporting FriendFeed, supportive of threaded comments. Immediately we saw Dave Winer implement a proof of concept example, and YooPlace also implemented it into their own code. Loic Le Meur of Seesmic, the owners of the Twhirl Twitter client responded as well saying he was reading the article and looking into it.

So a big question has become evident now that we can threaded replies. Is the ‘@’ really necessary in your replies to friends on your favorite microblogging service any more? A comment by Steve Gillmor on Identi.ca got me thinking about this earlier, and I think he has a strong point. In fact, I’ve briefly touched the subject before here.

The ‘@’ is mostly a Twitter-invented custom brought to the service by its users with some slight roots in bulletin boards and forums where threading was not possible. Users decided the Twitter service made a great communications tool and began replying to their friends’ posted statuses with the ‘@’ symbol. There was no other way because Twitter wasn’t expecting to be a communications tool. The popular Twitter clients like Twhirl and TweetDeck and even Twitter’s own web-based client started catching on, and separating those posts with usernames prepended by ‘@’ as “replies”. What’s odd is that the only thing they recognize as a reply is if the username is prepended by an ‘@’ - they take no thought as to the actual username itself, which really is the actual substance of who the user was replying to. In fact, FriendFeed users are starting to do this as well since it only has one level of threading and users can’t comment on other users’ comments. (Twitter and Identi.ca are actually one-upping Friendfeed with their recent announcements)

So while the “@”’s were a custom, they really aren’t necessary to determine if a user is replying to another user. In fact, even today you can use an XMPP tracker like Twitter Spy and Laconica Spy and track your username and get notified when a person mentions your username, exactly the way “@” replies work. It was silly that the “@”’s were required to be recognized as a reply in the first place.

Now, considering you can now actually track on the back end the entire hierarchy of a conversation via the API “@”’s are even less necessary as before. I’d like to see the various microblogging clients start to ignore the “@”’s and allow users to simply type usernames when replying to another individual, assuming threads aren’t in place. Then, once threads start to show in your favorite microblogging clients, even the usernames shouldn’t be necessary.

I’ve mentioned before that IRC works this way and most IRC clients will look at the existing list of users in a room and automatically detect the username and notify the targeted user if the message is directed at that user. Not only that, but the IRC clients actually keep a cached version of the users in a particular room and will even auto-complete usernames if you begin typing in the username and hit “tab”. That’s what I’d like to start seeing microblogging clients do so long as they’re going to be supporting a communications platform, and it should start with Twitter and Identi.ca themselves on their own web interfaces.

Then again, all this may now be moot with threading available. Oh, and don’t even get me started on hashtags. (Those should be handled by the API, not in the content of the message!) I think I’m going to try a new experiment of just not using the “@”’s like Steve Gillmor does - anyone else want to join me?

There’s a new kid in town in the microblogging space, and no it’s not just “another microblogging site”. I talked to Brian Hendrickson, the lead developer behind OpenMicroblogger.org and its accompanying service OpenMicroblogger.com today and he may just have something to scare both Twitter, and Evan Prodromou of Identi.ca in their tracks. What’s amazing about it all is Brian has actually taken the OpenMicroBlogging protocol that Evan established and implemented the protocol in Brian’s own, non-laconica-based implementation of the protocol that would communicate with any other OpenMicroblogging protocol supported site, similar to the way I mentioned on LouisGray earlier. Yes, OpenMicroblogger.com and the accompanying open source software it is based on will talk to Identi.ca, and on a completely different code base. That means you can follow anyone on Identi.ca within the OpenMicroblogger.com service and vice-versa, and they were written from the ground up by two entirely different developers!

What’s even more amazing about this new platform is that while not a Wordpress implementation, Brian seems to have made the platform almost entirely compatible with the Wordpress plugin and theme API. So, basically, if you are a Wordpress developer, you can write your own extensions to the code, implement your own versions of the code, and write your own themes, all in the same way you do on Wordpress. Brian wrote the code from the ground up using a framework he built and calls “dbscript”, and it contains no Wordpress code whatsoever. He felt Wordpress was too bulky to handle a full Microblogging platform (do I smell a potential acquisition by Automattic?). In fact, adding in integration with the OpenMicroBlogging Protocol was as simple as just adding a simple PHP plugin to his dbscript implementaion. The look and feel of OpenMicroblogger.com, his own implementation of the codebase, is all just an implementation of the Wordpress Prologue theme that my friend Joseph Scott at Automattic wrote.

Brian tells me that while Laconi.ca’s codebase is very good technology (he had very good things to say about Identi.ca, Evan, and the Laconi.ca codebase, especially when compared to Twitter), the technology underneath OpenMicroblogger and DBScript is even stronger and more scalable. According to him, “dbscript is an advanced ‘Restful’ framework with sophisticated features that are not found in the Wordpress code base, it shares features with Ruby on Rails (ruby) and Django (python) — things like MVC, ActiveRecord, Routes, Content-Negotiation”. Because the underlying code is Restful, an API is almost inheritently provided for other developers to interact with your implementation of the code-base and write their own applications for it.

OpenMicroblogger and DBScript are based on an open source MIT license similar to the license Ruby is under. Brian says it took him just 8 weeks to write this advanced implementation, with other client projects going on at the same time and 2 kids, which shows how simple it is to implement the Openmicroblogging Protocol. It also shows his devotion to the work.

OpenMicroblogger.com, the service that shows off his code, has some really nice features (also available in the code) such as sharing links and pictures with friends - definitely a little more advanced than Identi.ca in that manner. He fully supports the OpenID standard (he actually wrote his own OpenID host using his framework!), and is very big on OAuth and other standards and open protocols so you can expect to see much more around that with the site.

This one simple and amazing example goes to show that we have only hit the tip of the iceberg here on microblogging technology. Now that a Protocol has been established, you will see more and more sites and developers write their own extensions of the protocol to implement their own creative microblogging solutions and layers. This very creative and innovative solution could just be a more advanced option than Laconi.ca to consider for Microbranded solutions in the future. Brian has taken “viral coding” to heart.

You can download the code, try out, learn more and help out the OpenMicroblogger.org project over at http://openmicroblogger.org. I’ve created an account at http://openmicroblogger.com/?jessestay, and you can actually just go there, follow me, and follow my OpenMicroBlogger.com updates right on Identi.ca! Or, you can go over and create an account for yourself.

UPDATE: Brian corrected me about it being more scalable than Laconi.ca (see the comments below) - according to him, “Actually Laconi.ca is the more robust code and is more scalable. dbscript is a meta-object framework and runs some extra queries to “learn” about the db schema — it is currently not very optimized for performance, but is geared towards being programmer-friendly.”

Yesterday I guest-posted on LouisGray.com about how the technology behind Identi.ca, Laconi.ca, could pose as the launching platform to brand many smaller microblogging services. Today I’d like to share one more power of the service - its working API. Identi.ca/Laconi.ca seem to have introduced a new ideology to Web 2.0 with this code, viral software.

Now, when I mention “viral software”, I’m not necessarily mentioning software that can make things viral. I’m instead meaning software in which the underlying code itself is viral. This could change the face of the way developers write code in the future, and open source is only part of it.

Today I noticed (through Steve Gillmor on identi.ca) another new interesting thing that I knew was coming - Brad Williams (@williamsba) wrote a bridge that essentially allows you to post on identi.ca and have it automatically post to Twitter, prepended by “identi.ca:”. Interestingly enough, “Hippy Steve” (@exador23) pointed out now one of the top trends on Twitter as of today, according to http://search.twitter.com is “identi”. Now, many of the posts you see on Twitter are going to become posts prepended by “identi.ca:”, and many more are going to feel pressured to join identi.ca where they are seeing all their other friends post from. I guess you could consider it competitive micro-advertising, created and distributed on purpose by the users themselves (as Charlene and Josh would put it, we’re seeing a “Groundswell“).

It should be noted that you can remove the “Identi.ca:” from being prepended, but as long as you’re on identi.ca and want those on Twitter to know you’re posting from there and not Twitter, why remove it? You are posting from the competing team, after all. Would anyone want to pretend they’re not posting from Twitter? I’d like to know where my friends are posting from.

Now, onto the viral part. Why did Brad Williams implement this bridge? I’m sure there are preferential issues of trying to get his network onto identi.ca, but the fact of the matter is, from a development standpoint these applications like Brad William’s bridge are simply easier to write for Identi.ca. The lack of limits and plan to keep off those limits on Identi.ca are just one more thing that make the software behind Identi.ca viral. Developers want to develop for Identi.ca. With an API that also supports Twitter (I mean literally, it is simply a change in the hostname for your Twitter code), developing for Identi.ca is just too easy! Again, developers jumping ship could very well mean the demise for Twitter.

I can only hope that developers of the future learn from this experience - in a social era such as today, even your software has to remain viral and easily shareable and distributable. Laconi.ca is the prime example of this - completely open source, based on open protocols, and your software should be able to talk to other instances of itself in some way, preferably using standard protocols. In addition to that, a completely open API is a must - the minute you start closing your API you begin to lose your code’s virality. Brad William’s bridge is only the start of apps that make the transition to Identi.ca much easier. I imagine you’ll see many more of these things in the coming days and weeks.

Looking to learn more on how to make the jump to identi.ca? Check out my friend, Marina Martin’s site, ohidentica.com for some great howtos and tips all in one place. You can find me at http://identi.ca/jessestay.

O’Reilly just published a great interview with me on their FYI blog. If you want to learn why my book, FBML Essentials is important to you as a Facebook developer or business looking to develop Facebook applications, you should check it out. At the end, Mary Rotman announced a competition that could get you a free copy of my book, straight from O’Reilly.

Here’s the deal: regardless of whether you’re a Facebook developer or not, all you need is an idea. Let’s consider this the pre-cursor to getting your fbFund money — I’ll show you how to get started making the app, fbFund will fund the way. Simply go to O’Reilly’s FYI post and enter in the comments the application you would build (or are building) and how it’s different from the rest of the hundreds of Facebook applications out there. The best one or two ideas get a free copy of FBML Essentials - bring it to the next Social Media conference that I’m at and I’ll even sign it for you! How cool is that???

My good friend, Scott Lemon, made me aware of an interesting project underway that appears to possibly have been the inspiration behind Laconi.ca, the open source software behind the service, Identi.ca. The project is called “Fire Signal“, and is the brain child of Ron Whitman, the developer behind the Twitter Traffic alerts site, Commuter Feed.

Fire Signal appears to be a set of standards set out to encourage micro-blogging platform developers to build their systems in an open, distributed way. Identi.ca states that they are building off of Laconi.ca which is based on the “Open Microblogging Protocol“. Zenji Open Projects (Ron Whitman’s set of open standards) calls this protocol, “Fire Signal”. According to the Zenji Open Projects wiki,

“Fire Signal is an open protocol designed to allow users to publish and send short public and private messages of 160 characters or less across distributed web-based networks of Fire Signal Servers, the second initiative of this project. The concept behind this is commonly known by the term “micro-blogging”, popularized primarily by the web service Twitter and a growing number of competitors. ”

According to the diagram presented on the same page, the concept looks amazingly like the concepts behind laconi.ca, with multiple content servers all sharing data between each other. I see no links to code on the project (it seems to be a standard only, similar to the micro blogging protocol identi.ca references), and Ron Whitman seems to be the only contributor, but the site does claim that laconi.ca is a working example of Fire Signal Server. It’s interesting that the laconi.ca website and openmicroblogging website make no mention of Fire Signal Server, nor does identi.ca.

It’s hard to tell if this was the origin of Laconi.ca or not, or if several ideas all began at once, and ended up having the majority of efforts focused towards the laconi.ca project, but if it is the inspiration, Ron Whitman deserves a lot more credit for his contribution now that identi.ca seems to be taking off by storm. If not, this does seem like an excellent new project to help out with - I hope the two projects could work together. I’m interested to find out more about the origins of this and how it relates to laconi.ca - this concept is truly the future of micro-blogging!

You can find me on identi.ca at http://identi.ca/jessestay, or follow all my updates throughout the web and discuss on http://friendfeed.com/jessestay.

UPDATE: Per Evan Prodromou, founder of identi.ca, and the Laconi.ca project, the two projects are indeed separate. Hopefully Ron Whitman can take his great ideas and contribute with the Laconi.ca cause now. It’s nice to see lots of great minds wanting such a standard!

Yesterday I announced I am permanently and officially on hiatus from Twitter. Bloggers and other Twitter users, while annoyed, are giving them too much attention in both the negative and positive forms, and frankly, both of these only help Twitter. Any publicity is good publicity, especially when it comes to Twitter. I’m fed up with their lack of communication with users (try to talk to @ev or @biz - I rarely ever get a response to them, while many other companies on their own service I get an instant response from), their lack of experience and poor architecture that keeps causing these problems. It seems, while they are trying to get better, they just keep getting worse!

Just Wednesday, Twitter, while not on purpose, removed mine, and others’ followers in some sort of mistake that took a day to fix (I’m guessing someone erased too much data in the database via a bad query on live data, and they had to restore from Tape backup to get it all back). This hit the breaking point for me - they violated the most important thing to me about Twitter, my followers (which are also those I follow and have a deep interest in), and I just can’t trust that things like this won’t keep happening in the future. They crossed the line, whether on purpose or not, and it’s time for me to take action.

I’ve endured them being down in times I needed them most. I’ve endured them removing API features from us developers with little to no notice. I’ve endured them launching things into production without telling developers or warning users. I’ve endured their lack of a proper staging environment and other simple architectural issues that they still have yet to fix (I’m still not convinced they’re not developing in their production environment!). I’ve endured their lack of a proper and regular launch schedule to warn other developers and users when new features and bug fixes are being launched into place. I’ve frankly, been too patient with them and I’m fed up with it.

Unfortunately, after only one day I realized I could not do it cold-Turkey. I have a good number of followers on Twitter that have some interest in me (and I thank you so much for that support - it really means a lot to me), and regardless of whether I want to leave or not, abandoning Twitter would mean abandoning those followers, and I just can’t do that to all of you. To me, you’re not just a number - you’re all people interested in me in some way, and I follow each of you back because of that (and will continue to do so). I do care about you, and need to do what I can to encourage you to join me in more productive, more reliable and trustworthy sources however. Here’s what I’m going to do:

I’m going to post much more on Identi.ca

My followers from Twitter are already very quickly joining the open source communications and micro-blogging service, Identi.ca. I use identi.ca with Twhirl and have it open at the same time I have Twitter and FriendFeed open. I will be posting to identi.ca much more often - follow me there so you don’t miss anything!

Why identi.ca? Distributed or not distributed (some argue it isn’t, which they have a point), identi.ca is open source. This means I, as a developer, can actually have some sort of chance at giving back if things ever go wrong. Everything’s plain, simple, and out in the open. I know Evan, the identi.ca founder, has also been very open with the community and has maintained that communication. I don’t get that from Twitter, at least not on an individual level. Also, identi.ca, like Twitter, now imports to FriendFeed, and now satisfies my status updating needs to initiate conversation (which is what FriendFeed satisfies).

I’m going to be much more involved on FriendFeed

On Wednesday at F8 I realized something significant - I was using FriendFeed as my primary communication mechanism throughout the day, and I really wasn’t missing Twitter much by doing so (and most of it from my cell phone). FriendFeed, frankly, is much more viral and advantageous to my blog and brand than Twitter because every time anyone likes or comments on an item I post or comment on, that item goes right back to the top of the feeds for all my friends. It brings instant exposure, and in fact, for many posts on this blog I get more traffic on FriendFeed than Google, Twitter, or any other service out there. FriendFeed takes power away from the A-listers and puts it right back in your hands - it can happen to you too, and very easily!

Some people, for whatever reason, won’t give up Twitter

As long as the majority of my followers remain on Twitter and don’t join FriendFeed or Identi.ca, I still have an obligation to you, and frankly, I’m outvoted at the moment until the scale tips. I’ll still follow your Tweets on Twitter, respond to your @replies, and direct messages, assuming you’re not already on the other services. You gave me your attention and I need to continue to give you mine. For the most part, my blog posts will keep posting there (although they are also on FriendFeed - discuss below!). Please don’t hesitate to contact me - I respect you having your own opinion. I hope this post can convince you otherwise however.

SocialToo.com still lives! It has to.

The fact of the matter is, there is still a large audience using Twitter and frankly, there’s a business opportunity there as long as people are still there. I built SocialToo.com to work across many social networks, and as you switch, so will SocialToo.com. For now though, there’s an opportunity, and Twitter will still be a part of that opportunity, as will Identi.ca, Facebook, and even FriendFeed in the future. It is already powering hundreds of Twitter accounts helping you follow those that are also interested in you and I have no intention in giving that up. If I can do my part in making Twitter a better place, I’ll at least try, so long as they let me. I’ve actually got a really cool new feature that will be released soon for both Twitter and Identi.ca.

I will not give Twitter any more attention!

I’ve given Twitter too much attention, both positive and negative already. We as bloggers, if we’re frustrated with the service, need to take a stand, and my hiatus starts with blogging about Twitter, and that happens right now, cold-turkey. This, unless Twitter does something absolutely profound, will be my last post about Twitter.

How Twitter can get me back

Twitter needs to do something profound - they need to show they have the experience necessary to protect those that follow and are interested in me. Twitter needs to open up more - let us into what you’re doing. Allow other services to sync with my updates in a federated, open manner. Open your source code like identi.ca. Any one or two of these will do, but, frankly, I’ve been disappointed too many times. Twitter has to gain my trust back, if some other service doesn’t beat them to it. Show your support by joining me on Identi.ca at:

http://identi.ca/jessestay

Or, more importantly, join me at FriendFeed at:

http://friendfeed.com/jessestay

I hope to see more of you there!

On the heels of a post this morning by Biz Stone, it appears Twitter is beginning to bring the rate limit for posts through the Twitter API back to the 70 per hour it used to be. For the last several months, Twitter has brought that limit down to only 20 requests per hour. Per the Twitter developers mailing list just now, Twitter has now raised that limit to 40, and will gradually be raising it back up to 70 in the upcoming week.

This is welcome news in the week of months of API and service outages. What this means is that you, as the user will no longer see the “Rate Limit Exceeded” error you may be seeing through clients like Twhirl. In regards to the API this leaves mainly just the XMPP stream that they need to re-enable for developers - this may not be happening any time soon however, as Twitter may be looking to only enable a select few developers access to the stream.

Has this request limit affected you as a developer? How about as a user?

Those of you in the Facebook Group or Google group have already received notice about this but I just realized I hadn’t blogged about it yet. Tomorrow we have a great Facebook Developers Garage planned here in Salt Lake City. Facebook has sent us a professional copy of the DVD of the Palo Alto Facebook Developers Garage that I was able to attend in May, so we’re going to watch that, and then go over some of the new changes that are coming into play for the new Facebook design.

This should be a great event if your a developer or even non-techie, as it will help you see some of the integration points you can build into with the new design. A lot will be changing with the new Facebook design, so if you are currently, or are planning to build a Facebook application, either as a developer or in a marketing or business position, you’ll definitely want to attend. This is a completely open event so please invite your friends! All I ask is that you RSVP here.

We are still looking for someone that can provide food for the event so if your company would like some great exposure in front of possibly 20-30 developers and Facebook-interested people, please contact me! In the meantime, the event will be hosted at EPIC Ventures in downtown Salt Lake City and they will be providing snacks and drinks for all that attend. I’d like to thank them personally for hosting the event - they are doing this after hosting our food for last month’s event!

All in all, this should be a fun event as all of them are. If for some reason you can’t attend, our next meeting will be September 9th from 7pm to 10pm so put that on your calendar! I’ll look forward to seeing you all there!

Here’s a map to EPIC Ventures - it has been recommended that you park in the Joseph Smith Memorial Building parking lot across the street. I’m told they can provide vouchers for that. Also, if you arrive late a phone number will be posted on the door of the Zions building for Rachel Strate - please call that number and we’ll let you in!:

Epic Ventures
One South Main St, 8th floor
Salt Lake City, UT 84111

Today I was introduced to a new service called identi.ca, which claims to provide Twitter-like functionality, in a nice, Open Source interface. The service implements the OpenMicroBlogging protocol which, from their FAQs, states, “you can have friends on other microblogging services
that can receive your notices.” This means complete transparency and no reliance on any one service to trust your data with. I am unable to find any other services that have utilized this protocol, however.

The service seems to maintain an open atmosphere across the board. They publish all the details of the code identi.ca is based on, stating they run on the Open Source microblogging platform, Laconica. They state that “soon” they plan to implement SMS updates and notifications, a Twitter-compatible API, Maps, Cross-posting to Twitter, Pownce, Jaiku, etc., Facebook integration, Hashtags, Image, video, audio notices, and even a multilingual interface. Relying on the open source community, on an open standards-based platform may just put them in direct competition with Twitter very soon.

All of your updates posted to the service are under the Creative Commons Attribution 3.0 license and you have to agree to this when you sign up. They seem to remain open across the board - and this will make them successful. I have talked previously about how the mistake Twitter is making is that they are not open enough - they are not basing their protocols on open standards and open techniques of web development. It is showing now, as they are stuck fixing their own problems as the world watches. With a service like this, were it to go down, ideally other services would also sync data and you would not be without service when one service goes down. This is powerful!

The founder of identi.ca is ironically named Evan - they seem to be going head-to-head with Twitter in an Open platform. Based on my experience with open standards in the past, I can already tell which one has the strongest potential. They state to have 1,000 users already and are growing very fast (in Evan’s words). I look forward to seeing them grow, and hopefully contributing as I can - will you join me? You can find me at http://identi.ca/jessestay.

With all the frustration lately about Twitter going down, disabling features, and developers leaving the service, people still keep coming back for some reason. Frankly, there just isn’t anything that can fully replace Twitter. I think people have simply gotten so used to Twitter and have figured out their own ways to use the service, that moving to a new service and spending time adopting new ways of organizing communication is just too much for most people. Bring in FriendFeed - now, I know I have said previously that FriendFeed is not a competitor to Twitter, but they are getting closer and closer to being a reasonable alternative every day. At the same time, FriendFeed is just more stable and encourages conversation in ways that Twitter just can’t (especially when @replies are down!). I’d like to share with you a few ways that you can use FriendFeed to kick that Twitter habit, and utilize the full power of FriendFeed at the same time.

Not on FriendFeed yet? Sign up and see what you’re missing!

Joining is the first step. Be sure you have given it all of your favorite Social Networks, and especially your Twitter credentials. Don’t be overwhelmed though - the tips I’m about to give you will help ease some of that frustration, and most importantly, try it out for a little, give it a chance like you did Twitter, and you’ll begin to see why it’s so powerful. Remember that when you joined Twitter it didn’t make much sense at first either. It took getting in and using it for awhile before you were able to realize how powerful it actually was.

Find all your Twitter friends that are on FriendFeed and add them

One of my biggest worries of moving to another service from Twitter is abandoning the near 900 people following me. For some of you this number is much smaller, and therefore should be a little easier to migrate. There is a nice little program by Eric at InternetDuctTape (click on the link to get it yourself!) that searches through all your Twitter contacts, and then using the Google Social Graph API, identifies which of those are on FriendFeed. Run this now (sorry, Windows only - I ran mine on Parallels), and it will automatically send friend requests to all of your Twitter friends that are currently on FriendFeed.

This is only the first step to migrating your Twitter network over to FriendFeed and using the service on its own. Only those Twitter friends that are already on FriendFeed will be able to see your updates (you can actually post updates via the “share” button in FriendFeed), but now you can tell those other Twitter friends to come follow you on FriendFeed if they want to continue receiving your updates and join the conversation. The advantage FriendFeed gives you is that for every update and/or link posted to the service, users can actually have a discussion underneath that link as a community instead of guessing what it is they are talking about.

I fully expect someone to write a script (maybe socialtoo.com?) that will automatically post your “shares” on FriendFeed out to your Twitter account, with a link back to FriendFeed to discuss the shared post eventually. Look to see that soon, and all your posts can now be on FriendFeed with no worries of abandoning your Twitter network.

Get an imaginary friend (or two or three)

FriendFeed supports the concept of “Imaginary Friends” for all of those you follow on Twitter and other services that aren’t on FriendFeed. Simply click on the “friend settings” tab in the upper-right of FriendFeed, then click “imaginary” in the navigation. Click on “Create an imaginary friend”, and follow the instructions to create a name for that friend and what network they belong to. Now, those friends’ updates will appear in your list of other friends’ updates on FriendFeed, and you won’t miss a thing!

Reply to your friends’ Twitter statuses via FriendFeed

Now that you have all your Twitter friends in FriendFeed, on any post they make, you can reply, directly from FriendFeed! On any Twitter post, click on “Comment”, then comment and check “Also send this comment as an @reply twitter from (your username)”. Now, when you post your comment, not only will it appear under that user’s Twitter post in FriendFeed for other FriendFeed members to discuss, but it will also send an @reply to Twitter itself so the conversation continues on Twitter as well! I only suggest using this for those Twitter friends that are not on FriendFeed, because, hey - you’re trying to give up Twitter, aren’t you?

Get very familiar with FriendFeed mobile

Just today FriendFeed announced a new iPhone version of its service. The new design is very intuitive and easy to navigate, and I can only imagine will get better over time! The coolest feature is a link to their built-in ability to send photos to FriendFeed that you take on your cell phone. If you send any photo to yourusername+your_api_key@mail2ff.com it will automatically post it to FriendFeed for others to discuss and talk about. The iPhone version gives you the e-mail address you need to send to, but you can also get your api key via https://friendfeed.com/account/api if you don’t have an iPhone.

The other service to check out if you don’t have an iPhone is fftogo.com. FFtoGo.com gives a nice, mobile-formatted version of FriendFeed to your cell phone. Up until today I was using this, and it works very well at viewing what your friends are posting and discussing, what you’re posting and discussing, and who is discussing on the things you post.

Install the FriendFeed Comments Plugin for your blog

Okay, there’s really nothing in Twitter that compares with this or can compare with this, but it does demonstrate the power of FriendFeed. The FriendFeed comments plugin enables you as a blogger to allow your readers to comment to the blog post right on FriendFeed, and read what is being said on FriendFeed, right on your blog! It also shows who has liked it, and lets your users like it right from your blog. Ideally, you could really remove the current comments on your blog and completely replace it with this. You can see this in action right below this blog post above the Disqus comments by clicking the “show” link next to “Join the Discussion on FriendFeed”. Comment there and then go to FriendFeed and check it out!

RSS, RSS, RSS! — Learn to organize your FriendFeed data

Almost every page on FriendFeed has an associated RSS feed with it. Someone asked me today why Summize doesn’t support FriendFeed - that’s because FriendFeed has Summize functionality built into it! Open any page in FriendFeed, then scroll all the way down to the bottom, and click on one of the links next to “other ways to read this feed”. You can have new items on that page sent to your RSS Reader, Facebook, Google Reader or iGoogle, or even e-mail!

This has power. One way I use Twitter is I follow all those that follow me (using socialtoo.com), but I send all those I really need to pay attention to, and that are most interesting to my cell phone via SMS. FriendFeed doesn’t support SMS, but it does have another way to send you new updates of a particular user. Simply click on any username in FriendFeed (or just go to http://friendfeed.com/username or http://friendfeed.com/username/discussion if you want all of their likes and comments as well), and now all of their posts will be delivered to you via RSS! Add to this the power of Google Reader on your Cell phone and you have a superb way of staying up to date on the discussion of the most interesting people you follow.

One other way to utilize this is through the search box on the right of FriendFeed. Type in any text in the search box that you want to “track” (note that track is currently broken on Twitter), add the resulting page to your RSS Reader, and now all found discussions with that term contained (for instance, your brand, or your competitor’s brand) will be delivered automatically to your RSS Reader. This is powerful!

Use Twhirl for all the rest!

Now that you’re paying attention to all of the most interesting people you are following, you’ve brought over all those you can from Twitter, you’re tracking the terms you want, and you’ve integrated FriendFeed commenting onto your blog, you may want to skim over all the rest.

While the FriendFeed UI should be sufficient, Twhirl is an unbelievable tool for general FriendFeed use. From Twhirl you can skim over all of your friends’ posts and comment and discuss on the interesting posts, or just watch all of the posts you have sent to FriendFeed along with anything you have liked or commented on. If you click on the “Me” tab and “like” the interesting posts of your friends, you can then track the conversations that go on within each of those posts that you “like”.

USE the service!

The most important advice I can give to any Twitter user looking to move over to FriendFeed is to use the service! More people will talk about your posts, more people will “like” your posts, and your experience and conversation will get much better the more you use the service. If you just use it as an aggregator and don’t “like” or comment it will still be an interesting tool, but it just can’t replace Twitter until you start using it.

In the meantime, come follow me on FriendFeed at http://friendfeed.com/jessestay. Join the discussion below! I think you’ll start seeing me much more over there, and much less on Twitter as we all begin to utilize the full functionality of FriendFeed. Let’s just face it - we’re all getting tired of this Twitter downtime!

UPDATE: Sasha Kovaliov made the point (on FriendFeed) that I had the fftogo.com link wrong (I had it as ff2go.com). Thanks for the correction, and I’ve corrected it now.

This is a picture of my very first computer. It was my very first glimpse into the world of Microsoft that would soon bring interest to the brilliant career as a software developer that I am now able to fulfill. That computer, an IBM PC compatible (of some sort), is what matured my experience as a developer. I remember the days of MS Dos before we even had color and windowing systems, and this computer even booted to BASIC! I remember my Dad getting a pirated copy of Microsoft Windows version 1 on 5″ floppies (as we were living in Indonesia at the time and this was all you could get out there), and trying it out, thinking there was no way he’d ever want to use a system like that. If you notice in the picture, we didn’t even have a mouse! The closest input device was the Joystick you see, which I used to play ironically, my first glimpses of the Microsoft Brand, in the game, Flight Simulator. Back then, Microsoft was simply just another brand you saw on a piece of software. Next to the likes of Broderbund, Activision, Lotus, and Wordperfect, Microsoft was just another software manufacturer that you saw alongside the likes of games and DOS.

Over the years, we began to see the gradual creeping of Microsoft into our daily lives. My first notices of Microsoft after the gaming and DOS days that I can remember would probably be the emergence of Microsoft Office, which, ironically, would not work on the computer I picture above. I had to wait to get a new computer before I could use it at home. Most of my memories of that came from Junior High School lab computers. It was actually rare back then for students to have a computer at home, yet alone one with a Word Processor!

At some point, we ended up installing Windows 3.1. I think it was the beginning of High School. It was there that I learned what a driver was and how hard it was to get any external hardware to really work with Windows 3.1. I really gained an appreciation of DOS in those days and learned how to write my own Batch files, configure my autoexec.bat and config.sys files to get everything I needed working properly. Frankly, back then there wasn’t much to get working properly. 3.5″ floppies were the new thing, few computers had sound cards, and there was no such thing as a CD ROM drive (at least not that we could afford!).

In High School, I remember getting a summer job my Senior Year at Computer City, a Tandy company, the company that also owned Radio Shack. While there, Windows 95 launched, and I remember trying to explain to customers the differences between Windows 95 and OS 2 Warp. We also sold Mac machines and Apple software in our stores back then! I remember beta testing Windows 95 with my friend and remembering all the cool new features it brought over Windows 3.1, and thinking it was so weird I didn’t have to install DOS before installing Windows 95!

I ended up going from there to work in Tech Support for Gateway computers. It was at that time that Microsoft Bob came out and I was forced to support it. I can’t tell you the number of times I remember just encouraging users to format and reinstall - it was actually standard protocol for the company back then!

Not long after that, Windows 98 came out, and shortly before I remember the IE/Netscape wars, the Novell Wordperfect/Microsoft Office wars (that was right here in Utah!), and somehow Microsoft continued to prevail. I think it was at that time I began to use Microsoft Office over Wordperfect products regularly for the first time. It was my only choice!

When Windows 2000 came out I remember how stable it was! Finally, a version of the Microsoft OS that the average Joe could use, based on Enterprise technology! (NTFS) I think it was at that point that I started seeing Microsoft as “evil”, and began venturing towards Open Source and other technologies to break free of the Microsoft trenches. It was also at that time that Netscape was no longer the dominant browser and web developers were very quickly forced to change their ways.

Since then we’ve seen Windows XP, Windows Vista, Windows Me (choke!), Xbox 360, MSN, Windows Live, Windows Media Center, and even Microsoft Surface! From games and DOS to programmable furniture, Microsoft has come a long way over the years. Yet, one man has stood at the center of it all, a quiet, but very, very, rich man, Bill Gates. He has been the quiet identity behind Microsoft for probably most of my life. Friday, Bill Gates had his last day at Microsoft. He has brought me many great years, and much of the reason I am a developer today. As he leaves I feel a piece of me bidding farewell, yet, at the same time, that company that I have both loved and hated over the years will still continue on in his legacy. Mr. Gates, thanks for the Memories!

I’m going to dub this Part 2 of my Twitter Love/Hate fest - this should be my last installment for awhile on this topic, I hope. In reality, I really love Twitter. I have a good network on Twitter and frankly, I wouldn’t have met many of you if it weren’t for Twitter. Twitter, in many ways, has changed my career. For that reason I really don’t want to see it fail. It is perhaps this reason that I am so critical of it at times - it’s my hope that someone at Twitter can read these and at least see what the world is really thinking, hoping, and wishing at a given point in time about how their service is performing and being perceived.

Twitter is still continuing to fail developers!

It’s examples like the one I learned about recently where the service, Gridjit, was put offline entirely because of a rash decision on Twitter’s part to remove a feature from Twitter’s API with little to no notice for the developers to respond. In the time Gridjit was down, they have since added FriendFeed support, and I’m willing to bet they have other strategies that don’t include Twitter. Now that Twitter has re-enabled that feature, they are now back up and running, but Gridjit is just another example of the frustration that is occurring amongst developers in the Twitter development community.

Just today, for example, I noticed Twhirl was no longer working with @replies. I remember seeing posts on the Twitter blog recently stating that the @replies tab would be removed, but I remember no notice to developers stating that the features that enable this on clients like Twhirl would be disabled in the API (they did let us know the API was down today though - still no notice it would be down when they took down the replies tab, and nothing to the developer mailing list that I’m aware of).

Twitter tries, but not quite enough

I mentioned last week that Twitter was hiring on their site, but it just wasn’t enough because I think the problems they have exist at the management level. True, they even hired 3 new individuals recently, but they are developers used to being managed, not managing large groups of other developers. Twitter really needs one or two individuals at the top that have true Enterprise-level experience managing these types of IT issues, and very large groups of developers. Remember, Twitter isn’t just the developers that work for Twitter, but the vast group of developers that are also writing applications for their API. The individual in charge of development and IT efforts at Twitter has to have strong experience in managing very large development teams, and working with a very large user-base, in which any change to any part of the system could effect. Twitter needs a staging environment in place, and a system of testing every single change that goes into place before it actually goes out live into the production environment.

They are showing some promise though!

Just this week Twitter announced the inclusion of 2 new investment partners in their list of investors. One of those, Jeff Bezos, does have experience managing the types of issues and large development audiences that Twitter lacks. This is a huge move for Twitter, and long overdue! Jeff will bring Amazon’s firm experience in scalable web environments, and I hope, enable Twitter to enter the cloud more than they currently are, and reduce the tough scaling issues they are experiencing right now.

You can bet you’ll see Twitter begin adopting Amazon’s AWS Cloud services here soon now that Bezos is on board. Amazon has the capability to scale almost instantly as traffic spikes hit, and they seem to be doing it better than any other right now. Twitter really needs this service!

Why I think they’ll still survive, no matter how many developers leave

Twitter is a Marketer’s Paradise. Twitter is full of content about the every-day life of millions of individuals and their friends, who they connect and communicate with, and what their frustrations and interests are. Businesses are beginning to embrace this and use services such as Summize to track information about their Brand, their image, and even their competitors that they could never track before. Businesses can finally track real people instead of just “visitors”.

This is powerful and valuable information to many businesses out there. Because of this it doesn’t matter how many times Twitter goes down or how many developers stay or go from Twitter. So long as users still have networks on Twitter and the Twitter user-base continues to rise as it appears to still be doing, businesses like H&R Block and Comcast and even NASA will still flock to Twitter as a valuable tool in gathering data about their customers and fans. These businesses have it in their best interest to see Twitter succeed, and you better bet they’ll do their best to help out in that effort. Twitter isn’t going anywhere my friends, and I still haven’t retracted from that statement.

This morning Justin R. Young of TalkingHeadTV interviewed me via webcam (couldn’t figure out how to get rid of the yellow whitebalance on my webcam - I’m really not that yellow!), and asked some great questions in follow up to my article mentioning my concern on developers leaving Twitter. I think we covered a lot of the criticizing articles‘ (they were only somewhat critical, fortunately) issues in the interview. I wish we recorded the entire discussion because some of the best conversation occurred after the cameras were rolling.

To sum up, I’m not necessarily anti-Twitter. I’m as big a fan, if not more than any regarding Twitter - in fact, in the interview you can see I even wore my Twitter shirt that Ev and Biz gave me! I actually wore it all day yesterday, and was proud to show it off. I’m just worried with what I’m seeing and hearing from Twitter developers, and I want to be sure Twitter knows this so hopefully, they can come up with some way to fix it. My hope is they are already doing this, and they say they are. Here are the highlights of the interview:

Why Are Developers Leaving Twitter?

Despite Outages, Complaints Why Does Twitter Still Thrive?

How Do We Know When Twitter Is Dying?

I’ve been following various development mailing lists lately, and I’m seeing a trend of developers starting to bail on Twitter. This is a scary thought, because when the developers bail, so will the users. It all started with a conversation on the Twitter Developers’ mailing list with the subject, “Shame” by a developer named, “nath“, in which he said,

“Well, twitters always down or unusable due to the speed; the api’s
keep breaking and are down just as often; the groups now packed full
of spam which is littering my inbox.

“It’s a real shame to see such a great app crumble and die like this :(”

Alex Payne, a developer for Twitter, responded by saying,

We own Twitter’s speed a stability; my our metrics, it’s been pretty
solid over the last few days.

We do not, however, own spam prevention for this group. That’s up to
Google, and if it’s a hard problem for them, I’d imagine it’d be a
hard problem for anyone.

I go through and clear out spammy posts, but time they reach my inbox,
they’ve reached everyone else’s as well. There’s just not much I can
do about it. Please make use of Google’s “report as spam” features.

After which another developer that goes by “rlansky” responded:

Sorry, but I have to agree with the original author, it is a shame
that the service and the API are so unreliable. The potential for the
services that could be built on an API like the one offered by twitter
are endless. They really are.

Statements like this:

> my our metrics, it’s been pretty solid over the last few days.

don’t do much to boost my confidence. When you make an API available,
you are essentially saying to the world, “here’s our service, come and
build something great on top of it.” You can’t build anything of any
real value or widespread use on something that “has been *pretty
solid* over the last couple days (emphasis mine) .” You just can’t.
You need something that is rock solid all the time.

I’m not trying to start a flame war or bash twitter at all. Like I
said, I think it is a shame because the potential is so great. The
idea is great, the acceptance is great, the use is great, the
possibilities are awesome. But they just can’t be fulfilled given the
reliability of the service as it is today; try to build something on
top of the API that will see wide-spread use and you’ll find that when
you push the gas, the wheels fall off the car… at least that’s been
my experience. It’s been *extremely* frustrating and disappointing.

Peace.

After following a few threads on the Perl development library for Twitter, Net::Twitter, I recently found out that Net::Twitter’s original maintainer too has jumped ship. He has handed it over to a new maintainer, but developments like this are not a good sign for Twitter! It is very clear that frustration amongst Twitter developers has hit a maximum level and I fully expect to see this only increase in the short term.

At the same time, developers like Kee Hinckley are giving advice to Twitter, and they are graciously accepting it seems. Some great tips are being given on ways to enhance the API, and I even suggested they do a public bug tracker which they seemed to like. Twitter clearly doesn’t seem to have enough expertise in-house, although they do keep saying they are hiring. Their jobs page doesn’t seem to have any upper-management positions though which I think is really what they need right now.

I’m very worried for Twitter. As more developers jump ship and work on other platforms such as Plurk and FriendFeed (which really isn’t a direct competitor to Twitter), this great tool is going to be left in the dust with no new development and large networks of people moving elsewhere. Twitter’s largest traffic comes from the API itself, and as that traffic dies down, so will Twitter. Imagine, for instance, if Seesmic were to stop development on Twhirl due to the costs associated with keeping up with API flaws? That would be quite a chunk of Twitter’s users being forced over to the other Twhirl clients, FriendFeed and Seesmic itself - it’s such an easy transition were Twitter support to be dropped! What happens when Twhirl begins supporting Plurk?

Twitter needs to do something, and they need to do it fast. I agree they need to get their infrastructure in place, but before even doing that they really need to put every hack possible in place to keep the API up, keep it working, and work with the developers to ensure they are staying happy. A large revolution is about to take place, and I’m afraid it won’t be pretty.

UPDATE: See the little FriendFeed box below? Click “show” and join the discussion on FriendFeed about this right on my blog! Subscribe to my updates here.

“Is your Father also Jesse Stay?”

I can’t tell you how many times in my life I have heard those words when introducing myself. Whether I was registering for school, going to church, a Boy Scout, or even half-way around the world or in multiple states in the US, it seems there was always someone that knew my Grandpa, had some story to tell about how he influenced their lives, and what a great man he was. Despite the name, they, of course weren’t referring to me, but rather my name sake, my Grandfather, Colonel (President, Bishop, and Patriarch) Jesse Eldred Stay.

Talking about his life would take an entire book to publish (you can read in detail about him here - it really is worth reading!) - he was, quite simply, a great man, and I mean great in the very sincere and large/tall sense of the word. I remember one family telling me when they met me about how he helped bring them back to Church and changing their lives as they did so. I remember stories from other families of him helping them in times of need, fixing their cars, helping them with home repairs, and more. Everywhere I have gone in life, my Grandfather’s name was recognized and honored by many. There is a very good chance some of you, my readers, have had some brush with him over your own lives.

Grandpa was a War Hero. In World War II he was a B-24 bomber pilot in the 307th, 11th, and 42nd Bomb Groups for the United States Army Air Corps (there was no air force back then, but he soon became part of the Air Force after World War II). He flew many missions, risking his life, getting shot at and shooting back, so that you and I could maintain our freedom in this world. He was a true believer and maintainer of freedom.

At the highlight of his career (if you can really call World War II a “highlight” - I know he wouldn’t), he earned two Distinguished Flying Crosses, one for flying over Wake Island (he also flew over earlier at only the second time Wake Island was bombed by the US) despite most of his squadron being shot down. He literally saved the world with his own bare hands. Of the 40+ missions he flew in World War II, with five airplanes flying at his wing going down, he was only hit once, with one small 7.7mm hole in the bottom of his plane on a raid on Wake Island. In a letter to my Grandmother during the War, he shares this story:

“I found out that this ship (his airplane) will stand up, with any luck at all, against any number of Zeros. I also found out a very fine thing about the men in this outfit. As we were leaving our target in the raid, we heard one fellow say over the radio that his ship had been crippled and that he had been forced to fall behind. Naturally that meant that all the Zeros in the sky would be on him; so we turned around to give him some help. As we turned, we saw a wonderful sight. Every ship in the flight had the same plan. They had turned as one ship and soon we had the crippled ship tucked among us where we could protect him with our converging fire. I don’t believe that I will ever forget that. Every plane, without command, had turned back into the fight to help this one fellow out of a tough spot.”

These words show the integrity of this man and devotion he had to those he was fighting with. He would have done this for any one of his fellow squadron members.

Also notable, of his War accomplishments, it was one of his suggestions that led to the first recorded parachute landing. From his words:

Finally my wing man, 1st lt. Charles Pratte, had to leave also and headed for Tarawa to re-fuel. He had over three hundred holes in his airplane but didn’t have one man wounded. On one pass the Japanese machine guns had stitched holes the length of his fuselage and had blown up the oxygen tanks which had knocked down the two waist gunners in time for the machine gun bullets to pass through the fuselage where they had been standing. I later found out that his hydraulic system was also shot out and he landed at the new strip at Tarawa with parachutes tied to the waist and tail guns and which the crew men deployed as they touched down to slow the airplane because they had no brakes. We had talked about this possibility before but the crew of the Belle of Texas received a commendation from General Hap Arnold, Chief of Staff of the Army Air Corps for making the first recorded parachute landing.

Since then, every time I see a Space Shuttle land, I think of him as having had a contributing factor in allowing man to fly and come back from Outer Space.

It was said of him in his Squadron History,

“The greatest loss to the squadron was that of the Commanding Officer, Captain Jesse E. Stay. Captain Stay was with the squadron for nearly two years, beginning in April 1943, and was C.O. longer than any other man in the squadron’s history. He took part in practically every mission flown by the squadron since its arrival in Guam, either actually or in their preparation. He received the D.F.C. from Admiral Nimitz for his leadership in the highly successful but disastrous Wake raid in July 1943.

“As flight leader, he flew against the Marshalls, Gilberts, and Nauru, from the Ellice Islands. In his capacity as commander he accepted the mining project, which others had turned down, and led the unit to a superb record in its execution.

“Capt. Stay was missed by the members of the squadron who remained behind to carry on.” (p.35)

In his entire career he received 2 Distinguished Flying Crosses and 8 Air Medals for his service in the War. He sacrificed his all so that he could win freedom for this Country and many others.

It wasn’t just Grandpa’s military service that made him honorable. While he went on and did many things in the military, including putting an end to the United States Air Force UFO investigation program (which, to this day he still says, and I’ve asked him frequently, that they found no evidence of such), being on 24 hour notice with engines on during the Cold War, and being the first Colonel over the BYU Air Force ROTC, his Church service and devotion to God were paramount to his life. Throughout his life, as a member of the Church of Jesus Christ of Latter-day Saints, he served as a Bishop, Stake President, Regional Representative (over the L.A. area), Mission President, member of the General Sunday School Presidency (with Elder Russell M. Nelson, now an LDS Church Apostle) for the LDS Church, a member of the Los Angeles LDS Temple Presidency, Sealer, and Patriarch. His devotion to God came first, and as a member of The Church of Jesus Christ of Latter-day Saints, never ever drank a sip of Alcohol, never drank a sip of Coffee or Tea, remained faithful to his wife and 7 children, and served faithfully in his Church assignments with no pay for his service. He was also a Scout Master, and during his service in the Boy Scouts received the Silver Beaver Award. He touched the lives of many during his life of Service.

It was in Hawaii, when my Grandpa was head of Public Affairs for the LDS Church College there (now BYU Hawaii), that Judge Whitaker, a long-time friend of my Grandfather’s, invited him during the shoot of “Johnny Lingo” to come and serve as his Assistant Director of Motion Picture Production at the BYU Motion Picture Studios. My Grandfather packed up his family and moved back to Utah, and under the direction of Ernest Wilkinson (also longtime friend) and LDS Church President and Prophet, Spencer W. Kimball, produced and directed such shows as “The First Vision”, “Uncle Ben”, “The Gift”, “The Mail Box”, “John Baker’s Last Race”, and even the famous talk by Spencer W. Kimball asking members to “Lengthen [their] Stride” and “Go Ye into All the World” (Many LDS Church members may be familiar with these).

He recalled an experience with President Kimball which, to me shows the love and respect that even LDS Church leaders had of him:

“This morning I was called up to Salt Lake City to show the film “Where Jesus Walked” to President Kimball for his approval. The showing was to be in the fifth floor auditorium of the Church Administration Building. This is the room where the Council of the Twelve hold their regular meetings. I arrived early and had the film ready on the projector and was sitting alone in the room. President Kimball and Arthur Haycock, his secretary, arrived a few minutes before the scheduled time for the showing. President Kimball came over to me and took my hand in both of his. He looked up at me and smiled and told me how happy he was to see me. He then put both of his arms around me in a warm embrace and told me that he loved me. I was thrilled and touched and told him that I loved him and sustained him with all of my heart. This was no maudlin moment but the sincere expression of love between two bearers of the Priesthood. The Lord has surely preserved him for his holy calling as President of the Church and His Prophet on the earth. I am blessed to be associated with him. I know that I am nothing special to him above other men but he has the ability to make each person he meets feel that he loves him more than anyone else in the world. I felt this was a special moment worth recording.”

Through the Church movies he Directed and Produced, he also touched many lives, in and out of the LDS Church.

My Grandfather, Jesse Eldred Stay, died peacefully this morning at 7:13 am. I would not pay proper respect to him if I didn’t embrace this moment in celebration of his life, his accomplishments. At the same time I look forward to the future when he and I, and his family of 7 children, 50 Grandchildren, and numerous Great-Grandchildren, what he would consider to be his greatest life accomplishment, can be with him again. Grandpa was a Sealer in the Los Angeles temple of the LDS Church. As a sealer, he married and sealed me and my wife together like he did most of his children and grandchildren, for what we believe to be, time, but not just time - all eternity beyond this life. While I have my 3 month old son, Jesse Eldred Stay III, to continue this legacy in this life after me, my Grandfather’s greatest accomplishment is giving us hope, and knowledge that we, as a family, can be with him and each other again when we pass away, and always be able to cherish and respect the example that he gave to us here in this life. Seth Godin recently asked people to point out, celebrate, and respect the Superheroes in our lives. My Grandfather is my Superhero! He truly was a real-life Super-man. I have had the privilege to have known him longer than any other man, other than my Dad, in this life and it is my honor. It is with this respect, hope, and faith, that I honor, love, and thank him, for the life, both mortal and eternal, that he gave us.

Just yesterday, Facebook announced their second F8 conference, to occur July 23, 2008. This Developer-targeted event is said to possibly include some major announcements, including the new Profile redesign, more information about the fbOpen platform, and most significantly, possibly the launch of their E-Commerce platform. What hasn’t been announced or shared however is the odd timing of the event.

The event occurs right smack dab in the middle of O’Reilly’s Open Source Convention, scheduled to occur for about the past year now from July 21 through July 25. This conference is known as an essential “Mecca” for Open Source developers around the globe, and has presentations from such players as Google, MySQL, Sun, Meebo, and even SixApart. Everyone who is a developer (unless you solely develop for Microsoft) or Sysadmin will be at this conference.

As a developer, this is tough news to hear that Facebook will make me choose between OSCON and them. Frankly, I would by default choose OSCON if I were any smart developer, as I would get more. So why isn’t Facebook just joining OSCON and doing an “F8″ track there? Do they really want to tick off Open Source developers? You better bet that OpenSocial will have a presence there. If Facebook really wanted to target the Open Source crowd, as they have “claimed” to do with their fbOpen Platform and a few other contributions back to the community, they would try to have a presence at this conference and not interrupt it as they are currently doing. I was actually going to go to OSCON to promote my FBML Essentials book to potential Facebook developers for O’Reilly. Now I’m forced with a decision. I’ve contacted Facebook with no response, and I’m getting a little frustrated as a Social Media developer. Which conference will you choose?

Facebook appears to have just launched a previously announced feature to their new design staging area. If you go there you’ll notice a new little “+” sign next to the tabs at the top. Click on this, and now you can choose to add “Posted Items” to the tabs at the top, as well as “Find more applications”. The “Find more applications” feature does not seem to be working yet.

This new feature allowing you to add applications to the tabs menu in the new design was announced previously by Facebook, and is said to allow your application, through just a simple “tab url” in your application settings to appear in the drop-down you can see there now when you click on the “+” sign next to the tabs. This is also consistent with the removal of “adding” an application by Facebook. Instead, you will be able to add “components” of your application to different areas of a user’s profile, which includes the tabs. Your application can have only one tab and works passively by default, meaning you have to click on something for javascript or Flash to auto-play. Nothing has been confirmed on whether Advertisements will be allowed to run within the Tabs on the new design. The tab also defaults to your Application name and cuts off at 15 characters.

See below for some more examples of the new “+” sign, and adding the Posted Items application to the tabs menu in the new design:

As the first entry to my Social Coding series I’m going to cover Google’s Social Graph API. I saw a demo of this at Google I/O in San Francisco and was so impressed that I immediately started hacking on it when I got home. Little did I know how powerful this API was and how much information it could pull off the web about a single individual!

Google’s Social Graph API takes a cache of the rich storage of links, information, and URLs on Google’s servers, and determines which of those contain information about actual people. It combines OpenID for confirming an individual’s identity, and XFN and FOAF XML protocols to determine links between those identities. With a simple <link/> tag on a user’s website, a user can determine other websites that also identify them. If you link to one URL identifying that location as you, and at the linked website, it links back to you, Google can tell for sure both of those websites are yours, and identify you as a person. Not only that, but you can similarly provide XFN information or FOAF information via similar <link/> tags or a separately linked file identifying who your friends are. If they link back to you via similar metadata Google can tell for sure that the two of you are friends.

The Social Graph API lives and breaths this data. There are actually quite a few Social networks that use this protocol to identify you and your friends. Sites like Digg, Twitter, and FriendFeed all utilize these protocols to identify your friends. The Google Social Graph API scans this data and organizes it in an easy way for you, as a developer, to access.

Let’s try a simple example, and you don’t even have to be a developer to try it. Google has provided a simple playground to see how the Social Graph API works. If you go to http://socialgraph-resources.googlecode.com/svn/trunk/samples/exploreapi.html, enter in a few URLs of your blogs, social networking profiles, and other identifying locations on the web, leave “Follow ‘me’ Links”, “Pretty Output” checked, and click, “Find connections”. For me, just “twitter.com/jessestay” was all I needed to enter in the textarea.

The resulting structure is organized in a format called JSON - if you’re a Perl developer you might be familiar with this, as it is formatted the same way as a Perl Hash structure. You’ll see under “nodes” a bunch of URLs with different metadata about the URL - these are URLs that Google thinks, based on the metadata in the URL you provided, are you or contain info about you. I’ve found that only those with a “profile” attribute are actual Social Network profiles for yourself, so be sure to pay attention to those.

You can also go back and click “show inbound links” and “show outbound links” - this will then return URLs with links to sites you have identified as yourself, as well as sites you own that claim other sites as identifying for you. Play around with it - there’s a wealth of information it will give you about people!

Now, if you’re not a developer, you can skip over this next section because I’m going to get technical by showing an example. I’m a Perl developer so I’ll show one in Perl.

In Perl it’s simple - you need to install Net::SocialGraph with a command similar to this:

perl -MCPAN -e “install Net::SocialGraph”

Then, a bit of code like this will give you the data you need:

my $sg = Net::SocialGraph->new(’fme’ => 1);

my @urls = ();
push (@urls,’http://twitter.com/jessestay’);
push (@urls,’http://facebook.com/profile.php?id=683545112′);

my $res = $sg->get(@urls);
my @profiles = ();
foreach my $node (keys %{$res->{’nodes’}}) {
  if ($res->{’nodes’}->{$node}->{’attributes’}->{’profile’}) {
    push (@profiles, $res->{’nodes’}->{$node}->{’attributes’}->{’profile’});
  }
}

In the above example I instanciate my $sg object, telling it to follow “me” attributes in the response. I add a couple URLs to identify the individual I want profile information for (in this case, me), and then make the call to the SocialGraph API to go get my info based on those URLs with the “get” method provided by the API. Then, I just traverse the response and I can do whatever I want with it. After this, I could take the response information and list all of the user’s profiles as links, or perhaps I could scan those profiles for more information and provide information about each identified profile. You’ll also note that it’s not always correct so you’ll want to let the user intervene. Also, note I’m looking for only links with a “profile” attribute - I’ve found these to be most accurate.

Beyond that, that’s it. Ideally, you could take the Playground example above and look at the resulting URL. The basics of the Social Graph API are just that URL - plug in whatever you want and you’ll get back whatever information you need. You could then parse it with Javascript, Perl, PHP, or just leave it in the “pretty” format the Playground provides you by default.

Now, imagine taking that data and combining it with, say the Twitter API to pull out all of an individual’s friends on Twitter, then applying the Social Graph API to each of those individuals. Soon, you have a tool which can identify which of a user’s friends are on which networks, and if there are any of your friends you have not yet added on those networks. This API is powerful!

The Social Graph API can be an excellent utility to find out more information about any individual using your applications. No longer do you have to ask the individual for that information - so long as they are active on Web 2.0 that information can be provided for them to choose from!

You can learn more about the Social Graph API here.

Please note I too am new to this API - any inaccuracies in this document please let me know in the comments and I will correct them for others to benefit.

How did I get to spend a day with Robert Scoble? How did I get to participate in the interview with Twitter founders, Evan Williams and Biz Stone, that ended up on the front page of TechCrunch? I joined the discussion on FriendFeed.

I think some would probably consider me a Twitter power user. I think Twitter is great for posting updates, getting conversations going, and seeing what your friends and followers are up to. However, FriendFeed is where the true conversation is at. With threaded conversations, the ability to “like” and share items, it provides a much stronger catalyst for conversation that Twitter could never provide.

How do I use it? Well, I actually thought it was too cluttered at first. I am finding as I use it more I am coming up with my own ways to better organize my conversations and keep track of what is going on. First of all, I use the “Me” tab religiously. I often also click the “see both” link (just add “/discussion” after your username when on the “Me” tab) on the right sidebar to see not only the things I have posted and the discussions within, but also the things I have “liked”, and commented on. This allows me to keep track of the existing conversations I have entered.

Then, I skim the “friends” tab to see the interesting things others are posting (If you have over 100 friends, there’s no way you’ll be able to read it all like you do in Google Reader or some do on Twitter). I find as I join other conversations and like and comment on others’ posted items it shows them I have an interest in the things they too are interested in, and true friendships get nurtured from these conversations. Then, if you want a mobile solution, I use http://fftogo.com to read FriendFeed on my mobile phone (a internet plan for your phone is required, but if you haven’t signed up for one of those yet you’re still in 2007! ). It formats FriendFeed in a nice, easy-to-read browser format so you can track things in the same way you do on your computer. You can send photos to yourusername-yourapikey@friendfeed.com from your cell phone.

FriendFeed is not Twitter. Twitter is hard to replace in what it gives me. I will still use Twitter to post status and other items to get the discussion going, but I will now begin using FriendFeed to continue that discussion. Will you join me on FriendFeed? Subscribe to my updates at http://friendfeed.com/jessestay. You can see what I’m discussing at http://friendfeed.com/jessestay/discussion.

Pay attention - Google is onto something big, something that could very well change the world, and no, it’s not OpenSocial or App Engine or Android. One of the biggest overlooked items in the last several days has been an announcement by Google to release an API for their Google Health service. I’ve mentioned before that Google Health is one of the single biggest threats to the Healthcare Industry since the establishment of company-paid Health Insurance (well, maybe not in those words, but that’s what I meant).

The Google Health API does two things, for the most part. It allows a developer to retrieve medical profiles stored in Google, and format them as a “Continuity of Care Document”, a standard in the HealthCare Industry for sending HealthCare history information and data from HealthCare provider to HealthCare provider (a provider would be your doctor, or a hospital, or dentist). This allows your doctor’s systems that are already familiar with this system to easily read your history and process it accordingly so your doctor can read it.

Secondly, it allows you to send profile information from your own systems into Google Health. Through a simple post to Google’s servers, you can send history information via XML and it will get stored in Google’s servers. So, as a doctor you can hire a developer like me, and we’ll parse the information from your systems, and your customers can simply use their Google login to access not only the information you stored about their visit, but their entire history from previous doctors.

This is the start of something beautiful. Previously in order to send and receive medical data, it required a firm knowledge of pages and pages of HIPAA documents to know and understand, and at the same time know how to get the information, which could be in many different formats into, and out of your systems as a doctor. Now, Google is providing a single source, and a standard for developers to understand that will allow any developer to transfer data into, and out of a single source into your systems. Now you only have to know one standard as a Doctor and you can have that patient’s entire medical history with the push of a button. Google knows the standards so you don’t have to.

Google is in the position to take this much further. As the single destination source for consumers, they have the power to control standards, track payments, health issues, and more, and provide a single standard to do all this. I wouldn’t be sleeping very well right now if I were a HealthCare company. Google is in a position to take the power out of their hands and put it back in the consumer’s. Google is about to change the world of Healthcare as we know it.

Nick O’Neill blogged about it, and Facebook confirmed it officially at the Palo Alto 1 Year Anniversary Developers Garage on Thursday, but Facebook has finally released their platform under a modified version of the Mozilla Public License. The code and announcement can be found here, and includes the full API, a parser for FBML, and more. I will probably be trying to sneak in a little info about this in FBML Essentials if I can beat it to press.

What does this mean for you? Well, first of all, there is a good chance (I have not confirmed this) you’ll now see sites like Myspace and LinkedIn also join sites like Bebo in providing a Facebook-style API. It should be an easy decision for them. This also means you are not stuck porting your Apps over to OpenSocial to get them on those networks, assuming they implement this into their own architecture. Ideally, it will take very few changes to port a Facebook App over to other FbPlatform-enabled sites.

Also, if you are building your own social network, you can now cater to all the Facebook developers out there and bring in the rich API Facebook provides. OpenSocial is great, but you do have to keep in mind it is still in beta - while new, I see no “beta” put in front of this new Facebook Open Platform.

The other thing you should take into account is that because it is Open Source, you can now contribute back to the platform. If you see something in the platform that is strongly needed, you simply have to sign the Contribution Agreement they provide and if they implement your change they’ll even send you a (drum roll please) T-Shirt! (they didn’t say if the T-Shirt was free or not) In reality though, we as developers now have some responsibility to give back to Facebook - that is the essence of Open Source.

I think Facebook just played their cards for Google on this one. Their environment is still closed, but at the very least they are sharing the components that make their closed environment so the world too can get involved. Google now has much stronger pressure to get OpenSocial in order, and in a way that convinces the Facebook platform developers to use OpenSocial instead of the Facebook Open Platform. It’s a race for developers, and I’m afraid Facebook just made the choice for developers to leap to OpenSocial a lot harder.

I saw some very concerning issues on the Twitter development list today, and my frustration has only been increased after reading some of the claims of Blaine Cooke today on TechCrunch. Yesterday, the one thing that seemed evident, and perhaps I’m wrong on this, but Ev Williams and Biz Stone do not seem to have much of a technical background. They made this clear in the interview, and there’s nothing wrong with this, assuming they have the technical staff to handle it.

Today on the Twitter development mailing list something was made apparent - experienced developers and businesses on the Twitter development mailing list cannot trust the architecture of the API that runs on Twitter. Just yesterday, a crucial feature of the API which allowed the retrieval of an individual’s friends and all of those friends’ timelines was removed from the Twitter API.

About 1 week ago, Alex Payne, the developer Biz and Ev kept referring to in the interview yesterday as having a lead role in the development, announced on the developer mailing list that this feature was going to be removed and asked if anyone was using it. With only about 5% of the applications saying they needed it, Twitter removed the method Thursday with just a notification on the developer mailing list and about 8 hours notice, no other notification elsewhere or warning that it was happening at that point.

All of the sudden, application developers everywhere were saying they couldn’t run their applications because of this change. These were applications such as Hahlo, Twitterati, Twibble, and Gridjit. What’s the issue here?

The issue is Twitter isn’t communicating effectively. We addressed this yesterday - I think they realize it, but I want to reiterate it. I can’t help but wonder if the experience is even there to be able to communicate effectively. I’ve worked as a developer in several publicly traded companies, one of them a Fortune 40, and some of the decisions the Twitter development staff have made would have gotten me fired at previous employers I have worked for. Where is the experience, and how can I, as a business and developer using Twitter trust them to build something on top of? I want to see where the experience is before I build any more on top of the Twitter API - does the Twitter staff have LinkedIn profiles?

Now, I’m not trying to criticize any individual at Twitter - I want to think they have the experience necessary to handle this, but I’d prefer they not pull the wool over our eyes if there is not enough experience at Twitter to handle the API I am trying to build a business off of. I know for a fact there are many smarter people using the API that could help analyze the experience if they need that help, but we need Twitter to communicate with us and let us help them out. Because businesses are being built on the API we want to see them succeed (I’m writing this as I wear my “Wearing my Twitter Shirt” I got from them yesterday). I think, as they said in the interview yesterday, while it could take months to get things in place, we, as businesses and developers could help them out if they just let us and communicate properly with us.

The questions I asked yesterday were centered around the developer and how we could help them. They told us to communicate with them. I really don’t know how we can communicate effectively with Twitter if they can’t be open to us back. I even posted this on the mailing list this morning, and received absolutely no response. As a Twitter API developer and business owner, I don’t know how much longer I can keep my Apps on Twitter. I know many others share the same frustration, and once the Apps begin leaving, so will the users.

I think, and hope, based on the interview yesterday, that Twitter understands this. I’m optimistic they do. However, we need an open communication channel, consolidated, and the experience to know how to manage that channel effectively with the API, or new opportunities are going to arise very quickly wich developers will leave to.

UPDATE: It appears that Twitter has a pretty experienced crew, per their recent blog post. Again, you still have to keep in mind that it may take time to fix the problems that are already there - is it worth the wait?

Today I had a very unique opportunity to in many ways get in the middle of the Twitter Fiasco, the VentureBeat article suggesting that Robert Scoble was the reason for Twitter’s failures, and Robert’s response to it. It was an amazing experience that I will never forget, and before I start I want to thank Robert for bringing me along to be able to participate and hear all of this, first hand (and still getting me back to the airport in time). Robert Scoble’s such an amazing guy and no one could ever tell me otherwise - I wish all could meet him in person, hang out with him, etc. like I was able to do today.

Originally Robert and I were just going to go up to the Disqus new offices and see the founders, Daniel Ha and Jason Yan (they said they are readers of this blog!). However, today around lunch he called and said we were going to make a pit stop at the Twitter offices in South Park. I was told they had made an offer to him (and he was happy to accept) to come by and chat about the recent blog posts and frustration between the two.

When we got to Twitter I was actually quite impressed by the professionalism of Ev and Biz at Twitter, along with Robert as they discussed the matter. There was some nervousness on both parts I could tell, but after the cards were laid out on the table and both sides understood, I think both felt a little better about the situation. In the end, here’s what I got out of the conversation (which you can view via Robert’s Qik stream here):

• There is still a long way to go before Twitter will have a fully functional product - they are in the process of re-architecting it all so they can scale further as it grows further.
• It does seem they’re still trying to work with it to make the existing system work with what they have.
• The problems they are having are NOT because of big “whale” (and I doubt the picture on Twitter’s error page was meant to reflect this) users such as Robert Scoble or Michael Arrington.
• The problems they are having are very much due to problems with their current architecture, and in particular the way their API is currently set up to handle. Their system was built as a prototype and ended up becoming the product.
• There is no good immediate solution to this. As they remove API features, applications like Twhirl and TweetScan, and other 3rd party applications with thousands of users will fail, and thus the users will complain and leave. They simply can’t punish the developers as a whole because it would end up offending their users as well.
• There are still some pretty smart people at Twitter and I really think they know what they’re doing - they’re just stuck between a rock and a hard spot because they designed their architecture wrong.

The most interesting thing for me, and should be for developers as well, IMO, came at the end however, and I think it’s a smart move the faster they can implement it. Twitter is looking into the possibility of having a better way of tracking the Applications developers write on the Twitter API. By doing such, they can first of all put an end to spammy applications that are abusing the system and killing their traffic with too many unnecessary requests (similar to the way Facebook does with notification limits), but secondly they can begin to organize the Applications and provide a centralized directory for all the Twitter applications out there.

I recorded this video to get Robert’s thoughts on the interview afterwards - I think he shares the same feelings as I do:

Getting Robert Scoble’s Thoughts After the Twitter Interview from Jesse Stay on Vimeo.

You can also see some more of my thoughts afterwards, although I think I was still processing it after we were done so I didn’t say much. You can see that on Robert’s Qik stream here.

In all, I think while there’s still a long way for Twitter to get everything worked out, what they said to us was very promising. It’s promising, yet frustrating at the same time because I know it may still be some time. They are willing to accept help and ideas. If you are a developer and want to offer your time to help them out, join their mailing list, offer your assistance in any way. Most of all, as was pointed out, if you’re going to do any heavy hitting on their API, let’s talk to them the same way they’re talking to us now. Let’s build an open communication between the developers and the Twitter dev team themselves and I think perhaps we can all work together to make Twitter an even better place than it was before.

I’m going to talk a little more about my trip to the Bay area in another post coming up. I feel like I visited half the Web 2.0 internet, in person, in a matter of 3 days, and I’m still processing it all. The Bay is an amazing place that you just have to see for yourself to believe. Now Robert - my offer still stands if you ever want to come out to Salt Lake and have me show you around next time!

I don’t know if it’s the horrible logistics at yesterday’s keynote and that I had to sit on the floor to watch it, or the T-Shirts that in binary say, “GoogleKO” (Mike, I’ll give you mine if you have lunch with me tomorrow), or maybe the fact that I now can’t get internet connectivity as I write this due to the poor planning for WiFi in this room. Or maybe it’s that I’m presenting on Facebook and have had Facebook on the mind the time I’ve been here, but I’ve really been on an anti-Google run lately and I’m not sure why.

The biggest thing I’ve noticed here at Google I/O is there is absolutely no presence of Jaiku at the event. I haven’t seen any booths, presenters are not running it up on the screens like we saw with Twitter at Web 2.0, and it almost seems as though Google doesn’t care that there is an opportunity with the problems Twitter is having right now. In fact, I think I’ve even seen Twitter on a few of the presenters boxes rather than Jaiku.

Does Google just not care about Jaiku? They have an amazing opportunity here. Twitter is down about one half of the time. They are hosting a blog on their competitor, Tumblr’s, site because they can’t trust their own servers by all means! I don’t agree that FriendFeed is a competitor to Twitter - Jaiku is, however, and now is the time for them to step up! Google has a conference with attendance that perhaps exceeds that of Web 2.0, and the whole world watching them as they make some serious announcements, so I can’t figure out why they aren’t taking this opportunity to gain an edge on their competitors.

Jaiku is perhaps the only other service out there with an SMS status update system similar to Twitter’s. People really want to find another solution that solves what Twitter gives them. Jaiku does this, and Google is failing seriously at promoting it and bringing attention to it at this conference.

I mentioned earlier that we were working on a Fund for Phil Burns’ daughter, Serenity, and would post information about it today. Well, we have a bank account set up, but unfortunately the fund will take a little bit to get going. However, I’m going to set a new goal for the Chipin widget.

I’m proud to announce that the Chipin Widget for Serenity and the Burns’ family is, as of this writing (and in just 2 days!), at $1,506.97. There seems to be some issue with the Widget updating on mine and others’ blogs, but I’ve got a support request to get that fixed. We’re going to raise the goal for the Chipin Widget to $10,000 by the end of this Saturday. If you can donate, just a few dollars, help promote this, and maybe even Digg it up, your efforts are sincerely appreciated. Any little effort is a step towards Serenity’s recovery.

In addition to the ChipIn widget, you may also go to any Wells Fargo branch (I think only in Utah), and make a donation to:

Serenity Burns Donation Account
Wells Fargo Bank

or you may send a Check to:

Serenity Burns Donation Acct.
224 S. Main St. #555
Springville, UT 84663

Of course, you can install the Chipin Widget on your own site by visiting here. Please feel free to set aside a little now, or the coming months ahead to help out this family. I estimate their costs for medical expenses alone will exceed $100,000 and we should do what we can to help them not have to worry about that and focus on getting Serenity better.

I’m also proud to announce, thanks to the Burns’ friend, Becky Wilson, the creation of a site just for Serenity. You can find it at http://liftingupserenity.com. Please leave a Guestbook post for her or the family, leave your wishes, see updates from Phil and Adria’s blogs, Twitter feeds, and the FriendFeed room. You can also donate there. If your business would like to promote this through sharing proceeds with the Burns family, we will be happy to include your promotion on the website as well.

We’re also creating an Amazon “wishlist” that you can purchase items for Serenity and the Burns’ Family. Please look for that soon on the liftingupserenity.com website.

So let’s all “Lift up Serenity” together and do what we can to promote this cause.

Tomorrow evening I’ll be heading off to Google I/O at the Moscone Center in San Francisco. I’m very excited to look over the various new technologies Google is offering, including OpenSocial, Google App Engine (keep an eye out for Bungee Labs, the competitor to App Engine - I hear they’re planning to make an appearance there), and hopefully I’ll get a first chance to play with Google FriendConnect. I’m hoping to take quite a bit back so I can apply it to the work I’m doing for Takes All Types to transition them over to OpenSocial.

While I’m out there, look out for me the next few nights. Tomorrow evening, probably late, I’ll be visiting the Wordpress 5th Anniversary at the Minna Gallery. That should be quite a fun event, and I look forward to meeting Matt Mullenweg and crew again. Then, Wednesday night, be sure to come out to the Silicon Valley Web Builders meeting, where I’ll be speaking to about 100-150 developers and such with an interest in Facebook and Social Media development. There, I’ll be speaking about a few tags you probably weren’t aware of in FBML, and we’ll go over some fun FBML facts, as well as discuss some of the latest news we’re seeing about Facebook lately. I also hear a local news reporter will be there, so the pressure is on. I’ll have a number of copies of my first book, “I’m On Facebook–Now What???” there for you to purchase, and I’m happy to autograph any copies you buy - if you haven’t yet RSVP’d please do so now!

The final event, Thursday night, is the Palo Alto Facebook Developers meeting. That meeting looks to be jam packed with developers, Facebook enthusiasts, and investors, from Jim Breyer, to Lee Lorenzen, to Justin Smith of InsideFacebook, to Dave Morin of Facebook, it seems anyone that has anything to do with Facebook will be there. They will be celebrating the 1 year platform anniversary, going over the new design and how that will affect developers. I anticipate some announcements out of that meeting, although I can’t say for sure.

So if your out in the area, stop by and say hi! I’m @jessestay on Twitter and FriendFeed - give me a holler and maybe we can go get some Thai or Seafood (my two favorite San Fran cuisines!) together. I look forward to seeing you all there!

I’ve created a ChipIn Widget that goes straight to the Burns‘ Paypal account, which you can donate to help them with their miscellaneous expenses over the next few days. I’ll also be adding it to the right-sidebar of this blog. Until the banks open, please feel free to donate what you can - I am sure they are very much in need of help with their miscellaneous day-to-day expenses while they are in the hospital, so they can focus on their daughter, Serenity and getting her better. You may also use this widget to promote donations on your own blog - I highly recommend you share with others! We’ll be getting a tax-deductible (hopefully) fund organized for the Burns’ family as soon as the banks open after the holidays. In the meantime, let’s see if we can raise just $500 in the next few days to help them out. Any donation is very much appreciated!

I’ve been contemplating for awhile now a good way to share what I know about Social Software Development and helping business owners, marketers, and developers learn how to set up their own social apps. Especially for developers, I know there are many out there looking for howtos and ways to learn more about starting their own App, promoting it, and getting it off the ground. As the author of FBML Essentials, I feel I am well suited for the task so in the next few days I’m going to start doing howtos and overviews on how you can get your own Apps together. If you’re “the business type”, I may get a little technical on you, but I do recommend you keep watching and forward these onto your IT personell - your CIO, CTO, and the like should read these so they can learn what’s possible to integrate into your existing environments. I’ll also try to throw in a little goodie here and there for “the business type”.

So, I’ve created a new category to the right, “Social Coding” - if you want to track just that, click on the category name and add it to your RSS. I’ve also started a new FriendFeed Room where those involved or that want to get involved in Social Coding can discuss, learn, and talk with each other. You can subscribe to that here.

Let’s start by going over the types of sites I could cover. Here are just a few - let me know if you have a particular interest in learning about how to code for any one in particular:

• Facebook
• OpenSocial
• Google Friend Connect
• Twitter
• FriendFeed
• Pligg
• Digg
• LinkedIn
• MySpace
• Wordpress
• MoveableType
• Google App Engine
• Bungee Connect

Stay tuned! I’ll keep posting news and other rants as we go forward - I’ll just be adding in some good howtos at the same time. Oh, and if you’re a developer and would like to do a howto in your preferred language for us, contact me - I’d love to let you do a guest post.

For those unaware, my old partner and good friend, Phil Burns (aka @phil801 on Twitter) just found out today that his daughter, Serenity, has Leukemia. She has been pricked, prodded, and the stories Phil and Adria tell are heart-breaking! Phil says (much of what I have learned has been through Twitter) that Serenity just got a transfusion and is feeling relatively better, if there is such a thing. She will start chemo in the next day or two. I’m still trying to get things organized - we’re working on a website to show support for her and raise money for the family, and I’ve had numerous Web 2.0-related organizations offer to dedicate funds in their name. The support and interest in helping has been amazing so far. For now my suggestion would be to contact Phil directly to donate money in the more immediate term - I will try to set up a fund as soon as we’re able to. There are many expenses that they are unable to avoid now and I’m sure they can use all the help they can get (they are checked into the hospital now, so I’m sure things like just paying for food at the hospital restaurants is much appreciated).

In the meantime, I’ve set up a FriendFeed Room here that even if you’re not on FriendFeed, you should be able to subscribe to via rss and get updates on the situation. I’m trying to share everything I see from Phil there, including his Twitter posts, blog posts, Adria (his wife)’s blog posts, and his Flickr photo uploads. If you are a member of FriendFeed feel free to leave your comments there or on his or his wife’s blogs, where they seem to be documenting the process.

For those unaware, my Grandmother died from Cancer, my Aunt is fighting it, and seems to be surviving it, and my Uncle died from Cancer. My Grandfather is a Cancer survivor. Things like this hit home for me. Phil says Serenity has the type of Leukemia that has an 80% survival rate (the “good” kind, as he puts it) - however we need to make it easy for them to focus on her and give her 100% of that 80% to survive! Please stay tuned and I’ll post more here as we get organized. If you’d like to help out in any way please let me know and we’ll find a way to put you to good use.

In the meantime, please blog, retweet, or share with all you can to send support and encouragement their way!

Today Twitter announced the creation of an official “twitter” account on Twitter. This update has been a long time coming - other companies are doing it - why hasn’t Twitter all this time?

I brought up multiple times on the Twitter developer mailing list that Twitter needs to add an official “Tom” of Twitter that people can follow and get official Twitter updates from. Such a user would allow Twitter to let users know why there was slowness in the service and post about new blog updates (I just learned that Twitter actually has 2 blogs - a company blog and a development blog).

It’s good to see Twitter adopting this practice - this is one way Twitter will be able to better manage their reputation and keep others informed of service outages and updates to the system. I just hope they have given this user priority over other updates on the service so it can get messages out during slow times.

You can follow the “twitter” user here.

UPDATE: I’ve since learned from the comments of that post that there is a “twitter_status” user as well - the difference of the two, I’m unsure. Care to share your thoughts?

I was made aware via Twitter of all places today that Kirk Yuhnke, a reporter for Utah’s Fox 13 News morning show, has joined Twitter. They did a feature about Twitter, demoing it for Dan and Kerri (couldn’t find a link to the Morning Show on MyFoxUtah!) and showing live on the air how it works. You can see the post he made on the air here.

Looking at his Tweets, it looks as though Kirk has been using Twitter for at least a few days - I am curious what introduced him to Twitter. Anyway, it’s very refreshing to see more Old Media reporters and news people embracing Twitter as a tool to both receive and report the news. I think Kirk will realize very fast that Twitter’s more than just an addicting little thing to report statuses on - Twitter’s “the world’s largest conversation” (I tweeted that - wish Twitter archived Tweets for longer), and because of that, you’re able to get into everyone’s lives, receive news as it happens, and report it as it happens.

Kirk, in case you happen to read, here are some tips I’d love to give you as a reporter that I think you’ll really enjoy:

• Follow @newmediajim. Jim Long, a camera man for NBC News’s Presidential detail is one of the early users of Twitter. He has reported while on trips to Iraq, world summits, and basically anywhere the President goes. You get the news, as it happens - he’s the essence of one reason Twitter is so popular.
• Today, type “track san diego explosion” into Twitter. Soon, if you have notifications turned on in your Twitter settings, you’ll be receiving new notifications either via your cell phone or IM (depending on your user preferences) on everyone living in San Diego talking about the explosion at the downtown Hilton in San Diego.
• Use Tweetscan. Go to http://tweetscan.com and search for recent news you are tracking - do a search for “wii fit” and find a record of everyone trying out the Wii Fit. Do a search for “KirkYuhnke” and find out about all the people like me that are talking about you. As a reporter, this will be invaluable to use!
• Add 40404 to your Cell Phone. Be sure to add 40404 and set the name to “Twitter” on your cell phone. Then send a message to that address book entry. Now, imagine you’re the reporter on the scene at midnight at a local explosion and Fox 13 News has decided to go off the air and report it in the morning (true story!). You can live-report the event, all via Twitter, and those viewers all yelling at their screen asking what the explosion was can get up-to-the-minute updates on the Explosion happening. Not just that, but those outside of Utah following you can find out what’s happening! (I had about 5 people from outside of Utah trying to come to me after the south provo plant explosion a few months ago wanting the latest news about it, and I had nothing to give them!)
• Check out Twhirl. As a big news reporter, everyone will want to follow you on Twitter, and you’ll be quite a popular guy, both in and out of Utah! Here’s what I do: I follow everyone that follows me (unless they are outright spammers) - this allows them to direct message me if they need to (Twitter only allows those you are following to DM you), and shows that I have an interest in them as well. It’s courtesy, in my opinion. Now, install Twhirl on your computer, and use that to skim through the messages of all those you follow - you don’t have to read every single one, but at least you’ll have a good overview of what’s happening in the world.

  Now, for those nearest and dearest to you that you want to follow and pay attention to, turn on notifications for those people. Leave notifications for all the others off. Now, all those that you want to pay attention to will go to either your cell phone or IM client (depending on your Twitter preferences), and you won’t miss any of the important stuff. I should also mention that with notifications turned on, both @replies and direct messages will go to either your cell phone or IM client as well. This ensures you get all the important stuff.

• Use SocialToo.com. Okay, this is a little shameless plug on my part, but it’s one of the only services of its kind out there. When you sign up at http://socialtoo.com/registration and provide your Twitter credentials, it will automatically start following those people that follow you, for you. Not just that, but you can blacklist users you don’t want it to follow, and even leave a message for new followers (that features actually slightly broken right now, but you get the point). This will allow you to use the technique I mention above.
• Check out my post on ways to change the world using Twitter. I track the term “earthquake” as one of the terms I track, and recently there was a 4.0+ earthquake in London. I started receiving an influx of Twitters from people experiencing that Earthquake before it was even reported on USGS! Robert Scoble also does this, and recently he reported about learning of the recent China Earthquake before even USGS reported. Twitter has power in this way.

So Kirk, I think I speak for all of Twitter when I say, “welcome to the conversation!” Keep talking - we’d love to see what we can do to help you out. Hey, maybe we’ll even invite you to a “Tweetup” some time.

For those that would like to follow Kirk, he goes by @kirkyuhnke on Twitter.

Those that know me know that my last job before I went out on my own as an entrepreneur was with UnitedHealth Group working in their EDI Services division. While I was there I was following the interest Google had in Health Care with great curiosity. UnitedHealth Group (UHG) had many products Google could compete with, and perhaps at a better level. Google for the moment lacks a good, targeted audience in which to tap into the vast advertising money that could be provided by Pharmaceuticals and other Medical industry players. There is huge money in these areas of advertising, and I’m sure Google sees this as an opportunity (see the previous link - Google is definitely thinking about Health advertising!) they haven’t yet tapped into.

Today, Google launched the beta of their new Google Health product. Google Health competes right alongside UnitedHealth’s “Personal Health Histories” that they have provided to their customers. It allows you to easily provide your login credentials to about 20-30 HealthCare and Pharmaceutical providers, and import information from those providers into your Google Health Account. Not only that, but you can manually track health conditions and history of Doctors visits, medicine you are taking, hospital trips, and more, all through a simple login through your Google authentication credentials. All relying on the vast resources of hosting facilities and System Administrators protecting your data which Google has capability to provide.

Starting with Personal Health Histories, Google has the potential to do what UnitedHealth Group and others have been doing, but on a much larger, and unified scale. I would be willing to guess that a large majority of the internet has a Google account of some sort right now - imagine the possibilities!

For instance, what if Google were to integrate Google Calendar support into their interface? You could begin, just by importing your current medications, to receive alerts via text message and Google Calendar, reminding you to take your medication. Or perhaps your Doctor could integrate with Google Health to provide you with reminders and calendar entries of future appointments, as well as remind you when a Physical is due.

We’re just getting started though - now let’s take into account what Google is really good at - search. The project I was in charge of at UnitedHealth Group involved matching records between payers (the insurance companies) and providers (the doctors), an art that, thanks to our great government and the many rules and regulation they have already put into place but don’t follow themselves (called HIPAA), proved quite difficult. Many Insurance companies are making money off of this disunity and flaws in our Government’s system. Imagine if Google were to get into this game and start adding their own indexing algorithms to your medical records. In essence, Google themselves could become a “Clearing House” (a term in the Health Industry for basically a proxy/interpreter between payers and providers), sifting through claims and payments, matching them, and showing your bills, all through Google Health.

Imagine if your Doctor and your Health Insurance provider both join up to Google Health. All of the sudden, the two entities can understand each other and fewer errors will occur. Fraud will become less prevalent, and new standards will be established (if you call “Google” a standard). Ideally, your health care will become cheaper - I can see Doctors giving a discount if you maintain a Google Health Account because they can see more history and communicate with your provider better that way.

Now, imagine this - because Google is not a Insurance provider, they have an unbiased opportunity to show you some very interesting things. For instance, what if they started showing your payment histories to your Insurance provider vs. what the Provider was paying? They could begin to show customers how much more efficient it could be if they just went with a catastrophic insurance plan over their current plan, or how they could save money by just maintaining a Health Savings Account instead of paying a premium every month that goes nowhere. I can really see the potential of the Health Insurance companies getting cut out of the picture with the moves Google is making. Forget Universal HealthCare - Google will universalize it for us!

If Google can get their privacy issues out of the way, what if Google provided an opportunity to add in OpenSocial Support, allowing you, per privacy settings you set, to show the health histories of those you are related to (I can’t think of any reason to show this to just friends, but maybe you can). What if they provided a secure API to this, allowing other vendors, like Family History sites to have access to the data? Soon you’ll be able to track the health of your ancestors, and perhaps even track genetic reasons for the health issues you are having. I really think the possibilities are endless!

I think Google is onto something here - it is obviously another play in their world domination scheme, but with the position they have, why not? Maybe it’s the Libertarian in me, but Google may just revolutionize the Health Care Industry, without a need to turn to government here.

I’ve attempted to stay out of this until now because as Nick O’Neill implies, it’s pretty childish the way both the supporters and critics are handling this. I’m especially disappointed with the way Facebook is handling the Google Friend Connect issue. For those out of the loop, Facebook cancelled Google’s Friend Connect App on Facebook because, “it redistributes user information from Facebook to other developers without users’ knowledge, which doesn’t respect the privacy standards our users have come to expect and is a violation of our Terms of Service”. Facebook gave no examples of what sections of the Terms of Service Google was violating, nor did they explain why Google was wrong. This vaguely-presented move prevents Google from having a universal login and profile that includes Facebook.

Google responded today saying, “We read the Facebook numeric id, friendly name, and public photo URLs of the user and their friends. We read no other information.” Google then proceeded to show detailed examples of the data they are retrieving from Facebook, how it is presented back to them, and the fact that they only share the URL of the user’s public photo with third party applications. They also stated that they only store data for 30 minutes at a time, after which they purge any of the above data cached on their servers.

I was impressed with Google’s response, and due to the openness and (apparent) honesty of it, I’m edging towards Google’s side on this, and quite scared as a Facebook developer on what Facebook could do with my own Apps. Assuming Google is right and not leaving anything out, Facebook could potentially remove any developer’s App from Facebook, no questions asked (although they did say they contacted Google multiple times about “something”), even though, per the developer’s understanding of the Terms of Service, the developer’s App follows the rules.

Based on what Google has said, I can’t see anything they did wrong in the development of their App that violates the Terms of Service. I really wish Facebook would explain further so we as developers could ensure our Apps aren’t doing the same. It also brings up many important questions as to what Facebook means when it comes to certain parts of the Terms of Service. I’m actually quite confused now as to what I can and can’t do on Facebook.

For example, Section 2a-6 in the Terms of Service, it states:

“You may retain copies of Exportable Facebook Properties for such period of time (if any) as the Applicable Facebook User for such Exportable Facebook Properties may approve, if (and only if) such Applicable Facebook User expressly approves your doing so pursuant to an affirmative “opt-in” after receiving a prominent disclosure of (a) the uses you intend to make of such Exportable Facebook Properties, (b) the duration for which you will retain copies of such Exportable Facebook Properties and (c) any terms and conditions governing your use of such Exportable Facebook Properties (a “Full Disclosure Opt-In”);”

Yet, in the section before that, it says I can only store indefinitely the uid, nid, eid, gid, pid, aid, notes_count, and profile_update_time. Does this mean I can or can’t get a user’s permission to store data on my servers? What about permanent session keys? I don’t see them in that list, yet the documentation seems to imply you need one to auto-authenticate a user. Am I breaking the developer ToS by storing a permanent session key?

Google is passing the public photo URL to third parties. Technically, because this is public information, it doesn’t even take a developer key to retrieve that URL. I could simply pull up the user’s profile page via their profile ID, and scrape the photo from the public profile. Is this really what’s causing Google to have their App removed? If so, I’m really scared as a Facebook App developer.

As you can see, the Facebook developer Terms of Service are simply too vague and too confusing for any developer to feel secure about keeping their App on the network. With actions like the one Facebook took against Google, I now have to question if my Apps too could be a target for Facebook to remove. If Google, who has hundreds of Lawyers on hand to look over such terms can’t figure out what they can and can’t do on the service, how can I, as a developer know what I can and can’t do on the service? Right now it’s a complete guessing game, with just the hope that Facebook will be decent enough to give you a warning before canceling your App. Is this really how we as developers should be developing our Apps?

I really hope Facebook can clarify this matter. I think after this move by Facebook, Facebook needs to clarify their Terms of Service for Developers and first, explain according to what violation in the Terms of Service Google’s App was removed, and second, break down in plain English what we as developers can and can’t do.

Facebook, Google laid out all their cards, at least as far as we can tell (and even if not they certainly laid out way more than Facebook did). How about not leaving us developers hanging and clarify all this once and for all? As a developer, I’m absolutely confused and scared at the moment of the very Walled Garden I make a living off of.

Photo courtesy CommonSpace.org

A friend of mine, Ali Akbar (@aliakbar), has made me aware of an interesting development going on with the domain he bought, googleappsengine.com (note the “s”). When he bought it, he approached me asking if I would be a blogger for the site, with intent to blog about Google App Engine news and announcements on the domain. He seemed quite excited about it, and, as a fan of Google App Engine, saw this as the perfect domain to write under since Google didn’t seem to be using it.

On Friday, without even time to set up the blog he was intending to create, Ali received the following very generic letter from Google (which he shared with me), asking him, in a very bullied fashion, without any offer to even make it right, to surrender the domain or face legal consequences:

Dear Sir/Madam:

Google is the owner of the well-known trademark and trade name GOOGLE, as well as the domain name GOOGLE.COM. As you are no doubt aware, GOOGLE is the trademark used to identify our award-winning search engine, located at www.google.com. Since its inception in 1997, the GOOGLE search engine has become one of the most highly recognized and widely used Internet search engines in the world. Google owns numerous trademark registrations and applications for its GOOGLE mark in countries around the world.

Google has used and actively promoted its GOOGLE mark for a number of years, and has invested considerable time and money establishing exclusive proprietary rights in the GOOGLE mark for a wide range of goods and services. As a result of its efforts, the GOOGLE mark has become a famous mark and a property right of incalculable value.

You have registered, without Google’s permission or authorization, the domain name googleappsengine.com (the ‘Domain Name’). The Domain Name is either confusingly similar to or incorporates the famous GOOGLE mark in its entirety, and, by its very composition, suggests Google’s sponsorship or endorsement of your website and correspondingly, your activities.

Your use of the Domain Name constitutes trademark infringement and dilution of Google’s trademark rights and unfair competition. Your use of the Domain Name is diluting use because it weakens the ability of the GOOGLE mark and domain name to identify a single source, namely Google. Further, your registration and use of the Domain Name misleads consumers into believing that some association exists between Google and you, which tarnishes the goodwill and reputation of Google’s services and trademarks. Moreover, your registration and use of the Domain Name is also actionable under the Uniform Dispute Resolution Policy (’UDRP’). Under similar circumstances, Google has prevailed in numerous UDRP actions. These decisions are located online at www.icann.org/udrp/udrpdec.htm.

In view of your infringement of our rights, we must demand that you provide written assurances within 7 days that you will:

1. Immediately discontinue any and all use of the Domain Name;
2. Take immediate steps to transfer the Domain Name to Google;
3. Identify and agree to transfer to Google any other domain names registered by you that contain GOOGLE or are confusingly similar to the GOOGLE mark;
4. Immediately and permanently refrain from any use of the term GOOGLE or any variation thereof that is likely to cause confusion or dilution.

Sincerely,
The Google Trademark Team

What???!! “You have registered, without Google’s permission or authorization, the domain name googleappsengine.com (the ‘Domain Name’).” So wait - now I have to get Google’s permission before I get any name that even resembles the Google trademark?

I am astounded at the bullyish nature of this letter, and to assume that anyone that buys any name even resembling the Google trademark to be a violation against their trademark name. Google clearly hasn’t been very good at defending this in the past - just searching with their own search engine, I’m finding tons of examples of sites using the Google name in their own domain name (yes, I “Google’d” it):

googlefight.com
googlesystem.blogspot.com
googleguide.com
googlealert.com
googlerankings.com

The list just gets started from there…

Now, let me preface this with the fact that I am not a Lawyer, but I did learn this in Law class in college. The “Uniform Dispute Resolution Policy” which Google references can be found here, and in the document, it states:

c. How to Demonstrate Your Rights to and Legitimate Interests in the Domain Name in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how your response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its evaluation of all evidence presented, shall demonstrate your rights or legitimate interests to the domain name for purposes of Paragraph 4(a)(ii):

  (i) before any notice to you of the dispute, your use of, or demonstrable preparations to use, the domain name or a name corresponding to the domain name in connection with a bona fide offering of goods or services; or

  (ii) you (as an individual, business, or other organization) have been commonly known by the domain name, even if you have acquired no trademark or service mark rights; or

  (iii) you are making a legitimate noncommercial or fair use of the domain name, without intent for commercial gain to misleadingly divert consumers or to tarnish the trademark or service mark at issue.

Based on Ali’s approaches to me, there was no intention for commercial gain, nor to tarnish the trademark or service mark at issue. I also have e-mail to prove his demonstrable preparations to use the domain in connection with a bona fide offering. Let me also add that my intention to blog for him was simply in my own support of the Google App Engine. I personally had nothing huge to gain from it other than possibly a little exposure from what could possibly be a good blog.

Let me also add that Trademark issue is a very different issue than the Copyright issue I mentioned before with the Mormon Church and Wikileaks. That issue was about Wikileaks knowingly stealing the content owned by the Mormon Church and using it for unintended purposes. This issue is simply about using the Google domain to further promote Google and its properties. Ali had intent to do such, and with my limited knowledge he should have every right to do so.

What if Facebook were to go after my other blog, FacebookAdvice, or even the book I co-wrote, “I’m on Facebook — Now What???“? What about my friend Nick O’Neill’s AllFacebook, or my other friend, Justin Smith’s InsideFacebook. What about my other blog, OpensocialNow? Does this mean I’m the next target to be bullied by Google?

Of course, GoogleAppsEngine.com isn’t my domain, and I don’t know what would make Ali feel better, but my suggestion to Google is to apologize to Ali for such a rude and inappropriate letter to what may be one of their biggest fans, and make right with him. How about, instead of threatening to take it away from him, offering him at least some swag and a little money for the domain? Come on Google - let’s not be evil here. I know you’re better than that.

As for Ali, last I heard he is not backing down. It’s a David vs. Goliath battle, but let’s hope Google can be a little better than Goliath in this case and just back down a little.

What do you think? Am I wrong on this issue? Is this just the same as the copyright issue I mentioned earlier? I’m very interested to hear your thoughts - this seems very unfair to me.

Photo courtesy http://mathmath-ecomm.blogspot.com/2007/11/google-is-useful-but-worried.html

I just noticed today a few new features in the Facebook chat window. When a new chat message comes through you may now hear a small, “pop”. It appears as though Facebook has begun adding sounds to their messaging, a much needed addition for those trying to know when people are trying to chat with them on Facebook. I have Facebook open most of the time in a separate tab, and often don’t realize until it’s too late that someone has been trying to chat with me in another tab. Now, assuming I hear the “pop”, that seems to be resolved. You can turn this feature on or off by clicking on “Settings” under the chat box in the chat bar, then checking or unchecking the box labeled, “Play Sounds for New Messages”.

The other addition, which I believe may be new (or I just barely noticed it), is Facebook seems to have added picture emoticons to the chat window. Now if I type, : - ) (without the spaces), it appears as a smiley face like this: I’d love to get a list of these.

Anyone know of any other new features added since the “pop”?

Note that I’m not going to provide any links to the mentioned content here - you can go research yourself. Unlike Wikileaks, I respect others’ copyright.

One thing you may notice on this blog is that while I rarely pipe in with religious thoughts and my own personal religious beliefs (although I used to quite often), I will not hesitate to step in when a Social Media-related religious event occurs. An interesting Groundswell is happening today between the Headquarters of my Faith, and the controversial anonymous sharing site, Wikileaks. However, I don’t think it’s occurring in the way people think it is.

This morning on Slashdot you may have seen an article about the Mormon Church (or “The Church of Jesus Christ of Latter-day Saints“, which is the Official name of the Church) sending a Cease and Desist to Wikileaks for posting links to a Copyrighted, yet old version (1999) of the Church’s “General Handbook of Instructions” for others to freely download.

I don’t understand why this is news. Having been in LDS Bishoprics before as a Clerk and Executive Secretary, I am very familiar with this manual. It is simply a guide for leaders of the Church to know how to council and guide members of the Church, and according to my understanding, NOT (fully) DOCTRINE. It is simply a Policy manual, and while Bishops and other Leaders of the church may follow its council, in the end they are left up to their own judgement (encouraged by the Church “to follow the promptings of the Spirit”) to decide how to handle matters in the Church. The Church considers the Bible, Book of Mormon, Doctrine and Covenants, and Perl of Great Price to be the Official Doctrine of the Church.

The Mormon Church is simply requesting Wikileaks remove the content because it is their own IP, not Wikileaks, and they are removing it as they would any other Church-owned and copyrighted document. Wikileaks and other sites are also portraying the contents of the manual as though it is doctrine for the general membership of the Mormon church, when in reality it was only intended as a guide for Leaders in the first place. The Mormon church has to protect the dissemination of false information as well.

In Charlene Li’s and Josh Bernoff’s book, Groundswell, she starts out with an example that happened last year on Digg.com where a user shared a blog post about how the HD-DVD Encryption standard had been broken. AACS LA quickly sent a cease and desist to Digg.com and the Digg.com founders promptly removed the link. Before Digg knew it, their own users began to backlash against them, occupying the entire front page of Digg with copies of the HD DVD encryption algorithm. Digg had a Groundswell of its own between its own users and it knew it had to do something. What did they do? They listened to their users and put the link back up, stating they would go down fighting rather than ignore their users.

I think with the post on SlashDot this morning some people may be thinking (and some hoping) a similar Groundswell is going to occur with the Mormon Church. Those that think so will be pleasantly surprised - there’s a difference between a Groundswell of your own members and those outside of your membership talking about you. How do you handle a Groundswell of people outside of your customer-base/user-base/member-base? You get in the conversation!

I want to share with you a video from Elder Russell M. Ballard, a member of The Church of Jesus Christ of Latter-day Saints Quorum of 12 Apostles - religious or not, I’d like to encourage you to read this not just from a religious perspective, but also a business perspective and how you can disseminate correct information about your business:

The Church of Jesus Christ of Latter-day Saints is getting in the Groundswell through its own members. They encourage their members to blog, Twitter, get on Facebook, and clarify misconceptions. The Mormon Church will overcome this Groundswell (if you can even call it one) via its own membership, correcting misinformation Socially rather than through news releases and other means and letting the general media and blogosphere say what it believes. They have a Youtube channel here. They are on Twitter. They have a Facebook Page.

I encourage other churches and even businesses to take this response - there is a lot that can be applied from a religious, or even non-religious perspective from this. When you get your own followers of any business, brand, or religion to spread correct information about your brand it can overcome any misinformation spread about it.

Wikileaks is wrong in this case - they are sharing copyrighted information, not owned by themselves, and without the permission of the owner. The LDS Church isn’t going after them because the shared links are “secret”, but rather it is copyrighted material, and Wikileaks does not have permission to share it! As a book author and software developer I don’t want people using my content without my permission (which I’m generally pretty relaxed on in my personally owned content). Why would I want Wikileaks sharing the content I personally own on their site let alone others?

(Sorry it’s been awhile since my last blog - it took me several days to figure out how to get my Flip video imported and exported to and from iMovie. To make a long story short, if you want to export from iMovie and have both picture and sound, you must import your source as something other than MP4 or AVI.)

This is the first article in my “Utah Startup Series“. Starting today I will be circling Utah to find the best and most innovative startups in Utah, and featuring them here on Stay N’ Alive. If you have a hot startup (early to even late stage) and would like to demo for me what your product can do, please contact me - if I have the time and like your idea I’d love to come out and take a look at it!

While at Web 2.0 Expo I had the opportunity to meet with Bungee Labs, a local, well funded Utah company who had “Platform as a Service” down before Google even started thinking about their App Engine. In our meeting they demoed their Bungee Connect “IDE” (written entirely on the web). You can see the video below.

My thoughts - you have to see this stuff in person to understand the full ramifications of what they’re doing. One of the cool things about their service vs. Google’s is they actually integrate with Amazon’s EC2 service (which was announced during Web 2.0 Expo), so you can actually host your other stuff on Amazon’s EC2 platform with the same licensing as your Bungee Connect account. Their licensing structure is very appealing as well - Bungee only charges based on the number of registered user sessions using their platform, not traffic, not bandwidth. If I understand correctly, it’s all based on the number of users actively using your application on their platform. For Facebook and Social Media developers this is appealing, as most Applications are rated based on Application use, not number of users or traffic. With Bungee you only pay for the users that actively use your system.

Overall, the guys at Bungee were Rockstars at Web 2.0 Expo. With their announcements about EC2 integration, flexible licensing terms, features on TechCrunch, EWeek magazine, and a dozen other publications, you can bet Google has a watchful eye on them. Ironically, it was interesting seeing Kevin Marx, head guy over the OpenSocial (and other) efforts at their party on Thursday evening.

Bungee will be presenting at our Social Media Developers meeting this coming Tuesday, showing us a simple “Hello World” example on how to build a Facebook App using their platform. Follow me on Twitter and if we can stream it live you can watch it via my Ustream channel. After demo I may just write my own Facebook App to try out their system - it should be interesting.

Bungee Connect Demo - Web 2.0 Expo from Jesse Stay on Vimeo.

Props to Rachel Strate, an Analyst from Epic Ventures (formerly Wasatch Ventures) who has offered to represent her Firm in providing food and drinks for the Social Media Developers Garage event on Tuesday. Rumor has it that they will be providing Pizza and drinks so come if anything for a free meal! The topic for the event will be a demonstration by Bungee on creating a Facebook App using their Google App Engine Killer, Bungee Connect. We’ll try to play some Wii afterwards as well.

Again, a big thanks to Epic Ventures for the food and Bungee Labs for hosting the event! If you would like to host or provide food for a future event (or even speak!) please let me know and we’ll make sure your company gets credit. This is a great opportunity for your company to get in front of a group of developers, bloggers and Social Media Evangelists for more exposure and future recruiting events.

While still vague in regards to details, Facebook today released some important information regarding their new design that is sure to excite those users that are considering leaving for other networks. The first of such features seems to be a slap in the Face (and maybe a token from former Google Execs) to Google Employee-founded FriendFeed. Facebook is calling the feature, “Publisher”, and from the Developer Wiki,

“The Publisher will be a central focus of communication and sharing in the new profile. It sits right on top of a user’s Feed inviting the user or others to add content. Applications can integrate into the Publisher to provide rich experiences for creating or finding content to post into their own and their friends’ Feeds…

This has replaced the old Wall Attachments feature. Now, Wall is just one type of application for creating content (text content), on par with posting links, or uploading photos or videos. For example, to add a video with the Video application, the user no longer creates a Wall attachment and adds the video. Instead, the user posts a video to a friend’s Feed just as if she were writing a Wall post.”

From the screenshots (to the left), it appears as though you can also comment on each posted item, further encouraging a “conversation” amongst members of the Facebook community. What’s most interesting is the integration with the Facebook Platform API and ability for developers to present items for discussion within a particular user’s Feed. It appears as though your applications will be able to actually utilize the text box within the publisher to present information on a user’s feed in different ways. More information regarding the new combined Feed/Wall can be found here.

Also very interesting is it seems as though Facebook will soon allow, via the publisher, the automatic playing of Flash, and onload events within FBJS. It seems this is Facebook’s answer to the demand from users migrating from Myspace and the competition from Bebo who allows such onload events.

In addition to the publisher, Facebook has released more information via their developers wiki about the Tabs that will be available, and how applications will be displayed via those tabs. It appears as though at first, all applications will be rendered in their current form in a tab called “boxes” (they mentioned earlier today that name may be temporary). What’s new though is it seems as though your application will be able to give the user options to render other forms of profile boxes to an “Info” tab on the user’s profile. It’s unclear, but this could mean your application will be able to have multiple forms of displaying itself within the user experience beyond just Canvas pages, profile boxes, and feeds. A new FBML tag has been created for this purpose called “<fb:add-section-button/>” which appears to give your application the ability to have the user add a “section” to their profile. (I now need to update FBML Essentials!) Such section will have the ability to display image objects or text that the user can type and provide to your application.

Facebook is also allowing your applications to register an “Application Tab URL” which will have your Application appear in a list of applications next to a “+” (plus) sign in the list of tabs. The user will then have the option to add your Application as a tab, offering an alternate canvas view of your application for the user’s friends to see.

Beyond the Info and Boxes tabs, it’s a bit unclear as to what the other tabs will be called. The most recent screenshot by them includes a “Photos”, “Wall”, and “Feed” tab, but it seems as though the Wall and Feed may be combined to produce the “Publisher”. It could be that the current “News Feed” will be under the Feed tab, while the combined Mini-Feed and Wall will be under the Wall tab. I’m sure we’ll see more screenshots soon. Also of note is that the Action items, the links below your profile image currently, will be no more. Instead you’ll be able to offer your users interactivity via the publisher and other integration points throughout the user’s profile.

It also seems as though the separate News Feed/profile is no more when you log in. It seems they are bringing the focus on the profile and including what is now the “News Feed” to become what will be the “Feed” tab. I like this new concept and hope it catches on - I think it will be a win-win for both Facebook, users, and developers in that it will bring a more fluid experience to users, and encourage discussion and people more than anything else.

With the release of this information to the developers wiki it seems Facebook is on the verge of releasing the new design very soon. I would expect to see such features in the next week or two, considering it was originally supposed to launch last month.

UPDATE: Facebook just released their official announcement here: http://developers.facebook.com/news.php?blog=1&story=107

I received a copy of the cover for FBML Essentials last Friday. I was waiting to figure out what the bird was on the cover before I shared it. The bird is a White Throated Dipper - from Wikipedia:

The White-throated Dipper (Cinclus cinclus) is an aquatic passerine bird found in Europe and the Middle East, also known as the European Dipper or just Dipper. The species is divided into several subspecies on colour differences, especially of the pectoral band.

My Editor tells me that usually they don’t have reasons for the animals they have on the covers of O’Reilly books, and that they usually choose an animal that fits well with the look and feel of the book. I guess one could say that most birds are “Social” - anyone know anything more about the White-throated Dipper? Here’s a video of one in the wild:

You can pre-order the book here - it should be available in print around June or July, based on the production schedule they sent me. There’s always a chance it could be at Graphing Social Patterns in June. If not, look for it at OSCON in the O’Reilly booth (and who knows - maybe I’ll be there to sign your copy!).

UPDATE: I forgot to mention - Nick O’Neill of AllFacebook.com, and Rodney Rumford of FaceReviews.com did the Foreword and Afterword for the book. Thanks to both of them (Rodney wrote his Afterword on his birthday!) for putting the time in for those! It’s an excellent read and reference for all already into or looking to get into Facebook development!

Our Utah Social Media Developers Garages (UTSMDev) happen every second Tuesday of every other month, and that is coming up one week from today. Our next meeting will be on May 13th from 7pm to 10pm at the same place as last time, Bungee Labs. We’ll bring the Wii or Xbox in case there’s time to play afterwards.

At this event, Bungee is going to show us a simple “Hello World” for Facebook using their Bungee Connect Platform. For those unaware, Bungee had “Platform as a Service” down before Google App Engine came out, and have recently even partnered with Amazon EC2 in order to provide full server access beyond their current platform. I have some videos of their stuff I took while at Web 2.0 Expo that I’ll try to post later this week in my “Utah Startups” series.

I am still looking for businesses to sponsor snacks and drinks (or even a full dinner - Bungee supplied Fuddruckers for our last event!) for the event - if your business would like some exposure I’ll be sure you get the credit. It could be a great way to meet new developers, Social Media experts, and bloggers!

As usual, while this event is targeted towards developers, everyone is welcome at the event, as it could be a good way for your business to meet developers in this area, as well as just learn a little more about the Social Media space! For future announcements of UTSMDev events, be sure to subscribe to our Google Groups mailing list here!

Bungee Labs is located in the old Wordpress building on the second floor - you can find directions here:

625 E Technology Ave B2300
Orem, UT 84097

http://maps.google.com/maps?f=q&hl=en&geocode=&q=625+E+Technology+Ave,+84097&sll=37.0625,-95.677068&sspn=34.724817,82.265625&ie=UTF8&ll=40.325575,-111.679738&spn=0.008163,0.020084&z=16&iwloc=cent

Please RSVP on our Facebook Event Page.

(I’m beginning to move much of my activity over to FriendFeed lately. Scoble calls it the “World Wide Talk Show” - please subscribe to my feed to comment and participate!)

I was going to write a few more of my annoyances with Twitter today, but a few pleasant announcements have come out of Twitter lately that I thought I’d share.

First, just announced today, Twitter will be shutting down accounts entirely that they have marked as “spam” on their blacklist. What??? Twitter has a blacklist? Yes, you heard it right.

Before today, Twitter would mark accounts as “spam”, but not tell the owners of the accounts they marked them as spam. Those owners of the accounts could follow others, but no one was able to follow them, and there was no way for the owners of those accounts to know they had been blacklisted. It was the same with the API - it was actually a huge headache for me as a Twitter API developer because despite me following the user, Twitter would respond with nothing as though the follow went through, but the next day the user would show up again as not being followed. I checked with Twitter and they confirmed the accounts I was having trouble with were indeed accounts that were on their “blacklist”.

Today, Alex Payne confirmed on the Twitter Dev mailing list that from now on users marked as Spam on Twitter will have their accounts suspended entirely for violating the Terms of Service. He also confirmed that they would avoid the headaches Facebook has had (aka Scoble’s account being suspended) and contact the owners beforehand to let them state their case.

I strongly welcome this new practice - Twitter has all the stats on their end to flag accounts as possible spammers, and by removing their accounts promptly this will make Twitter a much nicer place to use. The only other thing I would suggest they add now that this is in place is a way for developers to notify them of possible Spam accounts. You can do this as a user by “blocking” the account in question - I have no way to do this as a developer that I’m aware of.

The second, very welcomed feature is the addition of a “since” variable when requesting the friends or followers of an individual. In the past on SocialToo.com I had to do a request on all of an individual’s friends and all of an individual’s followers, and do a compare to see which of those following you, you weren’t following. For several A-list bloggers with near tens of thousands of followers, this was taking a few hours to complete the entire script, not to mention increasing the number of HTTP requests back to Twitter’s servers, I’m sure further burdening their already overburdened bandwidth.

Now, with the “since” variable, I can keep a tally of when I last checked your following/follower ratio and only do a request on those friends that have followed you since the last check. I can now go from checking those you follow on a daily basis, to checking almost every minute!

Last, Twitter has added the ability to determine, with one API call if a friendship exists between two individuals. Now rather than having to get a list of those you’re following, and then those that have followed you, I can just get a list of those following you and check to see that a friendship exists.

It is very refreshing to see such an active effort on Twitter’s part to help out the development community. I hope they continue to maintain the relationship they have with us, and continue to listen - many of us really want to see them succeed.

I have disliked the Twitter syntax since I’ve been on it (you can find me via @JesseStay on Twitter - go ahead and follow me!). As a long-time IRC user, everything seems backwards! I have often referred to Twitter as “IRC 2.0″. I’m not sure I can fully embrace that concept though.

For those unfamiliar with IRC, it predates even instant messaging. It brought out the original concept of a “chatroom”, and exists even today on various servers throughout the world. Ustream.tv currently uses it for its users’ channel chatrooms. It is the home for almost any “live” activity of any open source project (log into irc.freenode.net to see - I’m often in #utah there, as well as recently #codeaway). Traditions have been established, and virtual friendships have been bonded. In many ways it could have been the original concept of a “social network”, the first concept of linking friends together in a single place on the internet.

I was at a Perl conference just last year, and was happy to see the #YAPC chatroom in irc.perl.org open during the banquet. We had a ton of fun with that! Now, just this year, when I go to conferences, I see speakers leaving up Twitter, and answering questions via Twitter. The two seem to be serving similar purposes, in different ways.

That’s why I was astonished when I got on Twitter for the first time, and started seeing public messages directed to individuals with “@” signs in front of them! Is there a source for that that I’m not aware of? I know of no known documentation that Twitter themselves created to establish that tradition. In IRC you simply type “username:”, and then your message, and it gets highlighted in that user’s chat window in most IRC clients. Better yet, I can start typing the username and it tab-completes. You can’t do that in Twitter. That tradition and method has been around for years, yet Twitter seems to break the mold for some reason.

IRC also supports commands - I can type “/nick newnickname”, and it switches my username, automatically! It’s a basic standard that all clients support, open, and available for all to use. Twitter I have to go entirely to their website to do anything, and it’s extremely limited in what you can do. To direct message someone on Twitter, I have to type, “dm username message”. In IRC it’s just a simple command, like all other commands, and I can always type, “/help” if I don’t know what the commands available are. I simply type, “/msg username message”, and it messages the user, and again, it tab-completes the username!

Why couldn’t Twitter just use the IRC standard in their platform, and then expand upon it to improve the IRC standard and bring it to a mobile world? By all means many of their scalability issues may have been taken care of had they done so. Not just that, but they would now be able to support groups, and less development would be needed to manage their platform. Twitter says they have an open API - I question that openness. It’s not based on much of an open standard, and IMO, it’s causing them problems now because of it.

Looking to start a project? Always look at the open solutions that are out there first, then build upon them - you’ll have much fewer headaches if you do.

(Photo courtesy GapingVoid.com)

I’m thinking about starting a series on this blog of hot startups that I find interesting in Utah. I’d really like to show to the world the great startup scene that Utah has to offer - hopefully other bloggers in the area can pitch in and join in this effort as well. I am relatively new to Utah, and am just getting to know the scene out here, so please don’t take this the wrong way. My hope is that this is only because I’m new to the area - honestly, I only know of one or two established startups. I know of many that are “in the works”, but only a few have an actual business model with customers and revenue stream (or venture/private equity/angel funding to hopefully get to that revenue stream). I’m hoping I am just not “in the know”.

Do you have an up-and-coming startup you’d like me to feature? Do you know of any that stand out to you? I really am hoping those in Utah can step out of the woodwork and share via the comments (I monitor FriendFeed as well so you can also comment there) what you know. I hope to then pick out the best and try to get the word out about what you’re doing. Speak up, or forever hold your peace!

I’ve been analyzing various Social Applications Analytics tools lately, and have recently stumbled upon Sometrics. Sometrics handles full Analytics for your Facebook, Bebo, and MySpace applications, and will actually utilize the Facebook API to retrieve demographic info about those visiting your Application. As I examine the other Analytics solutions for Facebook and other Social Network Applications, I’ll try to post my findings of their strengths and weaknesses here, OpenSocialNow, and FacebookAdvice.com. If you’re not a techie, you may want to skip the next part, or forward it onto your IT department.

One thing I noticed about Sometrics is it seems to only provide code to paste on your Application pages for PHP, Ruby, and ASP.net. The code they provide is relatively simple, but in case you’re wondering how to do it in Perl, here is how I did it in Template Toolkit under Catalyst on Perl:

Enter this on all Application pages (I do it in my “footer” file):


[% IF Catalyst.request.param("installed") %]

<fb:iframe width='1' height='0' frameborder='0' src="http://halo.sometrics.com/fb_tracer.html?src=fb&installed=1&session=%7B%22session_key%22%3A%22[% Catalyst.request.param("fb_sig_session_key") %]%22%2C%22uid%22%3A[% Catalyst.request.param("fb_sig_user") %]%2C%22expires%22%3A0%2C%22secret%22%3A%22%22%7D&t=[% date.now %]"></fb:iframe>

[% ELSE %]

<fb:iframe width='1' height='0' frameborder='0' src="http://halo.sometrics.com/fb_tracer.html?src=fb&session=%7B%22session_key%22%3A%22[% Catalyst.request.param("fb_sig_session_key") %]%22%2C%22uid%22%3A[% Catalyst.request.param("fb_sig_user") %]%2C%22expires%22%3A0%2C%22secret%22%3A%22%22%7D&t=[% date.now %]"></fb:iframe>

[% END %]


Then add this in the “post-remove url” subroutine for your Applicaiton (or create one and add the URL in your App’s config):

=head2 remove

  Page that handles App removal

=cut

sub remove : Local {

  my ( $self, $c ) = @_;

  if ($c->req->param(”fb_sig_uninstall”)) {

    $c->res->redirect(qq{http://halo.sometrics.com/met.gif?a=u&app=}.$c->req->param(”fb_sig_api_key”).qq{&uid=}.$c->req->param(”fb_sig_user”).qq{&age=&sex=&city=&state=&country=&friend=&src=fb});

    $c->detach();

  }

  return;

}

I just realized I was missing about a week’s worth of comments from this blog. It looks like Google Reader at some point stopped tracking the comments (which is how I knew you were commenting), and I missed a few great ones, including one from BJ Fogg, whom I look up to. My apologies if it has taken awhile for me to respond to your comments.

If you want to track any of the comments feeds for any particular article, simply view the article, and append, “/feed” to the end and add it to your favorite RSS Reader. It will then send you updates of all comments for that article. Or, you can just click the checkbox next to, “Notify me of followup comments via e-mail” below the Captcha and it will e-mail you updates.

My apologies if I have not responded very quickly lately - that should be fixed now.

I have a sincere favor to ask of you. Would you, if you have not already, go to http://socialtoo.com and sign up and help me out in my cause? Share it with others, blog about it, Twitter it - this was written for you. Today, I launched something special on SocialToo.com, something that I hope will make a better environment on Twitter. It only works if lots of people use it though.

Today I launched an intelligent blacklisting feature on SocialToo.com. After registering and logging into your SocialToo! Dashboard, you’ll see a text box where you can enter twitter screen names you would like to blacklist. For each “spammer” you see, or individual you simply do not want to follow, enter their Twitter screen-name, and when a certain percentage of users on SocialToo.com all blacklist that same user (we have a unique algorithm that determines that, based on crowd-sourcing the definition of “Spam” on Twitter), we add that name to a global blacklist on SocialToo.com. When anyone chooses to auto-follow those that follow them on Twitter using the SocialToo! auto-follow feature, now those users will never be followed. You can now ignore them forever, hindering their reasons for being on Twitter!

SocialToo.com is a project I term, “the Companion to the Social Web”. After registering you have options such as the ability to automatically follow those that follow you on Twitter, add an automated message that gets sent to users (via dm) after they follow you for the first time, and on Facebook, redirect to your Facebook profile via yourusername.socialtoo.com. More features are being worked on for multiple social networks, and the idea is to find all the needs that just are not provided by the traditional Social Networks, and make them available to the public. If you have a need let me know. All scripts that run behind the scenes at SocialToo.com I am releasing on a single-user level via Open Source (GPL v.2) so you can run it on your own server should you desire.

The final feature, released today, is this Global, Intelligent, blacklisting feature. This feature, to me makes much more sense than services like twitterblacklist.com, since rather than depending on ratio only, we’re depending on actual user definition, by the masses to determine who is a “spammer” on Twitter. I’ll look to also integrate with twitterblacklist.com’s API in the future, and maybe even contribute back to it as we grow, but this is the start of something big. This is truly a Groundswell opportunity (I’m reading Charlene Li’s book right now) that you can be a part of.