frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Sonnet 5

https://www.anthropic.com/news/claude-sonnet-5
810•marinesebastian•5h ago•457 comments

Claude Code is steganographically marking requests

https://thereallo.dev/blog/claude-code-prompt-steganography
1319•kirushik•8h ago•378 comments

From brain waves to words: a new path to communication without surgery

https://ai.meta.com/blog/brain2qwerty-brain-ai-human-communication/?_fb_noscript=1
88•alok-g•2h ago•47 comments

Hatari – Online Atari ST/STE/TT/Falcon Emulator

https://hatari.frama.io/hatari/online/hatari.html
20•gregsadetsky•1h ago•3 comments

Claude Science

https://claude.com/product/claude-science
335•lebovic•6h ago•111 comments

Nano Banana 2 Lite

https://deepmind.google/models/gemini-image/flash-lite/
286•minimaxir•7h ago•106 comments

How does a pull-back car work? Illustrated teardown

https://mechanical-pencil.com/products/car
81•Muhammad523•2d ago•21 comments

I ported Kubernetes to the browser

https://ngrok.com/blog/i-ported-kubernetes-to-the-browser
135•peterdemin•3h ago•44 comments

Leanstral 1.5

https://docs.mistral.ai/models/model-cards/leanstral-1-5-26-06
65•vetronauta•3h ago•9 comments

Hengefinder

https://hengefinder.com/
14•bookofjoe•2d ago•3 comments

TabFM: A zero-shot foundation model for tabular data

https://research.google/blog/introducing-tabfm-a-zero-shot-foundation-model-for-tabular-data/
22•brandonb•1h ago•4 comments

Ante: A new way to blend borrow checking and reference counting

https://verdagon.dev/blog/ante-blending-borrowing-rc
29•g0xA52A2A•2d ago•5 comments

I built a mmWave material classification radar (2025)

https://gauthier-lechevalier.com/radar
128•GL26•6h ago•35 comments

Stroustrup's Rule (2024)

https://buttondown.com/hillelwayne/archive/stroustrups-rule/
43•bmacho•3d ago•6 comments

CERN bids farewell to the LHC and enters Long Shutdown 3

https://home.cern/cern-bids-farewell-to-the-lhc-and-enters-long-shutdown-3/
97•HelloUsername•1d ago•25 comments

Long Island's decommissioned nuclear power plant

https://nickcarr.com/scouting-a-decommissioned-nuclear-power-plant/
55•mkmk•6d ago•7 comments

Tokyo has only two barley tea makers, we visited one to see how mugicha is made

https://soranews24.com/2026/06/30/tokyo-has-only-two-barley-tea-makers-and-we-visited-one-to-see-...
49•zdw•4h ago•10 comments

Building a custom octocopter from scratch with no prior hardware experience

https://karolina.mgdubiel.com/drone/
319•noleary•2d ago•69 comments

Show HN: My 13-year-old built an ant colony tracker

https://formicarium.es
32•abelgvidal•7h ago•24 comments

Reading the internals of Postgres: Database cluster, databases, and tables

https://www.buraksen.dev/articles/internals-of-postgresql-db-cluster-and-tables
45•buraksen•1d ago•0 comments

Knoppix

https://www.knopper.net/knoppix/index-en.html
238•hoangvmpc•11h ago•98 comments

Waveloop: What Fable left me

https://neynt.ca/writing/waveloop/
85•personjerry•4d ago•29 comments

Have you restarted your computer this week?

https://taonaw.com/2026/06/27/have-you-restarted-your-computer.html
94•surprisetalk•9h ago•203 comments

Memoirs of Extraordinary Popular Delusions and the Madness of Crowds (1852)

https://www.gutenberg.org/ebooks/24518
162•lstodd•11h ago•53 comments

I built a 10 inch mini rack from aluminium extrusions

https://louwrentius.com/i-build-a-10-inch-mini-rack-from-aluminium-extrusions.html
57•louwrentius•3d ago•26 comments

Understanding lattice risks: Many differences between marketing and reality

https://blog.cr.yp.to/20260630-risk.html
11•ledoge•2h ago•2 comments

Gone but Not Forgotten: Recovering the Dead Web

https://blog.archive.org/2026/04/23/gone-but-not-forgotten-recovering-the-dead-web/
7•wslh•2h ago•0 comments

RF hacking my cloud-controlled ceiling fan

https://samwilkinson.io/posts/2026-06-24-rf-hacking-dreo
36•sammycdubs•6d ago•13 comments

