Facebook Fraud?

The creator of popular YouTube channel Veritasium takes a look at what happened when he used Facebook’s advertising to promote his page. The results are pretty brutal.

Spoiler alert… those likes you paid for and cherish so dearly… they’re pretty much all fake.

If you have ever even thought about purchasing advertising from Facebook, you should watch this…

The UX of Facebook’s New Like Button

Much of the discussion around the new Like button has centered on the removal of the thumbs up icon. And while that it is a major symbolic move, the real change from a UX perspective is the color.

If you didn’t already know how huge the Like button is, here’s some perspective – the button is viewed 22 billion times daily across more than 7.5 million websites. Massive.

But that huge number of impressions was happening next to a whole slew of other sharing buttons that have popped up from companies such as Twitter, LinkedIn, Pinterest, etc.

And because all of those other companies had simply followed Facebook’s lead, and their UX, all the buttons pretty much looked identical. Lazy users had no visual indication as to which button to click first. Not any more…

One look and it’s clearly a great UX move. A simple splash of color is all it took to differentiate the button from the rest and draw the user’s eye. I would love to know what kind of engagement bump they’re seeing after the new button rolled out late last month.

I’m guessing it’s only a matter of time until we see colored buttons from everyone.

Django and Testing Facebook Applications Locally (Port 8000)

If you’re developing a web application that allows uses to create an account, you’re probably allowing them to do so using Facebook. In order to provide this functionality, Facebook requires you to create an application on their developer portal and set a few basic parameters.

But rather than create one application for both local development and production, my preferred way is to create a second Facebook application specifically for dev. You’ll need to set a few parameters in the application’s config to get things working.

First in the Basic settings set the App Domains along with the Site URL:

Then in the Advanced set the OAuth redirect URIs:

Make sure to include the port you use in the various URLs / URIs. Django’s default is 8000.

And if you keep your application ID / secret as settings in your Django config and use Disqus-style settings, you can simply add the new values for your Facebook application to your dev config to override the default values.

Django Register with Oauth – Facebook

Now that you’ve read the overview / disclaimer, let’s dive into Facebook.

First off, ensure that you have registered your application with Facebook and have created the following in your settings file:

1) Create the redirect URL

The first step in the oauth handshake is to redirect to Facebook with some application specific data in the URL including your application ID and redirect URL (where you want Facebook to send the user after they’ve approved / denied the application):

2) Redirect to provider’s site

This url can now be used to redirect to Facebook (i.e. HttpResponseRedirect(url)):

3) Handle the response (approved or denied)

Once the user makes their choice to approve or deny, Facebook will redirect back to your redirect_url. You will need to verify the user approved the application:

If any of the above tests fail, we can safely assume the user either arrived at this page directly (i.e. by typing in the URL) or they denied the application. Either way we don’t want to proceed and should redirect them to the start of the registration flow (i.e. HttpResponseRedirect(reverse('register'))).

4 & 5) Get an access token and the user’s profile

At this point the user has authorized your application but you don’t have actual access to their data yet. To get that you’ll need to request an access token. Notice that we’re saving the access token to the user’s session as we don’t want to request it more than once during the registration flow.

Once you have the access token, you can then make the request for the user’s profile data:

That’s it! You can now use the user’s profile information to pre-fill a registration form, perhaps skipping over fields where you already have a required value such as an email address or first and last name. Just be sure to save their Facebook ID along with their profile so you can use it validate them in the future. You should also save the access_token and expires values so that you can make future requests to the API for this user or refresh the access token when it has expired.

In a future post I’ll be looking at how to detect an already registered user as well as provide a login with this provider button.