frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Edsger – A handwritten Clojure REPL for the reMarkable 2

https://handwritten.danieljanus.pl/2026-06-01-edsger.html
51•nathell•15h ago•12 comments

1-Click GitHub Token Stealing via a VSCode Bug

https://blog.ammaraskar.com/github-token-stealing/
430•ammar2•19h ago•64 comments

Show HN: I reverse-engineered the world maps of Test Drive III (1990 DOS game)

https://github.com/s-macke/Test-Drive-3-Maps
108•s-macke•3d ago•30 comments

Use your Nvidia GPU's VRAM as swap space on Linux

https://github.com/c0dejedi/nbd-vram
325•tanelpoder•11h ago•88 comments

AI outperforms law professors in Stanford Law study

https://law.stanford.edu/press/ai-outperforms-law-professors-in-stanford-law-study/
261•berlianta•11h ago•203 comments

MAI-Code-1-Flash

https://microsoft.ai/news/introducingmai-code-1-flash/
476•EvanZhouDev•15h ago•211 comments

The Unreasonable Redundancy of Nature's Protein Folds

https://research.ligo.bio/posts/unreasonable-redundancy-of-natural-protein-folds/
99•ray__•6h ago•28 comments

It is an amazing time for programmers

https://46elks.com/blog/2026/05/29/an-amazing-time-for-programmers
66•jlundberg•2h ago•36 comments

Microsoft Doubles Down on Controversial Quantum Computing Claims

https://www.science.org/content/article/doubling-down-controversial-claims-microsoft-accelerates-...
32•igortru•4h ago•37 comments

CT scans of BYD car parts

https://www.lumafield.com/scan-of-the-month/byd
391•viasfo•14h ago•236 comments

Writing Portable ARM64 Assembly (2023)

https://ariadne.space/2023/04/12/writing-portable-arm-assembly.html
23•luu•2d ago•5 comments

My thoughts after using Clojure for about a month

https://www.acdw.net/clojure/
224•speckx•14h ago•112 comments

Pluto.jl 1.0 release – reactive notebook for Julia

https://discourse.julialang.org/t/pluto-1-0-release/137296
138•fons-p•11h ago•15 comments

DIY Bipedal Robot Used Pneumatic "Air-Muscles" Instead of Motors

https://spectrum.ieee.org/shadow-walker-biped-humanoid-robot
16•sohkamyung•2d ago•7 comments

U of T researchers demonstrate AI worm could target any online device

https://www.utoronto.ca/news/u-t-researchers-demonstrate-ai-worm-could-target-any-online-device
44•shscs911•6h ago•11 comments

Roku LT Operating System open source distribution

https://blog.roku.com/developer/roku-lt-os
77•dpmdpm•9h ago•24 comments

Capstone – multi-platform, multi-architecture disassembly framework

https://www.capstone-engine.org/
58•gregsadetsky•8h ago•1 comments

Words of Type

https://wiki.wordsoftype.com/
70•tobr•2d ago•12 comments

HP re-releases classic computer science calculator: The HP-16C

https://hpcalcs.com/product/hp-16c-collectors-edition/
177•dm319•15h ago•107 comments

Gmail thinks I'm stupid, so I left

https://moddedbear.com/gmail-thinks-im-stupid-so-i-left
978•speckx•15h ago•646 comments

Jonathan Franzen on Talent, Theatre, and His Next Novel

https://www.newyorker.com/books/this-week-in-fiction/jonathan-franzen-06-08-26
5•samclemens•1d ago•0 comments

Recovering Eric Graham's 1987 Amiga Juggler raytracer source code

https://alphapixeldev.com/recovering-eric-grahams-1987-amiga-juggler-raytracer-source-code/
10•mariuz•4h ago•2 comments

How we index images for RAG

https://www.kapa.ai/blog/how-we-index-images-for-rag
141•mooreds•18h ago•20 comments

Open Repair Data Standard

https://openrepair.org/open-data/open-standard/
134•cassepipe•15h ago•9 comments

Show HN: Phive, a Gomoku-like game to play with friends or solo

https://phive.app
10•0xCA1EB•3d ago•7 comments

4K years ago, Mohenjo-daro grew more equal over time

https://archaeologymag.com/2026/05/mohenjo-daro-grew-more-equal-over-time/
100•marojejian•12h ago•46 comments

OpenFOV – Webcam head tracking for iRacing

https://www.openfov.com/
127•mwit2023•3d ago•61 comments

Preparing for KDE Plasma's Last X11-Supported Release

https://blog.davidedmundson.co.uk/blog/596/
193•jandeboevrie•20h ago•240 comments

Trump signs downsized AI order after weeks of reversals

https://www.politico.com/news/2026/06/02/trump-signs-downsized-ai-order-00946389
213•_alternator_•18h ago•157 comments

Fidonet: Technology, Use, Tools, and History (1993)

https://www.fidonet.org/inet92_Randy_Bush.txt
170•BruceEel•20h ago•69 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?