frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

PyPI's redesigned project pages with clearer security signals are now live

https://blog.pypi.org/posts/2026-11-06-ui-updates-complete/
94•rbanffy•2h ago•27 comments

KDE: The documentary [video]

https://tube.kockatoo.org/w/fFinNHfanLT7aBEb2B8y4c
168•mrkn1•4h ago•26 comments

Why get an expensive Pi when I have an old phone?

https://so.long.thanks.fish/why-pi-when-i-have-an-old-phone/
372•casi•4d ago•227 comments

Advancing science and engineering with Antigravity's /teamwork

https://research.google/blog/advancing-science-engineering-with-antigravitys-teamwork-feature/
70•acossta•4h ago•18 comments

Show HN: A terminal-native idle factory game, written in Rust with ratatui

https://gitlab.com/snipedbywifi/terminactory
78•snipedbywifi•3h ago•14 comments

Generative AI uses more energy on non-English text

https://news.umich.edu/generative-ai-uses-more-energy-on-non-english-text/
95•DeepLogin•4d ago•64 comments

Show HN: DeepSeek V3 in ~200 lines of pure Jax

https://github.com/Vaibhaav-Tiwari/deepseek-v3-jax
19•VaibhaavTiwari•2h ago•0 comments

Show HN: Fursoy – Out-of-order RV64IMAFDV core in SystemVerilog (Linux 6.6)

https://github.com/FURSOY/fursoy-cpu
30•fursoy•3h ago•8 comments

Ggml v1.0.0

https://github.com/ggml-org/ggml/releases/tag/v1.0.0
377•cobychapple•15h ago•64 comments

Testing a Trash Can Faraday Cage

https://www.jefftk.com/p/testing-a-trash-can-faraday-cage
38•torutofu•2d ago•21 comments

Tech Companies Are Trying to Shift the Concept of Privacy (Again)

https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again
239•gslin•5h ago•94 comments

Monkey Island: all 13 versions side by side

https://monkeyisland.pages.dev/
353•maximilianburke•13h ago•121 comments

Reverse engineering a vintage diode-transistor logic chip

https://www.righto.com/2026/11/signetics-st680a-dtl-nand.html
19•dverlaeckt80•5d ago•1 comments

Formalizing US Tax Code (Using Lean)

https://lexifina.com/blog/formalizing-the-us-tax-code
53•dnw•2h ago•18 comments

Italy fines Meta $887M over Android users' data access

https://www.reuters.com/world/italy-fines-meta-887-million-over-android-users-data-access-2026-11...
146•giuliomagnifico•3h ago•71 comments

Show HN: Agweb – a browser for agents that stays out of your way

https://github.com/paul-nameless/agweb
47•paul_nameless•3h ago•14 comments

Serving GLM-5.3 at 607.8 tok/s across two Nvidia DGX stations with vLLM

https://developer.nvidia.com/blog/when-one-gpu-isnt-enough-serving-glm-5-3-across-two-nvidia-dgx-...
81•wondersky•3h ago•39 comments

Let's Write a PostScript Interpreter

https://beyondloom.com/blog/postscript.html
66•RebelPotato•1d ago•11 comments

C3 0.8.6:Library fetching,30% smaller safe-mode binaries,and stricter type rules

https://c3-lang.org/blog/c3_0_8_6_fetching_libraries/
11•DASD•2d ago•1 comments

Italy fines Meta €805M over photo privacy

https://www.rapporteur.com/news/italy-fines-meta-880mn-over-photo-privacy-authority/
95•jruohonen•1h ago•46 comments

A visual explanation of reinforcement learning

https://aatishb.com/myriad/how-brains-learn/
39•aatish•4h ago•1 comments

Terminal borders that don't cost a cell

https://www.joshka.net/cell-borders/
382•vinhnx•18h ago•165 comments

Nvidia allegedly engineered scarcity by funding AI startups to buy its GPUs

https://www.techpowerup.com/354814/nvidia-allegedly-engineered-scarcity-by-funding-ai-startups-to...
944•speckx•14h ago•574 comments

Bilingualism and Denaskuleco

https://pgadey.ca/notes/bilingualism-and-denaskuleco/
15•surprisetalk•2d ago•8 comments

Unsloth Qwen3.8-27B Quantizations – Dynamic v3.1 Update

https://unsloth.ai/docs/models/qwen3.8
224•Retro_Dev•17h ago•71 comments

FAA issues national ground stop – lifted 4.5 hours later

https://www.nbcnews.com/news/us-news/faa-orders-nationwide-ground-stop-departing-flights-reasons-...
1621•zulln•20h ago•1248 comments

What happened to 3Com?

https://dfarq.homeip.net/what-happened-to-3com/
191•gvieri•17h ago•109 comments

Show HN: Live map of U.S. flights during tonight's FAA nationwide ground stop

https://grounds.top/
196•gvsi•18h ago•24 comments

Found: A protein that drives ageing without unleashing inflammation

https://www.nature.com/articles/d41586-026-03638-3
242•gumby•22h ago•76 comments

Show HN: I have trained 15 blood glucose forecasting models on my own data

https://github.com/0xdeadf1sh/T1DMAI
83•0xdeadf1sh•3d ago•45 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?