frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open Molten Claw: Post-Eval as a Service

https://idiallo.com/blog/open-molten-claw
1•watchful_moose•23s ago•0 comments

New York Budget Bill Mandates File Scans for 3D Printers

https://reclaimthenet.org/new-york-3d-printer-law-mandates-firearm-file-blocking
1•bilsbie•1m ago•0 comments

The End of Software as a Business?

https://www.thatwastheweek.com/p/ai-is-growing-up-its-ceos-arent
1•kteare•2m ago•0 comments

Exploring 1,400 reusable skills for AI coding tools

https://ai-devkit.com/skills/
1•hoangnnguyen•3m ago•0 comments

Show HN: A unique twist on Tetris and block puzzle

https://playdropstack.com/
1•lastodyssey•6m ago•0 comments

The logs I never read

https://pydantic.dev/articles/the-logs-i-never-read
1•nojito•7m ago•0 comments

How to use AI with expressive writing without generating AI slop

https://idratherbewriting.com/blog/bakhtin-collapse-ai-expressive-writing
1•cnunciato•8m ago•0 comments

Show HN: LinkScope – Real-Time UART Analyzer Using ESP32-S3 and PC GUI

https://github.com/choihimchan/linkscope-bpu-uart-analyzer
1•octablock•9m ago•0 comments

Cppsp v1.4.5–custom pattern-driven, nested, namespace-scoped templates

https://github.com/user19870/cppsp
1•user19870•10m ago•1 comments

The next frontier in weight-loss drugs: one-time gene therapy

https://www.washingtonpost.com/health/2026/01/24/fractyl-glp1-gene-therapy/
1•bookofjoe•13m ago•1 comments

At Age 25, Wikipedia Refuses to Evolve

https://spectrum.ieee.org/wikipedia-at-25
1•asdefghyk•15m ago•3 comments

Show HN: ReviewReact – AI review responses inside Google Maps ($19/mo)

https://reviewreact.com
2•sara_builds•16m ago•1 comments

Why AlphaTensor Failed at 3x3 Matrix Multiplication: The Anchor Barrier

https://zenodo.org/records/18514533
1•DarenWatson•17m ago•0 comments

Ask HN: How much of your token use is fixing the bugs Claude Code causes?

1•laurex•20m ago•0 comments

Show HN: Agents – Sync MCP Configs Across Claude, Cursor, Codex Automatically

https://github.com/amtiYo/agents
1•amtiyo•21m ago•0 comments

Hello

2•otrebladih•22m ago•1 comments

FSD helped save my father's life during a heart attack

https://twitter.com/JJackBrandt/status/2019852423980875794
2•blacktulip•25m ago•0 comments

Show HN: Writtte – Draft and publish articles without reformatting, anywhere

https://writtte.xyz
1•lasgawe•27m ago•0 comments

Portuguese icon (FROM A CAN) makes a simple meal (Canned Fish Files) [video]

https://www.youtube.com/watch?v=e9FUdOfp8ME
1•zeristor•29m ago•0 comments

Brookhaven Lab's RHIC Concludes 25-Year Run with Final Collisions

https://www.hpcwire.com/off-the-wire/brookhaven-labs-rhic-concludes-25-year-run-with-final-collis...
2•gnufx•31m ago•0 comments

Transcribe your aunts post cards with Gemini 3 Pro

https://leserli.ch/ocr/
1•nielstron•35m ago•0 comments

.72% Variance Lance

1•mav5431•36m ago•0 comments

ReKindle – web-based operating system designed specifically for E-ink devices

https://rekindle.ink
1•JSLegendDev•38m ago•0 comments

Encrypt It

https://encryptitalready.org/
1•u1hcw9nx•38m ago•1 comments

NextMatch – 5-minute video speed dating to reduce ghosting

https://nextmatchdating.netlify.app/
1•Halinani8•39m ago•1 comments

Personalizing esketamine treatment in TRD and TRBD

https://www.frontiersin.org/articles/10.3389/fpsyt.2025.1736114
1•PaulHoule•40m ago•0 comments

SpaceKit.xyz – a browser‑native VM for decentralized compute

https://spacekit.xyz
1•astorrivera•41m ago•0 comments

NotebookLM: The AI that only learns from you

https://byandrev.dev/en/blog/what-is-notebooklm
2•byandrev•41m ago•2 comments

Show HN: An open-source starter kit for developing with Postgres and ClickHouse

https://github.com/ClickHouse/postgres-clickhouse-stack
1•saisrirampur•42m ago•0 comments

Game Boy Advance d-pad capacitor measurements

https://gekkio.fi/blog/2026/game-boy-advance-d-pad-capacitor-measurements/
1•todsacerdoti•42m ago•0 comments
Open in hackernews

Show HN: Student attempt at proving P ≠ NP using geometry and lattices

https://zenodo.org/records/16759468
6•LaghZen•6mo ago
Hi everyone,

I’m a student with a strong interest in computer science and complexity theory. Recently, I worked on a manuscript attempting to prove that P ≠ NP.

I know how this sounds — it’s one of the hardest and most debated problems in CS, and many have tried and failed. I don’t claim to have the final answer, but I believe the approach I used might at least offer some fresh perspective or provoke useful critique.

