frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

MiMo Code Is Now Released and Open-Source

https://mimo.xiaomi.com/mimocode
52•apeters•49m ago•26 comments

Lines of Code Got a Better Publicist

https://curlewis.co.nz/posts/lines-of-code-got-a-better-publicist/
186•RyeCombinator•2h ago•108 comments

Nextcloud Hub 26 Spring: Built together, designed for the future

https://nextcloud.com/blog/nextcloud-hub26-spring/
43•doener•58m ago•10 comments

MapComplete – Contibute to OpenStreetMaps

https://mapcomplete.org/
43•GTP•1h ago•5 comments

Pokémon Go Scans Trained the Navigation Tech for Military Drones

https://dronexl.co/2026/06/09/pokemon-go-scans-niantic-vantor-military-drone-navigation/
537•vrganj•8h ago•243 comments

Open Reproduction of DeepSeek-R1

https://github.com/huggingface/open-r1
55•yogthos•2h ago•7 comments

US-Canada border library gets new Quebec-only entrance

https://www.bbc.com/news/videos/clyrvrde160o
75•NalNezumi•1h ago•47 comments

Workers are spending over 6 hours a week botsitting AI, fueling job frustration

https://www.businessinsider.com/botsitting-ai-hidden-human-labor-at-work-2026-6
135•ZeidJ•1h ago•83 comments

Why Thermodynamics Rules Future Orbital Data Centers

https://spectrum.ieee.org/orbital-data-centers-heat
15•rbanffy•1h ago•6 comments

AI agent runs amok in Fedora and elsewhere

https://lwn.net/SubscriberLink/1077035/c7e7c14fbd60fae9/
506•tanelpoder•15h ago•229 comments

Web Browsers on Video Game Consoles

https://vale.rocks/posts/game-console-browsers
111•robin_reala•6h ago•56 comments

Queues Don't Fix Overload (2014)

https://ferd.ca/queues-don-t-fix-overload.html
5•locknitpicker•2d ago•0 comments

Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable

https://techcrunch.com/2026/06/10/cybersecurity-researchers-arent-happy-about-the-guardrails-on-a...
541•speckx•22h ago•471 comments

πFS

https://github.com/philipl/pifs
883•helterskelter•20h ago•197 comments

Build a Basic AI Agent from Scratch: Long Task Planning

https://medium.com/@rogi23696/build-a-basic-ai-agent-from-scratch-long-task-planning-14e803f9bd6d
96•ruxudev•2d ago•35 comments

Anthropic requires 30 day data retention for Fable and Mythos

https://support.claude.com/en/articles/15425996-data-retention-practices-for-mythos-class-models
558•lebovic•1d ago•282 comments

Amazon Says Its Data Centers Use 2.5B Gallons of Water

https://www.bloomberg.com/news/articles/2026-06-11/amazon-says-its-data-centers-use-2-5-billion-g...
15•1vuio0pswjnm7•18m ago•7 comments

Supporting Exchange and beyond

https://brendan.abolivier.bzh/exchange-pt-2/
7•babolivier•2d ago•0 comments

Linux latency measurements and compositor tuning

https://farnoy.dev/posts/linux-latency
93•GalaxySnail•2d ago•27 comments

I'm Eric Ries, author of "The Lean Startup" and new book "Incorruptible" – AMA

746•eries•1d ago•516 comments

AMD Gaslights Security Researcher, Changes Rules Retroactively [video]

https://www.youtube.com/watch?v=4HjWHNLRMB0
13•SockThief•40m ago•3 comments

Reverse engineering the Creative Katana soundbar to control it from Linux

https://blog.nns.ee/2026/02/20/katana-v2x-re/
119•theanonymousone•4d ago•9 comments

Why AI hasn't replaced software engineers, and won't

https://www.normaltech.ai/p/why-ai-hasnt-replaced-software-engineers
169•trueduke•7h ago•192 comments

Starfish by Peter Watts (1999)

https://www.rifters.com/real/STARFISH.htm#prelude
108•zetalyrae•2d ago•41 comments

Euro-Office: First version of the open-source web office is here

https://www.heise.de/en/news/Euro-Office-First-version-of-the-open-source-web-office-is-here-1132...
22•doener•1h ago•8 comments

Sequoyah’s syllabary created a written language for the Cherokee

https://www.smithsonianmag.com/innovation/man-created-written-language-cherokee-did-efficiently-e...
183•grahambargeron•17h ago•113 comments

PgDog is funded and coming to a database near you

https://pgdog.dev/blog/our-funding-announcement
514•levkk•1d ago•244 comments

The Economics of Speculative Decoding

https://fergusfinn.com/blog/economics-of-speculative-decoding/
17•kkm•2d ago•3 comments

Sweet Jeebus, macOS 27 Golden Gate Removes the Dumb Icons from Menu Items

https://daringfireball.net/2026/06/macos_27_golden_gate_removes_the_dumb_icons_from_menu_items
251•epaga•7h ago•112 comments

How JPL keeps the 13-year-old Curiosity rover doing science

https://spectrum.ieee.org/curiosity-rover-jpl-mars-science
263•pseudolus•21h ago•78 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?