frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
752•speedping•5h ago•318 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
323•gmays•4h ago•211 comments

Inside Deutsche Bank

https://www.inside-db.com/
391•gyre007•5h ago•141 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
477•ritzaco•7h ago•162 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
185•Betelbuddy•4h ago•97 comments

The Magic of Partial Evaluation

https://jimmyhmiller.com/magic-of-partial-evaluation
51•aray07•2h ago•5 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
104•leumon•1h ago•84 comments

DaisyRose-27B: 1,200-task RL took Qwen3.8 from 5.6% to 12% on Terminal-Bench 4.1

https://www.radixark.com/blog/daisyrose-27b
19•de_sty•1h ago•4 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
74•vighneshiyer•3h ago•32 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
187•DeepLogin•6h ago•143 comments

Search Browser – Minimalist WebKit browser with Chrome extension support

https://searchbrowser.app/
14•rsaz•43m ago•5 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
100•zerocool0101•4h ago•17 comments

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

51•codekarate•3h ago•15 comments

The First Revolver: How We Got from Blackbeard's Six Pistols to the Six-Shooter

https://americanhandgunner.com/handguns/revolvers/the-first-revolver/
27•bushwart•3d ago•5 comments

KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

https://www.cve.org/CVERecord?id=CVE-2026-99312
145•Kozmik1•4h ago•95 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
94•raj-shekhar•4h ago•23 comments

Show HN: Nobody blocks a keyboard – Rooted Android as a physical USB Deck

https://github.com/mr-anjaneyam/Emittr
30•mr-anjaneyam•2d ago•32 comments

F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)

https://sam.gov/workspace/contract/opp/8948e8601e964c6aba9c801eee16b1be/view
120•birdboat00•5h ago•76 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
109•ibobev•6h ago•27 comments

CrossPoint Reader

https://crosspointreader.com
51•kristianpaul•3h ago•23 comments

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

27•ashriv•3h ago•25 comments

A Primer on Fourier Series (2025)

https://arxiv.org/abs/2510.18203
84•teleforce•6h ago•21 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
280•frenchmajesty•11h ago•44 comments

Evidence (YC S21) Is Hiring

https://www.ycombinator.com/companies/evidence/jobs/1xb9PpP-founding-gtm-lead
1•amcaskill•8h ago

Lakegres: Vector search on existing Open/Hudi/Iceberg tables

https://www.onehouse.ai/blog/lakegres-vector-search-on-open-table-formats
32•cloud8bits•3h ago•6 comments

When Free Software Isn't Free Enough

https://foss.life/notes/2026/free-software-isnt-free-enough/
17•hn_acker•2h ago•0 comments

Sexp Matrix

https://lisper.cc/ideas/entangle.html
5•todsacerdoti•46m ago•1 comments

SuperEMeans: Making e-means 3× faster

https://www.lkuffo.com/superemeans/
39•lkuffo2•4h ago•0 comments

Octopus, Gecko and Tortoise: the 3 scanners hunting your AI keys

https://tin.computer/blog/fake-ai-crawler-secrets-scanners
9•demegire•1h ago•1 comments

Show HN: Type Fighter 2

https://typefighter2.com/
110•torumitch•9h ago•51 comments
Open in hackernews

OpenEoX to Standardize End-of-Life (EOL) and End-of-Support (EOS) Information

https://openeox.org/
31•feldrim•1y ago

Comments

feldrim•1y ago
An SBOM-like approach to EOL/EOS issues is on the way.
rollcat•1y ago
I think the only large projects that presently take SBOMs seriously are Nix, Guix, and Go (non-cgo). Bootstrapping is non-trivial, but at least builds are reproducible and can be compared against existing binaries.

"Oh, just write plain C". Which compiler do you mean? GCC? LLVM/clang? On top of what OS/kernel? What firmware? Etc.

Arnavion•1y ago
Some distros packaging Rust software (OpenSUSE at least) also transparently set up CARGO=cargo-audit to get embedded SBOMs.
wallrat•1y ago
How does this relate to the OWASP/Ecma Common Lifecycle Enumeration Specification (https://tc54.org/cle/)?
wpollock•1y ago
In my experience, many software projects become abandoned and no notice is given. I don't see how this standard helps in such cases.
repelsteeltje•1y ago
I think it will take a while for people to realize this effort looked great, but wasn't the right approach. Or no silver bullet, at least.

The presentation with a simple diagram that combines this data with an sbom to yield "information" gives me navel gazing vibes of UML being the future of coding.

Just as architecture didn't equate to well designed and maintainable software, I fear this initiative won't fix horribly outdated and vulnerable deployments. Software life cycle, deprecation, abandonment, supply chains are mostly a process problem, standards and technology won't fix that.

Arnavion•1y ago
It doesn't force someone who already wasn't checking their dependencies for CVEs / maintained-ness to start doing that. It does make someone who *was* doing that be able to show they're doing that in some standard way.

In other words it doesn't force you to add an SBOM + EOX checker step to your CI pipeline. But if your compliance auditor wants you to check your dependencies, adding such a standardized step makes it easier to satisfy the auditor.

repelsteeltje•1y ago
I'm basing this mostly off first hand and anecdotal evidence - but through the years I've found that the major contribution of audits lies in having to think about the checkboxes every now and then. And what they mean in the context of my organization or project.

Rarely have I found that compliance to the goals was an issue in themselves. Or that making changes to tick a checkbox correlated to material improvements.

That is to say that if this leads to more efficiency and makes it easier for compliance audits and such, I fear is stream lining the least impactful part of its goals.

hiatus•1y ago
> Rarely have I found that compliance to the goals was an issue in themselves. Or that making changes to tick a checkbox correlated to material improvements.

I am confused when I hear people say stuff like this. I guess if you turn on a tool and never look at it again, it won't result in material improvements. But complying with regulations or a particular compliance regime should _absolutely_ result in at least _some_ material improvement to your security posture. Like you can implement segregation of duties just as a checkbox, or use the requirement to revisit the way you gate changes to production, as just one example.

T3OU-736•1y ago
Htm. So, how does this compare, and/or is different from https://endoflife.date?
Arnavion•1y ago
The standard is for software to report its own EOL / EOS status. The website you linked is the opposite direction - it's aggregating that status for a certain set of software.
T3OU-736•1y ago
Aha. Very good point. SW self-reporting requires buy-in, though, which seems like a pretty high barrier.

I am very much hoping the effort succeeds, but I am also mindful of the fact that the site to which I have linked is more successful by virtue of having better coverage.

captn3m0•1y ago
We (endoflife.date) are also excited about OpenEoX.
mud_dauber•1y ago
JEDEC has long maintained an EOL/EOS standard for semiconductors. This was a big part of a previous PM gig. Sounds boring, and it was. But having a process kept us out of serious hot water.
Hackbraten•1y ago
That EoX logo though.

Every organization or committee that designs a logo should be legally required to have at least one teenager on the board to prevent accidental goatse or other inadvertent blunders.

genter•1y ago
Goatse has been around long enough that the teenagers are now in their thirties.
repelsteeltje•1y ago
It depends on where you're coming from. Your code base, that is.

If it's already outstanding, you spend a lot of time revalidating what you already know and it's often a noisy process with many false positives.

If it's in a horrible state, however, the regulation often leaves a lot of wiggle room where you do some work to achieve, say, PCI compliance and then spend a lot of time arguing why this and that don't apply in your specific case.

So admitted, the is probably some improvement in the latter case but it's hardly proportional.

So IMHO, it doesn't help those of good will & expertise and does too little for the negligent. It adds noise and in the end quality still depends on factors other than compliance and certification.