Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. How do you diagnose an AWS bill?
    discuss
  2. A Key Safety Feature Shipped in the May OpenTofu Release(masterpoint.io)
    discuss
  3. Show HN: A game about fake news and memes(unspin.app)
    discuss
  4. Rendering pull requests in the GitHub Copilot app(github.blog)
    discuss
  5. Australia says OpenAI agent hacked into government website(channelnewsasia.com)
    discuss
  6. Pentagon Investigating How F-35 Fighter Jet Parts Bound for US Were Diverted(military.com)
    1comments
  7. AP: Avoid language that gives [AI] human characteristics(twitter.com/apstylebook)
    discuss
  8. Qubits on NonQuantum HW Tested(laurinseclab.substack.com)
    discuss
  9. Liquid Network Security Incident Assessment(blockstream.com)
    discuss
  10. FLAWED's Flaws and What This Means for Industry Research(suhacker.ai)
    discuss
  11. Geminigravit Core: De la teoría estática(gemini.google.com)
    discuss
  12. We used an AI agent to fix an open-source bug. Someone asked to ban us(github.com/saulpw)
    5comments
  13. Shadow roots, explained with live examples(simonwillison.net)
    discuss
  14. Show HN: Does per-step reasoning effort save money in Claude Code?(github.com/ifoster01)
    discuss
  15. Show HN: ChaosTree – Cache-Aware Java NavigableMap and NavigableSet Library(github.com/chaos-vy)
    discuss
  16. Show HN: Posting Puzzle – A Game Made of Post's Correspondence Problem(mametter.itch.io)
    1comments
  17. AI startups with hyper ARR growth – what's happening inside these companies?
    discuss
  18. Nesbox: A fast MicroVM with GPU sharing(github.com/nestrilabs)
    discuss
  19. Using my transit card data to create a year in review experience(cailinpitt.com)
    discuss
  20. Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest(github.com/nestrilabs)
    discuss
  21. Scientists build most accurate atomic clock(phys.org)
    1comments
  22. AI Has Cracked the Most Diabolical Problems in Math. Why Can't It Solve Chess?(wsj.com)
    discuss
  23. lm-detector: Model fingerprint detection on Web and CLI(github.com/ikaleio)
    discuss
  24. SnakeCharmer: Fuzzing Harness Generation for Pure and Hybrid Python Libraries [pdf](utah.edu)
    discuss
  25. Making my vibe-coded app best as possible (I am perfectionist), umm for 0 users
    discuss
  26. JEV Engineering for Coding Agents(drive.google.com)
    discuss
  27. Show HN: An open-source manufacturing ERP/MES/QMS(carbon.ms)
    discuss
  28. Hard Startups (2020)(samaltman.com)
    discuss
  29. OnPanda – Open-source token inspection&data annotation tool from Step 5 Preview(twitter.com/stepfun_ai)
    discuss
  30. Feds Target AI Critics as "Foreign Agents"(kenklippenstein.com)
    2comments

We've Turned Starlink into a Planetary Barometer

11 pointsby 2h agospaceweather.com
2 comments
1h agoHN ↗

Such obnoxious Claudish in this article. I don't know enough verify the analysis and I genuinely don't know if the author does either.

1h agoHN ↗

It also doesn't "know" basic orbital mechanics.

From the article:

and station-keeping burns corrupt them

Geostationary satellites execute station keeping burns to avoid "wandering", from the POV of an observer on the ground.

Something like a satellite in a Lagrange point might also execute tiny station keeping burns.

A LEO satellite such as starlink has thrusters, yes, and it executes burns, yes, but its burns are executed prograde in the direction of travel to increase orbital altitude. Likely in several small burns. A single prograde burn made when on one side of the planet has the effect of increasing the height of apogee on the opposite side of the planet, so after you do your first burn and are halfway around a full orbit, you need to do at least a second burn to re-circularize your orbit.

Nobody that's involved in LEO satellite operations would call it a station keeping burn because it's literally not keeping station anywhere.

I also doubt the validity of the data in this article because without internal information from spacex on things like how often they burn, when they burn, duration of burn and expected delta-v gain per burn (which spacex is OBVIOUSLY not going to share with anyone because making an extremely fuel efficient small satellite is a competitive advantage and a trade secret), you can't know how much the satellites are actually thrusting in any given day, week, month or year to account for varying increased atmospheric density.

The one thing that the article did get right is that the superdove satellites, which are 3U cubesats, have no thrusters at all, so watching the degradation of their orbit over time (and the rate of change in any given week or month) might be a more valid source of data. There's no need to "guess" at what a satellite operations center at SpaceX might be commanding them to do in terms of fuel expenditure because there is no fuel to expend or thrusters to turn on to burn prograde.

https://www.google.com/search?client=firefox-b-d&q=superdove...