Artemis.fyi
There are plenty of Artemis II trackers out there. I looked at a bunch and kept running into the same issues - some had data that didn't look right, it was hard to use on smaller screen, others felt overly complicated for what I actually wanted to know: what's the crew doing, where is Orion, how fast is it going. The best one I found was issinfo.net/artemis, which inspired a lot of the design. So I built my own. The part that was genuinely interesting to me was the data. Turns out anyone can query JPL's Horizons API for full ephemeris data on the Orion spacecraft - position, velocity, range - for free. I had no idea this existed. Even better: NASA's Deep Space Network publishes a live XML feed (eyes.nasa.gov/dsn/data/dsn.xml) that updates every 5 seconds showing exactly which ground antennas are talking to which spacecraft. Right now two dishes in Canberra are locked onto Orion - one sending commands, both receiving 6 Mbps of S-band telemetry at 296,000 km. You can see Juno at Jupiter, JWST, Mars Odyssey, all in the same feed. It's pretty amazing what's just sitting there in the open. The app fetches trajectory from Horizons, crew activities from NASA's published flight plan, and live ground station status from DSN. I'll be honest - it's mostly vibe-coded with supervision. The data pipeline is the part that was more manual: figuring out what's publicly available, how to compute relative positions from raw vectors, how to cache and backfill. That was the fun part. Code is open on GitHub. I built it for myself and as a fun exercise, but happy for any feedback - especially around data correctness and what other public data sources are out there that I might be missing. Source: https://github.com/dmarchuk/artemis.fyi
AI Analysis
Analysis coming soon.
Similar Products
Capgo
Instant updates for Capacitor apps. Ship fixes in minutes, not weeks. Push OTA updates to users without app store delays.
OpenAlternative
Open source alternatives to popular software. Over 1 million users replaced their proprietary tools with open source software. Discover the best alternatives and join the movement.
Ancestree
Every time I talk to my older family members, especially my grandparents, I find out a new super interesting fact about them. Last week: my Croatian grandfather served in the French marine corps... Not worth mentioning I guess. I realized that these stories are passed down only by re-telling them. Just think about how much you don't know about your family from 2 generations ago. For this reason, I created ancestree.marindedic.com It's a really cool family tree creation app, where each person gets their own book. Inside it, write what they did, what happened to them, what they were like... whatever you want. Little biographies of your loved ones. Apart from exporting normal and detailed versions of your family tree, you can even export someone's chapters as one long biography. Of course, open-sourced, no account, no server. Nothing you draw or write ever leaves your browser.
Keenable
Hey HN! We built https://keenable.ai, a different web search API for AI agents. Keenable searches our own 100B+ page index. We are focused on low cost and latency (p95 <250ms from us-east). We donโt believe in benchmaxxing, so we open-sourced our internal benchmarking suite, NEEDLE (available at https://keenableai.github.io/needle): a live benchmark that compares Keenable with other search APIs on fresh agent-like queries. I spent seven years at Amazon as a scientist working on web grounding for Alexa/AGI, and my co-founder Andrey previously led search at Yandex. We started Keenable because agents search differently from humans, and we wanted to build around those patterns directly. The API is available now and we provide a free allowance of 100,000 requests a month. It also exposes a novel SQL-like interface to the web, which is useful for structured extraction and agent workflows. Happy to answer questions about the index, crawl, ranking, latency, or benchmarking.
Structural code grep across public GitHub repositories
Codemod grep searches public code by syntax and structure, not just text or regex. Use ast-grep patterns to find code by shape across repositories.