frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Linux kernel framework for PCIe device emulation, in userspace

https://github.com/cakehonolulu/pciem
47•71bw•3h ago•11 comments

The Overcomplexity of the Shadcn Radio Button

https://paulmakeswebsites.com/writing/shadcn-radio-button/
276•dbushell•3h ago•126 comments

Level S4 solar radiation event

https://www.swpc.noaa.gov/news/g4-severe-geomagnetic-storm-levels-reached-19-jan-2026
452•WorldPeas•14h ago•152 comments

Increasing the performance of WebAssembly Text Format parser by 350%

https://blog.gplane.win/posts/improve-wat-parser-perf.html
27•gplane•5d ago•13 comments

UK consulting on bringing in social media ban for under 16s

https://www.bbc.com/news/articles/cgm4xpyxp7lo
15•1659447091•32m ago•14 comments

King – man + woman is queen; but why? (2017)

https://p.migdal.pl/blog/2017/01/king-man-woman-queen-why/
19•CGMthrowaway•4d ago•16 comments

String Theory Can Now Describe a Universe That Has Dark Energy

https://www.quantamagazine.org/string-theory-can-now-describe-a-universe-that-has-dark-energy-202...
3•nsoonhui•37m ago•0 comments

Reticulum, a secure and anonymous mesh networking stack

https://github.com/markqvist/Reticulum
219•brogu•11h ago•45 comments

x86 prefixes and escape opcodes flowchart

https://soc.me/interfaces/x86-prefixes-and-escape-opcodes-flowchart.html
64•gaul•7h ago•15 comments

Apple testing new App Store design that blurs the line between ads and results

https://9to5mac.com/2026/01/16/iphone-apple-app-store-search-results-ads-new-design/
404•ksec•18h ago•314 comments

What came first: the CNAME or the A record?

https://blog.cloudflare.com/cname-a-record-order-dns-standards/
374•linolevan•17h ago•131 comments

Nanolang: A tiny experimental language designed to be targeted by coding LLMs

https://github.com/jordanhubbard/nanolang
160•Scramblejams•13h ago•122 comments

Giving university exams in the age of chatbots

https://ploum.net/2026-01-19-exam-with-chatbots.html
101•ploum•3h ago•67 comments

Scaling long-running autonomous coding

https://simonwillison.net/2026/Jan/19/scaling-long-running-autonomous-coding/
102•srameshc•10h ago•40 comments

The coming industrialisation of exploit generation with LLMs

https://sean.heelan.io/2026/01/18/on-the-coming-industrialisation-of-exploit-generation-with-llms/
153•long•1d ago•112 comments

Notes on Apple's Nano Texture (2025)

https://jon.bo/posts/nano-texture/
194•dsr12•16h ago•104 comments

Nova Launcher added Facebook and Google Ads tracking

https://lemdro.id/post/lemdro.id/35049920
260•celsoazevedo•10h ago•107 comments

3D printing my laptop ergonomic setup

https://www.ntietz.com/blog/3d-printing-my-laptop-ergonomic-setup/
75•kurinikku•11h ago•14 comments

The Antarctic Snow Cruiser

https://www.amusingplanet.com/2026/01/the-antarctic-snow-cruiser.html
4•terryf•3d ago•0 comments

Kahan on the 8087 and designing Intel's floating point (2016) [video]

https://www.youtube.com/watch?v=L-QVgbdt_qg
27•bananaboy•5d ago•0 comments

British redcoat's lost memoir reveals realities of life as a disabled veteran

https://phys.org/news/2026-01-british-redcoat-lost-memoir-reveals.html
88•wglb•4d ago•81 comments

Show HN: Artificial Ivy in the Browser

https://da.nmcardle.com/grow
74•dnmc•7h ago•12 comments

Porsche sold more electrified cars in Europe in 2025 than pure gas-powered cars

https://newsroom.porsche.com/en/2026/company/porsche-deliveries-2025-41516.html
325•m463•10h ago•389 comments

Understanding ZFS Scrubs and Data Integrity

https://klarasystems.com/articles/understanding-zfs-scrubs-and-data-integrity/
55•zdw•5d ago•22 comments

Prediction markets are ushering in a world in which news becomes about gambling

https://www.theatlantic.com/technology/2026/01/america-polymarket-disaster/685662/
299•krustyburger•1d ago•308 comments

The assistant axis: situating and stabilizing the character of LLMs

https://www.anthropic.com/research/assistant-axis
97•mfiguiere•13h ago•14 comments

Face as a QR Code

https://bookofjoe2.blogspot.com/2025/12/your-face-as-qr-code.html
25•surprisetalk•3d ago•6 comments

The microstructure of wealth transfer in prediction markets

https://www.jbecker.dev/research/prediction-market-microstructure
161•jonbecker•19h ago•146 comments

Targeted Bets: An alternative approach to the job hunt

https://www.seanmuirhead.com/blog/targeted-bets
67•seany62•13h ago•68 comments

From Nevada to Kansas by Glider

https://www.weglide.org/flight/978820
147•sammelaugust•4d ago•47 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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