Whoops.

Turns out that <> already has Twitter integration, they just hid it pretty well (under Services in the Admin tab). In that case there might actually be less people interested in <>, although it still has some advantages:

• You don't need to give GitHub your Twitter password. (Actually, that's Twitter's fault, their API doesn't allow for anything else.)
• You can change the information displayed in the tweets.
• You have <> URL shortening instead of <>.

See also <>.