Utah Open Source Planet

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?

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.

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.

It’s been a while since I’ve blogged about the Flock Browser, and after checking it out today I thought it was time for an update here at Ubuntu Tutorials.  For all of you that are addicted to all of the social networking sites (Digg, Twitter, Facebook, del.icio.us, Flickr, etc) you get an integrated-into-the-browser experience with the Flock Browser.  Follow the steps below and give ‘er a try:

Install Flock Browser v1.2 on Ubuntu 8.04

Unfortunately there are no .deb packages for the Flock Browser so you’ll have to install things manually.  Yes, this’ll require some commands at the terminal.  Yes, I’ll give you cut-and-paste commands.  No, the terminal won’t eat your cat.

1. Download Flock Browser v1.2 and select “Save File” to store it on your Desktop.
2. Open a terminal and run: sudo tar -C /opt -xzvf Desktop/flock-*.tar.gz
3. Create a link to the new browser within your PATH: sudo ln -s /opt/flock/flock /usr/bin/flock-browser
4. Dump the following into a new file: /usr/share/applications/flock.desktop

[Desktop Entry]
Encoding=UTF-8
Name=Flock
Comment=Flock Web Browser
Exec=flock-browser
Icon=/opt/flock/icons/mozicon128.png
StartupNotify=true
Terminal=false
Type=Application
Categories=Applications;Network

You should now have a new entry in your Applications menu called “Flock Web Browser” (your menu may need to refresh first).  You can also launch the browser from the terminal using the command:

flock-browser

Enjoy!  Anytime there is a Flock Browser update you should be able to safely repeat steps 1 and 2 and you’re set.

Random Posts

• How To Disable ipv6 on Ubuntu 7.10 “Gutsy Gibbon”
• Free Promotional Flyers Available for US LoCo Teams - Sponsored by System76
• nautilus-open-terminal : terminal quick launch
• KDE ‘Kompose’ (OSX Expose) : Ubuntu (6.06 / 6.10)
• Beginning Ubuntu Linux : From Novice to Professional
• FC5 Redeemed
• United States of Ubuntu : State of the Union
• One Week With KDE : My Challenge
• Synergy - share input between multiple machines : Ubuntu (6.06.1 / 6.10)
• Some Exciting News For Me

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.

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’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.

I got a message from Facebook today saying that someone had friended me. I realized I didn't care. Not that I didn't care about the person who'd friended me--I didn't care about Facebook. It's been weeks since I was there and my life is pretty much the same.

I think the reason is Twitter. Twitter is much more social, much more interesting, and the plethora of clients (including any mobile phone with SMS) means that I don't have to remember to go check the site to see what's happening. Twitterific displays a solid stream of the 140 character thoughts of my friends.

Because of Twitter, today I know:

• There were tornados in Denver and Laramie
• Twitter posted an article about their architecture on their blog
• There's a blogger dinner tonight in Salt Lake City
• @tylerwhitaker and @bradbaldwin aren't going to carpool to the blogger dinner

I like that.

Twitter has scaling problems even though their user base is reportedly quite small. As Nik Cubrilovic points out, Twitter isn't like Wordpress or Digg. Twitter is a group forming network (GFN). When a Metcalfeian network adds another user, the number of potential connections goes from N² to (N+1)². When a GFN adds one more user, the number of potential connections goes from 2^N to 2^(N+1). In case it's been a while since you'd done that math--it's a big difference.

To make this more real, consider TechCrunch's twitter account. When TechCrunch, with almost 18000 followers, sends a message, that results in 18000 messages--one to each follower. This is like the phone system with infinite, always-on conference call capability. Sure, you can do things internally to collapse some messages, but you're still dealing with exponential growth.

Cubrilovic points out that this feature creates some serious engineering problems getting Twitter to scale. AL3X at Twitter argues that they're not blind to the problems and they're working on them. There are dozens of people blogging about what kind of architectural solutions might lead to better uptime at Twitter. AL3X's final plea: if you're so smart, come work for us. Good answer.

Tags: facebook social+networks twitter

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.

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?

(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)

Lately I have been sucked into the Social Networking scheme.  I think someone is trying to tell me something about individuality and the need to collaborate, but I have been creating social networking logins all over the scene.  

It started with my sister-in-law convincing my sister to sign up at GoodReads, and my sister subsequently sending it to me.  I didn’t see any harm in it, as it was a place for me to post the books that I have read and currently reading.  Not too invasive, right?  

