frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
1077•karpathy•10h ago•322 comments

An Italian farmer found some unknown seeds in his attic and planted them

https://www.smithsonianmag.com/science-nature/italian-farmer-found-unknown-seeds-attic-with-nothi...
314•ecares•8h ago•88 comments

Brazilian Court Sanctions Lawyers for Prompt Injection in Court Filing

https://jetstream.security/insights/brazilian-court-sanctions-prompt-injection-filing/
76•doodlesdev•4h ago•26 comments

TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8

https://atlasum.net/blog/cve-2026-98432-linux-ipv4-tcp-uaf
456•oger•11h ago•208 comments

Memdoor: A team of 5 Qwen3.8-27B models beats Fable 5 on LiveCodeBench Hard

https://github.com/guregodevo/memdoor/tree/main/examples/workflows/team-solve
178•guregodevo•8h ago•94 comments

Leaking Secrets from Air-Gap Computers by Spelling Radio Signals from RAM (2024)

https://arxiv.org/abs/2409.02292
57•hapax_legomena•5h ago•27 comments

Pilot-wave hydrodynamics (Quantum phenomena in macroscopic hydrodynamic systems)

http://thales.mit.edu/bush/index.php/4801-2/
15•peter_d_sherman•1d ago•0 comments

Altoids Project

https://uvdn7.github.io/altoids-project/
90•uvdn7•8h ago•4 comments

Zinc creep in cable spelter sockets brought down the Arecibo telescope in 2020

https://maketecheasier.com/arecibo-zinc-creep-collapse/
81•ohjeez•1d ago•17 comments

It's the memory latency, stupid

https://pivotlake.io/blog/its-the-memory-latency-stupid/
176•ntur1337•12h ago•48 comments

A brief history of just-in-time: forty years of JIT work, from 1960–2000

https://dl.acm.org/doi/10.1145/857076.857077
17•gjvc•2d ago•0 comments

A 1580 Map Shows Why Data Visualization Is Never Neutral

https://thereader.mitpress.mit.edu/a-1580-map-shows-why-data-visualization-is-never-neutral/
26•the-mitr•1d ago•1 comments

Surviving "The Graduate"

https://www.newyorker.com/culture/the-weekend-essay/dustin-hoffman-on-surviving-the-graduate
104•samizdis•10h ago•31 comments

Running a bootstrapped SaaS for 20 years with my brother

https://blog.zamzar.com/2026/10/30/20-years-766-million-files-two-chameleons/
10•whyleyc•1d ago•0 comments

Edgar Allan Poe, Quintessential American Writer

https://slate.com/culture/2026/10/edgar-allan-poe-poems-stories-most-influential-american-writer-...
25•samclemens•3d ago•0 comments

ChatGPT and Codex usage limits merging

https://help.openai.com/en/articles/20001625-understanding-chatgpt-and-codex-usage-limits
70•Zariel•9h ago•26 comments

Jepsen: ParticleDB 1.1.4

https://jepsen.io/analyses/particledb-1.1.4
244•aphyr•17h ago•136 comments

Show HN: NES Contra (1987) port (ASM –> C and then C –> WebAssembly)

https://epoyraz.github.io/nes-contra-us/
81•tevlon•11h ago•48 comments

Electrification Could Cut Global Energy Use in Half

https://fullycharged.show/podcasts/podcast-361-why-electrification-could-cut-global-energy-use-in...
78•toomuchtodo•11h ago•23 comments

Do the math: How we took over ChatGPT accounts

https://www.parameter.ai/labs/we-found-a-gap-at-openai
319•armcat•20h ago•157 comments

OTape

https://www.otape.org/
14•dotmanish•4h ago•4 comments

Simple circuits can create complex behaviors

https://aatishb.com/myriad/lets-build-a-brain/
236•aatish•4d ago•77 comments

The Duty of a Scholar

https://www.daemonology.net/blog/2026-10-31-The-Duty-of-a-Scholar.html
110•gslin•11h ago•32 comments

Show HN: BBRouter – Ben Eater's 8-bit computer, simulated on 3D breadboards

https://bbrouter.com/bbrouter/ben-eater-sap-1
22•creack•6h ago•6 comments

Anthropic blocks users for anything touching training larger models

https://twitter.com/jiahaoshao1/status/2116475922190922088
303•pretext•11h ago•174 comments

Decode kernel panic from QR Code photo

https://gist.github.com/skorotkiewicz/c59e591c26661cb52b06afc42d8ac546
21•modinfo•1d ago•8 comments

Reading and writing are less symmetric than you (probably) think

https://fgiesen.wordpress.com/2015/10/25/reading-and-writing-are-less-symmetric-than-you-probably...
105•luu•3d ago•24 comments

Constructing a Quine from Kleene's Second Recursion Theorem

https://emarzion.github.io/KSRT/
16•mkckto•7h ago•1 comments

Show HN: A language model that lives in a boot sector

https://github.com/kerlenton/bootgpt
76•kerlenton•17h ago•3 comments

Sculpture re-creates odd optical effects of famed Lycurgus Cup

https://arstechnica.com/science/2026/10/scientists-recreate-the-1600-year-old-recipe-of-lycurgus-...
36•dverlaeckt80•1d ago•2 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

balloob•1y ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•1y ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•1y ago
Comments moved thither. Thanks!
pabs3•1y ago
They are two different articles, I don't think that was correct.
tomhow•1y ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•1y ago
Thanks for the response, guess that makes sense.
pabs3•1y ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?