frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Quad9 (DNS Resolver) to Exit France

https://quad9.net/news/blog/au-revoir-france/
211•farrokhi•2h ago•67 comments

eMudhra to exit global SSL/TLS certificate business

https://emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business
466•bo0tzz•2h ago•364 comments

What's Getting Pwned

https://pwn.watch/
136•mrkd•2h ago•86 comments

Show HN: Run full iOS 16.5 firmware on Android Devices

https://github.com/oosexgang/hackios-xnu-kernel
42•aghuang•1h ago•14 comments

What Is Gridifcation

https://musicalform.substack.com/p/what-is-gridifcation
229•gumby•3d ago•102 comments

Jailbreaking the Switch 2

https://pepsipu.com/blog/2026-10-switch2-jailbreak-ns2jb/
461•ledoge•8h ago•167 comments

Where Wealth Is Moving in America

https://thestatedtruth.com/?p=28732
6•hihetej•10m ago•2 comments

Faster than earcut: triangulating 3.7M map polygons in 489 ms

https://globus.software/blog/2026/10/16/cutting-map-polygons/
144•molind•7h ago•30 comments

Google cleared 300 hectares of Finnish forest

https://www.techspot.com/news/114100-google-cleared-300-hectares-finnish-forest-data-center.html
67•wetwater•1h ago•38 comments

WorldTUI: I trained a 360M model to pretend to be a terminal

https://simedw.com/2026/10/21/world-model-terminal/
417•alphax314•14h ago•129 comments

The Last Museum: Semantic search across 5.8M artworks from major museums

https://lastmuseum.com/
44•surprisetalk•3h ago•13 comments

VMMouse for NT 3.x: QEMU/VMware mouse integration driver

https://github.com/rhargreaves/vmmouse-nt3
23•kiyouta•3d ago•4 comments

Crystal 1.22

https://crystal-lang.org/2026/10/12/1.22.0-released/
107•ksec•3h ago•52 comments

Dungeon Generation in the Gnomish Mines of NetHack

https://www.boristhebrave.com/2026/10/18/dungeon-generation-in-the-gnomish-mines-of-nethack/
6•ibobev•3d ago•0 comments

Pentulive (Puppy Live) [video]

https://yle.fi/t/18-332106/fi
37•NaOH•3d ago•6 comments

The recently proposed o(n log n) integer multiplication algorithm [pdf]

https://web.maths.unsw.edu.au/~davidharvey/research/subnlogn.pdf
279•craigcitro•14h ago•236 comments

The painter behind Manhattan’s Gilded Age interiors

https://engelsbergideas.com/notebook/the-unknown-painter-behind-manhattans-gilded-age-interiors/
37•hoffmannesque•1d ago•4 comments

Show HN: Uberblok – an interactive museum of ZFS internals

https://uberblok.storagebits.workers.dev/
10•storagebits•1d ago•0 comments

Startup taps underwater volcano as energy source in "proof point" test

https://arstechnica.com/science/2026/10/startup-taps-underwater-volcano-as-energy-source-in-proof...
77•wffurr•2d ago•33 comments

Security Disclosure

https://blog.railway.com/p/security-disclosure-wednesday-october-21st
550•passenger•18h ago•318 comments

Amazon identifies Oct 17 PHP2Shell exploitation prior to public disclosure

https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitatio...
184•cubefox•4h ago•53 comments

MPs moving to restrict gambling ads in Canada amid mounting harms

https://www.cbc.ca/news/investigates/gambling-ads-restrictions-canada-9.7388888
46•Teever•2h ago•13 comments

Several Linux kernel vulnerabilities accidentally posted to public mailing list

https://www.phoronix.com/news/LKML-New-Trend-Vulnerabilities
197•mrkn1•5h ago•57 comments

Eigenmoon: linear algebra puzzles by moonlight

https://eigenmoon.vercel.app/
46•jessicarumbelow•2d ago•12 comments

Claude Duet

https://claude.com/product/claude-duet
509•kuberwastaken•21h ago•465 comments

SBD: We Have a Filesystem at Home

https://fly.io/blog/sprites-block-device/
33•torutofu•3h ago•24 comments

No more icons in every menu by default

https://blog.jim-nielsen.com/2026/icons-in-every-menu/
427•riffraff•2d ago•242 comments

Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor

https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/
576•abhisek•1d ago•186 comments

Using LLM for confidence scoring is a bad idea

https://rumple.github.io/blog/2026/10/20/asking-llm-for-confidence.html
168•jimauthors•1d ago•92 comments

GitLab critical patch release

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
395•artooro•21h ago•90 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.