frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The 26,000-Year Astronomical Monument Hidden in Plain Sight

https://longnow.org/ideas/the-26000-year-astronomical-monument-hidden-in-plain-sight/
66•mkmk•53m ago•12 comments

The Unix Pipe Card Game

https://punkx.org/unix-pipe-game/
70•kykeonaut•2h ago•20 comments

IP Addresses Through 2025

https://www.potaroo.net/ispcol/2026-01/addr2025.html
122•petercooper•5h ago•59 comments

Show HN: wxpath – Declarative web crawling in XPath

https://github.com/rodricios/wxpath
20•rodricios•6d ago•0 comments

Unconventional PostgreSQL Optimizations

https://hakibenita.com/postgresql-unconventional-optimizations
110•haki•4h ago•11 comments

Nvidia Stock Crash Prediction

https://entropicthoughts.com/nvidia-stock-crash-prediction
191•todsacerdoti•3h ago•149 comments

De-dollarization: Is the US dollar losing its dominance? (2025)

https://www.jpmorgan.com/insights/global-research/currencies/de-dollarization
412•andsoitis•3h ago•492 comments

I'm addicted to being useful

https://www.seangoedecke.com/addicted-to-being-useful/
319•swah•8h ago•179 comments

Google co-founder reveals that "many" of the new hires do not have a degree

https://www.yahoo.com/news/articles/google-cofounder-reveals-tons-recent-231500103.html
28•01-_-•45m ago•17 comments

Linux kernel framework for PCIe device emulation, in userspace

https://github.com/cakehonolulu/pciem
174•71bw•11h ago•65 comments

The Zen of Reticulum

https://github.com/markqvist/Reticulum/blob/master/Zen%20of%20Reticulum.md
66•mikece•5h ago•41 comments

Level S4 solar radiation event

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

Show HN: Ocrbase – pdf → .md/.json document OCR and structured extraction API

https://github.com/majcheradam/ocrbase
61•adammajcher•6h ago•18 comments

Channel3 (YC S25) Is Hiring

https://www.ycombinator.com/companies/channel3/jobs/3DIAYYY-backend-engineer
1•aschiff1•7h ago

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/
565•ksec•1d ago•463 comments

IP over Avian Carriers with Quality of Service (1999)

https://www.rfc-editor.org/rfc/rfc2549.html
51•mig4ng•8h ago•23 comments

Reticulum, a secure and anonymous mesh networking stack

https://github.com/markqvist/Reticulum
303•brogu•19h ago•72 comments

Everyone's a Gangster, Till You Get Bundled in G-Suite

https://twitter.com/keropillay/status/2013454666244481244
20•keroshanpillay•50m ago•7 comments

Running Claude Code dangerously (safely)

https://blog.emilburzo.com/2026/01/running-claude-code-dangerously-safely/
209•emilburzo•7h ago•176 comments

Increasing the performance of WebAssembly Text Format parser by 350%

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

What came first: the CNAME or the A record?

https://blog.cloudflare.com/cname-a-record-order-dns-standards/
431•linolevan•1d ago•149 comments

Kiss Launcher – fast launcher for Android

https://kisslauncher.com/
65•ifh-hn•9h ago•33 comments

Benchmarking a Baseline Fully-in-Place Functional Language Compiler [pdf]

https://trendsfp.github.io/papers/tfp26-paper-12.pdf
30•matt_d•4d ago•3 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/
230•long•1d ago•140 comments

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

https://github.com/jordanhubbard/nanolang
211•Scramblejams•21h ago•166 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/
440•krustyburger•2d ago•427 comments

How Hightouch built their long-running agent harness

https://www.amplifypartners.com/blog-posts/how-hightouch-built-their-long-running-agent-harness
33•thecr0w•38m ago•1 comments

Notes on Apple's Nano Texture (2025)

https://jon.bo/posts/nano-texture/
238•dsr12•1d ago•124 comments

3D printing my laptop ergonomic setup

https://www.ntietz.com/blog/3d-printing-my-laptop-ergonomic-setup/
141•kurinikku•19h ago•66 comments

Scaling long-running autonomous coding

https://simonwillison.net/2026/Jan/19/scaling-long-running-autonomous-coding/
155•srameshc•18h ago•83 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?