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

> You don't get to throw out "fondness for throwing Nazi salutes" slander, based on an hoax immediately debunked at the time, and then act like you're doing democracy a favor.

Just to clarify. This is the video context: https://www.youtube.com/watch?v=-VfYjPzj1Xw

Are you claiming that this is not an accurate depiction of what happened on stage? (That is the video is in some form fake. A deep fake, or special effects, or an Elon impersonator or whatever.)

Or are you claiming that the gesture seen is not a nazi salute?


Yes, "nazi salute" is obviously not an accurate description of the gesture Musk performed before saying "my heart goes out to you".

Here's a thought experiment for you.

If I stuck my middle finger up at you while saying "my heart goes out to you", what would you think?


Probably not that you support the Nazi regime, as that would be a ridiculous thing to think.

Particularly so if a year before you visited Auschwitz and stated it was "tragic that humans could do this to other humans", and told us how you attended a Hebrew preschool and have a lot of Jewish friends.


I didn't ask you what you wouldn't think. I asked you what you would think.

I don't get your point about the tailpipe emissions. Of course there is a hard cutoff. What else could there be? Do you want them to gently suggest that you should maybe fix your car above 90ppm, and then rudely suggest from 95ppm?

The response they can do is that they either let you use the car or not let you use the car. That is binary. Technically they cannot even do that. All they can do is promise you that if you use your non-compliant car and they find it out they will fine you. Laws are after all just formalised threats backed by force.


> What else could there be?

Charge a fee based on the number of ppm's your car emits:

    tax * ppm = fee to renew your tags
Even better would be to look at the odometer reading each year:

    tax * ppm * miles driven last year = fee to renew your tags

I work at a self-driving car company and we observed a similar problem when we did some off-road testing on dirt tracks. The cars were too precise and they were cutting deep ruts into the soil. We too solved it by adding a pseudo-random offset to the track.

I believe Google Maps adds a bit of a rng in which route it will recommend when two otherwise similar in distance/time. Obviously the traffic input also affects this, but that's a slower feedback mechanism; better to distribute the cars all leaving the airport for downtown across the 2-3 possible routes upfront rather than dumping them all onto route A until it's a jam and then all onto route B until it's a jam, etc.

I'm sure Google Maps has had to put their thumb on the scale in numerous instances. I recall reading articles about it "discovering" more optimal routes between Point A and Point B only to find things like the new "optimal" route being down a neighborhood street, and then the locals started squawking.

Annealing.

Before the current wave of automation there was a previous technology to automate buses using optical sensing and lines in the road which had the same issue.

If you want rails: build rails.

There are entire subway systems built with tire-on-concrete where the trains ride precisely the same routes down to the millimeter. Montreal’s is a famous one. These systems are not as efficient as rail, but they are quieter and gentler than the typical subway.

The problem is that the optical guided bus was built with the intention of reducing cost, since painting lines is a lot cheaper than building rails.

The moment you have to build rail-like things you lose most of the cost advantages.


That's still rail. It's just not steel-on-steel.

Otherwise you'd have to seriously limit what systems you call "monorail".


> pilots are trained to keep their nose gear on the centerline

Funily I was learning to fly at a grass strip and we were told to vary our positioning left and right on the runway for exactly this reason. In practice it meant that as we were taxiing to the runway my instructor would tell me “Today we are taking off left/right of center to avoid damaging the grass too much.”


> The real translator touch comes about when their is some nuance to the language.

And as we all know legal language is famous for having no nuance whatsoever, there are no opaque technical terms with hundreds of years of history behind their usage, there is no difference between the legal systems of different countries, and there is no possible difference in case law or the practicalities of legal enforcement. /sarcasm

What is clear to me that in a situation like this neither AI translation nor human translation is sufficient. What the imagined American signing an important legal document in the Czech Republic needs is a lawyer practicing in the Czech Republic who speaks a language the imagined American also speaks.


> Just, stop.

Why do you mind what others do?

> A leading zero does not unambiguously say "there are no implied nonzero digits to the left of this zero".

