frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Jane Street: Socratic Tutor

https://github.com/janestreet/agent_skills/blob/master/socratic-tutor/SKILL.md
217•tosh•2d ago•51 comments

A live tree of systemd jobs on the boot console

https://codeberg.org/wvhulle/bootvine
62•orhunp_•2d ago•10 comments

Tim Peters has died

https://discuss.python.org/t/in-memoriam-tim-peters-1952-2026/110028
1212•ayhanfuat•1d ago•134 comments

93% of paint splatters are valid Perl programs (2019)

https://www.mcmillen.dev/sigbovik/
433•zenincognito•11h ago•57 comments

Legocam: My Lego webcam from 2000, working on a modern Mac

https://blog.benjamin.ie/legocam
15•benkelly•1d ago•7 comments

Critical RCE Vulnerability in Apache HTTP Server

https://www.wiz.io/blog/cve-2026-119618-rce-apache-http-server-vulnerability
207•soheilpro•8h ago•91 comments

AWS emulator

https://github.com/aws/aws-emulator
851•super_linear•16h ago•236 comments

Nvidia is preparing to oust Jensen Huang

https://www.wsj.com/business/nvidia-is-preparing-to-oust-nvidia-ceo-jensen-huang-30f421ad
1029•jbredeche•11h ago•1385 comments

A false smoke alarm almost drowned Jane Street's only NYC datacenter

https://michael.bacarella.com/2026/11/10/false-smoke-alarm-jane-street-datacenter/
495•mbac32768•17h ago•236 comments

Gemini Decisions API

https://blog.google/innovation-and-ai/technology/developers-tools/gemini-decisions-api/
435•iamdelirium•15h ago•131 comments

I'm Working on a FOSS Linux Pinbal Simulation Engine

https://www.getlazarus.org/forums/topic/17/
42•sysrpl•4h ago•14 comments

United Airlines bans AI agents from booking flights on behalf of travelers

https://www.cbsnews.com/news/united-airlines-bans-ai-agents-booking-flights/
557•herpderperator•12h ago•550 comments

Lock Your GitHub Actions

https://hugovk.dev/blog/2026/lock-github-actions/
255•gslin•12h ago•51 comments

I gave an agent a lakehouse and control of my garden

https://jatorre.github.io/garden/
85•jatorre•3d ago•40 comments

Emacs in the Age of Magic

https://commandlinesystems.com/magic.txt
232•ggcr•13h ago•106 comments

Darling Development Update – Q4 2026

https://blog.darlinghq.org/2026/11/08/development-update-q4-2026/
27•tech234a•5h ago•5 comments

The Utah Teapot

https://graphics.cs.utah.edu/teapot/
139•cobbal•14h ago•33 comments

A general purpose Apple Silicon layer for x86-64 PCs

https://github.com/tylertms/Stela
109•iceboundrock•11h ago•43 comments

Hyper-Realistic Sand with WebGL2

https://av.github.io/safe-sand/
379•everlier•20h ago•71 comments

My AI agents found an unmapped Maya site?

https://pietromiotti.com/latest/maya-site
991•eyvindn•22h ago•361 comments

Did Life Begin in an RNA World?

https://www.quantamagazine.org/did-life-begin-in-an-rna-world-20261109/
61•acossta•2d ago•28 comments

The Lost World of Aquaterra

https://www.theatlantic.com/magazine/2026/12/aquaterra-ancient-human-migration/689029/
11•ag8•16h ago•0 comments

Slavdom Unearthed: Marian Wawrzeniecki's Neopagan Paintings (1891–1923)

https://publicdomainreview.org/collection/marian-wawrzeniecki/
30•lermontov•3d ago•8 comments

Lean Grimoire

https://terrytao.wordpress.com/2026/11/11/lean-grimoire/
37•smilelamp•7h ago•6 comments

Faster Retrieval for Better, More Efficient RAG

https://machinelearning.apple.com/research/faster-retrieval
209•zerop•17h ago•38 comments

Show HN: Yogurt – Free, private, open-source alternative to Granola

https://github.com/FrigadeHQ/yogurt
241•brownrout•18h ago•95 comments

Huawei releases MACaQ, its internal quantizer for local inference

https://github.com/huawei-csl/MACaQ
107•thefox96•13h ago•25 comments

Bad ideas that aren't bad anymore

https://devonestes.com/bad-ideas-that-arent-bad-anymore
70•sevenseacat•7h ago•53 comments

Using voltage glitching to unleash the A100 in my mining card

https://blog.kate.land/posts/using-voltage-glitching-to-unlock-the-a100/
305•lae•23h ago•116 comments

Can a Linear Program Do Weight-Space Programming?

https://nathan.rs/posts/weight-space-lp/
281•emschwartz•21h ago•38 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?