Matrix URIs, a URL syntax from Tim Berners-Lee that never shipped (1996)

https://www.w3.org/DesignIssues/MatrixURIs.html
47•napolux•4d ago•27 comments

Set up your own DoH (DNS over HTTPS) service

https://nochan.net/b/Internet-Crap/20260602-Set-Up-Your-Own-DoH-Service/
57•Bender•3d ago•22 comments
Open in hackernews

The Fastest Way yet to Color Graphs

https://www.quantamagazine.org/the-fastest-way-yet-to-color-graphs-20250512/
62•GavCo•1y ago

Comments

tonyarkles•1y ago
In case you haven't looked at the article, this is looking specifically at the Edge Coloring problem and not the more commonly known Vertex Coloring problem. Vertex Coloring is NP-complete unfortunately.
erikvanoosten•1y ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•1y ago
Wrong. You can convert edge-coloring problems into vertex-coloring problems of the so-called line graph: https://en.m.wikipedia.org/wiki/Line_graph

But the opposite is not true, because not every graph is a line graph of some other graph.

erikvanoosten•1y ago
Indeed. Thanks, I stand corrected.
tonyarkles•1y ago
Hrm... right. It's been a while. And it looks like both Vertex Coloring and Edge Coloring are both NP-complete (because of the O(n) procedure you're talking about and the ability to reduce both problems down to 3-SAT). I've started looking closer at the actual paper to try to figure out what's going on here. Thanks for the reminder, I miss getting to regularly work on this stuff.

Edit: thanks sibling reply for pointing out that it's not a bidirectional transform.

mauricioc•1y ago
For the edge-coloring problem, the optimal number of colors needed to properly color the edges of G is always either Delta(G) (the maximum degree of G) or Delta(G) + 1, but deciding which one is the true optimum is an NP-complete problem.

Nevertheless, you can always properly edge-color a graph with Delta(G) + 1 colors. Finding such a coloring could in principle be slow, though: the original proof that Delta(G) + 1 colors is always doable amounted to a O(e(G) * v(G)) algorithm, where e(G) and v(G) denote the number of edges and vertices of G, respectively. This is polynomial, but nowhere near linear. What the paper in question shows is how, given any graph G, to find an edge coloring using Delta(G) + 1 colors in O(e(G) * log(Delta(G))) time, which is linear time if the maximum degree is a constant.

Syzygies•1y ago
Yes. The article ran through this point as follows:

"In 1964, a mathematician named Vadim Vizing proved a shocking result: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum number of lines (or edges) connected to a single point (or vertex), and add 1."

I keep wondering why I ever read Quanta Magazine. It takes a pretty generous reading of "need" to make this a correct statement.

JohnKemeny•1y ago
phkahler•1y ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•1y ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•1y ago
Totally. The hard part isn't coloring (you can use simple heuristics to get a decent register assignment), rather, it's figuring out which registers to spill (don't spill registers in hot loops! and a million other things!).
NooneAtAll3•1y ago
and this post isn't even about vertex coloring
DannyBee•1y ago
No.

In SSA, the graphs are chordal, so were already easily colorable (relatively).

Outside of SSA, this is not true, but the coloring is still not the hard part, it's the easy part.

Not really. Coloring a graph is almost always talking about proper coloring, meaning that things that objects that are related receive different colors.

If you read the introduction, you'll also read that the goal is to "color each of your lines and require that for every point, no two lines connected to it have the same color."

Ps. "How many colors a graph needs" is a very well established term in computer science and graph theory.

mockerell•1y ago
I think the comment referred to the phrase „a graph needs X (colors or whatever)“. For me, this can be read two ways: 1. „a graph always needs at least X colors“ or 2. „a graph always needs at most X colors“.

Personally, I would interpret this as option 1 (and so did the comment above I assume). In that case, the statement is wrong. But I’d prefer to specify „at most/ at least“ anyways.

Or even better, use actual vocabulary. „For every graph there exists a coloring with X colors.“ or „any graph can be coloured using X colors“.

PS: I also agree with the sentiment about quanta magazine. It’s hard to get some actual information from their articles if you know the topic.

JohnKemeny•1y ago
What about this statement:

No matter how large a car is, it is easy to figure out how much money you'll need to buy it. Simply look at the price tag.

(From: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum ...)

mauricioc•1y ago
Parent's point is that sometimes (but not always) the store is perfectly fine selling you a car for $1 less than what the "price tag" of Delta(G)+1 dollars asks for, so "need" is a bit inaccurate.