frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ray Bradbury's "There Will Come Soft Rains" is set today (2026-08-04)

https://short-stories.co/@raybradbury/there-will-come-soft-rains-6k8vr4xxlnmj
207•askvictor•4h ago•54 comments

DeepSeek V4 Flash on a Single AMD MI300X

https://github.com/ryanzhou/deepseek-v4-flash-mi300x
184•zhoutong•4h ago•46 comments

Xbox goes down. You can't play games you own on disc

https://birchtree.me/blog/xbox-goes-down-you-cant-play-games-you-own-on-disc/
222•surprisetalk•2h ago•225 comments

LLMs reward expertise

https://www.seangoedecke.com/llms-reward-expertise/
1141•MaxMussio•17h ago•479 comments

Buckminster Fuller: everything I know

https://www.bfi.org/about-fuller/everything-i-know/
49•simonebrunozzi•2h ago•17 comments

Keyv and friends compromised in active Shai-Hulud supply chain attack

https://www.aikido.dev/blog/keyv-and-friends-compromised-in-npm-supply-chain-attack
63•cimi_•3h ago•11 comments

Show HN: Fine-tune an 8B model on a 4 GB laptop GPU

https://github.com/MakazhanAlpamys/Soup
46•MakazhanAlpamys•3h ago•7 comments

Harness Engineering for Self-Improvement

https://lilianweng.github.io/posts/2026-07-04-harness/
154•tosh•8h ago•30 comments

Why Large Language Models Fail at Tabular Prediction

https://arxiv.org/abs/2608.02412
35•sbulaev•4h ago•6 comments

AI-Generated Images Discourage Me from Reading Your Blog

https://nelson.cloud/ai-generated-images-discourage-me-from-reading-your-blog/
458•meysamazad•2h ago•268 comments

Roame (YC S23) Is Hiring Lead Engineer

https://www.ycombinator.com/companies/roame/jobs/mqqfa38-lead-full-stack-engineer
1•zman0225•2h ago

Show HN: Run an 80B Qwen in 4.3 GB of RAM on a Mac, and a 35B on an iPhone

https://github.com/leonickson1/Swiftlet
248•leonickson•21h ago•113 comments

Why etymologies matter: How tracing words can illuminate history (2024)

https://resobscura.substack.com/p/why-i-love-etymologies
34•benbreen•3d ago•7 comments

Ten advances in mathematics and theoretical computer science

https://openai.com/index/ten-advances-in-mathematics/
579•milkshakes•21h ago•868 comments

Devtools must be open source

https://blog.exe.dev/devtools-must-be-open-source
665•bryanmikaelian•1d ago•216 comments

Amazonian civilization had estimated 3M people in 3% of forest area

https://www.science.org/content/article/odd-shapes-hidden-dense-amazon-rainforest-reveal-sprawlin...
209•marojejian•5d ago•155 comments

Dates That Don't Exist (2015)

https://blog.yossarian.net/2015/06/09/Dates-That-Dont-Exist
5•EndXA•2d ago•0 comments

Homebench – Benchmark local LLMs for speed, memory, and quality

https://github.com/david-g-3654/homebench
22•davai-g•4h ago•1 comments

There Will Come Soft Rains (1950) [pdf]

https://users.wpi.edu/~zrbutzke/Docs/BradburyStories(1).pdf
249•pmg101•15h ago•88 comments

Mosh in a Lift (2012)

https://mosh.org/elevator.txt
17•gavide•1d ago•2 comments

Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone

https://learning-rust.github.io
21•dumindunuwan•4h ago•1 comments

FFmpeg 9.0

https://github.com/FFmpeg/FFmpeg/blob/n9.0/RELEASE_NOTES
327•gyan•4h ago•61 comments

Archaeologists Find Ancient Glyphs in the Amazon

https://www.nytimes.com/2026/07/31/world/americas/amazon-archaeology-geoglyphs.html
22•wglb•2d ago•9 comments

That time when I failed the Microsoft interview

https://ochagavia.nl/blog/that-time-when-i-failed-the-microsoft-interview/
102•wofo•6d ago•198 comments

Twenty Years of Pandoc

https://pandoc.org/twenty-years-of-pandoc.html
338•fiddlosopher•23h ago•41 comments

"Clean" Code, Horrible Performance

https://www.computerenhance.com/p/clean-code-horrible-performance
17•FrojoS•4h ago•2 comments

Smaller, faster, safer: running Kimi and GLM at scale

https://blog.cloudflare.com/smaller-faster-safer-models/
246•ascorbic•21h ago•61 comments

Ask HN: Who is hiring? (August 2026)

202•whoishiring•23h ago•188 comments

Nobel Disease

https://en.wikipedia.org/wiki/Nobel_disease
55•num42•3h ago•49 comments

Safe Lock-free Primitives with iceoryx2's ByteAtomic

https://ekxide.io/blog/byte-wise-atomic-wrapper-to-prevent-ub/
10•elfenpiff•3h 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?