Home - Stay N Alive

New Series: Social Coding

Posted on May 25, 2008 by jessestay

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

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.

Kirk Yuhnke, Reporter for Fox News 13 Joins the Conversation – My Tips for Him as a Reporter

Posted on May 19, 2008 by jessestay

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.

Facebook, as a Developer, I’m Scared!

Posted on May 18, 2008 by jessestay

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

Google Bullies Blogger to Surrender "GoogleAppsEngine.com"

Posted on May 16, 2008 by jessestay

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

The Mormon Church/Wikileaks Fiasco (or not-so-fiasco), A Mormon’s Perspective

Posted on May 14, 2008 by jessestay

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?

Facebook Announces Developer Integration Points to New Design, New "Publisher" Feature

Posted on May 7, 2008 by jessestay

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 “” 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