Rendered at 05:41:54 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
jug 3 days ago [-]
I recommend https://issinfo.net/artemis over the surge of vibe coded Artemis II trackers. Seen two others so far and they've all had major inaccuracies either regarding trajectory, current distance, or current mission state. One even said the remaining mission time was over 400 days. They all obviously used Claude Code.
solsane 3 days ago [-]
Just to be clear one glance and I can tell issinfo.net also used claude code
Great sense of scale, lovely to see the Moon apparently a long way from the "intercept" point, and it seems "accurate enough".
spuz 3 days ago [-]
Thanks - it's very nice to have a progress bar that you can scrub through to see where and when they have been and will be later in the mission.
codingmoh 3 days ago [-]
I did not use claude code, but codex, and I am fetching space weather from NOAA SWPc, trajectory, distance, speed, and comms delay are computed from NASA's published Artemis II mission plan parameters, not pulled live from NASA telemetry. Also, the current discrepancy is likely caused by the orbital phase and reference model being used. tracker shows about 192,000 km, while NASA's AROW shows about 80,000 miles, which is roughly 129,000 km. it is off by around 60,000 km.
difference can happen because the spacecraft is in a elliptical orbit and different trackers may be using different assumptions, interpolation methods,... or reference points for the trajectory
halfblood1010 2 days ago [-]
I really appreciate the idea and effort you put into building an Artemis 2 tracker dashboard. As an aerospace engineering student, I genuinely appreciate the information, the idea, and the effort that went into building this. The trajectory shape itself is technically a bit off, but honestly that doesn’t really matter here because the vast majority of people using the site aren’t aerospace engineers and aren’t looking for a perfectly modelled trajectory. They are looking for an accessible way to understand all the relevant information.
Also, it’s pretty common to see people immediately label projects as “AI slop.” There are quite a few folks who react that way right away, like @jug did here. That reaction is somewhat expected given how quickly AI has taken off and the existential/job-security concerns many computer engineers are dealing with right now, including the massive layoffs at Google 1-2 years ago.
At the end of the day, using AI to help write code is not that different from hiring a freelancer or contractor to implement parts of a project. The core idea, the decision to build it in the first place, the design choices, the testing, and the overall direction still come from humans. Those parts require thought, effort, and ownership, and that deserves appreciation. Either way, I think projects like this are valuable for sparking curiosity and making technical ideas more approachable to common people, which is always a good thing.
dvt 3 days ago [-]
To me, what's super interesting about this is the fact that my brain instantly recognized it's AI coded (not sure why, it might be the spacing, the font, the text glow, etc.).
pmontra 3 days ago [-]
Developers and their customers mostly gave up design many years ago and used frameworks like Bootstrap because they are good enough, they are cheap to create, they increase speed to deliver with no external designer in the loop, etc. That made many sites look alike. AI designed web sites are the next natural step.
YCprince 3 days ago [-]
The First thought that came to mind was It's AI coded. Maybe it's because they follow a similar design pattern. Or maybe we have some supernatural powers
This sort of bluish dark mode with monospace fonts. Similar accent colors. Not sure where it got this style from.
3 days ago [-]
altmanaltman 3 days ago [-]
I think it's because the UI sucks, like really bad. Why is there a CRT-type line in the background going down constantly. The mission timeline has weird colors that make no sense. Some graphs don't even fit their parent element. And so on.
I don't care if its vibe-coded but if you looked at this and thought "yeah that looks good", it only shows how bad you are at UI.
These types of interfaces are cool if you're like 12
sph 3 days ago [-]
What's even more interesting is that data is completely off compared to official sources, and the author doesn't even have the decency and self-reflection of checking if their slop is at all accurate before posting it to the HN front page.
Vibe coders, like the eggman himself, are philosophical zombies.
rickracconai 3 days ago [-]
[dead]
0x38B 3 days ago [-]
It says the distance from Earth right now is 154,000km, but the other trackers, including NASA, say 30,000km (numbers rounded). The velocity is different as well, 7km/s vs NASA's 4km/s.
codingmoh 3 days ago [-]
I am fetching space weather from NOAA SWPC.
Trajectory, distance, speed, and comms delay are computed from NASA’s published Artemis II mission plan parameters, not pulled live from NASA telemetry.
Also, the current discrepancy is likely caused by the orbital phase and reference model being used. Right now the tracker shows about 192,000 km, while NASA’s AROW shows about 80,000 miles, which is roughly 129,000 km. So yes, that is off by around 60,000 km.
difference can happen because the spacecraft is in a elliptical orbit and different trackers may be using different assumptions, interpolation methods, .. or reference points for the trajectory.
4ndrewl 3 days ago [-]
You're absolutely right! Let me go ahead and fix that now...(the sound of credits disappearing...) /s
It has "Distance From Earth" at 44,096 km (converted from miles...,) as opposed to 158,000 km. So yes, far off.
codingmoh 3 days ago [-]
Hey, I've responded before, I need to update the visualization: Iam fetching space weather from NOAA SWPC.
Trajectory, distance, speed, and comms delay are computed from NASA's published Artemis II mission plan parameters, not pulled live from NASA telemetry.
Also, the current discrepancy is likely caused by the orbital phase and reference model being used.
Right now the tracker shows about 192,000 km, while NASA's AROW shows about 80,000 miles, which is roughly 129,000 km. So yes, that is off by around 60,000 km. Difference can happen because the spacecraft is in a elliptical orbit and different trackers may be using different assumptions, interpolation methods,... or reference points for the trajectory.
washbasin 3 days ago [-]
This is cool!
NASA uses Imperial units (well, unless the it's the Mars Climate Orbiter). Can we get a version that follows the units they are using with their public feeds?
Aside... so impressed with the UI on the posted version.
rhubarbtree 3 days ago [-]
Great UI, but inaccurate slop. Couldn’t this have been validated against NASA’s site? Can we get this off the front page if the author can’t even be bothered to do that?
rozab 3 days ago [-]
This has always been a peeve of mine, but the lack of scale diagrams in coverage of this is maddening. We know what the Earth and the Moon look like, there is no need to make them 20 times bigger. Surely the point of these diagrams is to show the unbelievable scale of the journey. I'm yet to see one this news cycle, from NASA or anyone else
zamadatix 3 days ago [-]
In defense of the given approach:
False scale gives a direct way to see which body is which and where the craft is between them without having to work it out backwards from the rest of the context (while real scale makes both sides just looks like dots on typical sized screens and you need to know/read the rest before you can figure out which is which otherwise).
Combine that with "the scale of the Earth is already too large to comprehend accurately anyways" and defaulting to real scale doesn't really add as much as one might think to the experience anyways.
This is cool! I do want to ask, did you have AI design the page for you? It looks like a design pattern I've seen spit out by LLMs pretty frequently.
I'm not hear to talk down to you about the site, I love this little thing that gives me just enough info to satisfy my curiosity.
zamadatix 3 days ago [-]
I'll be the guy that talks down about Show HN becoming a place to post the thing you just vibe coded then because they didn't even bother to check the accuracy of the result - the numbers it provides about the mission are waaay off from reality right now, it just looks fancy.
I'm not necessarily against people sharing AI generated projects but there almost needs to be an [AI] tag if they do because it's really crashing the excitement of seeing a Show HN post where the assumption is this is something someone has been working hard on and is proud to show it off rather than something they just got out of Claude or whatever after a few prompts.
My take: If you didn't spend at least 24 hours of your own time (i.e. not munging with what the LLM is outputting but dedicated time for your own edits/testing) then it shouldn't qualify as a normal Show HN.
Polizeiposaune 3 days ago [-]
The closest they get to the moon is about 8000km/5000 miles above the surface over the far side
The trajectory depicted has them hitting the moon; it should instead show them passing 2+ lunar diameters behind the moon.
codingmoh 3 days ago [-]
thank you, I'll consider that
dap 3 days ago [-]
Is the MET right? They launched about 29 hours ago but it says 1d18h
danielszlaski 3 days ago [-]
Very cool! Nice to put it as a side window for live status (which do not take too much attention compared to YT)
thiht 3 days ago [-]
Why is a horizontal line constantly falling down? It’s so distracting, I feel like I can focus on the content
codingmoh 3 days ago [-]
Okay, sorry, I meant to make to emulate physical monitor
jamesbfb 3 days ago [-]
Bless! Absolutely love this, and an absolutely no disrespect, this is vibe code goodness! These are the kinds of things I have an absolute ball building, usually when I’m sitting on the couch at the end of the day duel screening.
What’s the data source? Assuming NASA being NASA they have a public API for the mission?
arnav7717 3 days ago [-]
very cool! How did you get the data?
rockdino 20 hours ago [-]
forgot the subject , who made it :)
desireco42 3 days ago [-]
Did they not just launch yesterday and they are already half way there? Am I wrong?
dvh 3 days ago [-]
They are right now only 44000km not 170000km, it's ai hallucinated slop (unless... NASA app is also ai slop...)
3 days ago [-]
mattfrommars 3 days ago [-]
This got vibed coded AF
Unai 2 days ago [-]
Pretty cool! This mission has me very excited, but it didn't even occur to me the I could keep track of all this data about it in real time, so thanks for sharing.
BTW, 90% of the comments being about whether this was made with AI or not (and personal opinions on it) is much MUCH worse than it being made with AI. The lack of downvotes for submissions is not an invitation to bring negativity to the comments; if the submission doesn't provide value to you, just move along. Make another post with your opinions on AI and see how many care to read it.
halfblood1010 2 days ago [-]
[dead]
Smoosh 3 days ago [-]
Nice, thanks.
lexcamisa54 3 days ago [-]
is it updating live data via
gitowiec 3 days ago [-]
I can't see crap. Fonts too small, everything too dark.
Great sense of scale, lovely to see the Moon apparently a long way from the "intercept" point, and it seems "accurate enough".
Also, it’s pretty common to see people immediately label projects as “AI slop.” There are quite a few folks who react that way right away, like @jug did here. That reaction is somewhat expected given how quickly AI has taken off and the existential/job-security concerns many computer engineers are dealing with right now, including the massive layoffs at Google 1-2 years ago.
At the end of the day, using AI to help write code is not that different from hiring a freelancer or contractor to implement parts of a project. The core idea, the decision to build it in the first place, the design choices, the testing, and the overall direction still come from humans. Those parts require thought, effort, and ownership, and that deserves appreciation. Either way, I think projects like this are valuable for sparking curiosity and making technical ideas more approachable to common people, which is always a good thing.
I don't care if its vibe-coded but if you looked at this and thought "yeah that looks good", it only shows how bad you are at UI.
These types of interfaces are cool if you're like 12
Vibe coders, like the eggman himself, are philosophical zombies.
Trajectory, distance, speed, and comms delay are computed from NASA’s published Artemis II mission plan parameters, not pulled live from NASA telemetry.
Also, the current discrepancy is likely caused by the orbital phase and reference model being used. Right now the tracker shows about 192,000 km, while NASA’s AROW shows about 80,000 miles, which is roughly 129,000 km. So yes, that is off by around 60,000 km.
difference can happen because the spacecraft is in a elliptical orbit and different trackers may be using different assumptions, interpolation methods, .. or reference points for the trajectory.
There are two kinds of countries: countries that use metric, and countries who have put a person on the moon.
Doesn't NASA use the metric system and only when they interact with the public they provide imperial units?
It has "Distance From Earth" at 44,096 km (converted from miles...,) as opposed to 158,000 km. So yes, far off.
Trajectory, distance, speed, and comms delay are computed from NASA's published Artemis II mission plan parameters, not pulled live from NASA telemetry.
Also, the current discrepancy is likely caused by the orbital phase and reference model being used.
Right now the tracker shows about 192,000 km, while NASA's AROW shows about 80,000 miles, which is roughly 129,000 km. So yes, that is off by around 60,000 km. Difference can happen because the spacecraft is in a elliptical orbit and different trackers may be using different assumptions, interpolation methods,... or reference points for the trajectory.
https://artemistracker.com/
https://artemislivetracker.com/
https://www.nasa.gov/missions/artemis-ii/arow/
Aside... so impressed with the UI on the posted version.
False scale gives a direct way to see which body is which and where the craft is between them without having to work it out backwards from the rest of the context (while real scale makes both sides just looks like dots on typical sized screens and you need to know/read the rest before you can figure out which is which otherwise).
Combine that with "the scale of the Earth is already too large to comprehend accurately anyways" and defaulting to real scale doesn't really add as much as one might think to the experience anyways.
I'm not hear to talk down to you about the site, I love this little thing that gives me just enough info to satisfy my curiosity.
I'm not necessarily against people sharing AI generated projects but there almost needs to be an [AI] tag if they do because it's really crashing the excitement of seeing a Show HN post where the assumption is this is something someone has been working hard on and is proud to show it off rather than something they just got out of Claude or whatever after a few prompts.
My take: If you didn't spend at least 24 hours of your own time (i.e. not munging with what the LLM is outputting but dedicated time for your own edits/testing) then it shouldn't qualify as a normal Show HN.
The trajectory depicted has them hitting the moon; it should instead show them passing 2+ lunar diameters behind the moon.
What’s the data source? Assuming NASA being NASA they have a public API for the mission?
BTW, 90% of the comments being about whether this was made with AI or not (and personal opinions on it) is much MUCH worse than it being made with AI. The lack of downvotes for submissions is not an invitation to bring negativity to the comments; if the submission doesn't provide value to you, just move along. Make another post with your opinions on AI and see how many care to read it.