frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.6 27B is the sweet spot for local development

https://quesma.com/blog/qwen-36-is-awesome/
872•stared•14h ago•596 comments

Open Source Low Tech

https://opensourcelowtech.org/
60•grep_it•4d ago•10 comments

.self: A new top-level domain designed to support self-hosting

https://hccf.onmy.cloud/2026/06/21/reclaiming-our-digital-selves-hccfs-vision-for-a-human-centere...
475•HumanCCF•12h ago•270 comments

Free the Icons

https://weblog.rogueamoeba.com/2026/06/26/free-the-icons/
408•zdw•2d ago•111 comments

LongCat-2.0, a large-scale MoE model with 1.6T total and 48B Active

https://longcat.chat/blog/longcat-2.0/
116•benjiro29•7h ago•34 comments

Memory Safe Context Switching

https://fil-c.org/context_switches
106•modeless•7h ago•23 comments

Old Computer Challenge

http://occ.sdf.org/
54•wrxd•2d ago•15 comments

The end of the AArch64 desktop experiment

https://marcin.juszkiewicz.com.pl/2026/06/26/the-end-of-the-aarch64-desktop-experiment/
25•signa11•3h ago•5 comments

Exploring PDP-1 Lisp (1960)

https://obsolescence.dev/pdp1-lisp-introduction.html
57•ozymandiax•6h ago•16 comments

Rocketlab acquires Iridium

https://investors.rocketlabcorp.com/news-releases/news-release-details/rocket-lab-acquire-iridium...
400•everfrustrated•17h ago•262 comments

Linux for the Sega MegaDrive

https://github.com/LinuxMD/linuxmd
84•HardwareLust•16h ago•11 comments

Popping the GPU Bubble

https://moondream.ai/blog/popping-the-gpu-bubble
99•radq•2h ago•18 comments

Ornith-1.0: self-improving open-source models for agentic coding

https://github.com/deepreinforce-ai/Ornith-1
200•danboarder•14h ago•39 comments

US Supreme Court Just Blew Up EU-US Data Transfers

https://noyb.eu/en/us-supreme-court-just-blew-eu-us-data-transfers
77•tomwas54•2h ago•30 comments

US Supreme Court rules geofence warrants require constitutional protections

https://www.theguardian.com/us-news/2026/jun/29/supreme-court-geofence-warrants-case-decision
513•cdrnsf•16h ago•243 comments

One million passports leaked online

https://www.theverge.com/tech/947157/passports-data-breach-cannabis-club-systems-nefos-puffpal
245•jruohonen•1d ago•132 comments

How to corrupt an SQLite database file

https://www.sqlite.org/howtocorrupt.html
64•tosh•3d ago•14 comments

Alan Kay on the meaning of "object-oriented programming" (2003)

https://notes.shixiangxi.com/en/docs/appendix/alan-kay-on-oop/
56•sxx0•2d ago•16 comments

Zig – SPIR-V Backend Progress

https://ziglang.org/devlog/2026/#2026-06-26
55•Retro_Dev•4d ago•17 comments

British Origami: the 1955 exhibition by Akira Yoshizawa (2005)

https://www.britishorigami.org/cp-lister-list/the-1955-exhibition-by-akira-yoshizawa/
30•dang•1d ago•3 comments

Apple Neural Engine: Architecture, Programming, and Performance

https://arxiv.org/abs/2606.22283
157•Jimmc414•2d ago•22 comments

A native graphical shell for SSH

https://probablymarcus.com/blocks/2026/06/28/native-graphical-shell-for-SSH.html
291•mrcslws•16h ago•157 comments

Dark Sky Lighting

https://www.savingourstars.org/darkskylighting#whatisdarkskylighting
198•alexandrehtrb•4d ago•33 comments

WATaBoy: JIT-Ing Game Boy Instructions to WASM Beats a Native Interpreter

https://humphri.es/blog/WATaBoy/
202•energeticbark•16h ago•33 comments

Kb – Prolog Knowledge Base

https://github.com/mat-mgm/kb-prolog
68•triska•2d ago•7 comments

What happens when you run a CUDA kernel?

https://fergusfinn.com/blog/what-happens-when-you-run-a-gpu-kernel/
252•mezark•18h ago•30 comments

South Korea to spend $1T on more memory chip production and humanoid robots

https://arstechnica.com/ai/2026/06/south-korea-to-spend-1t-on-more-memory-chip-production-and-hum...
211•jnord•9h ago•134 comments

Working With AI: A concrete example

https://htmx.org/essays/working-with-ai/
152•comma_at•17h ago•49 comments

30-year sentence for transporting zines is a five-alarm fire for free speech

https://theintercept.com/2026/06/26/daniel-sanchez-estrada-zines-prairieland-free-speech/
529•xrd•1d ago•327 comments

Wallace the 6 inch f/2.8 telescope, building it, and hiking with it

https://lucassifoni.info/blog/hiking-with-wallace/
133•chantepierre•4d ago•23 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?