frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AI's top startups are barely publishing their research

https://www.science.org/content/article/ai-s-top-startups-are-barely-publishing-their-research
245•YeGoblynQueenne•5h ago•135 comments

The coolest use for the Vision Pro

https://christianselig.com/2026/07/vision-pro-house/
421•robbiet480•6h ago•196 comments

A pharmacy chain in Vermont implemented AI for efficiency

https://vtdigger.org/2026/07/29/a-pharmacy-chain-in-vermont-implemented-ai-for-efficiency-its-led...
22•omerhj•1h ago•18 comments

Show HN: Open-source engine running Gemma 4 26B in 2 GB RAM on any M-series Mac

https://github.com/drumih/turbo-fieldfare
665•gitpusher42•11h ago•233 comments

Superlogical

https://www.superlogical.com/
545•yan•11h ago•338 comments

LLM Honeypot

https://llm2human.pages.dev/
77•8thom•3h ago•31 comments

Keychron announces first open-source firmware for gaming mice

https://www.digitalfoundry.net/news/2026/07/keychron-announces-first-open-source-firmware-for-gam...
299•JLO64•10h ago•112 comments

The Cold Email

https://zachholman.com/posts/cold-email
101•holman•5h ago•41 comments

The Productivity Mirage

https://frantic.im/mirage/
55•msephton•3h ago•18 comments

Anatomy of a Frontier Lab Agent Intrusion: A Timeline of the July 2026 Incident

https://huggingface.co/blog/agent-intrusion-technical-timeline
304•artninja1988•1d ago•182 comments

KOReader

https://koreader.rocks/
675•Cider9986•15h ago•213 comments

Kimi K3-256k

https://www.kimi.com/code/docs/en/kimi-code/models
350•monneyboi•7h ago•103 comments

A.I. companies are recruiting electricians and carpenters by the thousands

https://www.nytimes.com/2026/07/29/business/economy/data-center-electricians-training.html
227•thm•11h ago•285 comments

Document-borne AI worms can self-propagate through Copilot for Word

https://enklypesalt.com/posts/context-collapse-part3-ai-worming-through-word/
350•Canopy9560•14h ago•268 comments

Handbook.md shows that long policy documents do not reliably govern agents

https://arxiv.org/abs/2607.25398
300•spIrr•13h ago•185 comments

Angels in Coptic Magic I: Introduction

https://www.coptic-magic.phil.uni-wuerzburg.de/index.php/2026/01/16/angels-in-coptic-magic-i-intr...
9•jruohonen•3d ago•0 comments

SalesPatriot (YC W25) Is Hiring FDEs

https://www.ycombinator.com/companies/salespatriot/jobs/M46X6YX-forward-deployed-engineer
1•maciejSz•5h ago

Turning a dumb AC unit smart (without losing my security deposit)

https://prilik.com/blog/post/automating-ac-nyc/
114•austinallegro•8h ago•93 comments

A Trampoline

https://dogdogfish.com/blog/2026/07/29/a-trampoline/
74•matthewsharpe3•6h ago•42 comments

Show HN: CheapFoodMap – A map of good meals under $10

https://cheapfoodmap.com/
134•jaep1•9h ago•156 comments

Recursive Filters: SMA, EMA, Low‑Pass, and a Tiny Kalman

https://www.staszewski.xyz/blog/recursive-filters/
13•kamilstaszewski•1d ago•2 comments

Show HN: A local merge queue for parallel Claude Code agents

https://github.com/funador/claude-code-merge-queue
16•funador•2h ago•4 comments

Darktable

https://www.darktable.org/
303•siatko•14h ago•142 comments

Flume Water Monitor 915 MHz Security Is Pretty Good

https://waveformsecurity.com/blog/flume/
16•credibleconure•1h ago•5 comments

Commodification of Intelligence: Good, Bad, and Ugly Circular AI Deals

https://www.emergingtrajectories.com/lh/commodification-and-circularity/
62•cl42•7h ago•31 comments

Some thoughts about Anthropic's new cryptanalysis results

https://blog.cryptographyengineering.com/2026/07/29/some-notes-about-anthropics-new-results/
114•supermatou•10h ago•58 comments

Refactoring cuisine: how an Iraqi stew sailed to Singapore

https://iza.ac/posts/2026/07/the-journey-of-bamya/
25•infinitewalk•3d ago•6 comments

Launch HN: Tokenless (YC S26) – Automatic model switching to save money

https://usetokenless.com/
53•rohaga•10h ago•47 comments

Man and the Computer by John G. Kemeny (1972 book by the co-creator of BASIC)

https://archive.org/details/mancomputerbyjoh0000john
21•MilnerRoute•3h ago•9 comments

The Rust on ESP Book

https://docs.espressif.com/projects/rust/book/
128•AlexeyBrin•4d ago•13 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.