frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

God Sleeps in the Minerals

https://wchambliss.wordpress.com/2026/03/03/god-sleeps-in-the-minerals/
285•speckx•4h ago•70 comments

Want to Write a Compiler? Just Read These Two Papers (2008)

https://prog21.dadgum.com/30.html
357•downbad_•8h ago•108 comments

Open Source Isn't Dead. Cal.com Just Learned the Wrong Lesson

https://www.strix.ai/blog/cal-com-is-closing-its-code-due-to-ai-threats
140•bearsyankees•2h ago•92 comments

Show HN: Libretto – Making AI browser automations deterministic

https://github.com/saffron-health/libretto
19•muchael•1h ago•3 comments

Good Sleep, Good Learning (2012)

https://super-memory.com/articles/sleep.htm
270•downbad_•8h ago•122 comments

The Future of Everything Is Lies, I Guess: New Jobs

https://aphyr.com/posts/419-the-future-of-everything-is-lies-i-guess-new-jobs
174•aphyr•4h ago•108 comments

Adaptional (YC S25) Is Hiring Founding AI Engineers

https://www.ycombinator.com/companies/adaptional/jobs/k7W6ge9-founding-engineer
1•acesohc•43m ago

Do you even need a database?

https://www.dbpro.app/blog/do-you-even-need-a-database
81•upmostly•5h ago•149 comments

Forcing an inversion of control on the SaaS stack

https://www.100x.bot/a/client-side-injection-inversion-of-control-saas
26•shardullavekar•5d ago•24 comments

How do Wake-On-LAN works

https://blog.xaner.dev/post/wake-on-lan/
25•swq115•4d ago•9 comments

Gemini Robotics-ER 1.6

https://deepmind.google/blog/gemini-robotics-er-1-6/
139•markerbrod•3h ago•40 comments

Fix monitor that goes black, off or blinks due to static electricity in chair

https://aalonso.dev/blog/2023/how-to-fix-monitor-that-goes-black-off-due-to-static-electricity-in...
8•cyclopeanutopia•3d ago•5 comments

Costasiella kuroshimae – Solar Powered animals, that do indirect photosynthesis

https://en.wikipedia.org/wiki/Costasiella_kuroshimae
113•vinnyglennon•3d ago•47 comments

Anna's Archive loses $322M Spotify piracy case without a fight

https://torrentfreak.com/annas-archive-loses-322-million-spotify-piracy-case-without-a-fight/
136•askl•9h ago•145 comments

Wacli – WhatsApp CLI

https://github.com/steipete/wacli
201•dinakars777•10h ago•134 comments

Fixing a 20-year-old bug in Enlightenment E16

https://iczelia.net/posts/e16-20-year-old-bug/
230•snoofydude•12h ago•129 comments

We ran Doom on a 40 year old printer controller (Agfa Compugraphic 9000PS) [video]

https://www.youtube.com/watch?v=cltnlks2-uU
40•zdw•3d ago•12 comments

Metro stop is Ancient Rome's new attraction

https://www.bbc.com/travel/article/20260408-a-150-metro-ticket-to-ancient-rome
83•Stevvo•5d ago•20 comments

Google Gemma 4 Runs Natively on iPhone with Full Offline AI Inference

https://www.gizmoweek.com/gemma-4-runs-iphone/
219•takumi123•12h ago•146 comments

Pretty Fish: A better mermaid diagram editor

https://pretty.fish/
84•pastelsky•5d ago•18 comments

Show HN: Every CEO and CFO change at US public companies, live from SEC

https://tracksuccession.com/explore
137•porsche959•4h ago•58 comments

Study: Back-to-basics approach can match or outperform AI in language analysis

https://www.manchester.ac.uk/about/news/back-to-basics-approach-can-match-or-outperform-ai/
24•giuliomagnifico•5h ago•9 comments

The tiniest e-reader in the world, and you can build one yourself

https://www.androidauthority.com/tiny-e-reader-diy-3657661/
14•Brajeshwar•51m ago•2 comments

AI ruling prompts warnings from US lawyers: Your chats could be used against you

https://www.reuters.com/legal/government/ai-ruling-prompts-warnings-us-lawyers-your-chats-could-b...
102•alephnerd•4h ago•55 comments

Elevated errors on Claude.ai, API, Claude Code

https://claudestatus.com/
211•redm•3h ago•191 comments

Dependency cooldowns turn you into a free-rider

https://calpaterson.com/deps.html
175•pabs3•15h ago•111 comments

CRISPR takes a bold leap toward silencing Down syndrome's extra chromosome

https://medicalxpress.com/news/2026-04-crispr-bold-silencing-syndrome-extra.html
13•amichail•1h ago•9 comments

MIT Radiation Laboratory

https://www.ll.mit.edu/about/history/mit-radiation-laboratory
38•stmw•3d ago•8 comments

New Modern Greek

https://redas.dev/NewModernGreek/
10•holoflash•2d ago•17 comments

Not all elementary functions can be expressed with exp-minus-log

https://www.stylewarning.com/posts/not-all-elementary/
125•mmastrac•15h ago•105 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?