frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

France's homegrown open source online office suite

https://github.com/suitenumerique
197•nar001•2h ago•105 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
373•theblazehen•2d ago•133 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
64•AlexeyBrin•3h ago•12 comments

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

https://openciv3.org/
749•klaussilveira•18h ago•234 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
38•onurkanbkrc•3h ago•2 comments

First Proof

https://arxiv.org/abs/2602.05192
8•samasblack•29m ago•4 comments

The Waymo World Model

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

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
105•alainrk•2h ago•111 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
132•jesperordrup•8h ago•55 comments

Show HN: One-click AI employee with its own cloud desktop

https://cloudbot-ai.com
5•fainir•56m ago•0 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
4•vinhnx•1h ago•0 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

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

Ga68, a GNU Algol 68 Compiler

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
30•matt_d•4d ago•6 comments

Making geo joins faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
148•matheusalmeida•2d ago•40 comments

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
6•edent•2h ago•0 comments

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

https://github.com/valdanylchuk/breezydemo
253•isitcontent•18h ago•27 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
6•rbanffy•3d ago•0 comments

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

https://github.com/pydantic/monty
265•dmpetrov•18h ago•142 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
10•sandGorgon•2d ago•2 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
530•todsacerdoti•1d ago•256 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
407•ostacke•1d ago•105 comments

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

https://vecti.com
351•vecti•20h ago•159 comments

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

https://eljojo.github.io/rememory/
321•eljojo•21h ago•197 comments

Cross-Region MSK Replication: K2K vs. MirrorMaker2

https://medium.com/lensesio/cross-region-msk-replication-a-comprehensive-performance-comparison-o...
6•andmarios•4d ago•1 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
54•helloplanets•4d ago•54 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
447•lstoll•1d ago•296 comments

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

https://github.com/microsoft/litebox
365•aktau•1d ago•190 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
290•i5heu•21h ago•246 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
103•quibono•4d ago•29 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...
52•gmays•13h ago•22 comments
Open in hackernews

Supermassive black holes locked in a stable orbit around each other

https://www.helsinkitimes.fi/themes/themes/science-and-technology/28090-scientists-capture-first-image-of-two-black-holes-in-orbit.html
31•DaveZale•3mo ago

Comments

pavel_lishin•3mo ago
> The existence of two black holes in OJ287 was first suggested in 1982. Aimo Sillanpää, then a graduate student at the University of Turku, observed that the brightness of the quasar changed regularly over a 12-year cycle.

Damn, that's about the time it takes Jupiter to orbit the sun. That feels wildly close together for objects that mass 18 billion & 150 million times that of our own sun.

These black holes (according to a calculator I found online) have radii of 53 billion km and 400 million km, so I'm guessing they must be orbiting significantly further away, and significantly faster than Jupiter (which is ~800 million km away from the sun) - which makes sense, given the monstrous 18b figure. I wonder how far apart they are, but I don't really know how to easily calculate that right now.

hinkley•3mo ago
How much time dilation do you get at those masses though?

I’m having more trouble visualizing how accretion disks would work for a binary black hole. Because the light is coming from the disks, not the black holes. So those are what are actually pulsing/girating.