The idea involves geometric separation between deterministic and nondeterministic computation, using high-dimensional lattice constructions and some physics-inspired intuition. The full argument is technical, but I tried to keep it logically structured.

The preprint is 93 pages long. It was originally written in Russian, and I created an English version via machine translation, so apologies in advance for awkward wording or formatting.

DOI and full paper (both languages): https://doi.org/10.5281/zenodo.16759468

I’m genuinely open to feedback — whether it’s pointing out flaws, questioning assumptions, or just explaining why this approach doesn’t work. Any form of critical input is welcome.

If there’s interest, I can also create a short video explanation in simple terms to walk through the core ideas — even though I don’t have a channel or any audience yet.

Thanks in advance for taking the time, even if it’s just to skim or tell me what to fix!

Comments

doormatt•6mo ago
Just to clarify, how exactly does proving exponential lower bounds for Algphys translate into a proof that no polynomial time algorithm exists for NP-complete problems in the standard Turing model?

Isn’t it possible that your "hard" instances could be solvable in polynomial time by some algorithm that doesn’t rely on geometric modeling or Hamiltonian dynamics?

How do you justify that every polynomial-time Turing machine algorithm can be modeled as a trajectory in your Hamiltonian system?

LaghZen•6mo ago
Hi! Thanks for the question!

1. Algphys is shown to be equivalent to P, meaning any polynomial-time Turing algorithm can be modeled in Algphys. The paper constructs "frustrated" 3-SAT instances requiring exponential time in Algphys due to high combinatorial complexity and spectral properties (e.g., Hessian eigenvalues growing as ~ 2^n). Since Algphys = P, this implies no polynomial-time Turing algorithm can solve NP-complete problems.

2. The equivalence of Algphys and P means any polynomial-time algorithm, regardless of approach, can be modeled in Algphys. The exponential lower bound for these instances in Algphys applies to all polynomial-time Turing algorithms, suggesting these "hard" instances are inherently exponential, no matter the method.

3. The paper establishes P ~ Algphys by mapping Turing machine states to points on a symplectic manifold, with the cost function H encoding computation steps. The Hamiltonian dynamics (γ̇(t) = J∇H(γ(t))) simulate the algorithm’s execution path, ensuring every polynomial-time algorithm corresponds to a trajectory in Algphys.

doormatt•6mo ago
Thanks for the reply! Just to clarify, your proof is relying on the assumption that if an algorithm can be modeled in Algphys, then its execution time in Algphys reflects its true time complexity, right? But can you point to where you prove that modeling a polynomial-time Turing machine in Algphys necessarily results in a polynomial-time trajectory in your framework, across all problem instances? Specifically, how do you rule out the possibility that the mapping itself introduces exponential distortion in some cases?
LaghZen•6mo ago
Thanks for the follow-up!

Equivalence of P and Algphys: Section 2.3 and Appendix D show any polynomial-time algorithm can be modeled in Algphys with preserved complexity.

Polynomial Mapping: Section 2.2 and Appendix C detail symplectomorphic reductions, ensuring mappings like those for 3-SAT are polynomial-time computable.

No Exponential Distortion: Appendix F (Elimination of Objections) addresses concerns like exponential precision, confirming mappings don’t inflate complexity for polynomial algorithms.

The exponential bounds come from the inherent structure of NP-complete problems, not the mapping itself.

doormatt•6mo ago
You mention that Algphys can simulate any polynomial-time Turing algorithm with preserved complexity, but in your construction, the dynamics of Algphys are governed by physical properties: gradient norms, Hessian spectra, rigidity, etc. How do you guarantee that these geometric constraints don’t impose an exponential slowdown on some Turing algorithms that would otherwise run in polynomial time? Specifically, where do you prove that no such algorithm is mapped into a high-rigidity trajectory with exponential execution time?
LaghZen•6mo ago
You’re right — the paper does not currently contain an explicit theorem stating, word-for-word, that “every polynomial-time Turing machine is mapped to a low-rigidity region.”

In section C.4, at the end of step 4, there is a statement: the Hessian spectrum creates obstacles for polynomial algorithms in certain places, which can be interpreted as areas of high rigidity. However, it does not explicitly state that algorithms never enter these areas, but only highlights their difficulties. I agree that this is not written down as the only explicit lemma of the form you asked for.

I can add an explicit lemma to the appendix, which will specify in the required form the property that polynomial-time algorithms never fall into areas with high rigidity, and I will update the preprint. Meanwhile, the existing material (Thm. 2.5, Thms. C.1/C.4, App. F.4, Thm. E.1) contains ingredients that substantiate the claim; the new lemma will make this reference explicit.

If you want, I can update the preprint soon and report back with the precise lemma number and page.

doormatt•6mo ago
Thanks so much for being so open and willing to discuss this!

Just to be clear though, if that lemma isn’t yet explicitly proven, then the core claim (that Algphys cannot simulate certain NP-complete solutions in polynomial time) has not been established. I agree the components may suggest difficulty in high-rigidity regions, but unless you formally prove that no polynomial-time Turing machine’s trajectory enters those regions, the P != NP conclusion doesn’t follow.

LaghZen•6mo ago
Thanks for the help! It will take at least a week to fix the gap. During the addition, I came across a more serious problem: there was a contradiction between the "hard" function (ε = 2^(—n)) and the statement Algphys ⊆ P. I'm dealing with this now, and I'll need additional verification.