HN user

lukas9

42 karma
Posts1
Comments11
View on HN

Hey, thanks for trying it out and noting the bug, I'll look into it! As for the CelesTrack terms and usage, I also couldn't find much info on their website, but I only need one request every two hours so usage limits have never been an issue. For the license, I would assume that the SpaceTrack one would apply since CelesTrack doesn't list one.

Did you possibly misread the App Store page? The app's age rating is 4+, not its age. I published it on the App Store less than a month ago. Also, is there a specific functionality you were using when your device started overheating, and have you tried changing the performance settings in the app?

The reason why I even made this app is that all the similar apps I tried didn't have enough data about the satellites, or just didn't present them in a clean and interesting way. So what I tried to do with my app is to give users multiple options of displaying the satellite positions (AR, 2D, 3D) and have as much data as I could gather for each satellite.

The other guy is not wrong... kinda. I used AI for the code because I have no experience with Swift and SwiftUI, but I do understand how the calculations work, because I designed them. CelesTrack gives me TLE data, precisely describing each satellite's orbit and movement, as well as its current position on the orbit. What my app does is simply simulate the satellite's position (in 30-second intervals) up until 2 or 7 days into the future, and checks whether the satellite is overhead on each interval. Satellites are considered overhead based on just one criterion, and that is that they are above your horizon (so an elevation > 0 degrees). Hope that answers your question.

I'm currently working on a fully autonomous software development client. You can just tell the LLM what you want it to build, optionally adding a design doc or screenshots of app designs, and it iteratively keeps building the app and adding new features until you tell it to stop. It uses a vision model to verify correctness and rate the UI in-between iterations. The best part is that it can run purely on relatively small local models (I ran it on Qwen2.5 Coder 14b and Qwen3 VL 8b using my MacBook).

This is what I've noticed lately. I write articles and over the past year or two I had to stop using specific words or change my writing style a bit many times, because people kept asking if it was AI. It just makes me sad when I show someone my work and the first thing they say is "Is this AI"?