Hacker Newsnew | past | comments | ask | show | jobs | submit | ikonst's commentslogin

yaml: https://www.bram.us/2022/01/11/yaml-the-norway-problem/

bash: errexit depends on caller's context, will utterly fail you one day: https://lists.gnu.org/archive/html/bug-bash/2012-12/msg00093...


Added


same for the railways: https://www.kommersant.ru/doc/5571565

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


And to be honest they don't really need to anyway, the flights are full.


It's the news article that was already widely published and a local take (not by any government body, "campaigners have called") in Scotland.


Same (growing up in Israel). Didn’t realize it’s “gay” until much later.

Here’s from 1992: https://youtu.be/rQTbSFojYRE


Reminds me of Perl's taint mode


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'.


I would assume the definition of disabled at play here is related to the equipment of the car e.g. wheelchair lift, or service required e.g. driver getting out of the car to help someone in or out of the car.


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?


I interpreted that not as "disabled people don't pay surge pricing" but instead as "disabled people pay the same rate as nondisabled people, even when demand is high."


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.


This is apparently largely because Chrome's implementation of WebRTC has been less standards compliant than that of Firefox. See https://twitter.com/adambroach/status/959298097674305537 (by one of the WebRTC developers).


$250M sounds pretty behemotish?


Maybe not for the operation they're running, of which VoIP is only a small part.


Yeah, I was somewhat surprised by those. "Classes" on domestic flights in the USSR?! And yeah, GUM was (and still is) a department store for Soviet citizens - https://en.wikipedia.org/wiki/GUM_(department_store).


Actually I won't be surprised about classes, given that railway trains had up to 5 different classes of carriages.


No, long-distance trains had four classes: SV (two beds per cabin), Coupe (four beds per cabin), Platzkart (six beds per cabin) and Sitting (no beds, just benches). This classification goes back to Tzar (pre-revolution) times.

It has nothing to do with air transportation which has been developed in Soviet era, where everebody was equal.

edit: minor mistakes.


Weren't there also Soft ("мягкий", two posh beds per cabin)?


This is exactly SV ("спальный вагон").

https://ru.wikipedia.org/wiki/%D0%A1%D0%BF%D0%B0%D0%BB%D1%8C...


Apparently it's a different thing:

https://www.ozon.travel/help/railway/preparation/trains/

As far as I understand, М has private bathroom but СВ doesn't. It's confusing but I'm sure I saw them sold at different prices.


Are we discussing 1982 or 2017? :-)

There were no bathtubs on the trains in 1980-s in Soviet Union...


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.



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

Search: