frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Longest Straight Line Paths on Water or Land on the Earth (2018)

https://arxiv.org/abs/1804.07389
82•joebig•3h ago•16 comments

Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel

https://www.qubes-os.org/news/2026/08/29/qsb-118/
57•vntok•3h ago•17 comments

Brits would quite like their private messages to stay private

https://www.theregister.com/security/2026/08/30/turns-out-brits-would-quite-like-their-private-me...
115•defrost•2h ago•69 comments

Everyone Should Build Their Own Network Stack

https://blog.lyc8503.net/en/post/dn42-2-dnet/
22•uneven9434•2h ago•14 comments

RISC-V is now officially supported by CPython

https://blog.python.org/2026/08/riscv-now-officially-supported/
197•lumpa•5d ago•39 comments

Spark: Sparklines in your shell

https://git.zx2c4.com/spark/about/
25•hskimse•1h ago•3 comments

Hy4 preview

https://www.tencent.com/tencent-releases-and-open-sources-tencent-hy4-preview/
324•shenli3514•16h ago•197 comments

JupyterGIS 0.16: a grammar of graphics for maps, and collaborative story maps

https://blog.jupyter.org/jupytergis-0-16-new-visualization-capabilities-collaborative-story-maps-...
32•arjxn-py•5d ago•4 comments

Xcena and Samsung's Near Memory Compute CXL Device

https://chipsandcheese.com/p/hot-chips-2026-xcena-and-samsungs
18•klelatti•4h ago•1 comments

California lawmakers unanimously pass Linux exemption from age-verification law

https://www.tomshardware.com/software/linux/california-lawmakers-unanimously-pass-linux-exemption...
354•shscs911•8h ago•157 comments

Show HN: Bolnee-Chat – Self Hosted Chatbot Integration in Your Business Website

https://github.com/AniketWathore/bolnee-chat
9•AniketWathore•2h ago•0 comments

FreeCORE TrueNAS Core – Continued

https://freecore.org/
115•sashk•10h ago•65 comments

The Einstein-Szilard Refrigerator (2020)

https://invention.si.edu/invention-stories/einstein-szilard-refrigerator
43•EndXA•3d ago•12 comments

Bug Blindness

https://danluu.com/bug-blind/
285•davidmckenna•11h ago•176 comments

Tether: iMessage, SMS, etc. on Linux

https://zackbartel.com/blog/2026/08/tether/
474•zackb•6d ago•186 comments

Fair Work Commission condemns 'plain wrong' AI legal advice

https://www.abc.net.au/news/2026-08-29/fair-work-commission-condemns-ai-legal-advice/107089766
20•martyvis•1h ago•4 comments

Nancy Grace Roman Space Telescope

https://science.nasa.gov/mission/roman-space-telescope/
211•JumpCrisscross•20h ago•80 comments

Benchmarking Pocket-Scale Inference

https://artificialanalysis.ai/hardware-inference-stack/mobile-phones
53•sys42590•2d ago•4 comments

Creating Teensy ELF Executables for Linux (Or, "Size Is Everything") (1999)

https://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
51•Bluestein•4d ago•12 comments

Benjamin Franklin's Alter Egos Gave Him the Most Freedom

https://www.smithsonianmag.com/history/among-all-great-things-benjamin-franklin-invented-discover...
76•cisc•10h ago•34 comments

Orbs

https://ampcode.com/notes/orbs-explained
18•tosh•4d ago•10 comments

SQLite as a Document Database (2020)

https://dgl.cx/2020/06/sqlite-json-support
218•lioeters•5d ago•53 comments

EVE Online moves to Python 3

https://www.eveonline.com/news/view/the-move-to-python-3-begins
371•TylerJaacks•4d ago•200 comments

Lawmakers added $1 to car insurance policies. That money paid for Flock cameras

https://www.texastribune.org/2026/08/28/texas-flock-cameras-auto-insurance-fee-mvcpa-grants/
320•DeepLogin•12h ago•185 comments

Glacier Mice

https://en.wikipedia.org/wiki/Glacier_mice
311•ostacke•5d ago•61 comments

Functional State Machines in Rust: Typestate and Newtype Patterns

https://dl.acm.org/doi/10.1145/3830438.3830958
96•matt_d•16h ago•36 comments

Is it safe to call print in a Python signal handler?

https://iafisher.com/2026/08/sigprint
53•hellerve•3d ago•29 comments

Nvidia's AI advantage is moving beyond the GPU

https://techcrunch.com/2026/08/29/nvidias-ai-advantage-is-moving-beyond-the-gpu/
11•01-_-•2h ago•5 comments

Open Oscar Server: open-source server compatible with AIM and ICQ clients

https://github.com/mk6i/open-oscar-server
45•gregsadetsky•11h ago•16 comments

Samsung's Processing-in-Memory (PIM)

https://chipsandcheese.com/p/hot-chips-2026-samsungs-processing
267•ingve•1d ago•104 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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