Nor does it anywhere say that it means that or that it should mean that. To me the the leading zero in front of 1931 means “Do you think a thousand year is long? Think on a longer scale.” It is a vibe.

> Or is that the usual truncation of 101931, since most relevant dates are in this decamillennium?

The sentients of 101931 won’t be confused because they will know that 01931 refers to our time. Simply from all the context clues acrued. Such as the fact that the document was written in HTML (an archaic markup format rarely used past 8470 as any historicaly inclined sentient of that age would know) and found saved on an SD—card in the backpack of an astronaut who crash landed on the far side of the moon in 2457. Same as you don’t get confused about which milenia a roman public inscription unearthed in Pompei refers to.


> The sentients of 101931 won’t be confused because they will know that 01931 refers to our time.

They may well be confused, because by then this silly "long now" stuff will be long since forgotten.


Consider that every culture's predominant method of writing has undergone significant changes over a given millennia long period. I'm not about to confuse the date on a photograph of a wax tablet for a modern one.

Right. But the long now format is a rarity, and doesn't look like it's ever going to become the norm. If someone from the far future stumbles upon it, they may well not know what millennium it comes from. It's just some date in an unknown format.

That's like supposing that I (in the modern day) would stumble upon an ancient sumerian date formatted in a slightly unusual manner (for the time), lack the context to identify the approximate era, but somehow if it had been written without the extra character (or whatever) I would have been able to figure things out.

Either a future archeologist has sufficient context to localize the writing to within plus or minus 5k years or the situation was hopeless to begin with. In all likelihood the latin script itself will be sufficient. In the unlikely event that latin numerals remain in near continuous use for another 100k years the writing system alone would then prove insufficient but hopefully you see my point.

That said, it seems the latin alphabet has been in use for 2700 years and is used by approximately 70% of the global population at this point so I guess if any alphabet is going to survive that far into the future it's one of the top contenders. But even then the scripts and usage conventions have changed drastically since its advent. Do we really expect anyone to be employing anything that even vaguely resembles a present day font face that far into the future?


I have once created a pendant to my friends’ wedding following a similar idea. A silver disk engraved one one side with the position of the planets and major moons at the moment of the ceremony. Fun thing is that the Galilean moons orbit fast enough that you can even read the intended minute. https://www.instagram.com/reel/DIpFTPOIP60/

If you have a blog post with a few more technical details, it may be a nice submission for HN. (Do you have a few photos of the intermediate steps to share?)

Some ideas/questions: How is it painted? Is it laser cut or by hand? Did you designed it? How did you do the calculations? Does Saturn have rings? Where is the cutoff? (No Neptune/Uranus/Fobos/Deimos/...) Have you tried to give a different size to each planet?

PS: I showed the video to my older daughter that is interested in astronomy and she likes it.


> If you have a blog post with a few more technical details, it may be a nice submission for HN.

Oh. That is very kind of you. I do have many more pictures and details. I will try to collect them together, and will publish it once it is done. But can’t promise that it will happen soon. So i will answer your questions here in the meantime.

> How is it painted?

The shapes are recessed and the recesses are filled with black nail polish. The excess nail polish was then scraped off from the flat upper surfaces leaving it only in the recesses.

It was very fiddly, and i don’t necessarily recommend this method for anyone. I have since learned how to enamel by melting glass powders onto the metal surface which is both easier and gives a better result. That is how i would do it today. (On my instagram the last reel i posted is showing that process, even though with a different design.)

> Is it laser cut or by hand?

A third and a fourth option. The planet side is machined on a cnc. First I etched the orbits with a v-bit, then cut the planets with a 0.8mm flat endmill, then cut the hole, and finally cut the outline. After that i etched the initials side chemically. As a resist i used self-adhesive vinyl which i cut with a plotter.

To be honest. I wouldn’t recommend this process either. It was super finicky, slow, and error prone. Today i would just etch and cut the metal with a fiber laser. In fact i bought a fiber laser because i got sick of the chemical etching and mechanical machining during this project. :)

> Did you designed it? How did you do the calculations?

