frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.8 27B

https://huggingface.co/Qwen/Qwen3.8-27B-FP8
835•erdaltoprak•9h ago•550 comments

Going Dark, and the era of law enforcement hacking

https://blog.cryptographyengineering.com/2026/08/14/everything-is-about-to-go-dark/
144•vslira•3h ago•93 comments

RISC-V: They should have known better

https://dmitry.gr/?r=06.%20Thoughts&proj=12.%20RV
54•kaycebasques•1h ago•29 comments

Why does Opus 5 feel worse to work with?

https://mun-logadan.github.io/why-does-opus-5-feel-worse/
749•numeri•13h ago•686 comments

The case for overhauling American science

https://www.economist.com/by-invitation/2026/08/13/the-case-for-overhauling-american-science
8•andsoitis•51m ago•1 comments

RustDesk now supports true unattended remote access on Wayland

https://rustdesk.com/blog/unattended-remote-access-wayland/
205•rustdesk•7h ago•91 comments

Super Mario Derivations

https://fzakaria.com/2026/08/05/super-mario-derivations
35•domenkozar•1w ago•2 comments

Google is making private AI practical with homomorphic encryption

https://blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption/
253•u1hcw9nx•8h ago•158 comments

AI by Hand

https://www.byhand.ai/
180•sans_souse•8h ago•14 comments

Firefox is now the last major browser that still supports uBlock Origin

https://www.pcworld.com/article/3212428/firefox-is-now-the-last-major-browser-that-still-supports...
287•DemiGuru•5h ago•98 comments

Introducing Toast 1

https://www.mixedbread.com/blog/toast-1
171•mplappert•8h ago•56 comments

Ultraviolet Bird Photography

https://uvbirds.com/
98•EndXA•1w ago•19 comments

I turned my RSS feeds into an e-ink newspaper to stop reading on my phone

https://heyjonny.dev/posts/rss-to-eink-newspaper/
137•speckx•9h ago•57 comments

New Lower and Upper Bounds for the Grothendieck Constant

https://arxiv.org/abs/2608.11158
29•surprisetalk•4h ago•4 comments

Show HN: Mole – Deep research agent for your terminal

https://github.com/lajosdeme/mole
42•lajosdeme•5h ago•6 comments

Stop sending me huge PRs; a rant

https://getsmall.xyz/post/cmstjfl9l000if70ljmpzr4va
15•trezm•1h ago•2 comments

Maximizing the value of your Claude Code sessions

https://claude.com/blog/maximizing-the-value-of-your-claude-code-sessions
121•twapi•7h ago•83 comments

Turbo Pascal on CP/M, MSX-DOS and MS-DOS

http://pascal.hansotten.com/delphi/turbo-pascal-on-cpm-msx-dos-and-ms-dos/
64•rbanffy•2d ago•19 comments

Every exterior shot in The Taking of Pelham 123

https://iafisher.com/2026/07/pelham-123
24•evakhoury•3h ago•5 comments

The American sports plutocracy

https://www.derekthompson.org/p/the-american-sports-plutocracy-is
46•momentmaker•5h ago•28 comments

Seven books I keep close because I love them

https://blog.plover.com/2026/08/02/
287•surprisetalk•8h ago•129 comments

Show HN: Ember – Redshift safe color palettes

https://github.com/carpdiem/ember
48•carpdiem•5d ago•13 comments

Don't classify, hallucinate

https://softwaredoug.com/blog/2026/08/10/hypothetical-classifications
214•softwaredoug•4d ago•84 comments

GLM-5.3: Frontier coding with emergent cyber capabilities

https://z.ai/blog/glm-5.3
1022•pella•18h ago•504 comments

Show HN: LuaCAD – Parametric CAD Scripted in Lua

https://luacad.ad-si.com
66•adius•7h ago•13 comments

ICTP Announces 2026 Dirac Medal Recipients (Physics)

https://www.ictp.it/news/2026/8/ictp-announces-2026-dirac-medal-recipients
10•rramadass•4d ago•1 comments

Every Fucking Website (2020)

https://lxe.github.io/everywebsite/
718•doubletwoyou•9h ago•414 comments

Jane Street suffers $15B hit after meltdown at Situational Awareness

https://www.ft.com/content/47dd5308-dd17-404a-a615-61046defd697
13•bobstax•22m ago•0 comments

A humble cabbage became one of the Forbidden City’s treasures (2025)

https://www.cnn.com/2025/11/10/style/jadeite-cabbage-taiwan-forbidden-city-curio-hnk-intl
52•dude250711•2d ago•7 comments

Moving integer division to floating-point is trivial

http://marc-b-reynolds.github.io/math/2026/08/10/IntDivByFP.html
34•matt_d•3d ago•13 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?