frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Feynman Lectures on Physics (1961-1964)

https://www.feynmanlectures.caltech.edu/
155•rramadass•16h ago•46 comments

Exploring a Modern SMTPE 2110 Broadcast Truck

https://www.jeffgeerling.com/blog/2026/exploring-a-modern-smpte-2110-broadcast-truck-with-my-dad/
35•assimpleaspossi•2d ago•3 comments

The Day the Telnet Died

https://www.labs.greynoise.io/grimoire/2026-02-10-telnet-falls-silent/
240•pjf•5h ago•160 comments

The Singularity will occur on a Tuesday

https://campedersen.com/singularity
885•ecto•10h ago•511 comments

Ex-GitHub CEO launches a new developer platform for AI agents

https://entire.io/blog/hello-entire-world/
383•meetpateltech•12h ago•338 comments

End of an era for me: no more self-hosted git

https://www.kraxel.org/blog/2026/01/thank-you-ai/
74•dzulp0d•2h ago•31 comments

Fun With Pinball

https://www.funwithpinball.com/exhibits/small-boards
33•jackwilsdon•3h ago•0 comments

The Little Learner: A Straight Line to Deep Learning (2023)

https://mitpress.mit.edu/9780262546379/the-little-learner/
103•AlexeyBrin•2d ago•15 comments

Willow – Protocols for an uncertain future [video]

https://fosdem.org/2026/schedule/event/CVGZAV-willow/
25•todsacerdoti•2d ago•1 comments

Software design is now cheap

https://dottedmag.net/blog/cheap-design/
7•dottedmag•2d ago•2 comments

Clean-room implementation of Half-Life 2 on the Quake 1 engine

https://code.idtech.space/fn/hl2
348•klaussilveira•16h ago•66 comments

My eighth year as a bootstrapped founder

https://mtlynch.io/bootstrapped-founder-year-8/
165•mtlynch•2d ago•50 comments

Simplifying Vulkan one subsystem at a time

https://www.khronos.org/blog/simplifying-vulkan-one-subsystem-at-a-time
218•amazari•14h ago•146 comments

Mathematicians disagree on the essential structure of the complex numbers (2024)

https://www.infinitelymore.xyz/p/complex-numbers-essential-structure
166•FillMaths•11h ago•214 comments

The Falkirk Wheel

https://www.scottishcanals.co.uk/visit/canals/visit-the-forth-clyde-canal/attractions/the-falkirk...
50•scapecast•7h ago•18 comments

Tambo 1.0: Open-source toolkit for agents that render React components

https://github.com/tambo-ai/tambo
66•grouchy•7h ago•16 comments

Show HN: JavaScript-first, open-source WYSIWYG DOCX editor

https://github.com/eigenpal/docx-js-editor
56•thisisjedr•1d ago•16 comments

How did Windows 95 get permission to put the Weezer video Buddy Holly on the CD?

https://devblogs.microsoft.com/oldnewthing/20260210-00/?p=112052
131•ingve•8h ago•103 comments

Show HN: Rowboat – AI coworker that turns your work into a knowledge graph (OSS)

https://github.com/rowboatlabs/rowboat
129•segmenta•11h ago•31 comments

A brief history of oral peptides

https://seangeiger.substack.com/p/a-brief-history-of-oral-peptides
88•odedfalik•1d ago•33 comments

Google Fulfilled ICE Subpoena Demanding Student Journalist Credit Card Number

https://theintercept.com/2026/02/10/google-ice-subpoena-student-journalist/
720•lehi•10h ago•292 comments

Europe's $24T Breakup with Visa and Mastercard Has Begun

https://europeanbusinessmagazine.com/business/europes-24-trillion-breakup-with-visa-and-mastercar...
723•NewCzech•16h ago•603 comments

Competition is not market validation

https://www.ablg.io/blog/competition-is-not-validation
75•tonioab•11h ago•25 comments

Rivian R2: Electric Mid-Size SUV

https://rivian.com/r2
51•socialcommenter•3h ago•54 comments

Show HN: ArtisanForge: Learn Laravel through a gamified RPG adventure

https://artisanforge.online/
21•grazulex•2d ago•1 comments

Markdown CLI viewer with VI keybindings

https://github.com/taf2/mdvi
59•taf2•10h ago•29 comments

Show HN: I built a macOS tool for network engineers – it's called NetViews

https://www.netviews.app
184•n1sni•22h ago•52 comments

Show HN: Distr 2.0 – A year of learning how to ship to customer environments

https://github.com/distr-sh/distr
70•louis_w_gk•15h ago•18 comments

Show HN: Sol LeWitt-style instruction-based drawings in the browser

https://intervolz.com/sollewitt/
31•intervolz•7h ago•5 comments

Oxide raises $200M Series C

https://oxide.computer/blog/our-200m-series-c
536•igrunert•13h ago•289 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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