In fact, even after last year's breach, Target clearly isn't happy offloading that nightmare. They're currently teting CurrentC: http://www.dispatch.com/content/stories/business/2014/11/10/...
6,372 karma · joined September 27, 2009
In fact, even after last year's breach, Target clearly isn't happy offloading that nightmare. They're currently teting CurrentC: http://www.dispatch.com/content/stories/business/2014/11/10/...
Yes, merchants think that getting additional customer-identifying information that forces them to run extra analyses on the mountains of transaction data they warehouse is a huge burden they'd like to be relieved of.
</sarcasm>
Google Wallet is card-present for the merchant, but card-not-present between Google and the consumer. I guess that means Google is eating the difference between the two rates (and/or has other tricks up their sleeve).
With the benefit of hindsight, we can see that Android phones didn't get AIV until it was clear the Fire Phone flopped. And unless you mess around with sideloading, it still isn't supported on Android tablets (non-cellular ones, at least). And, from what I've heard, Android TV (or at least ADT-1) doesn't support the Google TV app even though it probably works (or, at worst, can be trivially made to).
My answer is: it depends. My wife and I have well over a thousand books on Kindle, but I've got a growing library of Kobo books (from taking advantage of some impressive discount coupons) and almost everything DRM-free I get outside a major ebookstore (e.g. books bought directly from publishers or authors) goes straight into Google Books (they're the best with uploads).
Yes, having books scattered across multiple apps isn't perfect, but it isn't that big a deal, either. Amazon has a significant edge (especially with customer service), but it is nowhere near insurmountable.
Publishers routinely demand that authors submit their next book (or even everything you write in the same genre for years) to them first and even if they reject it they have the right to match any offer you get later.
How many VCs demand rights over your next N years of startups?
Or we could talk about high-discount clauses: Where publishers get a bigger percentage when your books are discounted below a threshold they claim is unlikely... Only to turn around and encourage retailers (including Amazon) to discount your book just below that threshold - where they make more per book and you make substantially less.
How often do VCs make more money by going behind your back to convince an acquirer to pay less?
Or we could talk about rights reversion games, shuffling sales through shell companies cut royalties and on and on and on.
I know VCs can be ruthless, underhanded and worse, but traditional publishers can make them look like kittens by comparison.
India shouldn't be in a Canadian's comparison set with respect to health care systems. The resource differences are too great to learn anything useful about the impact of other dimensions. Can you name a developed country with a health care system as or more free market than the American one?
As for your experience in India... Consider how much wealthier you are than the average Indian. If you were that much wealthier than the average American, do you really think you'd have any complaints about the American health care system? Conversely, what do you think your experience would have been if your wealth relative to the average American has instead been your wealth relative to the average Indian?
Unless someone is doing something big or strategic to Apple (and random app piracy doesn't qualify, IMO), I just don't see it. Chasing "rogue" enterprise certs is all cost (time, effort, energy, risk of angering legitimate enterprise customers) for little to no benefit.
1. You can get Amazon Instant Video on your cellular tablet if you use the Amazon Appstore directly. It's kinda vague on the distinction between a cellular tablet and a phone.
2. Amazon Instant Video works just fine if you sideload the Amazon for Phones and Amazon Instant Video apps.
With SD cards, the "old way" had serious problems (security and robustness issues because apps could stomp on each other's data, all sorts of complexity and confusion on multi-user devices, orphaning private app data on the SD card when apps are uninstalled, no sensible backup possibilities for apps that depend on SD card data, apps not knowing whether data would be on internal or external storage because "/sdcard" means different things on different devices, etc.) that Google is trying to solve.
Google's solution required a compatibility break, but that doesn't mean they're just dropping all of the SD card use cases. KitKat introduced app-specific private data on external storage, apps can enable some simple sharing by the adding read permissions to their private data, the storage access framework can be used to support more complex structured sharing between and so on. Among other things, Google is even adding a new API in Android L that lets apps properly publish media (images, audio, video, etc.) from their private storage (including private SD card storage, which is when it is most useful) to the shared MediaStore.
Is this transition bumpy? Absolutely, especially for people who upgrade their OS or use an old SD card on a new device. Nevertheless, I don't think Google will go back no matter how loud the cries get. Google tried neglecting SD cards from Honeycomb through Jelly Bean (hoping they'd "wither away", I suspect). That failed. Now they have no choice but to do the hard work of putting external storage on a reasonable foundation.
None of them want to. That's not an accident. It's because Amazon isn't giving them an opening by abusing either customers or suppliers. Publishers can claim otherwise, but they're not putting their money where their mouths are. They're not walking away from Amazon, nor can they even demonstrate that they're getting clearly better terms from anyone else.
And, if you keep your headquarters in Cupertino, quite possibly from US authorities as well (see the currently in-progress Microsoft case about access to servers in Ireland).
I can understand the marketing benefits Apple sees in making these disingenuous privacy claims. I'd be willing to call that "just business" except for one thing: Trying to persuade people they have a technological solution will necessarily get in the way of the absolutely vital political project of destroying the political and legal foundations of the surveillance state.
I've seen people claim that there are SD/HD issues, but I haven't noticed (though, to be fair, a lot of my usage has been watching an SD TV show, so...).
It is. You just have to go to the Amazon Appstore and install the "phone" version of the Amazon app (the app is available in Google Play, but blocked for tablets there). Then that Amazon app can do the extra download of the Instant Video app/plugin and so on. It's working fine on my Nexus 7.
1. You will need Android support eventually (to go global, because users demand it, etc.).
2. If you try to add Android support later, you'll screw it up in ways that will be difficult to fix (e.g. porting iOS apps too slavishly, not taking advantage of Android-specific platform benefits, building a corporate culture that treats Android as second-class, etc.), especially since most of the best Android talent will want nothing to do with you.
Um, the Android Wear manufacturers may not have any secret plans of their own, but... The Android Wear OS developer is practically jumping up and down in the corner saying "I have secret plans! I have secret plans!" See, for instance:
http://www.cnet.com/news/google-says-android-wear-about-to-g...
This shouldn't be surprising. The existing Android Wear hardware is unusually powerful (a 2010 smartphone or better?) for what it is currently doing. Given the importance of battery life, that's a strange choice - unless more is coming.
I'd also note that the GP commenter works for the previously mentioned OS developer, and the comment seems entirely consistent with someone who knows more is coming, but can't do much beyond hinting at that.
If you're worried about merchant-level tracking, I think tokenization makes little or no difference. Quoting from the article:
"Tokenization is typically handled by the payment network, which (in some implementations) encrypts the credit card number right when you swipe it, sends it back for the token, and then provides that to the merchant to keep for things like refunds or customer tracking."
The only potential merchant-level tracking difficulty I can see is that tokens can be merchant-specific, which might make unified customer tracking more difficult after a merger. And even if financial institutions didn't provide services like post-merger token-matching (something I wouldn't bet on), plenty of merchants have quite a bit of experience using other signals to approximate that kind of matching.
Unless that's been fixed (I haven't come across any evidence one way or the other), you're not just worrying about Apple and the NSA: Your iMessages are vulnerable to anyone who can forge a certificate and MITM your connection to Apple's servers. I'd say that's a reasonably high bar except for one thing: I believe it covers the vast majority of corporate iPhones used on company-internal networks.
It may just be a coincidence, but it's hard not to notice that OS updates were faster before the US Nexus 7 LTE was certified on Verizon. Hopefully, the Android L update will be better, but I worry.
On the other, we've seen this movie before. Remember Verizon? The iPhone 5 (LTE and a screen-size bump)? NTT DoCoMo and China Mobile?
These were all supposed to be game-changers. And while they all helped Apple sell plenty of phones, the Android/iPhone game didn't really change.
I'm sure the iPhone 6 and 6+ will be very successful. But I'm going to need to see something more before I believe that this time the game really will change.