frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Jurassic Park computers in excruciating detail

https://fabiensanglard.net/jurrasic_park_computers/index.html
551•vinhnx•8h ago•126 comments

Vancouver PD website features Quick Escape button that wipes itself from history

https://vpd.ca/
299•LookAtThatBacon•11h ago•121 comments

Bonsai 27B: A 27B-Class model that runs on a phone

https://prismml.com/news/bonsai-27b
626•xenova•18h ago•219 comments

TS-2026-009: Insecure argument handling in Tailscale SSH permitted root access

https://tailscale.com/security-bulletins
167•jervant•10h ago•97 comments

Who's running all those tiny RPKI servers?

https://blog.apnic.net/2026/07/15/whos-running-all-those-tiny-rpki-servers/
49•enz•5h ago•4 comments

Floating Companion: Exploring Design Space for Soft Floating Robots in Indoor

https://dl.acm.org/doi/10.1145/3800645.3813051
4•hopelessluca•51m ago•0 comments

The Tower Keeps Rising

https://lucumr.pocoo.org/2026/7/13/the-tower-keeps-rising/
486•cdrnsf•18h ago•227 comments

RISC-V Is Inevitable: State of the Union Keynote Argues

https://www.eetimes.com/risc-v-is-inevitable-state-of-the-union-keynote-argues/
86•signa11•5h ago•76 comments

I tricked Claude into leaking your deepest, darkest secrets

https://www.ayush.digital/blog/the-memory-heist
398•macleginn•5h ago•185 comments

Cursor 0day: When Full Disclosure Becomes the Only Protection Left

https://mindgard.ai/blog/cursor-0day-when-full-disclosure-becomes-the-only-protection-left
389•Synthetic7346•17h ago•181 comments

How I use HTMX with Go

https://www.alexedwards.net/blog/how-i-use-htmx-with-go
273•gnabgib•15h ago•77 comments

Dependabot version updates introduce default package cooldown

https://github.blog/changelog/2026-07-14-dependabot-version-updates-introduce-default-package-coo...
184•woodruffw•14h ago•118 comments

Neverclick: Desktop application for performing mouse actions with your keyboard

https://github.com/LazoVelko/neverclick
16•thunderbong•3d ago•18 comments

Andon (manufacturing)

https://en.wikipedia.org/wiki/Andon_(manufacturing)
59•tony•3d ago•22 comments

Combinatorial Games in Lean

https://github.com/vihdzp/combinatorial-games
16•wertyk•3d ago•2 comments

How to stop Claude from saying load-bearing

https://jola.dev/posts/how-to-stop-claude-from-saying-load-bearing
552•shintoist•1d ago•571 comments

Microsoft has released software updates to plug at least 570 security holes

https://krebsonsecurity.com/2026/07/microsoft-patches-a-record-570-security-flaws/
146•robin_reala•14h ago•95 comments

Show HN: Web App Uses RTL-SDR to Align HDTV Antenna

https://tunerscope.com/
12•robotastic•2d ago•1 comments

I'm a USB-C Maximalist

https://shkspr.mobi/blog/2026/07/im-a-usb-c-maximalist/
301•speckx•20h ago•395 comments

The kids with phones are alright

https://heatherburns.tech/2026/07/08/the-kids-with-phones-are-alright/
227•JumpCrisscross•4d ago•256 comments

Surprising lessons from my research scientist job search

https://yongzx.github.io/blog/2026/06/24/job-search/
20•gmays•4d ago•2 comments

The largest available Minecraft world, totalling 15 TB

https://2b2t.place/1million
229•_____k•3d ago•73 comments

LeMario: Training a JEPA World Model on Super Mario Bros

https://www.benjamin-bai.com/projects/lemario
118•kevinjosethomas•13h ago•13 comments

Mathematical texts from a Maya site in Guatemala identify an ancient astronomer

https://www.nature.com/articles/d41586-026-02170-8
100•homarp•1d ago•23 comments

The bread paradox: why convenience always wins, and why SaaS isn't doomed

https://www.joanwestenberg.com/p/the-bread-paradox-why-convenience
99•srijan4•1d ago•93 comments

Launch HN: Agnost AI (YC S26) – Extract user feedback from agent conversations

https://agnost.ai
79•laalshaitaan•19h ago•43 comments

Probably check on your smart appliances

https://xeiaso.net/notes/2026/check-your-smart-tv/
80•xena•13h ago•30 comments

The Estranged Worlds of J. G. Ballard

https://lareviewofbooks.org/article/jg-ballard-illuminated-man-christopher-priest-nina-allan/
69•Caiero•1d ago•15 comments

Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

https://github.com/juggler-ai/juggler
253•julesrms•2d ago•107 comments

Your 'app' could have been a webpage (so I fixed it for you)

https://danq.me/2026/07/09/your-app-could-have-been-a-webpage/
832•MrVandemar•4d ago•500 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?