frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

I ♥ RSS – A directory of people who love RSS

https://andrewshell.org/2026/07/i-%e2%99%a5-rss/
59•speckx•44m ago•30 comments

Cursor removed cost information from the usage page and CSV export

https://forum.cursor.com/t/usage-page-to-token-amount-what/167153
130•EugeneOZ•2h ago•53 comments

The Art of 64-bit Assembly

https://nostarch.com/art-64-bit-assembly-v2
90•0x54MUR41•3h ago•46 comments

Kaisel – Routes as Values. Dart 3 Native Router for Flutter

https://kaisel.dev/
14•TheWiggles•51m ago•0 comments

RipGrep musl binaries occasionally segfault during very-large searches

https://github.com/BurntSushi/ripgrep/issues/3494
181•throwaway2037•5h ago•102 comments

Explorative modeling: Train on the best of K guesses

https://alexiglad.github.io/blog/2026/explorative_modeling/
24•DSemba•2h ago•4 comments

Pgtestdb's template cloning approach to testing is fast

https://brandur.org/fragments/pgtestdb
23•brandur•1h ago•5 comments

A Surveillance Treaty in Disguise: Canada Signs UN Cybercrime Convention

https://www.michaelgeist.ca/2026/07/a-surveillance-treaty-in-disguise-the-trouble-with-canadas-qu...
151•iamnothere•3h ago•79 comments

Register deprivation: spills and runtime under forced register scarcity

https://rjp.io/blog/2026-07-19-register-deprivation
11•surprisetalk•2d ago•0 comments

Study uncovers lost 'golden age' of languages

https://news.yale.edu/2026/07/23/study-uncovers-lost-golden-age-languages
33•gmays•2d ago•20 comments

Charlie Stross – On the non-use of AI in my writing process

https://www.antipope.org/charlie/blog-static/2026/08/on-the-non-use-of-ai-in-my-wri.html
79•jwx48•4h ago•65 comments

Linux on ESP32

https://github.com/GrieferPig/esp32-s31-linux
44•boveyking•3d ago•15 comments

Manual: •.,:;?·

https://type.today/en/journal/dots
90•behnamoh•2d ago•18 comments

Rear center fuel tank adds roughly 20k liters and extends range by 1k NM

https://www.airbus.com/en/newsroom/press-releases/2026-06-worlds-longest-range-aircraft-the-airbu...
18•r2sk5t•4d ago•10 comments

Flint: A Visualization Language for the AI Era

https://microsoft.github.io/flint-chart/
224•vinhnx•14h ago•65 comments

RamenHaus

https://ramen.haus/
170•oler•8h ago•83 comments

Kontigo (YC S24) Is Hiring

https://www.ycombinator.com/companies/kontigo/jobs/xAo6tMt-founding-engineer
1•jecastillof•5h ago

qm – Multiplayer agent harness for work

https://github.com/yc-software/qm
632•tosh•23h ago•146 comments

Solid Queue 1.6.0 now supports fiber workers

https://github.com/rails/solid_queue/releases/tag/v1.6.0
71•earcar•9h ago•28 comments

A tiny holdout building in the middle of Macy’s is back in view

https://ephemeralnewyork.wordpress.com/2026/07/27/hidden-by-billboards-for-over-100-years-the-tin...
154•donohoe•3d ago•43 comments

Elevators

https://john.fun/elevators
1511•Jrh0203•1d ago•380 comments

How to Exist

https://www.raptitude.com/2026/07/how-to-exist/
321•walterbell•17h ago•189 comments

Software for One

https://www.ajwaxman.com/writing/software-for-one
199•awaxman11•3d ago•204 comments

Toast IDE Gets Markdown Spell Checking

https://github.com/paradise-runner/toast
3•dividedcomet•2h ago•0 comments

Run Kimi K3 using 29 GB of RAM at 0.50 tok/s

https://github.com/sqliteai/waste
304•marcobambini•1d ago•142 comments

GitHub has alternatives, but no replacement

https://lalitm.com/post/github-alternatives/
67•lalitmaganti•1h ago•87 comments

The development pipeline is a production system

https://sundry.jerryorr.com/2026/07/31/development-pipeline-is-a-production-system
134•firefoxd•14h ago•66 comments

Assessment of open AI math results

https://twitter.com/stalkermustang/status/2083485500250198453
6•paulpauper•29m ago•1 comments

Astro Loop

https://pubdeer.com/
22•BaseBaal•5h ago•4 comments

The First Idempotency Key

https://hatchet.run/blog/first-idempotency-key
28•abelanger•4d ago•5 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?