frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
314•o4c•4h ago•55 comments

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
382•zaik•8h ago•110 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
45•PaulHoule•2d ago•7 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
544•ilreb•8h ago•227 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
297•hspeiser•12h ago•155 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
273•zdw•10h ago•347 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
160•aillia•10h ago•45 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
350•bcye•15h ago•57 comments

“…and the proof is checked in Lean”

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
22•matt_d•3h ago•3 comments

Preserving 30 years of Salon journalism

https://blog.archive.org/2026/11/12/preserving-30-years-of-salon-journalism/
154•CharlesW•11h ago•39 comments

The Lasting Influence of John Berger

https://www.newyorker.com/magazine/2026/11/16/john-berger-a-life-tom-overton-book-review
25•prismatic•4d ago•0 comments

A short explainer on how El Niño works [video]

https://www.youtube.com/watch?v=7_JF3etiAv8
245•nharada•16h ago•112 comments

Handwriting, as a Font

https://ductus.sorenblank.com
302•coinfused•15h ago•57 comments

Do we still have to denormalize? Have your schema and search it too

https://www.paradedb.com/blog/joins
77•philippemnoel•2d ago•20 comments

Crows make decisions faster than we can

https://www.nytimes.com/2026/11/15/science/birdbrain-crows-birds-research-decision.html
245•gumby•16h ago•165 comments

Making Atuin sync 32x faster with packfiles

https://blog.atuin.sh/making-atuin-sync-32x-faster-with-packfiles/
13•ossusermivami•4d ago•3 comments

Simple 8085 Computer

https://www.hackster.io/mit41301/simple-8085-computer-9fe156
43•AlexeyBrin•3d ago•3 comments

WebGL Flight Simulator with seed generated terrain

https://baron.by.dai.studio/
154•ranger_danger•14h ago•32 comments

Artificial Intelligence for the Z80

https://www.dfsantos.com/en/libro-ia-z80
49•AlexeyBrin•2d ago•7 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
71•nerdypepper•10h ago•19 comments

I Can't Believe It Can Sort

https://yugen-tsuki.github.io/unbelievablesort.html
10•Muhammad523•2d ago•19 comments

A quest to create the perfect whiskey glass

https://www.nytimes.com/2026/11/13/dining/drinks/kurt-josef-zalto-whiskey-glass.html
66•Kaibeezy•2d ago•69 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
100•artooro•5h ago•35 comments

Did the Apollo Guidance Computer use 60% of the ICs in 1963?

https://retrocomputing.stackexchange.com/questions/12158/did-the-apollo-guidance-computer-really-...
15•Skyfall106•5h ago•1 comments

Skydio's asymmetrical F10 Lightrunner solves a problem with fixed-wing drones

https://spectrum.ieee.org/skydio-f10-lightrunner-asymmetrical-drone
42•Gaishan•10h ago•6 comments

Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests

https://www1.wdr.de/nrw/rheinland/rhein-erft-kreis/technischer-defekt-chlor-phantasialand-100.html
551•DeepLogin•16h ago•238 comments

Emacs Is My Browser

https://joshblais.com/blog/emacs-as-my-browser/
214•nyc111•19h ago•122 comments

SpaceX catches the Starship to end Flight 15

https://www.spacex.com/launches/starship-flight-15
1701•ls612•1d ago•1271 comments

Eclipse Mosquitto – An open source MQTT broker

https://github.com/eclipse-mosquitto/mosquitto
95•gregsadetsky•16h ago•34 comments

Parcel: A desktop mail client for Linux, built with Zig

https://tangled.org/rockorager.dev/parcel
41•nerdypepper•10h ago•8 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?