frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Microsoft open-sources "the earliest DOS source code discovered to date"

https://arstechnica.com/gadgets/2026/04/microsoft-open-sources-the-earliest-dos-source-code-disco...
30•DamnInteresting•50m ago•3 comments

Wake up! 16b

https://hellmood.111mb.de/wake_up_16b_writeup.html
44•MaximilianEmel•1h ago•5 comments

Scammers are abusing an internal Microsoft account to send spam links

https://techcrunch.com/2026/05/21/scammers-are-abusing-an-internal-microsoft-account-to-send-spam/
18•spike021•1h ago•2 comments

Time to talk about my writerdeck

https://veronicaexplains.net/my-first-writerdeck/
296•hggh•7h ago•163 comments

My I3-Emacs Integration

https://khz.ac/software/i3-integration.html
30•nosolace•2h ago•7 comments

My two-part desk setup (2025)

https://arslan.io/2025/11/18/my-two-part-desk-setup/
223•James72689•3d ago•128 comments

On The <dl> (2021)

https://benmyers.dev/blog/on-the-dl/
351•ravenical•13h ago•107 comments

Sales and Dungeons: Thermal printer TTRPG utility

https://sales-and-dungeons.app/
48•hyperific•1d ago•16 comments

Green card seekers must leave U.S. to apply, Trump administration says

https://www.nytimes.com/2026/05/22/us/politics/green-card-changes-trump.html
578•tlhunter•1d ago•997 comments

Byrne's Euclid

https://www.c82.net/euclid/
18•layer8•3h ago•4 comments

Judson's Last Ride

https://www.realclearpolitics.com/articles/2026/05/22/judsons_last_ride_154150.html
32•NaOH•14h ago•1 comments

Show HN: Anyone interested in a tool helps to explore C++ ASTs

https://uvic-aurora.github.io/acav-manual/index.html
17•leomicv•2d ago•2 comments

.NET (OK, C#) finally gets union types

https://andrewlock.net/exploring-the-dotnet-11-preview-2-dotnet-gets-union-types/
140•ingve•1d ago•125 comments

New map reveals lost roads of the Roman Empire

https://www.scientificamerican.com/article/new-high-resolution-map-transforms-what-we-know-about-...
45•sohkamyung•3d ago•6 comments

SpaceX launches Starship v3 rocket

https://www.space.com/space-exploration/launches-spacecraft/spacex-starship-v3-megarocket-first-t...
365•busymom0•1d ago•235 comments

Hengefinder: Finding when the sun aligns with your street

https://victoriaritvo.com/blog/hengefinder/
112•evakhoury•1d ago•26 comments

Reverse engineering circuitry in a Spacelab computer from 1980

https://www.righto.com/2026/05/reverse-engineering-spacelab-computer.html
82•elpocko•9h ago•17 comments

80386 microcode disassembled

https://www.reenigne.org/blog/80386-microcode-disassembled/
221•nand2mario•13h ago•43 comments

ICE Awards $25M Iris-Scanning Contract to Bi2 Technologies

https://www.projectsaltbox.com/p/ice-awards-25-million-iris-scanning
75•cdrnsf•2h ago•16 comments

The Art of Money Getting

https://kk.org/cooltools/book-freak-210-the-art-of-money-getting/
199•dxs•13h ago•131 comments

Score by Collisions, Patch by Panic

https://blog.himanshuanand.com/2026/05/score-by-collisions-patch-by-panic/
4•unknownhad•3d ago•0 comments

PHP's Oddities

https://flowtwo.io/post/php%27s-oddities
96•thejoeflow•4d ago•126 comments

Don't Roll Your Own

https://susam.net/do-not-roll-your-own.html
83•adunk•3h ago•70 comments

Making deep learning go brrrr from first principles (2022)

https://horace.io/brrr_intro.html
153•tosh•14h ago•59 comments

Kindle loyalists scramble as Amazon turns page on old e-readers

https://www.reuters.com/business/retail-consumer/kindle-loyalists-scramble-amazon-turns-page-old-...
120•cf100clunk•4d ago•136 comments

-​-dangerously-skip-reading-code

https://olano.dev/blog/dangerously-skip/
97•fagnerbrack•16h ago•113 comments

NeuralNote

https://github.com/DamRsn/NeuralNote
8•hyperific•7h ago•0 comments

Toxic chemical leak at a manufacturing facility in Orange County

https://www.bbc.com/news/articles/c3w2l249j8go
112•borski•4h ago•79 comments

sp.h: Fixing C by giving it a high quality, ultra portable standard library

https://spader.zone/sp/
193•dboon•3d ago•173 comments

When does learning from data work (math starting from basic probability)

https://prateekchandrajha.github.io/vc-rademacher.html
3•alok-g•2h ago•0 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?