Next, my colleague introduced me to Last.FM, which is quickly taking the place of my regular iTunes materials.  After all, where else can I get Abney Park mixed with Vernian Process and Dolphins?  It’s now become an addiction, and I’ve only had it for one day.  

The final straw now is getting a Twitter account.  I’ve never seen the point in spending so much time writing about what I am doing.  Isn’t that what a blog is for?  well, yes and no.  A blog is great for longer thoughts, essays, comments, etc. that take a lot of thought and time to explain.  But what about those single thoughts, complaints about something not compiling, or little projects that just don’t take a lot of time?  This is what Twitter allows you to do.  

And I’m now using Twitter to keep track of my productivity.  I can use it to document the projects I do during the day, so I can look back and see just what it was I accomplished while working.  So, believe it or not, I’ve actually taken the plunge into the Social Networking scene.  Perhaps soon, I may actually become a social person.  ^_^

I’ve written before on the power of community and how Social Networks are bringing back the days of the small community within a large world. That’s why I was happy to hear in a recent interview I had with Erin MacLeod of the Toronto Star that BJ Fogg, Professor at Stanford, and teacher of the “Psychology of Facebook” class seemed to be on the same track (Fogg is also author of an excellent book on technology and marketing called “Persuasive Technology“). From the Toronto Star article,

“If you look at the history of civilization, you’re part of a community and as you grow up you stay connected with a community and those past lives and past friends,” Fogg says. “So maybe in some ways Facebook is bringing back what humans have lived with for thousands of years, a persistence of identity and relationships for decades.”

I agree wholeheartedly with Fogg. In the article I mention that it goes even further beyond that though. Technology always adds another layer to something that previously existed in a lesser form. With Social Networks, technology is simply bringing together a massive world of people into a small community-type atmosphere, but at the same time allowing a layer of privacy, giving users control over what that small community sees, and does not see.

It’s true that you will need to be more careful in the future with what you reveal on Social Networks, but the power of these Social Networks is that there are controls in place already to prevent information from getting out. Facebook has friends lists, privacy features, and flags you can enable and disable to control what elements are revealed to what people. You’ll find similar elements in other networks. I imagine even in Twitter (which I argue isn’t necessarily a “Social Network”, but rather a communications platform for Social Networks of people) will develop methods to segregate your friends and communicate only to whom you want.

At the same time, I feel we are becoming more forgiving of one another. We recognize through these mediums that we are all human, with flaws and imperfections, and that’s okay. Social Networks have power to make the world a better place.

Check out Fogg’s Psychology of Facebook class on Facebook here - he Ustreams it live every week!

I mentioned this at the Hackathon in March, but have not had the time to blog about it yet. Thus far all announcements for the Utah Social Media Developers Garage Meetings and Utah Facebook Developers Garage Meetings have been announced either through this blog, or our Facebook Group. I’ve now created a Google Group for us at http://groups.google.com/group/utsmdev. Please sign up there and I’ll issue all announcements via that list. Google Groups provides a more neutral ground in the sense that users don’t have to have an account to use it (to an extent), as compared to the Facebook groups. We’ll keep the Facebook groups around, and depending on membership I’ll still send announcements there as well, but I encourage all to sign up on the Google Group if possible. In addition, having a mailing list will allow us to have more of a discussion. This way if you are working on a project in Facebook, or OpenSocial, or even Wordpress or Twitter or other APIs and you run into issues, you can ask the group and we can work together to solve the problem. I figure this way we’ll be able to all build a strong Social Media Development community here in Utah that others can rely on. Google groups will also give us a page we can tell others about the group, when the next meeting is, etc. If you have some graphics and HTML skills to help with that I am open to volunteers!

Also, I have created a Google Code repository at http://code.google.com/p/utsmdev/. For anyone okay with producing their code under the GPL, this will give you a place to store your code, and collaborate with others on the code, track issues, etc. If you want commit permissions to that repository please contact me and I’ll add you. As Google App Engine gets more integration into these things we’ll also set up a hosting option through Google App Engine to actually host your apps. Hopefully all these options will make it all much easier for everyone to get out and collaborate in their coding. It’s a good time to be a developer…

P.S. - We will continue on in our every-other-month meeting structure now, so our next meeting will be the second Tuesday in May. I’m working on a speaker, so if you know anyone or have ideas let me know!

The hype is out there and it is real. After the launch of Google Apps Engine, everyone is up in arms as to what exactly it is, and who needs to watch out. The truth is, everyone needs to watch out when Google launches something, since