frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GPT-5.6 Sol can beat Factorio on peaceful mode

https://ryanmadden.net/gpt-56-beats-factorio/
80•ryanmadden•1h ago•66 comments

TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8

https://atlasum.net/blog/cve-2026-98432-linux-ipv4-tcp-uaf
57•oger•1h ago•30 comments

The Duty of a Scholar

https://www.daemonology.net/blog/2026-10-31-The-Duty-of-a-Scholar.html
35•gslin•1h ago•7 comments

It's the Memory Latency, Stupid

https://pivotlake.io/blog/its-the-memory-latency-stupid/
28•ntur1337•1h ago•3 comments

Hackers hijack Egypt highway billboard and Malaysian screens to show porn

https://www.cairoreport.org/p/egypt-brazil-iraq-billboard-hack
35•entryleveljobsc•2h ago•38 comments

Show HN: NES Contra (1987) port (ASM –> C and then C –> WebAssembly)

https://epoyraz.github.io/nes-contra-us/
8•tevlon•1h ago•2 comments

Molly (Signal fork) has not been updated since 3 months and is vulnerable

https://piefed.world/post/1503394
262•DeepLogin•9h ago•158 comments

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
9•karpathy•24m ago•1 comments

Jepsen: ParticleDB 1.1.4

https://jepsen.io/analyses/particledb-1.1.4
112•aphyr•6h ago•50 comments

Show HN: A language model that lives in a boot sector

https://github.com/kerlenton/bootgpt
13•kerlenton•7h ago•0 comments

Do the math: How we took over ChatGPT accounts

https://www.parameter.ai/labs/we-found-a-gap-at-openai
277•armcat•9h ago•128 comments

Much Ado About None: Sentinel Values in Python

https://florianwilhelm.info/2026/10/sentinel_values/
12•sebg•1d ago•2 comments

Redox: Ring Buffers Project Summary

https://www.redox-os.org/news/nlnet-rb-summary/
32•g0xA52A2A•3d ago•4 comments

I post trained a model on Demoscenes

https://datavorous.com/writing/demoscener/
30•datavorous_•2h ago•16 comments

Noctua Fan Swap on a Calnex Rb/GPS Frequency Reference

https://www.jeffgeerling.com/blog/2026/noctua-fan-swap-calnex-rb-gps-frequency-reference/
18•aray07•2d ago•10 comments

William Nordhaus has died

https://news.yale.edu/2026/10/31/william-nordhaus-nobel-laureate-who-integrated-economics-and-cli...
25•ilreb•2h ago•1 comments

Simple circuits can create complex behaviors

https://aatishb.com/myriad/lets-build-a-brain/
170•aatish•4d ago•55 comments

Casio Watches of the 1980s

https://www.casio.com/us/watches/50th/Heritage/1980s/
162•karagenit•4h ago•79 comments

Reading and writing are less symmetric than you (probably) think

https://fgiesen.wordpress.com/2015/10/25/reading-and-writing-are-less-symmetric-than-you-probably...
53•luu•3d ago•18 comments

Switch Lowering in GCC

https://xoranth.net/gcc-switch/
177•signa11•12h ago•34 comments

Serbia just elected the world's brainiest parliament

https://www.science.org/content/article/serbia-just-elected-world-s-brainiest-parliament
732•input_sh•9h ago•425 comments

Digital minimalism

https://vitalik.eth.limo/general/2026/10/31/digital_minimalism.html
267•wilbertliu•14h ago•200 comments

Show HN: Ghostman – A fast, keyboard-driven TUI API client and webhook inspector

https://github.com/4yk5/Ghostman
29•4yk5•1d ago•23 comments

Malware uses LLMs to rank victims by how much they're worth

https://blog.talosintelligence.com/appraisal-by-ai-model-driven-victim-prioritization-in-the-volt...
206•khalidkhair•5h ago•111 comments

The Impact of Generative AI on Critical Thinking: Self-Reported (2025)

https://dl.acm.org/doi/full/10.1145/3706598.3713778
60•the-mitr•2h ago•39 comments

AI, Lean, and the Future of Formal Verification, with Lean Creator Leo de Moura

https://thedataexchange.media/leo-de-moura-lean-aws/
171•datascientist•2d ago•38 comments

Show HN: A USB-C LTE modem that gives my computer a phone line

https://github.com/Koppar-AI/koppar-lte-modem
18•abijahkaj•4h ago•5 comments

What is a light-day? The milestone Voyager 1 is closing in on

https://science.nasa.gov/mission/voyager/voyager-1/voyager-1-what-is-a-light-day/
66•geox•4h ago•34 comments

Show HN: Marelleo, an open-source story box I built for my kids using ESP32

https://zebra.rodeo/en/blog/marelleo/
172•foOg•4d ago•46 comments

Copyright Office is restoring copyright to something you have to work to get

https://pluralistic.net/2026/10/31/burn-berne/#unvictored
39•beardyw•3h ago•25 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.