pavel_lishin•3mo ago
Yeah, good point on that, too. I bet someone's written a simulator that I could run locally, but I've got a busy day ahead of me :(

I thought that in this case, the light that they detected was coming from the jets coming from the poles, not the disk itself directly.

hinkley•3mo ago
Since black holes are black holes, the jets are generated by the disk.
ardel95•3mo ago
Unless I screwed up the math, they would be quarter of a light year apart. Plenty of space for each black hole to form its own accretion disk.
hinkley•3mo ago
Oh that chart is really awful then. It’s showing an accretion disk that’s half a light year in diameter at least.
ardel95•3mo ago
Kepler’s laws should still provide a pretty good estimate, at least until black holes get much closer. I did a quick back of the envelope calculation, and looks like they’ll be roughly 14k astronomical units, or 0.22 light years apart.
kmm•3mo ago
In Newtonian gravity, the relation between the orbital period T and the semimajor axis a of the orbital ellipse is a^3 / T^2 = GM / 4π^2, where M is the reduced mass of the system (in this case, with 99% of the mass being in one of the two black holes, it's simply the mass of the heavier one).

Plugging 12 years and 18e9 solar masses gives about 2e12 kilometers, or roughly a fifth of a lightyear. This also means the smaller black hole is zipping around the bigger one at around 6% of the speed of light, which is low enough that the Newtonian approximation is probably reasonable accurate (at least to give a rough idea of how large the distances must be).

hnuser123456•3mo ago

  Feature                  Primary Black Hole              Secondary Black Hole
  -----------------------  ------------------------------  ------------------------------
  Mass                     1.8 × 10^10 M                   1.5 × 10^8 M
  Schwarzschild Radius     356 AU                          3.0 AU
 
  --- Circular / Average Orbital Properties ---
  Orbital Period           12 years
  Semi-Major Axis          13,800 AU (~0.22 ly)
  Orbital Speed (avg)      282 km/s (0.094% c)             33,900 km/s (11.3% c)

  --- Elliptical Orbit (e ≈ 0.65) ---
  Pericenter Distance      4,830 AU                        (same)
  Orbital Speed (peri)     613 km/s (0.20% c)              73,600 km/s (24.5% c)

  Apocenter Distance       22,800 AU                       (same)
  Orbital Speed (apo)      130 km/s (0.043% c)             15,600 km/s (5.2% c)
So the "smaller" SMBH is punching through the larger one's disk at a significant fraction of c twice every 12 years. But it's losing energy to gravitational waves so quickly that they'll probably merge in around 10,000 years [1]

[1] https://archive.is/Ccy5M

IAmBroom•3mo ago
Orbiting at c/6 - WOW!
ccozan•3mo ago
The relativistiv effects must be wild there!
butlike•3mo ago
> the "smaller" SMBH is punching through the larger one's disk at a significant fraction of c twice every 12 years. But it's losing energy to gravitational waves so quickly

Bro should get in shape before they start to clap cheeks

Qem•3mo ago
Such a system would make easy[1] for any civilization living nearby to launch spaceships at a large fraction of the speed of light. But the tricky part would be braking at the destination, unless your destination is a similar and suitably aligned system.

[1] https://www.centauri-dreams.org/2023/06/08/freeman-dysons-gr...

kbelder•3mo ago
You made me wonder about the orbital speed of a planet circling one of these supermassive black holes, and how fast it would be... and then I realized, of course, the orbital speed would approach the speed of light at the event horizon.

There's a SF story waiting to be written about a planet just over that radius, traveling at something like 0.99c. Years would takes seconds, and seem even faster since they'd be significantly time-dilated. Of course, they'd quickly spiral in.

hinkley•3mo ago
Why “just released” if the paper the image came from is dated 2022?
DaveZale•3mo ago
maybe this:

One more flare happened since then, in 2022, but because of instrumental limitations, it was caught only at a prestage (M. J. Valtonen et al. 2023; M. J. Valtonen 2024). At the same time, more flares were discovered in historical photographic plate studies so that only eight of the expected 26 flares remain unconfirmed (R. Hudec et al. 2013). All the unconfirmed ones are due to lack of known photographs at the expected epochs.

https://iopscience.iop.org/article/10.3847/1538-4357/ae057e

hinkley•3mo ago
I understand that patterns and confirmations often come from data captured years ago and reanalyzed. That’s how some comets are discovered.

What I don’t get is how you can say we are publishing the first picture and then post a picture that was published three years ago.

It looks like HN has now changed the title from the “all editors should be fired” exhibit list to something more reasonable, but the linked article is still titled, “Scientists capture first image of two black holes in orbit.”

DaveZale•3mo ago
which editors should be fired? You mean the scientific journal editors?

As to the image, "The image shows two bright points, each representing a jet of high-energy particles emitted by one of the black holes. The black holes themselves remain invisible, but the image provides clear visual evidence of their position, motion, and dual existence. "

My best guess is that it took a few years to interpret the data. Frankly, I don't get the math. The numbers are so big! But I feel pretty small when considering this... and, of course, soon we'll hear of even more of these systems.

Do you think that gravitational lens effects will be studied when "the stars are aligned" for other studies?

hinkley•3mo ago
> You mean the scientific journal editors?

It’s died down lately but there has been a lot of spleen venting here about how shit article titles are compared to their contents. Often implying the exact opposite of the contents. The usual explanation is that editors pick the titles. And then there is a lot of uncharitable speculation about what exactly editors are good for given they are so overwhelmingly awful at titles. Which I am all too happy to participate in.

What’s interesting is the policy here used to be no editorializing on titles. But the title of this thread has been changed to something more like the paper and less like the article describing it. Seemingly in violation of that old policy. I hope that means I’ve missed a shift in policy happening.

InspGadget4343•3mo ago
*Muse starts playing somewhere in the cosmos
antognini•3mo ago
This system, OJ287, is perhaps the most important system we have for understanding what happens to supermassive black holes after a galaxy merger. This is the so-called "Last Parsec Problem."

When two galaxies merge, their supermassive black holes fairly rapidly sink to the center of mass of the newly combined galaxy via dynamical friction and enter into a slow orbit around each other. Over time, the SMBHs kick out interloping stars, which removes energy from the orbit and causes the two SMBHs to come closer together. If the SMBHs were able to get within ~0.1 parsecs of each other, gravitational wave radiation could take over and cause the orbit to shrink fairly rapidly and lead to the merger of the two SMBHs.

However, the theoretical models we have generally predict that at about 1 parsec, the SMBHs have kicked out all the stars in their neighborhood, so the process stalls out. In practice we don't observe many SMBH binary systems (OJ287 being the main exception), so there must be some mechanism that causes these systems to shrink from 1 pc to 0.1 pc. But we don't know what it is. The hope is that detailed studies of the orbit of OJ287 can provide some clues as to what that missing mechanism is.

AnimalMuppet•3mo ago
The diagram in the article shows them 0.02 apart, with no units that I can see. Parsecs? Light years? Arc-seconds? Does anybody know?

Other commenters have proposed 0.22 light years, but if that's it, it's off from the diagram by a factor of 10...

DaveZale•3mo ago
In Figure 3 (left panel), we show a detail of Paper II: the primary black hole is at the center, and the secondary black hole is at a PA of about 35°, at the distance of 20 μas from the primary black hole.

https://iopscience.iop.org/article/10.3847/1538-4357/ae057e

AnimalMuppet•3mo ago
Aha! Micro arc seconds!

Thank you.

OgsyedIE•3mo ago
Why can't they dissipate momentum by ejecting interloping matter that is smaller than individual stars, such as regions of interstellar-medium density gas?
antognini•3mo ago
They do, but there's just not that much mass compared to stars.
Avlin67•3mo ago
where is the image ?