frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Why Janet? (2023)

https://ianthehenry.com/posts/why-janet/
118•yacin•1h ago•40 comments

Adafruit Receives Demand Letter from Fenwick Legal Counsel on Behalf of Flux.ai

https://blog.adafruit.com/
45•semanser•1h ago•9 comments

CSS-Native Parallax Effect

https://dan-webnotes.com/posts/2026-06-02-css-native-parallax-effect/
14•dandep•43m ago•4 comments

The newest Instagram “exploit” is the goofiest I've seen

https://www.0xsid.com/blog/meta-account-takeover-fiasco
1866•ssiddharth•18h ago•423 comments

Muxcard, a dyi credit card size computer

https://github.com/krauseler/muxcard
65•sargstuff•2d ago•9 comments

Can the stockmarket swallow Anthropic, SpaceX and OpenAI?

https://www.economist.com/finance-and-economics/2026/06/01/can-the-stockmarket-swallow-anthropic-...
402•1vuio0pswjnm7•11h ago•698 comments

macOS needs its grid back

https://blog.hopefullyuseful.com/blog/macos-needs-its-grid-back/
270•ranebo•9h ago•157 comments

CQL: Categorical Databases

https://categoricaldata.net/
42•noworriesnate•2d ago•11 comments

OpenAI frontier models and Codex are now available on AWS

https://openai.com/index/openai-frontier-models-and-codex-are-now-available-on-aws/
284•typpo•13h ago•97 comments

Chipotlai Max

https://github.com/cyberpapiii/chipotlai-max
241•nigelgutzmann•12h ago•38 comments

How is Groq raising more money?

https://www.zach.be/p/how-the-hell-is-groq-raising-more
115•hasheddan•10h ago•50 comments

Debug Project

https://debug.com/
228•Eridanus2•14h ago•91 comments

AI Agent Guidelines for CS336 at Stanford

https://github.com/stanford-cs336/assignment1-basics/blob/main/CLAUDE.md
424•prakashqwerty•18h ago•140 comments

CS336: Language Modeling from Scratch

https://cs336.stanford.edu/
478•kristianpaul•20h ago•48 comments

Strace-ui, Bonsai_term, and the TUI renaissance

https://blog.janestreet.com/strace-ui-bonsai-term-and-the-tui-renaissance/
56•matt_d•7h ago•34 comments

Michael Burry says neither SpaceX nor Anthropic is worth $1T

https://www.businessinsider.com/big-short-michael-burry-spacex-anthropic-ipo-ai-bubble-claude-2026-6
28•mgh2•58m ago•22 comments

Fooling around with encrypted reasoning blobs

https://blog.cryptographyengineering.com/2026/05/29/fooling-around-with-encrypted-reasoning-blobs/
100•supermatou•4d ago•17 comments

Should you normalize RGB values by 255 or 256?

https://30fps.net/pages/255-vs-256-division/
274•pplanu•17h ago•118 comments

On Reading SRAMs in IR Images, and Establishing Bounds on Trust

https://www.bunniestudios.com/blog/2026/on-reading-srams-in-ir-images-and-establishing-bounds-on-...
5•zdw•1d ago•0 comments

Microsoft builds MacBook Pro rival with NVIDIA-powered Surface Laptop Ultra

https://www.windowslatest.com/2026/06/01/microsoft-builds-its-ultimate-macbook-pro-rival-with-the...
225•jbk•23h ago•470 comments

Launch HN: Expanse (YC P26) – Unlock Wasted GPU Capacity

83•ismaeel_bashir•22h ago•24 comments

What appear to be biochemical processes may be a natural feature of geology

https://www.quantamagazine.org/the-dirt-that-refused-to-die-20260601/
242•speckx•19h ago•88 comments

Crystal Nights (2008)

https://www.gregegan.net/MISC/CRYSTAL/Crystal.html
47•rorylawless•9h ago•6 comments

Ask HN: Who is hiring? (June 2026)

197•whoishiring•20h ago•277 comments

Alphabet announces $80B equity capital raise to expand AI infra and compute

https://abc.xyz/investor/news/news-details/2026/Alphabet-Announces-Proposed-80-Billion-Equity-Cap...
203•gregschlom•14h ago•187 comments

I made my phone slow on purpose

https://vinewallapp.com/notes/i-made-my-phone-slow-on-purpose/
210•gcampos•4d ago•177 comments

A new way to build chips: Sequentially stacking silicon to extend Moore's Law

https://matse.illinois.edu/news/85775
51•hhs•2d ago•32 comments

Florida sues OpenAI and Sam Altman over AI risks

https://www.politico.com/news/2026/06/01/openai-hit-with-florida-lawsuit-00944215
238•cyunker•19h ago•179 comments

America's Corporate Protector

https://www.bloomberg.com/features/2026-trump-cfpb-enforcement
6•petethomas•1h ago•0 comments

Age verification for social media, the beginning of the end for a free internet?

https://mullvad.net/en/blog/age-verification-for-social-media-the-beginning-of-the-end-for-a-free...
289•StrLght•11h ago•178 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?