ikonst

Joined 14 years ago

Karma
91
Submissions
58
Member since
Jun 11
https://github.com/ikonst
View on Hacker News

Recent submissions

Comment · 1 year ago
Comment · 4 years ago
same for the railways: https://www.kommersant.ru/doc/5571565

not unthinkable such things will follow, but so far might be fake news

Comment · 5 years ago
It's the news article that was already widely published and a local take (not by any government body, "campaigners have called") in Scotland.
Comment · 6 years ago
Comment · 7 years ago
Reminds me of Perl's taint mode
Comment · 7 years ago
So it's not a status but just a per ride assessment -- if you appear disabled when the driver comes to pick you up, he should ask not to receive surge pay for that particular ride?
Comment · 7 years ago
Many of the bullet points are somewhat vague, but one is strangely specific:

> Prohibiting companies from charging passengers with disabilities higher prices during busy times.

First of all, what constitutes 'disability'?

How will passengers identify themselves as 'disabled' to the apps?

How would the companies store this highly private information? (think medical-info grade, not credit-card grade)

What will indemnify the companies from claims of discrimination, claims possible in light of the companies being aware of users' disabilities, information they never wanted to keep in the first place?

And finally, not to make it the main topic, but who would pay for this? That "surge pricing" you pay is, in turn, being paid to the drivers. The drivers are "chasing the surge'.

Comment · 8 years ago
Maybe not for the operation they're running, of which VoIP is only a small part.
Comment · 8 years ago
WebRTC is somewhat new and complex, and browser support varies greatly. I don't know what kind of unlimited resources behemoth you imagine Slack to be, but I can definitely see how doing consistently working cross-browser WebRTC would be too much effort to be able to pull off at a given time.
Comment · 8 years ago
Comment · 9 years ago
re Lyft: We detect recycled phone numbers, and we'll challenge you (or "not you") for further identification.

Phone recycling has been a much bigger problem for non-fraudulent cases, e.g. you pop-in a new SIM card and naively sign up for Lyft, getting the account of someone else (e.g. a tourist's). Fraudulent takeover of passengers' Lyft accounts hasn't been happening that much — fraudsters have a much easier time stealing credit card numbers than Lyft accounts.

Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
I've read similar stories before the current administration. Telling a CBP officer that you're going to be "paid to lecture" is not recommended. This is a kind of honesty that doesn't return a favor.
Comment · 9 years ago
I think Rogue Amoeba was already doing serial numbers etc. for their other products.

re Payments: Have you ever seen how easy Stripe is?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton