Archive for September, 2010

Introducing New PHP, Java and .NET SDKs [Developers' Pad]

Friday, September 24th, 2010

Along with our mobile SDKs, Gigya recently released PHP, Java and .NET SDKs to make it even easier to interface with the Gigya API using REST. Implementing these SDKs into your web application is very straightforward and the benefits will range from simple convenience for developers to more efficient code.

We wanted to highlight several features that developers have been asking about.

Signing Requests Made Easier
For security reasons, Gigya requires that all standard REST API calls be digitally “signed” using the HMAC-SHA1 algorithm. This guarantees that requests originating from an authorized partner have not tampered with in transit. If you’re using one of our SDKs, signature calculation is now done automatically. Take a look at this quick PHP code sample and you’ll notice the signature calculation (and all other related security parameters) are performed by the SDK.

// Define the API-Key and Secret key (the keys can be obtained from your site setup page on Gigya's website).
$apiKey = "PUT-YOUR-APIKEY-HERE";
$secretKey = "PUT-YOUR-SECRET-KEY-HERE";

// Step 1 - Defining request parameters
$params = new GSDictionary();
$params->put("uid", "PUT-UID-HERE");  // set the "uid" parameter to user's ID
$params->put("status", "I feel great");  // set the "status" parameter to "I feel great"

// Step 2 - Sending the request
$method = "socialize.setStatus";
$request = new GSRequest($apiKey,$secretKey,$method,$params);
$response = $request->send();

// Step 3 - handling the request's response.
if($response->getErrorCode()==0)
{    // SUCCESS! response status = OK
     echo "Success in setStatus operation.";
}
else
{  // Error
     echo ("Got error on setStatus: " . $response->getErrorMessage());
}

Validating Responses Made Easier
Gigya attaches a cryptographic signature to all responses that include user information. To verify the response is actually coming from Gigya (i.e., hasn’t been tampered with) your application should always validate this signature. If you’re using one of our SDKs, the class SigUtils will perform this signature calculation automatically. Check out this PHP code sample and you’ll see that validating Gigya response signatures is just a couple lines of code.

(more…)

Facebook Adds an Implicit Follow Feature

Wednesday, September 22nd, 2010

by Eyal Magen, Chief Strategy Officer

As recently reported by Inside Facebook and TechCrunch, a small tweak in the “respond to friend request” screen on FB is going to make a huge impact on how many people follow (not friend) a person on FB. Yes, Facebook has a follow feature, though it’s not explicit. When you make a friend request of someone and they do not block you (left as pending) all of your public activities are streamed to their feed, just as they would be if they were following you on Twitter. You can think of this as one-sided friending.

But how many people have public activities? Lots. Since the privacy setting change from a few months back, the default setting on most activities and shares for many many users is “public”. This new tweak makes is more difficult to block friend requests – it’s now a two-step process across multiple pages -  and promotes keeping friends in pending mode with a prominent “Not now” button.

Chances are significantly more people will be exposed to shares from other websites, and theoretically with the same degree of influence.