frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Japan develops a method to recover up to 90% of lithium from used EV batteries

https://tech.supercarblondie.com/japan-recovers-up-to-90-of-lithium-from-used-ev-batteries/
354•donohoe•5h ago•87 comments

YouTrackDB is a general-use object-oriented graph database

https://github.com/JetBrains/youtrackdb
90•gjvc•4h ago•24 comments

The Git history command deserves more attention

https://lalitm.com/post/git-history/
243•turbocon•6h ago•139 comments

Fundamentals of Wireless Communication (2005)

https://web.stanford.edu/~dntse/wireless_book.html
115•teleforce•5h ago•3 comments

How to build a circular LCD clock

https://blinry.org/lcd-clock/
64•birdculture•2d ago•20 comments

Building and shipping Mac and iOS apps without opening Xcode

https://scottwillsey.com/building-and-shipping-mac-and-ios-apps-without-ever-opening-xcode/
437•speckx•13h ago•191 comments

The Economics of Recursive Self-Improvement [pdf]

https://elasticity.institute/rsi-paper.pdf
77•apsec112•6h ago•19 comments

Is x86 ready to ACE it?

https://chipsandcheese.com/p/is-x86-ready-to-ace-it
60•mfiguiere•6h ago•8 comments

Satellite Tracker – Live Map of Starlink and 30k Satellites

https://satellitemap.space/
69•rolph•5h ago•22 comments

An Englishwoman who sketched India before photography took hold

https://www.bbc.com/news/articles/cm2drrv6q54o
127•1659447091•8h ago•37 comments

MorphoHDL: A minimalistic language for growing circuits

https://paradigms-of-intelligence.github.io/morpho/
56•jacktang•6h ago•8 comments

World-First 'Super Alloy' Could Transform the Way Metals Are Made

https://www.sciencealert.com/world-first-super-alloy-could-transform-the-way-metals-are-made
52•tejohnso•4d ago•26 comments

Our Amish Language

https://www.thedial.world/articles/news/amish-pennsylvania-dutch
36•NaOH•5h ago•14 comments

Jektex 0.2.0 – A Jekyll plugin for LaTeX rendering is now ~10x faster

https://github.com/yagarea/jektex
4•yagarea•2d ago•1 comments

Writing a bindless GPU abstraction layer

https://www.kevin-gibson.com/blog/writing-a-bindless-gpu-abstraction-layer/
32•surprisetalk•4d ago•1 comments

The infinite scroll may become endangered if controversial Calif. law passes

https://www.sfgate.com/politics/article/meta-social-media-teenagers-22337724.php
149•Stratoscope•12h ago•260 comments

What will be left for us to work on?

https://www.normaltech.ai/p/what-will-be-left-for-us-to-work
112•randomwalker•5h ago•111 comments

Two Case Studies of NaN

https://sebsite.pw/w/20260709-nan.html
5•ryantsuji•4d ago•0 comments

OpenAI's Ad Business Is on Pace to Miss Its Own Forecast by 90%, Analyst Says

https://www.adweek.com/media/openais-ad-business-is-on-pace-to-miss-its-own-forecast-by-90-analys...
31•EvgeniyZh•2h ago•13 comments

Building Food Metadata with LLM Juries

https://careersatdoordash.com/blog/building-food-metadata-with-llm-juries-context-optimization-mu...
31•tie-in•6h ago•8 comments

Linux on the Sega 32X. Who needs hardware synchronization primitives anyway?

https://cakehonolulu.github.io/linux-on-32x/
121•cakehonolulu•13h ago•23 comments

Apple's new SpeechAnalyzer API, benchmarked against Whisper and its predecessor

https://get-inscribe.com/blog/apple-speech-api-benchmark.html
526•get-inscribe•15h ago•210 comments

Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

https://sleuth-io.github.io/sx/2026/07/10/your-dropbox-is-now-a-skill-server.html
34•detkin•8h ago•29 comments

Ancient Roman Board Game

https://ludus-coriovalli.web.app/
119•nobody9999•4d ago•45 comments

Show HN: I implemented a neural network in SQL

https://github.com/xqlsystems/xarray-sql/blob/claude/xarray-sql-mnist-demo/benchmarks/nn.py
87•alxmrs•11h ago•17 comments

SalesPatriot (YC W25) Is Hiring Full Stack Engineers (SF)

https://jobs.ashbyhq.com/SalesPatriot/df223727-5781-433e-bc75-2aa5bf8dc8d7
1•maciejSz•10h ago

Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices

https://hackney.app/
44•griffinli•16h ago•36 comments

Show HN: Jacquard, a programming language for AI-written, human-reviewed code

https://github.com/jbwinters/jacquard-lang
81•jbwinters•15h ago•44 comments

TFTP Honey Pot Results

https://bruceediger.com/posts/tftp-honeypot-results/
79•speckx•12h ago•34 comments

A Study of Microsoft's Early 2026 Rollout of Claude Code and GitHub Copilot CLI

https://arxiv.org/abs/2607.01418
56•softwaredoug•9h 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?