I did design it! I’m very proud of it. The initials side was designed in inkscape while the planet side was generated with a python script. The script used the super handy skyfield python library for the calculations. (Which in turn uses the planetary ephemeris files published by the Jet Propulsion Laboratory.)

> Does Saturn have rings?

No ring of Saturn unfortunately. But it would be a cool idea!

> Where is the cutoff? (No Neptune/Uranus/Fobos/Deimos/...)

Unfortunately I don’t have a real good principled answer to this. Because of the machining I had a hard limit on the smallest details I could put on the metal. I did know that i wanted to put the Gallilean moons on there because their short periods meant that they provide good basis for the minutes and hours part of the date. I did know that i also wanted one of the gas giants to provide a “slow hand” to the clock to show the years, and to hopefully stretch out the period before the next time the solar system is in a similar position to very far into the future. And i wanted the inner planets and the Moon so people and future alien minds will recognise it as the solar system. Everything else was just futzing around with the script and finding a good compromise between not making it too large to wear and not making it too crowded either.

> Have you tried to give a different size to each planet?

I did, but it looked uneven and too haphazard to my eyes. Not saying it is impossible to make it neat with different planet sizes but I liked the diagram simplicity of keeping all the planets one size and the moons an other smaller size.

> I showed the video to my older daughter that is interested in astronomy and she likes it.

Oh thank you! That is lovely!


> On my instagram the last reel i posted is showing that process, even though with a different design.

Permalink: https://www.instagram.com/cogs_and_curios/reel/DTNtEFPjEGQ/

> And i wanted the inner planets and the Moon so people and future alien minds will recognise it as the solar system.

I think it was successful.


Out of curiosity were the positions (especially of the Galilean moons) actual simultaneous positions, or positions as seen from Earth, given the ~40 light-minutes distance between the Earth and Jupiter?

Very good question! I believe they are simultaneous positions. Skyfield has facilities to calculate the light propagation adjusted position but i didn’t use them. Would you have? Is one more “correct” or more likely to be anticipated by future sentients? I’m always unsure about ther design details.

Also there is an other skewiness. Because obviously the drawing is not to scale the moon position can be correct from the sun’s coordinate frame or the Earth’s coordinate frame, but not from both. I choose to make the moons “correct” in the sun’s coordinate frame. Meaning that if you were hovering over the ecliptic frame looking down at the Jupiter during the wedding and rotating the pendants so the sun is in the direction the real sun is, then you would see the moons under you in the same arangement as they are on the pendant. But if you would stand on the surface of earth (during the wedding) and look at Jupiter you would see the moons in a different arangements than a tiny human standing on the earth dot looking at the jupiter dot. (And not just because of the time delay difference, but because the coordinate systems are different.)

Which is weird. Because the wedding happened on Earth, not hovering over the plane of the eliptic over Jupiter. So maybe that was a weird choice. (And not even talking about how north-centric it is that i decided to draw the diagram from the “north” looking down at the eliptic, instead of from the “south” side. These are all kinda culturally driven arbitrary choices. Would love to have none of those present but I haven’t found a good and principeled way yet.)


Wow such a great answer, thanks for sharing the thoughts that went into this. It's crazy that there are so many considerations when taking into account the limited speed of light.

The speed of light is most frustrating. I find myself alternately wishing it was infinite or slowed down to 'disc world speeds' depending on which of the two would make my current project easier.

If others are interested in getting something like this — there's an Australian firm already doing a good job at scale (but slightly different to parent).

https://www.thenightsky.com/


That's so cool! Is there a calculator somewhere that can convert to/from dates and solar system position charts?

To calculate the orbital positions i used the skyfield python library. https://rhodesmill.org/skyfield/

They have a very handy example right on the landing page how one can calculate the positions and angles of a planet from a date.

The inverse was a bit trickier. But I also implemented a script which could “solve” a given picture backwards and give us a date. I believe i used binary search to narrow the date down first for the planet with the slowest period, and then refined the date around that timestamp using the position of the planet one faster. That way the estimate got more and more accurate and i didn’t need to brute force search a large time interval. (I applied the assumption that the date to be found is within half a saturn year from our current date, but if that assumption were incorrect it would have resulted in a solver failure during the refinement and thus detected.)


