frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Bambu Lab is abusing the open source social contract

https://www.jeffgeerling.com/blog/2026/bambu-lab-abusing-open-source-social-contract/
352•rubenbe•1h ago•119 comments

Rendering the Sky, Sunsets, and Planets

https://blog.maximeheckel.com/posts/on-rendering-the-sky-sunsets-and-planets/
188•ibobev•2h ago•15 comments

Operation: Epic Furious

https://www.epicfurious.com/
54•dmschulman•1h ago•7 comments

Learning Software Architecture

https://matklad.github.io/2026/05/12/software-architecture.html
381•surprisetalk•6h ago•71 comments

Screenshots of Old Desktop OSes

http://www.typewritten.org/Media/
512•adunk•11h ago•241 comments

The Future of Obsidian Plugins

https://obsidian.md/blog/future-of-plugins/
13•xz18r•36m ago•1 comments

Launch HN: Voker (YC S24) – Analytics for AI Agents

https://voker.ai
4•ttpost•36m ago•1 comments

eBay Rejects GameStop's $56B Takeover as Not Credible

https://www.bloomberg.com/news/articles/2026-05-12/ebay-rejects-gamestop-s-56-billion-takeover-as...
33•voisin•32m ago•10 comments

Postmortem: TanStack NPM supply-chain compromise

https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
981•varunsharma07•19h ago•414 comments

Profiling.sampling – Statistical Profiler

https://docs.python.org/3.15/library/profiling.sampling.html#module-profiling.sampling
59•djoldman•2d ago•15 comments

EU to crack down on TikTok, Instagram's 'addictive design' targeting kids

https://www.cnbc.com/2026/05/12/tiktok-instagram-social-media-addictive-eu-crack-down.html
360•thm•5h ago•300 comments

They Live (1988) inspired Adblocker

https://github.com/davmlaw/they_live_adblocker
466•tokenburner•15h ago•149 comments

Chasing Chicago's movable bridges (2014)

https://aresluna.org/seesaws-for-giants/
53•NaOH•2d ago•7 comments

If AI writes your code, why use Python?

https://medium.com/@NMitchem/if-ai-writes-your-code-why-use-python-bf8c4ba1a055
736•indigodaddy•19h ago•766 comments

Text Blaze (YC W21) Is Hiring for a No-AI Summer Internship

https://www.ycombinator.com/companies/text-blaze/jobs/P4CCN62-the-blaze-no-ai-summer-internship
1•scottfr•4h ago

Through the looking glass of benchmark hacking

https://poolside.ai/blog/through-the-looking-glass
15•jxmorris12•18h ago•4 comments

The Surprisingly Long Life of the Vacuum Tube

https://www.construction-physics.com/p/the-surprisingly-long-life-of-the
23•surprisetalk•1d ago•9 comments

UCLA discovers first stroke rehabilitation drug to repair brain damage (2025)

https://stemcell.ucla.edu/news/ucla-discovers-first-stroke-rehabilitation-drug-repair-brain-damage
408•bookofjoe•22h ago•80 comments

Analysis points to a unexpected cause of reading difficulties

https://phys.org/news/2026-05-years-struggles-obvious-massive-analysis.html
12•wglb•2d ago•17 comments

Extremely Low Frequencies

https://computer.rip/2026-05-09-extremely-low-frequencies.html
160•pinewurst•12h ago•14 comments

Coursera and Udemy are now one company

https://blog.coursera.org/coursera-and-udemy-are-now-one-company-creating-the-worlds-most-compreh...
139•Anon84•5h ago•60 comments

UnDUNE II

https://liquidream.itch.io/undune2
94•tosh•3h ago•21 comments

Claude Platform on AWS

https://claude.com/blog/claude-platform-on-aws
203•matrixhelix•14h ago•86 comments

I let AI build a tool to help me figure out what was waking me up at night

https://martin.sh/i-let-ai-build-a-tool-to-help-me-figure-out-what-was-waking-me-up-at-night/
250•showmypost•19h ago•254 comments

Software Internals Book Club

https://eatonphil.com/bookclub.html
158•aragonite•13h ago•27 comments

I hate soldering

https://user8.bearblog.dev/rant/
205•James72689•4d ago•165 comments

Google says criminal hackers used AI to find a major software flaw

https://www.nytimes.com/2026/05/11/us/politics/google-hackers-attack-ai.html
223•donohoe•1d ago•165 comments

Rtwatch: Watch videos with friends using WebRTC

https://github.com/pion/rtwatch
70•nateb2022•3d ago•13 comments

Remembering Planet Source Code: Sharing Code Before GitHub Made It Easy

https://www.pietschsoft.com/post/2026/05/05/remembering-planet-source-code-sharing-code-before-gi...
44•pabs3•3d ago•9 comments

Nullsoft, 1997-2004 (2004)

https://slate.com/technology/2004/11/the-death-of-the-last-maverick-tech-company.html
310•downbad_•4d ago•88 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

tomhow•12mo 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?