frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Alberta startup sells no-tech tractors for half price

https://wheelfront.com/this-alberta-startup-sells-no-tech-tractors-for-half-price/
1346•Kaibeezy•9h ago•473 comments

Apple fixes bug that cops used to extract deleted chat messages from iPhones

https://techcrunch.com/2026/04/22/apple-fixes-bug-that-cops-used-to-extract-deleted-chat-messages...
376•cdrnsf•5h ago•97 comments

We found a stable Firefox identifier linking all your private Tor identities

https://fingerprint.com/blog/firefox-tor-indexeddb-privacy-vulnerability/
453•danpinto•8h ago•129 comments

Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model

https://qwen.ai/blog?id=qwen3.6-27b
708•mfiguiere•13h ago•344 comments

5x5 Pixel font for tiny screens

https://maurycyz.com/projects/mcufont/
438•zdw•3d ago•106 comments

Over-editing refers to a model modifying code beyond what is necessary

https://nrehiew.github.io/blog/minimal_editing/
296•pella•8h ago•172 comments

Tempest vs. Tempest: The Making and Remaking of Atari's Iconic Video Game

https://tempest.homemade.systems
11•mwenge•1h ago•1 comments

Website streamed live directly from a model

https://flipbook.page/
158•sethbannon•8h ago•57 comments

Approximating Hyperbolic Tangent

https://jtomschroeder.com/blog/approximating-tanh/
25•jtomschroeder•2h ago•4 comments

Technical, cognitive, and intent debt

https://martinfowler.com/fragments/2026-04-02.html
200•theorchid•10h ago•47 comments

Ping-pong robot beats top-level human players

https://www.reuters.com/sports/ping-pong-robot-ace-makes-history-by-beating-top-level-human-playe...
72•wslh•11h ago•84 comments

Our eighth generation TPUs: two chips for the agentic era

https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/eighth-generation-tpu...
403•xnx•14h ago•197 comments

3.4M Solar Panels

https://tech.marksblogg.com/american-solar-farms-v2.html
291•marklit•14h ago•225 comments

The handmade beauty of Machine Age data visualizations

https://resobscura.substack.com/p/the-handmade-beauty-of-machine-age
9•benbreen•12h ago•1 comments

Verus is a tool for verifying the correctness of code written in Rust

https://verus-lang.github.io/verus/guide/
8•fanf2•2d ago•0 comments

Scoring Show HN submissions for AI design patterns

https://www.adriankrebs.ch/blog/design-slop/
276•hubraumhugo•11h ago•202 comments

Parallel agents in Zed

https://zed.dev/blog/parallel-agents
166•ajeetdsouza•8h ago•101 comments

The Illuminated Man: an unconventional portrait of JG Ballard

https://www.theguardian.com/books/2026/apr/20/the-illuminated-man-by-christopher-priest-and-nina-...
49•agronaut•5h ago•16 comments

Effectful Recursion Schemes

https://effekt-lang.org/blog/recursion-schemes/
14•marvinborner•2d ago•1 comments

Another Day Has Come

https://daringfireball.net/2026/04/another_day_has_come
194•ndr42•1d ago•143 comments

Ultraviolet corona discharges on treetops during storms

https://www.psu.edu/news/earth-and-mineral-sciences/story/treetops-glowing-during-storms-captured...
202•t-3•12h ago•55 comments

Bring your own Agent to MS Teams

https://microsoft.github.io/teams-sdk/blog/bring-your-agent-to-teams/
18•umangsehgal93•3h ago•7 comments

The Neon King of New Orleans

https://gardenandgun.com/new-orleans-neon-king
35•renameme•4h ago•4 comments

Bodega cats of New York

https://bodegacatsofnewyork.com
158•zdw•4d ago•58 comments

What killed the Florida orange?

https://slate.com/business/2026/04/florida-state-orange-food-houses-real-estate.html
117•danso•2d ago•106 comments

OpenAI's response to the Axios developer tool compromise

https://openai.com/index/axios-developer-tool-compromise/
6•shpat•1h ago•0 comments

Workspace Agents in ChatGPT

https://openai.com/index/introducing-workspace-agents-in-chatgpt/
104•mfiguiere•8h ago•39 comments

GitHub CLI now collects pseudoanonymous telemetry

https://cli.github.com/telemetry
413•ingve•14h ago•301 comments

The great Scouse pasty war

https://www.livpost.co.uk/the-great-scouse-pasty-war/
44•DamonHD•2d ago•10 comments

New study compares growing corn for energy to solar production

https://www.anthropocenemagazine.org/2025/04/new-study-compares-growing-corn-for-energy-to-solar-...
68•dotcoma•6h ago•104 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?