frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

JSON-LD Explained for Personal Websites

https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
51•ethanhawksley•1h ago•11 comments

Prefer duplication over the wrong abstraction (2016)

https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
324•rafaepta•4h ago•231 comments

(How to Write a (Lisp) Interpreter (In Python)) (2010)

https://norvig.com/lispy.html
124•tosh•4h ago•37 comments

Beyond All Reason (Free Total Annihilation Inspired RTS)

https://www.beyondallreason.info
357•mosiuerbarso•8h ago•206 comments

Identity verification on Claude

https://support.claude.com/en/articles/14328960-identity-verification-on-claude
306•bathory•7h ago•269 comments

The minimum viable unit of saleable software

https://brandur.org/minimum-viable-unit
62•brandur•3h ago•32 comments

Show HN: CleverCrow: give tokens to your favorite projects

https://clevercrow.io
12•zhubert•1h ago•3 comments

An Embedded Linux on a Single Floppy

https://github.com/w84death/floppinux
26•modinfo•2d ago•13 comments

Occupancy Math on the AMD MI355X: A From-First-Principles Guide

https://indianspeedster.github.io/blog/occupancy-math-mi355x/
28•skidrow•4d ago•0 comments

A 3D voxel game engine written in APL

https://github.com/namgyaaal/avoxelgame
130•sph•12h ago•11 comments

15-minute at-home Lyme disease tick test

https://www.bostonglobe.com/2026/06/17/business/lyme-disease-tick-test/
207•bookofjoe•3d ago•142 comments

Wildcard (YC W25) is hiring an applied ML engineer

https://www.ycombinator.com/companies/wildcard/jobs/SEmo4di-founding-applied-ml-engineer
1•kaushikmahorker•3h ago

Loupe – A iOS app that raises awareness about what native apps can see

https://github.com/mysk-research/loupe
485•Cider9986•1d ago•198 comments

Developers don't understand CORS (2019)

https://fosterelli.co/developers-dont-understand-cors
320•toilet•18h ago•246 comments

System call instrumentation on Linux/x86‑64 using memory‑indirect calls, part I

https://www.humprog.org/~stephen/blog/2026/06/15/#system-call-instrumentation-on-intel-negative-r...
32•matt_d•4d ago•12 comments

Show HN: Pulse – Dashboard for Claude Code, approve tool calls from your phone

https://github.com/nikitadoudikov/claude-pulse
21•nikitadvd•23h ago•9 comments

Running MicroVMs in Proxmox VE, the Easy Way

https://taoofmac.com/space/blog/2026/06/18/1845
187•zdw•2d ago•31 comments

Show HN: TownSquare, a tiny presence layer for websites

https://townsquare.cauenapier.com/
227•cauenapier•1d ago•132 comments

Burnout is real for open source maintainers

https://openjsf.org/blog/burnout-is-real-for-open-source-maintainers
91•theanonymousone•3h ago•42 comments

Proportional-Integral-Derivative (PID) controllers

https://en.wikipedia.org/wiki/PID_controller
72•dhorthy•2d ago•45 comments

Slow breathing modulates brain function and risk behavior

https://www.cell.com/neuron/fulltext/S0896-6273(26)00339-9
349•croes•21h ago•99 comments

Excessive nil pointer checks in Go

https://konradreiche.com/blog/excessive-nil-pointer-checks-in-go/
78•ingve•3d ago•57 comments

Fossil Fuels Are 40% of Freight Shipping Tonnage, but Half Its Fuel Use

https://cleantechnica.com/2026/06/16/shipping-freight-energy-fossil-cargo/
109•choult•5h ago•76 comments

Cocktail Optimization, an Integer Programming Problem

https://bunkum.us/2026/06/18/cocktail-ingredients-milp
9•ftgregg•2d ago•2 comments

Renting a sewing machine from the library

https://www.bbc.com/future/article/20260618-the-weird-and-wonderful-libraries-of-finland
324•sohkamyung•21h ago•187 comments

The Commodore Callback 8020 smart flip phone

https://www.wired.me/story/commodore-made-a-digital-detox-phone-that-isnt-dumb
103•Audiophilip•3d ago•89 comments

Two Qwen3 models on one DGX Spark: the residency math

https://www.devashish.me/p/two-qwen3-models-on-one-dgx-spark
77•devashish86•3d ago•36 comments

The brain was not designed for this much bad news

https://www.sciencedaily.com/releases/2026/06/260614012006.htm
321•colinprince•16h ago•269 comments

The early hiring funnel is now breaking on both ends

https://hbr.org/2026/06/ai-has-broken-hiring-heres-how-to-fix-it
77•ChrisArchitect•4h ago•126 comments

Epoll vs. io_uring in Linux

https://sibexi.co/posts/epoll-vs-io_uring/
243•Sibexico•21h ago•57 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?