frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

A backdoor in a LinkedIn job offer

https://roman.pt/posts/linkedin-backdoor/
714•lwhsiao•6h ago•148 comments

Banned Book Library in a Wi-Fi Smart Light Bulb

https://www.richardosgood.com/posts/banned-book-library/
163•sohkamyung•3h ago•58 comments

Iroh 1.0

https://www.iroh.computer/blog/v1
950•chadfowler•10h ago•285 comments

TinyWind: A pixel pirate sailing game with real wind physics (380k+ kms sailed)

https://tinywind.io
613•tinywind•9h ago•125 comments

I Love the Computer

https://michaelenger.com/blog/i-love-the-computer/
144•speckx•5h ago•92 comments

Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?

695•cloudking•11h ago•339 comments

Amazon Announces Multibillion-Dollar Data Center in Missouri

https://www.narracomm.com/amazon-announces-multibillion-dollar-data-center-in-missouri/
24•thelonelyborg•1h ago•8 comments

Why I email complete strangers

https://www.goodinternetmagazine.com/why-i-email-complete-strangers/
76•karakoram•4h ago•39 comments

Peopleless economy? Not technically impossible

https://gmalandrakis.com/writings/ad-economicum.html
95•l0new0lf-G•4h ago•167 comments

My Homelab AI Dev Platform

https://rsgm.dev/post/ai-dev-platform/
240•rsgm•11h ago•48 comments

Hetzner Price Adjustment

https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/#cloud-servers
337•tuhtah•12h ago•484 comments

US battery manufacturing output continues to break records

https://fred.stlouisfed.org/series/IPG33591S
162•epistasis•5h ago•133 comments

What every coder should know about Gamma Correction

https://blog.johnnovak.net/2016/09/21/what-every-coder-should-know-about-gamma/
58•sph•2d ago•19 comments

Reviews have become expensive, rewrites have become cheap

http://ishmeetbindra.com/posts/reviews-have-become-expensive-rewrites-have-become-cheap/
12•arzh2•1h ago•11 comments

Fox to buy Roku

https://www.wsj.com/business/deals/fox-roku-deal-f6e564f9
276•thm•13h ago•369 comments

What job interviews taught me about Kubernetes

https://notnotp.com/notes/what-job-interviews-taught-me-about-kubernetes/
90•chmaynard•5h ago•83 comments

Cohere's First Model for Developers

https://cohere.com/blog/north-mini-code
15•hmokiguess•4d ago•3 comments

Game Engine White Papers Commander Keen

https://forgottenbytes.net/commander_keen.html
162•mfiguiere•8h ago•53 comments

Salesforce to Acquire Fin (formerly Intercom) for $3.6B

https://www.salesforce.com/news/press-releases/2026/06/15/salesforce-signs-definitive-agreement-t...
277•colesantiago•14h ago•208 comments

How TimescaleDB compresses time-series data

https://roszigit.com/en/blog/timescaledb-compression-hypercore
116•lkanwoqwp•8h ago•14 comments

An O(x)Caml book that runs

https://kcsrk.info/ocaml/oxcaml/teaching/nptel/llm/2026/06/13/an-oxcaml-book-that-runs/
26•anirudh24seven•2d ago•9 comments

Copper transport drug restores memory and clears toxic Alzheimer's proteins

https://www.monash.edu/news/articles/copper-drug-restores-memory-and-clears-toxic-alzheimers-prot...
255•bookofjoe•11h ago•96 comments

Launch HN: Drafted (YC P26) – Models for residential architecture

42•PrimalNick•9h ago•52 comments

Claude Corps

https://www.anthropic.com/news/claude-corps
85•Mustan•8h ago•59 comments

Show HN: Fata – Spaced repetition to fight skill rot from AI coding

https://fata.dev
79•djoume•4d ago•44 comments

Factoring "short-sleeve" RSA keys with polynomials

https://blog.trailofbits.com/2026/06/12/factoring-short-sleeve-rsa-keys-with-polynomials/
74•ledoge•3d ago•1 comments

How memory safety CVEs differ between Rust and C/C++

https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html
110•nicoburns•9h ago•111 comments

Making glass-to-metal seals for home­made vacuum tubes

https://maurycyz.com/projects/glass/1/
129•zdw•1d ago•41 comments

Boot Naked Linux

https://nick.zoic.org/art/boot-naked-linux/
94•abnercoimbre•10h ago•48 comments

Show HN: Vet turned founder, AI lawn diagnosis

https://grassdx.com/
38•andrewbr•8h ago•38 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?