frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kobo can run apps now

https://bandarlabs.github.io/Cobalt/
161•thepoet•2h ago•64 comments

Felony Bench

https://www.felonybench.com/
196•colinprince•3h ago•92 comments

Kagi added a setting for removing paywalled links from search results

https://kagi.com/changelog#11296
791•speckx•5h ago•280 comments

Scientists release biggest 2D map of the universe

https://newscenter.lbl.gov/2026/08/10/scientists-release-biggest-2d-map-of-the-universe/
19•NKosmatos•34m ago•3 comments

AI boosted homework scores, then exam scores dropped: study

https://www.economist.com/graphic-detail/2026/08/18/does-ai-stop-children-from-learning
84•dash2•2d ago•148 comments

I accidentally logged hundreds of thousands of phone calls to military bases

https://lina.sh/blog/hijacking-e164-arpa
270•gavide•5h ago•33 comments

DeepSeek-v4-flash-vision-exp

https://api-docs.deepseek.com/guides/vision/
392•dares2573•8h ago•129 comments

I ran Photoshop on a £0.60 computer chip

https://pointinthecloud.com/2026-08-19-144600.html
41•colinprince•3h ago•4 comments

Felony charges for citizen deleting phone data at US Border

https://www.nytimes.com/2026/08/21/us/politics/samuel-tunick-deleted-phone-felony.html
97•floathub•7h ago•160 comments

LiteLLM (YC W23) Is Hiring – Rust / Performance Engineers

https://jobs.ashbyhq.com/litellm/3f326076-7415-46a1-921e-8a1b1d6ee2b6
1•ij23•2h ago

Rebuilding our Electron meeting-recording engine in Swift

https://circleback.ai/blog/how-we-rebuilt-our-electron-recording-engine-in-swift
29•arguiot•1h ago•3 comments

People of ACM – Russ Cox

https://www.acm.org/articles/people-of-acm/2026/russ-cox
14•signa11•4d ago•1 comments

How we made a text-to-speech model respond in sub-50 ms

https://nari-labs.com/blog/qwen3-tts-speed-cost-frontier/
35•toebee•3h ago•9 comments

A look under our trunk: what's in our compute

https://waymo.com/blog/2026/08/look-under-our-trunk/
21•ra7•1d ago•2 comments

What happens when a GPU reads memory

https://blog.doubleword.ai/what-happens-when-a-gpu-reads-memory
40•ibobev•2h ago•10 comments

Kodak's "pre-invented" lunar orbiter camera; or, the fate of SAMOS readout

https://invertingvision.com/2026/08/10/kodaks-pre-invented-lunar-orbiter-camera-or-the-fate-of-sa...
38•cainxinth•5h ago•1 comments

Does whispering to agents in docs help?

https://passo.uno/if-you-are-an-agent-read-this/
25•theletterf•4d ago•6 comments

Quantifying the honey bee dance floor

https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0341456
14•Ariarule•1w ago•1 comments

Another better lower bound for n=17 square packing

http://gus-massa.blogspot.com/2026/08/another-better-lower-bound-for-n17.html
16•gus_massa•2h ago•1 comments

Building an (almost) fully self-hosted, sandboxed, agentic software factory

https://blog.jakesaunders.dev/building-an-almost-fully-self-hosted-sandboxed-agentic-software-fac...
28•jakelsaunders94•2h ago•20 comments

I'm becoming AI-blind

https://cymerys.com/w/im-becoming-ai-blind
134•rcymerys•7h ago•128 comments

Decayfmt – a file format that corrupts itself a little every time you open it

https://github.com/aravpanwar/decayfmt
21•unprovable•3h ago•6 comments

New Worlds: We are living in the future of J.G. Ballard or William Gibson

https://precastreinforced.co.uk/2026/08/16/new-worlds/
154•speckx•6h ago•107 comments

The road to ACID transactions in Cassandra 6

https://theconsensus.dev/p/2026/08/16/transactions-in-cassandra.html
43•eatonphil•7h ago•1 comments

Show HN: Shoehorn – Quantize any model down to run on your machine

https://notactuallytreyanastasio.github.io/shoehorn/
51•rhgraysonii•3d ago•10 comments

Radiation damage to Hubble has been 4.3 years out of phase with the Solar cycle

https://arxiv.org/abs/2608.18214
84•pppone•5h ago•28 comments

Show HN: Proliferate- open-source, self-hostable Codex for any coding agent

https://github.com/proliferate-ai/proliferate
23•pablo24602•2h ago•12 comments

The coolest anti-surveillance tools at Defcon [video]

https://www.youtube.com/watch?v=-2uAsJ5EPAw
73•neom•3d ago•5 comments

Galactic Compass 2: now with new augmented reality mode

https://interconnected.org/home/2026/08/21/galactic
7•bobbiechen•1h ago•2 comments

Claudette: Make Claude stop talking like a BuzzFeed article

https://github.com/adnanakil/nobuzz/blob/main/README.md
89•aakil•4h ago•81 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.