Debit cards can't be used without a PIN number, right? Target indicates that there is no evidence PIN numbers were compromised, so even if the cards got stolen, they're not that useful without brute-forcing the PIN. As such, I would think credit cards are more valuable to thieves.
What you do is you a separate list of known pins and work out the most likely pin is. Then you assume that all of your new Debit cards have that pin. Most won't have that pin, but for many of them you'll now have a working pin. For those you did not ever enter a wrong pin, so any sort of brute-force attempt detection software will never have any reason to suspect a thing.
You can use a debit card as a credit card in most cases though. If you hit cancel on the PIN prompt, it gives you the option to sign and charge as credit.
True, however my understanding is that, by contract, debit cards via Visa/Mastercard have the same protections as credit cards. So consumers can submit claims against fraudulent transactions the same way they would via a credit card.
The difference is that since they are backed by your bank account (rather than a running balance that you owe the credit card company or bank), the money comes directly out of your bank account. Depending on your bank's policies, even an immediate refund (with no fraud involved) might take a couple of weeks to credit back to your account. So, sure you might be made whole again in the end, but you are still out the cash in the meantime.
That may or may not matter to you depending on your financial situation, but it's probably much better to be in a position where you are debating/challenging what you owe rather than what someone else owes you.
Note: I know that the mechanics are slightly different when you "run it as a credit card" rather than a debit card, but you may be in the same boat if the money has already left your bank account (unless Visa or MasterCard lean on the bank to make things go faster in such situations).
Rather than losing credit against your credit limit, however, while awaiting resolution by your bank one would be out actual cash. Credit card companies act like actual cash is more valuable than credit - lower cash withdrawal limits, higher interest - and I'd agree.
I think it's the opposite. With Google's change, the sender can more accurately find out if you've opened the email, since a request to download the image will be made as soon as you open the email. However, what the sender doesn't get now is IP, location, and browser data.
Well, an appropriate solution would be to 'open, package and store' the email at the time of receipt, not reading - that may cost some resources of extra bandwidth and storage, but would provide a better functionality and permanence in case of opening that email two years later when the sending company and their servers may be out of business.
I think that's a great feature. Loading images manually is always annoying and isn't a great user experience. Novice user's don't always understand why it's risky and they probably opt to display the images anyways.
However, one interesting question is how can third-party analytics will workaround this? Is there a way? Given that gmail holds a large market share of email users, this is really going to negatively affect the usefulness of such services.
What issues are you facing exactly? I've been successfully developing Scala apps since IntelliJ 12 with no issues. It's leaps and bounds better than Eclipse. One thing to note that for sbt-based projects, I recommend generating the IntelliJ project from https://github.com/mpeltonen/sbt-idea
Getting it to work with SBT. Even generating the project with sbt idea I still can't get it to compile correctly. And I still haven't been able to get it attach a debugger.
I think the current issue is with SBT 0.13 which isn't supported by them right now.
I'm using SBT 0.13 on a fairly complex project. Not sure why it wouldn't work for you. What kind of project is it? Any specific frameworks you're using that are causing compilation errors?
Are you doing "sbt idea" or "play idea?" From what I recall, "sbt idea" was broken, while doing it using the play launcher works, as they have some broken dependencies.
Note that even with the changed default to 'acknowledged', data is not guaranteed to have been written to the journal. So, there is still no full durability in writes (by default) and there is a chance data might be lost (e.g. a mongod instance crashes).
I've always believed it's time for Apple to embrace running some of their software on other platforms. Not only would it take the competitive advantage away from other companies providing multi-platform products, but it would also show confidence in their products that users will ultimately use their products for the best experience. Sure, some products may not make sense on other platforms (e.g., Mac OS X), but many others do make sense.
In many ways, history is repeating itself here with Microsoft and Apple 20 years ago.
I think that's a bit of a hyperbole. If I'm asked by someone for a recommendation, but I'm not comfortable recommending him/her, chances are I will simply ignore the request. If I do write a recommendation, it will most likely be on things the positive things I've seen about the person.
Assuming people in general approach recommendations in the same way, LinkedIn recommendations are good at identifying strengths of a person, but not weaknesses. In that aspect, they're not total junk.
Obviously, I wouldn't base hiring decisions on LinkedIn recommendations, just like I won't base such decisions on letter references, but they can be a small factor that influences the overall decision (after an on-site interview for example).
> Visa, MasterCard, and co. have rules that effectively prevent you from using the same backends in different areas.
What's the reasoning behind that restriction? Could you just re-use your backend stack, but use a different data center / machines, that's isolated from the backend of other countries?
It's because the banks that issue credit cards have most of the negotiating leverage, and they don't want giant US banks competing on their territory on the payment acceptance side. As a result, you need to use a European bank to accept payments in Europe, a Latin American bank in Latin America, and so on. The payments industry is full of these non-obvious (and unfortunate...) power dynamics.
