frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Things to know when you get cancer – 2026 Edition

https://jjmaxwell4.com/writing/things-to-know-when-you-get-cancer/
482•jjmaxwell4•2h ago•119 comments

OpenCode 2.0

https://anoma.ly/notes/opencode-2-0/
117•gmays•1h ago•40 comments

We’re releasing Jev 1.14.0 along with experimental features for dreamers

https://typesafe.ai/blog/jev-1-14
70•emschwartz•1h ago•28 comments

Passkeys are not a trap

https://scotthelme.co.uk/passkeys-are-not-a-trap/
357•speckx•7h ago•553 comments

Do dentists know what they're doing?

https://mapwriting.substack.com/p/dentists
256•doitLP•2d ago•188 comments

Containment and monitoring failures are to blame for AI hacking reports: experts

https://www.csoonline.com/article/4234854/ai-agents-arent-going-rogue-frontier-labs-are-skipping-...
783•latexr•4h ago•384 comments

Better HTTP/1 connection reuse in Go 1.27

https://go.dev/blog/http-connection-reuse
170•allddd•5h ago•28 comments

Anthropic's Scion is heavily inspired by Mononoke

https://sunshowers.io/posts/anthropic-mononoke/
164•sunshowers•1h ago•57 comments

Fancy Curl Sites

https://nytpu.com/gemlog/2026-03-18
47•adunk•2h ago•10 comments

Show HN: Petal, open-source CoScreen/ScreenHero finally free

https://petal.live/
84•thedracle•3h ago•19 comments

Fire at Starlink site in Bulgaria after suspected sabotage in Poland

https://dpa-international.com/politics/urn:newsml:dpa.com:20090101:261014-930-839530/
238•ilamont•3h ago•168 comments

Iosevka is an open-source, sans-serif and slab-serif monospace font

https://typeof.net/Iosevka/
679•otobrglez•13h ago•279 comments

Yandex outage: data shows that instead of going dark, malicious bots moved

https://blog.cloudflare.com/yandex-outage/
138•coloneltcb•1h ago•44 comments

Phloem: Git history grown like a slime mold

https://phloem.stemdeck.app/
64•thclpr•2d ago•18 comments

Banks are now trying to offload the AI data center debt they just underwrote

https://startupfortune.com/banks-are-now-trying-to-offload-the-ai-data-center-debt-they-just-unde...
222•smartmic•3h ago•172 comments

Americans' social activity has steeply declined in the past 30 years

https://www.dataforprogress.org/blog/2026/9/29/americans-social-activity-has-steeply-declined-in-...
97•hubraumhugo•6h ago•176 comments

Marshall Islands Stick Chart

https://en.wikipedia.org/wiki/Marshall_Islands_stick_chart
25•Thevet•1d ago•4 comments

Submarine cable resilience

https://blog.apnic.net/2026/10/14/submarine-cable-resilience/
120•speckx•6h ago•38 comments

Has AI tells

https://theconsensus.dev/blog/2026/10/14/has-ai-tells.html?focus=1
59•7777777phil•5h ago•51 comments

Suicide rates highest ever among middle-aged men

https://www.telegraph.co.uk/news/2026/10/13/suicide-rates-highest-ever-among-middle-aged-men/
163•ivewonyoung•3h ago•189 comments

Google is silently linking your phone number across all signed-in accounts

https://www.androidauthority.com/google-auto-phone-number-verification-android-3723117/
310•Brajeshwar•5h ago•80 comments

Virtual Oxide Labs: Emulating a Full Oxide Rack

https://oxide.computer/blog/voxel-labs
28•tosh•3h ago•1 comments

Webster’s Dictionary: The pleasure of finding things out (2014)

https://jsomers.net/blog/dictionary
6•hangsi•1d ago•0 comments

Pg_vectorsearch: An index that is faster than pgvector's IVFFlat and HNSW

https://github.com/timescale/pg_vectorsearch
180•jascha_eng•10h ago•47 comments

LittleJS is 2D and 3D now

https://frankforce.com/littlejs-is-2d-and-3d-now/
79•dmit•1d ago•25 comments

Show HN: I wrote an email app that accepts only one sender per inbox

https://clova.email/
57•edpin2000•5h ago•45 comments

Amazon pushes up prices across the Internet

https://www.not-ship.com/how-amazon-pushes-up-prices-all-across-the-internet/
673•sighborg•12h ago•565 comments

America didn't lose its rare earth industry, it sold it

https://www.lawfaremedia.org/article/america-didn-t-lose-its-rare-earth-industry.-it-sold-it
120•speckx•4h ago•54 comments

Neckbeard – A DevOps/platform/SRE plugin for your agent

https://github.com/bealesh/neckbeard
56•bealesh•4h ago•47 comments

Why is every rationalist blog post way too long?

https://alexwennerberg.com/blog/2026-10-13-long.html
117•epestr•16h ago•95 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?