frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hybrid Reasoning Agents: LLM agents that think in latent space, act through text

https://arxiv.org/abs/2610.18861
278•allinonai•7h ago•155 comments

William Gibson and the trademarking of cyberspace

https://colo.to/cyberspace.html
103•Eric_Gullichsen•4h ago•19 comments

There's never been a better time to go into math (by: 3blue1brown) [video]

https://www.youtube.com/watch?v=LKrwhjOI8Nc
241•mdp2021•1d ago•264 comments

Superlite: A Faster Alternatie to Superpowers

https://contextfirst.blog/superlite-hand-an-agent-a-spec/
25•iheatuchriswogu•2h ago•11 comments

Someone behind the software

https://karrisaarinen.com/posts/someone-behind-the-software/
362•tosh•11h ago•144 comments

Laptop Based on 6502 CPU

https://www.maddox.pro/?p=448
61•nanochess•3d ago•25 comments

How Quickly Can the DoD Rebuild and Recast the Munitions Industrial Base?

https://www.csis.org/analysis/how-quickly-can-dod-rebuild-and-recast-munitions-industrial-base
36•gmays•4h ago•19 comments

The DNS Museum

https://dns.museum
24•zdw•2d ago•1 comments

RepRapMicron

https://github.com/VikOlliver/RepRapMicron/wiki
352•RobotToaster•14h ago•56 comments

Dogs seem to agree with humans that 'bouba' is round and 'kiki' is spiky

https://www.sciencealert.com/dogs-seem-to-agree-with-humans-that-bouba-is-round-and-kiki-is-spiky
164•gmays•1d ago•94 comments

Free Pascal compiler now supports dynamic packages

https://www.getlazarus.org/dynamic/
130•sysrpl•9h ago•28 comments

If you don't run your own LLM proxy, how do you know whats going on?

https://jrdsgl.com/if-you-dont-run-your-own-llm-proxy-how-the-fuck-do-you-even-know-whats-going-on/
79•amrrs•7h ago•58 comments

Show HN: WhatsApp MCP running free on Cloudflare

https://github.com/finereli/whatsapp-mcp
58•zoozla•6h ago•38 comments

PalmOS Lemmings

https://github.com/ardiri/palmos-lemmings
106•memalign•10h ago•24 comments

One parser, two bugs, many routers: Exploiting Broadcom WiFi across eCos, Linux

https://quentinkaiser.be/security/2026/10/16/one-parser-two-bugs/
58•zoobab•2d ago•9 comments

I built a programming language that LLMs can't use

https://blog.picheta.me/post/killswitch-lang/
114•dom96•1d ago•92 comments

Footage of the Flock search that a judge ruled was uncosntitutional

https://www.404media.co/watch-footage-of-the-flock-search-a-judge-ruled-unconstitutional/
56•anigbrowl•2h ago•15 comments

16-bit fully functional DIY magnetic core memory

https://www.youtube.com/watch?v=OJ1WYyO2jdY
45•oliculipolicula•4d ago•18 comments

"Traditional, but Puzzling"

https://unsung.aresluna.org/traditional-but-puzzling/
29•colinprince•2d ago•4 comments

"I'm on a war footing": Terry Tao and the crisis in math

https://www.nytimes.com/2026/10/16/us/math-ai-terence-tao.html
128•vinipolicena•2d ago•210 comments

Java sealed classes and exhaustive pattern matching

https://neilmadden.blog/2026/04/24/java-sealed-classes-and-exhaustive-pattern-matching/
149•hnisjafx40•13h ago•106 comments

A new way to think about borrow checking (in reverse)

https://verdagon.dev/blog/reverse-borrow-checking
33•verdagon•16h ago•4 comments

The First Candid

https://www.newyorker.com/magazine/2026/10/19/the-first-candid
48•Thevet•2d ago•12 comments

The Intel 8087 chip: floating-point addition and subtraction

https://www.righto.com/2026/10/8087-addition-subtraction-microcode.html
95•pwg•12h ago•33 comments

Open MicroManipulator – A sub-micrometer 3D motion control plattform

https://github.com/0x23/MicroManipulatorStepper
180•_Microft•17h ago•14 comments

Namecheap just seized and disabled all my domains

https://www.reddit.com/r/sysadmin/comments/1x8cycd/namecheap_just_seized_and_disabled_all_my_doma...
500•sashk•11h ago•249 comments

SIGSALY: Churchill's top secret hotline to the president

https://www.iwm.org.uk/history/iwm/cwr/telephone
121•stmw•4d ago•43 comments

I electrified my push scooter with a power drill

https://eddieabbondanz.io/post/shop/drill-powered-scooter/
159•speckx•4d ago•55 comments

Faster command recall with substring search

https://www.dantleech.com/blog/2026/10/15/faster-command-recall-with-substring-search./
3•speckx•3d ago•1 comments

Parser Combinators

https://t3.at/blog/2026-10-17-parser-combinators/
226•schindlabua•20h ago•81 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?