rtt

Tinder API documentation

Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution

http://rsty.org/

I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

ErikAndreas

Got a repo for this now: https://github.com/ErikAndreas/pjax-ractivejs

Start from/change/extend https://github.com/thybag/PJAX-Standalone with

• CommonJS format and Browserify
• Q around Superagent for XHR Promises
• No need to support more than data-pjax equivalent attribute
• Same Ractive templates on client as well as server (Ractive is isomorphic)
• Use Ractive for rendering of client side instead of PJAX "standard" of returning/render full html (also, page title element in response is hideous) and just return data (json) from server, kind of what twitter seem to be doing

michaelcox

// Based on https://github.com/jaubourg/ajaxHooks/blob/master/src/ajax/xdr.js

(function( jQuery ) {

if ( window.XDomainRequest && !jQuery.support.cors ) {
	jQuery.ajaxTransport(function( s ) {
		if ( s.crossDomain && s.async ) {
			if ( s.timeout ) {
				s.xdrTimeout = s.timeout;
				delete s.timeout;

jonathanmoore

Share Counts

I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.

If you want to roll up all of these into a single jQuery plugin check out Sharrre

Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.

Twitter

mattapperson

<?xml version="1.0" encoding="utf-8"?>
<TabHost xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@android:id/tabhost"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent">
 
    <LinearLayout
        android:orientation="vertical"
        android:layout_width="fill_parent"
        android:layout_height="fill_parent"

hotchpotch

#!nginx -p . -c cocproxy.nginx.conf

error_log /dev/stderr debug;
daemon off;

events {
  worker_connections 48;
}

http {