<![CDATA[Twitter blocked by T-Mobile - Valleywag Comments]]> <![CDATA[Twitter blocked by T-Mobile - Valleywag Comments]]> <![CDATA[Twitter blocked by T-Mobile]]> Actually I still wouldn't say with confidence this is a tech issue...that sounds like Twitter spin. I have it on good word that Twitter has not been getting their short codes approved by the carriers in many cases, taking a "screw them" approach. Maybe T-Mobile finally said enough. Frankly I think it's great that twitter is forcing the issue and exposing some of the woefully misguided policies of the carriers and their crony organization the MMA. But not convinced this tech issue isn't a policy issue that's now being worked out as a business arrangement behind the scenes.

TRex_418

]]> <![CDATA[Twitter blocked by T-Mobile]]> No, the controversy was started by narcissistic bloggers who started screaming "censorship" because two corporations are having trouble working together.

Michael Bauser

]]> <![CDATA[Twitter blocked by T-Mobile]]> Trackback

]]> <![CDATA[Twitter blocked by T-Mobile]]> T-Mobile seems to blcok any server relayed SMS... known work arounds:

Blackberry using T-mobile - web browse to [wwww.twitter.com]

Sony Mylo using T-mobile - use Mobile Twitter [www.m.twitter.com]

iCB

]]> <![CDATA[Twitter blocked by T-Mobile]]> Looks like this whole "controversy" was caused by a heavy-handed uninformed customer service representative. Not the first time.

Mr. E.

]]> <![CDATA[Twitter blocked by T-Mobile]]> According to Twitter's blog the problem is a technical one between their gateway and T-Mobile. Seems like no one reads the blog.

Mr. E.

]]> <![CDATA[Twitter blocked by T-Mobile]]> Twitter does not deal directly with carriers, rather they use a SMS gateway which has relationships with them. There either must be a problem on T-Mobile's end or a problem with Twitter's gateway. If there was a problem with their gateway Twitter would have been alerted to it by their provider so the problem is most likely with T-Mobile.

Mr. E.

]]> <![CDATA[Twitter blocked by T-Mobile]]> Oh Dear God, this is now the fourth blog I've had to explain this on this weekend.

T-Mobile can block Twitter messags all they want, because Twitter uses a short code (a number less than 7 digits, used for non-voice services only) for messaging. Short codes aren't phone numbers; they don't have to be supported by all carriers. It's up to the owner of each short code to negotiate carriage with phone companies.

Read this before you argue with me about that. Those are the terms Twitter would have agreed to when they decided to use a short code for Twitter Mobile, and they have no right to be outraged about having to live by them.

Likewise, the moral outrage of various bloggers is seriously misplaced. This isn't about blocking services, or picking technologies, or net neutrality, or anything else the easily excited technophiles want to claim. It's a business issue between Twitter and T-Mobile. If Twitter can't figure out what's going on, it's because Twitter didn't read the fucking manual. Now they need to act like a business (which is hard for them, I know) and work out their business issues with T-Mobile before I'm forced to explain this on another blog.

P.S. While I'm in snark-friendly territory, I just want to add: BibleBoy is one of the stupidest blogger aliases I've ever seen. Does he dress up in tights and help JesusMan fight crime?

Michael Bauser

]]> <![CDATA[Twitter blocked by T-Mobile]]> It's doubtful that T-Mobile is really actively blocking Twitter, rather it's more likely that there is some systems problem that Marianne Maestas has not been informed of. It makes absolutely no sense for T-Mobile to bock Twitter as the SMS traffic that Twitter drives is close to free money for them.

Mr. E.

]]> <![CDATA[Twitter blocked by T-Mobile]]> Pay the $200 cancellation per LINE, and then walk away to another carrier who sucks just as much. You'll show them!

rohitj

]]> <![CDATA[Twitter blocked by T-Mobile]]> Well, Microsoft probably WOULD block Firefox if they could get away with it.

I wish more people would just WALK when they get responses like this. In large numbers. Make a few examples out of responses like this and it would scare the shit out of all of them.

Here are my "Term of Service" for my personal vendors anyway: You give me what I want, NOW, for a reasonable price, or I drop you like a coyote date! Now bend over the other way."

macbeach

]]> <![CDATA[Twitter blocked by T-Mobile]]> Imagine what would happened to Microsoft if they denies Firefox being run on Windows because it's not a "authorized" application. T-Mob is evil.

yinst

]]> <![CDATA[Twitter blocked by T-Mobile]]> T-mobile's position that Twitter can be suspended as a 'third-party service' is absurd. SMS isn't a third-party service, and it's the only service that T-mobile needs to support. Blocking Twitter isn't 'suspending a service' it's actively denying messages at the sub-service level.

But this is a good thing. As others have mentioned in the last 24 hours, the more bonehead and harmful moves the telcos make in the near term the more case-studies are available when Net Neutrality legislation comes to the fore.

kfury

]]> <![CDATA[Twitter blocked by T-Mobile]]> "These fuckers also do not support Facebook mobile" - seconded

daveambrose

]]> <![CDATA[Twitter blocked by T-Mobile]]> Can you spell this out for me? Is T-mobile actively refusing to pass on text messages to/from Twitter, or are they just refusing to support a mobile app?

Nick Douglas

]]> <![CDATA[Twitter blocked by T-Mobile]]> These fuckers also do not support Facebook mobile

ScalaWag

]]>