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

I like the sentiment of reducing user friction, but one statement sticks out to me:

> And we chose Facebook / Twitter / OAuth right? Nope. It's a shitty position to be in when you have this large, deaf middle-man between you and your customers. Period.

Isn't the user's mobile carrier in between? While it may look less restrictive at the moment, I wouldn't be surprised in the least if (insert-your-carrier-here) changed policies on their network that restricted sending the information you need.

It's better than the FB/T/Y/G/etc. dependency, but only as a form of the UI. I think you still have a dependency there, and that dependency could be more volatile than meets the eye.



Isn't that like saying the datacenter or upstream provider is in between? Kind of alarmist, no?


Not really -- most datacenters or upstream providers aren't really engaged or interested in the data your application uses (outside of illegal activities.)

Carriers are definitely concerned with the bits being passed around.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: