Interesting post. One detail I don’t see is how the ROE info actually tells you what currency to convert to. I see the exchange rate calculation but how do you know what the final units are?
"This ticket was priced in GBP, not INR. Because the journey originated in Manchester, the fare is denominated in the currency of the origin country: the United Kingdom."
So: the currency is the one for the country of origin.
The post is “here’s what I do”, not “here’s what you should do and then confront the team about the results.” It’s just showing you a quick way to get some insights. It’s not even guaranteeing it’s accurate, just showing you some things you might be able to draw some quick conclusions on.
I’m not sure why HN attracts this need to poke holes in interesting observations to “prove” they aren’t actually interesting.
Some of us have watched it ratchet up since the 80’s, when there were no such restrictions. The fact that some people hit a threshold and decide to stop putting up with it isn’t surprising.
My iCloud is full. Every once in a while my iPhone nags me to upgrade for a few days in a row and I tell it no and it goes away for 6 months or so. My Mac has never once nagged me about iCloud storage.
I think there’s debate (which I don’t want to participate in) over whether or not invisible characters have their uses in Unicode. But I hope we can all agree that invisible characters have no business in code, and banishing them is reasonable.
We need a new suite of utilities with defined R/W/X properties, like a find that can't -exec arbitrary programs. Ideally the programs would have a standard parseable manifest.
I've seen this before with sodoers programs including powerful tools. Saw one today with make, just gobsmacked.
Laws and lawmakers just concern themselves with making broad "laws" with little regard to specificity and applicability. California, Colorado and Illinois mandate OS "providers" to generate a signal. It is a copy pasted bill with little grounding in reality but a lawmaker is not going to say no "protecting children".
Pushed by AVPA - a group of companies standing to profit from this: LexisNexis, some Thiel corp, etc.
California's law explicitly requires the system and apps to take the user's word for it and not use other information to determine age, which more and more feels to me like kind of a brilliant move to cut the legs out from under other attempts to use the same for surveillance while still satisfying all the surface-level "protect children" sound bites.
You missed US states competing on setting up age verification legislation that lets anyone sue any developer who produces systems that don't do age verification for life-destroying amounts of money.
Eh private prosecutions and third party standing are generally disfavored to such an extent that sure, attention-whoring legislators will propose it, but whether it even passes constitutional muster on the state level is an open question, and open in every state.
For what it's worth, the "verification" in the California law (not a bill, it's already passed and takes effect 2027) is basically the Steam birthdate popup interstitial. There's explicitly no actual link to any outside information, just requiring that the system save a value the user sets and then that apps use that value for any age gating.
> And Starlink / xAI is going to shoot them into space.
I highly doubt that. They claim they want to shoot them into space, but I don’t believe a word of it until I see it happen (and see it work). It’s no more real than hyperloop.
reply