Microsoft To Acquire SwiftKey Predictive Keyboard Technology Company For $250M (hothardware.com)
MojoKid writes: SwiftKey has been one of the more popular predictive keyboard offerings in the mobile space since it was first released in beta form on the Android market back in 2010. What made SwiftKey so appealing was its intelligent predictive texting technology. SwiftKey isn't a simple keyboard replacement. Rather, the software uses a combination of artificial intelligence technologies that give it the ability to learn usage patterns and predict the next word the user most likely intends to type. SwiftKey refines its predictions, learning over time by analyzing data from SMS, Facebook, and Twitter messages, then offering predictions based on the text being entered at the time. It is estimated that SwiftKey is installed on upwards of 500 million mobile devices. According to reports, Microsoft is apparently buying the UK-based company for a cool $250 Million. What Microsoft intends to do with SwiftKey is not clear just yet, but the company has been purchasing mobile apps at a good clip as of late.
The app market is where the smart money is now.
(Not games though, Zynga's $180M purchase of Draw Something was insanely moronic.)
Summation 2
So what's everybody's favorite alternative, since SwiftKey is owned by a company that is nowadays renowned for its spyware and keylogging?
Does SwiftKey phone home what users are typing? $250 million seems a lot for an input method, more reasonable for a large set of data for them to analyze.
It's how they make predictive typing work.
Half of me is delighted that W10 could actually get a useful keyboard. Half of me thinks they will utterly fumble the transition and, like most things MS tries to bolt on, it will suck horribly but will become the standard (And only) keyboard on W10 touch.
All of me knows that they will be using the data to improve their marketing side of the business. I'd worry about that, but I sold my soul (or at least all of my worldly data) to Google a decade ago, and it's always easier the second time.
Is it just my observation, or are there way too many stupid people in the world?
Based on recent attempts to push telemetry via updates and the monitoring built in to Windows 10, using SwiftKey as a key logger to gather information on mobile users seems possible.
has it ever occurred to you why android phones are all twenty cores and 8GB of RAM and still freeze all the time and the battery drops like your credit card available balance in a casino?
What Microsoft intends to do with SwiftKey is not clear just yet
Ruin it, then stuff it full of Windows/Office money in the vain hope that this will hide their incompetence at diversifying.
They could log keystrokes without buying SwiftKey.
Maybe they just want to add a great keyboard to their windows phones, without allowing 3rd party keyboard support.
Microsoft really wants everyone's keystrokes, don't they?
This has been debunked. There is no keylogger. If you have a packet capture that says otherwise, feel free to correct everyone that bothered to look into it.
What other rationale is there to spend even $1 on a company that develops and maintains a product only to give it away to its customers free of charge?
Intellectual property.
Microsoft learned a long time ago that buying stuff that people already like is far easier than creating stuff that people like.
Log in or piss off.
So, what's a good alternative to Swiftkey?
Actually, I'm going to wait and see what happens. I use Swiftkey on my tablets (swype on my phones), and I'm not going to knee-jerk abandon it.
In the land of the blind, the one-eyed man is kinky.
Maybe Microsoft is acquiring more weapons for its mobile patents war chest. Or defense, given the madness of the IP landscape that ensures only the big boys can innovate.
I find the Windows Phone's default swipe keyboard to be the best I have used. I find it marginally better than both HTC's swipe keyboard and also Google's keyboard.
Predictive keyboard? Sounds like autocorrect to me. And I hate those things. They make too many assumptions. I mean, how does it know I wasn't going to write about my "gigantic throbbing coconspirator"?
Purely to play Devil's advocate, but why would a keylogger show in a packet capture?
Microsoft sends home enough payloads of data that, if one was designing a super secret key logging mechanism, you'd just save up the data and send it with that stuff.
Sending packets with every keystroke would be wasteful and obvious.
Without seeing every data payload of what MS is including in their telemetry and other crap they've pushed into the OS, and accounting for all of it, I fail to see how you can make that conclusion.
If there's chunks of binary data MS won't tell you what it is, you have no way of knowing what's in it.
I have no idea what MS does and doesn't send, because I've never looked into it ... but hiding a keylogger from packet sniffing when you already call home?
That's not exactly rocket science. In fact, it's the kind of obvious solution when you're already sending other data.
Lost at C:>. Found at C.
"Ok let's try this out, M, swipe I, swipe C"
[clippy appeaers] "Say, it seems like you're trying to type Microsoft, should I just add it to the text box for you?"
"Go away you little..."
"Say, are you trying to type Fuschia? Let me add that for you..."
Microsoft is trying to 'innovate' another revolution it missed.
Sheesh, evil *and* a jerk. -- Jade
Yes, now we can have predictive key logging. Microsoft will know what you are going to type before you type it.
Imagine how much money they can make off that by buying things before you press the buy button and then selling it to you at a markup - all the stock brokers already do that.
Then please tell me what the hell these addresses do, which I blocked in my router:
134.170.30.202
137.116.81.24
204.79.197.200
23.218.212.69
65.39.117.230
65.55.108.23
or these ones which I blocked in my hosts file:
127.0.0.1 dns.msftncsi.com
127.0.0.1 ipv6.msftncsi.com
127.0.0.1 win10.ipv6.microsoft.com
127.0.0.1 ipv6.msftncsi.com.edgesuite.net
127.0.0.1 a978.i6g1.akamai.net
127.0.0.1 win10.ipv6.microsoft.com.nsatc.net
127.0.0.1 en-us.appex-rf.msn.com
127.0.0.1 v10.vortex-win.data.microsoft.com
127.0.0.1 client.wns.windows.com
127.0.0.1 wildcard.appex-rf.msn.com.edgesuite.net
127.0.0.1 v10.vortex-win.data.metron.life.com.nsatc.net
127.0.0.1 wns.notify.windows.com.akadns.net
127.0.0.1 americas2.notify.windows.com.akadns.net
127.0.0.1 travel.tile.appex.bing.com
127.0.0.1 www.bing.com
127.0.0.1 any.edge.bing.com
127.0.0.1 fe3.delivery.mp.microsoft.com
127.0.0.1 fe3.delivery.dsp.mp.microsoft.com.nsatc.net
127.0.0.1 ssw.live.com
127.0.0.1 ssw.live.com.nsatc.net
127.0.0.1 login.live.com
127.0.0.1 login.live.com.nsatc.net
127.0.0.1 directory.services.live.com
127.0.0.1 directory.services.live.com.akadns.net
127.0.0.1 bl3302.storage.live.com
127.0.0.1 skyapi.live.net
127.0.0.1 bl3302geo.storage.dkyprod.akadns.net
127.0.0.1 skyapi.skyprod.akadns.net
127.0.0.1 skydrive.wns.windows.com
127.0.0.1 register.mesh.com
127.0.0.1 BN1WNS2011508.wns.windows.com
127.0.0.1 settings-win.data.microsoft.com
127.0.0.1 settings.data.glbdns2.microsoft.com
127.0.0.1 OneSettings-bn2.metron.live.com.nsatc.net
127.0.0.1 watson.telemetry.microsoft.com
127.0.0.1 watson.telemetry.microsoft.com.nsatc.net
127.0.0.1 win8.ipv6.microsoft.com
127.0.0.1 go.microsoft.com
127.0.0.1 windows.policies.live.net
And I found all these myself, with tcpdump.
At a certain size, you can lo longer directly spend research money fast enough on just your own work. The only way get enough research results is to buy up results where you find them.
My suspicion is that they bought Swiftkey for the IP -- so they can license or sue.
sig: sauer
How? They need to control a dominant mobile keyboard for that. SwiftKey has decent market share in Android, but Microsoft, prior to this purchase, has no dominating keyboard.
If an app has learned enough about your working vocabulary and writing style to predict what you're going to type next, I bet it can figure out where you're doing the typing, no matter how anonymous you think you are.
I've calculated my velocity with such exquisite precision that I have no idea where I am.
If the deal does go thru, I will be uninstalling Swiftkey.
Problem is, I doubt the stock GOOGLE keyboard is an exemplar of anonymity and privacy either.
or these ones which I blocked in my hosts file...
Hope you don't mean the Windows's Hosts file. Wasn't it already found that Windows can ignore the Hosts file if it wants to for certain addresses?
That's just a case of the fox guarding the hen house.
Notice the first sentence... Unless Windows 10 can now bypass router blocks (at the IP level)
The SwiftKey personalization service, which is a feature of SwiftKey Cloud, accesses your recent content from online services that you specify, such as Gmail, Facebook and Twitter. It uses this content to build a personalized language model on our servers, which is then transferred to your device. This is an optimized view of the words and phrases that you use most often, and reflects your unique writing style. Your use of our personalization service means we may store and use data provided by you to develop and improve our Products. You have the right to have this data destroyed, as outlined below.
Arghhh.... I can feel apk's footsteps coming down the hall...