In fact, there are quite a few.
The simple ones are
Reply to a tweet (as outlined above): http://www.twitter.com/intent/tweet?in_reply_to=128569788623634432
Retweet a tweet: http://www.twitter.com/intent/retweet?tweet_id=128569788623634432
Favourite a tweet: http://www.twitter.com/intent/favorite?tweet_id=128569788623634432
View a mini twitter profile of a user (the mini profile includes a follow button): https://www.twitter.com/intent/user?screen_name=Wobable
The more complicated intents:
You can actually encode an entire tweet, or partial tweet ready for the user to tweet (though they retain the ability to alter the tweet before sending).
Prepare a tweet that includes a hashtag (or two): http://www.twitter.com/intent/tweet?hashtags=firsthashtag,secondhashtag – you can use as many hashtags as you want. Separate them with commas.
Why not use this technique to add a QR Code on an event programme so everyone tweets using the same hashtag!
Prepare a tweet that mentions an individual: http://www.twitter.com/intent/tweet?via=wobable
Prepare a tweet that includes a URL: https://twitter.com/intent/tweet?url=http%3A%2F%2Fwww.wobable.com%2FP%3D279 includes a link to this post. It looks complex until you understand that “http%3A%2F%2F” translates to “http://”. See the next section for more on encoding a tweet.
Prepare a tweet with some suggested text: http://www.twitter.com/intent/tweet?text=This+tweet+was+sent+by+using+a+twitter+intent
Note that the spaces are converted into plus signs. Any symbol that you want to include (for instance @ or #) needs to either be encoded into ASCII code (@ is %40, # is %23), or dealt with in the intent using the techniques above.
There is a very useful tool to encode ASCII here: http://meyerweb.com/eric/tools/dencoder/. This is what I used to convert the URL above.
It is worth noting that the meyerweb tool converts spaces into %20 rather than +. This will still work in the web intent, but takes up three times the space (as %20 is three characters and + is only one) – so it is likely to make a QR Code more complex than it needs to be.
If you want to include a carriage return, the symbol is %0A
Note. This next section doesn’t always work – it seems to be to do with whether the website or browser understands UTF (extended character sets). Use at own risk!
You can even include those annoying tweenage tweet symbols (assuming you know what the code is for them). For instance an open heart ? is %E2%99%A1
A closed heart is %E2%99%A5 – so “I ? New York” would be: http://www.twitter.com/intent/tweet?text=I+%E2%99%A5+New+York
There is a list of some of these pictograms here and here – the relevant code is in the third column. I urge caution though, because not all twitter clients can read all these pictograms – and you cheeky message can look very silly when it is just a load of empty boxes!
Note. End of picky section. If you copy and paste the above links, be careful that you don’t accidentally convert the percentage signs into ascii characters too (% is ascii %25) as this can get VERY confusing!
You can even combine the techniques: https://www.twitter.com/intent/tweet?text=I+am+very+excited+by+the+possibilities+of+mixing+Twitter+intents+and+QR+codes&hashtags=geek,QRCode&url=http%3A%2F%2Fwww.wobable.com%2F%3FP%3D279&via=wobable
And of course we need to end with the QR Code for that (courtesy of Bit.ly, as the URL above is waaay too long):
Have fun with it! Let me know if you have any novel uses for this idea.
Oh, and be sure to test it thoroughly before you use it – coding URLs I have found particularly tricky!


Just discovered you can do something similar on Facebook!
http://www.daddydesign.com/wordpress/how-to-create-a-custom-facebook-share-button-for-your-iframe-tab/