frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Granite 4.1: IBM's 8B Model Matching 32B MoE

https://firethering.com/granite-4-1-ibm-open-source-model-family/
125•steveharing1•2h ago•64 comments

Belgium stops decommissioning nuclear power plants

https://dpa-international.com/general-news/urn:newsml:dpa.com:20090101:260430-930-14717/
10•mpweiher•27m ago•1 comments

Mozilla's Opposition to Chrome's Prompt API

https://github.com/mozilla/standards-positions/issues/1213
212•jaffathecake•5h ago•90 comments

Where the goblins came from

https://openai.com/index/where-the-goblins-came-from/
764•ilreb•9h ago•456 comments

Noctua releases official 3D CAD models for its cooling fans

https://www.noctua.at/en/3d-cad-models
328•embedding-shape•2d ago•76 comments

Zed 1.0

https://zed.dev/blog/zed-1-0
1940•salkahfi•22h ago•612 comments

The Zig project's rationale for their anti-AI contribution policy

https://simonwillison.net/2026/Apr/30/zig-anti-ai/
388•lumpa•10h ago•197 comments

Copy Fail

https://copy.fail/
1109•unsnap_biceps•18h ago•398 comments

GCC 16 has been released

https://gcc.gnu.org/gcc-16/changes.html
48•HeliumHydride•1h ago•1 comments

A Primer on Bézier Curves – So What Makes a Bézier Curve?

https://pomax.github.io/bezierinfo/
23•mostlyk•1d ago•8 comments

Craig Venter has died

https://www.jcvi.org/media-center/j-craig-venter-genomics-pioneer-and-founder-jcvi-and-diploid-ge...
257•rdl•10h ago•50 comments

How to Disable Firefox's New Emoji Picker

https://emsh.cat/en/how-to-disable-firefoxs-emoji-picker/
12•embedding-shape•1h ago•26 comments

"Parse, don't validate" through the years with C++

https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
42•dwrodri•2d ago•11 comments

I aggregated 28 US Government auction sites into one search

https://bidprowl.com
4•scarsam•19m ago•0 comments

Cursor Camp

https://neal.fun/cursor-camp/
1024•bpierre•21h ago•166 comments

Alignment whack-a-mole: Finetuning activates recall of copyrighted books in LLMs

https://github.com/cauchy221/Alignment-Whack-a-Mole-Code
161•reconnecting•9h ago•125 comments

DataCenter.FM – background noise app featuring the sound of the AI bubble

https://datacenter.fm/
47•louisbarclay•4h ago•8 comments

Biology is a Burrito: A text- and visual-based journey through a living cell

https://burrito.bio/essays/biology-is-a-burrito
134•the-mitr•9h ago•19 comments

London to Calcutta by Bus (2022)

https://www.amusingplanet.com/2022/08/london-to-calcutta-by-bus.html
82•CGMthrowaway•1d ago•26 comments

FastCGI: 30 years old and still the better protocol for reverse proxies

https://www.agwa.name/blog/post/fastcgi_is_the_better_protocol_for_reverse_proxies
363•agwa•20h ago•87 comments

OpenTrafficMap

https://opentrafficmap.org/
299•moooo99•16h ago•79 comments

For the first time in history, more Americans are moving to EU than vice versa

https://twitter.com/benbawan/status/2049303326999609846
14•akyuu•1h ago•0 comments

Mike: open-source legal AI

https://mikeoss.com/
126•noleary•11h ago•46 comments

Monad Tutorials Timeline

https://wiki.haskell.org/Monad_tutorials_timeline
51•brudgers•8h ago•21 comments

Laws of UX

https://lawsofux.com/
297•bobbiechen•19h ago•49 comments

An open-source stethoscope that costs between $2.5 and $5 to produce

https://github.com/GliaX/Stethoscope
271•0x54MUR41•21h ago•118 comments

HERMES.md in commit messages causes requests to route to extra usage billing

https://github.com/anthropics/claude-code/issues/53262
1169•homebrewer•17h ago•496 comments

1.4 GW: battery storage at former Grohnde nuclear power plant

https://www.heise.de/en/news/1-4-GW-Huge-battery-storage-at-former-Grohnde-nuclear-power-plant-11...
18•pantalaimon•1h ago•5 comments

Why I still reach for Lisp and Scheme instead of Haskell

https://jointhefreeworld.org/blog/articles/lisps/why-i-still-reach-for-scheme-instead-of-haskell/...
242•jjba23•1d ago•130 comments

Joby kicks off NYC electric air taxi demos with historic JFK flight

https://www.flyingmag.com/joby-nyc-electric-air-taxi-jfk-airport/
63•Jblx2•11h ago•159 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•11mo ago

Comments

balloob•11mo 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•11mo ago
Discussion for the other article in the series:

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

tomhow•11mo ago
Comments moved thither. Thanks!
pabs3•11mo ago
They are two different articles, I don't think that was correct.
tomhow•11mo 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•11mo ago
Thanks for the response, guess that makes sense.
pabs3•11mo 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?