While Kik has been in the news quite a bit lately with it's popularity, it's taken a rather grim twist for the fellas over at Kik and potentially at RIM itself. Kik was a popular multi-platform messaging system very similar to BlackBerry Messenger; I say was merely because on RIM's BlackBerry OS it is not going to continue to be an offered application. RIM is reportedly suing Kik for patent infringement however, we don't know which patent as of yet. While I 100% agree RIM has the right to sue over property that rightfully belongs to them, I think picking on the little guy is a bit absurd. As far as I'm aware of, RIM pulled the app, rejected their pushing capabilities and is NOW suing them all in a very short period of time; either RIM has something big up their sleeves or they are potentially making themselves out to look like the bad guys here.
Shortly after RIM pulled Kik and revoked it's keys, Kik put up a plea to RIM saying "On behalf of our nearly one million Kik users on Blackberry devices, we truly hope RIM reverses these steps." I do agree that RIM should allow BlackBerry users to use whichever messaging platform they choose, however, when that platform violates any terms of service or violates copyright infringement laws, they deserved to be punished. The steps towards enforcing the punishment and the punishment itself need to be done in a manner that doesn't make RIM look like the bad guys. RIM has had nothing but great things recently and this little incident has made quite a few people turn to the other cheek (the one with Android and iPhone on it).
There have also been reports that they might not only have been copyright infringements but a security flaw as well which may be the reason it was taken down so swiftly. According to a member who reported a security flaw within Kik:
Personally, that's a big security flaw, how does something along those lines just slip right through development and the scope of the project itself? The owner of Kik has apologized numerous times on the website where this was reported, but, that I'm aware of, it was never solved and may now be too little too late.Originally Posted by wildta