frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Redistribution of Housing Wealth Caused by Rent Control [pdf]

https://www.rhawa.org/file/secure/shs-the-impact-of-rent-control-in-st-paul.pdf
26•luu•58m ago•23 comments

10th Gen Honda Civic Updates Are Signed with AOSP Test Keys

https://juniperspring.org/posts/honda-evil-valet/
95•librick•3h ago•15 comments

Noise infusion banned from statistical products published by Census Bureau

https://desfontain.es/blog/banning-noise.html
768•nl•14h ago•480 comments

GLM 5.2 Is Out

https://twitter.com/jietang/status/2065784751345287314
417•aloknnikhil•11h ago•225 comments

Every Frame Perfect

https://tonsky.me/blog/every-frame-perfect/
615•ravenical•16h ago•202 comments

Treating pancreatic tumours may have revealed cancer's master switch

https://economist.com/science-and-technology/2026/06/12/treating-pancreatic-tumours-may-have-reve...
321•andsoitis•14h ago•115 comments

Pyodide 314.0: Python packages can now publish WebAssembly wheels to PyPI

https://blog.pyodide.org/posts/314-release/
94•agriyakhetarpal•4d ago•22 comments

FreeOberon – Open-Source, Cross-Platform, Free Pascal/Turbo Pascal-Like Language

https://github.com/kekcleader/FreeOberon
41•peter_d_sherman•2d ago•18 comments

Building a serial and VGA "everything console"

http://oldvcr.blogspot.com/2026/06/building-serial-and-vga-everything.html
5•classichasclass•1h ago•0 comments

Python 3.14 garbage collection rigamarole

https://theconsensus.dev/p/2026/06/06/python-3-14-garbage-collection-rigamarole.html
15•eatonphil•1d ago•9 comments

A whale necropolis has been found

https://www.nature.com/articles/d41586-026-01581-x
39•tigerlily•3d ago•13 comments

ReactOS (FOSS "Windows") achieves 3D-accelerated Half-Life on real hardware

https://www.phoronix.com/news/ReactOS-Running-Half-Life
131•jeditobe•4h ago•19 comments

Codex for open source

https://openai.com/form/codex-for-oss/
189•EvgeniyZh•2d ago•63 comments

GameBoy Workboy

https://tcrf.net/Workboy
169•tosh•10h ago•57 comments

Amazon CEO's talks with U.S. officials triggered crackdown on Anthropic models

https://www.wsj.com/tech/ai/amazon-ceos-talks-with-u-s-officials-triggered-crackdown-on-anthropic...
592•ls612•10h ago•435 comments

Running DOS on Behringers DDX3216 with a DIY x86-Bios from Scratch

https://chrisdevblog.com/2026/06/08/running-dos-on-behringers-ddx3216-using-a-diy-x86-bios/
84•rasz•9h ago•17 comments

Apt Encounters of the Third Kind

https://igor-blue.github.io/2021/03/24/apt1.html
7•ogurechny•1h ago•1 comments

4 things to know about the new sunscreen ingredient the FDA approved

https://www.npr.org/2026/06/13/nx-s1-5856385/sunscreen-skin-protection-bemotrizinol
58•mikhael•2h ago•19 comments

The Field Guide to CSS Grid Lanes

https://gridlanes.webkit.org/
7•ingve•3d ago•0 comments

Police officer investigated for using AI to 'create evidence' in multiple cases

https://news.sky.com/story/derbyshire-police-officer-investigated-for-using-ai-to-create-evidence...
258•austinallegro•8h ago•122 comments

A low-carbon computing platform from your retired phones

https://research.google/blog/a-low-carbon-computing-platform-from-your-retired-phones/
257•vikas-sharma•18h ago•139 comments

Appreciating Exif

https://brentfitzgerald.com/posts/appreciating-exif/
140•burnto•4d ago•29 comments

Ancient genome duplications laid the foundations of complex brains

https://www.ox.ac.uk/news/2026-06-09-ancient-genome-duplications-laid-the-foundations-of-complex-...
22•hhs•5h ago•1 comments

Human Routers of Machine Words

https://borretti.me/article/human-routers-of-machine-words
42•zx321•6h ago•19 comments

The adder at the heart of Intel's 8087 floating-point chip

https://www.righto.com/2026/06/intel-8087-adder-reverse-engineered.html
99•pwg•11h ago•25 comments

RTX 5080 and RTX 3090 Setup: 80 Tok/s on Qwen 3.6 27B Q8

https://imil.net/blog/posts/2026/rtx-5080-+-rtx-3090-setup-80+-tok-s-on-qwen-3.6-27b-q8/
210•iMil•18h ago•69 comments

The experience of rendering Arabic typography and its technical debt

https://lr0.org/blog/p/arabic/
205•bookofjoe•15h ago•50 comments

Resurrecting a soaked, corroded, and damaged Commodore SX‑64 (2025)

https://jerrylparker.com/blogs/posts/sx-64.html
22•hggh•2d ago•3 comments

AI coding at home without going broke

https://stephen.bochinski.dev/blog/2026/06/13/ai-coding-at-home-without-going-broke/
253•sbochins•11h ago•222 comments

Orthodox C++ (2016)

https://bkaradzic.github.io/posts/orthodoxc++/
91•signa11•13h ago•153 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?