frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The UK's War on Anonymity Has Come to America

https://www.effort.news/uk-lobby
55•slowin•1h ago•10 comments

Show HN: Needle2: 14MB agentic LLM for phones, wearables, smart home and robots

https://cactuscompute.com/needle
146•HenryNdubuaku•7h ago•69 comments

Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

https://research.meta.ai/blog/introducing-muse-glimmer-open-agentic-model
1021•riordan•14h ago•570 comments

Show HN: Scroll through all 43252003274489856000 Rubik's Cube states

https://everycube.alen.is/
26•Alen123•1h ago•3 comments

Mark Zuckerberg attacks 'closed' AI rivals as Meta returns to open models

https://www.ft.com/content/4e3957f8-ea7c-4c46-a3de-cdce8e526878
350•root-parent•10h ago•367 comments

The "mechanical miracle" that ruined Mark Twain's life

https://resobscura.substack.com/p/the-mechanical-miracle-that-ruined
19•benbreen•5d ago•4 comments

Publishing Schematics Before “Open Source” Was a Word

https://fabscene.medium.com/publishing-schematics-before-open-source-was-a-word-55-years-of-akizu...
59•extralongdivisi•3d ago•14 comments

Sonic Pi v5

https://www.patreon.com/samaaron/posts/sonic-pi-v5-166001392
301•samaaron•3d ago•76 comments

Rust SIMD on the GPU

https://www.vectorware.com/blog/simd-on-gpu/
117•sagacity•6h ago•58 comments

Confessions of a Long-Distance Sailor

https://arachnoid.com/lutusp/sailbook.html
54•AntiRush•3h ago•10 comments

World Train Map – 1247 train routes around the world

https://worldtrainmap.com/
19•Flightmussy•2h ago•3 comments

Stop Killing Games: It's time to sue Sony, join us

https://www.massaschadeconsument.nl/collectieve-acties/playstation/
145•EDM115•4h ago•58 comments

Stowaway – take the window seat on any plane or satellite overhead

https://stowaway.live/
93•thunderbong•3d ago•11 comments

Exploiting System Management Mode with a very long interrupt

https://github.com/xoreaxeaxeax/smiiiiiiiiiiiiiiii
121•WhiteDawn•8h ago•40 comments

Squeak 6.1

https://squeak.org/release_notes/6.1/
219•fniephaus•12h ago•113 comments

Humanising LLM Outputs Is Dumb

https://kuber.studio/blog/Reflections/Humanising-LLM-Outputs-is-Actually-Dumb
148•kuberwastaken•11h ago•87 comments

Launch HN: Stoa Markets (YC S26) – A Marketplace for GPUs and AI Servers

https://www.stoaexchange.com
63•erenberke•8h ago•39 comments

What's the best programming language for coding agents?

http://danluu.com/pl-tokens/
45•chaychoong•8h ago•24 comments

The Psychedelic Toad of the Sonoran Desert

https://en.wikipedia.org/wiki/Bufo_Alvarius:_the_Psychedelic_Toad_of_the_Sonoran_Desert
75•simonebrunozzi•6d ago•52 comments

Ask HN: In your experience, what are sound conventions for e-ink UI development?

139•BoxOfRain•3d ago•50 comments

Parametron: 50s Japanese computer that uses neither transistors nor vacuum tubes

https://ethw.org/Milestones:Parametron,_1954
182•xeonmc•14h ago•46 comments

Letter to Governor Abbott on responsible AI infrastructure in Texas

https://openai.com/index/responsible-ai-infrastructure-texas/
86•hackerBanana•10h ago•165 comments

Exploring Claude/GPT Knowledge Cutoffs and Pre-Training Timelines

https://blog.sshh.io/p/exploring-claudegpt-knowledge-cutoffs
94•sshh12•10h ago•14 comments

Magnitude 7.4 Earthquake – 5 km S of San José del Palmar, Colombia

https://earthquake.usgs.gov/earthquakes/eventpage/us6000tjl2/executive
160•Bender•9h ago•62 comments

Tail-call optimization in C is relatively recent (2025)

https://lwn.net/Articles/1034703/
119•prakashqwerty•13h ago•115 comments

Google Search Is Dying. What Comes Next Is Worse

https://thewalrus.ca/google-search-is-dying/
77•awnird•2h ago•69 comments

50k Boat Names

https://www.beautifulpublicdata.com/boat-names/
152•jonathanmkeegan•11h ago•103 comments

Extreme 220GHz+Broadband Silicon Capacitor X2SC 0201M 22nF BV11

https://pim.murata.com/asset/pim4/siliconCapacitor/SICAP_X2SC422522_PDF_SILICONCAPACITOR
60•peter_d_sherman•8h ago•25 comments

Mistral Patent for “Code implemented tool calls”

https://patentsgazette.uspto.gov/week26/OG/html/1547-5/US12670045-20260630.html
207•theanonymousone•11h ago•172 comments

Tl;dv: Over 180k meetings left wide open

https://bobdahacker.com/blog/tldv-hack
527•colesantiago•12h ago•173 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?