Skip to content
A jQuery-based implementation of a Facebook-like MultiFriendSelector.
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



A Facebook-like Multi-friend selector interface for social applications built on the jQuery framework.. Support for Twitter is built into the public methods but can be used with basically any service that can follow the same JSON data model.


The MultiFriendSelector was written by Eston Bond for use on the social game Spymaster, which needed such an interface for its invite page. The multi-friend selector control is licensed under an MIT License, just as jQuery is. I’d like to know where this control is being used — if you decide to use it, please drop me a line at


To implement a MultiFriendSelector control, simply give it the div element you wish for it to instantiate itself in. For example, to instantiate the control in a div with the id my-friend-selector, simply write:

$(‘#my-friend-selector’).multifriendselector({id: ’eston’});

This will instantiate a MultiFriendSelector for the twitter user eston.

The MultiFriendSelector has many options you can set upon instantiation. Many mimic the same syntax used for the FBML fb:multi-friend-selector for the sake of other platform developers. Supported options are described below. These should be passed in as key/value pairs in an object as the first argument.

  • actiontext: The title at the top of the MultiFriendSelector. (Defaults to ‘Select friends to invite’),
  • actiongraf: The paragraph to display below the MultiFriendSelector (Defaults to ‘Select your friends to invite to this service.’)
  • async_post: Whether or not to post the selected IDs asynchronously. (Defaults to true)
  • async_post_url: An optional asynchronous endpoint to post an async ID post to, separate from action_url. If this is not set, asynchronous POST requests will use action_url. (Defaults to null)
  • async_post_redirect: A redirect point that is fired once the asynchronous post is complete. I will probably change this to a callback later. (Defaults to ‘/’)
  • async_post_success_callback: A callback to fire upon a successful POST of the data to your server.
  • async_post_error_callback: A callback to fire upon asynchronous error in making the POST to your server.
  • bypass: The default caption for bypassing the MultiFriendSelector. If this is left blank, no bypass controls are rendered. (Defaults to ’’)
  • bypass_url: The href at which bypass links point. (Defaults to /)
  • development_mode: Toggles on/off development mode. For developer use only.
  • exclude_ids: An array of Twitter IDs to exclude from the MultiFriendSelector interface. (Defaults to empty array)
  • friend_type: The type of friends to populate into the MultiFriendSelector control. Supports ‘friends’ and ‘followers’ by default. (_Defaults to friends)
  • id: The Twitter ID or screen name to pull friends for. This attribute is required.
  • limit: A limit of how many Twitter friends to display in $.fn.multifriendselector.getData. Raising this limit without having a proxy for authentication in place will get yourself quickly rate limited. (Defaults to 100)
  • mfs_id: ’’,
  • post_action: The primary POST action for the MultiFriendSelector control. (Defaults to ‘/’)

Public methods

Most functionality is encapsulated such that it will not clutter the namespace of your application further, including the HTML and CSS that the MultiFriendSelector code writes. However, two functions have been namespaced such that they are editable, in case you wish to deploy this function using Twitter authentication or server-side proxies for communication. If you are interested in this type of extension, please see $.fn.multifriendselector.getData, the function responsible for retrieving a user’s friends/followers and $.fn.multifriendselector.postForm, the asynchronous form posting plugin.

Interfacing with other social networks or proxies

If you wish to interface the MultiFriendSelector control with your own API proxy (like I do with Spymaster) or a different social network, you will still need to follow a Twitter-based object model for the user data returned so that the MultiFriendSelector control can properly render the data. In your result object for each user, you will need:

  • id: Integer or String The ID of the user. This will be set as a user ID on the box and is how the MultiFriendSelector keeps track of IDs to return after multi-friend selection.
  • screen_name: String The user’s screen name. In the case of Twitter, these are things like eston, cnnbrk, aplusk etc.
  • profile_image_url: String (optional) A URI to a profile image of the user.

All other data in the default Twitter object is not used by the MultiFriendSelector.

Bug reports

Any bugs in this code should be reported to me via email at the email address above. Bugs have a far greater chance of being patched if you submit a patch or request a pull.

Something went wrong with that request. Please try again.