frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Fabrice Bellard Releases MicroQuickJS

https://github.com/bellard/mquickjs/blob/main/README.md
1007•Aissen•14h ago•386 comments

X-ray: a Python library for finding bad redactions in PDF documents

https://github.com/freelawproject/x-ray
382•rendx•10h ago•78 comments

Some Epstein file redactions are being undone with hacks

https://www.theguardian.com/us-news/2025/dec/23/epstein-unredacted-files-social-media
413•vinni2•12h ago•290 comments

Unifi Travel Router

https://blog.ui.com/article/travel-in-style-unifi-style-unifi-travel-router
226•flurdy•7h ago•176 comments

Texas app store age verification law blocked by federal judge

https://www.macrumors.com/2025/12/23/texas-app-store-law-blocked/
218•danso•10h ago•119 comments

Autonomously navigating the real world: lessons from the PG&E outage

https://waymo.com/blog/2025/12/autonomously-navigating-the-real-world
73•scoofy•6h ago•22 comments

Show HN: Turn raw HTML into production-ready images for free

https://html2png.dev
57•alvinunreal•6h ago•26 comments

Nabokov's guide to foreigners learning Russian

https://twitter.com/haravayin_hogh/status/2003299405907247502
75•flaxxen•7h ago•101 comments

CEO killed at industrial site by worker operating forklift

https://www.12onyourside.com/2025/12/23/ceo-killed-industrial-site-by-worker-operating-forklift-w...
7•gehwartzen•2h ago•0 comments

Could lockfiles just be SBOMs?

https://nesbitt.io/2025/12/23/could-lockfiles-just-be-sboms.html
45•zdw•6h ago•21 comments

Custom Cross Compiler with Nix

https://www.hobson.space/posts/nixcross/
13•todsacerdoti•2h ago•0 comments

Life, Death and Mowing

https://www.cam.ac.uk/stories/lawnmower-poetry
6•timthorn•4d ago•2 comments

Don't Become the Machine

https://armeet.bearblog.dev/becoming-the-machine/
50•armeet•4h ago•16 comments

Proving Bounds for the Randomized MaxCut Approximation Algorithm in Lean4

https://abhamra.com/blog/randomized-maxcut/
26•todsacerdoti•3d ago•0 comments

Lua 5.5

https://lua.org/versions.html#5.5
276•km•1d ago•89 comments

Is Northern Virginia still the least reliable AWS region?

https://statusgator.com/blog/aws-least-reliable-region-in-2025/
89•colinbartlett•9h ago•59 comments

Perfect Software – Software for an Audience of One

https://outofdesk.netlify.app/blog/perfect-software
135•ggauravr•4d ago•57 comments

Correspondence Between Don Knuth and Peter van Emde Boas on Priority Deques 1977 [pdf]

https://staff.fnwi.uva.nl/p.vanemdeboas/knuthnote.pdf
30•vismit2000•6h ago•2 comments

Learn Lisp/Fennel Programming Against Neovim

https://github.com/humorless/fennel-fp-neovim
51•veqq•6d ago•5 comments

HTTP Caching, a Refresher

https://danburzo.ro/http-caching-refresher/
100•danburzo•12h ago•15 comments

We replaced H.264 streaming with JPEG screenshots (and it worked better)

https://blog.helix.ml/p/we-mass-deployed-15-year-old-screen
403•quesobob•14h ago•247 comments

Interactive Fluid Typography

https://electricmagicfactory.com/articles/interactive-fluid-typography/
41•list•5d ago•8 comments

What makes you senior

https://terriblesoftware.org/2025/11/25/what-actually-makes-you-senior/
311•mooreds•4d ago•153 comments

Open source USB to GPIB converter (for Test and Measurement instruments)

https://github.com/xyphro/UsbGpib
30•v15w•7h ago•6 comments

'Dracula's Chivito': Hubble reveals largest birthplace of planets ever observed

https://phys.org/news/2025-12-chaotic-dracula-chivito-hubble-reveals.html
41•wglb•6h ago•9 comments

Volvo Centum is Dalton Maag's new typeface for Volvo

https://www.wallpaper.com/design-interiors/corporate-design-branding/volvo-new-font-volvo-centum
81•ohjeez•13h ago•68 comments

Help My c64 caught on fire

https://c0de517e.com/026_c64fire.htm
94•ibobev•13h ago•30 comments

Fifty problems with standard web APIs in 2025

https://zerotrickpony.com/articles/browser-bugs/
112•dhruv3006•6d ago•36 comments

iOS 26.3 brings AirPods-like pairing to third-party devices in EU under DMA

https://www.macrumors.com/2025/12/22/ios-26-3-dma-airpods-pairing/
285•Tomte•1d ago•251 comments

Time-Traveling to 1979: Advice for Designing 'C with Classes

https://coderschmoder.com/i-time-traveled-1979-met-bjarne-stroustrup
11•birdculture•1w ago•8 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?