Skip to main content

Limited "unlimited" plans available in Czech T-Mobile

By
Ufff, Czech T-Mobile sux! Czech is the country having the worst set of operators within emerging markets. Before almost two years I have conclude the agreement with T-Mobile. Unlimited whenever minutes to five numbers for 500 czech crowns per month. Looks good.

Till next month, T-Mobile is changing the agreement to 300 whenever minutes in the same price. Sounds almost illegal. I don't want to T-Mobile wrong, you can quit your agreement but you have to do it 20 days before new policy will start to serve. I'll bet that 90% of customers let it alone.

Honestly, described policy change comes in useful to me. I have consider to leave T-Mobile to Vodafone in four months but I'm (actually was) still under contract so I can legally quit my contract right now. Good for me but I don't understand the arrogance of T-Mobile guys.

Beside this issue I'm really disappointed of their mobile internet. I'm paying 10 euro per month to 100MB FUP mobile internet with port restriction. It means that sometimes I get invoice having variable amount of paid internet. Why? I run Twitter or Facebook app which doesn't use standard 80 port. It sucks, it really sucks!

Czech T-Mobile is really funny company at all. Their web portal mainly doesn't work. I got 50% failure last month. I would like to know which company make this terrible piece of **** for them.

The worst thing? I believe that they can't afford such poor approach to customer in original T-Mobile country - Germany. But we still live in Czech.
Labels:

Comments

Post a Comment

Popular posts from this blog

Performance Battle of NoSQL blob storages #1: Cassandra

By
Preface We spend last five years on HP Service Virtualization using MsSQL database . Non-clustered server. Our app utilizes this system for all kinds of persistence. No polyglot so far. As we tuned the performance of the response time - we started at 700ms/call and we achieved couple milliseconds per call at the end when DB involved - we had to learn a lot of stuff. Transactions, lock escalation , isolation levels , clustered and non clustered indexes, buffered reading, index structure and it's persistence, GUID ids in clustered indexes , bulk importing , omit slow joins, sparse indexes, and so on. We also rewrite part of NHibernate to support multiple tables for one entity type which allows use scaling up without lock escalation. It was good time. The end also showed us that famous Oracle has half of our favorite features once we decided to support this database. Well, as I'm thinking about all issues which we encountered during the development, unpredictive behavio
3 comments
Read more

ETCD: POST vs. PUT understanding

By
ETCD is distributed key value store used as a core component in CoreOS . I've already send a post earlier this week. Here is a page describing how to use ETCD basic commands = ETCD API. Code snippets placed in a page mostly use put , but ETCD allows to use post as well.  Most of us understand differences between those two commands in a notion of a REST(ful) service, but how does it work in key value store? POST Example over many words. curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" Two same command result into following content: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 { "action" : "get" , "node" : { "key" : "/test" , "dir" : true , "nodes" : [ { "key" : "/test/194" , "value" : &
2 comments
Read more