frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
518•klaussilveira•9h ago•145 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
852•xnx•14h ago•512 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
65•matheusalmeida•1d ago•13 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
169•isitcontent•9h ago•20 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
172•dmpetrov•9h ago•77 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
286•vecti•11h ago•129 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
65•quibono•4d ago•11 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
340•aktau•15h ago•166 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
335•ostacke•15h ago•90 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
425•todsacerdoti•17h ago•223 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
232•eljojo•12h ago•142 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
366•lstoll•15h ago•253 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
37•kmm•4d ago•3 comments

Show HN: ARM64 Android Dev Kit

https://github.com/denuoweb/ARM64-ADK
14•denuoweb•1d ago•1 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
4•videotopia•3d ago•0 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
11•romes•4d ago•1 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
85•SerCe•5h ago•68 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
216•i5heu•12h ago•160 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
17•gmays•4h ago•2 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
36•gfortaine•6h ago•10 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
59•phreda4•8h ago•11 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
161•limoce•3d ago•80 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
124•vmatsiiako•14h ago•51 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
260•surprisetalk•3d ago•35 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1024•cdrnsf•18h ago•425 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
53•rescrv•16h ago•17 comments

WebView performance significantly slower than PWA

https://issues.chromium.org/issues/40817676
16•denysonique•5h ago•2 comments

I'm going to cure my girlfriend's brain tumor

https://andrewjrod.substack.com/p/im-going-to-cure-my-girlfriends-brain
102•ray__•5h ago•49 comments

Evaluating and mitigating the growing risk of LLM-discovered 0-days

https://red.anthropic.com/2026/zero-days/
44•lebovic•1d ago•13 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
82•antves•1d ago•59 comments
Open in hackernews

First Hubble telescope images of interstellar comet 3I/ATLAS

https://bsky.app/profile/astrafoxen.bsky.social/post/3luiwnar3j22o
109•jandrewrogers•6mo ago

Comments

hooo•6mo ago
While it would be cool if it were alien technology[1], it looks like an ancient comet?

[1]: https://avi-loeb.medium.com/is-the-interstellar-object-3i-at...

csours•6mo ago
Oh dear, he's already at it with this one too
meepmorp•6mo ago
It'd be more surprising if he wasn't, tbh.
mcswell•6mo ago
Agreed, it would be cool, but. From that article, with my commentary (disclaimer: IANAA, I Am Not An Astronomer):

1) "The retrograde orbital plane... of 3I/ATLAS around the Sun lies within 5 degrees of that of Earth... The likelihood for that coincidence out of all random orientations is 0.2%." Not sure where he comes up with 0.2%. 5/180 = 2.8%. (I use 180 degrees, rather than 360, because I suspect that if it were not retrograde, he'd use the same argument.)

2) "the brightness of 3I/ATLAS implies an object that is ~20 kilometers in diameter (for a typical albedo of ~5%), too large for an interstellar asteroid. We should have detected a million objects below the ~100-meters scale of the first reported interstellar object 1I/`Oumuamua for each ~20-kilometer object." Huh? We barely detected this object because it's so dim. Why should we be detecting interstellar objects two or three orders of magnitude smaller?

