I have since upgraded the blog to version 2.5.1, and hopefully thrwarted a few additional attempts to continue turning my blog into a spam-land free-for-all. Hopefully, that is.

Anyway, moving on. Still working on the next version of Maveno.us; as a little preview of what’s to come, the new version will include a reverse dictionary, antonym and synonym lookup, and several changes to the interface for easier access, and better organization. Spellcheck will be made easier to use, and include some additional features related to access it in the interface as well. I need to update the roadmap, and, actually, all but change it entirely. *sigh*

It’s coming, slowly, but surely. Work and school, and being a dad take precedence, of course, so it’s still just a side project.

Let me explain how this all came to light for me. About a month ago I attempted to setup Google Calendar alerts. Upon requesting the verification code, and never receiving it, I headed to the google help docs to solve the issue on my own. What I was about to discover, was that this issue had nothing to do with Google, but rather my wireless provider. What, you say, that can’t be??!? Nay, I say, err, rather, yay, it does. *cough* Anyway, here’s where it gets interesting.

After several, several calls to the T-Mobile customer support centers, and plethora of departments, multiple representatives and an ungodly amount of time (Three and a half hours) on the phone with nearly every department available in T-Mobile’s customer support arsenal, I have learned the following.

• T-Mobile does in fact block SMS shortcodes.
• Supposedly shortcodes are only blocked for Pre-paid accounts, but those on the flexpay accounts with contracts, as well as regular customers with contracts have also reported having shortcodes blocked for their phones as well.
• T-Mobile customer support is to inform customers that they are unable to block shortcodes, and in fact, are incapable of doing so.
• T-Mobile is the *ONLY* major wireless provider that blocks SMS shortcodes.
• T-Mobile does NOT block SMS shortcodes for INTERNAL use.
• T-Mobile customer support will use the afore-mentioned shortcodes to state that they do not block shortcodes, due to the fact that you can access their internal shortcodes.
• Only the Advanced Technical Support seems able to inform customers that they do block “3rd party” shortcodes; upon doing so they are also overwhelmingly ecstatic to inform you that “You have no recourse other than to cancel your account, and pay the $200.00 early termination fee that would be assessed at termination”.
• T-Mobile has way too many technical support departments.

What can we do then, you ask? I’ll tell you what, the same thing we geeks always do when faced an oppressive cooperate entity threatening our very way of life. Send a very scathing letter to the offending cooperation, and bring the issue to the attention of the rest of the community. I know there are many other T-Mobile customers that were unable to get as much information concerning the issue, and even more that were forced to just accept the BS given to them by the all knowing customer service representatives.

In case any of you other disenfranchised T-Mobile customers are wondering, you can submit a complaint via email by going to this URL and submitting a complaint to the “Products and Services” topic, and “text Messaging” sub-topic. Just as an example, following is my own personal letter to their customer support.

As a new T-Mobile customer, I must say I was quite excited to sign-up with T-Mobile, and purchased a new T-Mobile Shadow, and the unlimited texting plan. The service(s) explained to me by the sales representative, and the information gathered from your website prior to signing up seemed as though it would be a great deal for the cost.

It has since come to my attention (after being on the phone for several hours with your customer service representatives) that T-Mobile has made the erroneous decision to block what they refer to as “3rd party” SMS shortcodes. After multiple calls to technical support, and several other departments including the flexpay account department, the billing department, the PDA and smartphone department, and several other non-discriminant departments, I have received several different answers, from several different representatives, concerning this matter.

I was finally informed by your escalated technical support that T-Mobile in fact does NOT allow SMS shortcodes from outside their own company, and that I had no recourse other than to cancel my account, and pay the $200.00 early termination fee that would be assessed at termination. This response from a representative of your own company is quite disheartening and does not, in anyway, leave me with a positive impression of the company I was once so enthused to be a customer of.

While the very unsympathetic representative was technically correct in that T-Mobile has no legal obligation to support shortcodes, it is quite unscrupulous of T-Mobile to in fact disallow SMS shortcodes, and instruct all but the escalated technical support to inform your customers that they are in fact supported.

After a lot of digging, and a lot of research, I have come to the conclusion that I am in no way the only T-Mobile customer that is having this issue. I have also learned that T-Mobile is, in fact, currently the ONLY major courier that DOES block SMS shortcodes from outside their own company. As per several customers that have been with T-Mobile for quite some time, it has been made public that T-Mobile did in fact support SMS shortcodes once upon a time; making this decision to block said services a recent one.

Fearing a $200.00 early-termination, I’m sure you will be ecstatic to hear that I (like many other customers) will be remaining with T-Mobile for the duration of my current contract. All though I have become a disenfranchised customer, along side many others, primarily due to your voracious policy of limiting the abilities of your customers to embrace new technologies, and a tendency of your customer support to either be ill-informed of your internal policies, or outright instructed to provide disinformation to your customers.

I hope that T-Mobile can show that it is in fact a customer oriented company, and alter it’s current policy to block such services that customers of ever other major wireless provider are allowed access to without additional charges or nightmarish and lengthy calls to technical support.

I would like to once again be able to enthusiastically encourage those I know to also join up with T-Mobile, but am currently unable to do so, due to your current policies, and attitude towards your customers when it comes to the transparency of said policies.

Thank you for your time,
Dustin Hansen – T-Mobile Customer

I’m looking to take suggestions for what anyone would actually want to see changed, or added.

That’s a total compression of about 64%, that’s just frickin’ amazing, as I stated earlier. I take back everything bad I ever said about Apache. I don’t exactly ever remember saying anything bad about them, but if I ever have, I take it back.

Anyway, this really excited me, and I thought I would share it with you all, you may carry on now.

After using Ninjawords for a while, and being the programmer that I am, I found myself picking it apart thinking “how cool would it be if it did [insert something cool here]“. I really liked the way Ninjawords worked, and especially the speed at which it was able to define words; I just felt there was more that it could, or rather should do. I started off just wanting to be able to remove words from a word list once they’ve been defined. Then I wanted to be able to choose the correct spelling if I misspelled a word, or even simply just check the spelling of a word. That’s when I began Maveno.us.

I am still impressed with Ninjaword’s speed, and will more than likely never be quite as quick as it is. I understand that some speed is going to have to be sacrificed in order to provide the additional features I felt were missing. I have come to terms with this, and only cry about it every once in a while now.

There are still a lot of things that I feel Maveno.us can do, which is all laid out in the roadmap. Anyway, I’ll stop my rambling here, and get back to work.

If you’ve checked out the road map, you’ll see where mavenous is headed in the future, and we are always open to user suggestions. I really hope to have other language support in the future, and welcome anyone well versed in other languages to contribute their time translating the site. There really isn’t all that much text that needs to be translated, and if anyone is interested, by all means, let us know!

Well folks, that’s all for now, gonna get back to coding, you are now free to move about your office chair.