frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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/
202•vrganj•2h ago•76 comments

AI agent runs amok in Fedora and elsewhere

https://lwn.net/SubscriberLink/1077035/c7e7c14fbd60fae9/
382•tanelpoder•9h ago•136 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...
426•speckx•16h ago•378 comments

πFS

https://github.com/philipl/pifs
736•helterskelter•14h ago•177 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
414•lebovic•1d ago•212 comments

Web Browsers on Video Game Consoles

https://vale.rocks/posts/game-console-browsers
7•robin_reala•34m ago•0 comments

Reverse engineering the Creative Katana soundbar to control it from Linux

https://blog.nns.ee/2026/02/20/katana-v2x-re/
63•theanonymousone•3d ago•2 comments

Starfish by Peter Watts (1999)

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

Linux latency measurements and compositor tuning

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

Sequoyah’s syllabary created a written language for the Cherokee

https://www.smithsonianmag.com/innovation/man-created-written-language-cherokee-did-efficiently-e...
154•grahambargeron•11h ago•91 comments

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

654•eries•18h ago•488 comments

Vacuum-Form Signage

https://bethmathews.substack.com/p/the-history-behind-the-signs-lighting
65•benbreen•1d ago•11 comments

PgDog is funded and coming to a database near you

https://pgdog.dev/blog/our-funding-announcement
456•levkk•19h ago•221 comments

Macaroni – a single HTML file messenger

https://github.com/vanyapr/makaroshki
46•snowflaxxx•2h ago•42 comments

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

https://spectrum.ieee.org/curiosity-rover-jpl-mars-science
227•pseudolus•15h ago•64 comments

Klondike Solitaire game for curses in 5k of C

https://nanochess.org/klondike_in_c.html
74•nanochess•2d ago•10 comments

GeoLibre 1.0

https://geolibre.app/
240•jonbaer•15h ago•21 comments

L'Affaire Siloxane

https://mceglowski.substack.com/p/laffaire-siloxane
225•idlewords•2d ago•38 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
42•epaga•1h ago•11 comments

Making a Shading Language for My Offline Renderer

https://agraphicsguynotes.com/posts/making_a_shading_langauge_for_my_offline_renderer/
4•ibobev•2d ago•0 comments

Show HN: Extend UI – open-source UI kit for modern document apps

https://www.extend.ai/ui
207•kbyatnal•17h ago•48 comments

Who's the smartest corvid?

https://thetyee.ca/Culture/2026/06/05/Whos-the-Smartest-Corvid/
102•NaOH•1d ago•89 comments

World Capitals Voronoi

https://www.jasondavies.com/maps/voronoi/capitals/
87•vincnetas•2d ago•39 comments

Building an HTML-first site doubled our users overnight

https://mohkohn.co.uk/writing/html-first/
1123•edent•20h ago•506 comments

Raspberry Pi 5 – 16GB RAM

https://www.adafruit.com/product/6125?src=raspberrypi
258•akman•13h ago•265 comments

Apache Burr: Build reliable AI agents and applications

https://burr.apache.org/
216•anhldbk•18h ago•107 comments

CSS: Unavoidable Bad Parts

https://matklad.github.io/2026/06/04/css-unavoidable-bad-parts.html
73•surprisetalk•1d ago•24 comments

What is it like to be a bat? (1974) [pdf]

https://www.sas.upenn.edu/~cavitch/pdf-library/Nagel_Bat.pdf
89•shadow28•12h ago•98 comments

Show HN: HelixDB – A graph database built on object storage

https://github.com/HelixDB/helix-db/tree/main
122•GeorgeCurtis•17h ago•36 comments

Are insecure code completions in PyCharm a vulnerability?

https://sethmlarson.dev/are-insecure-code-completions-a-vulnerability
31•12_throw_away•7h ago•14 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?