Sign in with
Sign up | Sign in
Your question
Closed

BBM for Android and iPhone Not Lauching This Week

Last response: in News comments
Share
September 24, 2013 4:01:26 PM

One of the laid-off engineers probably posted the older version of the app knowing that it would cause the issue
September 24, 2013 7:05:41 PM

i don't think the older version causing the problem, the problem is their server and system can't handle the traffic, and they don't know what to do :D 
Related resources
September 24, 2013 10:30:09 PM

It's quite simple really. This is a service, not a standalone application. Therefore they need to block the leaked build so it does not impact legitimate users. Still, I'd imagine redirecting IP traffic, changing a DNS name and a few small fixes should suffice and not cause a significant delay... If the traffic is encrypted, a simple revocation of a crypto key should suffice even.
September 25, 2013 12:46:46 AM

I agree with Izman Quaasalmy. I really doubt the beta apps is the problems...

They also do not released bbm for android on time where android supposed get first before ios (for "whatever" reason), so people start looking for those beta apps..

IMO there a bigger scheme of this (not in a good way)
September 26, 2013 11:46:26 AM

Izman and rdc are obviously quite dumb.

When you make an application with 8 million current users, you always have the power to take on 10. When you open it up to over 200million additional customers, you should account for at least 50m, but if there is a pirate copy out there that means that one user takes up two or five worth of bandwidth, suddenly your previous capacity ot take on 42million new customers is reduced to taking on 8.5m new customers, far too little.

It's also incredibly likely that a pre-release system uses 5 or more times the bandwidth, as the debug data has to be communicated somehow and modifying the phone itself to JTAG or display debug data has the potential to hide, disguise, or entirely bypass the source of the bug or the bug itself.

If you have a number of closed platforms to test the hardware on, the last thing you should do is modify the test platform to record the data. No, you should have the data remotely forwarded to another source via a commonly used data route. With PCs it used to be Serial Ports, and now it's sometimes Ethernet sometimes USB. With a phone it has to be wireless, bluetooth or USB, and I suppose they chose wireless to-the-server debugging.
!