frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

CSS Grid Lanes

https://webkit.org/blog/17660/introducing-css-grid-lanes/
409•frizlab•7h ago•116 comments

Mistral OCR 3

https://mistral.ai/news/mistral-ocr-3
457•pember•1d ago•84 comments

Garage – An S3 object store so reliable you can run it outside datacenters

https://garagehq.deuxfleurs.fr/
519•ibobev•14h ago•108 comments

Carolina Cloud – One third the cost of AWS for data science workloads

https://carolinacloud.io/
65•bojangleslover•5d ago•26 comments

Fuzix on a Raspberry Pi Pico

https://ewpratten.com/blog/fuzix-pi-pico
24•ewpratten•4d ago•0 comments

Gh-actions-lockfile: generate and verify lockfiles for GitHub Actions

https://gh-actions-lockfile.net
17•gjtorikian•3d ago•4 comments

TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

https://www.evilsocket.net/2025/12/18/TP-Link-Tapo-C200-Hardcoded-Keys-Buffer-Overflows-and-Priva...
250•sibellavia•11h ago•68 comments

A better zip bomb (2019)

https://www.bamsoftware.com/hacks/zipbomb/
114•kekqqq•8h ago•40 comments

8-bit Boléro

https://linusakesson.net/music/bolero/index.php
205•Aissen•18h ago•36 comments

Graphite is joining Cursor

https://cursor.com/blog/graphite
204•fosterfriends•14h ago•219 comments

Iberian peninsula is rotating clockwise

https://phys.org/news/2025-12-iberian-peninsula-rotating-clockwise-geodynamic.html
16•karma_daemon•5d ago•1 comments

Android introduces $2-4 install fee and 10–20% cut for US external content links

https://support.google.com/googleplay/android-developer/answer/16470497?hl=en
34•radley•59m ago•11 comments

Brown/MIT shooting suspect found dead, officials say

https://www.washingtonpost.com/nation/2025/12/18/brown-university-shooting-person-of-interest/
129•anigbrowl•1d ago•153 comments

LLM Year in Review

https://karpathy.bearblog.dev/year-in-review-2025/
123•swyx•9h ago•36 comments

Build Your Own React

https://pomb.us/build-your-own-react/
44•howToTestFE•5h ago•4 comments

Rust's Block Pattern

https://notgull.net/block-pattern/
151•zdw•1d ago•70 comments

Qwen-Image-Layered: transparency and layer aware open diffusion model

https://huggingface.co/papers/2512.15603
85•dvrp•1d ago•13 comments

Show HN: TinyPDF – 3kb pdf library (70x smaller than jsPDF)

https://github.com/Lulzx/tinypdf
146•lulzx•1d ago•20 comments

Performance Hints (2023)

https://abseil.io/fast/hints.html
76•danlark1•12h ago•29 comments

The FreeBSD Foundation's Laptop Support and Usability Project

https://github.com/FreeBSDFoundation/proj-laptop
151•mikece•15h ago•56 comments

Believe the Checkbook

https://robertgreiner.com/believe-the-checkbook/
135•rg81•14h ago•60 comments

Vm.overcommit_memory=2 is the right setting for servers

https://ariadne.space/2025/12/16/vmovercommitmemory-is-always-the-right.html
65•signa11•2d ago•106 comments

History LLMs: Models trained exclusively on pre-1913 texts

https://github.com/DGoettlich/history-llms
789•iamwil•1d ago•380 comments

Amazon will allow ePub and PDF downloads for DRM-free eBooks

https://www.kdpcommunity.com/s/article/New-eBook-Download-Options-for-Readers-Coming-in-2026?lang...
573•captn3m0•19h ago•286 comments

The scariest boot loader code

http://miod.online.fr/software/openbsd/stories/boot_hppa.html
43•todsacerdoti•9h ago•4 comments

Reverse Engineering US Airline's PNR System and Accessing All Reservations

https://alexschapiro.com/security/vulnerability/2025/11/20/avelo-airline-reservation-api-vulnerab...
103•bearsyankees•11h ago•50 comments

The pitfalls of partitioning Postgres yourself

https://hatchet.run/blog/postgres-partitioning
62•abelanger•3d ago•5 comments

GotaTun – Mullvad's WireGuard Implementation in Rust

https://mullvad.net/en/blog/announcing-gotatun-the-future-of-wireguard-at-mullvad-vpn
559•km•18h ago•121 comments

Buteyko Method

https://en.wikipedia.org/wiki/Buteyko_method
51•rzk•8h ago•32 comments

Beginning January 2026, all ACM publications will be made open access

https://dl.acm.org/openaccess
1970•Kerrick•1d ago•233 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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