frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

US Court of Appeals: TOS may be updated by email, use can imply consent [pdf]

https://cdn.ca9.uscourts.gov/datastore/memoranda/2026/03/03/25-403.pdf
288•dryadin•6h ago•196 comments

Fontcrafter: Turn Your Handwriting into a Real Font

https://arcade.pirillo.com/fontcrafter.html
120•rendx•3h ago•48 comments

Ireland shuts last coal plant, becomes 15th coal-free country in Europe (2025)

https://www.pv-magazine.com/2025/06/20/ireland-coal-free-ends-coal-power-generation-moneypoint/
229•robin_reala•3h ago•87 comments

Owner of ICE detention facility sees big opportunity in AI man camps

https://techcrunch.com/2026/03/08/owner-of-ice-detention-facility-sees-big-opportunity-in-ai-man-...
24•monkeydust•16m ago•6 comments

Unlocking Python's Cores:Energy Implications of Removing the GIL

https://arxiv.org/abs/2603.04782
47•runningmike•3d ago•21 comments

Show HN: VS Code Agent Kanban: Task Management for the AI-Assisted Developer

https://www.appsoftware.com/blog/introducing-vs-code-agent-kanban-task-management-for-the-ai-assi...
13•gbro3n•2h ago•4 comments

Agent Safehouse – macOS-native sandboxing for local agents

https://agent-safehouse.dev/
658•atombender•16h ago•158 comments

Microscopes can see video on a laserdisc

https://www.youtube.com/watch?v=qZuR-772cks
502•zdw•1d ago•67 comments

PCB devboard the size of a USB-C plug

https://github.com/Dieu-de-l-elec/AngstromIO-devboard
205•zachlatta•1d ago•47 comments

Ask HN: What Are You Working On? (March 2026)

188•david927•13h ago•696 comments

Segagaga Has Been Translated into English

https://www.thedreamcastjunkyard.co.uk/2026/02/segagaga-has-finally-been-translated.html
19•nanna•1d ago•2 comments

Every single board computer I tested in 2025

https://bret.dk/every-single-board-computer-i-tested-in-2025/
184•speckx•4d ago•60 comments

FrameBook

https://fb.edoo.gg
463•todsacerdoti•21h ago•77 comments

Nvidia backs AI data center startup Nscale as it hits $14.6B valuation

https://www.cnbc.com/2026/03/09/nscale-ai-data-center-nvidia-raise.html
27•voxadam•2h ago•16 comments

My Homelab Setup

https://bryananthonio.com/blog/my-homelab-setup/
268•photon_collider•20h ago•177 comments

We Stopped Using the Mathematics That Works

https://gfrm.in/posts/why-decision-theory-lost/index.html
45•slygent•4h ago•10 comments

Linux Internals: How /proc/self/mem writes to unwritable memory (2021)

https://offlinemark.com/an-obscure-quirk-of-proc/
99•medbar•14h ago•22 comments

We should revisit literate programming in the agent era

https://silly.business/blog/we-should-revisit-literate-programming-in-the-agent-era/
262•horseradish•17h ago•179 comments

Artificial-life: A simple (300 lines of code) reproduction of Computational Life

https://github.com/Rabrg/artificial-life
128•tosh•16h ago•18 comments

Why can't you tune your guitar? (2019)

https://www.ethanhein.com/wp/2019/why-cant-you-tune-your-guitar/
225•digitallogic•4d ago•155 comments

I made a programming language with M&Ms

https://mufeedvh.com/posts/i-made-a-programming-language-with-mnms/
95•tosh•18h ago•37 comments

My “grand vision” for Rust

https://blog.yoshuawuyts.com/a-grand-vision-for-rust/
217•todsacerdoti•4d ago•213 comments

Living human brain cells play DOOM on a CL1 [video]

https://www.youtube.com/watch?v=yRV8fSw6HaE
210•kevinak•22h ago•207 comments

I love email (2023)

https://blog.xoria.org/email/
60•surprisetalk•3d ago•27 comments

Show HN: Mcp2cli – One CLI for every API, 96-99% fewer tokens than native MCP

https://github.com/knowsuchagency/mcp2cli
111•knowsuchagency•7h ago•67 comments

How the Sriracha guys screwed over their supplier

https://old.reddit.com/r/KitchenConfidential/comments/1ro61g2/how_the_sriracha_guys_screwed_over_...
267•thunderbong•9h ago•99 comments

Ask HN: How to be alone?

536•sillysaurusx•1d ago•394 comments

The death of social media is the renaissance of RSS (2025)

https://www.smartlab.at/rss-revival-life-after-social-media/
183•jruohonen•8h ago•117 comments

Z80 Sans – a disassembler in a font (2024)

https://github.com/nevesnunes/z80-sans
127•pabs3•4d ago•14 comments

FFmpeg at Meta: Media Processing at Scale

https://engineering.fb.com/2026/03/02/video-engineering/ffmpeg-at-meta-media-processing-at-scale/
13•sudhakaran88•7h ago•2 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•9mo ago

Comments

balloob•9mo 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•9mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•9mo ago
Comments moved thither. Thanks!
pabs3•9mo ago
They are two different articles, I don't think that was correct.
tomhow•9mo 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•9mo ago
Thanks for the response, guess that makes sense.
pabs3•9mo 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?