Skype is a polarizing product for telecom operators and customers. It is an application that lets customers abandon their historical phone services in favour of an encrypted Voice over Internet Protocol (VoIP) communications service that provides ‘free’ calls to computers and cheap rates when making a Skype-to-analogue/cellular phone service. For customers, it extends the choices presented to them and potentially reduces their monthly phone expenses.
The iPhone application for Skype has made headlines as telecom and smartphone manufacturers alike have actively and passively resisted, and ultimately relented, to permitting customers make Skype calls from their iPhones and other mobile devices. Apple has stated that they will not ‘jump through hoops’ to ensure that VoIP applications work through successive operating system updates, and AT&T’s poor data transmission systems likely made them somewhat hesitant to allow another bandwidth-heavy service onto their networks. What really got *me* interested in the Skype iPhone application, as a Canadian, was the following:
- Canadian customers can now install Skype on their iPhones;
- There was no place on the web that informed Skype users of how much data was consumed by the iPhone application when in use.
It was #2 that was particularly interesting. Canadian consumers tend to have fairly low default bandwidth caps with Rogers, the primary carrier of the iPhone in Canada, at 1GB in the basic iPhone plan. My thought was this: if the iPhone application actually consumed massive amounts of data Rogers would:
- Make a killing on the likely data overages as early adopters shifted over to Skype VoIP in favour of Rogers’ own voice services;
- If the application actually consumed a large amount of bandwidth, carriers might see it as ‘technically’ needing to be mediated using some system (perhaps deep packet inspection). Read more…
Deep Packet Inspection is being deploying by an increasing number of operators for a host of purposes, including content analysis, flow analysis, network management (broadly stated), network management as integrated with policy management, and behavioural advertising (to name a few). While BT, in the UK, has openly admitted to working with Phorm to bring behavioral advertising to its consumers, it now appears as though network owners are going to be analyzing Internet traffic from mobiles, as well as desktop and notebook computers.
The Guardian is reporting that in a recent GSMA trial to collect information of where mobile users’ are browsing, that “the UK’s five networks – 3, O2, Orange, T-Mobile and Vodafone – used deep packet inspection technology to collect data covering about half the UK’s entire mobile web traffic” (Source). There is no indication that this is presently being associated with customers’ geolocation, but this does suggest that DPI is gaining increasing acceptance in the UK as a means of tracking what people are doing. Apparently the weak regulatory responses in the UK are spurring companies to deploy DPI before they are left behind the rest of the pack. Read more…
I try to keep abreast of mobile-enabled geolocation software, and two of the largest contenders in this space (as I see it) are Google and Yahoo!. At the moment, Yahoo!’s Fire Eagle software has been publicly available (with an open API) for over a year (I talked about it previously) and, according to Ars Technica, about 70 third-party applications have been developed.
There are major updates coming to Fire Eagle:
…users will soon be seeing an ActionScript Fire Eagle library and a Mozilla Firefox geo-plugin that locates users via WiFi MAC addresses. Also coming up are new XMPP libraries. (Source)
It’s the focus on the Firefox geo-plugin that I think will be most interesting to watch. Given the Mozilla is currently developing their Fennec browser for mobile environments, it suggests that the Fire Eagle plugin could come to phones and other mobile devices that are Internet-by-WiFi but not GPS or data plan enabled. Using a browser plugin, it should be possible to identify your location on a map simply by being in vicinity to wireless APs, regardless of whether you can actually authenticate to them (similar to how users with iPod Touches can currently roughly locate themselves on Google Maps via WiFi MAC address detection). Below is an image of Mozilla’s beta-version of Fennec. Read more…
Last year I authored a post entitled “Mobiles and Your Identity“, where I attempted to unpack some of the privacy and surveillance concerns that are associated with smart phones, such as RIM’s Blackberry and Apple’s iPhone. In particular, I focused on the dangers that were associated with the theft of a mobile device – vast swathes of both your own personal data, as well as the personal information of your colleagues and friends, can be put at risk by failing to protect your device with passwords, kill switches, and so forth.
Mark Nestmann, over at “Preserving Your Privacy and More” has a couple posts discussing the risks that smart phones pose if a government authority arrests you (in the US). He notes that, in a recent case in Kansas, police examined a suspect’s mobile phone data to collect call records. When the case was brought to the Supreme Court, the Court found that since the smart phone’s records were held in a ‘container’ (i.e. the phone itself) that the police were within their rights to search the phone records. Mark notes that this ruling does not apply to all US states – several have more sensitive privacy laws – but leaves us with the warning that because laws of analogue search are being applied to digital devices that it is best to limit the data stored on smart phones (and mobile digital devices in general). Read more…
