frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Data Compression Explained (2012)

https://mattmahoney.net/dc/dce.html
66•mtdewcmu•3d ago•5 comments

There are no instances in ATProto

https://overreacted.io/there-are-no-instances-in-atproto/
396•danabramov•14h ago•207 comments

Snap Smart Glasses

https://www.specs.com/smart-glasses/specs-27
35•hmokiguess•2d ago•29 comments

The discovery that changed how scientists think about memory – IBM

https://www.ibm.com/think/news/discovery-changed-how-scientists-think-about-memory-kavli-prize
18•rbanffy•2d ago•0 comments

Surprising economics of load-balanced systems

https://brooker.co.za/blog/2020/08/06/erlang.html
75•KraftyOne•9h ago•19 comments

Hyundai buys Boston Dynamics

https://startupfortune.com/hyundai-takes-full-control-of-boston-dynamics-as-softbank-exits-for-32...
735•ck2•13h ago•339 comments

Norway imposes near ban on AI in elementary school

https://www.reuters.com/technology/norway-imposes-near-ban-ai-elementary-school-2026-06-19/
559•ilreb•13h ago•379 comments

Meet Nikolai Evreinov, the 19th century Nathan Fielder

https://mssv.net/2026/06/16/meet-nikolai-evreinov-the-19th-century-nathan-fielder/
18•adrianhon•3d ago•2 comments

Bobby Prince, composer for Doom, Wolfenstein 3D, and Duke Nukem 3D, has died

https://www.legacy.com/legacy/robert-bobby-prince-lll
293•pgrote•10h ago•33 comments

Project Valhalla, Explained: How a Decade of Work Arrives in JDK 28

https://www.jvm-weekly.com/p/project-valhalla-explained-how-a
564•philonoist•23h ago•355 comments

How many of the 170k English words do you know?

https://vocabowl-870366514258.us-west1.run.app/
295•abnry•16h ago•402 comments

Can you see three trees?

https://www.not-ship.com/can-you-see-three-trees/
23•Pamar•1d ago•0 comments

A Perceptron in Age of Empires II

https://adewynter.github.io/notes/aoe2-circuits
51•EvgeniyZh•1d ago•25 comments

Egyptian Fractions

https://blog.plover.com/math/egyptian-fractions.html
82•luu•4d ago•4 comments

Hey, n00b, we didn't hire you to complete tasks

https://newsletter.kentbeck.com/p/hey-n00b-we-didnt-hire-you-to-complete
137•rrvsh•5h ago•69 comments

How to feed a dictator

https://www.theguardian.com/film/2026/jun/09/how-to-feed-a-dictator-film
119•Michelangelo11•4h ago•41 comments

Satellite reveals immense scale of GPS signal tampering

https://www.space.com/space-exploration/satellites/its-quite-a-bit-more-than-we-expected-satellit...
18•y1n0•1h ago•0 comments

John Jumper to join Anthropic

https://twitter.com/JohnJumperSci/status/2068001285173834106
102•artninja1988•12h ago•74 comments

Ask HN: Will programmers write more efficient code during the memory shortage?

65•amichail•7h ago•99 comments

Telescope Ranchers

https://kottke.org/26/06/telescope-ranchers
112•bookofjoe•3d ago•43 comments

Court Records Should Be Free

https://www.eff.org/deeplinks/2026/06/court-records-should-be-free
316•hn_acker•12h ago•66 comments

Big Banana Car

https://bigbananacar.com/
135•Bender•11h ago•74 comments

Think of the children: How to force real ID for all internet traffic (2023)

https://nochan.net/b/Internet-Crap/20230829-Think-Of-The-Children/
181•Bender•9h ago•107 comments

Zen and the Art of Machine Learning Research

https://blog.jxmo.io/p/zen-and-the-art-of-machine-learning
247•jxmorris12•4d ago•89 comments

Show HN: Metiq: a real time 3D globe for 100 public datasets

https://metiq.space
107•rakeda•3d ago•30 comments

Building a robotics research setup that lives next to my desk

https://dfdxlabs.com/research/2026/robotics-setup/
133•mplappert•1d ago•45 comments

Digital Printing of Arabic: explaining the problem

https://digitalorientalist.com/2017/08/21/digital-printing-of-arabic-explaining-the-problem/
43•a_t48•3d ago•11 comments

Ten years of ClickHouse in open source

https://clickhouse.com/blog/open-source-10
293•saisrirampur•4d ago•73 comments

The AirPods Effect

https://www.theescapenewsletter.com/p/the-airpods-effect
395•herbertl•1d ago•702 comments

AURpocalypse now: a look at the recent AUR attacks

https://lwn.net/SubscriberLink/1077619/f7b07c5489fdd43a/
45•jwilk•12h ago•35 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?