Re:Introducing the Uber Request Endpoint
by nowarninglabel on Tuesday March 17, 2015 @03:27PM
(#9220619)
That third one reads like something out of a Gibson novel. Might work best with a pre-defined group of people (e.g., models in an agency) or something similar.
[ Parent
| on HN ]
Re:Introducing the Uber Request Endpoint
by toomuchtodo on Tuesday March 17, 2015 @04:03PM
(#9220963)
"like something out of a Gibson novel.", "models in an agency".
While not politically correct, it would be interesting to run an outcall escort service with this. Throw in an AirBNB API...
Disclaimer: The above is just a thought. I do not condone this use case.
This is what chatroulette should have turned into.
Re:Introducing the Uber Request Endpoint
by toomuchtodo on Tuesday March 17, 2015 @05:33PM
(#9221682)
Or Tinder even.
Re:Introducing the Uber Request Endpoint
by NeutronBoy on Tuesday March 17, 2015 @06:08PM
(#9221934)
An app for blind dates. Combines Tinder, Yelp, Uber, and Airbnb, with a pretty workflow over the top. Call it 'Dial-a-date'.
Airbnb might be a bit presumptuous.
Re:Introducing the Uber Request Endpoint
by aceperry on Wednesday March 18, 2015 @01:16AM
(#9223755)
You're giving Uber some ideas.
Re:Introducing the Uber Request Endpoint
by philip1209 on Tuesday March 17, 2015 @03:37PM
(#9220707)
There could be all kinds of uses. Imagine a product launch event - "We need to pack a room so the press is impressed. Want anybody and everybody - tell them we have free food."
That'll get them to the location, but how long will they stick around.
As long as the food is free and they are not yet satisfied. Drip feed them.