Positions at a given time could be simulated in e.g. Celestia (and then projected). The other direction, I don't know.

But is the star map there? This article seems to imply that it got demolished in 2022: https://www.oskarjwhansen.org/news/save-the-star-map

If so that is somewhat ironic. A message intended to communicate a date to thousands of years into the future got demolished a mere 86 years after its creation due to a drainage issue and a contract dispute.


I'd have to look at what it looked like before, but when I visited there earlier this month, I didn't see any restoration in progress and the star map was open. I didn't take a ton of photos in that area, and here are the only two of the monument I grabbed:

https://photos.app.goo.gl/qgJ3x5za82EiFz5P7


From my cursory web searches, your photos may be the first online evidence that the restoration project was indeed completed.

This is the second-best way to doxx HN users I've ever seen.

And the best way is...?

Job ads. It's job ads.

Thank you for the confirmation! This is so good to hear.

It is currently under reconstruction, it sounds like much of it was beyond salvage and has to be remade but it is difficult to find much info on this, bits and pieces strewn about the web. The project was resumed in 2023 and the BOR stated they were still committed to reconstructing the star map. In 2024 they completed the new underlayment and I have yet to find anything from 2025 other than that Monument plaza is still closed to the public.


At a loss for words. :|

This is horrible! I always wanted to visit this. :(

That is a crime of humanity. Terrible!

The same website says that as of 2024, it is slowly being reconstructed: https://www.oskarjwhansen.org/news/2024-hoover-dam-star-map-...

On Google maps, someone posted a photo from 9 months ago, explaining the restoration.

> asks whether you're at fault here, or she is

Or maybe nobody is? Why does someone has to be “at fault”?

> you can tell her then don't phrase your issues like that.

Sometimes people just want to be heard. There is value in recognising that.


> Great, so now GitHub can't change the structure of their IDs without breaking this person's code.

And that is all the fault of the person who treated a documented opaque value as if it has some specific structure.

> The lesson is that if you're designing an API and want an ID to be opaque you have to literally encrypt it.

The lesson is that you should stop caring about breaking people’s code who go against the documentation this way. When it breaks you shrug. Their code was always buggy and it just happened to be working for them until then. You are not their dad. You are not responsible for their misfortune.

> I find it really demoralizing as an API designer that I have to treat my API's consumers as adversaries who will knowingly and intentionally ignore guidance in the documentation like this.

You don’t have to.


Sounds like you’ve maybe never actually run a service or API library at scale. There’s so many factors that go into a decision like that at a company that it’s never so simple. Is the person impacted influential? You’ve got a reputation hit if they negatively blog about how you screwed them after something was working for years. Is a customer who’s worth 10% of your annual revenue impacted? Bet your ass your management chain won’t let you do a breaking change / revert any you made by declaring an incident.

Even in OSS land, you risk alienating the community you’ve built if they’re meaningfully impact. You only do this if the impact is minimal or you don’t care about alienating anyone using your software.


> Sounds like you’ve maybe never actually run a service or API library at scale.

What was the saying? When your scale is big enough, even your bugs have users.


Yeah, but when you are big enough you can afford to not care individual users.

VScode once broke a very popular extension that used a private API. Microsoft (righteously) didn't bother to ask if the private API had users.


VScode is free, so not really money on the line. Easy decision. Things get complicated when money gets involved.


If you think that just because VSCode is free there's no money on the line, you're not thinking about things the way others do. As I said, reputation alone definitely has a cost and Microsoft has partnerships where VSCode is strategic. They probably just made a calculation that there's not enough users and/or the users using that private API were strategically misaligned with their direction.


> The lesson is that you should stop caring about breaking people’s code who go against the documentation this way. When it breaks you shrug. Their code was always buggy and it just happened to be working for them until then. You are not their dad. You are not responsible for their misfortune.

Sure, but good luck running a business with that mindset.


Apple is pretty successful.


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

Search: