frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

PHP 8.2.35

https://github.com/php/php-src/releases/tag/php-8.2.35
475•tuyuri•1h ago•197 comments

PHP2Shell: AI uncovers critical RCE in PHP

https://www.wiz.io/blog/php2shell-php-rce
278•danlark1•2h ago•76 comments

DuckDB 2.0.0 LTS "Cinnamon Teal"

https://duckdb.org/2026/10/21/announcing-duckdb-200
133•nnx•1h ago•11 comments

Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds

https://scotthelme.co.uk/eight-bits-of-trust-emudhras-ca-keys-cracked-in-milliseconds/
547•hkc•6h ago•241 comments

Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor

https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/
52•abhisek•1h ago•19 comments

Patch the Planet: global response coordination as agents uncover vulnerabilities

https://openai.com/index/coordinated-disclosure-of-critical-vulnerabilities/
91•nr378•1h ago•47 comments

The No Kings Takedown Is Why You Shouldn't Rent Your Megaphone from Zuck

https://www.techdirt.com/2026/10/20/accident-or-not-the-no-kings-takedown-is-why-you-shouldnt-ren...
216•robtherobber•1h ago•145 comments

Oregon lawmakers approve money to buy an iconic waterfall listed on Redfin

https://apnews.com/article/oregon-waterfall-for-sale-lawmakers-996de63462d49ec3ad9bee1629fb9488
5•surprisetalk•23m ago•2 comments

Most advice is right for the person giving it

https://coached.com/essays/most-advice-is-right-for-the-person-giving-it/
89•rohanm93•2h ago•69 comments

Qwen3-Coder writes less secure code when told it's for a US persona

https://www.hirundo.io/blog/qwen3-coder-vulnerabilities
201•mattifrank•3h ago•101 comments

LayerFS: The filesystem for AI coding agents

https://layerfs.ai/
45•l2dy•3h ago•25 comments

Upcoming critical PHP security release (CVE-2026-109618 / -109619)

https://news-web.php.net/php.announce/509
1427•xd•19h ago•602 comments

9 Mothers (YC P26) Is Hiring in Austin, TX

https://9mothers.com/careers
1•ukd1•3h ago

C++ futures part 1: The mental model

https://devblogs.microsoft.com/oldnewthing/20261012-00/?p=112767/
21•ibobev•1d ago•5 comments

The Future of CSS

https://www.joshwcomeau.com/css/interop-2027/
521•soheilpro•13h ago•220 comments

Using thousands of AI agents to uncover new leads in biological data

https://openai.com/index/scaling-ai-research-for-complex-biological-data/
24•raahelb•2h ago•3 comments

Way to Play Super Mario 64: On Apple Vision Pro

https://www.pagetable.com/303
123•frizlab•2d ago•41 comments

Delays for Pull Requests and Webhook deliveries

https://www.githubstatus.com/incidents/nms1dpzmh9d9
36•bearsyankees•46m ago•9 comments

Show HN: SimCity, but with Permits

https://permit.petercai.com/
877•pcai•21h ago•396 comments

Muse exposes users' personal and business secrets when they share conversations

https://arstechnica.com/security/2026/10/meta-muse-exposes-users-personal-and-business-secrets-wh...
292•gumby•14h ago•140 comments

PHP2Shell

https://www.php2shell.com
18•nr378•1h ago•2 comments

Show HN: Sumi.css – CSS Framework

https://github.com/vladocar/Sumi.css
20•bepero•2h ago•6 comments

Dutch National Cyber Security Center is Offline because it uses PHP

https://www.ncsc.nl/actueel
232•jacquesm•3h ago•75 comments

The Decoherence Trap

https://maevyn.codes/decoherence
119•cassianoleal•2d ago•51 comments

Voxtral 3

https://mistral.ai/news/voxtral-3/
745•ilreb•23h ago•192 comments

Whatever Happened to Fire Escapes

https://practical.engineering/blog/2026/10/20/whatever-happened-to-fire-escapes
129•sohkamyung•5h ago•87 comments

The Lucrative World of Literary Scams

https://www.thedial.world/articles/news/ai-book-scams
37•samclemens•2d ago•4 comments

Feds suspect ransom negotiator ran ShinyHunters extortion site

https://krebsonsecurity.com/2026/10/feds-suspect-ransom-negotiator-ran-shinyhunters-extortion-site/
246•Bender•17h ago•124 comments

Good type against all odds

https://unsung.aresluna.org/good-type-against-all-odds/
180•firloop•13h ago•15 comments

The Other Epidemic: Trying to get off benzodiazepines

https://www.thebeliever.net/the-other-epidemic/
253•gaplong•16h ago•200 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.