frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

On The <dl> (2021)

https://benmyers.dev/blog/on-the-dl/
283•ravenical•6h ago•85 comments

It's time to talk about my writerdeck

https://veronicaexplains.net/my-first-writerdeck/
15•hggh•41m ago•4 comments

My two-part desk setup

https://arslan.io/2025/11/18/my-two-part-desk-setup/
96•James72689•2d ago•50 comments

Reverse engineering circuitry in a Spacelab computer from 1980

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

Texas woman arrested for Facebook post about town water quality

https://reclaimthenet.org/texas-woman-arrested-for-facebook-post-about-town-water-quality
186•abawany•1h ago•64 comments

Hengefinder: Finding When the Sun Aligns with Your Street

https://victoriaritvo.com/blog/hengefinder/
42•evakhoury•22h ago•13 comments

z386: An Open-Source 80386 Built Around Original Microcode

https://nand2mario.github.io/posts/2026/z386/
80•wicket•5h ago•17 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
118•tlhunter•21h ago•412 comments

80386 Microcode Disassembled

https://www.reenigne.org/blog/80386-microcode-disassembled/
176•nand2mario•7h ago•29 comments

PHP's Oddities

https://flowtwo.io/post/php%27s-oddities
56•thejoeflow•3d ago•61 comments

The Art of Money Getting

https://kk.org/cooltools/book-freak-210-the-art-of-money-getting/
117•dxs•6h ago•77 comments

Making Deep Learning Go Brrrr from First Principles (2022)

https://horace.io/brrr_intro.html
118•tosh•7h ago•44 comments

SpaceX launches Starship v3 rocket

https://www.space.com/space-exploration/launches-spacecraft/spacex-starship-v3-megarocket-first-t...
263•busymom0•19h ago•181 comments

Italy Cancels Boeing Pegasus Order, Shifting to Airbus A330 MRTT

https://www.euronews.com/my-europe/2026/05/21/italy-moves-to-airbus-a330-tankers-in-major-nato-al...
136•embedding-shape•3h ago•40 comments

We made our filesystem 47× faster by deleting it

https://microsandbox.dev/blog/oci-filesystem-47x-faster
10•appcypher•4d ago•5 comments

- -dangerously-skip-reading-code

https://olano.dev/blog/dangerously-skip/
44•fagnerbrack•9h ago•53 comments

Project Glasswing: An Initial Update

https://www.anthropic.com/research/glasswing-initial-update
502•louiereederson•23h ago•298 comments

Evaluating Spec CPU2026

https://chipsandcheese.com/p/evaluating-spec-cpu2026
12•zdw•3h ago•1 comments

Oura says it gets government demands for user data

https://this.weekinsecurity.com/oura-says-it-gets-government-demands-for-user-data-will-it-share-...
207•donohoe•5h ago•124 comments

Lisp in Vim (2019)

https://susam.net/lisp-in-vim.html
36•whent•4h ago•5 comments

Highest Random Weight in Elixir

https://jola.dev/posts/highest-random-weight-in-elixir
46•shintoist•2d ago•2 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-...
54•cf100clunk•4d ago•70 comments

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

https://spader.zone/sp/
139•dboon•3d ago•131 comments

Rubish: A Unix shell written in pure Ruby

https://github.com/amatsuda/rubish
148•winebarrel•12h ago•91 comments

Shipping a laptop to a refugee camp in Uganda

https://notesbylex.com/shipping-a-laptop-to-a-refugee-camp-in-uganda
634•lexandstuff•21h ago•220 comments

Why Japanese companies do so many different things

https://davidoks.blog/p/why-japanese-companies-do-so-many
818•d0ks•1d ago•380 comments

Electrobun 2.0 will be decoupled from Bun due to the Rust rewrite

https://twitter.com/i/status/2058064720553222567
84•bundie•7h ago•80 comments

Solving the “Zork” Mystery

https://www.dpolakovic.space/blogs/zork-part2
42•dpola•3d ago•16 comments

Improving C# Memory Safety

https://devblogs.microsoft.com/dotnet/improving-csharp-memory-safety/
120•soheilpro•2d ago•22 comments

The FBI Wants 'Near Real-Time' Access to US License Plate Readers

https://www.wired.com/story/security-news-this-week-fbi-license-plate-reader-real-time-access/
144•Brajeshwar•5h ago•70 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?