Thursday, April 15, 2010

How To Add Your Phone via One-Way Long Codes (International)

As of now, Twitter supports posting Tweets via text message from anywhere in the world, as long as your carrier supports Twitter. Click here for a list of supported carriers. (Receiving Twitter text messages via two-way short code is only available in these countries: US, UK, India, Indonesia, New Zealand, Haiti, and Canada. Click here if you live in one of these countries.)

If your country doesn't have a two-way short code, as listed above, you may still be able to use Twitter on your phone via our one-way international long codes. Please keep in mind that if you're using this number to access Twitter, you will only be able to send messages that will post as Tweets; you will not be able to receive any Tweets to your phone via this number. This is why we call it a "one-way" code.

List of One-Way Long Codes:

All International Users: +44 762 4801423

Germany: +49 17 6888 50505

Sweden: +46 737 494222

If you have already created a Twitter profile on the web, then follow the steps below to add your phone to one of our long codes so you can post Tweets on the go. You will not receive any confirmation messages from Twitter when you do this, so be sure you enter your information correctly.

To add your phone to your Twitter profile, follow these steps:
Send a text to the correct long code (listed above) with the word START.
Wait 2 minutes.
Next, send your username to the Twitter long-code. Do not use @ or quotes. Send your username ONLY, like so: hotdogsladies.
Wait 2 minutes after sending your username.
Next, send your password to the same number. This is case sensitive, so be sure you are sending your password correctly.
Wait 2 minutes.
Finally, send the word OK to the same number.

To test if you have correctly added your phone, send a "test" Tweet to your long code number (just like sending a normal text message). Then, log in to via the web to make sure your Tweets shows up on your Profile. If so, you have correctly added your phone. Once again, you will not be able to receive any texts to confirm phone activation!

Having trouble? Click here to read our long code troubleshooting tips.

Feel free to leave a comment below if you had problems adding your phone. Tell us your country and mobile carrier/provider, and the long code you used. We are working hard to support more countries and add more carriers. Click here for a list of currently supported carriers. Thanks! Thanks!

Wednesday, March 24, 2010

A last comment on editor/IntelliSense improvements

I got some data on some of the changes the languages team has made from Scott Wiltamuth (PUM of the languages team).

The first change is in the message dispatching priority that we do in keystroke processing. As a user is typing code that involves statement completion UI, we have a choice to make about the relative priority of (a) processing the keystrokes and (b) displaying and rendering the statement completion window. The VS 2008 behavior was to delay the processing of IntelliSense presenters until the WM_KEYDOWN queue is empty. As we transitioned the editor to WPF, the relative priorities changed. Changing them back to something closer to the VS 2008 behavior made a huge difference. The new code is show below, with the change highlighted (in case you can’t see the highlight, it’s “DispatcherPriority.Background”):

public void QueueSpaceReservationStackRefresh()


if (Interlocked.CompareExchange(ref _queuedSpaceReservationStackRefresh, 1, 0) == 0)


this.Dispatcher.BeginInvoke(DispatcherPriority.Background, new DispatcherOperationCallback(delegate


Interlocked.Exchange(ref _queuedSpaceReservationStackRefresh, 0);

if (!_isClosed)




return null;

}), null);



This one change generated huge wins on some of the typing tests that we use – between 39% and 55% from one build to the next!

The second change was to re-use rather than re-create the statement completion window, so that when you type o.Foo.Bar, we reuse the statement completion window that displayed “Foo” for the statement completion of “Bar”.

Combined, these performance wins will make a big difference, especially for fast typists who have slow graphics hardware or are using virtualization. Here are the % changes for some of our C# typing scenarios: