frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Google stole open source code without crediting the authors (Artemis/Minitap)

https://www.minitap.ai/blog/i-expected-better-from-google
52•MysteryPancake•1h ago•7 comments

A misalignment of AI in mathematics

https://mathandai.org/
737•meredydd•10h ago•746 comments

Pandas Should Go Extinct

https://eddie.codes/posts/pandas-should-go-extinct/
43•__eddie__•1h ago•24 comments

I spent $220 on Google app ads and 60% of the installs were robots

https://dayzlegame.com/blog/google-ads-bot-farm/
369•nickabe•9h ago•192 comments

A Design Space Exploration of Async/Await

https://cel.cs.brown.edu/blog/design-space-async-await/
184•wcrichton•2d ago•37 comments

Google no longer provides direct URLs in search results

https://www.autom.dev/blog/google-search-goto-links
8•1e1a•32m ago•2 comments

OpenAI agents carried out an undisclosed attack on RubyGems

https://www.rubyhack.ai/
441•chao-•4h ago•255 comments

GrapheneOS' rewritten Messages app is released

https://github.com/GrapheneOS/Messaging/releases/tag/13
219•microtonal•8h ago•134 comments

Project Blinkenlights

https://blinkenlights.de/en/
60•doener•5h ago•25 comments

Litelm: LiteLLM Without the Bloat

https://github.com/kennethwolters/litelm
108•kennethwolters•9h ago•39 comments

Mind-altering drugs played key role in rise of Andean civilization

https://www.science.org/content/article/mind-altering-drugs-played-key-role-rise-andean-civilization
116•geneticdrifts•10h ago•81 comments

Hepburn Romanization: How to Read Japanese in the Latin Alphabet

https://www.fink-translate.com/blog/hepburn-romanization.html
31•miuraboy•1d ago•31 comments

Show HN: ResolveHQ – A Helpdesk Built on Cloudflare Workers, D1, R2 and Queues

https://github.com/mirza-rizvi/ResolveHQ
40•mirza_rizvi•5h ago•14 comments

Great Lakes sturgeon may be 400 years old:Scientists rethinking how to save them

https://www.cbc.ca/news/canada/ontario-great-lakes-sturgeon-lifespan-study-9.7329250
7•bookofjoe•2d ago•1 comments

Λ Snap – An inviting programming language for kids and adults for CS study

https://snap.berkeley.edu/
122•dr_kiszonka•10h ago•62 comments

AlphaGenome maps 9B DNA variants

https://spectrum.ieee.org/alphagenome-atlas
73•ltononro•2d ago•7 comments

I've operated petabyte-scale ClickHouse clusters for 5 years

https://www.tinybird.co/blog/what-i-learned-operating-clickhouse
184•adastral•4d ago•72 comments

Rune is now open source

https://rune.build/blog/rune-is-now-open-source
155•ernestrc•12h ago•55 comments

The EPA is planning to scrap public review rules for data center pollution

https://capitalbnews.org/data-centers-permit-rules-epa/
387•doener•9h ago•269 comments

Starlink Signal Leakage Threatens Radio Astronomy's Most Critical Frequencies

https://www.gadgetreview.com/starlinks-signal-leakage-is-threatening-radio-astronomys-most-critic...
62•upofadown•3h ago•25 comments

Show HN: Graphify C# – Compiler-accurate Find Usages for coding agents

https://github.com/zachsaw/graphify-csharp
19•zachsaw•3h ago•9 comments

AI researchers debate how close we are to recursive self-improvement

https://www.dwarkesh.com/p/john-beren-charlie
66•artninja1988•6h ago•57 comments

Testing Race Conditions

https://projectzero.google/2026/09/maccconc-race-condition.html
23•alpaylan•2d ago•0 comments

Logo Programming Language

https://el.media.mit.edu/logo-foundation/what_is_logo/logo_programming.html
244•azhenley•2d ago•103 comments

Show HN: Bodily Oddities

https://vester.si/bodily-oddities/
179•vesterde•1d ago•141 comments

How we rebuilt complex permissions without migrating to Zanzibar

https://infisical.com/blog/folder-based-rbac
33•FinnLobsien•2d ago•8 comments

Claude is only available to people over 18 years

https://support.claude.com/en/articles/15171100-age-assurance-on-claude
595•Muhammad523•16h ago•612 comments

Zep AI (YC W24) Is Hiring a Head of Forward Deployed Engineering

https://www.getzep.com/careers/
1•roseway4•10h ago

QueryBrew: System-Agnostic SQL-to-SQL Query Optimization [pdf]

https://www.vldb.org/pvldb/vol19/p4494-schmidt.pdf
23•matt_d•5h ago•8 comments

RTK reports token savings, but our cost benchmarks disagree

https://quesma.com/blog/does-rtk-make-ai-coding-cheaper/
149•michalwarda•16h ago•76 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?