Gotta fix the typo on Anthropic's name
Fixed, thank you!
Readit Newsjohnmcelhone commented on Show HN: Lunon – Instant model switching across LLMs lunon.com/... · Posted by u/johnmcelhone
johnmcelhone commented on Show HN: Lunon – Instant model switching across LLMs lunon.com/... · Posted by u/johnmcelhone
Nice websites but seriously,
A. a pricing link that takes you to NOT pricing B. listing Grok and Groq in the same block as if they have anything to do one another is a bad choice
Didn't catch the pricing bug, will update right now.
A few others have also mentioned about the Grok & Groq confusion. Will think through some ideas here and update.
Appreciate the feedback!
johnmcelhone commented on Show HN: Lunon – Instant model switching across LLMs lunon.com/... · Posted by u/johnmcelhone
Front page says "Antrophic" rather than "Anthropic" :)
Some people may also find the grok/groq section confusing
That was my bad - just fixed that mistake. Thanks for catching it!
Will explore some more ideas for the Groq & Grok part too.
I thought so too but I think you need to know the constellations first to identify the North Star in the photo.
This is correct. The brightness of the stars made them a bit difficult to identify by eye, I'm sure someone more familiar with sky charts could have done it. The constellations helped me align the sky on Stellarium (from their angles) and the north star helped me find the approximate latitude by using the angle from the horizon.
I don't know if I entirely buy the line on "34-35 degrees off the horizon." Unless we knew the focal length of the lens it was taken with, and which camera it was taken from, you don't actually know that. A wide-angle lens is going to have a much larger field of view than, say, a 100mm macro. And different camera systems have different angle of view for the same focal length.
You don't actually need the focal length, it doesn't help accuracy that much but can help you line up the sky to the photo a bit quicker. Anyway, if we did, all that info was in the metadata anyway:
Camera: Nikon D5 F-stop: f/2.8 Exposure time: 5 sec. Focal length: 28mm Max aperture: 3
I feel like the entire thread should have led off with "This is in fact a publicly known hangar in Palmdale and this was known as public information as soon as the unveiling event occurred, and thus this is just an exercise to show how locating the spot could have been possible from just this photo as a technical demonstration."
Because I guarantee there are going to be a hundred clickbait articles by various 'news' sites now in the next few days about the MASSIVE SECURITY BREACH of the USAF and how US SECRETS have been EXPOSED so and and so forth. When nothing about this is actually the case.
I did mention this later in the thread - was just a fun experiment to see if locating it was possible if we didn't know
misleading. was more like:
* he got the approximate latitude from the stars (34 or 35)
* independently, he found the most plausible airbase based on other information and then noticed that the base is indeed around that latitude
The process can still be done using entirely the star pattern and no Google Maps. There wasn't any reason to exclude other information I could use, so I didn't.
more constructively, this is the kind of code ai is great at writing in my codebase and once it’s there locally as a library, it’s free. it’s not clear to me why I’d want it behind an api instead, at least as a solo-ish dev. I’d recommend looking at the similar openrouter that seems to have some traction and think about why users are using them. You might also think about deeper agent or eval stuff you could add that are beyond the scope of the little backend switching lib I could have Claude write. Anyway, good luck and thanks for sharing!
On your point about local code vs. API:
- We handle all the authentication, rate limiting, and API differences between providers, which becomes complex when working with multiple models. Our platform allows smart switching between different models depending on the message context.
- Our switching is optimized for performance. We provide detailed usage analytics and cost management across models so you can optimize which models to use where. This allows you to see what costs your users may be incurring / misbehaving.
We're building features that go beyond what's easily replicable locally, including some of the agent and evaluation capabilities you mentioned (rolling out over the next two weeks). OpenRouter is definitely doing great things in this space. We're taking a slightly different approach by focusing on bringing customization within the dashboard to allow for on-the-fly updates without pushing new code edits.
Appreciate the feedback and hopefully you get a chance to try out the tool!