frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Cloudflare outage on November 18, 2025 post mortem

https://blog.cloudflare.com/18-november-2025-outage/
348•eastdakota•2h ago•196 comments

Rebecca Heineman – from homelessness to porting Doom

https://corecursive.com/doomed-to-fail-with-burger-becky/
92•birdculture•2h ago•18 comments

Gemini 3

https://blog.google/products/gemini/gemini-3/
1160•preek•10h ago•753 comments

Google Antigravity

https://antigravity.google/
696•Fysi•10h ago•742 comments

Blender 5.0

https://www.blender.org/download/releases/5-0/
439•FrostKiwi•4h ago•122 comments

Pebble, Rebble, and a path forward

https://ericmigi.com/blog/pebble-rebble-and-a-path-forward/
319•phoronixrly•8h ago•148 comments

The code and open-source tools I used to produce a science fiction anthology

https://compellingsciencefiction.com/posts/the-code-and-open-source-tools-i-used-to-produce-a-sci...
77•mojoe•9h ago•7 comments

Lucent 7 R/E 5ESS Telephone Switch Rescue

http://kev009.com/wp/2024/07/Lucent-5ESS-Rescue/
19•gjvc•1h ago•9 comments

Gemini 3 Pro Model Card [pdf]

https://storage.googleapis.com/deepmind-media/Model-Cards/Gemini-3-Pro-Model-Card.pdf
164•virgildotcodes•14h ago•309 comments

GitHub: Git operation failures

https://www.githubstatus.com/incidents/5q7nmlxz30sk
329•wilhelmklopp•5h ago•271 comments

Cloudflare Global Network experiencing issues

https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
2310•imdsm•14h ago•1591 comments

I am stepping down as the CEO of Mastodon

https://blog.joinmastodon.org/2025/11/my-next-chapter-with-mastodon/
329•Tomte•7h ago•245 comments

OrthoRoute – GPU-accelerated autorouting for KiCad

https://bbenchoff.github.io/pages/OrthoRoute.html
111•wanderingjew•6h ago•12 comments

What I learned about creativity from a man painting on a treadmill (2024)

https://quinnmaclay.com/texts/lets-paint
26•8organicbits•4d ago•4 comments

Bild AI (YC W25) is hiring – Make housing affordable

https://www.ycombinator.com/companies/bild-ai/jobs/m2ilR5L-founding-engineer-applied-ai
1•rooppal•4h ago

Monotype font licencing shake-down

https://www.insanityworks.org/randomtangent/2025/11/14/monotype-font-licencing-shake-down
90•evolve2k•3h ago•17 comments

Chuck Moore: Colorforth has stopped working [video]

https://www.youtube.com/watch?v=MvkGBWXb2oQ#t=22
67•netten•1d ago•31 comments

Solving a million-step LLM task with zero errors

https://arxiv.org/abs/2511.09030
128•Anon84•9h ago•45 comments

Show HN: A subtly obvious e-paper room air monitor

https://www.nicolin-dora.ch/blog/en-epaper-room-air-monitor-part-1/
34•nomarv•18h ago•8 comments

Show HN: RowboatX – open-source Claude Code for everyday automations

https://github.com/rowboatlabs/rowboat
54•segmenta•7h ago•11 comments

Mysterious holes in the Andes may have been an ancient marketplace

https://www.sydney.edu.au/news-opinion/news/2025/11/10/mysterious-holes-in-the-andes-may-have-bee...
35•gmays•6d ago•10 comments

Nearly all UK drivers say headlights are too bright

https://www.bbc.com/news/articles/c1j8ewy1p86o
668•YeGoblynQueenne•11h ago•689 comments

Short Little Difficult Books

https://countercraft.substack.com/p/short-little-difficult-books
146•crescit_eundo•11h ago•86 comments

Trying out Gemini 3 Pro with audio transcription and a new pelican benchmark

https://simonwillison.net/2025/Nov/18/gemini-3/
117•nabla9•6h ago•45 comments

Show HN: Guts – convert Golang types to TypeScript

https://github.com/coder/guts
72•emyrk•7h ago•20 comments

Strix Halo's Memory Subsystem: Tackling iGPU Challenges

https://chipsandcheese.com/p/strix-halos-memory-subsystem-tackling
62•PaulHoule•9h ago•29 comments

Google boss says AI investment boom has 'elements of irrationality'

https://www.bbc.com/news/articles/cwy7vrd8k4eo
169•jillesvangurp•19h ago•314 comments

Microsoft-backed Veir is bringing superconductors to data centers

https://techcrunch.com/2025/11/12/microsoft-backed-veir-targets-data-centers-for-its-megawatt-cla...
6•sudonanohome•5d ago•2 comments

Silverbullet: Personal productivity platform built with Markdown and Lua

https://github.com/silverbulletmd/silverbullet
9•nateb2022•6d ago•2 comments

When 1+1+1 Equals 1

https://mathenchant.wordpress.com/2024/12/19/when-111-equals-1/
38•surprisetalk•5d ago•25 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•6mo ago

Comments

balloob•6mo 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•6mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•6mo ago
Comments moved thither. Thanks!
pabs3•6mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo 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•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo 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?