frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

California AB 2047 makes 3d printers off-limits to students, educators, business

https://www.the3dprintingnerd.com/ab2047
115•Buildstarted•55m ago•47 comments

United Wizards of the Coast recognized by NLRB

https://unitedwizardsofthecoast.com/news/2026-06-23-we-have-a-union
64•d4mi3n•1h ago•20 comments

Jerry's Map

http://www.jerrysmap.com/the-map
273•turtleyacht•4h ago•36 comments

Don't verify email addresses by sending spam to them

https://milek7.pl/mailverifyspam/
108•garaetjjte•2h ago•29 comments

Swift Package Index joins Apple

https://swiftpackageindex.com/blog/swift-package-index-joins-apple
150•JDevlieghere•5h ago•46 comments

FUTO Swipe – A new swipe typing model

https://swipe.futo.tech/
173•futohq•5h ago•63 comments

Printing Gaussian Splats

https://www.patreon.com/DanyBittel/posts/printing-splats-161333338
114•ilnmtlbnm•2d ago•8 comments

The worthlessness of Vitamin D is mildly exaggerated

https://dynomight.net/vitamin-d/
156•surprisetalk•6h ago•111 comments

Show HN: TikZ Editor – WYSIWYG editor for figures in LaTeX

https://tikz.dev/editor/
296•DominikPeters•8h ago•59 comments

AI's Affordability Crisis

https://blog.dshr.org/2026/06/ais-affordability-crisis.html
219•ilreb•7h ago•280 comments

F3

https://github.com/future-file-format/f3
586•tosh•6h ago•126 comments

Trains halted across Germany because of communication system problem

https://apnews.com/article/germany-trains-halted-communications-radio-problem-deutsche-bahn-e8fd9...
112•sva_•1h ago•115 comments

In memory of the man who put red and green squiggles under words

https://devblogs.microsoft.com/oldnewthing/20260622-00/?p=112451
44•saikatsg•4h ago•1 comments

Unlimited OCR: One-shot long-horizon parsing

https://github.com/baidu/Unlimited-OCR
425•ingve•11h ago•97 comments

The deadly rise of giant trucks and SUVs

https://www.nytimes.com/interactive/2026/06/21/us/trucks-suv-pedestrian-crashes.html
350•xnx•2d ago•573 comments

The Coming Loop

https://lucumr.pocoo.org/2026/6/23/the-coming-loop/
278•ingve•12h ago•213 comments

Five monitors on a Commodore 128 [video]

https://www.youtube.com/watch?v=ul5hC3PY1Yg
96•EvanAnderson•1d ago•18 comments

F* file system – file search that reads SSD directly bypassing OS kernel

https://github.com/dmtrKovalenko/ffs
17•neogoose•2d ago•18 comments

Fired by Google for creating the Google workspace CLI

https://twitter.com/JPoehnelt/status/2069482265953087602
182•justinwp•4h ago•121 comments

Samsung demonstrates 3D stacked FETs with triple nanosheet channels at 42nm

https://semiconductor.samsung.com/news-events/tech-blog/from-gaa-to-3d-stacked-fet-expanding-the-...
82•its_ajseven•4d ago•24 comments

Lift4D: Harmonizing Single-View 3D Estimation for 4D Reconstruction In-the-Wild

https://lift4d.github.io/
102•ilreb•8h ago•11 comments

Algorithmic Monocultures in Hiring

https://hai.stanford.edu/news/ai-hiring-tools-can-yield-racial-bias-and-systemic-rejection
121•sizzle•4h ago•122 comments

San Diego photologs from the 1970s

https://www.beautifulpublicdata.com/san-diego-photologs-from-the-1970s/
136•jonathanmkeegan•6h ago•46 comments

ATProto Permissioned Data Proposal Draft

https://github.com/bluesky-social/proposals/pull/94
12•danabramov•1h ago•2 comments

Plotnine

https://plotnine.org/
247•tosh•4d ago•74 comments

On the Skin-Furrows of the Hand (1880) [pdf]

https://galton.org/fingerprints/faulds-1880-nature-furrows.pdf
4•pncnmnp•1d ago•2 comments

Claude Tag

https://www.anthropic.com/news/introducing-claude-tag
222•adocomplete•5h ago•142 comments

Digital euro clears key hurdle as EU seeks to break free from U.S. credit cards

https://finance.yahoo.com/markets/currencies/articles/ecb-secures-key-parliamentary-backing-10271...
155•madars•6h ago•236 comments

Mistral OCR 4

https://mistral.ai/news/ocr-4/
418•meetpateltech•9h ago•109 comments

Performance Improvements in Libffi

https://atgreen.github.io/repl-yell/posts/libffi-plan-cache/
36•atgreen•2d ago•6 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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