frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

A Note from LWN

https://lwn.net/Articles/1090585/
395•rwky•2h ago•77 comments

Gemini 3.8 Flash

https://deepmind.google/models/model-cards/gemini-3-8-flash/
65•bratao•34m ago•32 comments

Biggest dark matter detector spots a single weird particle

https://www.science.org/content/article/world-s-biggest-dark-matter-detector-spots-single-weird-p...
87•randycupertino•2h ago•10 comments

GrapheneOS says Pixel 11 has MTE support after all

https://grapheneos.social/@GrapheneOS/117194007157499435
72•user_7832•1h ago•50 comments

Mistral now trains on user input by default, except on enterprise tier

https://help.mistral.ai/en/articles/455207-can-i-opt-out-of-my-input-or-output-data-being-used-fo...
138•teekert•3h ago•69 comments

Three sites made 215,128 “best software” pages for AI. Perplexity cites them

https://trellner.com/reports/manufactured-sources-behind-ai-recommendations/
113•jakobgreenfeld•1h ago•62 comments

Poisson Disk Sampling

https://stripeacross.com/posts/poisson-disk-sampling/
48•vismit2000•1h ago•5 comments

Exit the Cave

https://turtlespace.blog/p/exit-the-cave
37•akkartik•1h ago•7 comments

Commodore 64 released September 1, 1982

https://dfarq.homeip.net/commodore-64-released-september-1-1982/
228•giuliomagnifico•7h ago•116 comments

WebLLM: high-performance in-browser LLM inference engine

https://github.com/mlc-ai/web-llm
17•saikatsg•1h ago•7 comments

Aging Brains Blend Memories Together Instead of Just Forgetting Them

https://studyfinds.com/aging-brains-blend-memories-together-instead-of-forgetting-them-study-finds/
59•mdp2021•2h ago•20 comments

A Selection of Los Alamos Rolodex Business Cards

https://clui.org/collections/los-alamos-business-cards/selection-cards
24•1970-01-01•1d ago•4 comments

Six curl CVEs after OpenAI and Anthropic came back with zero

https://aisle.com/blog/aisle-discovered-six-curl-cves-after-openai-and-anthropic-found-zero
72•goobreee•2h ago•23 comments

Check if a file was made with Claude

https://claude.com/check-content
58•frexs•3h ago•37 comments

LLMs: Intelligence vs. Cost

https://openteams.com/intelligence-vs-cost/
34•theanonymousone•2h ago•16 comments

Dutch central bank moves share of gold from U.S., Canada to London

https://nltimes.nl/2026/09/02/dutch-central-bank-moves-share-gold-us-canada-london-cites-instability
144•TechTechTech•2h ago•119 comments

A third of Perplexity's citations don't contain the number they're cited for

https://hausresearch.com/reports/perplexity-citation-audit/
29•jakobgreenfeld•1h ago•4 comments

Ending my elixir exploratory writing

https://lucassifoni.info/blog/the-end-of-this-elixir-log/
52•ffin•3h ago•30 comments

The Emergent Symbolic Structure of Artificial Neural Networks

https://arxiv.org/abs/2608.29530
233•schmuhblaster•11h ago•80 comments

Telli (YC F24) is hiring engineers and designers [Berlin, on-site]

https://careers.telli.com/
1•sebselassie•7h ago

Using jq to format JSON on the clipboard

https://chris48s.github.io/blogmarks/posts/2021/jsontidy/
34•stefanvdw1•3h ago•8 comments

9000 RPM is faster than your screen refreshes

https://ma.ttias.be/9000-rpm/
26•Mojah•3h ago•12 comments

Move in C++ without a std:move

https://andreasfertig.com/blog/2026/09/move-in-cpp-without-a-stdmove/
30•dalvrosa•1d ago•35 comments

Banca Etica Suspends A/I's Account While Condemning the Sanctions Behind It

https://sabot.media/post/banca-etica-statement-english
47•rendx•5h ago•27 comments

It's OK to hardcode feature flags (2025)

https://code.mendhak.com/hardcode-feature-flags/
57•biscuits1•4h ago•31 comments

The Cables That Connect the World

https://xn--gckvb8fzb.com/the-cables-that-connect-the-world/
28•surprisetalk•2h ago•5 comments

Why humanoid robots won't catch up to human workers any time soon

https://www.understandingai.org/p/why-humanoid-robots-wont-catch-up
21•speckx•2h ago•31 comments

Quasar 438B: Europe's Leading AI Model

https://multiversecomputing.com/resources/introducing-quasar-438b-europe-s-leading-ai-model
104•amunozo•5h ago•85 comments

Fine, I'll build my own text editor

https://dbushell.com/2026/09/01/text-editor/
209•Alephinitesimal•22h ago•200 comments

A Beginner's Deep Dive Guide to Entra Passkeys

https://emsroute.com/2026/03/19/passkeys-beginners-101/
19•speckx•2h ago•15 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?