frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Retrospectively Reverse-Engineering Apple's Neural Engine

https://eiln.github.io/posts/ane.html
97•zdw•3h ago•11 comments

IKEA made a mod for Skyrim [video]

https://www.youtube.com/watch?v=iZODN0QUgjI
158•kegenaar•2d ago•27 comments

A misalignment of AI in mathematics

https://mathandai.org/
950•meredydd•17h ago•910 comments

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

https://dayzlegame.com/blog/google-ads-bot-farm/
558•nickabe•16h ago•295 comments

A Design Space Exploration of Async/Await

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

Navier-Stokes Announcement

https://www.claymath.org/news/navier-stokes-announcement/
182•rvz•6h ago•122 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
73•bookofjoe•2d ago•7 comments

google.com/goto: Google's anti-scraping update

https://www.autom.dev/blog/google-search-goto-links
451•1e1a•7h ago•351 comments

Inverse Kinematics and Foot Locking

https://theorangeduck.com/page/inverse-kinematics-foot-locking
52•airhangerf15•5d ago•6 comments

Usenet rewind archive search engine

https://www.usenet-rewind.com/
66•cstadler1869•6h ago•14 comments

Show HN: Bodily Oddities

https://vester.si/bodily-oddities/
260•vesterde•1d ago•171 comments

Logo Programming

https://el.media.mit.edu/logo-foundation/what_is_logo/logo_programming.html
286•azhenley•3d ago•115 comments

OpenAI agents carried out an undisclosed attack on RubyGems

https://www.rubyhack.ai/
727•chao-•11h ago•406 comments

Designing for Dual Screen and Foldable Devices with CSS (2023)

https://blog.stephaniestimac.com/posts/2023/05/design-foldable-devices/
36•mooreds•1d ago•7 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
165•geneticdrifts•17h ago•107 comments

Litelm: LiteLLM Without the Bloat

https://github.com/kennethwolters/litelm
148•kennethwolters•16h ago•49 comments

Project Blinkenlights

https://blinkenlights.de/en/
97•doener•12h ago•32 comments

Resistance Training Prescription for Muscle Function, Hypertrophy in Health

https://pmc.ncbi.nlm.nih.gov/articles/PMC12965823/
14•ultral•1h ago•2 comments

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

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

Bomb Sense (2021)

https://danboland.net/2021/07/15/bomb-sense.html
14•surprisetalk•2d ago•0 comments

Rune is now open source

https://rune.build/blog/rune-is-now-open-source
191•ernestrc•19h ago•58 comments

GrapheneOS' rewritten Messages app is released

https://github.com/GrapheneOS/Messaging/releases/tag/13
280•microtonal•16h ago•206 comments

Detailed report on the use of solar geoengineering

https://www.technologyreview.com/2026/09/10/1143804/this-road-map-could-help-us-decide-whether-to...
13•coloneltcb•1d ago•3 comments

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

https://snap.berkeley.edu/
147•dr_kiszonka•17h ago•84 comments

WeWorm: Zero-Click WeChat Worm

https://calif.io/research/weworm
28•BlackEarth•5h ago•1 comments

AlphaGenome maps 9B DNA variants

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

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

https://github.com/mirza-rizvi/ResolveHQ
61•mirza_rizvi•13h ago•21 comments

Testing Race Conditions

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

We've followed their lives for six decades; now the stars of 7 Up are bowing out

https://www.bbc.co.uk/news/articles/crm932el3yjo
4•mellosouls•19m ago•0 comments

Another way to leak traffic on Android has been discovered

https://mullvad.net/en/blog/another-way-to-leak-traffic-on-android-has-been-discovered
87•mhitza•13h ago•13 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?