3) "No spectral features of cometary gas are found in spectroscopic observations of 3I/ATLAS." An article today (22 July, https://astrobiology.com/2025/07/spectroscopic-characterizat...) says "Spectral modeling with an areal mixture of 70% Tagish Lake meteorite and 30% 10-micron-sized water ice successfully reproduces both the overall continuum and the broad absorption feature... 3I/ATLAS is an active interstellar comet containing abundant water ice, with a dust composition more similar to D-type asteroids..."

4. "For its orbital parameters, 3I/ATLAS is synchronized to approach unusually close to Venus (0.65au where 1au is the Earth-Sun separation), Mars (0.19au) and Jupiter (0.36au), with a cumulative probability of 0.005% relative to orbits with the same orbital parameters but a random arrival time." This probability is harder to compute (although 0.65au from Venus is nearly the radius of Venus' orbit, 0.72au, i.e. not close). In any case, so what? Why would an interstellar probe travel close to Mars or Jupiter, if they're interested in Earth? (see next point) Later (his point 8), he says the probe comes close enough to these planets to launch ICBMs at them. Ok...

5. "3I/ATLAS achieves perihelion on the opposite side of the Sun relative to Earth. This could be intentional..." Sure, if they're interested in Earth, stay away from it.

And similarly for the rest of his points.

teraflop•6mo ago
> "The retrograde orbital plane... of 3I/ATLAS around the Sun lies within 5 degrees of that of Earth... The likelihood for that coincidence out of all random orientations is 0.2%." Not sure where he comes up with 0.2%.

This part of the calculation, at least, is basically correct. The orientation of a plane in space is defined by its normal vector, so the right way to look at probabilities is in terms of solid angle. The normal of 3I/ATLAS's orbit falls within a cone around Earth's normal vector, having a half-angle of 5 degrees, and that cone's solid angle occupies about 0.2% of the full sphere.

Of course, this is only the chance of a retrograde alignment. Presumably, if the comet's orbit was prograde aligned with the Earth's to within 5 degrees, Loeb would be making exactly the same claim. So really, the relevant probability is 0.4%.

Nevertheless, I agree that the article is basically just a bunch of cherry-picked probabilities and insinuations that don't add up to much.

Also:

> "the brightness of 3I/ATLAS implies an object that is ~20 kilometers in diameter (for a typical albedo of ~5%), too large for an interstellar asteroid."

But to justify this, Loeb cites his own work showing that the object is either a large asteroid, or a comet with a small nucleus. And then he seems to have looked at some earlier spectra and jumped to the conclusion that 3I/ATLAS couldn't be a comet, so it must be a large asteroid. But of course, follow-up observations have debunked this point and clearly shown it to be a comet.

rachofsunshine•6mo ago
I think there's also a sampling bias here? ATLAS, the survey that discovered the comet, is specifically looking for potential Earth impactors. One assumes that would involve looking close to Earth's own orbital plane.
imafish•6mo ago
Why would it be cool, though? More like frightening, if the thing was sent on purpose by another civilization.
dylan604•6mo ago
The slew rate for tracking comets is something that I have not had to mess with before, but I adjust my little EQ mount when I'm tracking the moon vs deep sky objects. How accurate is Hubble now? How many of its reaction wheels does it have left? I seem to remember it being down to just one at one point. Does that add difficulty in tracking this object with its very high velocity?
pinko•6mo ago
I suspect, at ~4.5AU distance, even though 3I/ATLAS is moving at a relative speed of ~60 kms, its angular velocity across the sky is manageable for Hubble's current one-gyro pointing system, given non‑sidereal tracking and short (~100s) exposures.
teraflop•6mo ago
I'm no Hubble expert, but a bit of research turned up the "HST Primer" [1] which is apparently up-to-date for the current observing cycle, and which says:

> HST is capable of tracking moving targets with the same precision achieved for fixed targets. This is accomplished by maintaining FGS Fine Lock on guide stars and driving the FGS star sensors in the appropriate path, thus moving the telescope to track the target. Tracking under FGS control is technically possible for apparent target motions up to 5 arcsec/s.

According to JPL Horizons, the current angular motion of 3I/ATLAS across the sky is <0.03 arcsec/s, so it's well within Hubble's capabilities.

My understanding is that the Hubble's one-gyro mode mainly complicates the process of quickly moving from one target to another. Once the telescope is pointed at a target, the stabilization and tracking is done using guide stars without relying on gyros.

Anyway, in absolute terms, 3I/ATLAS isn't moving that fast. Its orbital speed is about 3x that of Mars, but it's farther away, and (for now) much of that motion is directed inward towards the sun.

[1]: https://hst-docs.stsci.edu/hsp/the-hubble-space-telescope-pr...

Starman_Jones•6mo ago
You're on the money. Hubble isn't too perturbed when it can lock on to guide stars, but some observations are no longer possible in one-gyro mode.
rachofsunshine•6mo ago
Hubble's slew rate (the rate at which it can change the broad direction its camera points) is about 6 degrees per minute [1], or about 1/10 of a degree per second (I refuse to use the incredibly cursed unit "minutes per second"). It tracks a fine object slower than that, but that gives a reasonable order-of-magnitude estimate.

At even 1 AU of distance, an angular velocity of 1/10 of a degree per second requires a linear speed of about 0.87c. Needless to say, 3I/ATLAS is not moving that fast - if it were, it would be outputting about 100 TW, mostly as heat, just from slamming into the interplanetary medium at relativistic speeds [2].

[1] https://www.pbs.org/deepspace/hubble/diagram.html#:~:text=Th...

[2] https://www.wolframalpha.com/input?i=%2840+*+mass+of+hydroge...

dylan604•6mo ago
> I refuse to use the incredibly cursed unit "minutes per second"

Man, that is a horrible unit. I've never heard of that, but I can only imagine each semester professors every where have to endure an enterprising student using this to be "clever" in some way

gammarator•6mo ago
“Arcminutes per second” would be the standard way to express it in astronomy.
saurik•6mo ago
FWIW, isn't it only "minutes" if you want to be confusingly short? I'd have said "minutes of arc" or "arcminutes".
rkagerer•6mo ago
Dumb question: Is it the smaller one (that moves, along the same axis as the background stars) or the bigger one (that's fairly static). What's the other one?
exitb•6mo ago
The static lines are motion blurred stars (even the bright one), the small dots are radiation noise, the one that moves, with a coma is the comet.
squigz•6mo ago
I don't think those are motion-blurred stars. Wouldn't they have to be considerably closer to us - or Hubble going much faster - for that to be the case?
vilhelm_s•6mo ago
The telescope is panning to keep the comet still in the frame during the exposure.
mcswell•6mo ago
About the bigger one that doesn't seem to move: I think it does move, it's just that it's so bright (for Hubble) that its brightness overwhelms the slight elongation of its image. In other words, it's (apparently) moving just like the other stars, it's just hard to tell.
throw0101b•6mo ago
A lot of motion blur: have they tried adjusting the shutter speed…
pinko•6mo ago
At ~100s, it's already at about the minimum for Hubble; often it's 1-2 orders of magnitude longer.
mcswell•6mo ago
If I know what you're referring to, the motion blur is the stars, not the comet. That's because Hubble is tracking (pointing at) the comet, not the stars. The comet is therefore not blurred in its direction of travel, while the stars appear to be moving in the direction opposite of the comet's travel. To the extent that the comet appears blurred, that's presumably its coma.
amrrs•6mo ago
Noob Q: How do they know it's an interstellar comet? With the speed of movement between two frames?
baggy_trough•6mo ago
This object was already discovered and known to have an hyperbolic (uncaptured) orbit.
vikingerik•6mo ago
Short answer, yes. But it's many frames, and over a time span of many nights and now weeks.
rachofsunshine•6mo ago
We know how fast it is moving and how far from the Sun it is. If its velocity is greater than the escape velocity of the Sun at its current distance, it can't have gained that velocity just from its orbit around the Sun (because by definition an object in an [elliptical] orbit is traveling more slowly than escape velocity).

It is possible for a Solar System comet to be perturbed by other effects (like a close passage with Jupiter) into an escape orbit. But in those cases, the speed above escape velocity is small, and the orbit barely escapes. 3I/ATLAS is moving much, much faster than that, too fast for within-the-solar-system effects to explain it. It must therefore be interstellar.

ycui1986•6mo ago
With Rubin Observatory coming online recently, we should be able to find many more of this type of event. So, it would make sense to have a more generic probe ready in standby and wait for the next interstellar object discovery. Then, send the probe to the interstellar object for a flyby mission. It would be revolutionary if the probe could directly detect the element and isotope composition of the comet tail during the flyby.
laacz•6mo ago
These are moving so fast, that there is nothing we might have on stand-by.