‘Twitter Spritzer’ And Other Twittery Things You Forgot Existed

You’re all over Twitter every day and you know all about it, right? Well, maybe you do, maybe you don’t, but (most likely) you don’t have “everything Twitter” at the tip of your tongue every second of the day, particularly if you’re a Twitter marketer and not an app developer.

Either way, we have a quick list for your reference. It’s full of Twittery things you either didn’t know about or heard of before and forgot they existed (like diphthongs). Take a scan so you don’t send out foolish tweets or say something silly the next time you’re “talking Twitter” with the masses.

Here are a few things you’ll hear tossed around Twitter from time to time. They may leave you scratching your head wondering what on Earth they could be, or you (most likely) just ignored them and moved on. Don’t move on.


If you’re “talking Twitter” to a client and they know more than you do, you can be prepared to look foolish or know your stuff – like this:

API. Application Programming Interface. Good luck remembering that (I never do), but know what it is: It’s the magical goop that third party developers need to manipulate Twitter data and create their Twitter-based apps. The first API is non-existent (after June 11th, that is) and it has developers in a tizzy: here’s why.

API v1.1. This is the new and improved API. It’s more restrictive and has killed off many third-party apps (as you read if you clicked above or here).

Token limits. App developers are limited by the number of individual tokens they get from Twitter. API v1.1 changed that limit, reducing it to 100,000 tokens. Many popular apps reached this threshhold pretty quickly and died.

OAuth. Twitter USED to let you run around using it’s stuff all wily nily apparently and v1.1 will also put a halt to that, requiring Twitticizens seeking access to authenticate (using OAuth) or vacate.

Blackout TestsThis term will soon be irrelevant, but it’s a fun one to know: It’s what Twitter did to help app developers prepare for the new API. They turned off API v1 and let loose API v1.1 so they could see what did/didn’t work. (Most of it didn’t.)

Twitter Firehose. If you want to mine Twitter’s data for insight (and who doesn’t), there are three levels of access. Firehose is full access and only available to certain Twitter partners – for a pretty hefty price.

Twitter Gardenhose. Gardenhose is next and IT provides you with a 10% sampling of all public tweets. You can obtain gardenhose access through an authorized provider (someone with full firehose access).

Twitter Spritzer. And the spritzer provides a 1% random sample of public tweets. This is common, everyday access and cost nothing beyond the time it takes to sort out how to use it.

What would you add to this list?

HT @HiveMindMap for pointing out my foolish tweet.

(Image from Shutterstock)