Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the important part of the article was that he was encouraging the simplest solution to interface needs. In this regard I totally agree with him. I think some of the stuff they've added to consumer products has fallen into a weird modular development space.

"Oh, you want us to add a touch responsive display to a refrigerator rather than using mechanical buttons?"

Then they throw the kitchen sink at it. Once you've installed that touch screen and the hardware needed to control it, you might as well add the ability to control ice cube production from a mobile app. Since you're already there, you might as well give them the ability to Tweet that they just pulled a slice of double-chocolate cake out of the fridge.

Just because these components are capable of acting as small computing devices doesn't mean they should be utilized like one.

The entire time I'm reading the article I'm cringing too. I don't want a device that just operates as a universal key for everything I do during my day. I walk up, order a sandwich and they charge my account without any physical transaction happening and no passcode required to open my phone? What's to stop someone else from doing the same thing?

A car that opens it doors and starts its engines because I have a phone in my pocket? Same issue.

Steal someone's phone and you steal the keys to their life then (really easily).



"What's to stop someone else from doing the same thing?"

No different than what happens now. When your wallet gets stolen you call the credit card companies to cancel your cards.

Yes, sometimes when you order a sandwich you don't want to pay for it immediately, and sometimes when you get close to your car you don't want it to unlock. But those times are the exceptions. The exceptions are the times that you should deal with a more complex interface. The other 99% of the time it should do the right thing automatically.


Renault experimented the no-interface approach around 2000 with their car. They had a wireless key that would lock/unlock the key depending how far you were from the car.

Later they added a button to lock/unlock the car because people were not comfortable with the technology:

1. They would get inside their house, drop the key, then get back out to check that the car was locked.

2. You could not just park in front of a shop, because the car could get unlocked while shopping if you got too close. Any activity around the car could end-up in continuous stream of locking/unlocking.

Unfortunately, making sure that nobody can enter your car is one of the primary concern of car user. And if it is not, sooner or later, your car insurance will convince you otherwise.


There are supposed to be checks in place to stop things like credit card theft from having an immediate affect though. Cashiers should be asking for ID and checking your signature. It's actually a control that is supposed to occur in stores.

Someone grabs your phone and gets free meals? What controls are there on that interface?

I don't even have a dongle on my keys to unlock my car remotely. Doesn't bother me in the slightest.


There are supposed to be checks in place to stop things like credit card theft from having an immediate affect though.

> Cashiers should be asking for ID and checking your signature. It's actually a control that is supposed to occur in stores.

No, it's not. For small purchases, merchants are not required by the credit card companies to check ID or to even ask for a signature.

And for larger purchases, it typically still doesn't happen. My credit card has "ask for photo ID" written on the back instead of a signature. Even with this, I get asked for ID maybe once every two months. Checks that are supposed to happen don't matter. Only checks that actually happen matter.

> Someone grabs your phone and gets free meals? What controls are there on that interface?

Well, if you're using the system Dorsey was describing, your photo pops up every time you go to pay. So the cashier sees it without asking for it. So if I try to pay with your phone, the cashier can say, "I'm sorry, but you don't look much like rbellio. Should I call my manager over?"


It's not a credit card company control, it's a merchant control to limit liability.

Having worked in loss prevention in the past, I know that the intent is to make sure these controls are checked an maintained. The issue you run into with cashiers is that the turn over rate is usually so high, or those checks aren't done frequently enough that the controls become lax.

Why would merchants be so concerned with these controls, you might ask? Because if it can be proven that the charges were made fraudulently, the merchant becomes responsible for them. If someone buys $300 of stuff from a store using your credit card, the store loses that cash.


Why are you bringing this control up if you know that it's 1) optional, 2) poorly implemented, 3) not actually intended to protect you?


If something so simple is deemed optional, how many merchants do you think are going to be willing to pay to have the equipment to view your picture when they try to charge your phone.

Speaking of pictures associated with your phone. Where is this picture going to be stored? On the phone? Where, if someone steals it, they could replace it? Should we have a national database then that relates your phone number to an image of you?


Actually merchants are specifically prohibited from asking for ID when a card is signed. That's under the merchant agreement they have with Visa and Mastercard.


So, the training I got when I worked as a cashier way back when must have been a fluke, even though it was with one of the largest retail companies in the country.


I think the author of the article was conflating "interface" with "GUI".

Yeah, absolutely. Don't put a GUI as part of my car controls; that's stupid. But the wheel, pedals and shifter are certainly an interface.


But you can eliminate that interface too, with sufficiently advanced driverless cars that know (from e.g. your habits or calendar) where you want to go.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: