frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.8 Max Preview

https://www.qwencloud.com/pricing/token-plan
156•lebovic•4h ago•85 comments

What I learned selling 2,500 MIDI recorders: Hardware is not so hard

https://chipweinberger.com/articles/20260719-hardware-is-not-so-hard
95•chipweinberger•2h ago•48 comments

Minecraft: Java Edition now uses SDL3

https://www.minecraft.net/en-us/article/minecraft-26-3-snapshot-4
27•ObviouslyFlamer•1h ago•5 comments

Blender 5.2 LTS

https://www.blender.org/download/releases/5-2/
108•makizar•4d ago•43 comments

I burned all my tokens researching how to save tokens

https://quesma.com/blog/custom-deep-research-pipeline/
27•bkotrys•1h ago•5 comments

Transcribe.cpp

https://workshop.cjpais.com/projects/transcribe-cpp
595•sebjones•12h ago•126 comments

The death and rebirth of my home server

https://sgt.hootr.club/blog/home-server-rebirth/
30•steinuil•2h ago•11 comments

OpenAI reduces Codex Model Context Size from 372k to 272k

https://github.com/openai/codex/pull/33972/files
74•AmazingTurtle•5h ago•32 comments

Qwen3.8 is launching and going open-weight soon

https://twitter.com/Alibaba_Qwen/status/2078759124914098291
287•nh43215rgb•4h ago•150 comments

Show HN: LoopGain – Stop agent loops with control theory, not max_iterations

https://github.com/loopgain-ai/loopgain
14•fitz2882•4d ago•8 comments

Speech Recognition and TTS in less than 500kb

https://github.com/moonshine-ai/moonshine/tree/main/micro
481•petewarden•4d ago•67 comments

The Mighty Big Array of Finn Jensen LA8YB

https://la0by.darc.de/LA8YB_EME_MBA.htm
19•kalehmann•5h ago•4 comments

The Kimi K3 Moment

https://stephen.bochinski.dev/blog/2026/07/18/the-kimi-k3-moment/
485•sbochins•19h ago•491 comments

I joined the IndieWeb, here's what I learned

https://en.andros.dev/blog/0b8e451e/i-joined-the-indieweb-heres-what-i-learned/
10•andros•2h ago•5 comments

Codex Resets

https://codex-resets.com/
222•denysvitali•14h ago•150 comments

Better and Cheaper Than IPTV

https://github.com/stupside/castor
242•xonery•12h ago•68 comments

Mathematicians still don't know the fastest way to multiply numbers

https://www.scientificamerican.com/article/mathematicians-still-dont-know-the-fastest-way-to-mult...
141•beardyw•5d ago•86 comments

Hardcore IndieWeb: Run your own website 100% independently for only $0.01/day

https://www.neatnik.net/hardcore-indieweb
193•cdrnsf•15h ago•163 comments

Scrying the AMD GFX1250 LLVM Tea Leaves

https://chipsandcheese.com/p/scrying-the-amd-gfx1250-llvm-tea
39•mfiguiere•8h ago•0 comments

Restoring and Demoing 1960s Vintage Computers at the Computer History Museum [pdf]

https://ibm-1401.info/pictures/Proc-MIW-2017-Garner-1401PDP1.pdf
22•rbanffy•1w ago•3 comments

Searchable field-level encryption on Supabase with CipherStash

https://supabase.com/blog/searchable-field-level-encryption-with-cipherstash
42•dandraper•4d ago•35 comments

Classic Amiga titles, free to download

https://amigafreeware.downer.tech/
139•doener•15h ago•19 comments

Half a Second – a book about the XZ backdoor

https://www.half-second.com/
40•zvr•4h ago•35 comments

Using self-hosted Umami for iOS app analytics

https://hjerpbakk.com/blog/2026/07/14/umami-for-apps
28•Sankra•5d ago•3 comments

A Visual Catalog of Retro Macintosh Software

https://www.marciot.com/mac68k-visual-catalog/
59•zdw•1w ago•6 comments

Making Software: How to make a font

https://www.makingsoftware.com/chapters/how-to-make-a-font
57•Garbage•5d ago•10 comments

Goodbye, and Thanks for All the Bikesheds

https://queue.acm.org/detail.cfm?id=3818307
238•Ygg2•19h ago•223 comments

The Art of Insight in Science and Engineering – Mastering Complexity(2014) [pdf]

https://ocw.mit.edu/courses/res-6-011-the-art-of-insight-in-science-and-engineering-mastering-com...
17•nill0•5h ago•1 comments

NYC may require landlords and realtors to disclose the use of AI in listings

https://petapixel.com/2026/07/16/mayor-mamdani-says-landlords-cant-secretly-use-ai-images-to-adve...
507•gnabgib•15h ago•220 comments

Claude Code uses Bun written in Rust now

https://simonwillison.net/2026/Jul/19/claude-code-in-bun-in-rust/
127•tosh•3h ago•165 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?