frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Attention at Constant Cost per Token via Symmetry-Aware Taylor Approximation

https://arxiv.org/abs/2602.00294
52•fheinsen•1h ago•12 comments

FBI couldn't get into WaPo reporter's iPhone because Lockdown Mode enabled

https://www.404media.co/fbi-couldnt-get-into-wapo-reporters-iphone-because-it-had-lockdown-mode-e...
216•robin_reala•1h ago•147 comments

A sane but bull case on Clawdbot / OpenClaw

https://brandon.wang/2026/clawdbot
76•brdd•1d ago•113 comments

A case study in PDF forensics: The Epstein PDFs

https://pdfa.org/a-case-study-in-pdf-forensics-the-epstein-pdfs/
44•DuffJohnson•1h ago•8 comments

Data centers in space makes no sense

https://civai.org/blog/space-data-centers
870•ajyoon•20h ago•993 comments

Guinea worm on track to be 2nd eradicated human disease; only 10 cases in 2025

https://arstechnica.com/health/2026/02/guinea-worm-on-track-to-be-2nd-eradicated-human-disease-on...
50•bookofjoe•1h ago•12 comments

Show HN: Ghidra MCP Server – 110 tools for AI-assisted reverse engineering

https://github.com/bethington/ghidra-mcp
185•xerzes•8h ago•46 comments

Lessons learned shipping 500 units of my first hardware product

https://www.simonberens.com/p/lessons-learned-shipping-500-units
722•sberens•2d ago•335 comments

Old Insurance Maps – Georeferencing Sanborn Fire Insurance Maps on Modern Maps

https://oldinsurancemaps.net/
29•lapetitejort•1w ago•3 comments

Voxtral Transcribe 2

https://mistral.ai/news/voxtral-transcribe-2
6•meetpateltech•41m ago•0 comments

Brazilian Micro-SaaS Map

https://saas-map.ssr.trapiche.cloud/
59•acfilho•3d ago•3 comments

I miss thinking hard

https://www.jernesto.com/articles/thinking_hard
973•jernestomg•11h ago•540 comments

Coding Agent VMs on NixOS with Microvm.nix

https://michael.stapelberg.ch/posts/2026-02-01-coding-agent-microvm-nix/
12•secure•3d ago•5 comments

Show HN: Craftplan – I built my wife a production management tool for her bakery

https://github.com/puemos/craftplan
464•deofoo•2d ago•127 comments

New York’s budget bill would require “blocking technology” on all 3D printers

https://blog.adafruit.com/2026/02/03/new-york-wants-to-ctrlaltdelete-your-3d-printer/
569•ptorrone•23h ago•647 comments

The fax numbers of the beast, and other mathematical sports

https://cabinetmagazine.org/issues/57/wertheim.php
14•marysminefnuf•1d ago•5 comments

Deno Sandbox

https://deno.com/blog/introducing-deno-sandbox
491•johnspurlock•22h ago•151 comments

Agent Skills

https://agentskills.io/home
496•mooreds•1d ago•238 comments

High-Altitude Adventure with a DIY Pico Balloon

https://spectrum.ieee.org/explore-stratosphere-diy-pico-balloon
73•jnord•3d ago•25 comments

Thatcher Effect – Optical Illusion and Explanation

https://optical.toys/thatcher-effect/
15•robin_reala•1h ago•9 comments

Goblins: Distributed, Transactional Programming with Racket and Guile

https://spritely.institute/goblins/
88•alhazrod•4d ago•9 comments

X offices raided in France as UK opens fresh investigation into Grok

https://www.bbc.com/news/articles/ce3ex92557jo
493•vikaveri•1d ago•947 comments

AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

https://github.com/alibaba/AliSQL
262•baotiao•21h ago•39 comments

Xcode 26.3 – Developers can leverage coding agents directly in Xcode

https://www.apple.com/newsroom/2026/02/xcode-26-point-3-unlocks-the-power-of-agentic-coding/
340•davidbarker•21h ago•293 comments

The Mathematics of Tuning Systems

https://math.ucr.edu/home/baez/tuning_talk/
59•u1hcw9nx•4d ago•9 comments

Broken Proofs and Broken Provers

https://lawrencecpaulson.github.io/2026/01/15/Broken_proofs.html
31•RebelPotato•6h ago•5 comments

Exploring Different Keyboard Sensing Technologies

https://www.lttlabs.com/articles/2026/01/27/exploring-different-keyboard-sensing-technologies
57•viraptor•1w ago•40 comments

221 Cannon is Not For Sale

https://fredbenenson.com/blog/2026/02/03/221-cannon-is-not-for-sale/
289•mecredis•22h ago•221 comments

Reimplementing Tor from Scratch for a Single-Hop Proxy

https://foxmoss.com/blog/kurrat/
67•Agreed3750•3d ago•10 comments

The largest zip tie is nearly 4 feet long and $75

https://www.thedrive.com/news/youll-have-that-on-those-big-jobs-the-worlds-largest-zip-tie-is-nea...
126•PaulHoule•5d 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•8mo ago

Comments

tonyarkles•8mo 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•8mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•8mo 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•8mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•8mo 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•8mo 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•8mo 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•8mo ago
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•8mo 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•8mo 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•8mo 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.
phkahler•8mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•8mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•8mo 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•8mo ago
and this post isn't even about vertex coloring
DannyBee•8mo 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.